From: Pavel Machek <pavel@ucw.cz>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Timers SMP] can this machine be helped?
Date: Mon, 3 Dec 2007 22:47:56 +0100 [thread overview]
Message-ID: <20071203214756.GB8704@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0712032242540.7783@axis700.grange>
On Mon 2007-12-03 22:45:06, Guennadi Liakhovetski wrote:
> On Sun, 2 Dec 2007, Pavel Machek wrote:
>
> > > I compiled a .24-ish kernel for it with CONFIG_NO_HZ and
> > > CONFIG_HIGH_RES_TIMERS. To get the system boot at least sometimes I have
> > > to specify nohz=off. Then I get
> >
> > Try highres=off, too... Hehe, and even idle=poll might help.
>
> Ok, for now I've compiled a kernel with all "advanced" features off like
> hrt, nohz. Will see how it behaves. But thanks for the hints.
Let us know...
> > > CR0: 8005003b CR2: 081dcf88 CR3: 07e46000 CR4: 000002d0
> > > DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> > > DR6: ffff0ff0 DR7: 00000400
> > > [<c01053fa>] show_trace_log_lvl+0x1a/0x30
> > > [<c0105f42>] show_trace+0x12/0x20
> >
> > ...and disable softlockup watchdog, too...
>
> So, you think those BUGs are bogus?
Well.... you want to make old machine usable, right? Disabling
warnings is fair game.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-12-03 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 21:00 Guennadi Liakhovetski
2007-12-02 18:30 ` Pavel Machek
2007-12-03 21:45 ` Guennadi Liakhovetski
2007-12-03 21:47 ` Pavel Machek [this message]
2007-12-03 21:56 ` Guennadi Liakhovetski
[not found] <fa./nzsMVb44+6c2x42WGfe04SPDrY@ifi.uio.no>
2007-12-05 2:19 ` Robert Hancock
2007-12-05 6:47 ` Guennadi Liakhovetski
2007-12-05 14:34 ` Robert Hancock
2007-12-05 15:05 ` Guennadi Liakhovetski
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=20071203214756.GB8704@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=g.liakhovetski@gmx.de \
--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
all inboxes | Powered by JetHome®