From: Patrick Mansfield <patmans@us.ibm.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>, linux-scsi@vger.kernel.org
Subject: still BUG's for smp_processor_id() on interrupt
Date: Tue, 8 Feb 2005 17:09:29 -0800 [thread overview]
Message-ID: <20050209010929.GA2933@us.ibm.com> (raw)
Hi Andrew -
I'm still getting lots of BUG's for the smp_processor_id, but via the
interrupt function.
I am running the latest bk, it has your patch to qla_os.c:
[elm3b79 qla2xxx]$ grep smp_proc qla_os.c
if (_smp_processor_id() == ha->last_irq_cpu || was_empty)
I'm running on a NUMAQ (sometimes has funky latencies). There are no
errors for simple IO (dd if=/dev/sda of=/dev/null bs=64k). There are about
40 disk drives attached.
More information available on request ...
elm3b79.beaverton.ibm.com login: QLogic Fibre Channel HBA Driver
qla2300 0000:01:0c.0: Found an ISP2300, irq 40, iobase 0xf888a000
qla2300 0000:01:0c.0: Configuring PCI space...
qla2300 0000:01:0c.0: Configure NVRAM parameters...
qla2300 0000:01:0c.0: Verifying loaded RISC code...
BUG: using smp_processor_id() in preemptible [00000001] code: modprobe/1362
caller is qla2300_intr_handler+0x184/0x204 [qla2xxx]
[<c01aea79>] smp_processor_id+0x99/0xb8
[<f88c0294>] qla2300_intr_handler+0x184/0x204 [qla2xxx]
[<f88be39a>] qla2x00_mailbox_command+0x246/0x444 [qla2xxx]
[<c0128487>] autoremove_wake_function+0x1b/0x40
[<f88beb05>] qla2x00_mbx_reg_test+0x5d/0xa0 [qla2xxx]
[<c01161e1>] release_console_sem+0xa9/0xb4
[<c01ae350>] __delay+0x10/0x14
[<f88bae73>] qla2x00_chip_diag+0x23b/0x29c [qla2xxx]
[<f88ba5c8>] gcc2_compiled.+0x108/0x22c [qla2xxx]
[<f88b76aa>] qla2x00_probe_one+0x42e/0x874 [qla2xxx]
[<f88d0012>] gcc2_compiled.+0x12/0x18 [qla2300]
[<c01b2424>] pci_device_probe_static+0x2c/0x40
[<c01b2457>] __pci_device_probe+0x1f/0x34
[<c01b2488>] pci_device_probe+0x1c/0x34
[<c01d918d>] driver_probe_device+0x41/0x64
[<c01d9260>] driver_attach+0x34/0x68
[<c01d96bb>] bus_add_driver+0x8b/0xbc
[<c01d9c08>] driver_register+0x50/0x54
[<c01b2686>] pci_register_driver+0x86/0xa0
[<f888800a>] qla2300_init+0xa/0x10 [qla2300]
[<c012c479>] sys_init_module+0x111/0x270
[<c0102443>] syscall_call+0x7/0xb
BUG: using smp_processor_id() in preemptible [00000001] code: modprobe/1362
...
-- Patrick Mansfield
next reply other threads:[~2005-02-09 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 1:09 Patrick Mansfield [this message]
2005-02-09 6:44 ` still BUG's for smp_processor_id() on interrupt Andrew Vasquez
2005-02-09 17:22 ` Patrick Mansfield
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 18:13 James.Smart
2005-02-09 18:26 ` Patrick Mansfield
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=20050209010929.GA2933@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
/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.