mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Rogge <marogge@onlinehome.de>
To: linux-kernel@vger.kernel.org
Cc: devzero@web.de
Subject: Re: 2.6.30.1-4 kernels freezes dual pentium-3 system
Date: Sat, 8 Aug 2009 23:03:52 +0200	[thread overview]
Message-ID: <200908082303.52471.marogge@onlinehome.de> (raw)
In-Reply-To: <859414371@web.de>

On Saturday 08 August 2009 11:49:50 devzero@web.de wrote:

> > Btw, since then there have been two more
> > reports on lkml of dual P2 systems locking up with 2.6.30++.
>
> could you send pointers?

Since I am not subscribed to the LKML (I only read it via a NNTP relay) I have 
some difficulties providing IDs. Anyway, the subject of the reports I have in 
mind is "PROBLEM: crash / hang with linux-2.6.30.x on PII-350 SMP system".

> any existing bugzilla bugentry for these or for your`s ?

Earlier today I filed bug 13933 on kernel.bugzilla. Unfortunately I had some 
problems attaching all the files, so my earlier LKML post is still the best 
source of information.

> > Network, sysrq and numlock are all unresponsive.
>
> ok, that`s why we need to have the last informations from before the dying
> breath...

agreed.

>
> btw, i one of your dmesg i found these:
>
> Aug  1 19:42:57 frya kernel: [...]

Again, that's someone else's report. Regarding clocksource, while I was trying 
to hunt down this bug I once booted with "clocksource=acpi_pm" but it made no 
difference. Truth be told, at that time I was still troubleshooting the 
nvidia.ko driver.

Martin


  reply	other threads:[~2009-08-08 21:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08  9:49 devzero
2009-08-08 21:03 ` Martin Rogge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-08 21:25 devzero
2009-08-08  8:19 Martin Rogge
2009-08-07 22:51 devzero
2009-08-10 14:42 ` John Stoffel
2009-08-18 14:40   ` John Stoffel
2009-08-19 14:53     ` Vince Weaver
2009-08-03 16:25 Martin Rogge
2009-08-07 20:29 ` Martin Rogge
2009-08-10 14:38   ` John Stoffel
2009-08-03  8:44 Осипов Станислав

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=200908082303.52471.marogge@onlinehome.de \
    --to=marogge@onlinehome.de \
    --cc=devzero@web.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®