From: sam <sam.tygier@hep.manchester.ac.uk>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Lenovo S12 2.6.36-rc7 lockup
Date: Tue, 12 Oct 2010 23:22:26 +0100 [thread overview]
Message-ID: <1286922146.4040.2.camel@oberon> (raw)
In-Reply-To: <20101010164818.6617102c@boulder.homenet>
On Sun, 2010-10-10 at 16:48 +0100, Chris Vine wrote:
> On Sun, 10 Oct 2010 13:59:12 +0100
> Chris Vine <chris@cvine.freeserve.co.uk> wrote:
> > Hi,
> >
> > kernel 2.6.36-rc7 completely locks up my Lenovo S12 notebook on
> > boot-up. It happens early enough in boot-up that nothing appears in
> > any of the system log files. The last message printed to the console
> > is "Using IPI - No Shortcut mode".
> >
> > The lock up does not occur with kernel 2.6.35.6. I do not know in
> > what version of 2.6.36-rc this first arose.
> >
> > The kernel configuration is set out below.
> >
> > Chris
> [snip]
>
> On testing now with the earlier 2.6.36-rc6, I see that it is not a
> lock-up but a hang, in that it partly responds to the keyboard. With
> rc6 boot-up can proceed further than with rc7 (but very slowly) if
> keyboard keys are more or less randomly pressed. Boot up is never
> completed though with rc6, even though it proceeds further.
>
> Chris
i have seen similar issue while running with older kernels (2.6.32) on a
S12 (intel GPU version). there is an ubuntu bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/643822
the "nolapic_timer" boot flag fixes it for me.
sam
next prev parent reply other threads:[~2010-10-12 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 12:59 Lenovo S12 2.6.36-rc7 lockup Chris Vine
2010-10-10 15:48 ` Chris Vine
2010-10-12 22:22 ` sam [this message]
2010-10-13 9:13 ` Chris Vine
2010-10-11 22:12 ` Len Brown
2010-10-11 23:27 ` Chris Vine
2010-10-11 23:38 ` Chris Vine
2010-10-12 17:12 ` Maciej Rutecki
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=1286922146.4040.2.camel@oberon \
--to=sam.tygier@hep.manchester.ac.uk \
--cc=chris@cvine.freeserve.co.uk \
--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.