NetBSD Problem Report #42128

From reed@reedmedia.net  Sat Sep 26 10:32:01 2009
Return-Path: <reed@reedmedia.net>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 336C763B850
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 26 Sep 2009 10:32:01 +0000 (UTC)
Message-Id: <28495-1253961119@reedmedia.net>
Date: Sat, 26 Sep 2009 05:32:00 -0500
From: reed@reedmedia.net
Reply-To: reed@reedmedia.net
To: gnats-bugs@gnats.NetBSD.org
Subject: page fault trap installing NetBSD/amd64 5.0.1 under Xen
X-Send-Pr-Version: 3.95

>Number:         42128
>Category:       port-xen
>Synopsis:       page fault trap installing NetBSD/amd64 5.0.1 under Xen
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-amd64-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Sep 26 10:35:00 +0000 2009
>Closed-Date:    Thu Aug 24 09:33:39 +0000 2017
>Last-Modified:  Thu Aug 24 09:33:39 +0000 2017
>Originator:     reed@reedmedia.net
>Release:        NetBSD 5.0.1
>Organization:
>Environment:
Architecture: x86_64
Machine: amd64
>Description:
Installing as a Xen guest using the amd64cd-5.0.1.iso.  When it
got to the untar step in sysinst (extracting kern-GENERIC.tgz), it
aborted with:

kernel: page fault trap, code=0
Stopped in pid 0.4 (system) at  0xffffffff804f163e:    repe insl      
%dx,%es:(%rdi)
db{0}> bt
?() at 0xffffffff804f163e
?() at 0xffffffff804fefc7
?() at 0xffffffff802c3207
?() at 0xffffffff804e0e4d
?() at 0xffffffff80105a4f
Bad frame pointer: 0xffff800001215ac40

(No symbols on that install kernel.)

This was also reported by someone else in January 2008
http://mail-index.netbsd.org/port-amd64/2008/01/14/msg000056.html

My Xen dom0 is a Debian Linux server with Linux 2.6.26-1-xen-amd64
kernel running xenwatch, xenbus, xenrestored, xend, xenconsoled,
and many qemu-dm processes. I think that is xen-3.2-1. (It is
hosting OpenSolaris, OpenBSD, Windows, Debian, and others.)

If you need dmesg output from when I am running 5.99.18, please
let me know.
>How-To-Repeat:
I was able to repeat by using sysinst.
>Fix:
Something appears to be fixed.
I am able to install and use NetBSD/amd64 5.99.18.
I don't know what the fix for 5.0.1 is.

>Release-Note:

>Audit-Trail:
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: port-amd64-maintainer@NetBSD.org, gnats-admin@NetBSD.org,
        netbsd-bugs@NetBSD.org
Subject: Re: port-amd64/42128: page fault trap installing NetBSD/amd64 5.0.1 under Xen
Date: Sat, 26 Sep 2009 16:37:19 +0200

 On Sat, Sep 26, 2009 at 10:35:00AM +0000, reed@reedmedia.net wrote:
 > >Number:         42128
 > >Category:       port-amd64
 > >Synopsis:       page fault trap installing NetBSD/amd64 5.0.1 under Xen
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    port-amd64-maintainer
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Sat Sep 26 10:35:00 +0000 2009
 > >Originator:     reed@reedmedia.net
 > >Release:        NetBSD 5.0.1
 > >Organization:
 > >Environment:
 > Architecture: x86_64
 > Machine: amd64
 > >Description:
 > Installing as a Xen guest using the amd64cd-5.0.1.iso.  When it
 > got to the untar step in sysinst (extracting kern-GENERIC.tgz), it
 > aborted with:

 Is it a PV guest or a HVM guest ?
 > 
 > kernel: page fault trap, code=0
 > Stopped in pid 0.4 (system) at  0xffffffff804f163e:    repe insl      
 > %dx,%es:(%rdi)
 > db{0}> bt
 > ?() at 0xffffffff804f163e
 > ?() at 0xffffffff804fefc7
 > ?() at 0xffffffff802c3207
 > ?() at 0xffffffff804e0e4d
 > ?() at 0xffffffff80105a4f
 > Bad frame pointer: 0xffff800001215ac40

 Also what is the message just before the page fault ? Did it start
 userland at this point ?

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

From: "Jeremy C. Reed" <reed@reedmedia.net>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-amd64/42128: page fault trap installing NetBSD/amd64 5.0.1
 under Xen
Date: Sat, 26 Sep 2009 13:27:43 -0500 (CDT)

 On Sat, 26 Sep 2009, Manuel Bouyer wrote:

 > > Installing as a Xen guest using the amd64cd-5.0.1.iso.  When it
 > > got to the untar step in sysinst (extracting kern-GENERIC.tgz), it
 > > aborted with:
 > 
 > Is it a PV guest or a HVM guest ?

 Sorry, I do not know. I do not know what this means. How can I check?

 > > kernel: page fault trap, code=0
 > > Stopped in pid 0.4 (system) at  0xffffffff804f163e:    repe insl      
 > > %dx,%es:(%rdi)
 > > db{0}> bt
 > > ?() at 0xffffffff804f163e
 > > ?() at 0xffffffff804fefc7
 > > ?() at 0xffffffff802c3207
 > > ?() at 0xffffffff804e0e4d
 > > ?() at 0xffffffff80105a4f
 > > Bad frame pointer: 0xffff800001215ac40
 > 
 > Also what is the message just before the page fault ? Did it start
 > userland at this point ?

 Sorry, I do not know of any previous message.

 Yes, userland was running. sysinst was running. I had been using it. It 
 failed after a few minutes when it got to the tar ball extraction step. 
 (Same as the Jan 2008 report.)

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: port-amd64-maintainer@NetBSD.org, gnats-admin@NetBSD.org,
        netbsd-bugs@NetBSD.org, reed@reedmedia.net
Subject: Re: port-amd64/42128: page fault trap installing NetBSD/amd64 5.0.1 under Xen
Date: Sun, 27 Sep 2009 11:31:41 +0200

 On Sat, Sep 26, 2009 at 06:30:04PM +0000, Jeremy C. Reed wrote:
 > The following reply was made to PR port-amd64/42128; it has been noted by GNATS.
 > 
 > From: "Jeremy C. Reed" <reed@reedmedia.net>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: port-amd64/42128: page fault trap installing NetBSD/amd64 5.0.1
 >  under Xen
 > Date: Sat, 26 Sep 2009 13:27:43 -0500 (CDT)
 > 
 >  On Sat, 26 Sep 2009, Manuel Bouyer wrote:
 >  
 >  > > Installing as a Xen guest using the amd64cd-5.0.1.iso.  When it
 >  > > got to the untar step in sysinst (extracting kern-GENERIC.tgz), it
 >  > > aborted with:
 >  > 
 >  > Is it a PV guest or a HVM guest ?
 >  
 >  Sorry, I do not know. I do not know what this means. How can I check?

 Did you use one of the netbsd-XEN* kernel ? Of a plain amd64 kernel ?

 >  
 >  > > kernel: page fault trap, code=0
 >  > > Stopped in pid 0.4 (system) at  0xffffffff804f163e:    repe insl      
 >  > > %dx,%es:(%rdi)
 >  > > db{0}> bt
 >  > > ?() at 0xffffffff804f163e
 >  > > ?() at 0xffffffff804fefc7
 >  > > ?() at 0xffffffff802c3207
 >  > > ?() at 0xffffffff804e0e4d
 >  > > ?() at 0xffffffff80105a4f
 >  > > Bad frame pointer: 0xffff800001215ac40
 >  > 
 >  > Also what is the message just before the page fault ? Did it start
 >  > userland at this point ?
 >  
 >  Sorry, I do not know of any previous message.
 >  
 >  Yes, userland was running. sysinst was running. I had been using it. It 
 >  failed after a few minutes when it got to the tar ball extraction step. 
 >  (Same as the Jan 2008 report.)

 OK.

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

From: "Jeremy C. Reed" <reed@reedmedia.net>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-amd64/42128: page fault trap installing NetBSD/amd64 5.0.1
 under Xen
Date: Mon, 28 Sep 2009 07:04:24 -0500 (CDT)

 On Sun, 27 Sep 2009, Manuel Bouyer wrote:

 > >  > > Installing as a Xen guest using the amd64cd-5.0.1.iso.  When it
 > >  > > got to the untar step in sysinst (extracting kern-GENERIC.tgz), it
 > >  > > aborted with:
 > >  > 
 > >  > Is it a PV guest or a HVM guest ?
 > >  
 > >  Sorry, I do not know. I do not know what this means. How can I check?
 > 
 > Did you use one of the netbsd-XEN* kernel ? Of a plain amd64 kernel ?

 I used the amd64cd-5.0.1.iso ISO image. I use the default kernel on it 
 which I assume was GENERIC and plain amd64. It defaulted to install
 kern-GENERIC.tgz.

Responsible-Changed-From-To: port-amd64-maintainer->port-xen-maintainer
Responsible-Changed-By: maxv@NetBSD.org
Responsible-Changed-When: Thu, 24 Aug 2017 08:34:57 +0000
Responsible-Changed-Why:
this is a xen issue


Responsible-Changed-From-To: port-xen-maintainer->port-amd64-maintainer
Responsible-Changed-By: bouyer@NetBSD.org
Responsible-Changed-When: Thu, 24 Aug 2017 09:33:39 +0000
Responsible-Changed-Why:
Actually not a NetBSD/Xen issue, because the submitter used a plain GENERIC
kernel (the amd64 boot iso, actually) in a HVM guest.


State-Changed-From-To: open->closed
State-Changed-By: bouyer@NetBSD.org
State-Changed-When: Thu, 24 Aug 2017 09:33:39 +0000
State-Changed-Why:
NetBSD 5.x is no longer maintained


>Unformatted:

Home	PR Database Search