Bug#366507: #366507

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#366507: #366507

Bastian Blank
tags 366507 moreinfo
thanks

The kernel clearly stats that it misses the interrupt routings for pin A
and pin B which are used by the cardbus bridge.

| PCI: No IRQ known for interrupt pin A of device 0000:00:13.0. Please try
| using pci=biosirq.
| PCI: Setting latency timer of device 0000:00:13.0 to 64
| PCI: No IRQ known for interrupt pin B of device 0000:00:13.1. Please try
| using pci=biosirq.
| PCI: Setting latency timer of device 0000:00:13.1 to 64

Please retest, if possible, with 2.6.18/2.6.21.

Bastian

--
No more blah, blah, blah!
                -- Kirk, "Miri", stardate 2713.6


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#366507: #366507

tnemeth (Bugzilla)
D'apr├Ęs Bastian Blank <[hidden email]> :

> tags 366507 moreinfo
> thanks
>
> The kernel clearly stats that it misses the interrupt routings for pin A
> and pin B which are used by the cardbus bridge.

     Yes.


> | PCI: No IRQ known for interrupt pin A of device 0000:00:13.0. Please try
> | using pci=biosirq.
> | PCI: Setting latency timer of device 0000:00:13.0 to 64
> | PCI: No IRQ known for interrupt pin B of device 0000:00:13.1. Please try
> | using pci=biosirq.
> | PCI: Setting latency timer of device 0000:00:13.1 to 64
>
> Please retest, if possible, with 2.6.18/2.6.21.

     Already done with the 2.6.18 since a long time. I even created an
     upstream bug report (see http://bugzilla.kernel.org/show_bug.cgi?id=7304
     you'll have a more complete feedback).
     I'll try to test 2.6.21 if it's on testing now, but not sure when I
     can find time.

     Thanks for all.


Thomas.

Reply | Threaded
Open this post in threaded view
|

Bug#366507: #366507

Maximilian Attems-3
On Thu, Jul 05, 2007 at 10:34:03AM +0200, Thomas Nemeth wrote:
>
>     Already done with the 2.6.18 since a long time. I even created an
>     upstream bug report (see http://bugzilla.kernel.org/show_bug.cgi?id=7304
>     you'll have a more complete feedback).
>     I'll try to test 2.6.21 if it's on testing now, but not sure when I
>     can find time.
>
>     Thanks for all.

there are 2.6.22-rc7 builds available, see trunk apt lines on
http://wiki.debian.org/DebianKernel
that's the latest and best to test against.

regards

--
maks


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]