On Mon, Apr 22, 2002 at 12:27:50PM +0300, Adrian Penisoara wrote:
> > > How-to-repeat: launch linux-netscape while in X11
> >
> > Are you absolutely sure all kernel modules are up to date? A
> > sure-fire way to cause panics with linux applications is to use an
> > out of date linux.ko.
>
>
On Mon, Apr 22, 2002 at 06:25:17PM +1000, Bruce Evans wrote:
> On Sun, 21 Apr 2002, Maxim Konovalov wrote:
>
> > As Adrian Penisoara already reported
> >
> > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=19645+0+current/freebsd-current
> >
> > there is panic in -current. I believe it is related to
Hi,
On Mon, 22 Apr 2002, Bruce Evans wrote:
> Yes; I forgot to write the clause about it only being equivalent to a
> panic if certain options (mainly INVARIANTS) are configured.
>
> > do see that falloc does lock the file descriptor table too, though ---
> > I wonder how it ever worked.
>
> I
On Mon, 22 Apr 2002, Jacques A. Vidrine wrote:
> On Mon, Apr 22, 2002 at 06:25:17PM +1000, Bruce Evans wrote:
> > I use the same patch. Locking here is essentially equivalent to calling
> > panic() here (except it gives a more confusing panic message :-).
>
> :-) That's a bit of an overstatemen
Hi,
On Sun, 21 Apr 2002, Kris Kennaway wrote:
> On Sun, Apr 21, 2002 at 05:22:20PM +0300, Adrian Penisoara wrote:
>
> > Panicstring: bremfree: bp 0xc77fb678 not locked
>
> This isn't the real panic, it's a second panic caused by trying to
> sync disks.
D'oh... I hope the gdb trace left mor
On Sun, 21 Apr 2002, Maxim Konovalov wrote:
> As Adrian Penisoara already reported
>
> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=19645+0+current/freebsd-current
>
> there is panic in -current. I believe it is related to the next
> commit:
>
> nectar 2002/04/18 17:45:29 PDT
>
> Modified
On Sun, Apr 21, 2002 at 05:22:20PM +0300, Adrian Penisoara wrote:
> Panicstring: bremfree: bp 0xc77fb678 not locked
This isn't the real panic, it's a second panic caused by trying to
sync disks.
> How-to-repeat: launch linux-netscape while in X11
Are you absolutely sure all kernel modules
As Adrian Penisoara already reported
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=19645+0+current/freebsd-current
there is panic in -current. I believe it is related to the next
commit:
nectar 2002/04/18 17:45:29 PDT
Modified files:
sys/kern kern_descrip.c kern_exec.c
Hi,
Environment:
FreeBSD xphome.home.ady.ro 5.0-CURRENT FreeBSD 5.0-CURRENT #0:
Sun Apr 21 10:39:36 EEST 2002 i386
XFree86-4.2.0_1,1 (3dfx Velocity 100 graphics card)
gnome-1.4.1b2_2 + sawfish-gnome-1.0.1
linux_base-6.1_1
linux-netscape-communicator-4.79
Panicstring: brem
