From: "Malte Schröder" <maltesch@gmx.de>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: 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: Sun, 4 May 2008 22:22:46 +0200 [thread overview]
Message-ID: <20080504222246.50dc6f5b@highlander.home.lan> (raw)
In-Reply-To: <alpine.LNX.1.10.0805042155530.11757@fbirervta.pbzchgretzou.qr>
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
On Sun, 4 May 2008 21:56:26 +0200 (CEST)
Jan Engelhardt <jengelh@medozas.de> wrote:
>
> On Sunday 2008-05-04 11:51, Malte Schröder wrote:
> >>
> >> If it's repeatable, it would be interesting if you are able to do a
> >> git-bisect to try to narrow the issue down...
> >
> >Hmm, that's about the only box of mine where bisecting a kernel really
> >hurts. It's my central VoIP, internet, mail and other stuff gateway and
> >it takes ages to boot (it's the box where my old hardware ends up).
>
> You can compile the tree elsewhere (without nfs) and then run the
> appropriate install mechanisms with an NFS mount.
>
Oh, that's not the problem, I use the debian's kernel-package
build-system
. The problem is that the affected box is about the only box
where I really don't like downtime because it handles my
internet connection, email and telephony.
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.
Regards
--
---------------------------------------
Malte Schröder
MalteSch@gmx.de
ICQ# 68121508
---------------------------------------
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-04 20:23 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 [this message]
2008-05-12 13:28 ` Malte Schröder
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=20080504222246.50dc6f5b@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®