From nobody@FreeBSD.org  Thu May 10 07:00:25 2001
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id D472D37B422
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 10 May 2001 07:00:19 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f4AE0Jp98788;
	Thu, 10 May 2001 07:00:19 -0700 (PDT)
	(envelope-from nobody)
Message-Id: <200105101400.f4AE0Jp98788@freefall.freebsd.org>
Date: Thu, 10 May 2001 07:00:19 -0700 (PDT)
From: mark@dvdnews.co.uk
To: freebsd-gnats-submit@FreeBSD.org
Subject: Panic on install - "page fault syncing discs"
X-Send-Pr-Version: www-1.0

>Number:         27247
>Category:       i386
>Synopsis:       Panic on install - "page fault syncing discs"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 10 07:10:03 PDT 2001
>Closed-Date:    Mon Sep 08 12:05:39 PDT 2003
>Last-Modified:  Mon Sep 08 12:05:39 PDT 2003
>Originator:     Mark Hughes
>Release:        4.1-release
>Organization:
>Environment:
Not able to install so not possible to give.
>Description:
6.5GB ATA33 IBM HDD, on Biostar M7MIA mobo including the VIA IDE controller identified by the boot process as a "VIA 82C686 ATA66 Controller", althoguh it may be the 686B chip not the 686. Full spec included below.

Hard drive partitioned as 4.5GB Win2K/FAT32 partition, rest empty awaiting a FreeBSD install. I've checked out the hard drive with the IBM disk testing utility and all tests passed fine (I've even tried doing a "low" level format on it using the IBM wipe utility,
to no avail), also windows 2000 installed without problem.

I have been booting from 4.1-release install CD, set up kernel as usual knocking out all the unused hardware and sorting out any conflicts. Picked express setup, created a FreeBSD partition, sliced it as per my requirements (100MB root, 260MB swap, 300MB /var, and the rest for /usr), picked the minimal distribution (althoguh picking any of the others has the same/similar effect), install begins. This is all much as I've done before with no problems before the new motherboard & hard drive re-format.

At a seemingly random point while either extracting/installing the distribution, or while the "Remaking all devices.. Please Wait!" message is on screen shortly thereafter, the computer pauses for a fair time (probably around two to five minutes, not always the same though) then displays the messages...

panic: page fault syncing discs... 374 374 374 374 374 374 (repeat 374 a total of 20
times)
giving up on 328 buffers
Uptime: (whatever)
Automatic reboot in 15 seconds....

I've a strong suspicion this is related to the hard drive controller, althoguh I've not been able to find any problems reported anywhere around the net with it, so that assumption could be wrong.

Also, on one occasion while trying to install, it did manage to complete the install, and it rebooted successfully once, but after a few minutes of use I had a "read command timeout" error, followed by a seemingly endless loop of the OS reseting the drive controller then it failing again, reseting again, failing again, and so on, only solved by
a hard reset. On restarting FreeBSD wouldn't even boot, crashing out with a "BTX halted" error and a load of hex (which I'm afraid I didn't think to note down, there was a lot of it) and no error codes or messages aside from this.

HW Spec:
Biostar M7MIA motherboard, using AMD761 north bridge and VIA 686B south bridge
128MB DDR PC2100 memory (under-clocked at 100/200MHz to match FSB of processor)
AMD Duron 750MHz CPU
IBM Deskstar 6.5GB ATA33 Hard Disk Drive (partitioned as 4.5GB FAT32 Win2K, rest FreeBSD)
SMC 1211TX-WL 10/100 WOL NIC
ATI Radeon VE 32MB DDR Graphics
12x ARTEC DVDROM
3.5" floppy drive, 1.44MB (wow)



>How-To-Repeat:
Put in the install CD and attempt to install.
>Fix:
No idea, I'm afraid.
>Release-Note:
>Audit-Trail:

From: "Mark Hughes" <mark@dvdnews.co.uk>
To: <freebsd-gnats-submit@FreeBSD.org>,
	"Mark Hughes" <mark@dvdnews.co.uk>
Cc:  
Subject: Re: i386/27247: Panic on install - "page fault syncing discs"
Date: Fri, 11 May 2001 01:29:42 +0100

 Follow up:
 
 Managed to get it to complete install again, and boot, twice. First time it booted up with
 a "read command timeout" error then a loop of reseting devices, write error, resetting
 devices, etc, after the UDMA startup sequence. After this the filesystem got ruined and it
 would not boot again. Second time though I managed to boot and login, it failed to start
 up the DMA mode on startup so didn't go all haywire. Placed
 
 /sbin/sysctl -w hw.atamodes="pio,dma"
 
 into /etc/rc.conf which has allowed me to boot every time successfully and the DMA related
 error messages have gone. However, this obviously comes at the cost of abysmal hard drive
 performance.
 
 Hope this helps to narrow down where the problem lies.
 
 Mark
 
 

From: "Mark Hughes" <mark@dvdnews.co.uk>
To: <freebsd-gnats-submit@FreeBSD.org>,
	"Mark Hughes" <mark@dvdnews.co.uk>
Cc:  
Subject: Re: i386/27247: Panic on install - "page fault syncing discs"
Date: Fri, 11 May 2001 02:20:24 +0100

 Follow up 2:
 
 Having run the system for about a half hour, it stopped working again, with 
 
 ad0: read command timeout
 ata0: resetting devices .. done
 ad0: WRITE command timeout
 ata0: resetting devices .. done
 ad0: read command timeout
 ata0: resetting devices .. done
 
 eventually ending in a 
 
 /: bad dir ino 12611 .. mangled entry
 
 then rebooting itself after a panic which i didn't catch before it rebooted i'm afraid.
 
 so, i'm back where I started. guess I was just lucky that it worked for a bit.
 
 Regards,
 Mark
 
State-Changed-From-To: open->feedback 
State-Changed-By: schweikh 
State-Changed-When: Sat Aug 10 07:59:51 PDT 2002 
State-Changed-Why:  
There has been some work on the ATA code. Does this problem 
still persist in a recent 4-STABLE? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=27247 

From: "Mark Hughes" <mh_lists@digitalspy.co.uk>
To: <freebsd-gnats-submit@FreeBSD.org>,
	"Mark Hughes" <mark@dvdnews.co.uk>
Cc:  
Subject: Re: i386/27247: Panic on install - "page fault syncing discs"
Date: Sat, 10 Aug 2002 16:21:28 +0100

 Began working from later version of FreeBSD (4.3-releaase onwards) and
 installed fine and has been working for many months without problems of this
 nature. Assume the bug is now fixed?
 
 Regards,
 Mark
 

From: "Leo S" <leonids@supportteam.net>
To: <freebsd-gnats-submit@FreeBSD.org>, <mark@dvdnews.co.uk>
Cc:  
Subject: Re: i386/27247: Panic on install - "page fault syncing discs"
Date: Thu, 30 Jan 2003 18:12:13 -0600

 Looks like it's doing it again. I went to upgrade from 4.5 to 4.7 today.
 And, I got the same EXACT error, at the same exact point. The only different
 was mine said panic: page fault syncing discs... 1 1 1 1 1 1 1 1 instead. My
 hardware is the following:
 
 Mobo:  Intel CA810e
 HD:      ad1: 14324MB <QUANTUM FIREBALLlct10 15> [29104/16/63] at ata0-slave
 UDMA66
             ad2: 14324MB <QUANTUM FIREBALLlct10 15> [29104/16/63] at
 ata1-master UDMA66
 
 Just as I side note, in 4.5, on boot I get the following error:
 
 Mounting root from ufs:/dev/ad1s1a
 ad1: READ command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 ad1: READ command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 ad1: READ command timeout tag=0 serv=0 - resetting
 ata0: resetting devices .. done
 ad1: READ command timeout tag=0 serv=0 - resetting
 ad1: trying fallback to PIO mode
 ata0: resetting devices .. done
 
 
 Leo S.
 
 
Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: kris 
Responsible-Changed-When: Sat Jul 12 05:27:40 PDT 2003 
Responsible-Changed-Why:  
Assign to the ATA maintainer for comment 

http://www.freebsd.org/cgi/query-pr.cgi?pr=27247 
State-Changed-From-To: feedback->open 
State-Changed-By: sos 
State-Changed-When: Mon Jul 14 04:28:45 PDT 2003 
State-Changed-Why:  
A complete dmesg would have been nice, as I cannot tell if you have a 
master device on channel 0 since the disk is *slave* which wont 
work well with fireballs.. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=27247 
State-Changed-From-To: open->closed 
State-Changed-By: sos 
State-Changed-When: Mon Sep 8 12:05:00 PDT 2003 
State-Changed-Why:  
feedback timeout 

http://www.freebsd.org/cgi/query-pr.cgi?pr=27247 
>Unformatted:
