public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chr <chunkeey@web.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Date: Mon, 31 Mar 2008 14:51:08 +0200	[thread overview]
Message-ID: <200803311451.08707.chunkeey@web.de> (raw)
In-Reply-To: <87wsnj8j2t.fsf@basil.nowhere.org>

On Monday 31 March 2008 09:10:34 Andi Kleen wrote:
> Chr <chunkeey@web.de> writes:
> > Ever since I went to the new 2.6.25-rcX, I encountered lots of random
> > system freezes after about 2 or 3 hours of uptime... but until now,
> > I couldn't _catch_ them, since the system
> > (AMD Athlon 4200+ X2 (Manchester) / nforce 4 SLI / x86_64) went
> > straight into oblivion (nothing on the serial console or anywhere else,
> > heck I couldn't even hit reset, It didn't POST anymore)
>
> Not POSTing would point to some kind of hardware problem. Normally
> the kernel shouldn't be able to cause that.
Normally yes.. but this is the first time that this ever happend!
(And my system has been stable so far (more than a year now, in fact more like 
2 years)... even with nvidia & madwifi drivers!). 

>
> I would recommend you double check if the problem is really not
> there with an older kernel by going back there and testing.
Well... older kernels won't freeze that way..
I can hit reset whenever I want and it still POSTs.

But, I'll try... maybe I get another change. 
(BTW, if it happends again, is there anything special, that
could help to find the real bugs?)
>
> -Andi
Regards,
	Chr.


  reply	other threads:[~2008-03-31 12:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-30 19:09 The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Chr
2008-03-30 19:25 ` Rafael J. Wysocki
2008-03-30 19:59   ` Thomas Gleixner
2008-03-30 20:18     ` Chr
2008-03-30 20:37       ` Thomas Gleixner
2008-03-30 21:09         ` Chr
2008-03-30 21:36           ` Thomas Gleixner
2008-03-30 22:19             ` Chr
2008-03-31 12:56             ` Adrian Bunk
2008-03-31 13:23               ` Chr
2008-03-31 22:01             ` Chr
2008-03-31 23:14               ` Rafael J. Wysocki
2008-03-31 23:30                 ` Chr
2008-04-01 21:16                   ` Rafael J. Wysocki
2008-04-01 22:27                     ` Chr
2008-04-02 12:45                     ` Chr
2008-04-01 16:27               ` Thomas Gleixner
2008-04-01 18:57                 ` Chr
2008-04-01 22:29                 ` Chr
2008-04-02  7:08                   ` Thomas Gleixner
2008-04-02  9:34                     ` Chr
2008-03-31  7:10 ` Andi Kleen
2008-03-31 12:51   ` Chr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-03 22:49 2.6.25-rc8-git2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-03 23:22 ` The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Rafael J. Wysocki
2008-04-04  1:49   ` Chr

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=200803311451.08707.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=andi@firstfloor.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox