On Mon, 27 Nov 2000, Andrew Gallatin wrote:
Bruce Evans writes:
Possible causes of the problem:
1) isa_handle_intr() claims to send specific EOIs (0x30 | irq) but
actually sends non-specific ones (0x20 | garbage). Since interrupts
I think that sending non-specific EOIs is
In [EMAIL PROTECTED],
Andrew Gallatin wrote:
Bruce Evans writes:
Possible causes of the problem:
1) isa_handle_intr() claims to send specific EOIs (0x30 | irq) but
actually sends non-specific ones (0x20 | garbage). Since interrupts
may be handled in non-LIFO order, this
Bruce Evans writes:
Possible causes of the problem:
1) isa_handle_intr() claims to send specific EOIs (0x30 | irq) but
actually sends non-specific ones (0x20 | garbage). Since interrupts
may be handled in non-LIFO order, this results in EOIs being sent
for the wrong
On Fri, Nov 17, 2000 at 05:58:30PM -0800, Kris Kennaway wrote:
On Fri, Nov 17, 2000 at 12:55:28PM +0100, Soren Schmidt wrote:
I thought I was the only one, since my question on the freebsd-current
mailing list went unanswered.
You are _not_ alone, there has been numerous complains
Interestingly though - I thrashed the disks for about 15 minutes to no
avail before kldloading random.ko and firing up ssh, at which point it
froze within a few minutes while typing. Obviously one data point
isn't much to go off, but it might be somewhere to start looking.
Now that I've
On Thu, Nov 16, 2000 at 12:20:49PM -0500, Steven E. Ames wrote:
It seems to only do it SMP... the same machine built with a non-SMP
kernel (same source code) runs just fine for extended periods.
I have a non-SMP machine that is running a 15-nov current kernel, which
freezes a few times a day.
On Fri, 17 Nov 2000 10:30:02 -0800 (PST), John Baldwin [EMAIL PROTECTED] said:
what the WITNESS code does is perform extra checks on mutex
enter's and exit's to ensure that we aren't handling mutexes in
such a way that a deadlock is possible. Thus, it verifies that
you don't
In article local.mail.freebsd-current/[EMAIL PROTECTED] you
write:
On Fri, 17 Nov 2000 10:30:02 -0800 (PST), John Baldwin [EMAIL PROTECTED] said:
what the WITNESS code does is perform extra checks on mutex
enter's and exit's to ensure that we aren't handling mutexes in
such a way
On Sat, 18 Nov 2000 11:40:34 -0600 (CST), Jonathan Lemon [EMAIL PROTECTED] said:
What version of if_dc.c
1.38
--
Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA
[EMAIL PROTECTED] [EMAIL PROTECTED]
"It's not what we don't know that hurts us,
it's what
On Thu, 16 Nov 2000 10:42:51 PST, Alfred Perlstein wrote:
I would try a new kernel, and perhaps some collabaration with John
to debug these problems rather than just complaining about the
situation. I see at least two experianced developers in the CC
list, there's no reason for these poor
It seems Sheldon Hearn wrote:
I would try a new kernel, and perhaps some collabaration with John
to debug these problems rather than just complaining about the
situation. I see at least two experianced developers in the CC
list, there's no reason for these poor bug reports.
The
On Fri, 17 Nov 2000 12:55:28 +0100 (CET), Soren Schmidt [EMAIL PROTECTED] said:
It doesn't help here at least, the machine(s) just lock up solid
only reset or a powercycle can bring them back...
Same here ... as others noted, started with SMPng ...
--
Michael D. Harnois, Redeemer
In message [EMAIL PROTECTED] Sheldon Hearn writes:
: The problem with a hard lock-up out of which you can't escape into the
: debugger is that it makes meaningful bug reports impossible. My non-SMP
: workstation has exhibited apparently arbitrary lock-ups since the advent
: of SMPng.
You can
On 17-Nov-00 Sheldon Hearn wrote:
On Thu, 16 Nov 2000 10:42:51 PST, Alfred Perlstein wrote:
I would try a new kernel, and perhaps some collabaration with John
to debug these problems rather than just complaining about the
situation. I see at least two experianced developers in the CC
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Sheldon Hearn writes:
: The problem with a hard lock-up out of which you can't escape into the
: debugger is that it makes meaningful bug reports impossible. My non-SMP
: workstation has exhibited apparently arbitrary
In message 25636.974487067@critter Poul-Henning Kamp writes:
: In message [EMAIL PROTECTED], Warner Losh writes:
: In message [EMAIL PROTECTED] Sheldon Hearn writes:
: : The problem with a hard lock-up out of which you can't escape into the
: : debugger is that it makes meaningful bug reports
On Fri, Nov 17, 2000 at 12:55:28PM +0100, Soren Schmidt wrote:
I thought I was the only one, since my question on the freebsd-current
mailing list went unanswered.
You are _not_ alone, there has been numerous complains about this
on the list, but so far they have not been taken seriously
: You can also short IOCHK to ground to get an NMI which kicks you into
: the debugger, even in an interrupt context.
:
: Bad news for you warner: On a too large sample of my newer
: motherboards this doesn't work anymore :-(
There's also a pci signal that you can either pull up or pull
On Thu, 16 Nov 2000, Soren Schmidt wrote:
After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in
10 min after boot...
You mean "is still freezing" right ?
Current has been like this for longer than I care to think about, it
seems those in charge doesn't take these
uot; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, November 16, 2000 12:17 PM
Subject: Re: CURRENT is freezing again ...
It seems Boris Popov wrote:
On Thu, 16 Nov 2000, Soren Schmidt wrote:
After last cvsup my machine (Dual PIII, SMP kernel) is freezing
again in
10 min after bo
It seems Boris Popov wrote:
On Thu, 16 Nov 2000, Soren Schmidt wrote:
After last cvsup my machine (Dual PIII, SMP kernel) is freezing
again in
10 min after boot...
You mean "is still freezing" right ?
Current has been like this for longer than I care to think about,
* Steven E. Ames [EMAIL PROTECTED] [001116 09:27] wrote:
It seems to only do it SMP... the same machine built with a non-SMP
kernel (same source code) runs just fine for extended periods.
John just checked in some code last night that may address your
problems.
I would try a new kernel, and
On 16-Nov-00 Valentin Chopov wrote:
Hi,
After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in
10 min after boot...
Thanks,
Val
Two questions:
1) What revision of sys/kern/kern_synch.c do you have? I fixed several things
yesterday, and the latest version is
It seems John Baldwin wrote:
1) What revision of sys/kern/kern_synch.c do you have? I fixed several things
yesterday, and the latest version is 1.108.
1.108
2) If you do have the latest version, have you compiled a kernel with WITNESS,
INVARIANTS, and INVARIANT_SUPPORT to see how it
On Thu, Nov 16, 2000 at 10:27:39PM +0100, Soren Schmidt scribbled:
| It seems John Baldwin wrote:
|
| 1) What revision of sys/kern/kern_synch.c do you have? I fixed several things
| yesterday, and the latest version is 1.108.
|
| 1.108
|
| 2) If you do have the latest version, have you
25 matches
Mail list logo
