Hello,
I was running in the same problem early this year. Probably you
have found my mails in the archive. Unfortunately I was not able
solve the problem. I am running now 3.3.6 on my laptop (which
furtunately supports the graphics chips that my laptop has).
Just as a datapoint: My understanding
On Sun, Jul 29, 2001 at 04:38:06PM +0200, Sheldon Hearn wrote:
> On Sun, 29 Jul 2001 22:29:40 +0800, Michael Robinson wrote:
> > I'd like to get advice on which of the following courses of action to take:
> >
> > 1. Isolate and fix the problem. I would need some help here.
>
> Try a better-pr
On Thu, 26 Jul 2001, Sheldon Hearn wrote:
> On Wed, 25 Jul 2001 19:20:45 MST, Kris Kennaway wrote:
>
> > Isn't this backwards? Code shouldn't be making assumptions about the
> > special meaning of numeric gids. What if you wanted to renumber gid
> > wheel to something else?
>
> So? My primary
Hi,
Just cvsup'd the latest sources and now KDE is very unstable. During window
opens or during busy times the box locks up. This is also happening reliably
on logout. I have two boxes running current, and they both have the same
symptoms. One's a 500MHz PIII and the other is a 233MHz PII. I'd
I've got an ongoing problem with apache. Sometimes in normal operation,
and always when sent a SIGHUP, the main httpd process will spin and
consume the cpu. GDB reveals that it's stuck somewhere in a thread
handling routine:
Program received signal SIGINT, Interrupt.
0x2862a31c in _thread_sig_h
- Original Message -
From: "Donald J. Maddox" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 30, 2001 12:10 AM
Subject: Re: just moved to current, mouse is jerky
> Try not using /dev/{u}random (don't load random.ko at boot). The random
> device uses mouse interrupts to h
On Mon, Jul 30, 2001 at 07:44:33AM -0700, David O'Brien wrote:
> On Sun, Jul 29, 2001, Kris Kennaway wrote:
> >
> > installed. This would involve a repo copy of crypto/openssl/crypto/bn
> > to contrib/openssl-bn or something, and I'd keep the two in sync with
> > future vendor imports.
>
> You'r
On Mon, Jul 30, 2001 at 09:28:06AM -0700, John Baldwin wrote:
>
> On 30-Jul-01 Kris Kennaway wrote:
> > Hi all,
> >
> > For the past 2 or 3 weeks my -current system has been experiencing
> > temporary lockups, usually under disk load. The entire system will
> > hang for around 20-30 seconds, du
fsck will create lost+found if it's not there.
On Mon, 30 Jul 2001, Aaron Angel wrote:
> On Sun, 29 Jul 2001, Matthew Jacob wrote:
>
> > 'truss clear |& tee /tmp/x'?
>
> ok, I figured out the clear issue...I didn't have entries in termcap for
> the QNX terminals (of course, not know that QNX
On Sun, 29 Jul 2001, Matthew Jacob wrote:
> 'truss clear |& tee /tmp/x'?
ok, I figured out the clear issue...I didn't have entries in termcap for
the QNX terminals (of course, not know that QNX used odd terminal names,
...). I'm still wondering, though, if there is such a thing as lost+found
in
Hi?!
Got fdisk broken recently or does it have to do with SOFTUPDATES?
Thanks!
Jan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Mike Smith schrieb:
[...]
> Unfortunately, I can't reproduce the problem here - the new timer seems
> to be working just fine. Can anyone seeing this please let me know:
>
> - What power management hardware your system has: look at the output of
>pciconf -lv for a "power management controll
On 30-Jul-01 Garrett Wollman wrote:
> <
> said:
>
>> However, the networking stack is being redone,
>
> By whom? I haven't seen anything about this posted to -net.
Err, bogon, networking stack _locking_ is being redone. (Missing keyword there)
jlemon is heading up that task atm, but I don't
>...since a lock order reversal means that you can get in a deadlock...
Argh, of course. It's only not problematic if it's a uniprocessor
and it doesn't take an interrupt at the wrong time. Sorry for being
dense, I'm still used to spl() =)
Bill
To Unsubscribe: send mail to [EMAIL PROTECTED
On Mon, Jul 30, 2001 at 12:31:43PM -0400, Garrett Wollman wrote:
> < said:
>
> > However, the networking stack is being redone,
>
> By whom? I haven't seen anything about this posted to -net.
I don't think John actually means "redone," just "locked down," or
"mutexified."
> -GAWoll
On Mon, 30 Jul 2001 09:28:09 MST, John Baldwin wrote:
> > panic: witness_restore: lock (sleep mutex) Giant not locked
>
> This is a different one. Is this during the dump itself? That I can
> try to work on. (Basically, I need to make witness just stop doing
> all of its various check
< said:
> However, the networking stack is being redone,
By whom? I haven't seen anything about this posted to -net.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 30-Jul-01 Kris Kennaway wrote:
> Hi all,
>
> For the past 2 or 3 weeks my -current system has been experiencing
> temporary lockups, usually under disk load. The entire system will
> hang for around 20-30 seconds, during which time absolutely no
> network/IO/keyboard/mouse activity is accept
On 30-Jul-01 Sheldon Hearn wrote:
>
>
> On Mon, 30 Jul 2001 07:38:47 MST, "David O'Brien" wrote:
>
>> However, those boxes were panicing often before I made that statement.
>> So I still believe current is now in better shape than it was in June.
>
> I'll be a lot happier when I can enabled D
On 30-Jul-01 Bill Fenner wrote:
>
> This lock order reversal is not a problem. See
> http://www.geocrawler.com/lists/3/FreeBSD/147/50/6267627/
> for the meta-issue of witness being too verbose; I'd post URL's for
> the followup discussion but there wasn't any.
See my response to this thread th
On 27-Jul-01 Bill Fenner wrote:
>
> I'm curious what the long-term plan is for witness(4). For
> example, it complains about BPF and device locks being reversed
> when BPF takes the device out of promiscuous mode --
>
> lock order reversal
> 1st 0xc04c1560 bpf global lock @ /usr/src/sys/net/b
At 2:02 AM -0400 7/30/01, Garance A Drosihn wrote:
>I will do some tests at home tomorrow morning, and
>let you know how it works out.
In the following:
"gilead" refers to a MacOS 10 machine in my office at work which
is running MacOS 10.0.4 plus an update to OpenSSH that
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED] on Mon,
Jul 30, 2001 at 02:06:26AM -0700
On Mon, Jul 30, 2001 at 02:06:26AM -0700, Mike Smith wrote:
> I've just committed a slightly different patch, based on a mix of your
> ideas and mine (mostly yours).
Thank you. Hmm, my previous p
On Mon, 30 Jul 2001, Brian F. Feldman wrote:
>For what it's worth, I tend to simply set "Protocol 1,2" in my .ssh/config
>and for the default case, it works fine (just like it used to). I don't
>want to make that policy decision, though, because we will be better off
>when everyone moves to the
This lock order reversal is not a problem. See
http://www.geocrawler.com/lists/3/FreeBSD/147/50/6267627/
for the meta-issue of witness being too verbose; I'd post URL's for
the followup discussion but there wasn't any.
Bill
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
Dear Ladies & Gentlemen,
Welcome to the GREATEST SEX SHOW on the ENTIRE NET !
We now offer you to ENTER to world´s No.1 voted SEX-SERVER on the WEB !
By far the largest and most incredible content of LIVE SEX is now served to users
WORLDWIDE!
EVERYTHING is offered 100% ANONOMOUSLY & you don´
My apologies for not looking into this more throughly before
posting to the list, but I thought someone might be interested.
The first time I run tcpdump after a reboot, I get this kernel
message:
xl0: promiscuous mode enabled
lock order reversal
1st 0xc04f3fa0 bpf global
"David O'Brien" <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 29, 2001 at 09:53:09PM -0400, Brian Fundakowski Feldman wrote:
> > I need to know, if OpenSSH is ever going to get MFC'ed, are there any people
> > currently running OpenSSH 2.9 from -CURRENT's base and getting major
> > problems with it?
Okay, AFTER rebuilding linuxthreads with the most recent port, IT DID make it past
gen_lex_hash.
Word to the wise, if you haven't rebuilt linuxthreads, I suggest you do to avoid the
problems I have had.
Again, I am running -current of the early hours [CDT] of Sunday morning.
Jim Bryant wrote:
On Mon, 30 Jul 2001 07:38:47 MST, "David O'Brien" wrote:
> However, those boxes were panicing often before I made that statement.
> So I still believe current is now in better shape than it was in June.
I'll be a lot happier when I can enabled DDB_UNATTENDED and do whatever
it is that causes m
On Sun, Jul 29, 2001, Kris Kennaway wrote:
>
> installed. This would involve a repo copy of crypto/openssl/crypto/bn
> to contrib/openssl-bn or something, and I'd keep the two in sync with
> future vendor imports.
You're likely to get people saying "repo bloat". And it does seem a
little wrong
Okay, I just built it successfully without "WITH_LINUXTHREADS=yes".
I also noticed that my linuxthreads lib was linuxthreads-2.1.2, and I'm rebuilding it
with the linuxthreads-2.2.3_1 sources.
Afterwards, I'll try the compile again.
Jim Bryant wrote:
>
> I forgot to add:
>
> I am using the m
On Mon, Jul 30, 2001 at 04:32:00PM +0200, Sheldon Hearn wrote:
> > I am also experiencing total wedging on disk activity (vi foo, was one)
> > on a SCSI system since I updated late last week. My May 7th kernel was
> > rock solid.
>
> Was this before or after you posted publically that -CURRENT s
On Sun, Jul 29, 2001 at 09:53:09PM -0400, Brian Fundakowski Feldman wrote:
> I need to know, if OpenSSH is ever going to get MFC'ed, are there any people
> currently running OpenSSH 2.9 from -CURRENT's base and getting major
> problems with it? Or even minor ones that actually make things more
On Mon, 30 Jul 2001 07:26:55 MST, "David O'Brien" wrote:
> I am also experiencing total wedging on disk activity (vi foo, was one)
> on a SCSI system since I updated late last week. My May 7th kernel was
> rock solid.
Was this before or after you posted publically that -CURRENT seemed
stable
On Sun, Jul 29, 2001 at 07:00:11PM -0700, Kris Kennaway wrote:
> For the past 2 or 3 weeks my -current system has been experiencing
> temporary lockups, usually under disk load. The entire system will
> hang for around 20-30 seconds, during which time absolutely no
> network/IO/keyboard/mouse act
In some email I received from Bruce Evans, sie wrote:
> On Mon, 30 Jul 2001, Darren Reed wrote:
>
> > Using ktrace ref5, I created ~darrenr/ktrace.out with "ktrace -i cc ..."
> > but trying to print it I get:
> > % kdump -f ~/ktrace.out > lout
> > kdump: Cannot allocate memory
> >
> > Is this st
On Mon, 30 Jul 2001, Darren Reed wrote:
> Using ktrace ref5, I created ~darrenr/ktrace.out with "ktrace -i cc ..."
> but trying to print it I get:
> % kdump -f ~/ktrace.out > lout
> kdump: Cannot allocate memory
>
> Is this stack corruption by kdump? ref5:~darrenr/ktrace.out is available
> for
I forgot to add:
I am using the make option: `make WITH_LINUXTHREADS=yes`
Jim Bryant wrote:
>
> I don't know if this belongs here, in the database list, or in the ports list...
>
> Under -current from early Sunday morning [CDT], a build of mysql-server-3.23.39
>hangs forever at:
>
>
I did an archive search of this list, and found a post from April from a guy who had
some diffs to scsi_da.c and the umass driver to
get this thing working. I sent him an email on Friday, but haven't heard back yet.
He said he had it working under -current.
Does anyone have a copy of these dif
I don't know if this belongs here, in the database list, or in the ports list...
Under -current from early Sunday morning [CDT], a build of mysql-server-3.23.39 hangs
forever at:
---
===> Building for mysql-server-3.23.39
.
. [snip]
.
./gen_lex_hash > lex_ha
Hi
I cvsupped my sources yesterday.
# make bulidworld
# make buildkernel
were o.k. ,
# make installkernel stopped with
cd /usr/obj/usr/src/sys/PUKRUPPA-5.5;
MAKEOBJDIRPREFIX=/usr/obj
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin
LIBRARY_PATH=/usr/obj/usr/src/i386/
On Mon, Jul 30, 2001 at 02:03:31AM -0700, Dima Dorfman wrote:
> Kris Kennaway <[EMAIL PROTECTED]> writes:
> > 1) For some reason, my mdmfs line in /etc/fstab always does a chmod
> > 777 /tmp at mount-time
> >
> > /dev/md0/tmpmfs rw,-s=65536 0 0
>
> I can
> Mike,
> Seems like I managed to solve my problem. Attached is to be applied against
> sys/dev/acpica/acpi_pcib.c, rev 1.10 .
Thanks for tracking this down; without hardware to test here, it's been
difficult. Great bug report!
I've just committed a slightly different patch, based on a mix of
Kris Kennaway <[EMAIL PROTECTED]> writes:
> 1) For some reason, my mdmfs line in /etc/fstab always does a chmod
> 777 /tmp at mount-time
>
> /dev/md0/tmpmfs rw,-s=65536 0 0
I can't reproduce this. You say it "does a chmod"; does that mean you
see it cal
45 matches
Mail list logo
