From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 13489] us2e_cpufreq does not work on Netra t1 200
Date: Wed, 18 Jan 2012 22:41:08 GMT [thread overview]
Message-ID: <201201182241.q0IMf8pH017240@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-13489-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=13489
--- Comment #5 from Jos van der Ende <seraph@xs4all.nl> 2012-01-18 22:41:07 ---
Wow, been a while since I reported this one.
I've just tested with a 3.1.6 kernel with Gentoo patches. Yes, the problem
still exists; loading the us2e-cpufreq mod caused an immediate hard reset.
I'll try with vanilla 3.2.1 as soon as I have some more time, but I have no
reason to assume the result will be any different.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-01-18 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13489-12968@https.bugzilla.kernel.org/>
2012-01-18 1:50 ` [Bug 13489] us2e_cpufreq does not work on Netra t1 200 bugzilla-daemon
2012-01-18 22:41 ` bugzilla-daemon [this message]
2012-05-13 14:39 ` bugzilla-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=201201182241.q0IMf8pH017240@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@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.