[Kernel-packages] [Bug 1665833] [NEW] inode exhaustion should be logged to dmesg
Public bug reported: Problem: My server just became unusable, because it ran out of inodes (something that shouldn't happen on a relatively normal installation). The root-cause was a misbehaving CRM program creating way too many session files and never deleting them. However, while debugging, it would have been really really helpful if there were something in the logfiles. But it just failed silently: the lack of any error message makes diagnosing this error condition 100x harder than it should be. We get messages about being out of disk-space, but that's not helpful, especially when "df -h" shows it not to be true. So, the bug report/feature request is this: when the kernel cannot create a new file due to a shortage of inodes, it should emit a message to that effect, at least in dmesg (and ideally also to syslog). [For anyone else who chances upon this bug report, you can tell if you have run out of inodes with "df -i", and you can find the offending directories with: "find / -xdev -size +100k -type d" ] ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1665833 Title: inode exhaustion should be logged to dmesg Status in linux package in Ubuntu: New Bug description: Problem: My server just became unusable, because it ran out of inodes (something that shouldn't happen on a relatively normal installation). The root-cause was a misbehaving CRM program creating way too many session files and never deleting them. However, while debugging, it would have been really really helpful if there were something in the logfiles. But it just failed silently: the lack of any error message makes diagnosing this error condition 100x harder than it should be. We get messages about being out of disk-space, but that's not helpful, especially when "df -h" shows it not to be true. So, the bug report/feature request is this: when the kernel cannot create a new file due to a shortage of inodes, it should emit a message to that effect, at least in dmesg (and ideally also to syslog). [For anyone else who chances upon this bug report, you can tell if you have run out of inodes with "df -i", and you can find the offending directories with: "find / -xdev -size +100k -type d" ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1665833] Re: inode exhaustion should be logged to dmesg
Sorry, I can't collect the report: apport isn't installed on the server, and the whole problem is that, having run out of inodes, I can't install anything (nor save files). Cleaning up and rebooting will destroy the logfiles of interest. The key point here is that: root@archimedes:/home/rjn# dmesg | grep -i inode [0.004000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) [1.640998] EXT4-fs (xvda2): 1 orphan inode deleted i.e. there is an absence of the log message along the lines of: "Warning: /dev/xvda2 has run out of inodes, cannot create new file" As requested, confirming anyway. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1665833 Title: inode exhaustion should be logged to dmesg Status in linux package in Ubuntu: Confirmed Bug description: Problem: My server just became unusable, because it ran out of inodes (something that shouldn't happen on a relatively normal installation). The root-cause was a misbehaving CRM program creating way too many session files and never deleting them. However, while debugging, it would have been really really helpful if there were something in the logfiles. But it just failed silently: the lack of any error message makes diagnosing this error condition 100x harder than it should be. We get messages about being out of disk-space, but that's not helpful, especially when "df -h" shows it not to be true. So, the bug report/feature request is this: when the kernel cannot create a new file due to a shortage of inodes, it should emit a message to that effect, at least in dmesg (and ideally also to syslog). [For anyone else who chances upon this bug report, you can tell if you have run out of inodes with "df -i", and you can find the offending directories with: "find / -xdev -size +100k -type d" ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338177] [NEW] BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295]
Public bug reported: I've just installed Utopic, and my machine is really slow to boot. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 [modified: boot/vmlinuz-3.15.0-6-generic] ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2642 F pulseaudio /dev/snd/controlC2: rjn2642 F pulseaudio /dev/snd/controlC0: rjn2642 F pulseaudio /dev/snd/controlC1: rjn2642 F pulseaudio Date: Sun Jul 6 00:58:31 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-05 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140703) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=41c3bf4e-49c3-4546-aea6-30a91309679d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-driver-fglrx kernel-oops utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338177 Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] Status in “linux” package in Ubuntu: New Bug description: I've just installed Utopic, and my machine is really slow to boot. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 [modified: boot/vmlinuz-3.15.0-6-generic] ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2642 F pulseaudio /dev/snd/controlC2: rjn2642 F pulseaudio /dev/snd/controlC0: rjn2642 F pulseaudio /dev/snd/controlC1: rjn2642 F pulseaudio Date: Sun Jul 6 00:58:31 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-05 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140703) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=41c3bf4e-49c3-4546-aea6-30a91309679d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x
[Kernel-packages] [Bug 1338177] Re: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295]
Dear Christopher, Thanks for your suggestion. I've done a few more experiments before and after updating the BIOS (to the latest version (4105 07/01/2013). Here are the results. 1. Old Bios. Mageia 3 + Fglrx driver => Worked fine 2. Old Bios, Kubuntu Trusty (installed yesterday, fully updated), Open-source (Radeon) driver. => No CPU hang. However, I did have a problem with video-modelines being auto-detected wrongly, (resulting in the monitors showing out-of range. I've since fixed that manually with xrandr --addmode and will shortly file a bug on it, but this is what set me off on the path of trying the binary drivers). 3. Old Bios, Trusty, and the fglrx driver (both fglrx and fglrx-update, as per https://help.ubuntu.com/community/BinaryDriverHowto/AMD ) => CPIU hang. 4. Old Bios, Utopic alpha, and open-source driver => No cpu hang (but the modeline problem still present) 5. New Bios, Utopic, open-source driver => No cpu hang (but the modeline problem still present) 6. New Bios, Utopic, fglrx CPU hang again (see dmesg attached) Best wishes Richard ** Attachment added: "Dmesg output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338177/+attachment/4147183/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338177 Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] Status in “linux” package in Ubuntu: Incomplete Bug description: I've just installed Utopic, and my machine is really slow to boot. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 [modified: boot/vmlinuz-3.15.0-6-generic] ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2642 F pulseaudio /dev/snd/controlC2: rjn2642 F pulseaudio /dev/snd/controlC0: rjn2642 F pulseaudio /dev/snd/controlC1: rjn2642 F pulseaudio Date: Sun Jul 6 00:58:31 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-05 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140703) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=41c3bf4e-49c3-4546-aea6-30a91309679d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] [NEW] fglrx deb postrm script hangs indefinitely
Public bug reported: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: New Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147251/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147243/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147246/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147249/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147245/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147248/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147252/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338622] [NEW] LCD monitor timing misdetected: 60Hz != 60 Hz
Public bug reported: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0 + 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 1600x1200_60.00 59.9* DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0 + 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x624
[Kernel-packages] [Bug 1338603] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147244/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147253/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] Re: fglrx deb postrm script hangs indefinitely
apport information ** Tags added: apport-collected utopic ** Description changed: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. + --- + ApportVersion: 2.14.4-0ubuntu1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: rjn2616 F pulseaudio + /dev/snd/controlC2: rjn2616 F pulseaudio + /dev/snd/controlC0: rjn2616 F pulseaudio + /dev/snd/controlC1: rjn2616 F pulseaudio + DistroRelease: Ubuntu 14.10 + HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac + InstallationDate: Installed on 2014-07-06 (0 days ago) + InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) + IwConfig: + eth0 no wireless extensions. + + eth1 no wireless extensions. + + lono wireless extensions. + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_GB:en + TERM=xterm + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.15.0-6-generic N/A + linux-backports-modules-3.15.0-6-generic N/A + linux-firmware1.132 + RfKill: + + Tags: utopic + Uname: Linux 3.15.0-6-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 07/01/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 4105 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: P8Z68-V LX + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147242/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0u
[Kernel-packages] [Bug 1338603] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147247/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338603] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1338603/+attachment/4147250/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338603 Title: fglrx deb postrm script hangs indefinitely Status in “linux” package in Ubuntu: Confirmed Bug description: I just installed fglrx (2:13.350.1-0ubuntu3) on Utopic. It causes a CPU hang (see Bug 1338177), so I wanted to remove it. Running: sudo apt-get purge fglrx fglrx-amdcccle silently hangs, indefinitely. The prompt just never returns (not even with Ctrl-C). I tracked the bug down to this script: /var/lib/dpkg/info/fglrx.postrm whose process I was able to kill, and dpkg then continued (to a non-graceful exit); -- Purging configuration files for fglrx (2:13.350.1-0ubuntu3) ... dpkg: error processing package fglrx (--purge): subprocess installed post-removal script was killed by signal (Terminated) Errors were encountered while processing: fglrx E: Sub-process /usr/bin/dpkg returned an error code (1) --- The offending line in the postrm script is this one: update-rc.d atieventsd remove >/dev/null Having commented it out, I was then able to re-run the sudo apt-get purge fglrx fglrx-amdcccle successfully. The root cause seems to be that the command: /usr/lib/insserv/insserv will sit there interminably, inactively, and unkillably. even sudo killall -9 insserv won't stop it. To fully recover from the insserv hang, I had to shut down the machine, with shutdown -h now, and even that didn't fully go down; I had to eventually physically reset the box. There are really 3 bugs here: 1. The fglrx package cannot be gracefully uninstalled. 2. insserv needs to be killed with fire. 3. the kernel's reboot or shutdown commands fail if a process like insserv is stuck in the "D" state. --- ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2616 F pulseaudio /dev/snd/controlC2: rjn2616 F pulseaudio /dev/snd/controlC0: rjn2616 F pulseaudio /dev/snd/controlC1: rjn2616 F pulseaudio DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-06 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=591b7866-2111-434a-8423-b79bbf373c85 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.15.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4105:bd07/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338622] Re: LCD monitor timing misdetected: 60Hz != 60 Hz
apport information ** Tags added: apport-collected utopic ** Description changed: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0 + 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7
[Kernel-packages] [Bug 1338622] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147262/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1
[Kernel-packages] [Bug 1338622] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147267/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left i
[Kernel-packages] [Bug 1338622] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147266/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left i
[Kernel-packages] [Bug 1338622] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147270/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (
[Kernel-packages] [Bug 1338622] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147265/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0
[Kernel-packages] [Bug 1338622] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147272/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal l
[Kernel-packages] [Bug 1338622] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147264/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inv
[Kernel-packages] [Bug 1338622] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147271/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left
[Kernel-packages] [Bug 1338622] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147263/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (norm
[Kernel-packages] [Bug 1338622] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147269/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+16
[Kernel-packages] [Bug 1338622] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147273/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.
[Kernel-packages] [Bug 1338622] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1338622/+attachment/4147268/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (
[Kernel-packages] [Bug 1338177] Re: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295]
Hello. I tried using both of the Ubuntu packages of the driver, from the utopic repositories, namely: fglrx and fglrx-updates. I also observed the same problem with the fglrx packages under Trusty. The versions were: fglrx_13.350.1-0ubuntu3_amd64.deb fglrx- amdcccle_13.350.1-0ubuntu3_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338177 Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] Status in “linux” package in Ubuntu: Incomplete Bug description: I've just installed Utopic, and my machine is really slow to boot. WORKAROUND: Use Radeon driver. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 [modified: boot/vmlinuz-3.15.0-6-generic] ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2642 F pulseaudio /dev/snd/controlC2: rjn2642 F pulseaudio /dev/snd/controlC0: rjn2642 F pulseaudio /dev/snd/controlC1: rjn2642 F pulseaudio Date: Sun Jul 6 00:58:31 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-05 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140703) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=41c3bf4e-49c3-4546-aea6-30a91309679d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338622] Re: LCD monitor timing misdetected: 60Hz != 60 Hz
Hi Joseph, Can I ask why you think this might be a kernel bug? I've had this problem for about 11 years, with multiple kernels, distros and both AMD and Nvidia graphics cards. I always fixed it with the binary driver. However, I only just discovered that it could also be fixed by the correct modeline in X. My current hunch is that these particular monitors are very choosy about modelines (notably, when X drives them at 60Hzx75kHz, they display an error about the timing being out of range and ask me to set it to 60x75). So either: 1) X is mis-calculating the modeline from the information given by the monitor's EDID. 2) There is an obscure compatibility bug, where these specific monitors (this model and vendor) need a special-case hack. I think (1) is the case, because Xorg already auto-detects them at 1600x1200@@60Hz, and if I then manually generate a modeline with "cvt 1600 1200" and force that, everything works. HTH - Richard P.S. Here is a picture of the problematic monitor. I bought this pair of 1600x1200 20" monitors as an investment in not getting eyestrain, back in 2003. They've worked really welll since then, but they were one of the first set of devices to support DVI at that resolution. This might be a clue to the compatibility problem. Photo here: http://skinflint.co.uk/eu/v7-videoseven-l20-1cm-a40169.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Incomplete Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' .
[Kernel-packages] [Bug 1338622] Re: LCD monitor timing misdetected: 60Hz != 60 Hz
I did just try the upstream kernel as requested (linux-image-3.16.0-031600rc4-generic). This does (mostly) fix the problem, but not entirely, so I'll tag it bug-exists upstream. 1) I have all 3 monitors working correctly if I combine kernel 3.16 AND a hand-tuned xorg.conf 2) Without Xorg.conf , the monitors are not correctly autoconfigured. 3) Everything is now great in XFCE, but under KDE, 2 of the 3 monitors don't show the mouse-pointer. In case it's relevant, I'm still seeing dmesg errors of this type: [ 60.216937] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 60.216941] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C7E8 (len 62, WS 0, PS 0) @ 0xC804 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Confirmed Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connect
