public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: linux-kernel@vger.kernel.org, Steve Fox <drfickle@us.ibm.com>,
	"Moore, Eric Dean" <Eric.Moore@lsil.com>,
	linux-scsi@vger.kernel.org
Subject: Re: 2.6.18-mm1
Date: Wed, 27 Sep 2006 09:12:33 -0700	[thread overview]
Message-ID: <20060927091233.dbb006f0.akpm@osdl.org> (raw)
In-Reply-To: <451A4394.7000504@shadowen.org>

On Wed, 27 Sep 2006 10:25:40 +0100
Andy Whitcroft <apw@shadowen.org> wrote:

> Ok.  Now that we've got past the linker changes breaking down under
> older tool chains I am getting following panic on boot.  The machine has
> one of these, other machines do seem to boot:
> 
> 0000:02:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030
> PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07)
> 
> It appears that this driver is unchanged between 2.6.18 and -mm1.
> 2.6.18 boots just fine.  Odd.
> 
> Any suggestions?
> 
> -apw
> 
> mptbase: Initiating ioc0 bringup
> ioc0: 53C1030: Capabilities={Initiator}
> mptbase: Initiating ioc0 recovery
> Unable to handle kernel NULL pointer dereference at 0000000000000500 RIP:
>  [<ffffffff803fadfb>] mptspi_dv_renegotiate_work+0x10/0x4a
> PGD 0
> Oops: 0000 [1] SMP
> last sysfs file:
> CPU 0
> Modules linked in:
> Pid: 14, comm: events/0 Not tainted 2.6.18-mm1-autokern1 #1
> RIP: 0010:[<ffffffff803fadfb>]  [<ffffffff803fadfb>]
> mptspi_dv_renegotiate_work+0x10/0x4a
> RSP: 0000:ffff8101000e1e20  EFLAGS: 00010282
> RAX: 0000000000000001 RBX: ffff810001fe6940 RCX: 000000000000001f
> RDX: 0000000000000000 RSI: ffff810001fe6940 RDI: 0000000000001fe6
> RBP: ffff8101000e1e30 R08: ffff8101000e0000 R09: 0000000000000011
> R10: ffff810001014820 R11: ffff810001014820 R12: 0000000000000500
> R13: ffff810001ef1640 R14: 0000000000000206 R15: ffff810001fe6940
> FS:  0000000000000000(0000) GS:ffffffff80582000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 0000000000000500 CR3: 0000000000201000 CR4: 00000000000006e0
> Process events/0 (pid: 14, threadinfo ffff8101000e0000, task
> ffff8100816b1040)
> Stack:  ffff810001fe6940 ffff810001fe6948 ffff8101000e1e70 ffffffff80239163
>  ffffffff803fadeb ffff810001ef1640 ffff810001f0dd40 ffffffff802391a7
>  00000000fffffffc ffffffff804b08d4 ffff8101000e1f00 ffffffff8023929a
> Call Trace:
>  [<ffffffff80239163>] run_workqueue+0xa2/0xe6
>  [<ffffffff803fadeb>] mptspi_dv_renegotiate_work+0x0/0x4a
>  [<ffffffff802391a7>] worker_thread+0x0/0x126
>  [<ffffffff8023929a>] worker_thread+0xf3/0x126
>  [<ffffffff80224de3>] default_wake_function+0x0/0xf
>  [<ffffffff80224de3>] default_wake_function+0x0/0xf
>  [<ffffffff802391a7>] worker_thread+0x0/0x126
>  [<ffffffff8023c304>] kthread+0xd0/0xfc
>  [<ffffffff8020a658>] child_rip+0xa/0x12
>  [<ffffffff8023c234>] kthread+0x0/0xfc
>  [<ffffffff8020a64e>] child_rip+0x0/0x12
> 
> 
> Code: 49 8b 04 24 31 f6 48 8b b8 48 01 00 00 e8 5f 8f fe ff 48 85
> RIP  [<ffffffff803fadfb>] mptspi_dv_renegotiate_work+0x10/0x4a
>  RSP <ffff8101000e1e20>
> CR2: 0000000000000500

There are mpt-fusion changes in 2.6.18-mm1, but afaict they're in mainline
now.  Do you know if current -linus works OK?

  reply	other threads:[~2006-09-27 16:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-24 11:02 2.6.18-mm1 Andrew Morton
2006-09-24 12:46 ` 2.6.18-mm1 Russell King
2006-09-24 13:11   ` 2.6.18-mm1 Russell King
2006-09-24 13:22   ` 2.6.18-mm1 Petr Baudis
2006-09-24 14:20     ` 2.6.18-mm1 Russell King
2006-09-24 14:29       ` 2.6.18-mm1 Petr Baudis
2006-09-24 14:47         ` 2.6.18-mm1 Russell King
2006-09-24 16:55           ` 2.6.18-mm1 Petr Baudis
2006-09-24 18:48           ` 2.6.18-mm1 Junio C Hamano
2006-09-24 21:34             ` 2.6.18-mm1 Russell King
2006-09-24 21:56               ` 2.6.18-mm1 Andrew Morton
2006-09-24 22:07               ` 2.6.18-mm1 Junio C Hamano
2006-09-24 16:35 ` 2.6.18-mm1 Dmitry Torokhov
2006-09-24 17:06   ` 2.6.18-mm1 Andrew Morton
2006-09-27  2:04 ` 2.6.18-mm1 Eric W. Biederman
2006-09-27  3:11   ` 2.6.18-mm1 Andrew Morton
2006-09-27  5:12     ` 2.6.18-mm1 Eric W. Biederman
2006-09-27  5:44       ` 2.6.18-mm1 Aaron Durbin
2006-09-27  6:20         ` 2.6.18-mm1 Eric W. Biederman
2006-09-27  7:13   ` 2.6.18-mm1 Andi Kleen
2006-09-27  7:39     ` 2.6.18-mm1 Eric W. Biederman
2006-09-27  7:51       ` 2.6.18-mm1 Andi Kleen
2006-09-27 14:08         ` 2.6.18-mm1 Eric W. Biederman
2006-09-27 22:06           ` 2.6.18-mm1 Aaron Durbin
2006-09-27 23:06             ` 2.6.18-mm1 Andrew Morton
2006-09-27  9:25 ` 2.6.18-mm1 Andy Whitcroft
2006-09-27 16:12   ` Andrew Morton [this message]
2006-09-27 16:50     ` 2.6.18-mm1 Andy Whitcroft

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=20060927091233.dbb006f0.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Eric.Moore@lsil.com \
    --cc=apw@shadowen.org \
    --cc=drfickle@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox