Re: About the recent kernel crashes.

2002-07-27 Thread Marc Recht

>   That's not what I was asking for.  He mentionned he had a kernel from
>   the 25th that was working and I wanted the version of subr_mbuf.c that
>   he had used to build _that_ kernel.
Oh, sorry. IIRC then (for me) everything worked just fine with r1.22.

Marc

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: About the recent kernel crashes.

2002-07-27 Thread Bosko Milekic


On Sat, Jul 27, 2002 at 07:27:11PM +0200, Marc Recht wrote:
> > > I started getting unexpected lockups during mozilla sessions after
> > > remaking world & kernel on the evening of July 25.  The screen
> > > would freeze completely, followed a few seconds later by a
> > > spontaneous reboot.
> > > 
> > > After this happened twice I deleted the new kernel and went back
> > > to using the kernel I compiled on the morning of the same day,
> > > July 25, and the crashes disappeared.
> > > 
> > > I've cvsup'd and remade the world twice since then (but not the
> > > kernel) and I remain crash-free.
> 
> > For the kernel that works, what version of src/sys/kern/subr_mbuf.c did
> > you build it from?  I just want to make sure that I didn't break it with
> > any of the changes I've made.  My last change was on 2002/07/24 15:11:23
> > so I don't think it's that, but just to make sure...
> I've exactly the same problems. My subr_mbuf.c is:
>  * $FreeBSD: src/sys/kern/subr_mbuf.c,v 1.23 2002/07/24 15:11:23 bmilekic Exp $
> (cvsup'ed today)
> 
> Marc

  That's not what I was asking for.  He mentionned he had a kernel from
  the 25th that was working and I wanted the version of subr_mbuf.c that
  he had used to build _that_ kernel.

-- 
Bosko Milekic * [EMAIL PROTECTED] * [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: About the recent kernel crashes.

2002-07-27 Thread Marc Recht

> > I started getting unexpected lockups during mozilla sessions after
> > remaking world & kernel on the evening of July 25.  The screen
> > would freeze completely, followed a few seconds later by a
> > spontaneous reboot.
> > 
> > After this happened twice I deleted the new kernel and went back
> > to using the kernel I compiled on the morning of the same day,
> > July 25, and the crashes disappeared.
> > 
> > I've cvsup'd and remade the world twice since then (but not the
> > kernel) and I remain crash-free.

> For the kernel that works, what version of src/sys/kern/subr_mbuf.c did
> you build it from?  I just want to make sure that I didn't break it with
> any of the changes I've made.  My last change was on 2002/07/24 15:11:23
> so I don't think it's that, but just to make sure...
I've exactly the same problems. My subr_mbuf.c is:
 * $FreeBSD: src/sys/kern/subr_mbuf.c,v 1.23 2002/07/24 15:11:23 bmilekic Exp $
(cvsup'ed today)

Marc

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: About the recent kernel crashes.

2002-07-27 Thread walt

Bosko Milekic wrote:
> On Fri, Jul 26, 2002 at 08:18:27PM -0700, walt wrote:
> 
.
.
.
>>Seems to implicate kernel code committed on July 25, sometime after
>>about 1430 GMT.


> For the kernel that works, what version of src/sys/kern/subr_mbuf.c did
> you build it from?...

My source tree has been updated daily since then, so I can't tell from
looking at the sources.  Is there a way to get that info directly from
the kernel?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: About the recent kernel crashes.

2002-07-27 Thread Bosko Milekic


On Fri, Jul 26, 2002 at 08:18:27PM -0700, walt wrote:
> A small observation which I hope will be useful:
> 
> I started getting unexpected lockups during mozilla sessions after
> remaking world & kernel on the evening of July 25.  The screen
> would freeze completely, followed a few seconds later by a
> spontaneous reboot.
> 
> After this happened twice I deleted the new kernel and went back
> to using the kernel I compiled on the morning of the same day,
> July 25, and the crashes disappeared.
> 
> I've cvsup'd and remade the world twice since then (but not the
> kernel) and I remain crash-free.
> 
> Seems to implicate kernel code committed on July 25, sometime after
> about 1430 GMT.

For the kernel that works, what version of src/sys/kern/subr_mbuf.c did
you build it from?  I just want to make sure that I didn't break it with
any of the changes I've made.  My last change was on 2002/07/24 15:11:23
so I don't think it's that, but just to make sure...

-- 
Bosko Milekic * [EMAIL PROTECTED] * [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: About the recent kernel crashes.

2002-07-26 Thread Peter Kostouros

Hi

I ran a gdb session again and I hope the following is more helpful:

GNU gdb 5.2.0 (FreeBSD) 20020627
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-undermydesk-freebsd"...
panic: bremfree: bp 0xc685fe48 not locked
panic messages:
---
panic: Assertion (m->mtx_lock & (MTX_RECURSED|MTX_CONTESTED)) == 0 failed at 
/mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_mutex.c:915

syncing disks... panic: bremfree: bp 0xc685fe48 not locked
Uptime: 2m49s
pfs_vncache_unload(): 1 entries remaining
Dumping 255 MB
ata1: resetting devices ..
done
 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
#0  doadump () at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_shutdown.c:213
213 dumping++;
(kgdb) where
#0  doadump () at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_shutdown.c:213
#1  0xc028b176 in boot (howto=260)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_shutdown.c:345
#2  0xc028b335 in panic ()
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_shutdown.c:493
#3  0xc02bd0a5 in bremfree (bp=0xc685fe48)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/vfs_bio.c:633
#4  0xc02be816 in vfs_bio_awrite (bp=0xc685fe48)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/vfs_bio.c:1627
#5  0xc02651b8 in spec_fsync (ap=0xcfffda94)
at /mnt/aux3/cvs/freebsd/usr/src/sys/fs/specfs/spec_vnops.c:403
#6  0xc0264da7 in spec_vnoperate (ap=0x0)
at /mnt/aux3/cvs/freebsd/usr/src/sys/fs/specfs/spec_vnops.c:121
#7  0xc037a385 in ffs_sync (mp=0xc17fae00, waitfor=2, cred=0xc0ef5e00, 
td=0xc0491540) at vnode_if.h:463
#8  0xc02cbe8c in sync (td=0xc0491540, uap=0x0)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/vfs_syscalls.c:127
#9  0xc028ae1d in boot (howto=256)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_shutdown.c:254
#10 0xc028b335 in panic ()
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_shutdown.c:493
#11 0xc0283fef in mtx_destroy (m=0x0)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_mutex.c:915
#12 0xc03037f9 in in6_pcbdetach (inp=0xc1953248)
at /mnt/aux3/cvs/freebsd/usr/src/sys/netinet6/in6_pcb.c:625
#13 0xc02f4046 in tcp_close (tp=0xc1953348)
at /mnt/aux3/cvs/freebsd/usr/src/sys/netinet/tcp_subr.c:729
#14 0xc02f871a in tcp_disconnect (tp=0xc1953348)
at /mnt/aux3/cvs/freebsd/usr/src/sys/netinet/tcp_usrreq.c:1192
#15 0xc02f6fe8 in tcp_usr_detach (so=0x0)
at /mnt/aux3/cvs/freebsd/usr/src/sys/netinet/tcp_usrreq.c:178
#16 0xc02b57c0 in soclose (so=0xc192c4e0)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/uipc_socket.c:360
#17 0xc02a919a in soo_close (fp=0x0, td=0xc17fea80)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/sys_socket.c:215
#18 0xc02758a2 in fdrop_locked (fp=0xc19f3a8c, td=0xc17fea80) at file.h:228
#19 0xc02754f8 in fdrop (fp=0xc19f3a8c, td=0xc17fea80)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_descrip.c:1622
#20 0xc02754cb in closef (fp=0xc19f3a8c, td=0xc17fea80)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_descrip.c:1608
#21 0xc027417b in close (td=0xc17fea80, uap=0x0)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_descrip.c:800
#22 0xc03c0ec4 in syscall (frame=
  {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 21, tf_ebp = 
-1078989288,
 tf_isp = -805315212, tf_ebx = 677687508, tf_edx = 699043868, tf_ecx = 9, tf_eax = 6, 
tf_trapno = 22, tf_err = 2, tf_eip = 677955607, tf_cs = 31, tf_eflags = 514, 
tf_esp = -1078989412, tf_ss = 47})
at /mnt/aux3/cvs/freebsd/usr/src/sys/i386/i386/trap.c:1050
#23 0xc03b435d in syscall_with_err_pushed () at {standard input}:128
(kgdb) up 11
#11 0xc0283fef in mtx_destroy (m=0x0)
at /mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_mutex.c:915
915 MPASS((m->mtx_lock & (MTX_RECURSED|MTX_CONTESTED)) == 0);
(kgdb) list
910 LOCK_LOG_DESTROY(&m->mtx_object, 0);
911 
912 if (!mtx_owned(m))
913 MPASS(mtx_unowned(m));
914 else {
915 MPASS((m->mtx_lock & (MTX_RECURSED|MTX_CONTESTED)) == 0);
916 
917 /* Tell witness this isn't locked to make it happy. */
918 WITNESS_UNLOCK(&m->mtx_object, LOP_EXCLUSIVE, __FILE__,
919 __LINE__);
(kgdb) p m
$1 = (struct mtx *) 0x0
(kgdb) q




Peter Kostouros wrote:

> Hi
>
> I got something similar after cvsup'ing and generating a system 
> earlier today (4hrs
> ago) and running mozilla. Unlike other times, I have a coredump.
> I hope the following helps:



-- 

Regards

Peter

As always the organisation disavows knowledge of this email



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: About the recent kernel crashes.

2002-07-26 Thread Peter Kostouros

Hi

I got something similar after cvsup'ing and generating a system earlier today (4hrs
ago) and running mozilla. Unlike other times, I have a coredump.
I hope the following helps:

GNU gdb 5.2.0 (FreeBSD) 20020627
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-undermydesk-freebsd"...
(no debugging symbols found)...
panic: bremfree: bp 0xc69041dc not locked
panic messages:
---
panic: Assertion (m->mtx_lock & (MTX_RECURSED|MTX_CONTESTED)) == 0 failed at 
/mnt/aux3/cvs/freebsd/usr/src/sys/kern/kern_mutex.c:915

syncing disks... panic: bremfree: bp 0xc69041dc not locked
Uptime: 2h39m25s
pfs_vncache_unload(): 98 entries remaining
Dumping 255 MB
ata1: resetting devices ..
done
 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
#0  0xc028ad40 in doadump ()
(kgdb) bt
#0  0xc028ad40 in doadump ()
#1  0xc028b176 in boot ()
#2  0xc028b335 in panic ()
#3  0xc02bd0a5 in bremfree ()
#4  0xc02be816 in vfs_bio_awrite ()
#5  0xc02651b8 in spec_fsync ()
#6  0xc0264da7 in spec_vnoperate ()
#7  0xc037a385 in ffs_sync ()
#8  0xc02cbe8c in sync ()
#9  0xc028ae1d in boot ()
#10 0xc028b335 in panic ()
#11 0xc0283fef in mtx_destroy ()
#12 0xc03037f9 in in6_pcbdetach ()
#13 0xc02f4046 in tcp_close ()
#14 0xc02f871a in tcp_disconnect ()
#15 0xc02f6fe8 in tcp_usr_detach ()
#16 0xc02b57c0 in soclose ()
#17 0xc02a919a in soo_close ()
#18 0xc02758a2 in fdrop_locked ()
#19 0xc02754f8 in fdrop ()
#20 0xc02754cb in closef ()
#21 0xc027417b in close ()
#22 0xc03c0ec4 in syscall ()
#23 0xc03b435d in syscall_with_err_pushed ()
(kgdb) q




walt <[EMAIL PROTECTED]> wrote

A small observation which I hope will be useful:

I started getting unexpected lockups during mozilla sessions after
remaking world & kernel on the evening of July 25.  The screen
would freeze completely, followed a few seconds later by a
spontaneous reboot.

After this happened twice I deleted the new kernel and went back
to using the kernel I compiled on the morning of the same day,
July 25, and the crashes disappeared.

I've cvsup'd and remade the world twice since then (but not the
kernel) and I remain crash-free.

Seems to implicate kernel code committed on July 25, sometime after
about 1430 GMT.





-- 

Regards

Peter

As always the organisation disavows knowledge of this email



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message