I get this all the time, and have for months now. On two different systems (both updated to -current about 2 times per month), both PCs (but with greatly differing HW).
What would be my first step to resolve this? I sent in a PR, with lots of notes, things I tried, and stack dumps. I'm willing to do some more work on it, if someone can point me in the right direction. panic: bremfree: bp 0xc77938f4 not locked panic messages: --- panic: Most recently used by kqueue syncing disks... panic: bremfree: bp 0xc77938f4 not locked Uptime: 1d2h2m49s Dumping 256 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- #0 0xc02f9a9b in doadump () (kgdb) where #0 0xc02f9a9b in doadump () #1 0xc02f9f7d in boot () #2 0xc02fa1a8 in panic () #3 0xc033a477 in bremfree () #4 0xc033cc60 in getblk () #5 0xc033a5aa in breadn () #6 0xc033a55c in bread () #7 0xc03fd2e6 in ffs_update () #8 0xc0411802 in ffs_fsync () #9 0xc040f18f in ffs_sync () #10 0xc034c358 in sync () #11 0xc02f9b9c in boot () #12 0xc02fa1a8 in panic () #13 0xc0434a9d in mtrash_ctor () #14 0xc0433527 in uma_zalloc_arg () #15 0xc02ee735 in malloc () #16 0xc02dd0e5 in fdcopy () #17 0xc02e5711 in fork1 () #18 0xc02e4c0a in fork () #19 0xc04657a1 in syscall () #20 0xc0455e5d in Xint0x80_syscall () ---Can't read userspace from dump, or kernel process--- -Seth To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
