Re: port-xen/39916: kernel panic with xen 3.1 on 5.0-Beta i386 (HP DL 380 G3) (200811090002Z)

[uw%o3si.de@localhost]

The following reply was made to PR port-xen/39916; it has been noted by GNATS.

From: uw%o3si.de@localhost
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: port-xen/39916: kernel panic with xen 3.1 on 5.0-Beta i386 (HP
 DL 380 G3) (200811090002Z)
Date: Thu, 13 Nov 2008 22:55:40 +0100

 >  > >Number:         39916
 >  > >Category:       port-xen
 >  > >Synopsis:       xen kernel fault on i389 with 5.0 Beta
 >  > >Confidential:   no
 >  > >Severity:       critical
 >  > >Priority:       high
 >  > >Responsible:    port-xen-maintainer
 >  > >State:          open
 >  > >Class:          sw-bug
 >  > >Submitter-Id:   net
 >  > >Arrival-Date:   Thu Nov 13 21:20:00 +0000 2008
 >  > >Originator:     Charlie Root
 >  > >Release:        NetBSD 5.0_BETA
 >  > >Environment:
 >  > System: NetBSD root03.o3si.de 5.0_BETA NetBSD 5.0_BETA (XEN3_DOM0)
 >  > #1: Thu Nov 13 15:17:38 CET 2008
 >  > root%root03.o3si.de@localhost:/usr/src/sys/arch/i386/compile/XEN3_DOM0 
 > i386
 >  > Architecture: i386 Machine: i386
 >  > >Description:
 >  > The system crashes after running ca. for two days with the
 >  > following console output:
 >  > 
 >  > panic: kernel diagnostic assertion "iplbit !=3D 0" failed. file
 >  > "../../../.= ./arch/
 >  > xen/xen/evtchn.c", line 294
 >  
 >  This should already be partially fixed in current and netbsd-5
 > (partially because it may still panic later on another KASSERT).
 >  evtchn.c 1.41 should fix the panic (although the real issue, which is
 >  that the IPL isn't lowered when it should, is still there it seems).
 >  
 >  evtchn.c 1.41 should print a debug printf with the address of the
 > handler which didn't lower the IPL; I'm interested to know what this
 > printf shows in dmesg after several days.
 >  
 >  -- 
 >  Manuel Bouyer <bouyer%antioche.eu.org@localhost>
 >       NetBSD: 26 ans d'experience feront toujours la difference
 >  --
 >  
 
 Hello Manuel,
 
 thank You! I'll update as soon as possible to 1.41 and then observe the
 system to send You the requested information.
 
 Regards Uwe