From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, Jacob Pan <jacob.jun.pan@intel.com>
Subject: Re: 2.6.34-rc5-git10: oops on Atom N270/ i945GSE upon shutdown with X86_MRST && APB_TIMER enabled
Date: Fri, 30 Apr 2010 00:07:34 +0200 [thread overview]
Message-ID: <201004300007.36911.s.L-H@gmx.de> (raw)
In-Reply-To: <4BD9F1FE.8010708@zytor.com>
Hi
On Friday 30 April 2010, H. Peter Anvin wrote:
> Could you apply this patch and verify that it solves your problem:
>
> http://git.kernel.org/tip/ae7c9b70dcb4313ea3dbcc9a2f240dae6c2b50c0
I can confirm that this patch applied on top of 2.6.34-rc5-git10 fixes
my shutdown problem; no further oops has shown within 20+ shutdowns so far,
while it was 100% reproducably before. Sorry that I didn't notice
https://bugzilla.kernel.org/show_bug.cgi?id=15786 before.
Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
> -hpa
>
> On 04/29/2010 12:43 PM, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > While testing kernel 2.6.34-rc5-git10 on an Acer Aspire One 110L netbook
> > (Atom N270, i945GSE chipset, hyperthreading enabled and not configurable,
> > BIOS 3309), I reproducably encounter the following oops while shutting down
> > (manual transcription below):
> >
> > Pid: 2253, comm: halt Not Tainted 2.6.34-rc5-sidux-686 #1 /AOA110
> > EIP: 0060:[<c0121232>] EFLAGS: 00010202 CPU: 0
> > EIP is at apbt_cpuhp_notify+0x32/0x60
[...]
Thanks a lot
Stefan Lippers-Hollmann
prev parent reply other threads:[~2010-04-30 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 19:43 2.6.34-rc5-git10: oops on Atom N270/ i945GSE upon shutdown with X86_MRST && APB_TIMER enabled Stefan Lippers-Hollmann
2010-04-29 20:31 ` Pan, Jacob jun
2010-04-29 20:54 ` H. Peter Anvin
2010-04-29 22:07 ` Stefan Lippers-Hollmann [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=201004300007.36911.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.