Ben Smithurst wrote:
> Bruce Evans wrote:
>
> > On Sat, 9 Sep 2000, Ben Smithurst wrote:
> >
> >> After poking around a bit with remote GDB, this seems to be caused by a
> >> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM.
> >>
> >> The attached rather crude patch has "f
Bruce Evans wrote:
> On Sat, 9 Sep 2000, Ben Smithurst wrote:
>
>> After poking around a bit with remote GDB, this seems to be caused by a
>> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM.
>>
>> The attached rather crude patch has "fixed" the problem for now, but
>> doe
On Mon, 11 Sep 2000, Greg Lehey wrote:
> On Monday, 11 September 2000 at 17:44:43 +1100, Bruce Evans wrote:
> > On Mon, 11 Sep 2000, Greg Lehey wrote:
> >> Independently of that, we need to be able to survive a spurious
> >> interrupt on any IRQ.
> >
> > Not really independent. Spurious interrup
On Monday, 11 September 2000 at 17:44:43 +1100, Bruce Evans wrote:
> On Mon, 11 Sep 2000, Greg Lehey wrote:
>
>> On Monday, 11 September 2000 at 13:18:37 +1100, Bruce Evans wrote:
>>> The stray interrupt handler needs to have a thread, or stray interrupts
>>> need to be handled as traps. Stray in
On Mon, 11 Sep 2000, Greg Lehey wrote:
> On Monday, 11 September 2000 at 13:18:37 +1100, Bruce Evans wrote:
> > The stray interrupt handler needs to have a thread, or stray interrupts
> > need to be handled as traps. Stray interrupts are more like NMIs than
> > normal interrupts, and NMIs are al
On Monday, 11 September 2000 at 13:18:37 +1100, Bruce Evans wrote:
> On Sat, 9 Sep 2000, Ben Smithurst wrote:
>
>> After poking around a bit with remote GDB, this seems to be caused by a
>> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM.
>>
>> The attached rather crude patc
On Sat, 9 Sep 2000, Ben Smithurst wrote:
> After poking around a bit with remote GDB, this seems to be caused by a
> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM.
>
> The attached rather crude patch has "fixed" the problem for now, but
> does anyone have any suggestions
Greg Lehey wrote:
> Sorry, I missed the beginning of this. Could somebody send me the
> patch? I'd assume that a relatively simple check would handle the
> issue, based on what I've seen here.
I've lost the actual patch, I basically just added
if (ir == NULL)
return;
Ben Smithurst wrote:
> Greg Lehey wrote:
>
>> Sorry, I missed the beginning of this. Could somebody send me the
>> patch? I'd assume that a relatively simple check would handle the
>> issue, based on what I've seen here.
>
> I've lost the actual patch, I basically just added
>
> if (ir
On Sunday, 10 September 2000 at 0:23:15 -0500, Mike Meyer wrote:
> Ben Smithurst writes:
>> After poking around a bit with remote GDB, this seems to be caused by a
>> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM.
>>
>> The attached rather crude patch has "fixed" the prob
Bosko Milekic wrote:
>I catch this page fault (described in topic) following an:
>
>`ifconfig de0 down'
>
>Unfortunately, I don't have much more information to provide for now.
>I'm in the middle of debugging something else. More info can be provided
>on request (let me know
I catch this page fault (described in topic) following an:
`ifconfig de0 down'
Unfortunately, I don't have much more information to provide for now.
I'm in the middle of debugging something else. More info can be provided
on request (let me know if you want to look at it and can
Ben Smithurst writes:
> After poking around a bit with remote GDB, this seems to be caused by a
> stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM.
>
> The attached rather crude patch has "fixed" the problem for now, but
> does anyone have any suggestions for a real fix?
Is
Ben Smithurst wrote:
> A kernel from the latest sources gets a page fault in sched_ithd. DDB says:
>
> Stopped at: sched_ithd+0x3c:movl $0x01,0x14(%edi)
>
> Any ideas what's wrong?
After poking around a bit with remote GDB, this seems to be caused by a
stray I
A kernel from the latest sources gets a page fault in sched_ithd. DDB says:
Stopped at: sched_ithd+0x3c:movl $0x01,0x14(%edi)
Any ideas what's wrong?
I'll try to get a serial console working at some point so hopefully I
can get some more useful information.
Here&#x
15 matches
Mail list logo
