| 2011-01-29 08:22:40 |
Cliff |
bug |
|
|
added bug |
| 2011-01-29 08:22:40 |
Cliff |
attachment added |
|
dmesg of this issue https://bugs.launchpad.net/bugs/709649/+attachment/1814124/+files/dmesg.txt |
|
| 2011-01-29 08:23:46 |
Cliff |
visibility |
private |
public |
|
| 2011-01-29 08:42:08 |
Cliff |
description |
I've got this all typed in and I see in dmesg that there are some CD read errors. I have seen these before with what appear to be incorrectly created squashfs CD's. The panic / oops may indeed be caused by a CD error.
This is when running the i386 Natty (11.04) daily live (development) CD dated I believe 2011-01-27 on a very stable Dual core (Intel 925 dual core (AMD64 capable), P4M800PRO, 2 gigs, Asus Geforce 3 AGP) system that I just want to get better OpenGL running on. (Hoping to find better OpenGL support in Natty.) It happened as the desktop was coming up. No icons or task bars appeared before the error, but the background had been painted for perhaps 30 seconds (wild guess).
This system exhibits the "no human readable MCE decoding support on this CPU type" issue at boot up into this live Natty CD and I had to use "nomce" in the kernel boot options line to get past it. I also recall that with previous kernels on Lucid (AMD64) this stable system always generates an MCE at 300 seconds after boot in dmesg. I researched it before and didn't find anything useful.
I use this system for 12 hours every day (with Maverick lately) and have no lockups or corruptions at all.
With the Natty daily CD, this system also exhibits the "it seems you do not have the hardware requirements to run unity" issue, perhaps because it has an old monitor that these later kernels (at least the later ones, maybe the earlier ones too) have a hard time finding the EDID on. On my hard drive upgrade from Lucid to Maverick I had to make an xorg.conf with some horizontal and vertical monitor timing ranges before it would let me use a reasonable screen resolution and refresh rate. In Maverick, the refresh rate was 0 before this and (I forget the tool) said it got an EDID error trying to get info from the monitor.
Looking at dmesg, I see that I have an easycap (video to USB adapter) plugged in (with no video source though). The easycap device works fine under previous versions of Ubuntu (sourceforge driver). I notice though that it was detected as the FOUR-CVBS (4 video input) hardware version which is incorrect if that matters. It is the single CVBS version.
If I had to guess at possible causes, I would point first to the CD read errors (that I now see in the dmesg) (I need to retest reading the CD on this drive from my stable Maverick), then to the benign MCE that always happened at 300 seconds (at least with earlier Ubuntus) and I suspect that is related to the "no human readable MCE decoding support on this CPU type" that I now get with this Natty development version.
This is the first time I have tried the early Natty.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nux-tools 0.9.16-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
Date: Sat Jan 29 02:18:49 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/lib/nux/unity_support_test
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110127)
ProcCmdline: /usr/lib/nux/unity_support_test
ProcEnviron:
LANGUAGE=en_US.UTF-8:en
LANG=en_US.UTF-8
LC_MESSAGES=en_AG.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
?? ()
nux::IOpenGLAsmVertexShader::IOpenGLAsmVertexShader(nux::NString) () from /usr/lib/libnux-graphics-0.9.so.0
nux::GpuDevice::CreateAsmVertexShader(nux::IOpenGLAsmVertexShader**) () from /usr/lib/libnux-graphics-0.9.so.0
nux::GpuDevice::CreateAsmVertexShader() () from /usr/lib/libnux-graphics-0.9.so.0
nux::IOpenGLAsmShaderProgram::IOpenGLAsmShaderProgram(nux::NString) () from /usr/lib/libnux-graphics-0.9.so.0
Title: unity_support_test crashed with SIGSEGV in nux::IOpenGLAsmVertexShader::IOpenGLAsmVertexShader()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nm-applet:3138): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
(nautilus:3115): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed |
I've got this all typed in and I see in dmesg that there are some CD read errors. I have seen these before with what appear to be incorrectly created squashfs CD's. The panic / oops may indeed be caused by a CD error. <EDIT> I tested the CD with the test CD boot option and it passed. </EDIT>
This is when running the i386 Natty (11.04) daily live (development) CD dated I believe 2011-01-27 on a very stable Dual core (Intel 925 dual core (AMD64 capable), P4M800PRO, 2 gigs, Asus Geforce 3 AGP) system that I just want to get better OpenGL running on. (Hoping to find better OpenGL support in Natty.) It happened as the desktop was coming up. No icons or task bars appeared before the error, but the background had been painted for perhaps 30 seconds (wild guess).
This system exhibits the "no human readable MCE decoding support on this CPU type" issue at boot up into this live Natty CD and I had to use "nomce" in the kernel boot options line to get past it. I also recall that with previous kernels on Lucid (AMD64) this stable system always generates an MCE at 300 seconds after boot in dmesg. I researched it before and didn't find anything useful.
I use this system for 12 hours every day (with Maverick lately) and have no lockups or corruptions at all.
With the Natty daily CD, this system also exhibits the "it seems you do not have the hardware requirements to run unity" issue, perhaps because it has an old monitor that these later kernels (at least the later ones, maybe the earlier ones too) have a hard time finding the EDID on. On my hard drive upgrade from Lucid to Maverick I had to make an xorg.conf with some horizontal and vertical monitor timing ranges before it would let me use a reasonable screen resolution and refresh rate. In Maverick, the refresh rate was 0 before this and (I forget the tool) said it got an EDID error trying to get info from the monitor.
Looking at dmesg, I see that I have an easycap (video to USB adapter) plugged in (with no video source though). The easycap device works fine under previous versions of Ubuntu (sourceforge driver). I notice though that it was detected as the FOUR-CVBS (4 video input) hardware version which is incorrect if that matters. It is the single CVBS version.
If I had to guess at possible causes, I would point first to the CD read errors (that I now see in the dmesg) (I need to retest reading the CD on this drive from my stable Maverick), <EDIT> CD tested OK </EDIT> then to the benign MCE that always happened at 300 seconds (at least with earlier Ubuntus) <EDIT> Maverick also produces this benign MCE at 300 seconds (and not again till reboot) </EDIT> and I suspect that is related to the "no human readable MCE decoding support on this CPU type" that I now get with this Natty development version.
This is the first time I have tried the early Natty.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nux-tools 0.9.16-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
Date: Sat Jan 29 02:18:49 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/lib/nux/unity_support_test
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110127)
ProcCmdline: /usr/lib/nux/unity_support_test
ProcEnviron:
LANGUAGE=en_US.UTF-8:en
LANG=en_US.UTF-8
LC_MESSAGES=en_AG.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
?? ()
nux::IOpenGLAsmVertexShader::IOpenGLAsmVertexShader(nux::NString) () from /usr/lib/libnux-graphics-0.9.so.0
nux::GpuDevice::CreateAsmVertexShader(nux::IOpenGLAsmVertexShader**) () from /usr/lib/libnux-graphics-0.9.so.0
nux::GpuDevice::CreateAsmVertexShader() () from /usr/lib/libnux-graphics-0.9.so.0
nux::IOpenGLAsmShaderProgram::IOpenGLAsmShaderProgram(nux::NString) () from /usr/lib/libnux-graphics-0.9.so.0
Title: unity_support_test crashed with SIGSEGV in nux::IOpenGLAsmVertexShader::IOpenGLAsmVertexShader()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nm-applet:3138): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
(nautilus:3115): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
|
|
| 2011-01-29 08:49:16 |
Cliff |
description |
I've got this all typed in and I see in dmesg that there are some CD read errors. I have seen these before with what appear to be incorrectly created squashfs CD's. The panic / oops may indeed be caused by a CD error. <EDIT> I tested the CD with the test CD boot option and it passed. </EDIT>
This is when running the i386 Natty (11.04) daily live (development) CD dated I believe 2011-01-27 on a very stable Dual core (Intel 925 dual core (AMD64 capable), P4M800PRO, 2 gigs, Asus Geforce 3 AGP) system that I just want to get better OpenGL running on. (Hoping to find better OpenGL support in Natty.) It happened as the desktop was coming up. No icons or task bars appeared before the error, but the background had been painted for perhaps 30 seconds (wild guess).
This system exhibits the "no human readable MCE decoding support on this CPU type" issue at boot up into this live Natty CD and I had to use "nomce" in the kernel boot options line to get past it. I also recall that with previous kernels on Lucid (AMD64) this stable system always generates an MCE at 300 seconds after boot in dmesg. I researched it before and didn't find anything useful.
I use this system for 12 hours every day (with Maverick lately) and have no lockups or corruptions at all.
With the Natty daily CD, this system also exhibits the "it seems you do not have the hardware requirements to run unity" issue, perhaps because it has an old monitor that these later kernels (at least the later ones, maybe the earlier ones too) have a hard time finding the EDID on. On my hard drive upgrade from Lucid to Maverick I had to make an xorg.conf with some horizontal and vertical monitor timing ranges before it would let me use a reasonable screen resolution and refresh rate. In Maverick, the refresh rate was 0 before this and (I forget the tool) said it got an EDID error trying to get info from the monitor.
Looking at dmesg, I see that I have an easycap (video to USB adapter) plugged in (with no video source though). The easycap device works fine under previous versions of Ubuntu (sourceforge driver). I notice though that it was detected as the FOUR-CVBS (4 video input) hardware version which is incorrect if that matters. It is the single CVBS version.
If I had to guess at possible causes, I would point first to the CD read errors (that I now see in the dmesg) (I need to retest reading the CD on this drive from my stable Maverick), <EDIT> CD tested OK </EDIT> then to the benign MCE that always happened at 300 seconds (at least with earlier Ubuntus) <EDIT> Maverick also produces this benign MCE at 300 seconds (and not again till reboot) </EDIT> and I suspect that is related to the "no human readable MCE decoding support on this CPU type" that I now get with this Natty development version.
This is the first time I have tried the early Natty.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nux-tools 0.9.16-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
Date: Sat Jan 29 02:18:49 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/lib/nux/unity_support_test
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110127)
ProcCmdline: /usr/lib/nux/unity_support_test
ProcEnviron:
LANGUAGE=en_US.UTF-8:en
LANG=en_US.UTF-8
LC_MESSAGES=en_AG.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
?? ()
nux::IOpenGLAsmVertexShader::IOpenGLAsmVertexShader(nux::NString) () from /usr/lib/libnux-graphics-0.9.so.0
nux::GpuDevice::CreateAsmVertexShader(nux::IOpenGLAsmVertexShader**) () from /usr/lib/libnux-graphics-0.9.so.0
nux::GpuDevice::CreateAsmVertexShader() () from /usr/lib/libnux-graphics-0.9.so.0
nux::IOpenGLAsmShaderProgram::IOpenGLAsmShaderProgram(nux::NString) () from /usr/lib/libnux-graphics-0.9.so.0
Title: unity_support_test crashed with SIGSEGV in nux::IOpenGLAsmVertexShader::IOpenGLAsmVertexShader()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nm-applet:3138): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
(nautilus:3115): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
|
I've got this all typed in and I see in dmesg that there are some CD read errors. I have seen these before with what appear to be incorrectly created squashfs CD's. The panic / oops may indeed be caused by a CD error. <EDIT> I tested the CD with the test CD boot option and it passed. </EDIT>
This is when running the i386 Natty (11.04) daily live (development) CD dated I believe 2011-01-27 on a very stable Dual core (Intel 925 dual core (AMD64 capable), ECS (Via) P4M800PRO, 2 gigs, Asus Geforce 3 AGP) system that I just want to get better OpenGL running on. (Hoping to find better OpenGL support in Natty.) It happened as the desktop was coming up. No icons or task bars appeared before the error, but the background had been painted for perhaps 30 seconds (wild guess).
This system exhibits the "no human readable MCE decoding support on this CPU type" issue at boot up into this live Natty CD and I had to use "nomce" in the kernel boot options line to get past it. I also recall that with previous kernels on Lucid (AMD64) this stable system always generates an MCE at 300 seconds after boot in dmesg. I researched it before and didn't find anything useful.
I use this system for 12 hours every day (with Maverick lately) and have no lockups or corruptions at all.
With the Natty daily CD, this system also exhibits the "it seems you do not have the hardware requirements to run unity" issue, perhaps because it has an old monitor that these later kernels (at least the later ones, maybe the earlier ones too) have a hard time finding the EDID on. On my hard drive upgrade from Lucid to Maverick I had to make an xorg.conf with some horizontal and vertical monitor timing ranges before it would let me use a reasonable screen resolution and refresh rate. In Maverick, the refresh rate was 0 before this and (I forget the tool) said it got an EDID error trying to get info from the monitor.
Looking at dmesg, I see that I have an easycap (video to USB adapter) plugged in (with no video source though). The easycap device works fine under previous versions of Ubuntu (sourceforge driver). I notice though that it was detected as the FOUR-CVBS (4 video input) hardware version which is incorrect if that matters. It is the single CVBS version.
If I had to guess at possible causes, I would point first to the CD read errors (that I now see in the dmesg) (I need to retest reading the CD on this drive from my stable Maverick), <EDIT> CD tested OK </EDIT> then to the benign MCE that always happened at 300 seconds (at least with earlier Ubuntus) <EDIT> Maverick also produces this benign MCE at 300 seconds (and not again till reboot) </EDIT> and I suspect that is related to the "no human readable MCE decoding support on this CPU type" that I now get with this Natty development version.
This is the first time I have tried the early Natty.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nux-tools 0.9.16-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
Date: Sat Jan 29 02:18:49 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/lib/nux/unity_support_test
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110127)
ProcCmdline: /usr/lib/nux/unity_support_test
ProcEnviron:
LANGUAGE=en_US.UTF-8:en
LANG=en_US.UTF-8
LC_MESSAGES=en_AG.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
?? ()
nux::IOpenGLAsmVertexShader::IOpenGLAsmVertexShader(nux::NString) () from /usr/lib/libnux-graphics-0.9.so.0
nux::GpuDevice::CreateAsmVertexShader(nux::IOpenGLAsmVertexShader**) () from /usr/lib/libnux-graphics-0.9.so.0
nux::GpuDevice::CreateAsmVertexShader() () from /usr/lib/libnux-graphics-0.9.so.0
nux::IOpenGLAsmShaderProgram::IOpenGLAsmShaderProgram(nux::NString) () from /usr/lib/libnux-graphics-0.9.so.0
Title: unity_support_test crashed with SIGSEGV in nux::IOpenGLAsmVertexShader::IOpenGLAsmVertexShader()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nm-applet:3138): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
(nautilus:3115): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
|
|
| 2011-02-01 18:48:57 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
| 2011-02-01 18:49:03 |
Apport retracing service |
attachment added |
|
Stacktrace.txt https://bugs.launchpad.net/bugs/709649/+attachment/1822784/+files/Stacktrace.txt |
|
| 2011-02-01 18:49:05 |
Apport retracing service |
attachment added |
|
ThreadStacktrace.txt https://bugs.launchpad.net/bugs/709649/+attachment/1822785/+files/ThreadStacktrace.txt |
|
| 2011-02-01 18:49:10 |
Apport retracing service |
attachment removed |
CoreDump.gz https://bugs.launchpad.net/bugs/709649/+attachment/1814125/+files/CoreDump.gz |
|
|
| 2011-02-01 18:49:13 |
Apport retracing service |
nux (Ubuntu): importance |
Undecided |
Medium |
|
| 2011-02-01 18:49:17 |
Apport retracing service |
tags |
apport-crash i386 natty need-i386-retrace |
apport-crash i386 natty |
|
| 2011-02-02 21:35:50 |
Cliff |
attachment added |
|
Dmesg from the second time I documented this issue https://bugs.launchpad.net/ubuntu/+source/nux/+bug/709649/+attachment/1825982/+files/dmesg2.txt |
|
| 2011-02-03 10:15:06 |
Didier Roche-Tolomelli |
bug task added |
|
nux |
|
| 2011-02-04 17:59:21 |
Cliff |
attachment added |
|
dmesg from the boot (3rd documented boot) with F6-nomodeset https://bugs.launchpad.net/ubuntu/+source/nux/+bug/709649/+attachment/1829798/+files/dmesg3.txt |
|
| 2011-02-04 19:21:35 |
Cliff |
attachment added |
|
glxinfo from an F6-nomodeset (= metacity) boot up https://bugs.launchpad.net/ubuntu/+source/nux/+bug/709649/+attachment/1829943/+files/glxinfo.txt |
|
| 2011-02-08 17:09:46 |
Jay Taoko |
bug task added |
|
unity (Ubuntu) |
|
| 2011-02-08 17:10:21 |
Jay Taoko |
bug task added |
|
unity |
|
| 2011-02-09 04:20:21 |
Jay Taoko |
nux: status |
New |
Triaged |
|
| 2011-02-09 04:20:28 |
Jay Taoko |
unity: status |
New |
Triaged |
|
| 2011-02-09 04:20:49 |
Jay Taoko |
nux: importance |
Undecided |
Medium |
|
| 2011-02-09 04:20:56 |
Jay Taoko |
unity: importance |
Undecided |
Medium |
|
| 2011-02-09 04:21:02 |
Jay Taoko |
nux: assignee |
|
Jay Taoko (jaytaoko) |
|
| 2011-02-09 04:21:09 |
Jay Taoko |
unity: assignee |
|
Jay Taoko (jaytaoko) |
|
| 2011-02-11 00:23:35 |
Brian Murray |
unity (Ubuntu): status |
New |
Triaged |
|
| 2011-02-21 16:55:24 |
Didier Roche-Tolomelli |
nux (Ubuntu): status |
New |
Triaged |
|
| 2011-03-07 10:43:03 |
Neil J. Patel |
tags |
apport-crash i386 natty |
apport-crash i386 natty unity-priority |
|
| 2011-03-07 21:54:43 |
Duncan McGreggor |
tags |
apport-crash i386 natty unity-priority |
apport-crash dids-top-ten i386 natty unity-priority |
|
| 2011-03-08 00:50:27 |
Jay Taoko |
nux: status |
Triaged |
Confirmed |
|
| 2011-03-08 00:50:31 |
Jay Taoko |
unity: status |
Triaged |
Confirmed |
|
| 2011-03-08 00:50:37 |
Jay Taoko |
nux (Ubuntu): status |
Triaged |
Confirmed |
|
| 2011-03-08 00:50:51 |
Jay Taoko |
unity (Ubuntu): status |
Triaged |
Confirmed |
|
| 2011-03-08 00:51:56 |
Jay Taoko |
nux: status |
Confirmed |
Fix Committed |
|
| 2011-03-08 00:52:00 |
Jay Taoko |
unity: status |
Confirmed |
Fix Committed |
|
| 2011-03-08 00:52:06 |
Jay Taoko |
nux (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2011-03-08 00:52:11 |
Jay Taoko |
unity (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2011-03-08 08:09:26 |
Didier Roche-Tolomelli |
unity: milestone |
|
3.6.4 |
|
| 2011-03-10 16:53:19 |
Didier Roche-Tolomelli |
nux: status |
Fix Committed |
Fix Released |
|
| 2011-03-10 16:53:22 |
Didier Roche-Tolomelli |
unity: status |
Fix Committed |
Fix Released |
|
| 2011-03-10 18:52:32 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-desktop/nux/ubuntu |
|
| 2011-03-10 18:54:32 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-desktop/unity/ubuntu |
|
| 2011-03-10 19:01:02 |
Launchpad Janitor |
nux (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2011-03-10 19:01:35 |
Launchpad Janitor |
unity (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2011-03-10 19:16:52 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/unity |
|
| 2011-03-10 19:17:23 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/nux |
|
