From: Justin Madru <jdm64@gawab.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.30-rc1: invalid opcode with call trace
Date: Wed, 08 Apr 2009 00:11:54 -0700 [thread overview]
Message-ID: <49DC4E3A.6040809@gawab.com> (raw)
In-Reply-To: <20090408065352.GR5178@kernel.dk>
Jens Axboe wrote:
> On Wed, Apr 08 2009, Ingo Molnar wrote:
>
>> * Ingo Molnar <mingo@elte.hu> wrote:
>>
>>
>>> I too have an async hang/crash, on an old-style SCSI (aic7xxx) box
>>> - hang log attached below.
>>> [...]
>>>
>>> ( Full bootlog attached below as well - i'm sending the config as a
>>> reply as this mail is close to lkml size limits already. )
>>>
>> Config attached.
>>
>> known bad : v2.6.29-9854-gd508afb
>> known good : v2.6.29
>>
>> Suspected commit introducing the regression:
>>
>> 9710794: async: remove the temporary (2.6.29) "async is off by default" code
>>
>> (i'll now try a revert of this.)
>>
>
> That's what I figured was the culprit as well, but that does not really
> tell us anything about what part of async.c is buggy :-)
>
>
In my case, the system doesn't hang or anything, it continues to boot
into a working system (except for no wireless and usb).
The only thing is that shutting down doesn't work. I have to hold the
power button because it hangs on shutdown.
Justin Madru
next prev parent reply other threads:[~2009-04-08 7:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 5:30 2.6.30-rc1: invalid opcode with call trace Justin Madru
2009-04-08 6:32 ` Jens Axboe
2009-04-08 6:47 ` Ingo Molnar
2009-04-08 6:52 ` Ingo Molnar
2009-04-08 6:53 ` Jens Axboe
2009-04-08 7:11 ` Ingo Molnar
2009-04-08 7:15 ` Jens Axboe
2009-04-08 7:11 ` Justin Madru [this message]
2009-04-08 8:12 ` Ingo Molnar
2009-04-10 8:15 ` Heinz Diehl
2009-04-08 7:27 ` Vegard Nossum
2009-04-08 7:40 ` Jens Axboe
2009-04-08 7:48 ` Ingo Molnar
2009-04-08 7:56 ` Jens Axboe
2009-04-08 16:15 ` Vegard Nossum
2009-04-09 14:45 ` Cornelia Huck
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=49DC4E3A.6040809@gawab.com \
--to=jdm64@gawab.com \
--cc=arjan@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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