Hello Tim,
It's a known bug. I asked for the fix to go into 2.6.6, but it was
decided to
wait until 2.6.7 instead.
Back to Core 1 it is then :-/
You better raise this issue at the [EMAIL PROTECTED] . Maybe
somebody on that list can update you on the status of Fedora Core 2 in
regard to
You better raise this issue at the [EMAIL PROTECTED] . Maybe
somebody on that list can update you on the status of Fedora Core 2 in
regard to this bug.
It's a kernel problem and will be fixed in 2.6.7. Maybe the fedora people
can backport the fix (= a bunch of changes in
