Bug#415239: closed by Bastian Blank [EMAIL PROTECTED] (Re: Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8)
reopen 415239 thanks On Sun, May 27, 2007 at 11:30:04AM +, Debian Bug Tracking System wrote: Date: Sun, 27 May 2007 13:28:52 +0200 From: Bastian Blank [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8 X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,FROMDEVELOPER, HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 On Sat, Mar 17, 2007 at 11:20:50PM +1100, Hamish Moffatt wrote: Pid: 2954, comm: powernowd Tainted: P 2.6.18-4-amd64 #1 The kernel is tainted. We can't support this. I supplied reports of untainted 2.6.18-4-amd64 failing, earlier in this bug report. I will test untainted 2.6.21-1-amd64 too. It seems from the 2.6.18 testing that the tainting is not relevant. Hence I supplied a report against 2.6.21 with the same taint. Nonetheless I will do further tests. Thanks for being quite unhelpful. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#415239 closed by Bastian Blank [EMAIL PROTECTED] (Re: Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8)
Processing commands for [EMAIL PROTECTED]: reopen 415239 Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8 Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8
On Wed, Mar 21, 2007 at 02:45:19PM +0100, Oleg Verych wrote: So, if you are getting relieble crashes, please try * to get minimal test-case, * kernel targeted for experimental/sid: deb http://kernel-archive.buildserver.net/debian-kernel trunk main * or latest upsteam one. And please collect and send all fault logs. This can be useful, when tracing problems. There's one similar report in lkml, i've found: Archived-At: http://permalink.gmane.org/gmane.linux.kernel/474449 Message-ID: [EMAIL PROTECTED] But it have no follow-ups. Thus, as more info you can collect, more chance we can get upsteam interested. I tried the 2.6.20 package from buildserver.net. It crashed similarly. Yes I had the nvidia driver loaded as usual :-| I will try upstream 2.6.20 asap. Hamish Mar 24 17:52:47 noddy kernel: general protection fault: [1] SMP Mar 24 17:52:47 noddy kernel: CPU 1 Mar 24 17:52:47 noddy kernel: Modules linked in: tcp_diag inet_diag binfmt_misc rfcomm l2cap bluetooth nvidia(P) nfs lockd nfs_acl sunrpc tun ipt_ULOG ipt_recent nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables mkiss ax25 crc16 ipv6 parport_serial parport_pc dm_snapshot dm_mirror dm_mod it87 hwmon_vid i2c_isa lp parport cpufreq_ondemand powernow_k8 freq_table processor ide_disk ide_generic ide_cd cdrom eth1394 pata_amd usb_storage snd_ens1371 snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_seq_device skge ohci1394 ieee1394 sata_sil tsdev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd amd74xx i2c_nforce2 shpchp k8temp psmouse i2c_core ohci_hcd ehci_hcd forcedeth pci_hotplug soundcore serio_raw snd_page_alloc floppy analog gameport pcspkr ext3 jbd mbcache raid1 md_mod sd_mod ata_generic sata_nv libata scsi_mod generic ide_core evdev Mar 24 17:52:47 noddy kernel: Pid: 7383, comm: exim4 Tainted: P 2.6.20-1-amd64 #1 Mar 24 17:52:47 noddy kernel: RIP: 0010:[80221c2d] [80221c2d] vma_prio_tree_remove+0x29/0xe0 Mar 24 17:52:47 noddy kernel: RSP: 0018:81004d1d9e48 EFLAGS: 00010246 Mar 24 17:52:47 noddy kernel: RAX: fffc810060e6a700 RBX: RCX: 2b6487493000 Mar 24 17:52:47 noddy kernel: RDX: 81007ebc9b20 RSI: 81001080af40 RDI: 81001080aef8 Mar 24 17:52:47 noddy kernel: RBP: 8100638e3680 R08: 81007d715538 R09: 81007fe76f06 Mar 24 17:52:47 noddy kernel: R10: 81001080aef8 R11: 810012e994b0 R12: 81001080aef8 Mar 24 17:52:47 noddy kernel: R13: 2b6485f2c000 R14: R15: Mar 24 17:52:47 noddy kernel: FS: 2b6487170f20() GS:81007fe76e40() knlGS: Mar 24 17:52:47 noddy kernel: CS: 0010 DS: ES: CR0: 8005003b Mar 24 17:52:47 noddy kernel: CR2: 2b6486ac7d44 CR3: 22ed8000 CR4: 06e0 Mar 24 17:52:47 noddy kernel: Process exim4 (pid: 7383, threadinfo 81004d1d8000, task 810067da1850) Mar 24 17:52:47 noddy kernel: Stack: 005d5fff 81007d715518 8100638e3680 8021c6ed Mar 24 17:52:47 noddy kernel: 81001080ae48 81001080aef8 81001080ae48 8021caab Mar 24 17:52:47 noddy kernel: 81004d1d9ed0 81004d1d9ed0 81007e8f0e48 81006b618540 Mar 24 17:52:47 noddy kernel: Call Trace: Mar 24 17:52:47 noddy kernel: [8021c6ed] unlink_file_vma+0x31/0x3d Mar 24 17:52:47 noddy kernel: [8021caab] free_pgtables+0x69/0x98 Mar 24 17:52:47 noddy kernel: [80236228] exit_mmap+0x91/0xeb Mar 24 17:52:47 noddy kernel: [80238126] mmput+0x28/0x98 Mar 24 17:52:47 noddy kernel: [80213783] do_exit+0x214/0x7ff Mar 24 17:52:47 noddy kernel: [80243395] cpuset_exit+0x0/0x6b Mar 24 17:52:47 noddy kernel: [8025611e] system_call+0x7e/0x83 Mar 24 17:52:47 noddy kernel: Mar 24 17:52:47 noddy kernel: Mar 24 17:52:47 noddy kernel: Code: 48 89 10 48 89 76 08 48 89 77 48 e9 a3 00 00 00 4c 89 c7 41 Mar 24 17:52:47 noddy kernel: RIP [80221c2d] vma_prio_tree_remove+0x29/0xe0 Mar 24 17:52:47 noddy kernel: RSP 81004d1d9e48 Mar 24 17:52:47 noddy kernel: 1Fixing recursive fault but reboot is needed! Mar 24 17:53:34 noddy kernel: BUG: soft lockup detected on CPU#0! Mar 24 17:53:34 noddy kernel: Mar 24 17:53:34 noddy kernel: Call Trace: Mar 24 17:53:34 noddy kernel: IRQ [802a3cbe] softlockup_tick+0xdb/0xed Mar 24 17:53:34 noddy kernel: [802862f3] update_process_times+0x42/0x68 Mar 24 17:53:34 noddy kernel: [8026ada0] smp_local_timer_interrupt+0x34/0x55 Mar 24 17:53:34 noddy kernel: [8026b467] smp_apic_timer_interrupt+0x52/0x6a Mar 24 17:53:34 noddy kernel: [80256ce6] apic_timer_interrupt+0x66/0x70 Mar 24 17:53:34 noddy kernel: EOI [8025c76f] _spin_lock+0x5/0xf Mar 24 17:53:34 noddy kernel: [8021d75e] copy_process+0xb7e/0x13a2 Mar 24 17:53:34 noddy kernel:
Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8
On Sun, Mar 25, 2007 at 10:49:30PM +1000, Hamish Moffatt wrote: [] I tried the 2.6.20 package from buildserver.net. It crashed similarly. Yes I had the nvidia driver loaded as usual :-| Full dmesg and without nvidia, please. I will try upstream 2.6.20 asap. Latest upstream is 2.6.21-rc5 (:. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8
On Wed, Mar 21, 2007 at 06:54:55PM +1100, Hamish Moffatt wrote: [] It runs perfectly stable after 'cpufreq-set -g performance', so I don't think I can rule out the cpufreq stuff. Or ACPI, or SMP PREEMPT. Can you redo your previous observations without taining also? Maybe powernow-k8 and nvidia just can't go together. Which previous observations do you mean? Same results you've mentioned before. With either cpufreq-userspace or cpufreq-ondemand, it crashes, with or without nvidia. With cpufreq set to performance mode it is stable. I don't know of any other cases to test? So, if you are getting relieble crashes, please try * to get minimal test-case, * kernel targeted for experimental/sid: deb http://kernel-archive.buildserver.net/debian-kernel trunk main * or latest upsteam one. And please collect and send all fault logs. This can be useful, when tracing problems. There's one similar report in lkml, i've found: Archived-At: http://permalink.gmane.org/gmane.linux.kernel/474449 Message-ID: [EMAIL PROTECTED] But it have no follow-ups. Thus, as more info you can collect, more chance we can get upsteam interested. _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8
On Sat, Mar 17, 2007 at 07:52:37PM +0100, Oleg Verych wrote: general protection fault: [1] SMP CPU 0 Modules linked in: tcp_diag inet_diag binfmt_misc rfcomm l2cap bluetooth nvidia nfs lockd nfs_acl sunrpc tun ipt_ULOG ipt_recent xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables mkiss ax25 crc16 ipv6 parport_serial parport_pc dm_snapshot dm_mirror dm_mod it87 hwmon_vid i2c_isa lp parport cpufreq_userspace powernow_k8 freq_table processor ide_disk ide_generic ide_cd cdrom eth1394 tsdev snd_ens1371 snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_seq_device snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer ohci1394 snd amd74xx sata_sil ieee1394 i2c_nforce2 psmouse soundcore skge i2c_core serio_raw pcspkr snd_page_alloc forcedeth ohci_hcd ehci_hcd floppy shpchp pci_hotplug analog gameport ext3 jbd mbcache raid1 md_mod sd_mod generic ide_core sata_nv libata scsi_mod evdev Pid: 2954, comm: powernowd Tainted: P 2.6.18-4-amd64 #1 (1) ^ RIP: 0010:[8028a7bb] [8028a7bb] notifier_call_chain+0x11/0x32 RSP: 0018:810073cf5db8 EFLAGS: 00010282 RAX: RBX: fffc882cd110 RCX: fffc882cd110 RDX: 000649c5 RSI: 03e8 RDI: 80522090 RBP: 810073cf5e18 R08: R09: 0006 R10: 0001 R11: R12: R13: R14: R15: 002191c0 FS: 2af4ab0f56d0() GS:80521000() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 2b917a438000 CR3: 74ef3000 CR4: 06e0 Process powernowd (pid: 2954, threadinfo 810073cf4000, task 8100740d77f0) (2) ^ Try to not use proprietary modules, powernowd daemon (use ondemand driver) and reproduce that. OK, I will try all that asap (tomorrow hopefully). Two more observations since then; 1. It does crash under heavy load, if powernow-k8 is loaded (+ powernowd + cpufreq_userspace). 2. If I remove the frequency govenor stuff (stop powernowd, remove all modules) then it's perfectly stable. The tainting was caused by the nvidia module, btw. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8
On Mon, Mar 19, 2007 at 06:50:10PM +1100, Hamish Moffatt wrote: On Sat, Mar 17, 2007 at 07:52:37PM +0100, Oleg Verych wrote: [] Try to not use proprietary modules, powernowd daemon (use ondemand driver) and reproduce that. OK, I will try all that asap (tomorrow hopefully). Two more observations since then; 1. It does crash under heavy load, if powernow-k8 is loaded (+ powernowd + cpufreq_userspace). This daemon seems obsolete to me: last release is more than year ago, there's ondemand governor, no problems with brain-damage like sysfs. 2. If I remove the frequency govenor stuff (stop powernowd, remove all modules) then it's perfectly stable. As i saw so many problems with sysfs (in lkml), i doubt it will get better anyway. Even bug was reported against ondemand governor, and it turned to be this daemon was running (:. Why ondemand governor is bad? The tainting was caused by the nvidia module, btw. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8
On Mon, Mar 19, 2007 at 10:37:04AM +0100, Oleg Verych wrote: On Mon, Mar 19, 2007 at 06:50:10PM +1100, Hamish Moffatt wrote: On Sat, Mar 17, 2007 at 07:52:37PM +0100, Oleg Verych wrote: [] Try to not use proprietary modules, powernowd daemon (use ondemand driver) and reproduce that. OK, I will try all that asap (tomorrow hopefully). Two more observations since then; 1. It does crash under heavy load, if powernow-k8 is loaded (+ powernowd + cpufreq_userspace). This daemon seems obsolete to me: last release is more than year ago, there's ondemand governor, no problems with brain-damage like sysfs. 2. If I remove the frequency govenor stuff (stop powernowd, remove all modules) then it's perfectly stable. As i saw so many problems with sysfs (in lkml), i doubt it will get better anyway. Even bug was reported against ondemand governor, and it turned to be this daemon was running (:. Why ondemand governor is bad? Hi, I have been using userspace/powernowd because it worked for me until now. I have no preference though. I just switched to the ondemand governor and it seems to be working so far. Should cpufreq-userspace be removed if it can cause general protection faults? Thanks for your help. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8
On Tue, Mar 20, 2007 at 12:09:30AM +1100, Hamish Moffatt wrote: [] Why ondemand governor is bad? Hi, I have been using userspace/powernowd because it worked for me until now. I have no preference though. I just switched to the ondemand governor and it seems to be working so far. Should cpufreq-userspace be removed if it can cause general protection faults? That was daemon's problem, maybe some rules has changed since 2.6.16 or so, when it was updated. The userspace governor works form me, i setup laptop on minimum, and if building a kernel switch on maximum: cd /sys/devices/system/cpu/cpu0/cpufreq/ echo userspace scaling_governor ddscaling_min_freqscaling_setspeed # or max here cd /tmp Another crash in your original report is related to cpu hotplug, but it seems a known problem and work-in-progress: ,-*- |Message-ID: [EMAIL PROTECTED] |Archived-At: http://permalink.gmane.org/gmane.linux.kernel/479386 | |Yet another attempt to resolve cpufreq and hotplug locking issues. `-*- I don't know how broken it may be in 2.6.18 with all debian's updates. Maybe cpu-hot-plug isn't useful for default kernel, i also don't know. Close bugreport, please, if problem will strike again you may reopen it. Thanks for your help. Thank you. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8
Package: linux-image-2.6.18-4-amd64 Version: 2.6.18.dfsg.1-11 Severity: normal I'm running AMD64 x2 4200 (ie dual-core). I've only just upgraded from 2.6.17, which was working fine. Soon after boot I get a general protection fault; general protection fault: [1] SMP CPU 0 Modules linked in: tcp_diag inet_diag binfmt_misc rfcomm l2cap bluetooth nvidia nfs lockd nfs_acl sunrpc tun ipt_ULOG ipt_recent xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables mkiss ax25 crc16 ipv6 parport_serial parport_pc dm_snapshot dm_mirror dm_mod it87 hwmon_vid i2c_isa lp parport cpufreq_userspace powernow_k8 freq_table processor ide_disk ide_generic ide_cd cdrom eth1394 tsdev snd_ens1371 snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_seq_device snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer ohci1394 snd amd74xx sata_sil ieee1394 i2c_nforce2 psmouse soundcore skge i2c_core serio_raw pcspkr snd_page_alloc forcedeth ohci_hcd ehci_hcd floppy shpchp pci_hotplug analog gameport ext3 jbd mbcache raid1 md_mod sd_mod generic ide_core sata_nv libata scsi_mod evdev Pid: 2954, comm: powernowd Tainted: P 2.6.18-4-amd64 #1 RIP: 0010:[8028a7bb] [8028a7bb] notifier_call_chain+0x11/0x32 RSP: 0018:810073cf5db8 EFLAGS: 00010282 RAX: RBX: fffc882cd110 RCX: fffc882cd110 RDX: 000649c5 RSI: 03e8 RDI: 80522090 RBP: 810073cf5e18 R08: R09: 0006 R10: 0001 R11: R12: R13: R14: R15: 002191c0 FS: 2af4ab0f56d0() GS:80521000() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 2b917a438000 CR3: 74ef3000 CR4: 06e0 Process powernowd (pid: 2954, threadinfo 810073cf4000, task 8100740d77f0) Stack: 80478040 81007aa9dac0 810073cf5e18 8028abc4 0012 000e 882c6820 8101 81007b5fa600 00087b0bbf20 Call Trace: [8028abc4] blocking_notifier_call_chain+0x22/0x36 [882c6820] :powernow_k8:powernowk8_target+0x2d1/0x647 [882cc202] :cpufreq_userspace:store_speed+0x8d/0xab [80268dc0] store+0x44/0x5b [802e1404] sysfs_write_file+0xb4/0xe3 [80214966] vfs_write+0xce/0x174 [802151f0] sys_write+0x45/0x6e [802584d6] system_call+0x7e/0x83 The system seems to keep running though I haven't stressed it to see if it changes frequency succesfully. Some time later I've also had the following (3 times); don't know if it's related, but I wasn't hotplugging anything at the time: Lukewarm IQ detected in hotplug locking BUG: warning at kernel/cpu.c:38/lock_cpu_hotplug() Call Trace: [8029472b] lock_cpu_hotplug+0x50/0x73 [8027e257] sched_getaffinity+0x17/0x93 [8027e2f9] sys_sched_getaffinity+0x26/0x55 [802584d6] system_call+0x7e/0x83 Hamish -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages linux-image-2.6.18-4-amd64 depends on: ii coreutil 5.97-5.3The GNU core utilities ii debconf 1.5.13 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib ii module-i 3.3-pre4-2 tools for managing Linux kernel mo ii yaird [l 0.0.12-18 Yet Another mkInitRD linux-image-2.6.18-4-amd64 recommends no packages. -- debconf information: linux-image-2.6.18-4-amd64/postinst/kimage-is-a-directory: linux-image-2.6.18-4-amd64/postinst/bootloader-test-error-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/lilo-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/initrd-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/failed-to-move-modules-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/old-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-amd64/postinst/old-dir-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/prerm/removing-running-kernel-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/already-running-this-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/abort-install-2.6.18-4-amd64: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-amd64/preinst/abort-overwrite-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/depmod-error-initrd-2.6.18-4-amd64: false linux-image-2.6.18-4-amd64/postinst/create-kimage-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/postinst/depmod-error-2.6.18-4-amd64: false
