> hi, i got the following panic in a kernel I compiled today: panic: D2B called on non-block f0d72af8 (double-free?) panic: D2B called on non-block f0d72af8 (double-free?) dumpstack disabled cpu0: exiting it happen evertime i plug a usb device in. i don't know how to debug this. any ...

hi, i got the following panic in a kernel I compiled today: panic: D2B called on non-block f0d72af8 (double-free?) panic: D2B called on non-block f0d72af8 (double-free?) dumpstack disabled cpu0: exiting it happen evertime i plug a usb device in. i don't know how to debug this. any suggestions? with my old kernel(2008-04-30) everthing works fine. markus

... USP=20A55 AX 00000011 BX 00000006 CX 00000000 DX 00000009 S1 00000001 D1 000020ASE BP 00000009 CS 0010 DS 0008 ES 0008 FS 001b GS 0017 MCA 40de 1064a MCT fc0000000000d1dd ur f0e42f34 up f0233318 panic: fault: 0x9 cpu0 exiting I'm afraid I'm not of much help but recently I was told to email this kind of problems to 9trouble@plan9.bell-labs.com. --Vej

... 0008 ES 0008 FS 001b GS 0017 MCA 40de 1064a MCT fc0000000000d1dd ur f0e42f34 up f0233318 panic: fault: 0x9 cpu0 exiting dump stack disabled cpu0 exiting **end of output The numbers after ...registers for window 114" differing values for the mid-section. and at the end invariably: panic: fault: 0x9 It does not seem that the error is repeatable. The system is a ...

On Wed, Nov 21, 2007 at 05:29:26PM +0100, Frank Lenaerts wrote: Hi, Apart from the original problem (the panic), where should I put the plan9.ini style file when booting via PXE from a non-Plan 9 (e.g. Linux) box. Would 9pxeload look for the file in /cfg/pxe under the tftp root directory (e.g. /tftpboot)? As this machine does not have a floppy drive and I do not want to burn a new ...

...the same root cause. i saw this error on my machine yesterday. - erik On Wed Nov 21 12:32:22 EST 2007, tim@nop.cx wrote: i think this is realted to recient problems with huge kernels. actually this looks like something different. i never got a panic with the previous issue, the kernel just hung after it was loaded. unless Andrey saw something different....

> i think this is realted to recient problems with huge kernels. actually this looks like something different. i never got a panic with the previous issue, the kernel just hung after it was loaded. unless Andrey saw something different....

...<menu> ... Plan 9 E820: ... <several E820: panic: vmap: va=0xf0400000 pa=0x00400000 pde=0x00400083 panic: vmap: va=0xf0400000 pa=0x00400000 pde=0x00400083 dumpstack disabled cpu0: ... the possible cause, I just googled for the panic line and found a post in an old ...? [*] http://lists.cse.psu.edu/archives/9fans/2006-July.txt Kind regards, -- Frank ...

...make sure I've actually got qemu's host->guest port redirection working. Stumbled upon a reproducable panic along the way: term%% cat /net/tcp/clone 0term%% echo -n hangup /net/tcp/0/ctl panic: tcphangup: version 0 panic: tcphangup: version 0 dumpstack disabled cpu0: exiting the kernel has this to say about the NIC: #l0: NE2000: 10Mbps port...

Sorry about that. We're soaking a version of the kernel that includes a reference count in the Block struct. It's so far used by the Ethernet drivers, IP stack and USB code, and usbohci.c escaped a little too early. I've just pushed out a newer allocb.c to sources that initializes the refence count at allocation.