Hi,
recent tcp additions seem to corrupt harddisk. X/KDE doesn't start up anymore
and 'mount' was broken after reboot. (Debian/unstable, ext3 fs) No Problem
with clean 2.5.41. Will try 2.5.42 now. You need any more information?
jan
Here goes dmesg/config output:
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0x9000-0x9007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x9008-0x900f, BIOS settings: hdc:DMA, hdd:DMA
hda: IC35L060AVVA07-0, ATA DISK drive
hda: DMA disabled
hda: bad special flag: 0x03
hda: tagged command queueing enabled, command queue depth 8
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: SONY CD-RW CRX175E2, ATAPI CD/DVD-ROM drive
hdd: Pioneer DVD-ROM ATAPIModel DVD-104S 012, ATAPI CD/DVD-ROM drive
hdc: DMA disabled
hdd: DMA disabled
ide1 at 0x170-0x177,0x376 on irq 15
hda: host protected area => 1
hda: 120103200 sectors (61493 MB) w/1863KiB Cache, CHS=7476/255/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 >
ide-cd: passing drive hdc to ide-scsi emulation.
hdd: ATAPI DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: SONY Model: CD-RW CRX175E2 Rev: S002
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
[...]
attempt to access beyond end of device
ide0(3,2): rw=0, want=1076371720, limit=19535040
attempt to access beyond end of device
ide0(3,2): rw=0, want=1076261672, limit=19535040
attempt to access beyond end of device
ide0(3,2): rw=0, want=1076240168, limit=19535040
attempt to access beyond end of device
ide0(3,2): rw=0, want=1076243240, limit=19535040
attempt to access beyond end of device
ide0(3,2): rw=0, want=1076335080, limit=19535040
attempt to access beyond end of device
ide0(3,2): rw=0, want=1076262568, limit=19535040
attempt to access beyond end of device
ide0(3,2): rw=0, want=1076262568, limit=19535040
attempt to access beyond end of device
ide0(3,2): rw=0, want=1076262568, limit=19535040
.config:
#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_BLK_DEV_GENERIC is not set
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_IDE_TCQ=y
CONFIG_BLK_DEV_IDE_TCQ_DEFAULT=y
CONFIG_BLK_DEV_IDE_TCQ_DEPTH=8
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_IDEDMA_FORCED=y
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_PCI_WIP=y
CONFIG_IDEDMA_NEW_DRIVE_LISTINGS=y
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_AMD74XX_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NFORCE is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
From: Jan Dittmer <[email protected]>
Date: Sat, 12 Oct 2002 10:50:01 +0200
recent tcp additions
I hope you really mean "tcq" additions.
Nothing that has happened in the TCP networking lately
can corrupt your harddisk. :-)
On Sat, Oct 12 2002, Jan Dittmer wrote:
> Hi,
>
> recent tcp additions seem to corrupt harddisk. X/KDE doesn't start up anymore
> and 'mount' was broken after reboot. (Debian/unstable, ext3 fs) No Problem
> with clean 2.5.41. Will try 2.5.42 now. You need any more information?
2.5.42 has no changes in this area, so it's probably not safe for you
either.
> Here goes dmesg/config output:
>
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> VP_IDE: IDE controller at PCI slot 00:07.1
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
> ide0: BM-DMA at 0x9000-0x9007, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0x9008-0x900f, BIOS settings: hdc:DMA, hdd:DMA
> hda: IC35L060AVVA07-0, ATA DISK drive
Vancouver, I'm using the very same drive here on the machine where I'm
writing this mail. This could be some odd via interaction.
> [...]
>
> attempt to access beyond end of device
> ide0(3,2): rw=0, want=1076371720, limit=19535040
Any messages _before_ these??
--
Jens Axboe
> > attempt to access beyond end of device
> > ide0(3,2): rw=0, want=1076371720, limit=19535040
>
At least not ide related. Just ext3 moaning.
I'm just reinstalling debian, e2fsck just killed most of my filesystem :-(
(including old dmesg/config).
I'll give 2.4.42 a try on a fresh install with ext_2_. But I think there
were no changes with respect to ext3 lately?!
jan
> Any messages _before_ these??
>
> --
> Jens Axboe
>
--
portrix.net GmbH
[email protected]
> 2.5.42 has no changes in this area, so it's probably not safe for you
> either.
Tried it anyway. Nothing better. Seems to happen also with tcq disabled. I've
for now downgraded to 2.4 ... Don't want to reinstall again.
I don't have a serial console available. So I'm sorry but I can't give you any
further clues. X locks up completly after some minutes, on reboot e2fsck gives a
ton of errors (also with ext2 btw). Or can you point me to something I can try
safely?! Perhaps I'll give 2.5.40 a try again tomorrow. That was the latest
revision working iirc. But for now I'm tired and a bit scared ;-)
jan
On Sat, 2002-10-12 at 07:37, Jan Dittmer wrote:
> > > attempt to access beyond end of device
> > > ide0(3,2): rw=0, want=1076371720, limit=19535040
> >
> At least not ide related. Just ext3 moaning.
> I'm just reinstalling debian, e2fsck just killed most of my filesystem :-(
> (including old dmesg/config).
> I'll give 2.4.42 a try on a fresh install with ext_2_. But I think there
> were no changes with respect to ext3 lately?!
>
I had similar problems with 2.4.20-pre5-ac6 where my /home partition was
totally killed. Though I used 2.4.19 to dd it off and ran fsck on
copies till I got it back and remounted it as a ext2 partition. It had
some really bad corruption in the journal, but as far as I could tell
there was no other corruption. I originally thought it was bad hard
disk, but I reinstalled to the same drive and no more errors with
2.4.20-pre8-ac3. I also got all kinds off errors about trying to read
past the end of the device and partition magic said something about the
partition table being corrupt and not being able to determine the
partition type. Though cfdisk didnt say a thing about any of this. Just
a wierd situation that had me confused for several days.
-Scott Henson