Hi,
I just patched my kernel and here are my results:
> systems. Please apply and give me the "IRQ to pin mappings:" part of the
> bootstrap log. I'm pretty confident we get everything fine there, but
> just in case...
0000
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4
Dans son message du Thu 23 November, Maciej W. Rozycki ecrit :
> Hmm, your BIOS reports the timer IRQ is directly connected...
> > Int: type 0, pol 3, trig 3, bus 2, IRQ 09, APIC ID 2, APIC INT 09
> This is weird for an ISA IRQ.
Remember that I have TWO PCI buses and one ISA Bus.
>
> > ENABLI
Dans son message du Tue 21 November, Maciej W. Rozycki ecrit :
> But this message is printed when a workaround for certain early SMP EISA
> boards gets activated. You shouldn't normally get it for anything newer
> than P5/66 unless your MP-table is broken. Can you send me a dump of your
> MP-t
On Tue, 21 Nov 2000, Benjamin Monate About the 8254, the kernel log contains :
>
> Nov 20 17:15:15 pc8-118 kernel: MP-BIOS bug: 8254 timer
> not connected to IO-AP
> IC
> Nov 20 17:15:15 pc8-118 kernel: ...trying to set up timer (IRQ0)
>
> I guess not -- the timer interrupt and the NMI use different I/O APIC
> inputs. If both are stuck, it's probably 8254 that gets reprogrammed. I
> suppose XFree86 might be at fault -- does it happen with the NMI watchdog
> disabled, either?
Yes. I just enabled the nmi watchdog to try to debug
On Mon, 20 Nov 2000, Alan Cox wrote:
> > a lock of the PCI bus (as SCSI and NIC are still working). Only the
> > timer interrupts and NMI seem to be stuck : can a driver cause
> > something so "lowlevel" ?
>
> Something stopping the timers on the APIC I guess. But quite what or how I
> don't kno
> a lock of the PCI bus (as SCSI and NIC are still working). Only the
> timer interrupts and NMI seem to be stuck : can a driver cause
> something so "lowlevel" ?
Something stopping the timers on the APIC I guess. But quite what or how I
don't know
-
To unsubscribe from this list: send the line
Dans son message du Mon 20 November, Fort David ecrit :
> > Further investigations showed that the problem will occur only when
> > Xfree 4.0.1 is running with an smp kenel . Xfree 3.3.6 is ok. Could this
> > be a bug in X ? I thought that the kernel should prevent such a bug
> > from locking th
"Benjamin Monate
> In his message of Sat 18 November, Andrew Morton writes :
> > Try booting with the `noapic' option. Looks like your APIC
> > is getting itself unprogrammed. Check that you're not
> > overclocked and not over temperature.
>
> Booting with noapic did not improve anything.
> The
In his message of Sat 18 November, Andrew Morton writes :
> Try booting with the `noapic' option. Looks like your APIC
> is getting itself unprogrammed. Check that you're not
> overclocked and not over temperature.
Booting with noapic did not improve anything.
The processor is not supposed to
10 matches
Mail list logo
