From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Wander Winkelhorst <w.winkelhorst@gmail.com>,
David Johnson <dj@david-web.co.uk>,
linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: cpufreq longhaul locks up
Date: Sat, 05 May 2007 21:58:51 +0200 [thread overview]
Message-ID: <463CE1FB.4050305@interia.pl> (raw)
In-Reply-To: <Pine.LNX.4.61.0705052028560.18504@yvahk01.tjqt.qr>
>> I found one line which wasn't were it should be. Probably this will not
>> fix Your problem with powersave governor, but it is a bit related.
>> Looks like Longhaul isn't skipping frequency transtition when it is asked
>> to set f which is already set. Now after first transition it will not
>> try to set same frequency again. Second part contains some magic
>> because I don't have CN400 datasheet. It is NDA protected :-( Should
>> print You one byte in hex and will try to set one register. I don't
>> know if anything will change but it is worth testing.
>
> Did not help unfortunately. The output the printk line generated was
> longhaul: 0x0
>
> (Strangely enough, %#02x with glibc outputs "00", not "0x0".
> And I would have expected "0x00". Subtleties of the kernel
> printk/glibc?)
:-/ Weird. Nothing new in datasheet. Longhaul MSR seems to be OK too.
Would be good to check if PLL really can go downto x4,0. Can You
limit minimal CPU multiplier to 5,0 and check if is stable? If it
is check 4,5.
Please send me below part of Your dmesg too:
CPU: After generic identify, caps: 0381b83f 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 64K (32 bytes/line)
CPU: After all inits, caps: 0381b93f 00000000 00000000 00000000 00000000 000000dd 00000000
"dd" is very important here.
> Jan
Rafa³
----------------------------------------------------------------------
Kasia Cichopek eksponuje biust
>>> http://link.interia.pl/f1a6f
WARNING: multiple messages have this Message-ID (diff)
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Wander Winkelhorst <w.winkelhorst@gmail.com>,
David Johnson <dj@david-web.co.uk>,
linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: cpufreq longhaul locks up
Date: Sat, 05 May 2007 21:58:51 +0200 [thread overview]
Message-ID: <463CE1FB.4050305@interia.pl> (raw)
In-Reply-To: <Pine.LNX.4.61.0705052028560.18504@yvahk01.tjqt.qr>
>> I found one line which wasn't were it should be. Probably this will not
>> fix Your problem with powersave governor, but it is a bit related.
>> Looks like Longhaul isn't skipping frequency transtition when it is asked
>> to set f which is already set. Now after first transition it will not
>> try to set same frequency again. Second part contains some magic
>> because I don't have CN400 datasheet. It is NDA protected :-( Should
>> print You one byte in hex and will try to set one register. I don't
>> know if anything will change but it is worth testing.
>
> Did not help unfortunately. The output the printk line generated was
> longhaul: 0x0
>
> (Strangely enough, %#02x with glibc outputs "00", not "0x0".
> And I would have expected "0x00". Subtleties of the kernel
> printk/glibc?)
:-/ Weird. Nothing new in datasheet. Longhaul MSR seems to be OK too.
Would be good to check if PLL really can go downto x4,0. Can You
limit minimal CPU multiplier to 5,0 and check if is stable? If it
is check 4,5.
Please send me below part of Your dmesg too:
CPU: After generic identify, caps: 0381b83f 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 64K (32 bytes/line)
CPU: After all inits, caps: 0381b93f 00000000 00000000 00000000 00000000 000000dd 00000000
"dd" is very important here.
> Jan
Rafał
----------------------------------------------------------------------
Kasia Cichopek eksponuje biust
>>> http://link.interia.pl/f1a6f
next prev parent reply other threads:[~2007-05-05 19:58 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 10:16 cpufreq longhaul locks up Jan Engelhardt
2007-05-04 11:36 ` Wander Winkelhorst
2007-05-04 11:51 ` Jan Engelhardt
2007-05-04 11:51 ` Jan Engelhardt
2007-05-04 17:08 ` Rafał Bilski
2007-05-04 17:08 ` Rafał Bilski
2007-05-04 17:42 ` Chuck Ebbert
2007-05-04 17:42 ` Chuck Ebbert
2007-05-04 18:40 ` Rafał Bilski
2007-05-04 18:08 ` Wander Winkelhorst
2007-05-04 19:00 ` Rafał Bilski
2007-05-04 19:00 ` Rafał Bilski
2007-05-04 18:48 ` Jan Engelhardt
2007-05-04 18:48 ` Jan Engelhardt
2007-05-04 20:11 ` Rafał Bilski
2007-05-04 20:11 ` Rafał Bilski
2007-05-04 21:03 ` Jan Engelhardt
2007-05-04 21:03 ` Jan Engelhardt
2007-05-04 20:37 ` john stultz
2007-05-04 21:02 ` Jan Engelhardt
2007-05-04 22:49 ` john stultz
2007-05-04 23:32 ` Jan Engelhardt
2007-05-05 4:03 ` Rafał Bilski
2007-05-05 8:00 ` Jan Engelhardt
2007-05-05 8:00 ` Jan Engelhardt
2007-05-05 13:58 ` Rafał Bilski
2007-05-05 13:58 ` Rafał Bilski
2007-05-05 18:13 ` Jan Engelhardt
2007-05-05 18:13 ` Jan Engelhardt
2007-05-04 22:20 ` David Johnson
2007-05-04 22:20 ` David Johnson
2007-05-04 23:37 ` Jan Engelhardt
2007-05-04 23:37 ` Jan Engelhardt
2007-05-05 5:40 ` Rafał Bilski
2007-05-05 5:40 ` Rafał Bilski
2007-05-05 8:44 ` Wander Winkelhorst
2007-05-05 14:02 ` Rafał Bilski
2007-05-05 14:02 ` Rafał Bilski
2007-05-05 17:48 ` Rafał Bilski
2007-05-05 17:48 ` Rafał Bilski
2007-05-05 18:42 ` Jan Engelhardt
2007-05-05 18:42 ` Jan Engelhardt
2007-05-05 19:58 ` Rafał Bilski [this message]
2007-05-05 19:58 ` Rafał Bilski
2007-05-05 20:30 ` Jan Engelhardt
2007-05-05 20:30 ` Jan Engelhardt
2007-05-05 20:50 ` Jan Engelhardt
2007-05-05 20:50 ` Jan Engelhardt
2007-05-05 21:32 ` Rafał Bilski
2007-05-06 7:53 ` Jan Engelhardt
2007-05-06 7:53 ` Jan Engelhardt
2007-05-06 5:12 ` Rafał Bilski
2007-05-06 5:12 ` Rafał Bilski
2007-05-06 8:03 ` Jan Engelhardt
2007-05-06 8:03 ` Jan Engelhardt
2007-05-06 9:23 ` Rafał Bilski
2007-05-06 9:23 ` Rafał Bilski
2007-05-06 9:32 ` Jan Engelhardt
2007-05-06 10:25 ` Rafał Bilski
2007-05-06 10:25 ` Rafał Bilski
2007-05-06 11:33 ` Jan Engelhardt
2007-05-06 12:20 ` Rafał Bilski
2007-05-05 9:37 ` Jan Engelhardt
2007-05-05 9:37 ` Jan Engelhardt
2007-05-05 14:10 ` Rafał Bilski
2007-05-05 14:10 ` Rafał Bilski
2007-05-05 17:38 ` Jan Engelhardt
2007-05-05 17:38 ` Jan Engelhardt
2007-05-05 18:04 ` Rafał Bilski
2007-05-05 18:04 ` Rafał Bilski
2007-05-05 18:23 ` Jan Engelhardt
2007-05-05 18:23 ` Jan Engelhardt
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=463CE1FB.4050305@interia.pl \
--to=rafalbilski@interia.pl \
--cc=cpufreq@lists.linux.org.uk \
--cc=dj@david-web.co.uk \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=w.winkelhorst@gmail.com \
/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.