[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#417121: marked as done (pcmciautils: Data Corruption while using Texas Instrument PCI7420 --CardBus)

Your message dated Thu, 13 Aug 2009 23:18:49 +0200
with message-id <20090813211849.GA30992@galadriel.inutil.org>
and subject line Re: Bug#417121: can you reproduce with a later kernel?
has caused the Debian Bug report #417121,
regarding pcmciautils: Data Corruption while using Texas Instrument PCI7420   --CardBus
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 owner@bugs.debian.org
immediately.)


-- 
417121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417121
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: pcmciautils
Version: 014-3
Severity: grave
Justification: renders package unusable

-----

As the Card reader does not work with Debian-3.1 on my Acer Aspire 1524
Laptop, I download the Debian Live CD of Testing, 2 days back (made on
29th March). I booted the machine from that all the testing is done
while the machine was running from the CD.

I have an SD card, which I use in my camera and wanted to read that.
When I insert the Card reader (with the SD card in the socket), I get a
Syslog message:
--------------------------
Apr  1 15:21:50 debian kernel: pccard: PCMCIA card inserted into slot 1
Apr  1 15:21:50 debian kernel: cs: memory probe 0xa0000000-0xa0ffffff:
excluding 0xa0000000-0xa00fffff
Apr  1 15:21:50 debian kernel: pcmcia: registering new device pcmcia1.0
Apr  1 15:21:50 debian kernel: Probing IDE interface ide2...
Apr  1 15:21:51 debian kernel: hde: Memory Card Adapter, CFA DISK drive
Apr  1 15:21:52 debian kernel: ide2 at 0x100-0x107,0x10e on irq 3
Apr  1 15:21:52 debian kernel: hde: max request size: 128KiB
Apr  1 15:21:52 debian kernel: hde: 990976 sectors (507 MB) w/1KiB
Cache, CHS=3871/8/32
Apr  1 15:21:52 debian kernel:  hde:hde: status error: status=0x7f {
DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index
Error }
Apr  1 15:21:52 debian kernel: hde: status error: error=0x00 { }
Apr  1 15:21:52 debian kernel: ide: failed opcode was: unknown
Apr  1 15:21:52 debian kernel: hde: drive not ready for command
Apr  1 15:21:52 debian kernel: ide2: reset: master: error (0x40?)
Apr  1 15:21:52 debian kernel:  hde1
Apr  1 15:21:52 debian kernel: ide-cs: hde: Vpp = 0.0
------------------------------------

While starting the test, the card was blank and was formatted in the
camera (the card reader works fine in Windows), and I had copied an
image and a small text file while running Debian CD from my hard disk
without any error. (The name for that file (pict0001.jpg) is seen 
below in the output).

After writing the file, I did 'sync. 
Then I could open the file with 'gimp' from the '/media/usbdisk/....'
area. However, after unmounting, when I mount it again (this time 'ro'
for safefty),
I get an error while opening it with 'gimp': Corrupt JPEG data: 25
extraneous
bytes before marker 0x0f.
Then it shows Unsupported marker type 0x0f.

('/dev/hde1' is mounted on '/media/usbdisk' as vfat).
Also, 'ls -l /media/usbdisk/dcim/100km006' shows something strange.

---------
-rwxr-xr-x 1 root root       0 1980-01-01 00:00 ??
-rwxr-xr-x 1 root root       0 1980-01-01 00:00 ???
?--------- ? ?    ?          ?                ?
/media/usbdisk/dcim/100km006/????w??`
-rwxr-xr-x 1 root root 1441808 2007-03-31 01:43 pict0001.jpg
-rwxr-xr-x 1 root root      13 2007-04-01 00:03 ttab
------------------
Notice several question marks appearing above.

Though 'ls -l' shows the file sizes on hard disk and the SD card to be
the same, 'md5sum' differs between the two. Being curious, I tried
the same again on a different file. Copy a file while being mounted in
'rw' mode, 'sync' and then 'mount -o remount,ro'. Till this step,
'md5sum' remains the same. However, once 'umount' and 'mount' with
either in 'ro' or 'rw', the 'md5sum' differs.

The same repeats for any small Text files.

Once in a while, I have also noticed FAT file system panic:
----------
Apr  1 15:57:35 debian kernel: FAT: Filesystem panic (dev hde1)
Apr  1 15:57:35 debian kernel:     invalid access to FAT (entry
0x0000e001)
---------
However, I have checked that no error message appeared in 'syslog'
while I mounted the SD card 'rw' to the time I mount it 'ro'.

Note that the same error repeats with Knoppix-5.1.1 Live CD.

Since Data corruption like this without an error message is a Grave
error, I am filing a RC Bug.
However, I am not clear whether the Bug lies in PCMCIA, or in the
respective KERNEL module.
Since both are part of Debian Etch, I am leaving it to the package
maintainer to reassign it to Kernel, if appropriate.

For your possible inspection, I have also attached the output of
'lspci -v' (lspci-v), and 'lsmod' (lsmod) along with this mail.

Subhashis
------------

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages pcmciautils depends on:
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared
libraries
ii  libsysfs2                   2.1.0-1      interface library to sysfs
ii  lsb-base                    3.1-23.1     Linux Standard Base 3.1
init scrip
ii  module-init-tools           3.3-pre4-2   tools for managing Linux
kernel mo

Versions of packages pcmciautils recommends:
ii  udev                          0.105-4    /dev/ and hotplug
management daemo

-- no debconf information


-- 
  subhashisroy@gmail.com
  subhashis3@fastmail.fm

-- 
http://www.fastmail.fm - Access all of your messages and folders
                          wherever you are

Attachment: lspci-v
Description: Binary data

Attachment: lsmod
Description: Binary data


--- End Message ---
--- Begin Message --- 
On Sat, Feb 07, 2009 at 03:30:20PM +0100, Moritz Muehlenhoff wrote:
> On Sat, Nov 22, 2008 at 02:17:34PM +0100, Moritz Muehlenhoff wrote:
> > On Thu, May 31, 2007 at 12:55:41PM +0200, Subhashis Roy wrote:
> > > Hi,
> > >
> > > I do find similar problem with the latest 2.6.21.3 (i686 image) kernel in Sid.
> > >
> > > What is peculiar is that the kernel tries to access the card both as
> > > '/dev/sda' and '/dev/sdb' simultaneously, as the 'dmesg' shows. 'udev'
> > > does create '/dev/sda1', but access to '/dev/sdb' throws a bunch of
> > > Error messages with the final one being 'failure to read the partition
> > > table' (this is probably expected as the card is already accessed as
> > > '/dev/sda').
> > > I can mount the card and copy an image file from hard disk successfully
> > > to it (can be viewed in the camera LCD screen).  Successive mounting of 
> > > the card in the laptop (Acer Aspire 1524) shows 'md5sum' of
> > > that file to be different than the original file. Displaying it in the
> > > machine also fails. However, I noticed that the actual file on the card
> > > remained fine (viewable on the camera LCD).  Therefore, it appears
> > > that the problem is in 'reading' the contents of the card (the way
> > > kernel access the card seems incorrect).
> > >
> > > I checked the same behaviour with the earlier 2.6.18 kernel in Etch.
> > 
> > Does this error still occur with more recent kernel versions?
> > 
> > If you're running Etch, could you try to reproduce this bug
> > with the 2.6.24 based kernel added in 4.0r4?
> > http://packages.qa.debian.org/l/linux-2.6.24.html
> 
> Have you been able to reproduce the problem with more recent kernel
> versions?

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz

--- End Message ---
Reply to: