From: wharms@bfs.de (walter harms)
To: kernelnewbies@lists.kernelnewbies.org
Subject: My Kernel bug is celebrating 2 years. Can you help me fix it?
Date: Wed, 05 Mar 2014 09:27:54 +0100 [thread overview]
Message-ID: <5316E00A.3030704@bfs.de> (raw)
In-Reply-To: <CA+MoWDrTNtAHKsiBHz=W4=eJRO=m9EK_HZ7zLxb=4fg5riUQeg@mail.gmail.com>
Am 04.03.2014 22:26, schrieb Peter Senna Tschudin:
> I have reported a bug more than two years ago and it is still
> affecting me. The bug report gives some information:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=787299
>
> I have tried basic debug instructions from:
> https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt
>
> And everything works as expected when:
> # echo freeze > /sys/power/state
> # echo disk > /sys/power/state
>
> I have asked for help for fixing it:
> https://lkml.org/lkml/2013/11/1/186
>
> But I don't have a serial port. How can I debug this issue without a
> "real" serial port? Or what else can I try?
You need to create a kernel with networksupport,
setup "netconsole" you need a second computer to receive the issues.
>How can I explore the hint
> about the problem only happening with VT-d enabled in BIOS? How can I
> explore the hint about the problem not happening if the option
> nox2apic is passed to the Kernel?
never heard about that until now, obviously there is a bug in several
acpi's that can be triggered. If your systems works with nox2apic
as bootparameter you should be happy since a workaround is available.
Information about it is used can be find here:
http://lxr.free-electrons.com/ident?a=microblaze;i=nox2apic
re,
wh
> Thank you,
>
> Peter
>
> P.S Yes, it works on Windows.
>
next prev parent reply other threads:[~2014-03-05 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 21:26 My Kernel bug is celebrating 2 years. Can you help me fix it? Peter Senna Tschudin
2014-03-05 8:27 ` walter harms [this message]
2014-03-05 11:54 ` Peter Senna Tschudin
2014-03-05 22:32 ` Thomas Petazzoni
2014-03-06 18:27 ` Bjorn Helgaas
2014-03-06 19:08 ` Peter Hurley
2014-03-07 15:01 ` Peter Senna Tschudin
2014-03-07 15:44 ` Peter Hurley
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=5316E00A.3030704@bfs.de \
--to=wharms@bfs.de \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).