On 2002-09-24 18:00, Lars Eggert <[EMAIL PROTECTED]> wrote:
> Alexander Kabaev wrote:
> >On Tue, 24 Sep 2002 00:00:45 -0700
> >"Crist J. Clark" <[EMAIL PROTECTED]> wrote:
> >
> >>Not too sure about that. Now I'm getting SIGSEGV again,
> >
> >You are right. There was a stupid mistake in the latest
The next one will pass.
On Tue, 24 Sep 2002, Dag-Erling Smorgrav wrote:
> --
> >>> Rebuilding the temporary build tree
> --
> >>> stage 1: bootstrap tools
> ---
My latest panic..
Sep 25 11:39:48 leeloo kernel: ../../../vm/uma_core.c:1307: could sleep with
"pcm0:play:1" locked from ../../../dev/sound/pcm/dsp.c:696
Sep 25 11:39:48 leeloo kernel: ../../../vm/uma_core.c:1307: could sleep with
"pcm0:play:1" locked from ../../../dev/sound/pcm/dsp.c:696
Sep
I tried booting a kernel with lock checking enabled and got the
following panic:
panic: mutex vnode interlock owned at vnode_if.h:24
panic()
_mtx_assert()
VOP_ISLOCKED()
vop_unlock_pre()
vput()
kern_mkdir()+0x9e - the first call to vput() to handle the "found" case?
start_init()
fork_exit()
fork
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
JFRH.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I just build latest -CURRENT on my laptop.
The error is:
panic: vrele: negative ref cnt
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
I did the following:
After bootup - logged in as root.
touch'ed /var/log/xferlog
and hit ctrl-d, to logout. (That is when the pani
Michael Hostbaek wrote:
> I just build latest -CURRENT on my laptop.
>
> The error is:
> panic: vrele: negative ref cnt
> Debugger("panic")
> Stopped atDebugger+0x54: xchgl %ebx,in_Debugger.0
>
> I did the following:
> After bootup - logged in as root.
> touch'ed /var/log/xferlog
> and h
Does CURRENT support journaled filesystem ?
P.S. please, CC me, i'm not subscribed
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Funny, this argument suddenly reminds me of the "Hitch Hikers Guide to
the Galexy" :-)
Bob
On Tue, Sep 24, 2002 at 05:01:29PM -0400, Garrett Wollman wrote:
> < said:
>
> > Oh man, this is going to suck. There are thousands and thousands of third
> > party scripts that use +n syntax.
>
> > I a
VAIO Z600TEK, PIII/700, 20 GB, 256 MB.
cvsup from three hours ago, whicle rebooting I get this:
panic: vrele: missed vn_close
Debugger("panic")
Stopped at Debugger+0x45:xchgl%ebx,in_Debugger.0
db> trace
Debugger at Debugger+0x45
panic at panic+0x9f
vrele at vrele+0x13b
vn_close at vn
In message <[EMAIL PROTECTED]>, Bob Willcox writes:
>Funny, this argument suddenly reminds me of the "Hitch Hikers Guide to
>the Galexy" :-)
"I've gone of the idea of progress, it's over rated."
:-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP sin
On Wed, 25 Sep 2002, Ollivier Robert wrote:
> VAIO Z600TEK, PIII/700, 20 GB, 256 MB.
> cvsup from three hours ago, whicle rebooting I get this:
>
> panic: vrele: missed vn_close
> Debugger("panic")
> Stopped at Debugger+0x45:xchgl%ebx,in_Debugger.0
> db> trace
> Debugger at Debugger+
On Wed, 25 Sep 2002, walt wrote:
> Michael Hostbaek wrote:
> > I just build latest -CURRENT on my laptop.
> >
> > The error is:
> > panic: vrele: negative ref cnt
> > Debugger("panic")
> > Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
> >
> > I did the following:
> > After bootup - logge
On Wed, Sep 25, 2002 at 04:19:34PM +0300, Anton Yudin wrote:
>
> Does CURRENT support journaled filesystem ?
There are not journaling file systems in current at this time. Efforts
to port both xfs and jfs are underway.
-- Brooks
--
Any statement of the form "X is the one, true Y" is FA
On Tue, Sep 24, 2002 at 06:13:33PM -0400, Alexander Kabaev wrote:
> > Nope, still getting it.
>
> I was able to reproduce the crash with your config file and unpatched
> GCC, however crash does not happen when I use the patch. Are you using
> make buildkernel or old config/make method?
Since I'
If I may add a comment here...
You already *have* a kind of journaled filesystem for some time now.
Please read "Soft Updates vs. Journalling Filesystems" from M.K.
McKusick (www.mckusick.com).
I'm really sad if see the efforts done especially for porting JFS to
FreeBSD, which has already und
On Wed, 25 Sep 2002, David Wolfskill wrote:
> panic: vrele: missed vn_close
> cpuid = 0; lapic.id =
> Debugger("panic")
> Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
> db> tr
> Debugger(c036903a,0,c0372831,d7b9cb70,1) at Debugger+0x55
> panic(c0372831,0,c03724c2,810,c443
* De: Matthias Schuendehuette <[EMAIL PROTECTED]> [ Data: 2002-09-25 ]
[ Subjecte: Re: Journaled filesystem in CURRENT ]
> If I may add a comment here...
>
> You already *have* a kind of journaled filesystem for some time now.
>
> Please read "Soft Updates vs. Journalling Filesystems" fr
Hi! I'm experiencing an increasing amount of problems here, and will
try to list them below. Some of this may be well known already, but,
hopefully, something will be usefull.
Unless I set rc_ng to NO, the ypbind will not start, even though
enable_nis_client is set and "Starting ypbind" is displa
According to Jeff Roberson:
> A dump would be good. Some more information on your configuration too
I'll send it tomorrow (CET time).
> please. What filesystems were mounted? You said you were rebooting? Had
> you done anything significant with the box?
Filesystems are /, /usr, /var and /lo
I thought it was just me, but since last week sometime I have been seeing
several strange crashes in X. It usually has something to do with the
keyboard. X will bomb out saying it caught a sig11, and the message in my
system log shows a sig6.
At first I thought this was due to using XFree that I
One possible solution to the sort problem:
* Continue to accept the old syntax for now,
but add a warning message, something like:
"Warning: sort +N is deprecated, use -k instead."
* After a year, drop support for the
old syntax. After staring at warning
messages for a year, few peo
Mikhail Teterin wrote:
> Unless I set rc_ng to NO, the ypbind will not start, even though
> enable_nis_client is set and "Starting ypbind" is displayed on boot.
Do you have rpcbind_enable set? ypbind needs the portmapper and will
silently exit if it isn't running.
Lars
--
Lars Eggert <[EMAIL P
> Michael Hostbaek wrote:
> > I just build latest -CURRENT on my laptop.
> >
> > The error is:
> > panic: vrele: negative ref cnt
> > Debugger("panic")
> > Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
> >
> > I did the following:
> > After bootup - logged in as root.
> > touch'ed /var/lo
In the last episode (Sep 25), Lars Eggert said:
> Mikhail Teterin wrote:
> >Unless I set rc_ng to NO, the ypbind will not start, even though
> >enable_nis_client is set and "Starting ypbind" is displayed on boot.
>
> Do you have rpcbind_enable set? ypbind needs the portmapper and will
> silently
Here it's the same. The box is absolutly fubar.
I get always one of these:
panic: vrele: missed vn_close
panic: vrele: negative ref cnt
Sometimes this, too:
syncing disks... 7 7 panic: bremfree: bp 0xd381cab0 not locked
> A dump would be good. Some more information on your configuration too
>
On Wed, 25 Sep 2002, Mikhail Teterin wrote:
> Hi! I'm experiencing an increasing amount of problems here, and will try
> to list them below. Some of this may be well known already, but,
> hopefully, something will be usefull.
>
> Unless I set rc_ng to NO, the ypbind will not start, even though
Dan Nelson wrote:
>
> Ooh. bug! rc.d/ypbind should have the same check all the other
> rpcbind-dependant scripts have:
>
> ypserv_precmd() { case ${OSTYPE} in FreeBSD) if ! checkyesno
> rpcbind_enable && \ ! /etc/rc.d/rpcbind forcestatus 1>/dev/null 2>&1
> then force_depend rpcbind || re
that's all folks...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, Sep 25, 2002 at 09:47:36PM +, attila! wrote:
> David:
>
> DC395U on CURRENT from Houchard's driver works like a
> champ on 'da' (ZIP 100) and 'cd (Creative DVD-RAM)
> devices; I haven't had an 'sa' device since my Exabyte
> died.
>
> I've been beating on the d
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Jeff Roberson wrote:
> Can you give me some more info? What
> filesystems did you have mounted? Any kernel options that are not in
> GENERIC?
I had ext2 mounted in addition to the usual BSD/softupdates and swap partition.
I had just rebooted the new kernel, started X/gnome with an gnome-termi
> On Wed, 25 Sep 2002, Mikhail Teterin wrote:
[...]
> > Unless I set rc_ng to NO, the ypbind will not start, even though
> > enable_nis_client is set and "Starting ypbind" is displayed on boot.
> Locally, I discovered that the hard dependency of ypbind on rpcbind
> now seems to be broken. Try set
On Wed, 25 Sep 2002, Mikhail Teterin wrote:
> Thanks, but I have much bigger troubles at the moment :-( The workaround
> for this one is simple -- rc_ng="NO"...
>
> FWIW, this -- introducing this sort of instability just two months
> before the scheduled release -- is a lot more damaging than
I notice several people complaining about crashing X servers recently.
I'm seeing them also for about 2 weeks or so, usually mozilla-related.
I've seen this error message following at least two or three of
these crashes:
Fatal server error:
Beziers this big not yet supported.
Anyone else seeing
walt ([EMAIL PROTECTED]) wrote:
> WTF is a bezier?
A bezier is a type of curve drawn by endpoints and anchor points to bend
it.
--
Eric Hodel - [EMAIL PROTECTED] - http://segment7.net
All messages signed with fingerprint:
FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04
msg43407/pgp0
On Wed, 25 Sep 2002, Don Lewis wrote:
> I tried booting a kernel with lock checking enabled and got the
> following panic:
>
> panic: mutex vnode interlock owned at vnode_if.h:24
Yeah, sorry, there was a bit of my patch that I forgot to commit. It's in
there now.
Thanks!
Jeff
To Unsubscribe:
On Wed, 25 Sep 2002, walt wrote:
> Date: Wed, 25 Sep 2002 16:45:16 -0700
> From: walt <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: X server crashes?
>
> I notice several people complaining about crashing X servers recently.
> I'm seeing them also for about 2 weeks or so, usually mozilla
On Thu, Sep 26, 2002 at 02:51:05AM +0200, Michael Reifenberger wrote:
> >
> Yes.
> They started after the last round of KSE-kernel changes which
> also required changes to libc_r.
>
I reckon that they're libc_r bugs as well. Linux-Opera has been causing X11 to
coredump. With a kernel from 24 h
Yep, I'm seeing this using the new native Opera binary, when doing some
font-related things.
On Wed, 25 Sep 2002, Eric Hodel wrote:
> walt ([EMAIL PROTECTED]) wrote:
>
> > WTF is a bezier?
>
> A bezier is a type of curve drawn by endpoints and anchor points to bend
> it.
>
>
To Unsubscribe: s
Michael Reifenberger wrote:
> On Wed, 25 Sep 2002, walt wrote:
>
> > Date: Wed, 25 Sep 2002 16:45:16 -0700
> > From: walt <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: X server crashes?
> >
> > I notice several people complaining about crashing X servers recently.
> > I'm seeing them
> On Wed, 25 Sep 2002, Mikhail Teterin wrote:
> > FWIW, this -- introducing this sort of instability just two months
> > before the scheduled release -- is a lot more damaging than the
> > stupid trolls, IMO. The finger-breakers should consider leaving the
> > troll alone and switching to super-g
Jeff Roberson wrote:
> I'll look at it a bit later today. Can you give me some more info?
24 hours later: I just compiled another new kernel. This time all I did was
log in as root and unmount the ext2 filesystem, which gets mounted automatically
at boot. Then I hit ctrl-D and got this:
pa
The VFS panic that was introduced in my recent commits has been fixed. I
accidentally commited extra stuff from my tree that was not entirely
correct.
Thank you all for the error reports and debugging assistance.
Jeff
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
On Wed, 25 Sep 2002, Mikhail Teterin wrote:
> > There are probably going to be a few nits involved in the VFS changes,
> > but there are a number of serious bugs being fixed here. I've been
> > running into a bug on some boxes involving a race condition that
> > occurs when newsyslog runs on a b
That precisely describes my crashes. _always_ when i was typing something.
On Wed, 25 Sep 2002, Peter Wemm wrote:
> This was a few days ago. I was typing something at the time. Mozilla was
> running but it is an old linux binary, not a freebsd-native binary. Unless
> exmh/wish or xterm are th
this is on a UP machine running a -current from ~19 sep.
Two nights in a row it has died with:
panic: pipe buffer gone
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c048d71c,c0538440,c0492060,e2f38c04,1) at Debugger+0x54
panic(c0492060,0,c0491fb
Jeff Roberson wrote:
> The VFS panic that was introduced in my recent commits has been fixed...
The obvious problems (at least) are gone now, thanks. In fact, even
the X server didn't make fun of my Big Beziers this time around.
--
Maybe now's the time to buy a lottery ticket.
To Unsubscri
I use kde3 with Konq and it crashes too on my laptop when i have
multiple browsers open. Its usually my friends or girlfriend who crash
it with all their browsers, but i haven't noticed much of a problem with
Konquer.
On Wed, 2002-09-25 at 16:45, walt wrote:
> I notice several people complaining
50 matches
Mail list logo
