ATA/DMA problem after reboot
From: Jeremie Le Hen (jeremie_at_le-hen.org)
Date: 09/28/05
- Previous message: Artemiev Igor: "current-i386: thread 0xc07686a0 unlocking unheld lock"
- Next in thread: Anish Mistry: "Re: ATA/DMA problem after reboot"
- Reply: Anish Mistry: "Re: ATA/DMA problem after reboot"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 28 Sep 2005 21:03:37 +0200 To: freebsd-current@FreeBSD.org
Hi list,
one of my boxes running FreeBSD 6.0-BETA5 experiences the problem
described below. I must add that this box never ran something else
than FreeBSD, and I've been seeing this since the beginning, back to
FreeBSD 5.x.
The box run quite well most of the time, i.e. no particular ATA
problem, when the box has just been powered up. However, after a
reboot, whether soft or hard, I get READ_DMA errors for all my ATA
drives.
I would be glad if one could give me some clues or hints on how to debug
this. I understand this may be a kind of weird hardware problem that
could not be worked around, but I'd like to be sure about this.
The verbose dmesg: is attached, the READ_DMA errors can be seen at the
very end of it. I also attached my kernel configuration file in case it
is relevant.
Thank you.
Regards,
-- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- text/plain attachment: dmesg
- text/plain attachment: OBIWAN
- Previous message: Artemiev Igor: "current-i386: thread 0xc07686a0 unlocking unheld lock"
- Next in thread: Anish Mistry: "Re: ATA/DMA problem after reboot"
- Reply: Anish Mistry: "Re: ATA/DMA problem after reboot"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|