Re: Crash in g_dev_strategy / CURRENT as of yesterday.

DEV_STRATEGY(bp); (kgdb) print *bp-b_dev There is no member named b_dev. (kgdb) I can give you SSH access to the server if it's any help / easier for you to look at this yourself without telling me one command at a time. -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED

Crash in swapgeom_strategy?

= IOPL = 0 currnet process = 6 (pagedaemon) Stopped at swapgeom_strategy+0x3c: movl%edi,0x40(%eax) db panic panic: from debugger Uptime: 12h58m23s panic: free locked buf Uptime: 12h58m24s Dumping 191 MB ...and there it just hangs... -- Regards Eivind Olsen

Still crashes in swapgeom_strategy and also sometimes in propagate_priority

have any suggestions as to what the problem might be? For the record, I've seen the exact same crashes with kernel+world built from source around the 7th and 15th of September as well. -- Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list

Re: Still crashes in swapgeom_strategy and also sometimes in propagate_priority

--On 18. september 2003 09:23 +0200 Eivind Olsen [EMAIL PROTECTED] wrote: Hello. I'm experiencing frequent crashes on my FreeBSD box here. It's running FreeBSD 5.x CURRENT (CVSUP'ed yesterday (the 17th) around 1800 CET). I've now had more crashes which looks like those I mentioned in the last

Unable to compile kernel

it as a module. -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Unable to compile kernel

/ Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]

Two crashes in CURRENT from October 7th, both mention Xint0x80_syscall()

Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Native JDK with libthr/libkse

RAM + 256MB SWAP at that time and it wasn't enough). After I gave it enough diskspace and 192MB RAM + 512MB SWAP it compiled fine. -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman

Fatal trap 12 under RELENG_5_1, anyone who can help?

done to find more information? Any other commands to give to the kernel debugger? Any way of making the crashdump happen next time I see a kernel trap like this? -- Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org

Yet another crash in FreeBSD 5.1

to find out about this crash? -- Regards Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: vinum bug? (Re: Yet another crash in FreeBSD 5.1)

the same crash again (well, it does look like that to my untrained eye). -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL

Re: Yet another crash in FreeBSD 5.1

) debug-kernel available on http://eivind.aminor.no/debug/kernel.debug.gz NOTE! It's approx. 13MB compressed! -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current

Re: vinum bug? (Re: Yet another crash in FreeBSD 5.1)

Size: 8192 MB S home.p1.s0State: up D: WHITESize: 8192 MB S storage.p0.s0 State: up D: BLACKSize: 84 GB S storage.p0.s1 State: up D: WHITESize: 84 GB vinum - -- Regards / Hilsen Eivind Olsen [EMAIL

Re: Yet another crash in FreeBSD 5.1

(Negative bio_offset (%jd) on bio %p, 418 (intmax_t)bp2-bio_offset, bp)); 419 bp2-bio_length = (off_t)bp-bio_bcount; -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org

Re: Yet another crash in FreeBSD 5.1

be needed for further analysis. A: Sorry, I don't have a crash dump. I tried creating one when the computer had crashed by giving the commands panic and then continue but that didn't help. Was this of any help? -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED

Re: Yet another crash in FreeBSD 5.1

debugging (I've looked around in the developers handbook, specifically http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerne ldebug-online-gdb.html) -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http

Re: Crash in g_dev_strategy / CURRENT as of yesterday.

--On 12. august 2003 21:26 +0200 Poul-Henning Kamp [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Eivind Olsen writes: Hello. Some of you might have seen my previous mailings regarding crashes in g_dev_strategy under FreeBSD 5.1 (RELENG_5_1). I have now upgraded to CURRENT (cvsupped

Re: Crash in g_dev_strategy / CURRENT as of yesterday.

-bio_offset = (off_t)bp-bio_blkno DEV_BSHIFT; 402 KASSERT(bp2-bio_offset = 0, 403 (Negative bio_offset (%jd) on bio %p, 404 (intmax_t)bp2-bio_offset, bp)); 405 bp2-bio_length = (off_t)bp-bio_bcount; (kgdb) -- Regards / Hilsen Eivind Olsen [EMAIL

Re: Yet another crash in FreeBSD 5.1

which are apparently not resolved. -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]

Crash in g_dev_strategy / CURRENT as of yesterday.

in fork_exit (callout=0xc04b6f90 vm_pageout, arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:790 (kgdb) Is this of any help at all to anyone? Suggestions as to what I should try out etc.? -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL

Panic in _mtx_lock_sleep

, FreeBSD ELF32, sendmsg), eip = 0x283057af, esp = 0xbfbfe14c, ebp = 0xbfbfe2f8 --- db I then had to write panic two or three times until it started to do the crashdump. -- Regards / Hilsen Eivind Olsen [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list