From kyle@heathers.stdio.com  Wed Jul 16 10:28:44 2003
Return-Path: <kyle@heathers.stdio.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 39F8337B401
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 16 Jul 2003 10:28:44 -0700 (PDT)
Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5E38043F75
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 16 Jul 2003 10:28:42 -0700 (PDT)
	(envelope-from kyle@heathers.stdio.com)
Received: (from kyle@localhost)
	by heathers.stdio.com (8.11.6/8.11.6) id h6GHSft36627;
	Wed, 16 Jul 2003 13:28:41 -0400 (EDT)
	(envelope-from kyle)
Message-Id: <200307161728.h6GHSft36627@heathers.stdio.com>
Date: Wed, 16 Jul 2003 13:28:41 -0400 (EDT)
From: Kyle McPeek <kyle@stdio.com>
Reply-To: Kyle McPeek <kyle@stdio.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: panic on install on Dell 600sc
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         54549
>Category:       i386
>Synopsis:       [panic] panic on install on Dell 600sc
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-i386
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 16 10:30:16 PDT 2003
>Closed-Date:    Mon Sep 11 11:45:31 GMT 2006
>Last-Modified:  Mon Sep 11 11:45:31 GMT 2006
>Originator:     Kyle McPeek
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
Lexmark International, Inc.
>Environment:
System: FreeBSD 5.1-RELEASE and 5.1-CURRENT-20030709-JPSNAP

>Description:

	( Copied by me, errors in transcription are mine.)

	unknown PNP0501 Can't assign resources (port)
	unknown PNP0401 Can't assign resources (port)
	unknown PNP0700 Can't assign resources (port)
	unknown PNP0f13 Can't assign resources (irq)
	unknown PNP0303 Can't assign resources (port)
	unknown PNP0c01 Can't assign resources (port)

	timecounters tick every 10.000 msec

	fatal trap 12: page fault while in kernel mode

	fault virtual address           = 0x20
	fault code                      = supervisor read, page not present
	instruction pointer             = 0x8: 0xc018a87c
	stack pointer                   = 0x10: 0xdf4aace0
	frame pointer                   = 0x10: 0xdf4aacf0
	code segment                    = base 0x0, limit 0xfffff, type 0x1b
                                	= DPL 0, pres 1, def32 1, gran 1
	processor eflags                = interrupt enable, resume, IOPL = 0
	current process                 = 19 (irq 11: atapci0)
	trap number                     = 12

	panic: page fault

>How-To-Repeat:
	boot 5.1-RELEASE or 5.1-CURRENT on a dell 600sc.
>Fix:
	use current from around March 2003.  That works.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: kris 
State-Changed-When: Sat Oct 11 01:16:03 PDT 2003 
State-Changed-Why:  
Without a traceback it's difficult to tell, but this looks like it 
might be ATA related.  Can you retry with a newer -CURRENT, since 
it has a rewritten ATA driver? 

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

From: Anoop Ranganath <anoop@ranganath.com>
To: freebsd-gnats-submit@FreeBSD.org, kyle@stdio.com
Cc:  
Subject: Re: kern/54549: panic on install on Dell 600sc
Date: Wed, 15 Oct 2003 19:15:39 -0400

 This is still occurring on -CURRENT from 10/15.  Let me know what 
 information you need.
 

From: Kris Kennaway <kris@obsecurity.org>
To: bug-followup@FreeBSD.org, kyle@stdio.com
Cc:  
Subject: Re: kern/54549
Date: Fri, 31 Oct 2003 19:07:54 -0800

 See
 
   http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
 
 for a description of how to obtain the necessary debugging information.
 
 Kris

From: Dan Roberts <droberts@gwis.com>
To: freebsd-gnats-submit@FreeBSD.org, kyle@stdio.com
Cc:  
Subject: Re: kern/54549: panic on install on Dell 600sc
Date: Sun, 23 Nov 2003 22:05:59 -0500 (EST)

 You're assuming that the OS boots to the point where you can
 obtain a crashdump, but this is not the case.. the panic occurs
 during device probe, well in advance of any drives being mounted.
 Is there anything else that can be done?
 
 Dan

From: Dan Roberts <droberts@gwis.com>
To: freebsd-gnats-submit@FreeBSD.org, kyle@stdio.com,
	Kris Kennaway <kris@obsecurity.org>
Cc:  
Subject: Re: kern/54549: panic on install on Dell 600sc (fwd)
Date: Sun, 23 Nov 2003 22:31:27 -0500 (EST)

 Sorry for misspeaking.. didn't read far enough. I just now
 stumbled upon the remote GDB feature.  It'll take a while before
 I get that done, but in the meantime, here is the full output of
 the the device probe and subsequent error:
 
 Copyright (c) 1992-2003 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
 FreeBSD 5.1-RELEASE #0: Thu Jun  5 02:55:42 GMT 2003
     root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC
 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0b0c000.
 Preloaded mfs_root "/boot/mfsroot" at 0xc0b0c204.
 Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0b0c248.
 Timecounter "i8254"  frequency 1193182 Hz
 Timecounter "TSC"  frequency 2399335008 Hz
 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2399.34-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7
 
 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,>
 real memory  = 134152192 (127 MB)
 avail memory = 118632448 (113 MB)
 Pentium Pro MTRR support enabled
 md0: Preloaded image </boot/mfsroot> 4423680 bytes at 0xc06877a4
 npx0: <math processor> on motherboard
 npx0: INT 16 interface
 acpi0: <DELL   PE600SC > on motherboard
 acpi0: power button is handled as a fixed feature programming model.
 Timecounter "ACPI-safe"  frequency 3579545 Hz
 pcibios: BIOS version 2.10
 Using $PIR table, 7 entries at 0xc00fc320
 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
 acpi_cpu0: <CPU> on acpi0
 acpi_cpu1: <CPU> on acpi0
 pcib0: <ACPI Host-PCI bridge> on acpi0
 pci0: <ACPI PCI bus> on pcib0
 em0: <Intel(R) PRO/1000 Network Connection, Version - 1.5.31> port 0xecc0-0xecf0
 em0:  Speed:N/A  Duplex:N/A
 twe0: <3ware Storage Controller> port 0xecb0-0xecbf mem 0xfe000000-0xfe7fffff,00
 twe0: 2 ports, Firmware FE7X 1.05.00.050, BIOS BE7X 1.08.00.046
 sis0: <NatSemi DP83815 10/100BaseTX> port 0xe800-0xe8ff mem 0xfe922000-0xfe922f0
 sis0: Ethernet address: 00:a0:cc:79:73:c9
 miibus0: <MII bus> on sis0
 ukphy0: <Generic IEEE 802.3u media interface> on miibus0
 ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 pci0: <display, VGA> at device 8.0 (no driver attached)
 atapci0: <ServerWorks CSB6 UDMA66 controller> port 0x900-0x90f,0x36c-0x36f,0x160
 ata2: at 0x1e8 on atapci0
 ata3: simplex device, DMA on primary only
 ata3: at 0x168 on atapci0
 atapci1: <ServerWorks CSB6 UDMA100 controller> port 0x8b0-0x8bf,0x374-0x377,0x10
 ata0: at 0x1f0 irq 14 on atapci1
 ata1: at 0x170 irq 15 on atapci1
 ohci0: <OHCI (generic) USB controller> mem 0xfe920000-0xfe920fff irq 3 at devic0
 usb0: OHCI version 1.0, legacy support
 usb0: SMM does not respond, resetting
 usb0: <OHCI (generic) USB controller> on ohci0
 usb0: USB revision 1.0
 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 isab0: <PCI-ISA bridge> at device 15.3 on pci0
 isa0: <ISA bus> on isab0
 fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> port 0x3f7,0x3f0-0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: <1440-KB 3.5" drive> on fdc0 drive 0
 atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0kbd0 at atkbd0
 psm0: <PS/2 Mouse> irq 12 on atkbdc0
 psm0: model IntelliMouse, device ID 3 sio0 port 0x3f8-0x3ff irq 4 on acpi0
 sio0: type 16550A, console
 ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 1 on acpi0
 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/8 bytes threshold
 ppbus0: <Parallel port bus> on ppc0
 plip0: <PLIP network interface> on ppbus0
 lpt0: <Printer> on ppbus0
 lpt0: Interrupt-driven port
 ppi0: <Parallel I/O> on ppbus0
 orm0: <Option ROMs> at iomem 0xec000-0xeffff,0xc8000-0xc8fff,0xc0000-0xc7fff on0pmtimer0 on isa0
 sc0: <System console> at flags 0x100 on isa0
 sc0: VGA <16 virtual consoles, flags=0x100>
 sio1: configured irq 3 not in bitmap of probed irqs 0
 sio1: port may not be enabled
 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 Timecounters tick every 10.000 msec
 
 
 Fatal trap 12: page fault while in kernel mode
 fault virtual address   = 0x20
 fault code              = supervisor read, page not present
 instruction pointer     = 0x8:0xc01bf255
 stack pointer           = 0x10:0xc8805cc8
 frame pointer           = 0x10:0xc8805ce0
 code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, def32 1, gran 1
 processor eflags        = interrupt enabled, resume, IOPL = 0
 current process         = 25 (irq11: atapci0)
 trap number             = 12
 panic: page fault
 
 syncing disks, buffers remaining...
 done
 Uptime: 1s

From: Anoop Ranganath <newdeal@ranganath.com>
To: kyle@stdio.com, freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/54549: panic on install on Dell 600sc
Date: Sun, 7 Dec 2003 23:51:52 -0500

 A workaround is available.  This drive has a tertiary IDE controller 
 that the CD-ROM sits on.  Moving the CD-ROM to the seconday controller 
 alleviates the panic.  At this point you can install the OS and boot 
 normally.  I haven't attempted to move the cd-rom back to the tertiary 
 controller after the installation.  I'll give that a shot next week.
 

From: Kyle McPeek <kyle@openworldinc.com>
To: freebsd-gnats-submit@FreeBSD.org, <kyle@stdio.com>
Cc:  
Subject: Re: kern/54549: panic on install on Dell 600sc
Date: Thu, 5 Feb 2004 15:00:41 -0500 (EST)

 using a current iso image from current.freebsd.org the following is what
 happens now.
 
 ata2-master: FAILURE - ATAPI_IDENTIFY no interrupt
 
 scrolling on the screen over and over again.
 
 kyle.
 
State-Changed-From-To: feedback->suspended 
State-Changed-By: linimon 
State-Changed-When: Sun Oct 23 18:31:58 GMT 2005 
State-Changed-Why:  
Feedback was received quite some time ago.  Mark as 'suspended' because 
apparently no one has looked at this for quite some time. 

To submitter: does this problem still recur on 5.4 and/or the upcoming 6.0? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=54549 
State-Changed-From-To: suspended->closed 
State-Changed-By: remko 
State-Changed-When: Mon Sep 11 11:45:28 UTC 2006 
State-Changed-Why:  
Mark requested feedback in 2005, we are now in 2006, timeout 

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