Hello, Having just seen Jonathan Haslam (almost) modeling his fabulous "Fast Reboot" t-shirt at LOSUG last night, I thought I would give it a try in my 2008.11 installation. And it worked great, and is a great new feature..
Then I did it a second time, and the VM panicked. I had kmdb loaded, so was able to get a stack backtrace, which contained the following (apols for absence of arguments to the routines; but where there are no arguments, I have inserted parentheses)). kmdb_enter+0x9 debug_enter+0x29 panicsys+0x354 vpanic+0xc3 panic+0x12 die+0x93 trap+0x1422 [all of which you would kinda expect in a panic scenario] Then in the backtrace: 0xfe00837c() 0x501d Both of which look strange... Then: pci_check_bios+0x2e() pci_check+0x1e() pci_cfgspace_init+0x31 mlsetup+0x42 Which suggests that the problem area is PCI. Another side-issue is that when I try to quit kmdb, I get "mkmdb: cannot modify read-only variable 'mdb_ks'", and the only way "forward" is to reset the VM. This is reproduceable. Kmdb also reports that there is a "Bad kernel fault at addr=0x889cb9b3c", and that "pc=0x501d" Repeating without kmdb loaded, I get "panic[cpu0]=fec1e360 BAD TRAP type=e" repeated, until finally "WARNING: Request for too much kernel memory (4096 bytes), will hang forever", and the code "delay(1000000000)" in a "for(;;)" loop in vm_page.c sees to that ;-) Finally, my VirtualBox is 2.0.6. Anyone any ideas? Or anything I could try..... Thanks and regards... Sean. -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
