[hafqa] [hafqa] [Bug 2940] New: oversized partition on N810 internal card from factory

From: bugzilla-daemon at lists.maemo.org bugzilla-daemon at lists.maemo.org
Date: Thu Feb 14 10:50:22 EET 2008
https://bugs.maemo.org/show_bug.cgi?id=2940

           Summary: oversized partition on N810 internal card from factory
           Product: System software
           Version: 4.0
          Platform: N810
        OS/Version: IT OS
            Status: NEW
          Severity: normal
          Priority: Low
         Component: general
        AssignedTo: carlos at maemo.org
        ReportedBy: dufkaf at seznam.cz
         QAContact: hafqa at maemo.org


SOFTWARE VERSION:
2.2007.50-2

STEPS TO REPRODUCE THE PROBLEM:
1. buy new N810, complete wizard
2. (maybe optionally) test media player with supplied videos, start map
application, watch tutorial, disable key an touchscreen sound (for clean dmesg
log)
3. shutdown, power on, start xterm, type dmesg and see something like 
[    1.257812] mmcblk0: mmc1:0001 000000 1966080KiB 
[    1.257812]  mmcblk0: p1
[    1.257812]  mmcblk0: p1 exceeds device capacity
lots of I/O errors

4. type cat /proc partitions and see

major minor  #blocks  name

  31     0        128 mtdblock0
  31     1        384 mtdblock1
  31     2       2048 mtdblock2
  31     3       2048 mtdblock3
  31     4     257536 mtdblock4
 254     0    1966080 mmcblk0
 254     1    2007032 mmcblk0p1


This happened me twice with two different new devices. One German one bought in
January and one UK one bought in February. The German one was bought and
pre-tested by someone else so I ignored it but with the UK one I was the first
one to power it on and can verify this really comes straight from factory
without any modifications done by me.

The card still appears to work (unless one looks in kernel log) but will
produce user visible errors sooner or later when filled up more.


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the hafqa mailing list