Re: [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
Have no idea why i'm getting this On Sun, Sep 21, 2014 at 7:54 PM, keepitsimpleengr 1101...@bugs.launchpad.net wrote: Not fixed. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
I upgraded on 9/13/13 from whatever repo came with mythbuntu. On Sun, Sep 15, 2013 at 7:02 PM, Thomas Mashos 1101...@bugs.launchpad.netwrote: Are you running packages that are after September 7th? (currently, those only exist in the Mythbuntu repo). You'll see from this commit that it's literally impossible for mythlogserver to crash anymore https://github.com/MythTV/packaging/commit/b2571edc639c8d99262dfd4ea222ec920d8a2451 Thanks, Thomas Mashos On Sun, Sep 15, 2013 at 3:46 PM, Peter D. 1101...@bugs.launchpad.net wrote: Bug still exists 16th September. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to MythTV. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Triaged Status in MythTV: Unknown Status in “mythtv” package in Ubuntu: Fix Released Bug description: crashed on remote frontend ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: mythtv-common 2:0.26.0+fixes.20130118.8f8274a-0ubuntu0mythbuntu2 [origin: LP-PPA-mythbuntu-0.26] ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: nvidia .var.log.mythtv.mythavtest.log: .var.log.mythtv.mythbackend.log: .var.log.mythtv.mythccextractor.log: .var.log.mythtv.mythcommflag.log: .var.log.mythtv.mythfilldatabase.log: .var.log.mythtv.mythjobqueue.log: .var.log.mythtv.mythlcdserver.log: .var.log.mythtv.mythmediaserver.log: .var.log.mythtv.mythmetadatalookup.log: .var.log.mythtv.mythpreviewgen.log: .var.log.mythtv.mythshutdown.log: .var.log.mythtv.mythtranscode.log: .var.log.mythtv.mythtv.setup.log: .var.log.mythtv.mythutil.log: .var.log.mythtv.mythwelcome.log: ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CrashDB: mythbuntu Date: Fri Jan 18 15:13:07 2013 Disassembly: = 0x0: Cannot access memory at address 0x0 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ExecutablePath: /usr/bin/mythlogserver InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 Installed_mythtv_dbg: 2:0.26.0+fixes.20130118.8f8274a-0ubuntu0mythbuntu2 MarkForUpload: True MythTVDirectoryPermissions: total 4 drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos ProcCmdline: /usr/bin/mythlogserver --daemon --verbose general --loglevel info --syslog local7 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing NULL VMA Signal: 11 SourcePackage: mythtv StacktraceTop: ?? () QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 disconnect (member=0x0, receiver=0x7ff2d800b560, this=0x7ff2e000b4c0) at /usr/include/qt4/QtCore/qobject.h:252 unregisterSocket (socket_=0x7ff2e000b4c0, this=0x7ff2d800b560) at ../include/nzmqt/nzmqt.hpp:703 nzmqt::PollingZMQContext::qt_static_metacall (_o=0x7ff2d800b560, _c=optimized out, _id=optimized out, _a=optimized out) at moc_nzmqt.cpp:401 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions ___ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : mythbuntu-b...@lists.launchpad.net Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions -- ubuntu-bugs mailing list
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
I'm running .26 see below. I thought .27 was not out yet? I'm also running on a hypervisor xcp with xen monitoring tools installed. I have my system snapshots so if you want me to try something just let me know. dc@mythbackend:~$ sudo apt-cache policy mythtv mythtv: Installed: 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Candidate: 2:0.26.1+fixes.20130914.bd7198b-0ubuntu0mythbuntu1 Version table: 2:0.26.1+fixes.20130914.bd7198b-0ubuntu0mythbuntu1 0 500 http://ppa.launchpad.net/mythbuntu/0.26/ubuntu/ precise/main amd64 Packages *** 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 0 100 /var/lib/dpkg/status 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/multiverse amd64 Packages 2:0.25.0+fixes.20120410.1f5962a-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/multiverse amd64 Packages dc@mythbackend:~$ On Sun, Sep 15, 2013 at 8:44 PM, Thomas Mashos 1101...@bugs.launchpad.netwrote: 0.26 or 0.27? Thanks, Thomas Mashos On Sun, Sep 15, 2013 at 5:32 PM, doylecentral 1101...@bugs.launchpad.net wrote: I upgraded on 9/13/13 from whatever repo came with mythbuntu. On Sun, Sep 15, 2013 at 7:02 PM, Thomas Mashos 1101...@bugs.launchpad.netwrote: Are you running packages that are after September 7th? (currently, those only exist in the Mythbuntu repo). You'll see from this commit that it's literally impossible for mythlogserver to crash anymore https://github.com/MythTV/packaging/commit/b2571edc639c8d99262dfd4ea222ec920d8a2451 Thanks, Thomas Mashos On Sun, Sep 15, 2013 at 3:46 PM, Peter D. 1101...@bugs.launchpad.net wrote: Bug still exists 16th September. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to MythTV. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Triaged Status in MythTV: Unknown Status in “mythtv” package in Ubuntu: Fix Released Bug description: crashed on remote frontend ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: mythtv-common 2:0.26.0+fixes.20130118.8f8274a-0ubuntu0mythbuntu2 [origin: LP-PPA-mythbuntu-0.26] ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: nvidia .var.log.mythtv.mythavtest.log: .var.log.mythtv.mythbackend.log: .var.log.mythtv.mythccextractor.log: .var.log.mythtv.mythcommflag.log: .var.log.mythtv.mythfilldatabase.log: .var.log.mythtv.mythjobqueue.log: .var.log.mythtv.mythlcdserver.log: .var.log.mythtv.mythmediaserver.log: .var.log.mythtv.mythmetadatalookup.log: .var.log.mythtv.mythpreviewgen.log: .var.log.mythtv.mythshutdown.log: .var.log.mythtv.mythtranscode.log: .var.log.mythtv.mythtv.setup.log: .var.log.mythtv.mythutil.log: .var.log.mythtv.mythwelcome.log: ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CrashDB: mythbuntu Date: Fri Jan 18 15:13:07 2013 Disassembly: = 0x0: Cannot access memory at address 0x0 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ExecutablePath: /usr/bin/mythlogserver InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 Installed_mythtv_dbg: 2:0.26.0+fixes.20130118.8f8274a-0ubuntu0mythbuntu2 MarkForUpload: True MythTVDirectoryPermissions: total 4 drwxr-xr-x 2 root root 4096 Nov 24 18:26 videos ProcCmdline: /usr/bin/mythlogserver --daemon --verbose general --loglevel info --syslog local7 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing NULL VMA Signal: 11 SourcePackage: mythtv StacktraceTop: ?? () QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 disconnect (member=0x0, receiver=0x7ff2d800b560, this=0x7ff2e000b4c0) at /usr/include/qt4/QtCore/qobject.h:252 unregisterSocket (socket_=0x7ff2e000b4c0, this=0x7ff2d800b560) at ../include/nzmqt/nzmqt.hpp:703 nzmqt::PollingZMQContext::qt_static_metacall (_o=0x7ff2d800b560, _c=optimized out, _id=optimized out, _a=optimized out) at moc_nzmqt.cpp:401
Re: [Mythbuntu-bugs] [Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
Sorry didn't see your mail. c@mythbackend:~$ dpkg -l | grep -i myth rc libmyth-0.25-0 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 Common library code for MythTV and add-on modules (runtime) ii libmyth-0.26-0 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Common library code for MythTV and add-on modules (runtime) ii libmyth-python 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 A python library to access some MytTV features ii libmythtv-perl 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 A PERL library to access some MythTV features ii mythbuntu-bare-client 2.2Mythbuntu Bare Client ii mythbuntu-common 0.67 Mythbuntu application support functions ii mythbuntu-control-centre 0.63-0ubuntu2 Mythbuntu Configuration Application ii mythbuntu-default-settings 1.08 default settings for Mythbuntu ii mythbuntu-desktop 0.77 The Mythbuntu standalone system ii mythbuntu-lightdm-theme 1.01 Mythbuntu LightDM setup ii mythbuntu-log-grabber 0.10-0ubuntu1 Mythbuntu diagnostic utility ii mythgallery 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Image gallery/slideshow add-on module for MythTV ii mythmusic 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Music add-on module for MythTV ii mythtv 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (client and server) ii mythtv-backend 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (server) ii mythtv-backend-master 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Metapackage to setup and configure a Master Backend profile of MythTV. ii mythtv-common 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (common data) ii mythtv-database 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (database) ii mythtv-frontend 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Personal video recorder application (client) ii mythtv-theme-mythbuntu 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 The mythbuntu MythTV Theme ii mythtv-transcode-utils 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Utilities used for transcoding MythTV tasks ii mythweb 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 Web interface add-on module for MytTV ii php-mythtv 2:0.26.1+fixes.20130906.dbdd455-0ubuntu0mythbuntu1 PHP Bindings for MythTV On Sun, Sep 15, 2013 at 7:41 PM, Thomas Mashos 1101...@bugs.launchpad.netwrote: No, dropping the repo would not fix the issue. Can you post what the output of this is dpkg -l | grep -i myth Thanks, Thomas Mashos On Sun, Sep 15, 2013 at 4:24 PM, kmitche 1101...@bugs.launchpad.net wrote: Thomas, I am running the mythbuntu repo. Mythlogserver appears to be active as a result. Dropping the repo would fix this issue, correct? Thanks for following up with this. Kent On Sep 15, 2013, at 4:02 PM, Thomas Mashos 1101...@bugs.launchpad.net wrote: Are you running packages that are after September 7th? (currently, those only exist in the Mythbuntu repo). You'll see from this commit that it's literally impossible for mythlogserver to crash anymore https://github.com/MythTV/packaging/commit/b2571edc639c8d99262dfd4ea222ec920d8a2451 Thanks, Thomas Mashos On Sun, Sep 15, 2013 at 3:46 PM, Peter D. 1101...@bugs.launchpad.net wrote: Bug still exists 16th September. -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to MythTV. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Triaged Status in MythTV: Unknown Status in “mythtv” package in Ubuntu: Fix Released Bug description: crashed on remote frontend ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: mythtv-common 2:0.26.0+fixes.20130118.8f8274a-0ubuntu0mythbuntu2 [origin: LP-PPA-mythbuntu-0.26] ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: nvidia .var.log.mythtv.mythavtest.log: .var.log.mythtv.mythbackend.log: .var.log.mythtv.mythccextractor.log: .var.log.mythtv.mythcommflag.log: .var.log.mythtv.mythfilldatabase.log: .var.log.mythtv.mythjobqueue.log: .var.log.mythtv.mythlcdserver.log: .var.log.mythtv.mythmediaserver.log: .var.log.mythtv.mythmetadatalookup.log: .var.log.mythtv.mythpreviewgen.log: .var.log.mythtv.mythshutdown.log: .var.log.mythtv.mythtranscode.log: .var.log.mythtv.mythtv.setup.log:
[Bug 139865] Re: gutsy on hp compaq 6910p does not suspend or hibernate
This is fixed in Hardy. -- gutsy on hp compaq 6910p does not suspend or hibernate https://bugs.launchpad.net/bugs/139865 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139865] Re: gutsy on hp compaq 6910p does not suspend or hibernate
Still on the hunt for a solution and came across this bit-o-knowledge : http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide Attention: Suspend/Hibernation will not work With Gutsy release, there's a big problem using the ATI proprietary drivers. The Suspend/Hibernate function will stop working. The problem is due to the new SLUB allocator incorporated in 2.6.22 / 2.6.23 Kernel. There are no workaround, except: - Return to Feisty (with 2.6.20 kernel, and apply specific solutions: see Feisty installation guide). - Use default Mesa Drivers (the easiest way is to disable ATI driver from Restricted Driver Manager). - Recompiler your Kernel to use SLAB. Unfortunately some new ATI cards couldn't start X with Mesa drivers, so the only workaround is returning to Feisty. The problem will be solved in the next ATI driver release. -- gutsy on hp compaq 6910p does not suspend or hibernate https://bugs.launchpad.net/bugs/139865 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139865] Re: gutsy on hp compaq 6910p does not suspend or hibernate
Brian, I could not get the graphics going without the fglrx video driver. I had to install Ubuntu non-visually and then add the ati drivers. How do you suggest I proceed? Can I unload the proprietary driver and use _? Thanks for letting me contribute to the make Ubuntu better. Brian Doyle -- gutsy on hp compaq 6910p does not suspend or hibernate https://bugs.launchpad.net/bugs/139865 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139865] Re: gutsy on hp compaq 6910p does not suspend or hibernate
After upgrading this is what i have for the lspci ... 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M64-S [Mobility Radeon X2300] [1002:7188] (prog-if 00 [VGA]) Subsystem: Hewlett-Packard Company Unknown device [103c:30c1] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at d000 (32-bit, prefetchable) [size=64M] Region 1: I/O ports at 4000 [size=256] Region 2: Memory at d840 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at d842 [disabled] [size=128K] Capabilities: access denied Let me know if there is anything you want me to try I'm going to disable the restricted driver that is on right now and get back to you ... -- gutsy on hp compaq 6910p does not suspend or hibernate https://bugs.launchpad.net/bugs/139865 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139865] Re: gutsy on hp compaq 6910p does not suspend or hibernate
I got it to sort of work. Here were my steps ... 1. Clicked the restricted driver manager. stopped the driver. It unloaded. I restarted. 2. When it started X failed. So I did the below [EMAIL PROTECTED]:~$ history | grep aticonfig 65 sudo apt-get install xorg-driver-fglrx 66 sudo aticonfig --initial 67 sudo aticonfig --overlay-type=Xv 3. Then I started X and I could suspend and hibernate. 4. See my config below ( You know I don't think X should be working with this configuration ) 5. My graphics are craptacular blurry and distorted and have a lag .. Let me know what you want me to do next... Brian Doyle # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section ServerLayout Identifier Default Layout Screen 0 aticonfig-Screen[0] 0 0 InputDeviceGeneric Keyboard InputDeviceConfigured Mouse InputDevicestylus SendCoreEvents InputDevicecursor SendCoreEvents InputDeviceeraser SendCoreEvents InputDeviceSynaptics Touchpad EndSection Section Files EndSection Section Module EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout us Option XkbVariant intl Option XkbOptions lv3:ralt_switch EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device /dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 Option Emulate3Buttons true EndSection Section InputDevice Identifier Synaptics Touchpad Driver synaptics Option SendCoreEvents true Option Device /dev/psaux Option Protocol auto-dev Option HorizScrollDelta 0 EndSection Section InputDevice Identifier stylus Driver wacom Option Device /dev/input/wacom Option Type stylus Option ForceDevice ISDV4 # Tablet PC ONLY EndSection Section InputDevice Identifier eraser Driver wacom Option Device /dev/input/wacom Option Type eraser Option ForceDevice ISDV4 # Tablet PC ONLY EndSection Section InputDevice Identifier cursor Driver wacom Option Device /dev/input/wacom Option Type cursor Option ForceDevice ISDV4 # Tablet PC ONLY EndSection Section Monitor Identifier Generic Monitor Option DPMS EndSection Section Monitor Identifier aticonfig-Monitor[0] Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true EndSection Section Device Identifier Generic Video Card Driver vesa BusID PCI:1:0:0 EndSection Section Device Identifier aticonfig-Device[0] Driver fglrx Option VideoOverlay on Option OpenGLOverlay off EndSection Section Screen Identifier Default Screen Device Generic Video Card MonitorGeneric Monitor DefaultDepth 24 SubSection Display Modes1280x800 EndSubSection EndSection Section Screen Identifier aticonfig-Screen[0] Device aticonfig-Device[0] Monitoraticonfig-Monitor[0] DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection -- gutsy on hp compaq 6910p does not suspend or hibernate https://bugs.launchpad.net/bugs/139865 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139865] Re: gutsy on hp compaq 6910p does not suspend or hibernate
Adding this information since I just read the wiki about additional information to ask for: Linux 2.6.22-11-generic #1 SMP Fri Sep 7 05:07:05 GMT 2007 i686 GNU/Linux [EMAIL PROTECTED]:~$ sudo lspci -vvnn 00:00.0 Host bridge [0600]: Intel Corporation Mobile Memory Controller Hub [8086:2a00] (rev 0c) Subsystem: Hewlett-Packard Company Unknown device [103c:30c1] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Capabilities: [e0] Vendor Specific Information 00:01.0 PCI bridge [0604]: Intel Corporation Mobile PCI Express Root Port [8086:2a01] (rev 0c) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 4000-4fff Memory behind bridge: d840-d84f Prefetchable memory behind bridge: d000-d3ff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- Capabilities: [88] Subsystem: Hewlett-Packard Company Unknown device [103c:30c1] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+ Address: fee0300c Data: 41d1 Capabilities: [a0] Express Root Port (Slot-) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s 64ns, L1 1us Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 2 Link: Latency L0s 256ns, L1 4us Link: ASPM L0s L1 Enabled RCB 64 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x16 Root: Correctable- Non-Fatal- Fatal- PME- 00:03.0 Communication controller [0780]: Intel Corporation Mobile HECI Controller [8086:2a04] (rev 0c) Subsystem: Hewlett-Packard Company Unknown device [103c:30c1] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 255 Region 0: Memory at d850 (64-bit, non-prefetchable) [size=16] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [8c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Address: Data: 00:03.2 IDE interface [0101]: Intel Corporation Mobile PT IDER Controller [8086:2a06] (rev 0c) (prog-if 85 [Master SecO PriO]) Subsystem: Hewlett-Packard Company Unknown device [103c:30c1] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin C routed to IRQ 11 Region 0: I/O ports at 5000 [size=8] Region 1: I/O ports at 5008 [size=4] Region 2: I/O ports at 5010 [size=8] Region 3: I/O ports at 5018 [size=4] Region 4: I/O ports at 5020 [size=16] Capabilities: [c8] Power Management version 3 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Address: Data: 00:03.3 Serial controller [0700]: Intel Corporation Mobile KT Controller [8086:2a07] (rev 0c) (prog-if 02 [16550]) Subsystem: Hewlett-Packard Company Unknown device [103c:30c1] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 17 Region 0: I/O ports at 5030 [size=8] Region 1: Memory at d8501000
[Bug 139865] Re: gutsy on hp compaq 6910p does not suspend or hibernate
here is the /var/log/kernlog ** Attachment added: kern.log http://launchpadlibrarian.net/9299447/kern.log -- gutsy on hp compaq 6910p does not suspend or hibernate https://bugs.launchpad.net/bugs/139865 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139865] gutsy on hp compaq 6910p does not suspend or hibernate
Public bug reported: Binary package hint: acpi I'm using the development snap shot of gutsy up to date as of 15-9-2007. When I suspend or try to hibernate I get a cursor and nothing else. This did work on 7.04 ... but needed the latest kernel for the hardware. Please let me know what logs and or other information you need. ** Affects: acpi (Ubuntu) Importance: Undecided Status: New -- gutsy on hp compaq 6910p does not suspend or hibernate https://bugs.launchpad.net/bugs/139865 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
