call+0x310
Xint0x80_syscall() at Xint0x80_syscall+0x1d
-- syscall (28, 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 PROTEC
TOP_SC(p, td, S_PT_SCE);
1008
1009error = (*callp->sy_call)(td, args);
1010}
(kgdb) l *Xint0x80_syscall+0x1d
0xc07f5eed is at {standard input}:146.
141 {standard input}: No such file or directory.
in {standard input}
(kgdb)
--
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]"
in /usr/src.
vimes#
--
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]"
_DEFAULT_BLOCK #block all packets by default
>
vimes#
Any suggestions? I need ipfilter-support and I've had problems when using 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]"
--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 tho
* the blocked chain
177 */
178 if (td == TAILQ_FIRST(&m->mtx_blocked)) {
179 continue;
180 }
181
182 td1 = TAILQ_PREV(td, threadqueue, td_lock
32 1, gran 1
processor eflags= 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 han
ategy (vp=0xc1fa9cc0, bp=0x0) at
/usr/src/sys/fs/specfs/spec_vnops.c:512
512 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
bp2->bio_length = (off_t)bp->bio_bcount;
(kgdb)
--
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]"
out_scan (pass=0) at
/usr/src/sys/vm/vm_pageout.c:1015
#20 0xc04b72f8 in vm_pageout () at /usr/src/sys/vm/vm_pageout.c:1509
#21 0xc032ef61 in fork_exit (callout=0xc04b6f90 , arg=0x0,
frame=0x0) at /usr/src/sys/kern/kern_fork.c:790
(kgdb)
Is this of a
--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 CURRE
here now) but I haven't
gotten to it yet. I'm actually a bit scared of going to CURRENT, especially
since there seems to be mentions of GEOM/Vinum issues 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]"
and try to figure out exactly how
to do remote GDB 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]>
analysis as
discussed below under Kernel Panics. Please don't delete the crash dump; it
may 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
KASSERT(bp2->bio_offset >= 0,
417 ("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]>
State: up D: BLACKSize: 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 ->
--
Re
(kgdb) list *(vinumstart+2b2)
No symbol "vinumstart" in current context.
(kgdb)
If anyone wants to take a look at this themselves I've put the compressed
(gzip) debug-kernel available on
http://eivind.aminor.no/debug/kernel.debug.gz
NOTE! It's approx. 13MB compressed!
-
and).
So, it looks like it's 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-
ped to
disk.
Can anyone suggest what I do next 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]"
ets by default
vimes#
So, can anyone help me out here? Are there anything else I should have 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]
___
ot;a lot" doesn't really say much - I had 128MB 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]>
_
21 matches
Mail list logo
