At 12:29 PM -0700 1/20/05, Scott Long wrote: >Ketrien I. Saihr-Kenchedra wrote: > >>Screen transcription attached. In a nutshell; >> >>fdc0: <floppy drive controller> port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 >>device_attach: fdc0 returned 6 >>sio0: <16550A-compatible COM port> port0x3f8-0x3ff irq 4 flags 0x10 on acpi0 >>sio0: type 16550A >>Memory modified after free 0xc1cde200(252) val=0 _at_ 0xc1cde228 >>panic: Most recently used by none >> >>System was fine with Jan16 srcs, fdc returning 6 is new. Looks >>like a uma problem to me, but odd enough that I'm honestly not >>sure. Need ips(4) for dumpdev, so no dump again. (Argh.) >> > >I'm seeing this quite often too. I'm hoping that Bosko will make >his memguard changes available soon as I'm sure it could quickly >be tracked down with them. Ugh. I see this too, immediately at bootup. The system can't even make it into single-user mode. Right now I can't get a dump of it, since doadump() complaints that it doesn't know my dump device. How do I set the dump-device from the boot-loader? Will a dump of this be of any help to someone, or does the panic happen too late to have any useful information? -- Garance Alistair Drosehn = gad_at_gilead.netel.rpi.edu Senior Systems Programmer or gad_at_freebsd.org Rensselaer Polytechnic Institute or drosih_at_rpi.eduReceived on Thu Jan 20 2005 - 18:46:28 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:26 UTC