NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/42319: uvm_fault/fatal page fault on 5.0_STABLE



The following reply was made to PR kern/42319; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, 
netbsd-bugs%NetBSD.org@localhost
Subject: Re: kern/42319: uvm_fault/fatal page fault on 5.0_STABLE
Date: Sun, 15 Nov 2009 22:56:15 +0100

 On Sun, Nov 15, 2009 at 08:40:01AM +0000, dalibor.gudzic%gmail.com@localhost 
wrote:
 > >Number:         42319
 > >Category:       kern
 > >Synopsis:       uvm_fault/fatal page fault on 5.0_STABLE
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       high
 > >Responsible:    kern-bug-people
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Sun Nov 15 08:40:00 +0000 2009
 > >Originator:     Dalibor Gudzic
 > >Release:        5.0_STABLE
 > >Organization:
 > None
 > >Environment:
 > NetBSD 5.0_STABLE (GENERIC) #0: Fri Nov 13 20:55:43 CET 2009
 >       root%nbsd.dot.org.dot@localhost:/usr/obj/sys/arch/i386/compile/GENERIC
 > 
 > >Description:
 > On FS AMilo Pro V3515 I'm getting fatal page fault after cvs update on 
 > 13/11/09. Kernel build went fine, but when booting the new kernel it spits 
 > error and drops to ddb:
 > 
 > db{0}>trace
 > 
 > uvm_fault (0xc0b69240, 0, 1) -> 0xe
 > fatal page fault in supervisor mode
 > trap type 6 code 0 eip c057a491 cs 8 eflags 10246 cr2 0 ilevel 8
 > kernel: supervisor trap page fault code=0
 > Faulted in DDB; continuing
 > 
 > dmesg in ddm showing (sorry, a few lines shown only as I don't have other 
 > means to get the full dmesg):
 > 
 > ...
 > ppb4 at pci0 dev 19 function 1: vendor 0x1106 product 0x337a (rev. 0x00)
 > pci5 at ppb4 bus5
 > pci5: i/o space, memory space enabled
 > ath0 at pci5 dev 1 function 0
 > ath0: interrupting at ioapic0 pin 18
 > uvm_fault (0xc0b69240, 0, 1) -> 0xe
 
 Looks like the problem is in ath(4). Could you try to boot -c
 at the boot prompt, and then
 disable ath
 quit
 
 (or alternatively rebuild a kernel without the ath driver)
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --
 


Home | Main Index | Thread Index | Old Index