From: "Uwe Bugla" <uwe.bugla@gmx.de>
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: bugs in 2.6.20 kernels
Date: Tue, 27 Feb 2007 19:44:42 +0100 [thread overview]
Message-ID: <20070227184442.21690@gmx.net> (raw)
Hi,
one problem in this mail is already being discussed - excellent!
The rest is cced now to linux-kernel@vger.kernel.org just to take care for that it is not forgotten and to help to avoid that rubbish is not being pushed into mainline vanilla:
In the current 2.6.20 kernels I found three bugs:
A. kernel 2.6.20-mm1 plus kernel 2.6.20-git14
Bug 1: I cannot mount an ordinary floppy drive without hanging up the whole system (somewhere between git10 and git14).
Bug 2: If I boot my home LAN server with 2.6.20-mm1 this kernel freezes my Apache-2.2.3 services after a certain amount of time: The physical connection, controllable by ping, stays functionable, but I cannot address that apache server with my workstations any more (somewhere <= git14).
B. kernel 2.6.20-git14:
Bug 3: As I reported already nerolinux runs fine and excellent again, recognizes my burning devices and everything is fine so far.
BUT: One problem I reported in connection with those CD burning problems unfortunately still exists:
>From time to time my burning device is being reinitialized for whatever nonsense reason that I do not know. As if it would lose electricity or data connection for just a moment. The one consequence is that the KDE daemon arizes and tells me something about an audio CD in one of my drives:
/dev/hdc is a LG DVD drive
/dev/hdd is a TEAC CD W54 burning device.
But fact is both drives do not contain any Audio CD at all.
The other consequence is that dmesg tells me about endless drive seek errors. What a crucial bug! It does not happen immediately, but from time to time.
And I can promise that my hardware is fine! So this is no hardware bug at all. Timing problems? No idea!
I am working with an intel ICH 4 chipset on an ASUS P4 PE mainboard. My distro is Debian Etch snapshot from february 13, 2007.
This bug number 3 appeared first at the transition from 2.6.19 to 2.6.20-rc1 if I remember right (but not sure).
I did not have that problem with 2.6.19 and earlier kernels.
Would you please fix those errors please?
Best regards
Uwe
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
reply other threads:[~2007-02-27 18:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070227184442.21690@gmx.net \
--to=uwe.bugla@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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