From: Nigel Cunningham <ncunningham@cyclades.com>
To: "Hesse, Christian" <mail@earthworm.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: hald in status D with 2.6.16-rc4
Date: Wed, 22 Feb 2006 21:09:16 +1000 [thread overview]
Message-ID: <200602222109.21816.ncunningham@cyclades.com> (raw)
In-Reply-To: <200602221110.44813.mail@earthworm.de>
[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]
Hi.
On Wednesday 22 February 2006 20:10, Hesse, Christian wrote:
> On Tuesday 21 February 2006 23:49, Andrew Morton wrote:
> > "Hesse, Christian" <mail@earthworm.de> wrote:
> > > On Tuesday 21 February 2006 06:19, Andrew Morton wrote:
> > > > "Hesse, Christian" <mail@earthworm.de> wrote:
> > > > > Hello everybody,
> > > > >
> > > > > since using kernel version 2.6.16-rc4 the hal daemon is in status D
> > > > > after resume. I use suspend2 2.2.0.1 for 2.6.16-rc3. Any hints what
> > > > > could be the problem? It worked perfectly with 2.6.15.x and
> > > > > suspend2 2.2.
> > > >
> > > > a) Look in the logs for any oopses, other nasties
> > >
> > > Nothing.
> > >
> > > > b) Do `echo t > /proc/sysrq-trigger', `dmesg -s 1000000 > foo' then
> > > > find the trace for `hald' in `foo', send it to this list.
> > >
> > > Ok, here it is:
> > >
> > > [ trace snipped ]
> > >
> > > This is with 2.6.16-rc4-git1 + suspend2 2.2.0.1.
> >
> > Hopefully suspend2 isn't involved. People would feel more comfortable if
> > you could test a vanilla mainline tree..
> >
> > Could the ACPI team please take a look at fixing this regression?
>
> I did two cycles with mainline suspend now and did not hit the problem... I
> will keep an eye on it.
Could you let me know how you go? I didn't make any changes between 2.2 and
2.2.0.1 that I think could cause this, but if you can't reproduce it
otherwise, I'll happily look again.
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-22 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602202034.29413.mail@earthworm.de>
[not found] ` <20060220211909.7964d56e.akpm@osdl.org>
[not found] ` <200602212322.48645.mail@earthworm.de>
2006-02-21 22:49 ` hald in status D with 2.6.16-rc4 Andrew Morton
2006-02-22 10:10 ` Hesse, Christian
2006-02-22 11:09 ` Nigel Cunningham [this message]
2006-02-22 22:36 ` Hesse, Christian
2006-02-22 22:51 ` Nigel Cunningham
2006-02-22 20:12 ` Hesse, Christian
2006-02-27 22:48 ` Hesse, Christian
2006-02-28 0:40 ` Nigel Cunningham
2006-02-28 7:47 ` Hesse, Christian
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=200602222109.21816.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@earthworm.de \
/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;
as well as URLs for NNTP newsgroup(s).