search

bo-yang / plan9front

Automatically exported from code.google.com/p/plan9front
0 stars 0 forks source link

kernel panic on Virtual Box #118

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I got a kernel panic on my virtual box (very recent standard install). I don't 
know what information to collect on a panic (and how). So attaching the picture.

Original issue reported on code.google.com by 9...@vrtra.net on 9 May 2012 at 12:20

Attachments:

GoogleCodeExporter commented 9 years ago 
is this from live cd boot or after installation?

Original comment by cinap_le...@felloff.net on 10 May 2012 at 2:44

GoogleCodeExporter commented 9 years ago 
recent iso boots just fine in vbox 4.1.6 r74713 on windows xp

Original comment by cinap_le...@felloff.net on 10 May 2012 at 3:08

GoogleCodeExporter commented 9 years ago 
It is after installation.

Original comment by rahul.g....@gmail.com on 10 May 2012 at 3:18

GoogleCodeExporter commented 9 years ago 
The kernel panic does not occur always. I am able to work just fine otherwise. 
I thought it might help to report it even if it is once in a while. The host 
machine is Ubuntu.

Original comment by rahul.g....@gmail.com on 10 May 2012 at 3:19

GoogleCodeExporter commented 9 years ago 
the PC value from the panic scrolled off :( maybe try to
boot with *nodumpstack=1 parameter. (hit key until you
see > prompt, then type *nodumpstack=1 and boot) it also
looks like a double fault from your screenshot. wired.

what version of virtual box is this?

thanks for reporting btw :)

Original comment by cinap_le...@felloff.net on 10 May 2012 at 3:28

GoogleCodeExporter commented 9 years ago 
just ran a test install. worked fine, system booted
normally after install.

Original comment by cinap_le...@felloff.net on 10 May 2012 at 4:06

GoogleCodeExporter commented 9 years ago 
It is VirtualBox 4.1.14
I will post the screen shot if I see it again.

Original comment by rahul.g....@gmail.com on 10 May 2012 at 4:33

GoogleCodeExporter commented 9 years ago 
i think this is most likely a problem when we detect sub mhz cpu frequency. (eg 
m->cpumhz == 0) then intrtime() would divide by zero when trying to scale 
interrupt handling time to the histogram buckets.

Original comment by cinap_le...@felloff.net on 10 Aug 2012 at 9:09

GoogleCodeExporter commented 9 years ago 
geoff added code that will panic the kernel when we guess the cpu frequency 
wrong, which seems to be the problem here. (commited in re5c23972bdda)

Original comment by cinap_le...@felloff.net on 24 Aug 2012 at 2:06

GoogleCodeExporter commented 9 years ago 
commited new guesscpuhz() (commited in r3025c10480cf) that should give more 
stable measurements.

Original comment by cinap_le...@felloff.net on 30 Sep 2012 at 5:55

GoogleCodeExporter commented 9 years ago 
original submitter of bug disappeared, should be fixed

Original comment by cinap_le...@felloff.net on 8 Oct 2012 at 6:55