All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alberto Alonso <alberto@ggsys.net>
To: linux-kernel@vger.kernel.org
Cc: mlord@pobox.com
Subject: qstor driver -> irq 193: nobody cared
Date: Fri, 03 Nov 2006 12:02:53 -0600	[thread overview]
Message-ID: <1162576973.3967.10.camel@w100> (raw)

I have a Pacific Digital qstor card on irq 193. I am using kernel
2.6.17.13 SMP

The error happens every now and then. I have not been able to
figure out any triggers and I can not reproduce it on demand. Today
it happened 3 times within a 40 minutes period. 

All disks connected to the card are disabled and I can't do anything
other than a reboot to get them back.

It is reported as follows:

irq 193: nobody cared (try booting with the "irqpoll" option)
 <c013e19a> __report_bad_irq+0x2a/0xa0  <c013d970> handle_IRQ_event
+0x30/0x70
 <c013e2b0> note_interrupt+0x80/0xf0  <c013da8c> __do_IRQ+0xdc/0xf0
 <c0105799> do_IRQ+0x19/0x30  <c010391a> common_interrupt+0x1a/0x20
 <c0100d91> default_idle+0x41/0x70  <c0100e60> cpu_idle+0x80/0x90
 <c046699d> start_kernel+0x18d/0x1d0  <c0466330> unknown_bootoption
+0x0/0x1d0
handlers:
[<c0301300>] (qs_intr+0x0/0x220)
Disabling IRQ #193

The PCI info for the card is:

0000:01:03.0 0106: Pacific Digital Corp: Unknown device 2068 (rev 01)
        Subsystem: Pacific Digital Corp: Unknown device 2068
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 193
        I/O ports at eff0 [size=8]
        I/O ports at efe0 [size=8]
        I/O ports at efa8 [size=8]
        I/O ports at efa0 [size=8]
        Memory at febf0000 (64-bit, non-prefetchable) [size=64K]
        Expansion ROM at febe0000 [disabled] [size=64K]
        Capabilities: [40] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
        Capabilities: [50] Power Management version 2
        Capabilities: [58] PCI-X non-bridge device.


This is really creating problems for me now. If anybody knows
of a dumb (ie. non-raid) PCI SATA card with 8 ports with good
Linux support for a couple hundred backs I would appreciate
it.

If there is any other info that I should provide to help 
troubleshoot please let me know.

Thanks,

Alberto


-- 
Alberto Alonso                        Global Gate Systems LLC.
(512) 351-7233                        http://www.ggsys.net
Hardware, consulting, sysadmin, monitoring and remote backups


             reply	other threads:[~2006-11-03 18:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 18:02 Alberto Alonso [this message]
2006-11-03 19:00 ` qstor driver -> irq 193: nobody cared Sergey Vlasov
2006-11-03 20:22   ` Alberto Alonso
2006-11-03 20:52     ` Sergey Vlasov
2006-11-03 23:21       ` Alberto Alonso
2006-11-04 18:39 ` Mark Lord
2006-11-06  4:04   ` Alberto Alonso
2006-11-06 14:51     ` Mark Lord
2006-11-10 17:36   ` Alberto Alonso
2006-11-12  5:09     ` Mark Lord
2006-11-12  5:17       ` Alberto Alonso
2006-11-12 20:31       ` Alberto Alonso
2006-11-13 14:29         ` Mark Lord
2006-11-14  4:50           ` Alberto Alonso
2006-11-14 16:46             ` Mark Lord
2006-11-14 18:17               ` Alberto Alonso
2006-11-14 18:23                 ` Mark Lord
2006-11-16  6:35                   ` Alberto Alonso
2006-11-16 13:53                     ` Mark Lord
2006-11-17 21:42                       ` Alberto Alonso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1162576973.3967.10.camel@w100 \
    --to=alberto@ggsys.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlord@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.