RE: Cpufreq on k8 with xen dom0

[xeb <xeb@mail.ru>]

geaaru wrote:
> 
> I have done another test: i insert powernow-k8 driver as module not
> built-in and now when i try to insert powernow-k8 kernel module i have a
> segfault (but seems that so, before do a segfault found cpu frequencies:
> 
> powernow-k8: Found 1 AMD Turion(tm) 64 Mobile Technology ML-30
> processors (version 2.00.00)
> powernow-k8:    0 : fid 0x8, vid 0x4
> powernow-k8:    1 : fid 0x0, vid 0x16
> powernow-k8:    0 : fid 0x8 (1600 MHz), vid 0x4
> powernow-k8:    1 : fid 0x0 (800 MHz), vid 0x16
> general protection fault: 0000 [1] SMP 
> CPU 0 
> Modules linked in: powernow_k8 snd_pcm_oss snd_mixer_oss snd_seq_dummy
> snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device rtc_sysfs rtc_dev
> rtc_proc rtc_core rtc_lib video processor ac button dm_crypt ipt_REJECT
> ipt_LOG xt_state nf_conntrack nfnetlink iptable_filter ip_tables
> x_tables pktcdvd psmouse radeon drm 8139too capability commoncap tsdev
> evdev usbmouse usbhid sdhci mmc_core ohci1394 ieee1394 snd_atiixp
> snd_atiixp_modem snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd
> soundcore snd_page_alloc ehci_hcd ohci_hcd
> Pid: 5485, comm: modprobe Not tainted 2.6.18-xen #2
> RIP: e030:[<ffffffff880a8060>]
> [<ffffffff880a8060>] :powernow_k8:pending_bit_stuck+0x10/0x20
> RSP: e02b:ffff880035ecdbd0  EFLAGS: 00010297
> RAX: 0000000000000000 RBX: 0000000000001600 RCX: 00000000c0010042
> RDX: ffffffffff578000 RSI: 0000000000000000 RDI: ffff880001e39420
> RBP: ffff880037b20200 R08: 0000000000000036 R09: 0000000000000000
> R10: ffff880037b20200 R11: 0000000000000002 R12: 0000000000000001
> R13: 000000000000000f R14: ffff8800367308c0 R15: ffff880036522730
> FS:  00002b9b7af5bae0(0000) GS:ffffffff806fc000(0000)
> knlGS:0000000000000000
> CS:  e033 DS: 0000 ES: 0000
> Process modprobe (pid: 5485, threadinfo ffff880035ecc000, task
> ffff8800009bd040)
> Stack:  ffffffff880a9d85 ffff880035ecdc68 0000000000000060
> ffff8800367308f8
>  00000001349ebf08 ffff880036522720 ffff880036522720 0000000000000002
>  0000000000000060 0000000100000001 ffffffff807741e8 ffffffff806a30a0
> Call Trace:
>  [<ffffffff880a9d85>] :powernow_k8:powernowk8_cpu_init+0xb45/0xdd0
>  [<ffffffff804e4884>] cpufreq_add_dev+0x174/0x540
>  [<ffffffff8022b6e3>] __wake_up+0x43/0x70
>  [<ffffffff8020d540>] monotonic_clock+0x50/0xa0
>  [<ffffffff805a54f5>] thread_return+0x0/0x13b
>  [<ffffffff805a54f5>] thread_return+0x0/0x13b
>  [<ffffffff804304f6>] sysdev_driver_register+0x96/0x100
>  [<ffffffff804e3947>] cpufreq_register_driver+0xc7/0x1b0
>  [<ffffffff80253faf>] sys_init_module+0x189f/0x1aa0
>  [<ffffffff8020a2ee>] system_call+0x86/0x8b
>  [<ffffffff8020a268>] system_call+0x0/0x8b
> 
> 
> Code: 0f 32 c1 e8 1f f3 c3 66 66 90 66 66 90 66 66 90 8b 57 60 85 
> RIP  [<ffffffff880a8060>] :powernow_k8:pending_bit_stuck+0x10/0x20
>  RSP <ffff880035ecdbd0>
> 
It seems you forgot to pass cpufreq option to xen hypervisor.

I have tested cpufreq patchset for K8 and it works fine. Frequencies
successfully switches from userspace. But i have tested it not long time.

-- 
View this message in context: http://www.nabble.com/Cpufreq-on-k8-with-xen-dom0-tf4515569.html#a12960971
Sent from the Xen - Dev mailing list archive at Nabble.com.