Alan Cox wrote:
Does anyone have any ideas on how I can track this issue down? From what I
can tell, it's either a motherboard problem or a kernel bug/issue, but there
may be something I'm overlooking that might be causing this.
Posting the actual text of system logs, and info about the hardware - eg
what controller. Most likely its a drive failing.
There's nothing logged in the logs after the journal commit error because the
kernel makes the drive read-only at that point. Most of the time I'm not able
to run anything either - I just get a generic "input/output" error message. I
haven't tried running dmesg when the problem happens; would anything useful
come out of that?
There's only one hard drive in the system, and I replaced it a week or so ago
with a brand new drive. Although anything is possible, I doubt that the new
drive is exhibiting the same problems as the old drive.
The motherboard chipset is a VIA VT8237. The kernel says it's using the
pata_via drivers:
Jan 28 09:27:46 draco kernel: scsi0 : pata_via
Jan 28 09:27:46 draco kernel: scsi1 : pata_via
Jan 28 09:27:46 draco kernel: ata1: PATA max UDMA/133 cmd 0x000101f0 ctl
0x000103f6 bmdma 0x0001d000 irq 14
Jan 28 09:27:46 draco kernel: ata2: PATA max UDMA/133 cmd 0x00010170 ctl
0x00010376 bmdma 0x0001d008 irq 15
Jan 28 09:27:46 draco kernel: ata1.00: ATA-7: WDC WD1600AAJB-00PVA0, 00.07H00,
max UDMA/100
Jan 28 09:27:46 draco kernel: ata1.00: 312581808 sectors, multi 16: LBA48
Jan 28 09:27:46 draco kernel: ata1.00: configured for UDMA/100
Jan 28 09:27:46 draco kernel: ata2.00: ATAPI: LITE-ON DVDRW LH-20A1H, LL05,
max UDMA/66
Jan 28 09:27:46 draco kernel: ata2.00: limited to UDMA/33 due to 40-wire cable
Jan 28 09:27:46 draco kernel: ata2.00: configured for UDMA/33
--
Mike Iglesias Email: iglesias@xxxxxxx
University of California, Irvine phone: 949-824-6926
Network & Academic Computing Services FAX: 949-824-2270
