hda: status error: status = 0x00 {}
hda: device not ready for command
ide0: reset: success
hda: read_intr: status = 0xd0 {busy}
end_request: I/O error, dev 03:06, sector 1261595
ide0: reset: success
hda: read_intr: status = 0xd0 {busy}
end_request: I/O error, dev 03:06, sector (another number here)
(sometimes also apears here something about e2fsck errors in
filesystem, but it scrolls too fast to read it)
ide0: reset: success
hda: read_intr: status = 0xd0 {busy}
end_request: I/O error, dev 03:06, sector (another number here)
...
..
.
And after this it usually gets hard locked, but sometimes seems like
nothing has happened until when you reboot and the filesystem is
checked.
I know that the disk it's not the problem because I am using it under
NoTechnology and under linux 2.0.3x with no problems, it's a Seagate.
The motherboard it's a Gigabyte 586dx with the onboard scsi 7880
disabled and all irq's to only one device (ie, no sharing)
quartz syslogd 1.3-3: restart.
quartz kernel: klogd 1.3-3, log source = /proc/kmsg started.
quartz kernel: Loaded 6088 symbols from /usr/src/linux/System.map.
quartz kernel: Symbols match kernel version 2.1.95.
quartz kernel: Error seeking in /dev/kmem
quartz kernel: Error adding kernel module table entry.
^^^^^ don't know why ther's such errors at the beginnig, this is
the beginnig of the session messages, but seems that nothing extrange
happens, and the booting process continues.
PIIX3: IDE controller on PCI bus 00 dev 39
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: ST34342A, ATA DISK drive
hdd: OSD OJC-F101, ATAPI CDROM drive
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: ST34342A, 4103MB w/128kB Cache, CHS=523/255/63, DMA
hdd: ATAPI 20X CDROM drive, 0kB Cache
Uniform CD-ROM driver Revision: 2.12
That's all, I know that the 2.1 series are developmente releases, but
I think it could be interesting to take some risks.
P.S. It's a copy of a message that I sent on April 16, since then
nothing has changed, now I'm "using" 2.1.96 (couldn't compile 97) and
I tink that the problem is the writes, when the activity is reading
it's OK, but when there are writings I get this messages.
the sysrq works and I think that my fsck's are less heavys because of
"emergency Sync"
I can give you as much info as you want, just ask for it, since I
don't know what do you need exactly.
\_/, _
| @___oo ( Jorge Nerin
/\ /\ / (___,,,}_--~
) /^\) ^\/ _) ~__ jnerin@svalero.es
) /^\/ _) (_
) _ / / _) ( jnerinl@nexo.es
/\ )/\/ || | )_)
< > |(,,) )__)
|| / \)___)\
| \____( )___) )___
\______(_______;;; __;;;
Greeetings from Zaragoza (Spain)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu