From: Linus Torvalds <torvalds@linux-foundation.org>
To: Chris Clayton <chris2553@googlemail.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
NeilBrown <neilb@suse.de>,
linux-kernel@vger.kernel.org,
James Bottomley <james.bottomley@hansenpartnership.com>,
scsi <linux-scsi@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: 2.6.30-rc8 Oops whilst booting
Date: Mon, 8 Jun 2009 09:21:04 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906080916130.6847@localhost.localdomain> (raw)
In-Reply-To: <c6b1100b0906080553o2aa77a40pe0077b1b10a7d88a@mail.gmail.com>
On Mon, 8 Jun 2009, Chris Clayton wrote:
>
> OK. I reversed that change and built and installed the kernel. It has
> withstood 100 reboots without a panic. Additionally, I pulled the
> latest changes (that will be rc8-git5, I think) from kernel.org,
> reversed the change to that kernel and built and installed it. That
> too withstood 100 reboots without a panic.
>
> Let me know if there's anything else I can do to help fix this.
That's already pretty convincing.
James, Arjan? The original oops message is here (a jpg screen capture,
unable to open initial console):
http://lkml.org/lkml/2009/6/6/142
and it's this bug entry:
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13474
Subject : Oops whilst booting
Submitter : Chris Clayton <chris2553@googlemail.com>
Date : 2009-06-06 18:59 (2 days old)
References : http://marc.info/?l=linux-kernel&m=124431487924254&w=4
and now bisected down to
>> commit d5a877e8dd409d8c702986d06485c374b705d340
>> Author: James Bottomley <James.Bottomley@HansenPartnership.com>
>> Date: Sun May 24 13:03:43 2009 -0700
>>
>> async: make sure independent async domains can't accidentally entangle
please advice. Otherwise I'll have to revert.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Chris Clayton <chris2553@googlemail.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
NeilBrown <neilb@suse.de>,
linux-kernel@vger.kernel.org,
James Bottomley <james.bottomley@hansenpartnership.com>,
scsi <linux-scsi@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: 2.6.30-rc8 Oops whilst booting
Date: Mon, 8 Jun 2009 09:21:04 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906080916130.6847@localhost.localdomain> (raw)
In-Reply-To: <c6b1100b0906080553o2aa77a40pe0077b1b10a7d88a@mail.gmail.com>
On Mon, 8 Jun 2009, Chris Clayton wrote:
>
> OK. I reversed that change and built and installed the kernel. It has
> withstood 100 reboots without a panic. Additionally, I pulled the
> latest changes (that will be rc8-git5, I think) from kernel.org,
> reversed the change to that kernel and built and installed it. That
> too withstood 100 reboots without a panic.
>
> Let me know if there's anything else I can do to help fix this.
That's already pretty convincing.
James, Arjan? The original oops message is here (a jpg screen capture,
unable to open initial console):
http://lkml.org/lkml/2009/6/6/142
and it's this bug entry:
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13474
Subject : Oops whilst booting
Submitter : Chris Clayton <chris2553@googlemail.com>
Date : 2009-06-06 18:59 (2 days old)
References : http://marc.info/?l=linux-kernel&m=124431487924254&w=4
and now bisected down to
>> commit d5a877e8dd409d8c702986d06485c374b705d340
>> Author: James Bottomley <James.Bottomley@HansenPartnership.com>
>> Date: Sun May 24 13:03:43 2009 -0700
>>
>> async: make sure independent async domains can't accidentally entangle
please advice. Otherwise I'll have to revert.
Linus
next prev parent reply other threads:[~2009-06-08 16:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 18:59 2.6.30-rc8 Oops whilst booting Chris Clayton
2009-06-06 21:15 ` Chris Clayton
2009-06-07 13:25 ` Jaswinder Singh Rajput
2009-06-07 18:38 ` Chris Clayton
2009-06-07 22:31 ` Jaswinder Singh Rajput
2009-06-07 22:55 ` NeilBrown
2009-06-08 8:08 ` Chris Clayton
2009-06-08 8:08 ` Chris Clayton
2009-06-08 10:58 ` Chris Clayton
2009-06-08 10:58 ` Chris Clayton
2009-06-08 11:34 ` Jaswinder Singh Rajput
2009-06-08 12:53 ` Chris Clayton
2009-06-08 12:53 ` Chris Clayton
2009-06-08 16:21 ` Linus Torvalds [this message]
2009-06-08 16:21 ` Linus Torvalds
2009-06-08 16:51 ` James Bottomley
2009-06-08 17:06 ` Jaswinder Singh Rajput
2009-06-08 17:45 ` Chris Clayton
2009-06-08 17:45 ` Chris Clayton
2009-06-08 18:21 ` Linus Torvalds
2009-06-08 19:17 ` Chris Clayton
2009-06-08 19:17 ` Chris Clayton
2009-06-08 20:03 ` Chris Clayton
2009-06-08 20:03 ` Chris Clayton
2009-06-08 17:21 ` Linus Torvalds
2009-06-08 17:37 ` Arjan van de Ven
2009-06-08 17:38 ` James Bottomley
2009-06-08 17:06 ` James Bottomley
2009-06-08 17:42 ` Linus Torvalds
2009-06-08 17:49 ` James Bottomley
2009-06-08 18:33 ` Chris Clayton
2009-06-08 18:33 ` Chris Clayton
2009-06-08 14:23 ` James Bottomley
2009-06-08 15:04 ` Chris Clayton
2009-06-08 15:04 ` Chris Clayton
2009-06-08 15:17 ` Chris Clayton
2009-06-08 15:17 ` Chris Clayton
2009-06-08 15:32 ` James Bottomley
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=alpine.LFD.2.01.0906080916130.6847@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=chris2553@googlemail.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tj@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.