mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Malte Schröder" <maltesch@gmx.de>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: Jan Engelhardt <jengelh@medozas.de>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Hard lockup with kernel 2.6.25 and 2.6.25.1
Date: Mon, 12 May 2008 15:28:34 +0200	[thread overview]
Message-ID: <20080512152834.37507516@highlander.home.lan> (raw)
In-Reply-To: <20080504222246.50dc6f5b@highlander.home.lan>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

On Sun, 4 May 2008 22:22:46 +0200
Malte Schröder <maltesch@gmx.de> wrote:
> Besides from that I am currently trying to find the last working
> kernel-version, since 2.6.24.6 shows the same problem.
> I am currently running 2.6.24.5 again. Let's see if that runs stable.
> When I have found a stable kernel I think I will bisect it, but I am
> quite busy currently so it could take a while. Who knows, maybe it's
> not the kernel's fault at all but some strange kind of hardware failure.

A short report to that issue:
I went back down to 2.6.24.4 and the problem did not disappear. I am
not convinced that this is a new kernel-bug.
I will investigate this more and come back if/when I find some more
clues.

Regards
-- 
---------------------------------------
Malte Schröder
MalteSch@gmx.de
ICQ# 68121508
---------------------------------------


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2008-05-12 13:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03 22:52 Malte Schröder
2008-05-03 23:05 ` Christian Kujau
2008-05-04  9:54   ` Malte Schröder
2008-05-03 23:18 ` Greg KH
2008-05-04  9:51   ` Malte Schröder
2008-05-04 11:49     ` Malte Schröder
2008-05-04 19:56     ` Jan Engelhardt
2008-05-04 20:22       ` Malte Schröder
2008-05-12 13:28         ` Malte Schröder [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=20080512152834.37507516@highlander.home.lan \
    --to=maltesch@gmx.de \
    --cc=greg@kroah.com \
    --cc=jengelh@medozas.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®