GateK33per wrote:

> 1. What is the deal with the impossibly high IRQ number?

It is APIC (!= ACPI ) the few years old feature that is used mainly for
multiprocessor machines, it allows for up to 256 interrupts if computer
hardware has support for it.

> 2. What is the "irqpoll option," and how do I boot with it?

If you have installed kernel sources than in:
/usr/src/linux/Documentation
file
kernel-parameters.txt
has all bout kernel paramateres.
....
irqpoll [HW]
When an interrupt is not handled search all handlers
for it. Also check all handlers each timer
interrupt. Intended to get systems with badly broken
firmware running.
....
Something that might help, but can make more troubles (not sure).
On a first boot screen type
irqpoll
as test solution to see that other stuff will work.
Than if everything works as before put that option in
/boot/grub/menu.lst
and see will that help.

--
Regards,
Rajko.

Rajko M. wrote:
> GateK33per wrote:
>
>> 1. What is the deal with the impossibly high IRQ number?
>
> It is APIC (!= ACPI ) the few years old feature that is used mainly for
> multiprocessor machines, it allows for up to 256 interrupts if computer
> hardware has support for it.
>
>> 2. What is the "irqpoll option," and how do I boot with it?
>
> If you have installed kernel sources than in:
> /usr/src/linux/Documentation
> file
> kernel-parameters.txt
> has all bout kernel paramateres.
> ...
> irqpoll [HW]
> When an interrupt is not handled search all handlers
> for it. Also check all handlers each timer
> interrupt. Intended to get systems with badly broken
> firmware running.
> ...
> Something that might help, but can make more troubles (not sure).
> On a first boot screen type
> irqpoll
> as test solution to see that other stuff will work.
> Than if everything works as before put that option in
> /boot/grub/menu.lst
> and see will that help.
>
I tried the irqpoll option, but it made things worse. The x-server hung
at startup. Do you think there would be any point in disabling APIC? I
do have an AMD 64 x2 processor, so technically this is a multi-processor
machine.

GateKeeper wrote:

> Rajko M. wrote:
>> GateK33per wrote:
>>
>>> 1. What is the deal with the impossibly high IRQ number?
>>
>> It is APIC (!= ACPI ) the few years old feature that is used mainly for
>> multiprocessor machines, it allows for up to 256 interrupts if computer
>> hardware has support for it.
>>
>>> 2. What is the "irqpoll option," and how do I boot with it?
>>
>> If you have installed kernel sources than in:
>> /usr/src/linux/Documentation
>> file
>> kernel-parameters.txt
>> has all bout kernel paramateres.
>> ...
>> irqpoll [HW]
>> When an interrupt is not handled search all handlers
>> for it. Also check all handlers each timer
>> interrupt. Intended to get systems with badly broken
>> firmware running.
>> ...
>> Something that might help, but can make more troubles (not sure).
>> On a first boot screen type
>> irqpoll
>> as test solution to see that other stuff will work.
>> Than if everything works as before put that option in
>> /boot/grub/menu.lst
>> and see will that help.
>>
> I tried the irqpoll option, but it made things worse. The x-server hung
> at startup. Do you think there would be any point in disabling APIC? I
> do have an AMD 64 x2 processor, so technically this is a multi-processor
> machine.

It real multiprocessor machine although both CPUs are in the same chip.

It is cheap to try noapic option.
Enter it the same way as irqpoll and see if it works.
So far I know, the worst that can happen is that computer will not boot.

--
Regards,
Rajko.

Rajko M. wrote:
> GateKeeper wrote:
>
>> Rajko M. wrote:
>>> GateK33per wrote:
>>>
>>>> 1. What is the deal with the impossibly high IRQ number?
>>> It is APIC (!= ACPI ) the few years old feature that is used mainly for
>>> multiprocessor machines, it allows for up to 256 interrupts if computer
>>> hardware has support for it.
>>>
>>>> 2. What is the "irqpoll option," and how do I boot with it?
>>> If you have installed kernel sources than in:
>>> /usr/src/linux/Documentation
>>> file
>>> kernel-parameters.txt
>>> has all bout kernel paramateres.
>>> ...
>>> irqpoll [HW]
>>> When an interrupt is not handled search all handlers
>>> for it. Also check all handlers each timer
>>> interrupt. Intended to get systems with badly broken
>>> firmware running.
>>> ...
>>> Something that might help, but can make more troubles (not sure).
>>> On a first boot screen type
>>> irqpoll
>>> as test solution to see that other stuff will work.
>>> Than if everything works as before put that option in
>>> /boot/grub/menu.lst
>>> and see will that help.
>>>
>> I tried the irqpoll option, but it made things worse. The x-server hung
>> at startup. Do you think there would be any point in disabling APIC? I
>> do have an AMD 64 x2 processor, so technically this is a multi-processor
>> machine.
>
> It real multiprocessor machine although both CPUs are in the same chip.
>
> It is cheap to try noapic option.
> Enter it the same way as irqpoll and see if it works.
> So far I know, the worst that can happen is that computer will not boot.
>
Neither noapic nor irqpoll worked. Noapic had no effect, and irqpoll
made the computer hang at reboot. So I tried UBUNTU. I had the same
problem. Then I rebooted once with irqfixup. That solved the problem.
Don't know if that will work with Suse.

Barry R Ford wrote:

....
>>>>
>>> I tried the irqpoll option, but it made things worse. The x-server hung
>>> at startup. Do you think there would be any point in disabling APIC? I
>>> do have an AMD 64 x2 processor, so technically this is a multi-processor
>>> machine.
>>
>> It is a real multiprocessor machine although both CPUs are in the
>> same chip.
>>
>> It is cheap to try noapic option.
>> Enter it the same way as irqpoll and see if it works.
>> So far I know, the worst that can happen is that computer will not boot.
>>
> Neither noapic nor irqpoll worked. Noapic had no effect, and irqpoll
> made the computer hang at reboot. So I tried UBUNTU. I had the same
> problem. Then I rebooted once with irqfixup. That solved the problem.
> Don't know if that will work with Suse.

Hi Barry,

It is a kernel problem and that is the reason that Ubuntu failed in the same
way. SUSE and Ubuntu use similar kernel versions, so solution for one can
be for the other too.

--
Regards,
Rajko.

Rajko M. wrote:
> Barry R Ford wrote:
>
> ...
>>>> I tried the irqpoll option, but it made things worse. The x-server hung
>>>> at startup. Do you think there would be any point in disabling APIC? I
>>>> do have an AMD 64 x2 processor, so technically this is a multi-processor
>>>> machine.
>>> It is a real multiprocessor machine although both CPUs are in the
>>> same chip.
>>>
>>> It is cheap to try noapic option.
>>> Enter it the same way as irqpoll and see if it works.
>>> So far I know, the worst that can happen is that computer will not boot.
>>>
>> Neither noapic nor irqpoll worked. Noapic had no effect, and irqpoll
>> made the computer hang at reboot. So I tried UBUNTU. I had the same
>> problem. Then I rebooted once with irqfixup. That solved the problem.
>> Don't know if that will work with Suse.
>
> Hi Barry,
>
> It is a kernel problem and that is the reason that Ubuntu failed in the same
> way. SUSE and Ubuntu use similar kernel versions, so solution for one can
> be for the other too.
>
The fix is still working with Ubuntu Feisty 7.04 for x86_64 (AMD64).

Thanks again. I'll be on the Ubuntu newsgroup from now on.