From: Kasper Sandberg <lkml@metanurb.dk>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: LKML Mailinglist <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [BUG] ACPI bug in 2.6.17-rc3
Date: Tue, 02 May 2006 17:09:44 +0200 [thread overview]
Message-ID: <1146582584.7183.0.camel@localhost> (raw)
In-Reply-To: <44572EFD.9070703@gmail.com>
On Tue, 2006-05-02 at 12:05 +0159, Jiri Slaby wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Cc: linux-acpi@vger.kernel.org
>
> Kasper Sandberg napsal(a):
> > hello.. just tried out 2.6.17-rc3 on my amd64 system, and i got this
> > backtrace:
> > khelper pid 4
> > trace:
> > activate_task+319 try_to_wake_up+93
> > __wake_up_common+68 complete+38
> > run_workqueue+136 worker_thread+353
> > default_wake_function+0 worker_thread+0
> > kthread+219 worke_thead+0
> > child_rip+8 worker_thread+0
> > kthread+0 child_rip+0
> >
> > this happened immediately after vesafb changed resolution, i tried
> > without vesafb, still the same..
> We need whole bug log, no just the trace. Is it possible to grab it?
this is all i get..
>
> thanks,
> - --
> Jiri Slaby www.fi.muni.cz/~xslaby
> \_.-^-._ jirislaby@gmail.com _.-^-._/
> B67499670407CE62ACC8 22A032CC55C339D47A7E
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFEVy79MsxVwznUen4RAp6tAJ9RvSDGtglFtMUW912z3dJQY75mFwCgu5i5
> sKbi0EN6YYKmlUo6qcqvU5c=
> =CNZM
> -----END PGP SIGNATURE-----
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2006-05-02 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 6:02 [BUG] ACPI bug in 2.6.17-rc3 Kasper Sandberg
2006-05-02 10:06 ` Jiri Slaby
2006-05-02 15:09 ` Kasper Sandberg [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=1146582584.7183.0.camel@localhost \
--to=lkml@metanurb.dk \
--cc=jirislaby@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox