Re: 2.6.10-rc2-bk7, back to an irq 12 "nobody cared!"

From: Gene Heskett
Date: Tue Nov 23 2004 - 17:48:48 EST


On Tuesday 23 November 2004 15:30, Gene Heskett wrote:

Here I go again, replying to my own post, with new info

>On Tuesday 23 November 2004 14:39, Chris Wright wrote:
>>* Zwane Mwaikambo (zwane@xxxxxxxxxxxxx) wrote:
>>> On Mon, 22 Nov 2004, Andrew Morton wrote:
>>> > Gene Heskett <gene.heskett@xxxxxxxxxxx> wrote:
>>> > > Just built bk7 after running the bk4-kjt1 version for a
>>> > > cpouple of days, and noticed this in /var/log/dmesg:
>>
>>Try current, should be fixed.
>>
>>thanks,
>>-chris
>
>Current, as in bk8? Or have the janitors a new one? In which case a
>url please. :-)

Ok, I've built and rebooted to 2.6.10-rc2-bk8, but the magic
invocation on the kernel command line doesn't seem to have any
effect. THat was to append the string

acpi_skip_timer_override

to that line in grub.conf.

A cat of proc/interrupts shows many shared irq's again.
root@coyote linux-2.6.10-rc2-bk8]# cat /proc/interrupts
CPU0
0: 247857 XT-PIC timer
1: 862 XT-PIC i8042
2: 0 XT-PIC cascade
3: 20 XT-PIC serial
4: 993 XT-PIC serial
5: 3238 XT-PIC ehci_hcd, radeon@pci:0000:02:00.0
7: 226 XT-PIC parport0
8: 2 XT-PIC rtc
9: 0 XT-PIC acpi
11: 22798 XT-PIC ohci_hcd, eth0, Bt87x audio
12: 806 XT-PIC ohci_hcd, NVidia nForce2
14: 10864 XT-PIC ide0
15: 2574 XT-PIC ide1
NMI: 0
LOC: 247790
ERR: 44

And, while the rest of the counters are incrementing as expected, the
ERR: seems to be stuck at 44. I assume thats good that its not
incrementing (now) but 2.6.10-rc2 has it as a 0 for extended periods
of time.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.29% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/