From: Andrew Morton <akpm@osdl.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: ak@muc.de, ashok.raj@intel.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: 2.6.13-rc5-mm1 doesnt boot on x86_64
Date: Mon, 8 Aug 2005 10:42:06 -0700 [thread overview]
Message-ID: <20050808104206.42a51477.akpm@osdl.org> (raw)
In-Reply-To: <1123522409.5019.0.camel@mulgrave>
James Bottomley <James.Bottomley@SteelEye.com> wrote:
>
> On Mon, 2005-08-08 at 19:11 +0200, Andi Kleen wrote:
> > Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?
>
> The traceback looks pretty meaningless.
>
> What was happening on the machine before this. i.e. was it booting up,
> in which case can we have the prior dmesg file; or was the aic79xxx
> driver being removed?
>
-mm has extra list_head debugging goodies. I'd be suspecting a list_head
corruption detected somewhere under spi_release_transport().
--- 25/include/linux/list.h~list_del-debug 2005-03-08 11:40:27.000000000 -0800
+++ 25-akpm/include/linux/list.h 2005-03-08 11:40:49.000000000 -0800
@@ -5,7 +5,9 @@
#include <linux/stddef.h>
#include <linux/prefetch.h>
+#include <linux/kernel.h>
#include <asm/system.h>
+#include <asm/bug.h>
/*
* These are non-NULL pointers that will result in page faults
@@ -160,6 +162,8 @@ static inline void __list_del(struct lis
*/
static inline void list_del(struct list_head *entry)
{
+ BUG_ON(entry->prev->next != entry);
+ BUG_ON(entry->next->prev != entry);
__list_del(entry->prev, entry->next);
entry->next = LIST_POISON1;
entry->prev = LIST_POISON2;
_
next prev parent reply other threads:[~2005-08-08 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050808094818.A17579@unix-os.sc.intel.com>
2005-08-08 17:11 ` 2.6.13-rc5-mm1 doesnt boot on x86_64 Andi Kleen
2005-08-08 17:27 ` Ashok Raj
2005-08-08 17:33 ` James Bottomley
2005-08-08 17:39 ` Ashok Raj
2005-08-08 17:42 ` Andrew Morton [this message]
2005-08-09 0:06 ` James Bottomley
2005-08-09 18:12 ` Ashok Raj
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=20050808104206.42a51477.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=James.Bottomley@SteelEye.com \
--cc=ak@muc.de \
--cc=ashok.raj@intel.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