NetBSD Problem Report #48464

From www@NetBSD.org  Fri Dec 20 13:36:32 2013
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "Postmaster NetBSD.org" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 74451A63E0
	for <gnats-bugs@gnats.NetBSD.org>; Fri, 20 Dec 2013 13:36:32 +0000 (UTC)
Message-Id: <20131220133630.EC2EEA645E@mollari.NetBSD.org>
Date: Fri, 20 Dec 2013 13:36:30 +0000 (UTC)
From: pooka@iki.fi
Reply-To: pooka@iki.fi
To: gnats-bugs@NetBSD.org
Subject: ping localhost causes a kernel panic
X-Send-Pr-Version: www-1.0

>Number:         48464
>Category:       kern
>Synopsis:       ping localhost causes a kernel panic
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 20 13:40:00 +0000 2013
>Last-Modified:  Fri Dec 20 16:50:00 +0000 2013
>Originator:     pooka@iki.fi
>Release:        HEAD 201312171040Z/amd64
>Organization:
>Environment:
>Description:

>How-To-Repeat:
python anita interact http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201312171040Z/amd64/
[...]
# ping localhost
PING localhost (127.0.0.1): 64 data bytes
fatal page fault in supervisor mode
trap type 6 code 0 rip ffffffff80269787 cs 8 rflags 206 cr2 fffffe8040000000 ilevel 4 rsp fffffe80014a4bb8
curlwp 0xfffffe8007f2b420 pid 0.3 lowest kstack 0xfffffe80014a1000
kernel: page fault trap, code=0
Stopped in pid 0.3 (system) at  netbsd:cpu_in_cksum+0xa7:       movl    4(%rbx),
%eax
db{0}> tr
cpu_in_cksum() at netbsd:cpu_in_cksum+0xa7
fatal page fault in supervisor mode
trap type 6 code 0 rip ffffffff802898f3 cs 8 rflags 246 cr2 a9e8 ilevel 8 rsp fffffe80014a3f40
curlwp 0xfffffe8007f2b420 pid 0.3 lowest kstack 0xfffffe80014a1000
kernel: page fault trap, code=0
Faulted in DDB; continuing...
db{0}> 

>Fix:

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/48464
Date: Fri, 20 Dec 2013 16:10:20 +0100

 I could not reproduce it with qemu 1.7 and the latest HEAD autobuild available.

 Martin

From: Antti Kantee <pooka@iki.fi>
To: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org, 
 gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Cc: 
Subject: Re: kern/48464
Date: Fri, 20 Dec 2013 15:35:55 +0000

 On 12/20/2013 03:15 PM, Martin Husemann wrote:
 > The following reply was made to PR kern/48464; it has been noted by GNATS.
 >
 > From: Martin Husemann <martin@duskware.de>
 > To: gnats-bugs@NetBSD.org
 > Cc:
 > Subject: Re: kern/48464
 > Date: Fri, 20 Dec 2013 16:10:20 +0100
 >
 >   I could not reproduce it with qemu 1.7 and the latest HEAD autobuild available.

 Still 100% reproducible with 
 http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201312192200Z/amd64/

 qemu 1.5

From: Martin Husemann <martin@duskware.de>
To: Antti Kantee <pooka@iki.fi>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
	gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/48464
Date: Fri, 20 Dec 2013 16:37:35 +0100

 On Fri, Dec 20, 2013 at 03:35:55PM +0000, Antti Kantee wrote:
 > Still 100% reproducible with 
 > http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201312192200Z/amd64/

 Can you show ifconfig -a before the ping?

 Martin

From: Martin Husemann <martin@duskware.de>
To: Antti Kantee <pooka@iki.fi>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org,
	gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/48464
Date: Fri, 20 Dec 2013 17:19:28 +0100

 On Fri, Dec 20, 2013 at 04:00:58PM +0000, Antti Kantee wrote:
 > Not sure why you expect that to be different for lo0 -- it is a 
 > completely fresh first-boot installation with anita defaults -- but:

 I don't - but I'm running out of ideas, as the same image you originally
 refered works fine for me with qemu 1.7, and -current also works for me
 on real hardware. So, what is the difference that makes it fail with
 qemu0 and/or anita involved?

 Martin

From: Antti Kantee <pooka@iki.fi>
To: Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org, 
 gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/48464
Date: Fri, 20 Dec 2013 16:00:58 +0000

 On 12/20/2013 03:37 PM, Martin Husemann wrote:
 > On Fri, Dec 20, 2013 at 03:35:55PM +0000, Antti Kantee wrote:
 >> Still 100% reproducible with
 >> http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201312192200Z/amd64/
 >
 > Can you show ifconfig -a before the ping?

 Not sure why you expect that to be different for lo0 -- it is a 
 completely fresh first-boot installation with anita defaults -- but:

 # ifconfig -a
 wm0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
 	capabilities=2bf80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx>
 	capabilities=2bf80<TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Tx>
 	capabilities=2bf80<UDP6CSUM_Tx>
 	enabled=0
 	ec_capabilities=7<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU>
 	ec_enabled=0
 	address: 52:54:00:12:34:56
 	media: Ethernet autoselect (none)
 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
 	inet 127.0.0.1 netmask 0xff000000
 	inet6 ::1 prefixlen 128
 	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
 # ping localhost
 PING localhost (127.0.0.1): 64 data bytes
 fatal page fault in supervisor mode
 [...]

From: Antti Kantee <pooka@iki.fi>
To: Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org, kern-bug-people@NetBSD.org, 
 gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/48464
Date: Fri, 20 Dec 2013 16:29:25 +0000

 On 12/20/2013 04:19 PM, Martin Husemann wrote:
 > On Fri, Dec 20, 2013 at 04:00:58PM +0000, Antti Kantee wrote:
 >> Not sure why you expect that to be different for lo0 -- it is a
 >> completely fresh first-boot installation with anita defaults -- but:
 >
 > I don't - but I'm running out of ideas, as the same image you originally
 > refered works fine for me with qemu 1.7, and -current also works for me
 > on real hardware. So, what is the difference that makes it fail with
 > qemu0 and/or anita involved?

 Dunno.  Considering it pagefaults in cpu_foo(), maybe it's a qemu 1.5 bug.

Home	PR Database Search