From: Andreas Schmidt <andy@space.wh1.tu-dresden.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Frequent system freezes after kernel bug
Date: Mon, 14 Jun 2004 05:51:00 +0200 [thread overview]
Message-ID: <20040614035100.GQ1733@rocket> (raw)
In-Reply-To: <40CCD1BD.6090509@g-house.de> (from evil@g-house.de on Mon, Jun 14, 2004 at 00:14:21 +0200)
On 2004.06.14 00:14, Christian Kujau wrote:
> Andreas Schmidt wrote:
> 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.
Hmmm, I guess my posting was a bit ambigious in this regard. I started
out with 2.4.18, upgraded to 2.4.19, later 2.4.21. As the fcdsl-crashes
(triggered by disconnection) didn't cease, I googled and found other
reports of the same bug on kernels 2.4.18 and higher, so I decided to
give it a try and downgrade to 2.4.17. From there, I went right up to
2.4.24. At that time I learned of a patch to the module which allowed
to run it without the problems previously encountered. However, there
still remained the system freezes from the second bug (buffer.c/
transaction.c), so I decided to upgrade to 2.4.25 and, ultimately,
2.4.26.
Best regards,
Andreas
next prev parent reply other threads:[~2004-06-14 3:51 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
2004-06-14 3:51 ` Andreas Schmidt [this message]
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=20040614035100.GQ1733@rocket \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox