[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
I can absolutely verify and confirm that I get the same results as everyone in this thread: Whether or not the CPU is running at 3.0GHz or is overclocked to 3.6GHz, the reported speed always remains 3.0Ghz. The output of both dmidecode and by checking the actual processing speed with any application (bogomips), shows the exact overclocking ratio when compared to stock - as expected. While it is only a reporting issue, as the CPU performance is correct - it does mean that I'm (always) multiplying the actual CPU speeds by 1.2 (3.6/3.0 GHz) for any performance calculations I might be doing. The probable issue here is that dmidecode is collecting the correct bus overclocking information from the BIOS, and using that in the calculations; whereas cpufrequtils is either only collecting the stock information, or is defaulting to a standardised set of values; if for some reason the true information is unavailable (BIOS issues?). (ASUS P5Q Motherboard) I have to say ... OPINION is actually an interesting (and can be quite useful) project status, however, I can absolutely CONFIRM this as an issue, and am available for any further testing or analysis. -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
Yes, the problem is still the same under Lucid - all latest updates: Linux thundercat 2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:20:59 UTC 2010 x86_64 GNU/Linux Still the same machine and same processor ... have upgraded throughout and no change. 9.10 full reinstall 10.04 synaptic upgrade CPU has been overclocked from stock 3.00GHz to 3.60GHz. This can be confirmed through dmidecode (output attached). cpuinfo (and related utilities) all report the stock CPU speeds instead. This is only a visual/reporting issue. The CPU is still throttling correctly, and the speed is correct as per the overclocking ratio. i.e. (tested and confirmed in benchmarks Bogomips) Reported 2.00Ghz = (3.6/3.0 * 2.0) = 2.40GHz True Clock Speed Reported 3.00Ghz = (3.6/3.0 * 3.0) = 3.60GHz True Clock Speed Fully up to date BIOS, (ASUS P5Q) - BIOS options standard except for overclock. Output of dmidecode and cpuinfo attached. Regards, Robert. ** Attachment added: cat /proc/cpuinfo http://launchpadlibrarian.net/52812470/cpuinfo -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
** Attachment added: output of dmidecode http://launchpadlibrarian.net/52812514/dmidecode -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
Ran the command: - Authorised apport-collect to access LaunchPad Output of command (for reference) rob...@thundercat:~$ apport-collect -p cpufrequtils 379873 The authorization page: (https://edge.launchpad.net/+authorize-token?oauth_token=858h97qhLdpKlW3VJzKDallow_permission=WRITE_PRIVATE) should be opening in your browser. After you have authorized this program to access Launchpad on your behalf you should come back here and press Enter to finish the authentication process. Created new window in existing browser session. Package cpufrequtils not installed and no hook available, ignoring rob...@thundercat:~$ Should I install cpufrequtils first? At present they have not been installed. Cheers, Robert. -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
apport information ** Tags added: apport-collected ** Description changed: The reported frequencies of an overclocked Core 2 Duo are incorrect. Benchmarking and performance testing can confirm that the CPU is running at the overclocked speeds, but the values reported through cpuinfo are the standard stock speeds. CPU has been overclocked from stock 3.00GHz to 3.60GHz. This can be confirmed through dmidecode (output attached). The issue is that cpuinfo (and related utilities) all report the stock CPU speeds instead. This is only a visual/reporting issue. The CPU is still throttling correctly, and the speed is correct as per the overclocking ratio. i.e. (tested and confirmed in benchmarks Bogomips) Reported 2.00Ghz = (3.6/3.0 * 2.0) = 2.40GHz True Clock Speed Reported 3.00Ghz = (3.6/3.0 * 3.0) = 3.60GHz True Clock Speed There are a few reports of this in the Ubuntu forums, however no resolution had been found. I have updated the BIOS on my motherboard (ASUS P5Q) to the latest available, with no changes. All other BIOS options are per standard - allowing CPU throttling/etc. Bug #132403 makes reference to this similar issue, but this is not a BIOS problem, only a reporting problem. Compare: cat /proc/cpuinfo cpufreq-info dmidecode --type processor Only dmidecode is reporting the correct CPU speed as set in the BIOS. Regards, Robert. + --- + Architecture: amd64 + DistroRelease: Ubuntu 10.04 + InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) + NonfreeKernelModules: nvidia + Package: cpufrequtils 006-2 + PackageArchitecture: amd64 + ProcEnviron: + LANG=en_NZ.utf8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 + Tags: lucid + Uname: Linux 2.6.32-24-generic x86_64 + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/52818649/Dependencies.txt -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
Checked the output of: cat /proc/cpuinfo - (Same as attached) dmidecode - (Same as attached) cpufreq-info (Output below) --- r...@thundercat:~# cpufreq-info cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 2.00 GHz - 3.00 GHz available frequency steps: 3.00 GHz, 2.67 GHz, 2.34 GHz, 2.00 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 2.00 GHz and 3.00 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 2.00 GHz (asserted by call to hardware). cpufreq stats: 3.00 GHz:1.52%, 2.67 GHz:0.04%, 2.34 GHz:0.03%, 2.00 GHz:98.41% (250583) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us. hardware limits: 2.00 GHz - 3.00 GHz available frequency steps: 3.00 GHz, 2.67 GHz, 2.34 GHz, 2.00 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 2.00 GHz and 3.00 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 2.00 GHz (asserted by call to hardware). cpufreq stats: 3.00 GHz:1.67%, 2.67 GHz:0.03%, 2.34 GHz:0.04%, 2.00 GHz:98.26% (226133) r...@thundercat:~# Hope this helps, Robert. -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
** Attachment added: Output of cat /proc/cpuinfo http://launchpadlibrarian.net/27103170/cpuinfo -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] [NEW] CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
Public bug reported: The reported frequencies of an overclocked Core 2 Duo are incorrect. Benchmarking and performance testing can confirm that the CPU is running at the overclocked speeds, but the values reported through cpuinfo are the standard stock speeds. CPU has been overclocked from stock 3.00GHz to 3.60GHz. This can be confirmed through dmidecode (output attached). The issue is that cpuinfo (and related utilities) all report the stock CPU speeds instead. This is only a visual/reporting issue. The CPU is still throttling correctly, and the speed is correct as per the overclocking ratio. i.e. (tested and confirmed in benchmarks Bogomips) Reported 2.00Ghz = (3.6/3.0 * 2.0) = 2.40GHz True Clock Speed Reported 3.00Ghz = (3.6/3.0 * 3.0) = 3.60GHz True Clock Speed There are a few reports of this in the Ubuntu forums, however no resolution had been found. I have updated the BIOS on my motherboard (ASUS P5Q) to the latest available, with no changes. All other BIOS options are per standard - allowing CPU throttling/etc. Bug #132403 makes reference to this similar issue, but this is not a BIOS problem, only a reporting problem. Compare: cat /proc/cpuinfo cpufreq-info dmidecode --type processor Only dmidecode is reporting the correct CPU speed as set in the BIOS. Regards, Robert. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: cpufreq cpufreq-info cpuinfo dmidecode -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
** Attachment added: Output of cpufreq-info http://launchpadlibrarian.net/27103182/cpufreq-info -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
** Attachment added: Output of dmidecode http://launchpadlibrarian.net/27103190/dmidecode -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked
Apologies - neglected to report on Ubuntu/kernel version information: Description: Ubuntu 9.04 Release: 9.04 Linux thundercat 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux All latest updates/patches as available on May 24, 2009 -- CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked https://bugs.launchpad.net/bugs/379873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318465] Re: Logitech MX5000 doesn't connect via bluetooth under ubuntu
I'm using the Logitech MX5500 Bluetooth, and other than needing to add the numlockx startup fix, everything is now working out of the box on Jaunty 9.04 (fresh installation). I no longer need to use the USB HID mode (disable bluez) as I did in 8.04 and 8.10, and instead finally! have both keyboard and mouse (MX Revolution) paired properly through the Bluetooth Manager. Bluetooth devices (headphones) also work through the same dongle. The only thing I need to do on startup is 'bash' on the modifier keys (Shift, Ctrl, Alt, Super, Caps Lock) at least once before trying to use the keyboard. Possibly there is something in bluez which is not initialising the keyboard 100% properly - i.e. the problem which Jack is experiencing and my modifier keys issue above may somehow be related. This also happens after the computer has been idle (screen black, or screen saver starts), and I've become quite used to toggling all modifiers before starting work again. So it may or may not have anything to do with bluez itself, or it may have something to do with power management or other system elements. Robert. -- Logitech MX5000 doesn't connect via bluetooth under ubuntu https://bugs.launchpad.net/bugs/318465 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218259] Re: mythfilldatabase crashed with SIGSEGV in QMutex::lock()
I had reinstalled, reconfigured, everything ... no luck ... but i'ts not a problem any more. I gave up on trying to resolve it, threw out all the hardware and bought brand new equipment. Barring a few configuration hiccups, everything went smoothly with the new gear. Problem was never resolved, but you can mark the bug as closed, as there will not be any more information I can provide. -- mythfilldatabase crashed with SIGSEGV in QMutex::lock() https://bugs.launchpad.net/bugs/218259 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211700] Re: mythfilldatabase crashed with SIGSEGV in QMutex::lock()
I had reinstalled, reconfigured, everything ... no luck ... but i'ts not a problem any more. I gave up on trying to resolve it, threw out all the hardware and bought brand new equipment. Barring a few configuration hiccups, everything went smoothly with the new gear. Problem was never resolved, but you can mark the bug as closed, as there will not be any more information I can provide. -- mythfilldatabase crashed with SIGSEGV in QMutex::lock() https://bugs.launchpad.net/bugs/211700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211700] Re: mythfilldatabase crashed with SIGSEGV in QMutex::lock()
Marked to Invalid - no further information can be provided - too long ago, now have new equipment. ** Changed in: mythtv (Ubuntu) Status: Incomplete = Invalid -- mythfilldatabase crashed with SIGSEGV in QMutex::lock() https://bugs.launchpad.net/bugs/211700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204991] Re: update-manager leaves screen gray after sudo authentication
I have the same effect happening - specifically with gksudo. The screen remains 'darkened', and I can subsequently move windows around and 're- paint' the sections of the screen. Similarly, moving over buttons, panels, etc. which are redrawn, also corrects the screen display. XFCE desktop / mythbuntu installation, compiz installed and active, nVidia Twinview monitor setup. The effect happens at all screen resolutions, so it is not video memory (128Mb) dependent. I also have some corruption when windows are initially drawn (window edge trails), but this is minor. -- update-manager leaves screen gray after sudo authentication https://bugs.launchpad.net/bugs/204991 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211700] Re: mythfilldatabase crashed with SIGSEGV in QMutex::lock()
Unfortunately, the same issue is still happening ... can't seem to figure out what/why this would be happening, as it's always occurring when there is no MythTV usage. XMLTV grabber appears to complete perfectly ... about to try disabling anything/everything else just to see what (if any) interaction may be at fault. Again - unreportable because of obsolete packages (which weren't involved in the crash itself) ... --- ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Tue Apr 15 04:31:18 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/mythfilldatabase NonfreeKernelModules: nvidia ProcCmdline: /usr/bin/mythfilldatabase ProcCwd: /home/mythtv/.mythtv/channels ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin Disassembly: 0x815a757: add%cl,-0x57f7ea5a(%eax) 0x815a75d: push %eax 0x815a75e: pop%ss 0x815a75f: or %al,(%eax) 0x815a761: add%al,(%eax) 0x815a763: add%al,(%eax) 0x815a765: add%al,(%eax) 0x815a767: add%dh,(%eax) 0x815a769: movsl %ds:(%esi),%es:(%edi) 0x815a76a: adc$0x8,%eax 0x815a76f: add%al,(%eax) 0x815a771: add%al,(%eax) 0x815a773: add%dl,0x815a7(%eax) 0x815a779: add%al,(%eax) 0x815a77b: add%al,(%eax) 0x815a77d: add%al,(%eax) Package: mythtv-backend 0.21.0+fixes16838-0ubuntu2 PackageArchitecture: i386 Registers: eax0x815a5e8 135636456 ecx0x1 1 edx0x815a750 135636816 ebx0xb6dc3794 -1227081836 esp0xb480401c 0xb480401c ebp0xb4804028 0xb4804028 esi0xb48040e8 -123192 edi0xb48040e4 -123196 eip0x815a757 0x815a757 eflags 0x10286 [ PF SF IF RF ] cs 0x73115 ss 0x7b123 ds 0x7b123 es 0x7b123 fs 0x0 0 gs 0x3351 SourcePackage: mythtv Stacktrace: #0 0x0815a757 in ?? () #1 0xb6533ea6 in QMutex::lock () from /usr/lib/libqt-mt.so.3 #2 0xb6baface in MythContext::ClearSettingsCache () from /usr/lib/libmyth-0.21.so.0 #3 0xb6bb4caa in MythContext::readyRead () from /usr/lib/libmyth-0.21.so.0 #4 0xb6c158fd in readyReadThread_iffound () from /usr/lib/libmyth-0.21.so.0 #5 0xb6c16245 in MythSocket::readyReadThread () from /usr/lib/libmyth-0.21.so.0 #6 0xb5cd64fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb5b34e5e in clone () from /lib/tls/i686/cmov/libc.so.6 StacktraceTop: ?? () QMutex::lock () from /usr/lib/libqt-mt.so.3 MythContext::ClearSettingsCache () MythContext::readyRead () from /usr/lib/libmyth-0.21.so.0 readyReadThread_iffound () from /usr/lib/libmyth-0.21.so.0 ThreadStacktrace: . Thread 2 (process 12119): #0 0xb7eeb410 in __kernel_vsyscall () #1 0xb5cdd589 in __lll_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb5cd8ba6 in _L_lock_95 () from /lib/tls/i686/cmov/libpthread.so.0 #3 0xb5cd858a in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 #4 0xb653435b in QRecursiveMutexPrivate::lock () from /usr/lib/libqt-mt.so.3 #5 0xb6533ea6 in QMutex::lock () from /usr/lib/libqt-mt.so.3 #6 0x08077cff in ?? () #7 0xb5a74450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #8 0x0804e4a1 in ?? () . Thread 1 (process 12124): #0 0x0815a757 in ?? () #1 0xb6533ea6 in QMutex::lock () from /usr/lib/libqt-mt.so.3 #2 0xb6baface in MythContext::ClearSettingsCache () from /usr/lib/libmyth-0.21.so.0 #3 0xb6bb4caa in MythContext::readyRead () from /usr/lib/libmyth-0.21.so.0 #4 0xb6c158fd in readyReadThread_iffound () from /usr/lib/libmyth-0.21.so.0 #5 0xb6c16245 in MythSocket::readyReadThread () from /usr/lib/libmyth-0.21.so.0 #6 0xb5cd64fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb5b34e5e in clone () from /lib/tls/i686/cmov/libc.so.6 Title: mythfilldatabase crashed with SIGSEGV in QMutex::lock() UnreportableReason: You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs: sysv-rc, libdbus-glib-1-2 -- mythfilldatabase crashed with SIGSEGV in QMutex::lock() https://bugs.launchpad.net/bugs/211700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211700] Re: mythfilldatabase crashed with SIGSEGV in QMutex::lock()
Unfortunately the story is still the same - when everything is idle, there is an unexplained crash. Again I have simply restarted the machine, and left it idle. No access, no MythTV usage, only samba access which works flawlessly, and was not occurring at the time of the crash. The only thing I can come up with which could be happening at 5am would be an XMLTV Listings update. However, the listing information appears to be completely available and valid/correct within MythTV. Possibly this is occurring during a cleanup/update information operation after the XMLTV Listings update. As I reside in New Zealand, I'm using the tv_grab_nz-py script to perform the update (download/source can be found here: http://nice.net.nz/tv_grab_nz-py) Again - can't upload full report (more updated dependency packages!), so copying out relevant information: ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sun Apr 13 05:07:38 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/mythfilldatabase NonfreeKernelModules: nvidia ProcCmdline: /usr/bin/mythfilldatabase ProcCwd: /home/mythtv/.mythtv/channels ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin Disassembly: 0x8173e62: pop%ss 0x8173e63: or %al,(%eax) 0x8173e65: add%al,(%eax) 0x8173e67: add%al,(%eax) 0x8173e69: add%al,(%eax) 0x8173e6b: add%al,(%eax) 0x8173e6d: add%al,(%eax) 0x8173e6f: add%bh,%bh 0x8173e71: (bad) 0x8173e72: (bad) 0x8173e73: incl (%eax) 0x8173e75: add%al,(%eax) 0x8173e77: add%al,(%eax) 0x8173e79: add%al,(%eax) 0x8173e7b: add%al,(%eax) 0x8173e7d: add%dh,(%edi) Package: mythtv-backend 0.21.0+fixes16838-0ubuntu2 PackageArchitecture: i386 Registers: eax0x815a539 135636281 ecx0xb658fea6 -1235681626 edx0x8173e58 135741016 ebx0xb6e1f794 -1226705004 esp0xb4860020 0xb4860020 ebp0xb4860028 0xb4860028 esi0xb48600e8 -1266286360 edi0xb48600e4 -1266286364 eip0x8173e62 0x8173e62 eflags 0x10207 [ CF PF IF RF ] cs 0x73115 ss 0x7b123 ds 0x7b123 es 0x7b123 fs 0x0 0 gs 0x3351 SourcePackage: mythtv Stacktrace: #0 0x08173e62 in ?? () #1 0x0815a538 in ?? () #2 0xb48600e4 in ?? () #3 0xb4860104 in ?? () #4 0xb6c0bace in MythContext::ClearSettingsCache () from /usr/lib/libmyth-0.21.so.0 #5 0xb6c10caa in MythContext::readyRead () from /usr/lib/libmyth-0.21.so.0 #6 0xb6c718fd in readyReadThread_iffound () from /usr/lib/libmyth-0.21.so.0 #7 0xb6c72245 in MythSocket::readyReadThread () from /usr/lib/libmyth-0.21.so.0 #8 0xb5d324fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #9 0xb5b90e5e in clone () from /lib/tls/i686/cmov/libc.so.6 StacktraceTop: ?? () ?? () ?? () ?? () MythContext::ClearSettingsCache () ThreadStacktrace: . Thread 2 (process 7775): #0 0xb7f47410 in __kernel_vsyscall () #1 0xb5d39589 in __lll_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb5d34ba6 in _L_lock_95 () from /lib/tls/i686/cmov/libpthread.so.0 #3 0xb5d3458a in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0 #4 0xb659035b in QRecursiveMutexPrivate::lock () from /usr/lib/libqt-mt.so.3 #5 0xb658fea6 in QMutex::lock () from /usr/lib/libqt-mt.so.3 #6 0x08077cff in ?? () #7 0xb5ad0450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #8 0x0804e4a1 in ?? () . Thread 1 (process 7781): #0 0x08173e62 in ?? () #1 0x0815a538 in ?? () #2 0xb48600e4 in ?? () #3 0xb4860104 in ?? () #4 0xb6c0bace in MythContext::ClearSettingsCache () from /usr/lib/libmyth-0.21.so.0 #5 0xb6c10caa in MythContext::readyRead () from /usr/lib/libmyth-0.21.so.0 #6 0xb6c718fd in readyReadThread_iffound () from /usr/lib/libmyth-0.21.so.0 #7 0xb6c72245 in MythSocket::readyReadThread () from /usr/lib/libmyth-0.21.so.0 #8 0xb5d324fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #9 0xb5b90e5e in clone () from /lib/tls/i686/cmov/libc.so.6 Title: mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache() -- mythfilldatabase crashed with SIGSEGV in QMutex::lock() https://bugs.launchpad.net/bugs/211700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204451] Re: xfce4-mixer-plugin crashed with SIGSEGV in g_type_check_instance_is_a()
After many days of frustration with this machine, I now believe that this crash is principally due to hardware/configuration failure instead of software, and this bug report should potentially be closed off. The Motherboard BIOS settings were somehow corrupted and changed without my actually doing this, and this appeared to occur randomly on reboot. In the latest instance, not only was the CPU underclocked (bad Memory Bus timings - 100Mhz instead of 200Mhz), but the PCI Bus timing was set to Manual, and was overclocked to 75Mhz instead of the default 66Mhz. If this was the case during the above faults, it would definitely lead to issues with valid data availability on the PCI bus, and could lead to other lockup issues, which, while they are reproducible, are not due to application software. The probable effect was that the AGP Video card (nVidia) could cope with the faster bus, but the sound card was entirely unable to and caused the fault. Replacing the CMOS Battery, cleaning and rebuilding the machine, and reconfiguring the BIOS correctly to proper defaults has now solved this problem. The machine does not exhibit this failure anymore, without any software changes made, other than applying the most recent 8.04 updates. Very strange that the CMOS checksum did not fail in any of these conditions ... so I'm not entirely sure what or why this was happening, and/or if there is a fault in the BIOS itself. Will research further independently. -- xfce4-mixer-plugin crashed with SIGSEGV in g_type_check_instance_is_a() https://bugs.launchpad.net/bugs/204451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 14135] Re: Grub Install Failure
I have been experiencing the exact same issue. In order to complete the installation, I physically remove and disable the additional SCSI drives, and only then can I install Ubuntu. Then comes the job of putting everything back in, and thankfully, the first boot then completes without any issues, all drives are mounted and visible, and life is good from then on. It's only the installation and specification of the drives (and mounts) which causes grief. My configuration: (for a MythTV/RAID/Ubuntu box - Using Mythbuntu) ASUS P4B533-E / 2Gb / P4 2.8GHz - Onboard Standard PATA (3 Drives + DVD R/W 2nd/Slave) - Onboard Promise FastTrack 133 RAID PATA (4 Drives - Used in s/w RAID5) - PCI Promise Ultra TX/100 PATA (4 Drives - Used in s/w RAID5) Boot in BIOS is set to Onboard PATA first. Drives are in order: 160Gb (Boot), 300Gb (Storage), 40Gb (Windoz XP), DVD R/W Trying to install Ubuntu on the 160Gb drive I experience the GRUB issues: 1). With all drives in the machine, the boot drive is recognized as /dev/sdi, and not /dev/sda (as might be expected). No success ever getting GRUB to work through the installer. Specifying explicitly the drive to install on will not work. 2). Removing the drives, but leaving the BIOS (both Onboard and TX/100 enabled) also leads to failure, even though drive is correctly detected as /dev/sda. Alone the presence of the controllers / BIOS causes the GRUB failure. 3). Only when removing all drives, physically removing the TX/100, and disabling the onboard RAID BIOS will GRUB be able to successfully install. This is akin to changing the entire machine in order to get things to install - although Ubuntu has no problems afterwards using the drives/controllers/hardware/etc. After this, one other 'odd' thing ... the only way I'm able to successfully (or properly) mount drives (/etc/fstab) is to always use the GUID methodology. This works reliably. Specifying /dev/sdaX does not work, and leads to the incorrect drive being mapped to the mount point each and every time. The drives swap ordering if specified in /etc/fstab. Very frustrating and odd. Annoying that the full install can complete, and then it fails writing the GRUB boot ... *sigh* -- Grub Install Failure https://bugs.launchpad.net/bugs/14135 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
