From: walter harms <wharms@bfs.de>
To: Satyam Sharma <satyam.sharma@gmail.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: crash with 2.6.22.1 crash:ll_rw_blk.c blk_remove_plug()
Date: Mon, 23 Jul 2007 09:57:19 +0200 [thread overview]
Message-ID: <46A45F5F.3090606@bfs.de> (raw)
In-Reply-To: <a781481a0707221020m3c3a397fifa9076aefc63148a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Satyam Sharma wrote:
> Hi Walter,
>
> Thanks for reporting this.
>
> On 7/22/07, walter harms <wharms@bfs.de> wrote:
>> hello all,
>> on my asus notebook tm620 there is a crash with 2.6.22 and 2.6.21
>
> Did this happen when you were resuming from a suspend-to-ram/disk?
> [ I ask because I see swsusp in the trace below, linux-pm added to Cc: ]
>
hi all,
this is a 'simple' bootprocess no suspend from ram/disk no exotic devices beyond
a 20GB ide-hd.
attached is the current .conf (renamed to _config so nobody will accidentally overwrite)
re,
wh
[-- Attachment #2: _config.gz --]
[-- Type: application/x-gzip, Size: 18812 bytes --]
prev parent reply other threads:[~2007-07-23 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 8:46 crash with 2.6.21 BUG:ll_rw_blk.c walter harms
2007-07-18 10:33 ` Jens Axboe
[not found] ` <469DF233.5080902@bfs.de>
[not found] ` <20070718110724.GN11657@kernel.dk>
[not found] ` <469E072E.7080400@bfs.de>
[not found] ` <20070718123142.GV11657@kernel.dk>
2007-07-22 16:51 ` crash with 2.6.22.1 crash:ll_rw_blk.c blk_remove_plug() walter harms
2007-07-22 17:20 ` Satyam Sharma
2007-07-22 22:17 ` Jens Axboe
2007-07-25 0:22 ` Satyam Sharma
2007-07-25 7:05 ` walter harms
2007-07-25 11:18 ` Jens Axboe
2007-07-25 12:19 ` walter harms
2007-07-26 7:05 ` walter harms
2007-07-29 15:48 ` walter harms
2007-07-23 7:57 ` walter harms [this message]
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=46A45F5F.3090606@bfs.de \
--to=wharms@bfs.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=satyam.sharma@gmail.com \
/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