From: Martin Mueller <mm@sig21.net>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel locks up when idle on VIA-nano U2300 with VIA VX800 on Jetway JNF76-N1GL-LF mainboard
Date: Fri, 26 Jun 2009 17:55:46 +0200 [thread overview]
Message-ID: <20090626155542.GA26353@caesar.sig21.net> (raw)
In-Reply-To: <20090601201951.01a48d3e@dhcp-100-2-144.bos.redhat.com>
Hi,
On Mon, Jun 01, 2009 at 08:19:51PM -0400, Chuck Ebbert wrote:
> On Sun, 26 Apr 2009 19:06:02 +0200
> Martin Mueller <mm@sig21.net> wrote:
>
> > Hi Jeffrey,
> >
> > On Sun, Apr 26, 2009 at 12:25:51PM +0000, Jeffrey Cao wrote:
> > > On 2009-04-26, Martin Mueller <mm@sig21.net> wrote:
> >
> > > > Next, I downloaded linux-2.6.30-rc3, compiled a minimal version with
> > > > just initrd. I left out PCI-support, ACPI and almost everything else
> > > > menuconfig allowed me to unselect except the VGA text console. This
> > > > kernel locked up after giving me the initial prompt from busybox in
> > > > the initrd.
> > > >
> > > > When adding the following lines in the script executed by the kernel
> > > > after booting in the initrd, the system actually works:
> > > >
> > > > while true; do true; done &
> > > > /bin/sh
> > > >
> > > > As soon as I kill the shell loop, the system freezes again.
> > > >
> > > > So my conclusion is: the kernel locks up the first time the CPU
> > > > is idle.
> >
> > > This seems something to do with the board and the hard disk drive.
> >
> > Thanks for your suggestion, but it has nothing to do with the hardisk.
> > As I wrote above, the problem is reproducible with only an initrd, vga
> > text console, keyboard and no other driver loaded or compiled in.
> >
> > The kernel freezes as soon as it get's idle the first time.
> >
>
> Adding idle=halt to the boot options works. idle=nomwait should work too but
> it doesn't.
Thanks for your suggestion it worked fine. Yesterday I did a BIOS
update (A03) from jetway, which contained a microcode update for the
CPU. Since then it also works without this bootparam.
bye
MM
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
prev parent reply other threads:[~2009-06-26 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 9:51 Martin Mueller
2009-04-26 12:25 ` Jeffrey Cao
2009-04-26 17:06 ` Martin Mueller
2009-06-02 0:19 ` Chuck Ebbert
2009-06-26 15:55 ` Martin Mueller [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=20090626155542.GA26353@caesar.sig21.net \
--to=mm@sig21.net \
--cc=cebbert@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome