On Tue, 31 Jul 2001, John Baldwin wrote:
On 31-Jul-01 Vincent Poy wrote:
On Mon, 30 Jul 2001, John Baldwin wrote:
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.
On Tue, 31 Jul 2001 12:06:49 -1000, Vincent Poy wrote:
Yeah, that's the weird part... I thought adding a DDB_UNATTENDED
as a option would atleast make it reboot or something...
For the record, DDB_UNATTENDED is mostly pointless. It just sets the
default value of
On Wed, 1 Aug 2001, Sheldon Hearn wrote:
:
:
:On Tue, 31 Jul 2001 12:06:49 -1000, Vincent Poy wrote:
:
: Yeah, that's the weird part... I thought adding a DDB_UNATTENDED
: as a option would atleast make it reboot or something...
:
:For the record, DDB_UNATTENDED is mostly pointless. It
On Tue, 31 Jul 2001, John Baldwin wrote:
On 31-Jul-01 Vincent Poy wrote:
On Mon, 30 Jul 2001, John Baldwin wrote:
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.
On 31-Jul-01 Vincent Poy wrote:
On Tue, 31 Jul 2001, John Baldwin wrote:
root@pele [9:29pm][/usr/temp]
Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
Jul 28 21:29:40 pele /boot/kernel/kernel: 1st 0xd92fea9c
On Tue, 31 Jul 2001, John Baldwin wrote:
On 31-Jul-01 Vincent Poy wrote:
On Tue, 31 Jul 2001, John Baldwin wrote:
root@pele [9:29pm][/usr/temp]
Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
Jul 28
On 31-Jul-01 Vincent Poy wrote:
On Tue, 31 Jul 2001, John Baldwin wrote:
On 31-Jul-01 Vincent Poy wrote:
On Tue, 31 Jul 2001, John Baldwin wrote:
root@pele [9:29pm][/usr/temp]
Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
Jul 28 21:29:40 pele /boot/kernel/kernel:
On Tue, 31 Jul 2001, John Baldwin wrote:
On 31-Jul-01 Vincent Poy wrote:
On Tue, 31 Jul 2001, John Baldwin wrote:
root@pele [9:29pm][/usr/temp]
Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
Jul 28
On Mon, 30 Jul 2001, John Baldwin wrote:
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
On Mon, 30 Jul 2001 16:52:27 +0200, Sheldon Hearn wrote:
I'll be a lot happier when I can enabled DDB_UNATTENDED and do whatever
it is that causes my panic of the day and actually get a crashdump
instead of
panic: witness_restore: lock (sleep mutex) Giant not locked
Right! We
On 31-Jul-01 Vincent Poy wrote:
On Mon, 30 Jul 2001, John Baldwin wrote:
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
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
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 checks if
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 and
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 my
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 accepted. Usually, after 20-30
seconds the system
This has happened on and off for various platforms since SMPNG.
On Sun, 29 Jul 2001, 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
Compiling Mozilla with make -j 2 got -current to lock up, twice in
succession. I'm running a fairly recent snapshot (a week or two old)
on a Dual celeron box (BP6) with UDMA66 enabled.
The kernel had DDB enabled. I was running X, but I didn't see any
signs of the kernel attempting to get
On 2000-Mar-09 10:05:21 +1100, Peter Dufault [EMAIL PROTECTED] wrote:
There's no difference between rtprio and P1003.1B scheduling other than
the name. rtprio is the same as P1003.1B "SCHED_RR".
I wasn't aware of that.
I'd like to remove the rtprio call from ntpd. I think we ought to
It is rumoured that Vallo Kallaste had the courage to say:
I had a lockup yesterday while stress-testing new SMP machine. Tyan
motherboard with Intel GX chipset, 256MB of memory, one 20GB IBM UDMA66
disk, but running at UDMA33. All power management disabled completely in
the BIOS. I was doing
On 2000-Mar-07 06:29:17 +1100, Dave Boers [EMAIL PROTECTED] wrote:
It is rumoured that Arun Sharma had the courage to say:
Compiling Mozilla with make -j 2 got -current to lock up, twice in
succession. I'm running a fairly recent snapshot (a week or two old)
on a Dual celeron box (BP6) with
:On 2000-Mar-07 06:29:17 +1100, Dave Boers [EMAIL PROTECTED] wrote:
:It is rumoured that Arun Sharma had the courage to say:
: Compiling Mozilla with make -j 2 got -current to lock up, twice in
: succession. I'm running a fairly recent snapshot (a week or two old)
: on a Dual celeron box (BP6)
On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers
[EMAIL PROTECTED] wrote:
I'm interested in the fix, of course :-) But where to start looking? I've
had three lockups so far (none before january 2000) but I didn't find
anything that reliably triggered it.
I had a lockup yesterday while
I'll second this email...
My computer had been stable all winter (with setiathome runnning full
time) but suddenly come the Australian summer it started freezing.
Not panicing, just totally freezing under load.
I could reproduce it by trying to build the whole of KDE and each time
it was a
It is rumoured that Arun Sharma had the courage to say:
Compiling Mozilla with make -j 2 got -current to lock up, twice in
succession. I'm running a fairly recent snapshot (a week or two old)
on a Dual celeron box (BP6) with UDMA66 enabled.
Finally. I've been complaining about this on several
On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers wrote:
Has this been fixed ? Is anyone interested in investigating ?
I'll post more info if I find anything.
I'm interested in the fix, of course :-) But where to start looking? I've
had three lockups so far (none before january 2000)
It is rumoured that Arun Sharma had the courage to say:
The cooling theory sounds the most plausible so far. I'm not over clocking
my CPUs (Celeron 366s) and have appropriate cooling installed. But the
machine is kept in a small room, with a bunch of other machines and gets
a bit warm at
The cooling theory sounds the most plausible so far. I'm not over clocking
my CPUs (Celeron 366s) and have appropriate cooling installed. But the
machine is kept in a small room, with a bunch of other machines and gets
a bit warm at times.
I have seen a couple of suggestions that this may
On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers wrote:
on a Dual celeron box (BP6) with UDMA66 enabled.
Finally. I've been complaining about this on several occasions. I'm also
running UDMA66 and Dual Celeron BP6. No overclocking.
Can you people reproduce this on a kernel without SMP
I'm willing to bet a nickel (perhaps more) you people are running non-IBM
UDMA66 drives on that BP6. Seems that most UDMA66 drives are not actually
UDMA66 compliant, and they only drives that have been reported successful
on the BP6 are IBM. Try taking your HD's off the UDMA66 controller and
It is rumoured that Marius Strom had the courage to say:
I'm willing to bet a nickel (perhaps more) you people are running non-IBM
UDMA66 drives on that BP6. Seems that most UDMA66 drives are not actually
UDMA66 compliant, and they only drives that have been reported successful
on the BP6
Dave,
Well, there was a discussion a few weeks back with Soren Schmidt and a few
others. I believe the conclusion was made that this occurred with most WD
drives (interesting about the WD == IBM part, I did notice he mentioned
that in -current a few weeks ago as well). I had a WD20 gig that
It is rumoured that Marius Strom had the courage to say:
Well, there was a discussion a few weeks back with Soren Schmidt and a few
others. I believe the conclusion was made that this occurred with most WD
drives (interesting about the WD == IBM part, I did notice he mentioned
that in
Interesting. I'll check my own archives of -current to see if I can find
the discussion. I always thought that the "Lost Disk Contact" messages were
due to the disk recalibrating itself after six days of continued use. After
Soren increased the timeout from 5 to 10 seconds, I never saw the
On 2000-Mar-06 21:39:11 +1100, Matthew Sean Thyer [EMAIL PROTECTED] wrote:
My computer had been stable all winter (with setiathome runnning full
time) but suddenly come the Australian summer it started freezing.
And it's been the coldest summer for something like 5 years...
How about these
On 2000-Mar-07 06:29:17 +1100, Dave Boers [EMAIL PROTECTED] wrote:
It is rumoured that Arun Sharma had the courage to say:
Compiling Mozilla with make -j 2 got -current to lock up, twice in
succession. I'm running a fairly recent snapshot (a week or two old)
on a Dual celeron box (BP6) with
In message [EMAIL PROTECTED], Peter Jeremy writes
:
How about these Peltier (sp ?) cooling devices I have heard about ?
A Peltier cell is just a semiconductor heat pump. It effectively just
reduces the junction-to-heatsink thermal resistance, allowing you (in
theory) to use a less efficient
It is rumoured that Peter Jeremy had the courage to say:
Note that ntpd will use rtprio if the Posix P1003.1b extensions aren't
enabled in the kernel. (These were enabled by default in GENERIC on
i386 in mid-January). If you have the new ntpd (rather than xntpd)
and are running a kernel
On Mon, Mar 06, 2000 at 11:59:21PM +0100, Dave Boers wrote:
It is rumoured that Peter Jeremy had the courage to say:
Note that ntpd will use rtprio if the Posix P1003.1b extensions aren't
enabled in the kernel. (These were enabled by default in GENERIC on
i386 in mid-January). If you
On Mon, Mar 06, 2000 at 03:46:25PM -0600, Marius Strom wrote:
Unfortunately, the discussions occurred while the mailing list archive was
kaput (WD Drive on UDMA66? =]) so it's not archived where I can find it.
I think this is the thread you're looking for:
1. Is your computer overclocked?
2. Is the computer totally frozen? (i.e. scroll lock doesn't turn the light on)
3. Does similar load crash the box as well? (try make -j2 world)
4. Does it freeze in the same spot?
5. Is the computer not responding to pings?
If you've answered yes to a good
Compiling Mozilla with make -j 2 got -current to lock up, twice in
succession. I'm running a fairly recent snapshot (a week or two old)
on a Dual celeron box (BP6) with UDMA66 enabled.
The kernel had DDB enabled. I was running X, but I didn't see any
signs of the kernel attempting to get into
42 matches
Mail list logo
