Bug 20069

Summary:	hard crash, errors with freebsd 4.0 (walnut creek cdrom)
Product:	Base System	Reporter:	zurk <zurk>
Component:	i386	Assignee:	Søren Schmidt <sos>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description zurk 2000-07-20 19:50:00 UTC

Heres a dump for the soft crash i had (it recovered) :
Jul 20 22:02:12 fbsd4 /kernel: ad0: HARD READ ERROR blk# 97439ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA
Jul 20 22:02:12 fbsd4 /kernel: ad0: HARD READ ERROR blk# 97439ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA
Jul 20 22:02:14 fbsd4 /kernel: ad0: DMA problem fallback to PIO mode
Jul 20 22:02:14 fbsd4 /kernel: ad0: DMA problem fallback to PIO mode
Jul 20 22:02:15 fbsd4 last message repeated 4 times
Jul 20 22:02:15 fbsd4 /kernel: ad0: HARD READ ERROR blk# 97519 status=59 error=40
Jul 20 22:02:15 fbsd4 last message repeated 4 times
Jul 20 22:02:15 fbsd4 /kernel: ad0: HARD READ ERROR blk# 97519 status=59 error=40
Jul 20 22:02:15 fbsd4 /kernel: ad0: DMA problem fallback to PIO mode
Jul 20 22:02:15 fbsd4 /kernel: ad0: DMA problem fallback to PIO mode
Jul 20 22:02:15 fbsd4 /kernel: ad0: HARD READ ERROR blk# 98975 status=59 error=40
Jul 20 22:02:15 fbsd4 /kernel: ad0: HARD READ ERROR blk# 98975 status=59 error=40
Jul 20 22:02:16 fbsd4 /kernel: ad0: HARD READ ERROR blk# 98327 status=59 error=40
Jul 20 22:02:16 fbsd4 /kernel: ad0: HARD READ ERROR blk# 98327 status=59 error=40
<internal>:0: Jul 20 22:02:18 fbsd4 /kernel: ad0: HARD READ ERROR blk# 98327 status=59 error=40
Jul 20 22:02:18 fbsd4 /kernel: spec_getpages:(#ad/0x20000) I/O read failure: (error=5) bp 0xc6017ec0 vp 0xcb927f60
Jul 20 22:02:18 fbsd4 /kernel: ad0: HARD READ ERROR blk# 98327 status=59 error=40
Jul 20 22:02:18 fbsd4 /kernel: spec_getpages:(#ad/0x20000) I/O read failure: (error=5) bp 0xc6017ec0 vp 0xcb927f60
Internal compiler error.
<internal>:0: Please submit a full bug report.
<internal>:0: See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
Jul 20 22:02:19 fbsd4 /kernel: size: 49152, resid: 49152, a_count: 49152, valid: 0x0
Jul 20 22:02:19 fbsd4 /kernel: size: 49152, resid: 49152, a_count: 49152, valid: 0x0
*** Error code 1

Stop in /usr/src/gnu/usr.bin/groff/libgroff.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/groff.
Jul 20 22:02:20 fbsd4 /kernel: nread: 0, reqpage: 3, pindex: 296, pcount: 12
Jul 20 22:02:20 fbsd4 /kernel: nread: 0, reqpage: 3, pindex: 296, pcount: 12
*** Error code 1

Stop in /usr/src/gnu/usr.bin.
*** Error code 1
Jul 20 22:02:20 fbsd4 /kernel: vm_fault: pager read error, pid 37480 (cc1plus)

Stop in /usr/src/gnu.
Jul 20 22:02:20 fbsd4 /kernel: vm_fault: pager read error, pid 37480 (cc1plus)
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
fbsd4# Jul 20 22:02:20 fbsd4 /kernel: ad0: HARD READ ERROR blk# 99791 status=59 error=40
Jul 20 22:02:20 fbsd4 /kernel: ad0: HARD READ ERROR blk# 99791 status=59 error=40
Jul 20 22:02:20 fbsd4 /kernel: spec_getpages:(#ad/0x20000) I/O read failure: (error=5) bp 0xc6017ec0 vp 0xcb927f60
Jul 20 22:02:20 fbsd4 /kernel: spec_getpages:(#ad/0x20000) I/O read failure: (error=5) bp 0xc6017ec0 vp 0xcb927f60
Jul 20 22:02:20 fbsd4 /kernel: size: 28672, resid: 20480, a_count: 28672, valid: 0x0
Jul 20 22:02:20 fbsd4 /kernel: size: 28672, resid: 20480, a_count: 28672, valid: 0x0
Jul 20 22:02:20 fbsd4 /kernel: nread: 8192, reqpage: 6, pindex: 480, pcount: 7
Jul 20 22:02:20 fbsd4 /kernel: nread: 8192, reqpage: 6, pindex: 480, pcount: 7
Jul 20 22:02:20 fbsd4 /kernel: vm_fault: pager read error, pid 37480 (cc1plus)
Jul 20 22:02:20 fbsd4 /kernel: vm_fault: pager read error, pid 37480 (cc1plus)

also had a HARD crash 4 hours after install. complete lockup with keyboard
not reponsive. machine completely dead. had to hit main power button.
it said : disk timeout on ad0 or something similar.

system works perfectly with linux .. never had a problem. machine is an 
asus p2bds with dual 500mhz p-iiis, 256mb ram, voodoo3 graphics, quantum fireball 1.6A
IDE hdd. first time freebsd install...very frustrating. im probably going to switch
to redhat linux again. *sigh*

Fix: 

dunno. im a newbie.
How-To-Repeat: make world.

Comment 1 billf 2000-07-20 22:57:19 UTC

On Thu, Jul 20, 2000 at 11:48:31AM -0700, zurk@arbornet.org wrote:

> fbsd4# Jul 20 22:02:20 fbsd4 /kernel: ad0: HARD READ ERROR blk# 99791 status=59 error=40
> Jul 20 22:02:20 fbsd4 /kernel: ad0: HARD READ ERROR blk# 99791 status=59 error=40
> Jul 20 22:02:20 fbsd4 /kernel: spec_getpages:(#ad/0x20000) I/O read failure: (error=5) bp 0xc6017ec0 vp 0xcb927f60
> Jul 20 22:02:20 fbsd4 /kernel: spec_getpages:(#ad/0x20000) I/O read failure: (error=5) bp 0xc6017ec0 vp 0xcb927f60
> Jul 20 22:02:20 fbsd4 /kernel: size: 28672, resid: 20480, a_count: 28672, valid: 0x0
> Jul 20 22:02:20 fbsd4 /kernel: size: 28672, resid: 20480, a_count: 28672, valid: 0x0
> Jul 20 22:02:20 fbsd4 /kernel: nread: 8192, reqpage: 6, pindex: 480, pcount: 7
> Jul 20 22:02:20 fbsd4 /kernel: nread: 8192, reqpage: 6, pindex: 480, pcount: 7
> Jul 20 22:02:20 fbsd4 /kernel: vm_fault: pager read error, pid 37480 (cc1plus)
> Jul 20 22:02:20 fbsd4 /kernel: vm_fault: pager read error, pid 37480 (cc1plus)
> 
> also had a HARD crash 4 hours after install. complete lockup with keyboard
> not reponsive. machine completely dead. had to hit main power button.
> it said : disk timeout on ad0 or something similar.

Your hard disk is dead or dying.

> system works perfectly with linux .. never had a problem. machine is an 
> asus p2bds with dual 500mhz p-iiis, 256mb ram, voodoo3 graphics, quantum fireball 1.6A
> IDE hdd. first time freebsd install...very frustrating. im probably going to switch
> to redhat linux again. *sigh*

You lose points for playing (in the same paragraph) both the "this worked just fine in
Linux"-card and the "*whine* *whine* if you don't help me, I'll go back to Linux"-card.

-- 
Bill Fumerola -	Network Architect, BOFH / Chimes, Inc.
                billf@chimesnet.com / billf@FreeBSD.org

Comment 2 Sheldon Hearn freebsd_committer

2000-07-21 10:15:25 UTC

State Changed
From-To: open->feedback

This looks a lot like a hardware error.  If you're convinced 
that it is not a failing disk, please send the output 
of the dmesg(8) utility to <freebsd-gnats-submit@FreeBSD.org> 
using the subject line of this message. 

This will assist the maintainer of the ata(4) driver. 
However, my money's on a bad disk. :-(

Comment 3 Sheldon Hearn freebsd_committer

2000-07-21 10:17:19 UTC

Responsible Changed
From-To: freebsd-bugs->sos

Soren might be interested in the feedback from this one.

Comment 4 Søren Schmidt freebsd_committer

2000-11-14 08:25:25 UTC

State Changed
From-To: feedback->closed

Belived to be hardware problems, and no followups received