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
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, t
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 inter
> 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 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
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, Andrew Gallatin wrote:
> [fxp isa irq pending but never occurs]
> I then wrote a hack which sends an eoi. If I call my hack from ddb
> and send an eoi for irq10, everything goes back to normal and the
> network interface is back.
>
> So, is it a race in the interrupt code,
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 wha
In article [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 that a deadlock
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 d
> : >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
Valentin Chopov writes:
> Hi,
>
> After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in
> 10 min after boot...
>
I've seen one similar problem on an alpha UP1000 that I'd like some
input about.
The UP1000 is essentially an alpha 21264 stuffed into an AMD Athlon
system.
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 lock-ups since
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 ser
On 17-Nov-00 Sheldon Hearn wrote:
>
>
> On Fri, 17 Nov 2000 10:30:02 PST, John Baldwin wrote:
>
>> # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom
>
> All very well and good once you've figured out which command makes your
> machine go boom.
Yes, I know. I didn't say
On Fri, 17 Nov 2000 10:30:02 PST, John Baldwin wrote:
> # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom
All very well and good once you've figured out which command makes your
machine go boom.
But as I said, the locks I'm getting appear completely arbitrary. I'm
no ha
On Fri, Nov 17, 2000 at 11:26:02AM -0700, Warner Losh wrote:
> 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
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 rep
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 ar
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 i
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 a
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
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.
>
> T
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 p
It seems Michael C . Wu wrote:
> I had those problems too a while ago on a UP p3-650 laptop. Finally I just
> newfs'ed the machine and installed the 20001028 snapshot, then cvsupp'ed
> to 20001122. The laptop now works well. What I saw was processes
> forking and forking again until the machine
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 co
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 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 i
* 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, an
> 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
ot;Valentin Chopov" <[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
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 abo
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
It seems Valentin Chopov wrote:
> Hi,
>
> 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 problems s
34 matches
Mail list logo
