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

[Dalibor Gudzic <dalibor.gudzic%gmail.com@localhost>]

Hi,

Apology for top-posting, but a quick update;

I forgot to say that I'm allowed to boot using 5.0.1, and now 5.0.2.
The error message from dmesg (as reported in pr/40507) is still there.
Probably the code that prevents system from booting was introduced
later in -STABLE, or it was a bug that got corrected and is now not
present in 5.0.2.

All best

On Mon, Nov 16, 2009 at 9:40 AM, Dalibor Gudzic
<dalibor.gudzic%gmail.com@localhost> wrote:
> The following reply was made to PR kern/42319; it has been noted by GNATS.
>
> From: Dalibor Gudzic <dalibor.gudzic%gmail.com@localhost>
> To: gnats-bugs%netbsd.org@localhost
> Cc:
> Subject: Re: kern/42319: uvm_fault/fatal page fault on 5.0_STABLE
> Date: Mon, 16 Nov 2009 09:38:36 +0100
>
>  Hi Manuel,
>
>  On Mon, Nov 16, 2009 at 1:40 AM, Manuel Bouyer 
> <bouyer%antioche.eu.org@localhost> wro=
>  te:
>  > 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@NetBS=
>  D.org
>  > Subject: Re: kern/42319: uvm_fault/fatal page fault on 5.0_STABLE
>  > Date: Sun, 15 Nov 2009 22:56:15 +0100
>  >
>  > =A0On Sun, Nov 15, 2009 at 08:40:01AM +0000, 
> dalibor.gudzic%gmail.com@localhost wro=
>  te:
>  > =A0> >Number: =A0 =A0 =A0 =A0 42319
>  > =A0> >Category: =A0 =A0 =A0 kern
>  > =A0> >Synopsis: =A0 =A0 =A0 uvm_fault/fatal page fault on 5.0_STABLE
>  > =A0> >Confidential: =A0 no
>  > =A0> >Severity: =A0 =A0 =A0 critical
>  > =A0> >Priority: =A0 =A0 =A0 high
>  > =A0> >Responsible: =A0 =A0kern-bug-people
>  > =A0> >State: =A0 =A0 =A0 =A0 =A0open
>  > =A0> >Class: =A0 =A0 =A0 =A0 =A0sw-bug
>  > =A0> >Submitter-Id: =A0 net
>  > =A0> >Arrival-Date: =A0 Sun Nov 15 08:40:00 +0000 2009
>  > =A0> >Originator: =A0 =A0 Dalibor Gudzic
>  > =A0> >Release: =A0 =A0 =A0 =A05.0_STABLE
>  > =A0> >Organization:
>  > =A0> None
>  > =A0> >Environment:
>  > =A0> NetBSD 5.0_STABLE (GENERIC) #0: Fri Nov 13 20:55:43 CET 2009
>  > =A0> =A0 =A0 =A0 
> root%nbsd.dot.org.dot@localhost:/usr/obj/sys/arch/i386/compile/GEN=
>  ERIC
>  > =A0>
>  > =A0> >Description:
>  > =A0> 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 spi=
>  ts error and drops to ddb:
>  > =A0>
>  > =A0> db{0}>trace
>  > =A0>
>  > =A0> uvm_fault (0xc0b69240, 0, 1) -> 0xe
>  > =A0> fatal page fault in supervisor mode
>  > =A0> trap type 6 code 0 eip c057a491 cs 8 eflags 10246 cr2 0 ilevel 8
>  > =A0> kernel: supervisor trap page fault code=3D0
>  > =A0> Faulted in DDB; continuing
>  > =A0Looks like the problem is in ath(4). Could you try to boot -c
>  > =A0at the boot prompt, and then
>  > =A0disable ath
>  > =A0quit
>  >
>  > =A0(or alternatively rebuild a kernel without the ath driver)
>  >
>  > =A0--
>
>  Actually I have not had much time when I run into a problem, so I
>  tried disabling the ath driver yesterday evening. It worked, but
>  unfortunatally I had electricity problems and couldn't make a reply on
>  my original PR message.
>  The botom line is, yes, the ath driver is the culprit. I already said
>  the ath(4) driver did not work for my card, but never prevented kernel
>  from booting. Pls tell me if you need some more output.
>
>  Thanx
>
>