From: "Rafał Bilski" <rafalbilski@interia.pl>
To: cpufreq@lists.linux.org.uk
Subject: [Bug 6426] Working Longhaul driver removed from kernel
Date: Sat, 22 Apr 2006 22:42:55 +0200 [thread overview]
Message-ID: <444A954F.5030408@interia.pl> (raw)
> http://bugzilla.kernel.org/show_bug.cgi?id=6426
>
> ------- Additional Comments From davej at codemonkey.org.uk 2006-04-22 10:50 -------
> You got lucky. It's completely broken (In part due to the quirky hardware
> design of longhaul), and needs significant effort to fix.
> (There needs to be infrastructure work done to quiesce dma from IDE/SCSI during
> speed transitions, otherwise real bad things can happen ranging from lock-ups,
> to disk corruption.)
>
> It's possible you never hit it because you were using conservative which doesn't
> change the speed very often, however in some cases a single transition is enough
> to hit the bug.
>
I try to hang my machine. It's imposible with cpufreq. In worst case
there is 2-10 secs freeze. But only when delta f is big (example
532<->997). Only way to hang machine is "modprobe viafb" with hw accel
enabled.
----------------------------------------------------------------------
Swietnie zdjecia do poogladania >>> http://link.interia.pl/f192b
next reply other threads:[~2006-04-22 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 20:42 Rafał Bilski [this message]
[not found] <bug-6426-3570@http.bugzilla.kernel.org/>
2008-03-12 1:18 ` [Bug 6426] Working Longhaul driver removed from kernel bugme-daemon
-- strict thread matches above, loose matches on Subject: below --
2006-07-10 19:28 bugme-daemon
2006-05-17 14:07 bugme-daemon
2006-04-30 19:40 bugme-daemon
2006-04-22 17:50 bugme-daemon
2006-04-22 17:42 bugme-daemon
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=444A954F.5030408@interia.pl \
--to=rafalbilski@interia.pl \
--cc=cpufreq@lists.linux.org.uk \
/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