From: Christian Kujau <evil@g-house.de>
To: Andreas Schmidt <andy@space.wh1.tu-dresden.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Frequent system freezes after kernel bug
Date: Mon, 14 Jun 2004 00:14:21 +0200 [thread overview]
Message-ID: <40CCD1BD.6090509@g-house.de> (raw)
In-Reply-To: <20040613175134.GO1733@rocket>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andreas Schmidt wrote:
| _did_ happen again. So, what do you suggest? (Sorry if that sounds
| obnoxious, but I'm really a bit confused about this stuff...)
sorry to confuse. no, i'm not able to tell any relevant information from
your oops. i must say that it just occured *to me* that we had different
oopses and lockups with fcdsl and fcpci (!) modules, which were hard to
reproduce too.
you said:
| This box runs under Debian stable; I noticed these particular bugs
| starting with kernel 2.4.24. Yesterday, I updated from 2.4.25 to
so 2.4.23 did work? would be strange, since patch-2.4.24.b2 is only
2,5KB in size and touches very few things. good for you: if 2.4.23 is
really working and 2.4.24 is not, you could back out the changes and see
what it gives.
just my 2¢,
Christian.
- --
BOFH excuse #179:
multicasts on broken packets
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAzNG8+A7rjkF8z0wRAo4XAJ9wP6X38jyICqmB7ATYSyc2N6l/BgCfQnVf
TkJlP1NWnExS6uub5KEHesk=
=DoAL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-13 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 18:37 Frequent system freezes after kernel bug Andreas Schmidt
2004-06-12 20:20 ` Chris Wedgwood
2004-06-12 21:49 ` Andreas Schmidt
2004-06-13 0:10 ` Christian Kujau
2004-06-13 17:51 ` Andreas Schmidt
2004-06-13 22:14 ` Christian Kujau [this message]
2004-06-14 3:51 ` Andreas Schmidt
2004-06-16 7:23 ` Andreas Schmidt
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=40CCD1BD.6090509@g-house.de \
--to=evil@g-house.de \
--cc=andy@space.wh1.tu-dresden.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.