From: Stefan Biereigel <security@biereigel-wb.de>
To: Donald Allen <donaldcallen@gmail.com>
Cc: john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PROBLEM: tickless scheduling
Date: Mon, 17 May 2010 18:15:34 +0200 [thread overview]
Message-ID: <4BF16BA6.3040404@biereigel-wb.de> (raw)
In-Reply-To: <AANLkTinDvxfub_CBYQru7yi9KAAjjf5Q4emme0VXSErG@mail.gmail.com>
Am 17.05.2010 17:26, schrieb Donald Allen:
> Stefan --
>
> Would you check the BIOS on your machine and report the maker and
> version number? If you've followed this, I'm especially interested to
> know if it's a Phoenix BIOS.
>
> Thanks --
> /Don
Hello Don,
I did try some things here. pci=nomsi didn't work really, but I think it
decreased the rate of stucks, even though I'm not sure. My BIOS is a
Phoenix TrustedCore with version number PG2G3A08, should be from 7/2009
or so.
I will try my next boot with hpet=disable and report my results. Thanks
for your help!
Stefan DK3SB
next prev parent reply other threads:[~2010-05-17 16:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 0:18 PROBLEM: tickless scheduling Donald Allen
2010-05-11 0:27 ` Robert Hancock
2010-05-11 0:34 ` Donald Allen
2010-05-11 0:38 ` Robert Hancock
2010-05-11 0:53 ` Donald Allen
2010-05-11 0:54 ` john stultz
2010-05-11 0:59 ` Donald Allen
2010-05-11 1:12 ` john stultz
2010-05-11 1:52 ` Donald Allen
2010-05-12 19:54 ` Donald Allen
2010-05-12 20:52 ` john stultz
2010-05-15 17:11 ` Donald Allen
2010-05-16 16:14 ` Stefan Biereigel
2010-05-16 20:41 ` Arjan van de Ven
2010-05-17 15:26 ` Donald Allen
2010-05-17 16:15 ` Stefan Biereigel [this message]
2010-05-16 23:36 ` Thomas Gleixner
2010-05-17 13:44 ` Donald Allen
2010-05-17 14:02 ` Donald Allen
2010-05-17 14:04 ` Arjan van de Ven
2010-05-17 14:11 ` Donald Allen
2010-05-17 14:29 ` Arjan van de Ven
2010-05-17 14:45 ` Donald Allen
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=4BF16BA6.3040404@biereigel-wb.de \
--to=security@biereigel-wb.de \
--cc=donaldcallen@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.