I have 2.4.22 running fine on this box, before and after
trying 2.6.0-test9. What happens is that I can use the
box for a few minutes, then it locks up hard for no apparent
reason. The hard drive light comes on and stays on,
sysrq is unresponsive, and no response via ethernet.
This has happened everytime I've used -test9 (about
4-6 times). The kernel is compiled for K7 (Athlon).
I have support for IDE disk, VIA vt82c686b, HPT370A,
and PDC20269 compiled in. There is nothing in any
log file that hints of trouble. Here's part of syslog, FWIW:
kernel: PCI: Probing PCI hardware
kernel: PCI: Probing PCI hardware (bus 00)
kernel: Disabling VIA memory write queue (PCI ID 0305, rev 03): [55] 89 & 1f -> 09
kernel: pty: 256 Unix98 ptys configured
kernel: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
kernel: hda: Maxtor 94610U6, ATA DISK drive
kernel: Using anticipatory io scheduler
kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
kernel: hdc: HL-DT-ST RW/DVD GCC-4480B, ATAPI CD/DVD-ROM drive
kernel: ide1 at 0x170-0x177,0x376 on irq 15
kernel: hde: Maxtor 6Y160P0, ATA DISK drive
kernel: ide2 at 0xbc00-0xbc07,0xc002 on irq 11
kernel: HPT37X: using 33MHz PCI clock
kernel: hdi: MAXTOR 4K080H4, ATA DISK drive
kernel: ide4 at 0xdc00-0xdc07,0xe002 on irq 11
kernel: hda: max request size: 128KiB
kernel: hde: max request size: 1024KiB
kernel: hdi: max request size: 128KiB
kernel: EXT2-fs warning (device hda5): ext2_fill_super: mounting ext3 filesystem as ext2
kernel:
kernel: VFS: Mounted root (ext2 filesystem) readonly.
kernel: sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
kernel: blk: queue dfe10400, I/O limit 4095Mb (mask 0xffffffff)
kernel: blk: queue dfe02400, I/O limit 4095Mb (mask 0xffffffff)
kernel: blk: queue dfdf7800, I/O limit 4095Mb (mask 0xffffffff)
Is there anything else I can provide that would be useful?
Is there anything I can turn on to get more info when this happens?
Andy Johnson
Hey guys,
i keep getting things like this in my dmesg
============================================
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
ide0: reset: success
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
ide0: reset: success
=============================================
>From hdparm
============================================
/dev/hda:
Model=IC35L080AVVA07-0, FwRev=VA4OA52A, SerialNo=VNC402A4CBRJLA
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=52
BuffType=DualPortCache, BuffSize=1863kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=160836480
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4 5
=================================================
Ive searched high and low to try find out what this means, all ive found
it people keep saying its all different kinds of things..
I was wondering if this means my hdd is drying or is ti a setting?
Thanks guys,
Steve
On Tue, Nov 04, 2003 at 08:29:38PM -0600, Andrew S. Johnson wrote:
> I have 2.4.22 running fine on this box, before and after
> trying 2.6.0-test9. What happens is that I can use the
> box for a few minutes, then it locks up hard for no apparent
> reason. The hard drive light comes on and stays on,
> sysrq is unresponsive, and no response via ethernet.
> This has happened everytime I've used -test9 (about
> 4-6 times). The kernel is compiled for K7 (Athlon).
I get something similar, but it takes a few days.
This is with 2.6.0-test6-mm4 #2 SMP Mon Oct 6 02:32:09 PDT 2003
I've been meaning to update for a while now... :-/