From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [bug] 2.6.27-rc1: I/O errors after resume
Date: Thu, 31 Jul 2008 20:54:59 +0200 [thread overview]
Message-ID: <200807312055.00323.rjw@sisk.pl> (raw)
In-Reply-To: <200807312041.35544.rjw@sisk.pl>
On Thursday, 31 of July 2008, Rafael J. Wysocki wrote:
> On Thursday, 31 of July 2008, Miklos Szeredi wrote:
> > On Thu, 31 Jul 2008, Rafael J. Wysocki wrote:
> > > On Thursday, 31 of July 2008, Miklos Szeredi wrote:
> > > > With 2.6.27-rc1 things break badly after resume on my T60. Dmesg and
> > > > config attached. 2.6.26 worked fine.
> > >
> > > Ugh, lots of stuff in a single message.
> >
> > Yeah, sorry. Search for "I/O error" for the interesting parts.
> >
> > > Anyway, can you try the current -git and report back, please? It's possible
> > > that this has been fixed already.
> >
> > Not fixed:
> >
> > mszeredi@tucsk:~> uname -a
> > Linux tucsk 2.6.27-rc1-00156-g94ad374 #17 SMP Thu Jul 31 15:45:10 CEST 2008 x86_64 x86_64 x86_64 GNU/Linux
> > mszeredi@tucsk:~> dmesg
> > bash: /bin/dmesg: Input/output error
> >
> > Seems easily reproducible, so if no better ideas I can try to bisect it.
>
> That would be really helpful.
Please also have a look at http://bugzilla.kernel.org/show_bug.cgi?id=11178
Thanks,
Rafael
prev parent reply other threads:[~2008-07-31 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 10:03 nvidia MCP78B ahci failed to IDENTIFY error on 2.6.26 Jan Schneider
2008-07-30 8:12 ` Andrew Morton
2008-07-31 13:04 ` [bug] 2.6.27-rc1: I/O errors after resume Miklos Szeredi
2008-07-31 13:31 ` Rafael J. Wysocki
2008-07-31 14:06 ` Miklos Szeredi
2008-07-31 18:41 ` Rafael J. Wysocki
2008-07-31 18:54 ` Rafael J. Wysocki [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=200807312055.00323.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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
all inboxes | Powered by JetHome®