From: Ben Collins <ben.collins@ubuntu.com>
To: Cal Peake <cp@absolutedigital.net>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org,
Tim Gardner <tim.gardner@canonical.com>
Subject: Re: Regression in 2.6.22, clock problems on Turion with 32-bit kernel
Date: Fri, 03 Aug 2007 11:58:33 -0400 [thread overview]
Message-ID: <1186156713.8105.76.camel@cunning> (raw)
In-Reply-To: <Pine.LNX.4.64.0708031146090.3978@lancer.cnet.absolutedigital.net>
On Fri, 2007-08-03 at 11:50 -0400, Cal Peake wrote:
> On Fri, 3 Aug 2007, Ben Collins wrote:
>
> >
> > On Fri, 2007-08-03 at 08:30 -0700, Arjan van de Ven wrote:
> > > > I've tried every combination of boot param revolving around clocksource
> > > > and interrupts. The only thing that gets me booting is nolapic, but then
> > > > again, that knocks me down to a single cpu.
> > >
> > > hummm.... I wonder how nolapic knows you down to a single cpu.......
> > > that is just an entirely strange relationship.
> >
> > Sorry, s/cpu/core/, but not sure if that makes a difference.
>
> Ben, Tim,
>
> See thread <http://marc.info/?t=118573271600006&r=1&w=2>. Short version:
> nolapic_timer should fix things for the moment. Long term: some AMD kernel
> code needs to be fixed up to deal with a broken local APIC.
nolapic_timer does not fix it for me. Only nolapic and acpi=off works. I
commented on that thread as well now, thanks.
--
Ubuntu : http://www.ubuntu.com/
Linux1394: http://wiki.linux1394.org/
next prev parent reply other threads:[~2007-08-03 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 14:14 Regression in 2.6.22, clock problems on Turion with 32-bit kernel Ben Collins
2007-08-03 14:18 ` Tim Gardner
2007-08-03 15:30 ` Arjan van de Ven
2007-08-03 15:43 ` Ben Collins
2007-08-03 15:47 ` Arjan van de Ven
2007-08-03 15:50 ` Cal Peake
2007-08-03 15:58 ` Ben Collins [this message]
2007-08-03 16:01 ` Cal Peake
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=1186156713.8105.76.camel@cunning \
--to=ben.collins@ubuntu.com \
--cc=arjan@infradead.org \
--cc=cp@absolutedigital.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.gardner@canonical.com \
/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.