lkml.org 
[lkml]   [2006]   [Nov]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: qstor driver -> irq 193: nobody cared
On Fri, Nov 03, 2006 at 02:22:07PM -0600, Alberto Alonso wrote:
> On Fri, 2006-11-03 at 22:00 +0300, Sergey Vlasov wrote:
> > On Fri, 03 Nov 2006 12:02:53 -0600 Alberto Alonso wrote:
> >
> > > I have a Pacific Digital qstor card on irq 193. I am using kernel
> > > 2.6.17.13 SMP
> > >
> > >
> > > irq 193: nobody cared (try booting with the "irqpoll" option)
> >
> > Did you try this option? It may decrease performance, but in some cases
> > IRQ routing is so screwed that only irqpoll helps.
>
> I have now switched to using that option. Will kick in after I reboot.

Actually, it might be better to wait with this - it is the last resort
option, if there is nothing else to try.

> 0000:00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 04) (prog-if 10 [OHCI])
> Subsystem: ServerWorks OSB4/CSB5 OHCI USB Controller
> Flags: bus master, medium devsel, latency 64, IRQ 10
> Memory at fe9fe000 (32-bit, non-prefetchable) [size=4K]

Can you try with ohci-hcd loaded (and without irqpoll)? USB
controllers might cause such problems, because BIOSen often do weird
things with them for legacy emulation; however, loading a proper
driver should make BIOS stop messing with the hardware behind the back
of the OS.

After loading ohci-hcd look which IRQ does the USB controller use - if
it is the same IRQ as the qstor card, you should keep ohci-hcd loaded
to avoid problems. (If it is on some other IRQ, loading ohci-hcd
might still help - the code for enabling the PCI device calls ACPI
BIOS, which might change interrupt routing setup in the chipset.)

Also look for something like "USB Keyboard Support" and maybe "USB
Mouse Support" in BIOS setup - some BIOS versions have severe problems
with this emulation, so it may be better to disable it unless you
really need it.

Disabling USB in the BIOS setup if you really don't need might be
another option.

> 0000:01:05.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 Ultra3 SCSI Adapter (rev 01)
> Subsystem: Gateway 2000: Unknown device 1040
> Flags: medium devsel
> I/O ports at 1000 [disabled] [size=256]
> Memory at <ignored> (64-bit, non-prefetchable) [disabled]
> Memory at <ignored> (64-bit, non-prefetchable) [disabled]
> Capabilities: [40] Power Management version 2
>
> 0000:01:05.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 Ultra3 SCSI Adapter (rev 01)
> Subsystem: Gateway 2000: Unknown device 1040
> Flags: medium devsel
> I/O ports at 1400 [disabled] [size=256]
> Memory at <ignored> (64-bit, non-prefetchable) [disabled]
> Memory at <ignored> (64-bit, non-prefetchable) [disabled]
> Capabilities: [40] Power Management version 2

These devices seem to be disabled, but if loading ohci-hcd does not
help, you can try to load the sym53c8xx driver and look whether it
ends up on the same IRQ as qstor.
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2006-11-03 21:55    [W:0.105 / U:0.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site