Kenneth R Westerback wrote: > When in doubt, panic. If you can try this and send me the ddb> > trace, perhaps it will be a clue as to why we are doing a block > device open. > > .... Ken
Sounds like a plan! :-) -Bryan. ----- panic: Why are we here? Stopped at Debugger+0x4: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb> trace Debugger(ff4c0,d0d76480,100,d2f460a0,d084ce9c) at Debugger+0x4 panic(d0783d06,0,d08cd050,0,402) at panic+0x55 sdopen(402,1,6000,0,402) at sdopen+0x28e spec_open(d0a2dbc0,d084ce99,0,400,d085f9fc) at spec_open+0x1db VOP_OPEN(d2f460a0,1,ffffffff,0) at VOP_OPEN+0x34 sr_meta_native_bootprobe(d0d96800,d0d65800,d0a2de6c,d084ce99) at sr_meta_native_bootprobe+0x9b sr_boot_assembly(d0d96800,d0d96800,0,d0376aed,d0a2df20) at sr_boot_assembly+0x82e config_attach(0,d08550a4,0,0,d07460b7) at config_attach+0xfd config_rootfound(d0746100,0,d074dddc,0,3) at config_rootfound+0x27 main(0,0,0,0,0) at main+0x4bd ddb>
