On Wed, Sep 10, 2003 at 01:53:24PM -0700, Alan Horn wrote:
> 
> 
> The saga of the soekris box continues....
> 
> I decided to once again try pxe booting to see if I could get this
> box to stay up for any length of time. The plan was to get it netbooted,
> then install onto the microdrive from the netboot.
> 
> dhcp server and pxe server are both on the same netbsd 1.6.1 box.
> Diskless tree is setup in /export/diskless/root.
> 
> I needed to cp /export/diskless/root/netbsd to
> /export/diskless/root/pxeboot_ia32_com0.bin for some reason, the boot
> wouldn't find (or couldn't open, despite my making various permissions
> wide open just 'to see') /export/disklex/root/netbsd.
> 
> This may be something funky with my dhcp server setup...
> 
> Anyway.. the system panics during boot, and these are the messages I see :
> 
> > boot f0
> 
> BootManage UNDI, PXE-2.0 (build 082)
> BootManage PXE-2.0 PROM 1.0, NATSEC 1.0, SDK 3.0/082 (OEM52)
> Copyright (C) 1989,2000 bootix Technology GmbH, D-41466 Neuss.
> PXE Software Copyright (C) 1997, 1998, 1999, 2000 Intel Corporation.
> Licensed to National Semiconductor
> 
> CLIENT MAC ADDR: 00 00 24 C0 B1 3C
> CLIENT IP: 192.168.0.65  MASK: 255.255.255.0  DHCP IP: 192.168.0.59
> GATEWAY IP: 192.168.0.1
> PXE-E11: ARP timeout
> 
> 
> >> NetBSD/i386 PXE Boot, Revision 1.0
> >> (autobuild@tgm.daemon.org, Sun Sep  8 19:25:51 UTC 2002)
> >> Memory: 577/64512 k
> Press return to boot now, any other key for boot menu
> Starting in 0
> PXE BIOS Version 2.1
> Using PCI device at bus 0 device 18 function 0
> pxe0: Ethernet address 00:00:24:c0:b1:3c
> net_open: client addr: 192.168.0.65
> net_open: subnet mask: 255.255.255.0
> net_open: net gateway: 192.168.0.1
> net_open: server addr: 192.168.0.59
> net_open: server path: /export/diskless/root
> net_open: file name: pxeboot_ia32_com0.bin
> 
> 
> NetBSD 1.6.1 (GENERIC) #0: Tue Apr  8 12:05:52 UTC 2003
>     autobuild@tgm.daemon.org:/autobuild/netbsd-1-6/i386/OBJ/autobuild/netbsd-1-C
> cpu0: AMD Am5x86 W/B 133/160 (486-class)
> cpu0: features 1<FPU>
> total memory = 65088 KB
> avail memory = 53860 KB
> using 839 buffers containing 3356 KB of memory
> BIOS32 rev. 0 found at 0xf00c0
> mainbus0 (root)
> pci0 at mainbus0 bus 0: configuration mode 1
> pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
> pchb0 at pci0 dev 0 function 0
> pchb0: Advanced Micro Devices Elan SC520 System Controller (rev. 0x00)
> sip0 at pci0 dev 18 function 0: NatSemi DP83815 10/100 Ethernet, rev 00
> sip0: interrupting at irq 10
> sip0: Ethernet address 00:00:24:c0:b1:3c
> nsphyter0 at sip0 phy 0: DP83815 10/100 media interface, rev. 1
> nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> sip1 at pci0 dev 19 function 0: NatSemi DP83815 10/100 Ethernet, rev 00
> sip1: interrupting at irq 11
> sip1: Ethernet address 00:00:24:c0:b1:3d
> nsphyter1 at sip1 phy 0: DP83815 10/100 media interface, rev. 1
> nsphyter1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> sip2 at pci0 dev 20 function 0: NatSemi DP83815 10/100 Ethernet, rev 00
> sip2: interrupting at irq 5
> sip2: Ethernet address 00:00:24:c0:b1:3e
> nsphyter2 at sip2 phy 0: DP83815 10/100 media interface, rev. 1
> nsphyter2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> isa0 at mainbus0
> com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
> com0: console
> com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
> kbc selftest: ffffffff
> wdc0 at isa0 port 0x1f0-0x1f7 irq 14
> wd0 at wdc0 channel 0 drive 0: <IBM-DSCM-11000>
> wd0: drive supports 16-sector PIO transfers, LBA addressing
> wd0: 1027 MB, 2088 cyl, 16 head, 63 sec, 512 bytes/sect x 2104704 sectors
> wd0: drive supports PIO mode 3, DMA mode 1
> extent `ioport' (0x0 - 0xffff), flags = 0x3
>      0x0 - 0xf
>      0x80 - 0x8e
>      0xc0 - 0xdf
>      0x1f0 - 0x1f7
>      0x2f8 - 0x2ff
>      0x3f6 - 0x3f6
>      0x3f8 - 0x3ff
>      0x530 - 0x533
>      0x534 - 0x537
>      0xe000 - 0xe0ff
>      0xe100 - 0xe1ff
>      0xe200 - 0xe2ff
> extent_free: start 0x134, end 0x137
> panic: extent_free: region not found
> Stopped in pid 0 (swapper) at   cpu_Debugger+0x4:       leave
> db>
> 
> This is very reproducible. I suspected the IBM microdrive in wd0, so
> I removed that ad repeated.
> 
> The same thing happens, except this time panic occurs a few lines earlier at :
> 
> wdc0 at isa0 port 0x1f0-0x1f7 irq 14
> extent `ioport' (0x0 - 0xffff), flags = 0x3
>      0x0 - 0xf
>      0x80 - 0x8e
>      0xc0 - 0xdf
>      0x1f0 - 0x1f7
>      0x2f8 - 0x2ff
>      0x3f6 - 0x3f6
>      0x3f8 - 0x3ff
>      0x530 - 0x533
>      0x534 - 0x537
>      0xe000 - 0xe0ff
>      0xe100 - 0xe1ff
>      0xe200 - 0xe2ff
> extent_free: start 0x134, end 0x137
> panic: extent_free: region not found
> Stopped in pid 0 (swapper) at   cpu_Debugger+0x4:       leave
> db>
> 
> Trace showed :
> 
> db> trace
> cpu_Debugger(137,1f7,1f0,c028d84f,c04f3f20) at cpu_Debugger+0x4
> panic(c04f3f45,c08f003c,533,c0422703,c0738b9c) at panic+0xad
> extent_free(c067d3c0,134,4,10) at extent_free+0x123
> i386_memio_unmap(0,134,4,0,c0738ce4) at i386_memio_unmap+0xd7
> ad1848_isa_mapprobe(c0738b9c,534,1,c0738ce4) at ad1848_isa_mapprobe+0x54
> wssfind(c0889b00,c0738b9c,1,c0738ce4) at wssfind+0x82
> wss_isa_probe(c0889b00,c0640f20,c0738ce4,c040f7b4) at wss_isa_probe+0x4f
> isasearch(c0889b00,c0640f20,0,279,c063f584) at isasearch+0xd6
> mapply(c0738d7c,c0640f20,c0738d80,c028ff2f) at mapply+0x20
> config_search(c040f9c0,c0889b00,0,c028bff3,c0889b00) at config_search+0x7c
> isaattach(c08acfc0,c0889b00,c064ca94,c028c25c,c0889b00,c064ca94,c08acfd4,c028bda
> c) at isaattach+0xa4
> config_attach(c08acfc0,c0640cd4,c064ca94,c03947e8,c08acfc0) at config_attach+0x2
> 48
> config_found_sm(c08acfc0,c064ca94,c03947e8,0,c08acfc0) at config_found_sm+0x2f
> mainbus_attach(0,c08acfc0,0,c028c25c,c08acfc0,0,7,c028be43) at mainbus_attach+0x
> 12f
> config_attach(0,c06407e8,0,0,c06870d8) at config_attach+0x248
> config_rootfound(c05073e0,0,c0738f60,c0367ef4) at config_rootfound+0x3f
> cpu_configure(9,c06848e0,c0684ae8,c02795bf,c06848e0) at cpu_configure+0x1f
> configure(c0736010,736000,73d000,500007ff,c07a) at configure+0x49
> main(0,0,0,0,0) at main+0x377
> 
> 
> 
> Any help greatly appreciated, I've had this box now for about four months
> and I'd really like to get some use out of it :)

Looks like a bug in the wss isa front end. Maybe try rebuilding a kernel
without this driver ?

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