mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Richard <tuxbox.guru@gmail.com>
Cc: Thomas Renninger <trenn@suse.de>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"andreas.herrmann3" <andreas.herrmann3@amd.com>,
	eumaster@gmail.com, uli.geins@geins-web.de
Subject: Re: [PATCH] Re: AMD Mobile Semprons (3500+, 3600+,...) break with nohz and highres enabled
Date: Thu, 17 Jul 2008 13:05:43 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0807171255320.4316@apollo.tec.linutronix.de> (raw)
In-Reply-To: <487F309D.20709@gmail.com>

On Thu, 17 Jul 2008, Richard wrote:
> > north-bridge: nvidia c51mv
> > south-bridge: nvidia mcp51m
> > 
> > Also both are MSI laptops:
> >   - MSI-M670, modell MS-1632
> >   - MSI S430x
> > (This could also be a chipset or even an MSI specific BIOS bug?
> > Richard could you compare with your HW, pls if still possible).
> > 
> > Some more info:
> >   - things break entering C2 or deeper
> >   - noapictimer workaround helps to come a bit further, but results in sever
> >     other errors, disk(dma error), keyboad, mouse etc., also see:

Hmm, I don't see how the apic timer is related to that, but it might
be a problem with the hpet.

Does "noapictimer nohz=off" work ?

> >     https://bugzilla.novell.com/show_bug.cgi?id=396220#c13
> >   - "nohz=off" works (tested on 2.6.25.4-8-pae and 2.6.22.17-0.1-default
> > SUSE kernels)
> >   - processor.max_cstate=1 works

Why does it work with 2.6.24 on kubuntu 8.04 ? 

How does a 2.6.24/25/26 vanilla kernel behave on those systems ?

> > 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
> 
> Here is a dump from lspci.... looks completely different :-P and here i was
> blaming ATI :-)
> 
> 00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge

Oh, that's a different beast, but it might be also a problem with the
timer interrupt routing.

Thanks,

	tglx

      reply	other threads:[~2008-07-17 11:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 17:47 Thomas Renninger
2008-06-16 17:54 ` H. Peter Anvin
2008-06-16 20:06   ` Richard
2008-07-16 16:27 ` [PATCH] " Thomas Renninger
2008-07-16 19:03   ` Thomas Gleixner
2008-07-16 19:56     ` Thomas Renninger
2008-07-17  6:55       ` Richard
2008-07-17 10:51         ` Thomas Gleixner
2008-07-17 11:58           ` Richard
2008-07-17 11:11             ` Thomas Gleixner
2008-07-17 12:23               ` Richard
2008-07-17 12:03                 ` Thomas Gleixner
2008-07-17 17:47                   ` Richard
2008-07-17 16:59                     ` Thomas Gleixner
2008-07-18 11:03                       ` Richard
2008-07-18 17:12                       ` Richard
2008-07-18 17:14                       ` Richard
2008-07-18 17:15                       ` Richard
2008-07-17 10:32     ` Thomas Renninger
2008-07-17 11:44       ` Richard
2008-07-17 11:05         ` Thomas Gleixner [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=alpine.LFD.1.10.0807171255320.4316@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=andreas.herrmann3@amd.com \
    --cc=eumaster@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=trenn@suse.de \
    --cc=tuxbox.guru@gmail.com \
    --cc=uli.geins@geins-web.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome