public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <damm@opensource.se>
To: linux-kernel@vger.kernel.org
Subject: 2.2.18 corruption: IDE + PCMCIA ?
Date: Thu, 08 Mar 2001 15:41:33 +0100	[thread overview]
Message-ID: <3AA79A1D.49E5ADC@opensource.se> (raw)

Hi all,

I've experienced some disk corruption on my laptop.

Scenario:
I'm cross-compiling tons of sources and I felt the need
to insert a CompactFlash card (via PCMCIA) in my laptop.
So I did, no problem: 
mounted, touched a file, umounted, cardctl-ejected.

Pretty soon my compilation stops:
bash: /usr/bin/sort: cannot execute binary file

Okey. The date on /usr/bin/sort is unchanged. Must be root to write.
I am NOT compiling as root. 
"File" on /usr/bin/sort says "data". No elf.
The only thing that the logs say:

modprobe: Can't locate module binfmt-464c

The filesystem on /usr is ext2.

I downloaded a new textutils.deb and installed it.
(But I made a backup of the corrupted file for some reason)
Searched the net and found some previous problem with
2.2.10 and DMA + CompactFlash.
Started to write a mail like this. 
Tried to do a ls -> Segmentation fault.
Then the entire machine crashed.
I rebooted the machine and fsck.ext2 complained about
my largest partition, did a manual check and now I'm back.

I wonder how many corrupted files there are left...

The machine is usually very stable, but I haven't done
much PCMCIA activity with it.

Maybe this is not even related to PCMCIA...

Anyway, this is what I do to my disk/controller:

/sbin/hdparm -c1 -d1 -m16 -a0 -S4 -u1 /dev/hda

I don't know if that has anything to do with it.

I've used this computer about three months now
and another Portege (3440CT) six months.
Never experienced anything like that...

So, all Portege users out there - be careful!

Cheers /

Magnus


Software:

linux-2.2.18
pcmcia-cs-3.1.23

Hardware:

Toshiba Portege 3480CT:

CPU and memory:

600MHz Speedstep PII 
192MByte ram.

Harddisk and controller:

PCI_IDE: unknown IDE controller on PCI bus 00 device 39, VID=8086,
DID=7199
PCI_IDE: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xbff0-0xbff7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xbff8-0xbfff, BIOS settings: hdc:pio, hdd:pio
hda: TOSHIBA MK1214GAP, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: TOSHIBA MK1214GAP, 11513MB w/0kB Cache, CHS=1467/255/63, UDMA

Pcmcia/pccard:

Linux PCMCIA Card Services 3.1.23
  kernel build: 2.2.18 #2 Mon Jan 15 23:56:28 CET 2001
  options:  [pci] [cardbus] [apm]
PCI routing table version 1.0 at 0xf0190
  00:0b.0 -> irq 11
  00:0b.1 -> irq 11
Intel PCIC probe: 
  Toshiba ToPIC100 rev 20 PCI-to-CardBus at slot 00:0b, mem 0x68000000
    host opts [0]: [slot 0xf0] [ccr 0x16] [cdr 0x86] [rcr 0xc000000]
[pci irq 11] [lat 64/176] [bus 20/20]
    host opts [1]: [slot 0xf0] [ccr 0x26] [cdr 0x86] [rcr 0xc000000]
[pci irq 11] [lat 64/176] [bus 21/21]

Compact Flash:

hdc: Hitachi CV 7.2.2, ATA DISK drive
hdc: Hitachi CV 7.2.2, 30MB w/1kB Cache, CHS=492/4/32

             reply	other threads:[~2001-03-08 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-08 14:41 Magnus Damm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-09  0:38 2.2.18 corruption: IDE + PCMCIA ? Thomas Hood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AA79A1D.49E5ADC@opensource.se \
    --to=damm@opensource.se \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox