Your message dated Wed, 7 Oct 2009 22:11:30 +0200
with message-id <20091007201130.gb5...@inutil.org>
and subject line Re: linux-image-2.6.18-4-686: modprobe diskonchip
unconditionally formatted my mtd device! :(
has caused the Debian Bug report #435054,
regarding linux-image-2.6.18-4-686: modprobe diskonchip unconditionally
formatted my mtd device! :(
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
435054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12etch2
Severity: critical
Justification: causes serious data loss
# modprobe diskonchip
syslog:
Jul 28 23:52:02 pxe1 kernel: NFTL driver: nftlcore.c $Revision: 1.98 $,
nftlmount.c $Revision: 1.41 $
Jul 28 23:52:41 pxe1 kernel: DiskOnChip found at 0xd8000
Jul 28 23:52:41 pxe1 kernel: DiskOnChip 2000 responds to DWORD access
Jul 28 23:52:41 pxe1 kernel: Detected 1 chips per floor.
Jul 28 23:52:41 pxe1 kernel: NAND device: Manufacturer ID: 0xec, Chip ID: 0x75
(Samsung NAND 32MiB 3,3V 8-bit)
Jul 28 23:52:41 pxe1 kernel: ECC error scanning DOC at 0x10000
Jul 28 23:52:41 pxe1 kernel: Found DiskOnChip ANAND Media Header at 0x10000
Jul 28 23:52:41 pxe1 kernel: ECC error scanning DOC at 0x14000
Jul 28 23:52:41 pxe1 kernel: Found DiskOnChip ANAND Media Header at 0x14000
Jul 28 23:52:41 pxe1 kernel: DataOrgID = ANAND
Jul 28 23:52:41 pxe1 kernel: NumEraseUnits = 2044
Jul 28 23:52:41 pxe1 kernel: FirstPhysicalEUN = 4
Jul 28 23:52:41 pxe1 kernel: FormattedSize = 32768000
Jul 28 23:52:41 pxe1 kernel: UnitSizeFactor = 255
Jul 28 23:52:41 pxe1 kernel: Bad block table at page 129, version 0x55
Jul 28 23:52:41 pxe1 kernel: Bad block table at page 161, version 0x55
Jul 28 23:52:41 pxe1 kernel: Formatting block 6
Jul 28 23:52:41 pxe1 kernel: Formatting block 7
Jul 28 23:52:41 pxe1 kernel: Formatting block 8
Jul 28 23:52:41 pxe1 kernel: Formatting block 9
Jul 28 23:52:41 pxe1 kernel: Formatting block 10
Jul 28 23:52:41 pxe1 kernel: Formatting block 11
and so on...
Jul 28 23:53:53 pxe1 kernel: Formatting block 2045
Jul 28 23:53:54 pxe1 kernel: Formatting block 2046
Jul 28 23:53:54 pxe1 kernel: Formatting block 2047
Jul 28 23:53:54 pxe1 kernel: nftla: unknown partition table
Jul 28 23:53:54 pxe1 kernel: Creating 1 MTD partitions on "DiskOnChip 2000
(NFTL Model)":
Jul 28 23:53:54 pxe1 kernel: 0x00018000-0x02000000 : " DiskOnChip BDTL
partition"
Jul 28 23:53:54 pxe1 kernel: Found alias of DOC at 0xd8000 to 0xda000
I'd rather expect a kernel message like "Failed to load ... use modprobe
diskonchip format=1 to format mtd" instead of it deciding on its own.
My whole intention was to backup the mtd before working with it - but
now it's trashed.
The kernel I'm using is based on the same code+patches, but with static
NFS+NIC and nfsroot support (so it'll pxeboot), otherwise it's identical
to the package. (my money is on "upstream" anyway).
Thanks,
Scott
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i586)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-geode
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
Moritz Muehlenhoff wrote:
> > I'd rather expect a kernel message like "Failed to load ... use modprobe
> > diskonchip format=1 to format mtd" instead of it deciding on its own.
> > My whole intention was to backup the mtd before working with it - but
> > now it's trashed.
> >
> > The kernel I'm using is based on the same code+patches, but with static
> > NFS+NIC and nfsroot support (so it'll pxeboot), otherwise it's identical
> > to the package. (my money is on "upstream" anyway).
>
> Does this still occur with later kernels, such as the one from Lenny?
No further feedback, closing the bug. If anyone reencouters the problem,
please reopen.
Cheers,
Moritz
--- End Message ---
