Re: bnx driver in 5.99.7 panics under xen 3.3.1

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Wed, Jan 28, 2009 at 04:25:39PM -0800, Mike Bowie wrote:
> Mike Bowie wrote:
> > Manuel Bouyer wrote:
> >> On Tue, Jan 27, 2009 at 01:30:28PM -0800, Mike Bowie wrote:
> >>  
> >>> [...]
> >>> bnx0 at pci8 dev 0 function 0: Broadcom NetXtreme II BCM5708 1000Base-T
> >>> ioapic1: int5
> >>> 0x1a9a8<vector=0xa8,delmode=0x1,logical,actlo,level,masked,dest=0x0>
> >>> 0xff000000<target=0xff>
> >>> bnx0: Ethernet address 00:22:19:53:d8:a3
> >>> xen_alloc_contig: XENMEM_decrease_reservation failed!
> >>> bnx0: Could not create Tx mbuf 0 DMA map!
> >>>     
> >>
> >> This is more serious than just a bnx issue. I can't see how a
> >> XENMEM_decrease_reservation can fail, unless it gets passed nonexistent
> >> pages. Can you try booting xen-debug.gz instead of xen.gz, and see
> >> if xen has something to say about this XENMEM_decrease_reservation
> >> operation (should appear just before the NetBSD kernel reports that
> >> it failed).
> >>
> >>   
> > Hrm... in a bizarre twist of fate, xen-debug.gz actually manages to get
> > past the bnx init.  Here's the serial dump, not sure why it stops where
> > it does, but I won't be able to look at that until tonight.
> > 
> 
> Just to confirm, the VGA console is blank, so the serial output is all
> there is.  <ctrl>+aaa does switch to Xen, but dom0 is unresponsive
> following the output I posted earlier.  (Besides echoing any input.)

After swicthing to xen you could try 'q' and see if the dom0 prints
anything on its console. 'd' may also be usefull if you can match the
addresses printed with the netbsd.gdb kernel using gdb.

I remember having strange issues with a 4GB ram dell 2950 and xen (3.1.x/i386).
The dom0 kernel would segfault unless I reduce the amount of ram seen by
the xen kernel using mem=3072M on the xen.gz boot line (xen.gz did see
something like 3200M as it's a 32bit kernel).
A supermicro server also with 4GB ram didn't have troubles with the same
xen and dom0 kernels.

My theroy at that time was that the Dell BIOS did provide either a bogus
memory segment to xen, or that xen misinterpreted the BIOS's memory map.
This was probably the last memory segment as the dom0 kernel is loaded
in the top of the RAM. You can try reducing a bit the ram availble to xen
like I did.

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