GNOME Bugzilla – Bug 168550
Change monitoring CPU to CPU1 whit a P4 Hyper Threading processor
Last modified: 2010-01-24 01:07:45 UTC
Distribution: Debian 3.1 Package: gnome-applets Severity: normal Version: GNOME2.9.91 2.9.x Gnome-Distributor: Ubuntu Synopsis: abnormal app exit Bugzilla-Product: gnome-applets Bugzilla-Component: cpufreq Bugzilla-Version: 2.9.x BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: Steps to reproduce the crash: 1. enter properties 2. change to CPU 1 (from the default 0) 3. app crashes Expected Results: app exits How often does this happen? everytime Additional Information: linux-image-2.6.10-4-686-smp Debugging Information: Backtrace was generated from '/usr/libexec/cpufreq-applet' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1222847840 (LWP 9237)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in ?? ()
+ Trace 56151
Thread 1 (Thread -1222847840 (LWP 9237))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-25 16:20 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-applets". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was rezydent@gmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** Bug 170036 has been marked as a duplicate of this bug. ***
A P4 Hyper Threading processor seems to trigger this according to the duplicate. Bumping version to 2.10 because of the dup. Err.. to CVS HEAD then. Retitling. Confirming because the duplicate describes same steps to reproduce.
I'm not in a SMP system, so I need more information: $ cat /proc/cpuinfo $ ls -l /sys/devices/system/cpu/cpu0/cpufreq/ $ ls -l /sys/devices/system/cpu/cpu1/cpufreq/ Could you give me the output of those commands, please?
*** Bug 300316 has been marked as a duplicate of this bug. ***
This may still be an issue. Will have to locate a HT enabled machine to confirm.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!