All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG]  linux-next: Tree for March 25 kernel oops, when loading mpt fusion driver - regression
Date: Fri, 27 Jun 2008 09:26:37 -0500	[thread overview]
Message-ID: <20080627142637.GB13664@redhat.com> (raw)

On Wed, Mar 26, 2008 at 12:14:00PM +0530, Kamalesh Babulal wrote:
> Hi Stephen,
> 
> Kernel bug is hit while booting up the next-20080325 kernel with MPT
> Fusion driver built in.This was reported previously for the
> next-20080320 kernel
> http://marc.info/?l=linux-next&m=120601013920868&w=2

Hi, did you ever get this fixed?  I have the same problem every time I
try to boot any 2.6.26-rc kernel.
http://marc.info/?l=linux-scsi&m=121061780821823&w=4


Loading scsi_transport_spi.ko module
Loading mptscsih.ko module
Loading mptspi.ko module
Fusion MPT SPI Host driver 3.04.06
ACPI: PCI Interrupt 0000:86:01.0[A] -> GSI 32 (level, low) -> IRQ 32
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B2: Capabilities={Initiator,Target}
mptbase: ioc0: PCI-MSI enabled
mptbase: ioc0: Initiating recovery
BUG: unable to handle kernel NULL pointer dereference at 0000000000000948
IP: [<ffffffffa00e5e28>] :mptspi:mptspi_dv_renegotiate_work+0x13/0xc3
PGD 7e981067 PUD 7e982067 PMD 0
Oops: 0000 [1] SMP
CPU 1
Modules linked in: mptspi(+) mptscsih scsi_transport_spi mptbase sd_mod
scsi_mod
 ext3 jbd ehci_hcd ohci_hcd uhci_hcd
Pid: 16, comm: events/1 Not tainted 2.6.26-rc8 #2
RIP: 0010:[<ffffffffa00e5e28>]  [<ffffffffa00e5e28>]
:mptspi:mptspi_dv_renegotia
te_work+0x13/0xc3
RSP: 0000:ffff81007f479e50  EFLAGS: 00010286
RAX: ffffffff802429f7 RBX: ffff81007f479e90 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff81007f424138
RBP: ffff81007f479e80 R08: 0000000000000002 R09: 0000000000000000
R10: ffffffff802429f7 R11: ffff81007ffddde0 R12: ffff81007ffbcd90
R13: 0000000000000948 R14: ffffffffa00e5e15 R15: 0000000000000000
FS:  0000000000680850(0000) GS:ffff81007ff5fbe8(0000)
knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000948 CR3: 000000007e979000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process events/1 (pid: 16, threadinfo ffff81007f478000, task
ffff81007f476480)
Stack:  ffffffffa00e5e15 0000000000000000 ffff81007f479e90
ffff81007ffbcd90
 ffff81007f424138 ffffffffa00e5e15 ffff81007f479ed0 ffffffff80242a46
 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a
Call Trace:
 [<ffffffffa00e5e15>] ? :mptspi:mptspi_dv_renegotiate_work+0x0/0xc3
 [<ffffffffa00e5e15>] ? :mptspi:mptspi_dv_renegotiate_work+0x0/0xc3
 [<ffffffff80242a46>] run_workqueue+0xee/0x1f6
 [<ffffffff802435d3>] worker_thread+0xdb/0xe8
 [<ffffffff80246254>] ? autoremove_wake_function+0x0/0x38
 [<ffffffff802434f8>] ? worker_thread+0x0/0xe8
 [<ffffffff80246131>] kthread+0x49/0x78
 [<ffffffff8020cd98>] child_rip+0xa/0x12
 [<ffffffff80245fac>] ? kthreadd+0x1a6/0x1cb
 [<ffffffff802460e8>] ? kthread+0x0/0x78
 [<ffffffff8020cd8e>] ? child_rip+0x0/0x12


Code: 8b bc 24 f8 00 00 00 e8 83 f7 ff ff 5a 5b 41 5c 41 5d 41 5e 41 5f c9
c3 55
 48 89 e5 41 56 41 55 41 54 53 48 83 ec 10 4c 8b 6f 40 <4d> 8b 75 00 e8 6a
9e 1a
 e0 66 41 83 bd fa 02 00 00 00 49 8b be
RIP  [<ffffffffa00e5e28>] :mptspi:mptspi_dv_renegotiate_work+0x13/0xc3
 RSP <ffff81007f479e50>
CR2: 0000000000000948
---[ end trace 9714d7078ea4157a ]---


> Loading mptscsih.ko module
> Loading mptspi.ko module
> [    6.591066] Fusion MPT SPI Host driver 3.04.06
> [    6.592181] ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 22
> [    6.593991] mptbase: ioc0: Initiating bringup
> [    6.718342] ioc0: LSI53C1030 B2: Capabilities={Initiator}
> [    6.722484] mptbase: ioc0: PCI-MSI enabled
> [   16.902699] mptbase: ioc0: Initiating recovery
> [   16.903618] mptbase: ioc0: WARNING - IOC is in FAULT state!!!
> [   16.904618] mptbase: ioc0: WARNING -            FAULT code = 8112h
> [   21.909082] mptbase: ioc0: ERROR - Doorbell ACK timeout (count=4999), IntStatus=80000009!
> [   39.152711] mptbase: ioc0: Recovered from IOC FAULT
> [   61.630538] BUG: unable to handle kernel NULL pointer dereference at 00000528
> [   61.632545] IP: [<f881ccc9>] :mptspi:mptspi_dv_renegotiate_work+0xc/0xab
> [   61.634545] *pde = 00000000 
> [   61.636219] Oops: 0000 [#1] SMP 
> [   61.636537] last sysfs file: /sys/block/ram15/dev
> [   61.636537] Modules linked in: mptspi(+) mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd
> [   61.636537] 
> [   61.636537] Pid: 17, comm: events/2 Not tainted (2.6.25-rc6-next-20080325-autotest #1)
> [   61.636537] EIP: 0060:[<f881ccc9>] EFLAGS: 00010282 CPU: 2
> [   61.636537] EIP is at mptspi_dv_renegotiate_work+0xc/0xab [mptspi]
> [   61.636537] EAX: f79e5868 EBX: f79e586c ECX: f78c308c EDX: 00000001
> [   61.636537] ESI: f7867e38 EDI: 00000528 EBP: f78a2f78 ESP: f78a2f58
> [   61.636537]  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> [   61.636537] Process events/2 (pid: 17, ti=f78a2000 task=f78c29a0 task.ti=f78a2000)
> [   61.636537] Stack: 00000000 00000002 00000000 c0430b45 f78a2f90 f79e586c f7867e38 f79e5868 
> [   61.636537]        f78a2fac c0430b80 00000000 00000002 c0430b45 f881ccbd f8821588 c08ee870 
> [   61.636537]        f881d870 00000002 f7867e38 c043140a f7867e60 f78a2fd0 c04314be 00000000 
> [   61.636537] Call Trace:
> [   61.636537]  [<c0430b45>] run_workqueue+0x80/0x186
> [   61.636537]  [<c0430b80>] run_workqueue+0xbb/0x186
> [   61.636537]  [<c0430b45>] run_workqueue+0x80/0x186
> [   61.636537]  [<f881ccbd>] mptspi_dv_renegotiate_work+0x0/0xab [mptspi]
> [   61.636537]  [<c043140a>] worker_thread+0x0/0xbf
> [   61.636537]  [<c04314be>] worker_thread+0xb4/0xbf
> [   61.636537]  [<c043393d>] autoremove_wake_function+0x0/0x33
> [   61.636537]  [<c043387b>] kthread+0x3b/0x64
> [   61.636537]  [<c0433840>] kthread+0x0/0x64
> [   61.636537]  [<c040468f>] kernel_thread_helper+0x7/0x10
> [   61.636537]  =======================
> [   61.636537] Code: ff 8b 87 8c 00 00 00 e8 b0 6c 03 00 8b 87 8c 00 00 00 e8 6e f8 ff ff 8d 65 f4 5b 5e 5f 5d c3 55 89 e5 57 56 53 83 ec 14 8b 78 20 <8b> 17 89 55 e0 e8 87 2a c5 c7 8b 55 e0 66 83 bf b2 02 00 00 00 
> [   61.636537] EIP: [<f881ccc9>] mptspi_dv_renegotiate_work+0xc/0xab [mptspi] SS:ESP 0068:f78a2f58
> [   61.636550] ---[ end trace c0dc9c06e06bc602 ]---


             reply	other threads:[~2008-06-27 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 14:26 David Teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-25  6:52 linux-next: Tree for March 25 Stephen Rothwell
2008-03-26  6:44 ` [BUG] linux-next: Tree for March 25 kernel oops, when loading mpt fusion driver - regression Kamalesh Babulal
2008-06-26 20:38   ` David Teigland
2008-06-27 17:42     ` Kamalesh Babulal
2008-07-06 19:23     ` James Bottomley
2008-07-07 15:27       ` David Teigland
2008-07-07 15:43         ` James Bottomley
2008-07-10 15:51           ` David Teigland
2008-07-07 20:17       ` Kamalesh Babulal
2008-07-07 20:25         ` James Bottomley
2008-07-08 10:48           ` Kamalesh Babulal

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=20080627142637.GB13664@redhat.com \
    --to=teigland@redhat.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@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.