[Bug 1944991] Re: Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) when shadowPrimary is off
** Package changed: linux (Ubuntu) => xserver-xorg-video-ati (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) when shadowPrimary is off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) if some options not used
It looks like (with glamor) that adding: Option "ShadowPrimary" "on" is enough to work around the bug on resume. ** Summary changed: - Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) if some options not used + Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) when shadowPrimary is off -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) when shadowPrimary is off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
It looks like suspend-resume works with glamor if I have the next two lines (I think, still unsure, that both are necessary): Section "Device" #Identifier "Configured Video Device" #Driver "radeon" #Option "AccelMethod" "EXA" Identifier "Configured Video Device" Driver "radeon" #Option "AccelMethod" "glamor" #legacy "exa" #Option "DRI" "3" #legacy "2" #Option "TearFree" "on" #Option "ColorTiling" "on" Option "ColorTiling2D" "on" Option "ShadowPrimary" "on" #only possible with "glamor" AccelMethod EndSection The following dmesg log is successful: [ 76.376583] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 76.378801] OOM killer disabled. [ 76.378803] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 76.380005] printk: Suspending console(s) (use no_console_suspend to debug) [ 76.402987] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 76.403159] sd 0:0:0:0: [sda] Stopping disk [ 76.445147] serial 00:04: disabled [ 76.445223] parport_pc 00:03: disabled [ 76.847345] ACPI: Preparing to enter system sleep state S3 [ 76.848098] PM: Saving platform NVS memory [ 76.848100] Disabling non-boot CPUs ... [ 76.848717] IRQ 25: no longer affine to CPU1 [ 76.849735] smpboot: CPU 1 is now offline [ 76.850726] IRQ 22: no longer affine to CPU2 [ 76.851750] smpboot: CPU 2 is now offline [ 76.853525] ACPI: Low-level resume complete [ 76.853608] PM: Restoring platform NVS memory [ 76.853633] PCI-DMA: Resuming GART IOMMU [ 76.853635] PCI-DMA: Restoring GART aperture settings [ 76.853643] LVT offset 1 assigned for vector 0x400 [ 76.853661] LVT offset 1 assigned [ 76.854003] Enabling non-boot CPUs ... [ 76.854101] x86: Booting SMP configuration: [ 76.854103] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 76.854551] microcode: CPU1: patch_level=0x0195 [ 76.857615] CPU1 is up [ 76.857672] smpboot: Booting Node 0 Processor 2 APIC 0x2 [ 76.858117] microcode: CPU2: patch_level=0x0195 [ 76.861277] CPU2 is up [ 76.863872] ACPI: Waking up from system sleep state S3 [ 76.864583] ahci :00:11.0: set SATA to AHCI mode [ 76.888031] parport_pc 00:03: activated [ 76.889094] serial 00:04: activated [ 76.890950] tg3 :3f:00.0 enp63s0: Link is down [ 76.891910] sd 0:0:0:0: [sda] Starting disk [ 76.893464] [drm] PCIE GART of 512M enabled (table at 0xC004). [ 76.893531] radeon :01:05.0: WB enabled [ 76.893537] radeon :01:05.0: fence driver on ring 0 use gpu addr 0xac00 [ 76.893856] debugfs: File 'radeon_ring_gfx' in directory '0' already present! [ 76.925648] [drm] ring test on 0 succeeded in 1 usecs [ 76.925681] [drm] ib test on ring 0 succeeded in 0 usecs [ 77.210929] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 77.210973] ata3: SATA link down (SStatus 0 SControl 300) [ 77.211016] ata4: SATA link down (SStatus 0 SControl 300) [ 77.219093] ata2.00: configured for UDMA/100 [ 77.737610] tpm tpm0: TPM is disabled/deactivated (0x7) [ 77.741747] OOM killer enabled. [ 77.741750] Restarting tasks ... done. [ 77.759486] PM: suspend exit [ 79.981259] tg3 :3f:00.0 enp63s0: Link is up at 1000 Mbps, full duplex [ 79.981286] tg3 :3f:00.0 enp63s0: Flow control is on for TX and on for RX [ 80.896609] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 80.898040] ata1.00: configured for UDMA/100 [ 83.754767] tg3 :3f:00.0 enp63s0: Link is up at 1000 Mbps, full duplex [ 83.754798] tg3 :3f:00.0 enp63s0: Flow control is on for TX and on for RX [ 83.754829] IPv6: ADDRCONF(NETDEV_CHANGE): enp63s0: link becomes ready client@client-HP-Compaq-dc5850-Small-Form-Factor:~$ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) + Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) if some options not used -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) if some options not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
I see in dmesg log after resume: oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: debugfs: File 'radeon_ring_gfx' in directory '0' already pr> Also: oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: serial 00:04: disabled oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: parport_pc 00:03: disabled oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: ACPI: Preparing to enter system sleep state S3 oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: PM: Saving platform NVS memory oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: Disabling non-boot CPUs ... oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: smpboot: CPU 1 is now offline oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: IRQ 22: no longer affine to CPU2 oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: smpboot: CPU 2 is now offline oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: ACPI: Low-level resume complete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529967/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529970/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529968/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529969/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529966/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529965/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529963/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529961/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529964/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529962/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529960/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529959/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529958/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529957/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1944991/+attachment/5529956/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
apport information ** Tags added: apport-collected impish ** Description changed: GPU: ATI Radeon 3100 Graphics (ChipID = 0x9611) (RS780) GPU Lockup message in dmesg output after resume: [ 916.000550] radeon :01:05.0: ring 0 stalled for more than 10084msec [ 916.000569] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 916.516556] radeon :01:05.0: ring 0 stalled for more than 10600msec [ 916.516569] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 917.024566] radeon :01:05.0: ring 0 stalled for more than 11108msec [ 917.024575] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 917.536558] radeon :01:05.0: ring 0 stalled for more than 11620msec [ 917.536570] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 918.048571] radeon :01:05.0: ring 0 stalled for more than 12132msec [ 918.048580] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) ... [ 935.726783] radeon :01:05.0: GPU softreset: 0x0019 [ 935.726788] radeon :01:05.0: R_008010_GRBM_STATUS = 0xE57034E0 [ 935.726793] radeon :01:05.0: R_008014_GRBM_STATUS2 = 0x00110103 [ 935.726797] radeon :01:05.0: R_000E50_SRBM_STATUS = 0x2040 [ 935.726801] radeon :01:05.0: R_008674_CP_STALLED_STAT1 = 0x0100 [ 935.726805] radeon :01:05.0: R_008678_CP_STALLED_STAT2 = 0x1002 [ 935.726809] radeon :01:05.0: R_00867C_CP_BUSY_STAT = 0x00028486 [ 935.726813] radeon :01:05.0: R_008680_CP_STAT = 0x80838645 [ 935.726817] radeon :01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 935.779906] radeon :01:05.0: R_008020_GRBM_SOFT_RESET=0x7FEF [ 935.779962] radeon :01:05.0: SRBM_SOFT_RESET=0x0100 [ 935.782061] radeon :01:05.0: R_008010_GRBM_STATUS = 0xA0003030 [ 935.782066] radeon :01:05.0: R_008014_GRBM_STATUS2 = 0x0003 [ 935.782070] radeon :01:05.0: R_000E50_SRBM_STATUS = 0x20008040 [ 935.782074] radeon :01:05.0: R_008674_CP_STALLED_STAT1 = 0x [ 935.782078] radeon :01:05.0: R_008678_CP_STALLED_STAT2 = 0x [ 935.782081] radeon :01:05.0: R_00867C_CP_BUSY_STAT = 0x [ 935.782085] radeon :01:05.0: R_008680_CP_STAT = 0x8010 [ 935.782089] radeon :01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 935.782097] radeon :01:05.0: GPU reset succeeded, trying to resume Graphics is broken... text hardly readable, interface not responding. First observed on latest Mint (20.2)... then discovered Peppermint 10 was not affected. I believe Peppermint 10 is based on 18.04 and I am unsure why it is not affected. I tested with many versions of Ubuntu... Before 17.04... no problem... but was using EXA acceleration. 17.04 first to use Glamor... screen corruption is not obvious... but dmesg show GPU lockup... 17.10 and following is really problematic after resume, but possible to Ctrl-Alt-F4 to go to a text console and ... sudo reboot. There is a possibility I missed the exact version as I don't have my notes near me. Adding Option "AccelMethod" "EXA" at the good place in xorg.conf file have fixed the issue. - I am unlikely to have access again to that specific computer in the - future. + I am unlikely to have access again to that specific computer in the future. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu69 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 6610 F pulseaudio + CasperMD5CheckResult: pass + CasperVersion: 1.465 + DistroRelease: Ubuntu 21.10 + IwConfig: + lono wireless extensions. + + enp63s0 no wireless extensions. + LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210920) + MachineType: Hewlett-Packard HP Compaq dc5850 Small Form Factor + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- + ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.13.0-16-generic N/A + linux-backports-modules-5.13.0-16-generic N/A + linux-firmware 1.200 + RfKill: + + Tags: impish + Uname: Linux
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
I found the following link: https://forum.manjaro.org/t/new-install-amd-fx-6300-wont-wake-from-suspend/39471/10 Suggesting that setting TearFree on may help (RS780L) However... I wonder if ShadowPrimary did not help. Section "Device" Identifier "Radeon" Driver "radeon" Option "AccelMethod" "glamor" #legacy "exa" Option "DRI" "3" #legacy "2" Option "TearFree" "on" Option "ColorTiling" "on" Option "ColorTiling2D" "on" Option "ShadowPrimary" "on" #only possible with "glamor" AccelMethod EndSection Note that it should be in a file /usr/share/X11/xorg.conf.d/20-radeon.conf on Ubuntu. And should rename my suggested /etc/X11/xorg.conf to xorg.conf.old. I might have temporary access to the computer in the next 48h to test it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1342561] Re: [Asus X750LN] Touchpad not recognized
I see there is already a proposed patch... But I'd like to mention https://wiki.ubuntu.com/DebuggingTouchpadDetection for others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342561 Title: [Asus X750LN] Touchpad not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
If you think about using this with amdgpu driver rather than radeon... use 'Option "AccelMethod" "none"' rather than EXA... because I think, not sure, amdgpu does not support EXA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
Suggested /etc/X11/xorg.conf file. I just edited it a bit... not really tested. ** Attachment added: "Suggested /etc/X11/xorg.conf file to work around the bug" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+attachment/5527755/+files/xorg.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
** Attachment added: "Dmesg showing errors after resume" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+attachment/5527751/+files/dmesg_after_resume.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
I confirm I will not have access to that particular machine... But maybe I will find an other computer affected by this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
Added a comment linking here on https://bugzilla.kernel.org/show_bug.cgi?id=85421 ** Bug watch added: Linux Kernel Bug Tracker #85421 https://bugzilla.kernel.org/show_bug.cgi?id=85421 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
I am unsure if I will have access again to the computer. But if that's the case, I intend the suggested apport-collect command. Also, to do my tests I did use: sudo su echo mem > /sys/state/power to cause suspend to ram. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
The BIOS of that computer have some ACPI bugs: (I believe latest BIOS but unsure... I did upgrade to 3.14) but still showing as 3.14. DMI: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6 v03.14 11/15/2011 [0.283156] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] [0.283163] ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared 5, ACPI requires 4 (20210331/nsarguments-162) [0.283317] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0._OSC.CAPD], AE_ALREADY_EXISTS (20210331/dsfield-184) [0.283373] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20210331/dswload2-477) [0.283422] Initialized Local Variables for Method [_OSC]: [0.283424] Local0: (ptrval)Integer 0001 [0.283432] Local1: (ptrval)Integer 0005 [0.283439] Initialized Arguments for Method [_OSC]: (5 arguments defined for method invocation) [0.283440] Arg0: (ptrval)Buffer(16) 5B 4D DB 33 F7 1F 1C 40 [0.283452] Arg1: (ptrval)Integer 0001 [0.283457] Arg2: (ptrval)Integer 0003 [0.283462] Arg3: (ptrval)Buffer(12) 01 00 00 00 1F 01 00 00 [0.283479] ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (20210331/psparse-529) [0.283536] acpi PNP0A08:00: _OSC: platform retains control of PCIe features (AE_ALREADY_EXISTS) [0.283549] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] Re: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
I note that daily Ubuntu [will become Ubuntu 21.10] (of yesterday) was affected by this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944991] [NEW] Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611)
Public bug reported: GPU: ATI Radeon 3100 Graphics (ChipID = 0x9611) (RS780) GPU Lockup message in dmesg output after resume: [ 916.000550] radeon :01:05.0: ring 0 stalled for more than 10084msec [ 916.000569] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 916.516556] radeon :01:05.0: ring 0 stalled for more than 10600msec [ 916.516569] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 917.024566] radeon :01:05.0: ring 0 stalled for more than 11108msec [ 917.024575] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 917.536558] radeon :01:05.0: ring 0 stalled for more than 11620msec [ 917.536570] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 918.048571] radeon :01:05.0: ring 0 stalled for more than 12132msec [ 918.048580] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) ... [ 935.726783] radeon :01:05.0: GPU softreset: 0x0019 [ 935.726788] radeon :01:05.0: R_008010_GRBM_STATUS = 0xE57034E0 [ 935.726793] radeon :01:05.0: R_008014_GRBM_STATUS2 = 0x00110103 [ 935.726797] radeon :01:05.0: R_000E50_SRBM_STATUS = 0x2040 [ 935.726801] radeon :01:05.0: R_008674_CP_STALLED_STAT1 = 0x0100 [ 935.726805] radeon :01:05.0: R_008678_CP_STALLED_STAT2 = 0x1002 [ 935.726809] radeon :01:05.0: R_00867C_CP_BUSY_STAT = 0x00028486 [ 935.726813] radeon :01:05.0: R_008680_CP_STAT = 0x80838645 [ 935.726817] radeon :01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 935.779906] radeon :01:05.0: R_008020_GRBM_SOFT_RESET=0x7FEF [ 935.779962] radeon :01:05.0: SRBM_SOFT_RESET=0x0100 [ 935.782061] radeon :01:05.0: R_008010_GRBM_STATUS = 0xA0003030 [ 935.782066] radeon :01:05.0: R_008014_GRBM_STATUS2 = 0x0003 [ 935.782070] radeon :01:05.0: R_000E50_SRBM_STATUS = 0x20008040 [ 935.782074] radeon :01:05.0: R_008674_CP_STALLED_STAT1 = 0x [ 935.782078] radeon :01:05.0: R_008678_CP_STALLED_STAT2 = 0x [ 935.782081] radeon :01:05.0: R_00867C_CP_BUSY_STAT = 0x [ 935.782085] radeon :01:05.0: R_008680_CP_STAT = 0x8010 [ 935.782089] radeon :01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 935.782097] radeon :01:05.0: GPU reset succeeded, trying to resume Graphics is broken... text hardly readable, interface not responding. First observed on latest Mint (20.2)... then discovered Peppermint 10 was not affected. I believe Peppermint 10 is based on 18.04 and I am unsure why it is not affected. I tested with many versions of Ubuntu... Before 17.04... no problem... but was using EXA acceleration. 17.04 first to use Glamor... screen corruption is not obvious... but dmesg show GPU lockup... 17.10 and following is really problematic after resume, but possible to Ctrl-Alt-F4 to go to a text console and ... sudo reboot. There is a possibility I missed the exact version as I don't have my notes near me. Adding Option "AccelMethod" "EXA" at the good place in xorg.conf file have fixed the issue. I am unlikely to have access again to that specific computer in the future. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944991 Title: Resume with glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923302] Re: tumblerd crashed with SIGSEGV (memory leaks detected)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923302 Title: tumblerd crashed with SIGSEGV (memory leaks detected) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1923302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168558] Re: tumblerd crashed with SIGSEGV in tumbler_thumbnailer_create()
Like in my yet private bug #1923302 Stack memory exhausted (SP below stack segment) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168558 Title: tumblerd crashed with SIGSEGV in tumbler_thumbnailer_create() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tumbler/+bug/1168558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312]
The patch is included in: Linux 4.14.125 Linux 4.19.50 Linux 5.1.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
The patch is included in: Linux 4.14.125 Linux 4.19.50 Linux 5.1.9 I don't have access to the laptop on which I investigated this problem anymore. But it could be tested from the built kernel packages at: https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.125/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.50/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.9/ Install linux-headers then linux-modules then linux-image (I think) In fact, testing on other ATI hardware too see not bad results happen would be... reassuring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
** Patch added: "patch radeon-display.c for latest kernel (5.0.0rc7)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+attachment/5240017/+files/radeon-display.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Well, It seems to take more than 12 hours ( I did stopped it ) to compile a kernel (many features deactivated) on my atom based laptop. Will retry. But the line I wanted to comment out does not seems to exist anymore. But I found that the function to select PLL values show them before returning in a DRM_DEBUG_KMS macro. I also found that if booted with kernel parameter drm.debug=4 then KernelModeSettings related messages are added to dmesg output. So I expect to be able to compare tomorrow PLL values for the old version where the bug does not manifest to a new one where the bug manifest itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Indeed, the two radeon parameters for PLL mention in previous message does not seems to appear anymore in modinfo radeon. paul@paul-NC210-NC110:~/linux-stable$ git log --oneline v3.15-rc1..v3.15-rc2 | grep radeon bcddee29b0b8 drm/radeon/ci: make sure mc ucode is loaded before checking the size 8c79bae6a30f drm/radeon/si: make sure mc ucode is loaded before checking the size f8a2645ecede drm/radeon: improve PLL params if we don't match exactly v2 74073c9dd299 drm/radeon: memory leak on bo reservation failure. v2 681941c1790b drm/radeon: fix VCE fence command 7e1858f9aff7 drm/radeon: re-enable mclk dpm on R7 260X asics 277babc374f6 drm/radeon: add support for newer mc ucode on CI (v2) 1ebe92802eaf drm/radeon: add support for newer mc ucode on SI (v2) 5fb9cc4d8b16 drm/radeon: apply more strict limits for PLL params v2 6abc6d5c73b2 drm/radeon: update CI DPM powertune settings 90c4cde9d5a2 drm/radeon: fix runpm handling on APUs (v4) 57700ad1f2f2 drm/radeon: disable mclk dpm on R7 260X 8902e6f2b832 drm/radeon: Improve vramlimit module param documentation be0949f5eb9c drm/radeon: fix audio pin counts for DCE6+ (v2) 379dfc25e257 drm/radeon/dp: switch to the common i2c over aux code 25377b921b40 drm/radeon/dp: handle zero sized i2c over aux transactions (v2) paul@paul-NC210-NC110:~/linux-stable$ paul@paul-NC210-NC110:~/linux-stable$ git show 5fb9cc4d8b16 commit 5fb9cc4d8b1639b9a7487c1ee7b2b0c52877327d Author: Christian König Date: Fri Apr 4 13:45:42 2014 +0200 drm/radeon: apply more strict limits for PLL params v2 Letting post and refernce divider get to big is bad for signal stability. v2: increase the limit to 210 Signed-off-by: Christian König diff --git a/drivers/gpu/drm/radeon/radeon_display.c b/drivers/gpu/drm/radeon/radeon_display.c index 386cfa4c194d..2f42912031ac 100644 --- a/drivers/gpu/drm/radeon/radeon_display.c +++ b/drivers/gpu/drm/radeon/radeon_display.c @@ -937,6 +937,9 @@ void radeon_compute_pll_avivo(struct radeon_pll *pll, } post_div = post_div_best; + /* limit reference * post divider to a maximum */ + ref_div_max = min(210 / post_div, ref_div_max); + /* get matching reference and feedback divider */ ref_div = max(den / post_div, 1u); fb_div = nom; paul@paul-NC210-NC110:~/linux-stable$ I might try to recompile kernel with that line commented out. But it has been many years I did not compile a kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
From: https://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/CHANGES I see the folowing changes for radeon: Alex Deucher (13): drm/radeon/dp: handle zero sized i2c over aux transactions (v2) drm/dp/i2c: send bare addresses to properly reset i2c connections (v4) drm/dp/i2c: Update comments about common i2c over dp assumptions (v3) drm/radeon/dp: switch to the common i2c over aux code drm/radeon: fix audio pin counts for DCE6+ (v2) drm/radeon: disable mclk dpm on R7 260X drm/radeon: fix runpm handling on APUs (v4) drm/radeon: update CI DPM powertune settings drm/radeon: add support for newer mc ucode on SI (v2) drm/radeon: add support for newer mc ucode on CI (v2) drm/radeon: re-enable mclk dpm on R7 260X asics drm/radeon/si: make sure mc ucode is loaded before checking the size drm/radeon/ci: make sure mc ucode is loaded before checking the size Christian König (2): drm/radeon: apply more strict limits for PLL params v2 drm/radeon: improve PLL params if we don't match exactly v2 Christoph Jaeger (2): ... drm/radeon: fix VCE fence command Quentin Casasnovas (1): drm/radeon: memory leak on bo reservation failure. v2 The: Christian König (2): drm/radeon: apply more strict limits for PLL params v2 drm/radeon: improve PLL params if we don't match exactly v2 rings a bell for me, because I believe someone somewhere was saying that a kernel parameter speaking of PLL was fixing the problem... but people did not find PLL parameters for radeon, so people did not follow about that comment. From: https://www.x.org/releases/current/doc/man/man4/radeon.4.xhtml I see: Option "LVDSProbePLL" "boolean" When BIOS panel information isn’t available (like on PowerBooks), it may still be necessary to use the firmware-provided PLL values for the panel or flickering will happen. This option will force probing of the current value programmed in the chip when X is launched in that case. This is only useful for LVDS panels (laptop internal panels). The default is on. Also: Option "DefaultTMDSPLL" "boolean" Use the default driver provided TMDS PLL values rather than the ones provided by the BIOS. This option has no effect on Mac cards. Enable this option if you are having problems with a DVI monitor using the internal TMDS controller. The default is off. Also: drm/radeon: update CI DPM powertune settings ring an other bell, because I think I remember someone saying something about DPM in some message. Sorry for not being more specific. A similar, older fixed closed bug: https://bugzilla.kernel.org/show_bug.cgi?id=26552 ** Bug watch added: Linux Kernel Bug Tracker #26552 https://bugzilla.kernel.org/show_bug.cgi?id=26552 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Ok, I have access at "work" on a Compaq nx9420, for a few days. linux 3.15.0-rc2 is first one to flickers, but goes to busybox linux 3.15.0-rc1 does not flickers, but goes to busybox I found: mounting /dev/sda1 on /root: invalid argument and then initrd not mounting. previous version, 3.14.79: no flickers, boot to graphics mode will try to study changes for 3.15.0-rc2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
I just retried by installing headers, then reinstall kernel-generic. This time wifi works. Note that these packages won't show in Synaptic. Will show in dpkg -l|grep kernel. Use dpkg -r to remove them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Well, I tested on my laptop with: paul@paul-NC210-NC110:~$ cat /proc/version Linux version 3.14.79-031479-generic (kernel@gloin) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #20160910530 SMP Sun Sep 11 09:41:06 UTC 2016 When I used gdebi to install the kernel .deb, in the details, there were some errors. I believe this was because I did not installed headers .deb before... I would suggest you install the headers .deb before... but it work even without the headers .deb. Also gdebi said version was already installed: I am pretty sure it was not. I lost my wifi however after rebooting with that version (I plugged Ethernet wire for writing this). And I am on Linux Mint 19.1. When I rebooted, it continue to boot with old kernel, and was not showing me the menu... even if I pressed Esc and Shift. So I edited /etc/default/grub from: GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=0 to: GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=10 but I think this could be needed only on Mint. after that, advanced options were showing, and I was able to select old kernel version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Thanks for trying the tearfree option! (ok, it don't work) By reading: https://wiki.ubuntu.com/Kernel/MainlineBuilds I discovered: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D which would allow to download prebuild .deb for old mwainline kernels. I am a bit sceptical if new versions of ubuntu would boot with so old versions. But it could help someone pinpoint the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Someone said: "I tried this with a Ubuntu 17.10 and could not boot. I had to use a rescue boot and remove the lines again to get it up and running." from:https://askubuntu.com/questions/794865/16-04-ati-mobility-radeon-x1600-full-resolution-flickering So, try with care! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
I guess I would rather add the two option lines (with same indentation) to: file:///usr/share/X11/xorg.conf.d/10-radeon.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
The bug have been reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=108514 https://forums.linuxmint.com/viewtopic.php?t=229387 suggest the bug could be "fixed" by creating /usr/share/X11/xorg.conf.d/20-radeon.conf with: Section "Device" Identifier "Radeon" Driver "radeon" Option "AccelMethod" "glamor" Option "TearFree" "on" EndSection Someone could try? ** Bug watch added: freedesktop.org Bugzilla #108514 https://bugs.freedesktop.org/show_bug.cgi?id=108514 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735067] Re: upgrade to Mint 18.3 not in edit if system is in french
** Project changed: linuxmint => update-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735067 Title: upgrade to Mint 18.3 not in edit if system is in french To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1735067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267922] Re: Installer becomes confused and crashes when grub-install fails
I copy here a link to message of someone who seems to have investigated this quite far: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/686859/comments/15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267922 Title: Installer becomes confused and crashes when grub-install fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1267922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267922] Re: Installer becomes confused and crashes when grub-install fails
** Tags added: artful beta1 ** Tags added: grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267922 Title: Installer becomes confused and crashes when grub-install fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1267922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267922] Re: Installer becomes confused and crashes when grub-install fails
This is still an issue in 17.10 beta 1 (xubuntu 32 bits). In my case, I created LVM partitions, and ubiquity suggested to install grub on dm-0, that sounded odd to me, but I tried it. Grub failed to install. I could select new destination in the window, to try, bug nothing happen when I accepted. Also, giving up installation option, was not responding either. Pretty much like what I remembered from previous versions. I don't know about unomounting /target/dev as the original poster said however. I finally 'sudo killall ubiquity' to give up installation and give better options (created a boot 30M boot partition before installing). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267922 Title: Installer becomes confused and crashes when grub-install fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1267922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714634] Re: starting gnome-software: segfault at 0 ip b64a38e6 sp bffe1d68 error 4 in libc-2.24.so[b6413000+1b3000]
I just made the updates, without restarting (because I use 'Try Ubuntu'). Now it does launch! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714634 Title: starting gnome-software: segfault at 0 ip b64a38e6 sp bffe1d68 error 4 in libc-2.24.so[b6413000+1b3000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1714634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714634] [NEW] starting gnome-software: segfault at 0 ip b64a38e6 sp bffe1d68 error 4 in libc-2.24.so[b6413000+1b3000]
Public bug reported: In: xubuntu-17.10-beta1-desktop-i386.iso, running in 'Try Ubuntu'. Everytime I try to start gnome-software I get nothing except this error in dmesg: [ 388.510237] gnome-software[4251]: segfault at 0 ip b64548e6 sp bffaa1c8 error 4 in libc-2.24.so[b63c4000+1b3000] [ 672.893089] gnome-software[4400]: segfault at 0 ip b650a8e6 sp bfdb6e68 error 4 in libc-2.24.so[b647a000+1b3000] [ 735.140781] gnome-software[4464]: segfault at 0 ip b648f8e6 sp bfa5aaa8 error 4 in libc-2.24.so[b63ff000+1b3000] [ 859.557640] gnome-software[4474]: segfault at 0 ip b64a38e6 sp bffe1d68 error 4 in libc-2.24.so[b6413000+1b3000] apport does not seems to catch it: xubuntu@xubuntu:~$ apport-cli Aucun rapport de plantage en attente. Essayer --help pour plus d'informations. (no report) (gdb) run Starting program: /usr/bin/gnome-software [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [New Thread 0xb39b0b40 (LWP 4665)] [New Thread 0xb2fffb40 (LWP 4666)] [New Thread 0xb25ffb40 (LWP 4667)] [New Thread 0xb1032b40 (LWP 4668)] Thread 1 "gnome-software" received signal SIGSEGV, Segmentation fault. __strchr_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strchr-sse2-bsf.S:60 60 ../sysdeps/i386/i686/multiarch/strchr-sse2-bsf.S: Aucun fichier ou dossier de ce type. (gdb) bt #0 __strchr_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strchr-sse2-bsf.S:60 #1 0xb7e84f7e in g_param_spec_pool_lookup () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #2 0xb7e7fe07 in g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #3 0xb7e802a9 in g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #4 0x0043af6c in ?? () #5 0x00447313 in gs_shell_change_mode () #6 0x00449d1f in gs_shell_set_mode () #7 0x00423af3 in ?? () #8 0xb7e78d08 in g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #9 0xb7e8bb95 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #10 0xb7e94bf3 in g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #11 0xb7e953a5 in g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #12 0xb7bf4330 in g_application_activate () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #13 0xb7bf4b13 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #14 0xb7bf4d3f in g_application_run () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ---Type to continue, or q to quit--- CPU supports SSE2: xubuntu@xubuntu:~$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 75 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping: 2 microcode : 0x62 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good cpuid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch vmmcall bugs: fxsave_leak sysret_ss_attrs swapgs_fence amd_e400 bogomips: 2009.18 clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 75 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping: 2 microcode : 0x62 cpu MHz : 1000.000 cache size : 512 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good cpuid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch vmmcall bugs: fxsave_leak sysret_ss_attrs swapgs_fence amd_e400 bogomips: 2009.18 clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc xubuntu@xubuntu:~$ ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: artful beta1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714634 Title: starting gnome-software: segfault at 0 ip b64a38e6 sp bffe1d68 error 4 in libc-2.24.so[b6413000+1b3000] To manage notifications about this
[Bug 420933] Re: Current grub-pc takes several minutes to show menu
I have an hypothesis. I have seen that when I do a grub ls on my bios_boot (flag in GPARTED) partition, it takes about 3 mins to list it. I believe this is due to the fact that I put clear partition typed for that partition in gparted. So I belive that when grub 2.0.2 do a search on that partition, it try to 'mount' it with all known partition types to figure out what it is. So what I am thinking to do is to add on my search commands, the undocumented hint=[guess to what the search should return as partition answer], that way, I expect search to try that partition first, and then avoid passing by the bios_boot partition without a known type that make things very slow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/420933 Title: Current grub-pc takes several minutes to show menu To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/420933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639324] [NEW] Lubuntu 16.10 cannot be installed offline because misssing grub-pc (grub-install)
Public bug reported: Was trying Lubuntu 16.10 offline. First I tried intall in Grub, but grub-install failed, and was gone in the popup window error (which there is no way to close, but a bug for that already exist). So I try to install in "Test Ubuntu", but it did the same. I search for grub-install and found out it was not there. In log file, I found the system was trying to 'apt-install grub-pc' but could not (I was in a place without Internet). And indeed I saw that grub-pc package was not installed (on the DVD). ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Lubuntu 16.10 cannot be installed online because misssing grub-pc (grub-install) + Lubuntu 16.10 cannot be installed offline because misssing grub-pc (grub-install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639324 Title: Lubuntu 16.10 cannot be installed offline because misssing grub-pc (grub-install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1639324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608006] Re: "bootloader install failed" dialog unresponsive
Think I got the same with Lubuntu 16.10, because grub-install is not present, grub-pc is not part of the DVD, and I was offline I got that dialog. It is responsive (I can select any options) but if I select continue installation, or end installation, or close the window with close decoration, nothing will make the window to go away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608006 Title: "bootloader install failed" dialog unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1608006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632184] Re: image build with bodhibuilder crash near end-installation
Lubuntu 16.10 (32&64 bits) works fine (install from grub menu). Seems to have change quite much since 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632184 Title: image build with bodhibuilder crash near end-installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1632184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632184] Re: image build with bodhibuilder crash near end-installation
After trying to reboot machine to test, an error occured and system opened me a session for me to test what was going on. In it I just ran "$ gksudo ubiquity gtk_ui" and it worked flawlessly. Same medium, same answers, but this time in the environment, in root mode. Which suggests to me that the problem appears in non-english, while install from GRUB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632184 Title: image build with bodhibuilder crash near end-installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1632184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632184] Re: image build with bodhibuilder crash near end-installation
Indeed I had chosen 'Install' directly in Grub (which seems to suggest that because it is not run by root, it failed to create a temporary file in /target/etc/default while installing language pack). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632184 Title: image build with bodhibuilder crash near end-installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1632184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632184] Re: image build with bodhibuilder crash near end-installation
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1579454/comments/10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632184 Title: image build with bodhibuilder crash near end-installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1632184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632184] Re: image build with bodhibuilder crash near end-installation
Now that I look at the end of Syslog, this is probably more relevent: Oct 10 22:58:33 gl finish-install: Disabling CDROM entries in sources.list Oct 10 22:58:33 gl ubiquity: sed: impossible d'ouvrir le fichier temporaire /target/etc/apt/sedP1IjGy: Permission non accordée Oct 10 22:58:33 gl /plugininstall.py: Exception during installation: Oct 10 22:58:33 gl /plugininstall.py: Traceback (most recent call last): Oct 10 22:58:33 gl /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1778, in Oct 10 22:58:33 gl /plugininstall.py: install.run() Oct 10 22:58:33 gl /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 78, in wrapper Oct 10 22:58:33 gl /plugininstall.py: func(self) Oct 10 22:58:33 gl /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 198, in run Oct 10 22:58:33 gl /plugininstall.py: self.configure_locale() Oct 10 22:58:33 gl /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 562, in configure_locale Oct 10 22:58:33 gl /plugininstall.py: self.run_plugin(language_plugin) Oct 10 22:58:33 gl /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 547, in run_plugin Oct 10 22:58:33 gl /plugininstall.py: "Plugin %s failed with code %s" % (plugin.NAME, ret)) Oct 10 22:58:33 gl /plugininstall.py: ubiquity.install_misc.InstallStepError: Plugin language failed with code 4 Oct 10 22:58:33 gl /plugininstall.py: Oct 10 22:58:49 gl ubiquity: Gtk-Message: Failed to load module "overlay-scrollbar" Oct 10 22:58:49 gl ubiquity: Gtk-Message: Failed to load module "overlay-scrollbar" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632184 Title: image build with bodhibuilder crash near end-installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1632184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632184] Re: image build with bodhibuilder crash near end-installation
Part of my add_info function as it appears on my computer:
def add_info(report, ui):
add_installation_log(report, 'UbiquitySyslog', 'syslog')
syslog = report['UbiquitySyslog']
if 'Buffer I/O error on device' in syslog:
if re.search('Attached .* CD-ROM (\w+)', syslog):
cd_drive = re.search('Attached .* CD-ROM (\w+)', syslog).group(1)
cd_error = re.search('Buffer I/O error on device %s' % cd_drive,
syslog)
else:
cd_error = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632184
Title:
image build with bodhibuilder crash near end-installation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1632184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632184] Re: image build with bodhibuilder crash near end-installation
Similar but not identical bug #1495055 in 15.10 resulting in:
ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 60, in
add_info
syslog = report['UbiquitySyslog'].decode('UTF-8')
AttributeError: 'str' object has no attribute 'decode'
while this bug in 16.04 results in:
if 'Buffer I/O error on device' in syslog:
TypeError: a bytes-like object is required, not 'str'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632184
Title:
image build with bodhibuilder crash near end-installation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1632184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632184] Re: image build with bodhibuilder crash near end-installation
Very similar report reported on VLC 4 years ago: https://trac.videolan.org/vlc/ticket/7651 ** Bug watch added: VLC Trac #7651 http://trac.videolan.org/vlc/ticket/7651 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632184 Title: image build with bodhibuilder crash near end-installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1632184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632184] [NEW] image build with bodhibuilder crash near end-installation
Public bug reported: I think I got this error most of the time trying to install LXLE 16.04, on many old computers. But pretty first time I get apport running fine, and I am on my own computer having time to debug and investigate rather than just use LXLE 12.04.5 like we usually do. This is when I would expect the installer say it has finished. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 [modified: usr/lib/ubiquity/user-setup/user-setup-apply usr/share/ubiquity/apt-setup] ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CasperVersion: 1.376 Date: Mon Oct 10 22:58:50 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. LiveMediaBuild: LXLE 16.04 - Release i386 ProcEnviron: LANGUAGE=fr_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632184 Title: image build with bodhibuilder crash near end-installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1632184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873239] Re: Linux Mint live DVD installer crashes on Dell Inspiron 6000
I now guess slideshow is/was using debconf at installation time to request information. I guess this is ubiquity that use webkit for ... I don t know (don t think it is the progress bar... maybe for debconf finally). So probably any package using debconf trigger the problem. Not sure if it is webkit... could try the trick of installing webkit_debug and try to get a backtrace... I am not too used to that but I think the mentioned bug was explaining how to do. Middle of night here... I need to sleep now! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873239 Title: Linux Mint live DVD installer crashes on Dell Inspiron 6000 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/873239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873239] Re: Linux Mint live DVD installer crashes on Dell Inspiron 6000
Well, I think I made this bug much more complex than it is. My stacktrace shows no problem with webkit... other bug I mention was having. Here, the problem is only that the flush need to be inside try catch, because the write stream have been receive at class initialisation. We don't control it, it may well have been close, so we cannot assume that we can flush it... that's all... I think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873239 Title: Linux Mint live DVD installer crashes on Dell Inspiron 6000 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/873239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873239] Re: Linux Mint live DVD installer crashes on Dell Inspiron 6000
I just have this too with Linux Mint 17.1 Cinnamon DVD.
My crash:
/***
Jan 28 06:33:13 mint ubiquity:
Jan 28 06:33:14 mint /plugininstall.py: Exception during installation:
Jan 28 06:33:14 mint /plugininstall.py: Traceback (most recent call last):
Jan 28 06:33:14 mint /plugininstall.py: File
/usr/lib/ubiquity/ubiquity/install_misc.py, line 287, in pulse
Jan 28 06:33:14 mint /plugininstall.py: self.db.progress('SET',
int(self.percent))
Jan 28 06:33:14 mint /plugininstall.py: File
/usr/lib/python3/dist-packages/debconf.py, line 62, in lambda
Jan 28 06:33:14 mint /plugininstall.py: lambda *args, **kw:
self.command(command, *args, **kw))
Jan 28 06:33:14 mint /plugininstall.py: File
/usr/lib/python3/dist-packages/debconf.py, line 67, in command
Jan 28 06:33:14 mint /plugininstall.py: self.write.flush()
Jan 28 06:33:14 mint /plugininstall.py: BrokenPipeError: [Errno 32] Broken pipe
Jan 28 06:33:14 mint /plugininstall.py:
Jan 28 06:36:21 mint dbus[934]: [system] Activating service
/
This seems to (have been) a known bug affecting AMD Athlon XP 2600+ to 2800+
Mine is a 2700+
As can be seen on Bug #710582 :
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/710582
People was saying that removing slideshow package (on XUbuntu or Kubuntu) prior
to installing was fixing problem.
Not tried it.
Seems they did (supposedly) resolved it in webkit (I can only suppose slideshow
use webkit).
Now, because of my graphics card I am in fallback mode... and I am not sure it
did not trigger the bug:
in install_misc.py in pulse function near:
try:
if os.environ['UBIQUITY_FRONTEND'] != 'debconf_ui':
self.db.progress('SET', int(self.percent))
except debconf.DebconfError:
return False
I have seen also, still not resolved bug:
I consider bug #1309340 linked
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1309340
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873239
Title:
Linux Mint live DVD installer crashes on Dell Inspiron 6000
To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/873239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873239] Re: Linux Mint live DVD installer crashes on Dell Inspiron 6000
** Attachment added: Paul's /var/log/installer/debug https://bugs.launchpad.net/linuxmint/+bug/873239/+attachment/4307056/+files/debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873239 Title: Linux Mint live DVD installer crashes on Dell Inspiron 6000 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/873239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576953] Re: Can not mark 'ubuntu-desktop' for upgrade
I note the following repeated many times in main.log: 2010-05-07 13:43:27,890 WARNING updateStatus: dlFailed on 'http://security.ubuntu.com/ubuntu/dists/karmic-security/main/i18n/Translation-en_US.bz2' I note the following in apt.log: Package python-gtksourceview2 has broken Depends on python2.5-gtk2 Considering python-gtk2 138 as a solution to python-gtksourceview2 3 Removing python-gtksourceview2 rather than change python2.5-gtk2 ... many other packages broken dependencies... Investigating gedit Package gedit has broken Depends on python-gtksourceview2 Considering python-gtksourceview2 3 as a solution to gedit 4 Added python-gtksourceview2 to the remove list Fixing gedit via keep of python-gtksourceview2 Investigating python-gtksourceview2 Package python-gtksourceview2 has broken Depends on python2.5-gtk2 Considering python-gtk2 138 as a solution to python-gtksourceview2 4 Removing python-gtksourceview2 rather than change python2.5-gtk2 Try to Re-Instate gnome-games Investigating gedit Package gedit has broken Depends on python-gtksourceview2 Considering python-gtksourceview2 138 as a solution to gedit 4 Removing gedit rather than change python-gtksourceview2 Investigating ubuntu-desktop Package ubuntu-desktop has broken Depends on gedit Considering gedit 138 as a solution to ubuntu-desktop 0 Removing ubuntu-desktop rather than change gedit ... Investigating ubuntu-desktop Package ubuntu-desktop has broken Depends on gedit Considering gedit 1 as a solution to ubuntu-desktop 1 Considering gedit 1 as a solution to ubuntu-desktop 1 Done Log time: 2010-05-07 13:46:59.474142 ... Well, I am just a bug triager with almost zero experience with these messages. That looks strange to me that such dependancies happens on released version. -- Can not mark 'ubuntu-desktop' for upgrade https://bugs.launchpad.net/bugs/576953 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576953] Re: Can not mark 'ubuntu-desktop' for upgrade
Do you have xubuntu-desktop installed on this machine? There is a known bug, bug #57143 that make it problematic to update ubuntu-desktop if xubuntu-desktop is there. I doubt this is your problem... but it seems worth to ask. ** Changed in: update-manager (Ubuntu) Status: New = Incomplete -- Can not mark 'ubuntu-desktop' for upgrade https://bugs.launchpad.net/bugs/576953 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576920] Re: The package 'xubuntu-desktop' is marked for removal but it is in the removal blacklist karmic2lucid
** Summary changed: - can't upgrade to lucid + The package 'xubuntu-desktop' is marked for removal but it is in the removal blacklist karmic2lucid -- The package 'xubuntu-desktop' is marked for removal but it is in the removal blacklist karmic2lucid https://bugs.launchpad.net/bugs/576920 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576953] Re: Can not mark 'ubuntu-desktop' for upgrade
Sorry, I meant bug #571743 -- Can not mark 'ubuntu-desktop' for upgrade https://bugs.launchpad.net/bugs/576953 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576920] Re: The package 'xubuntu-desktop' is marked for removal but it is in the removal blacklist karmic2lucid
http://www.edmondscommerce.co.uk/ubuntu/ubuntu-10-04-upgrade-package-ubuntu-desktop-is-marked-for-removal-but-is-in-the-removal-blacklist-solution/ seems to suggest that: apt-get remove xubuntu-desktop then rebooting, then update the problem could work around the problem. Some similarity, without being the same as bug #571743 -- The package 'xubuntu-desktop' is marked for removal but it is in the removal blacklist karmic2lucid https://bugs.launchpad.net/bugs/576920 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576920] Re: The package 'xubuntu-desktop' is marked for removal but it is in the removal blacklist karmic2lucid
Hi, thank you for reporting this bug. Looking at the information given: DistroRelease: Ubuntu 9.10 ... Package: update-manager 1:0.111.10 I come to the conclusion that you probably did not update the system before upgrading, since current version of update-manager in karmic (9.10) repository is 0.126.5 and with karmic-update repository 0.126.9 according to: http://packages.ubuntu.com/karmic-updates/update-manager This suggest that your update-manager is more at jaunty (9.04 with updates enabled). I am unsure what is the correct procedure to apply now that the upgrade have been tried. -- The package 'xubuntu-desktop' is marked for removal but it is in the removal blacklist karmic2lucid https://bugs.launchpad.net/bugs/576920 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306401] Re: Brother MFC8840D errors on 1st print job
Marking as Fix Released, since the original poster claim the problem does not happens anymore in 10.04. ** Changed in: cups (Ubuntu) Status: Confirmed = Fix Released -- Brother MFC8840D errors on 1st print job https://bugs.launchpad.net/bugs/306401 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 351115] Re: Firefox 3.0.8 address does not change when changing tab
Marking my own bug as Invalid, becoming very old, was cleared by removing cache files, and never rehappened. ** Changed in: firefox-3.0 (Ubuntu) Status: New = Invalid -- Firefox 3.0.8 address does not change when changing tab https://bugs.launchpad.net/bugs/351115 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 503577] Re: g-p-m brightness not applied anymore after rebooting
** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete = Confirmed -- g-p-m brightness not applied anymore after rebooting https://bugs.launchpad.net/bugs/503577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 503577] Re: g-p-m brightness not applied anymore after rebooting
The real issue here is that when pressing the brightness keys, the brightness value in gconf is not updated I think you are oversimplifying this bug. Well you do have much more experience than me but for me, there seems to be 3 sub-bugs in this bug: 1) Normal drivers are unable to update the brightness of the LCD, that seems to explain why step two of the workaround does not work until step one is done. Also bug description suggest that there is no way to change brightness even with mouse in gnome-power-manager, until the acpi_backlight=vendor is passed to the kernel. 2) Brightness keys are not recognized with normal drivers (I suspect scancodes could be different with vendor drivers than normal ones, but this is just my hypothesis). Still, it need vendor drivers to work, as explain in initial description. But it is also possible that vendor drivers do direct brightness adjustments directly, that would explain why gconf never see the changes. 3) Gnome-power-manager settings (set by mouse) is not saved, but is temporarily value. According to documentation, that would be normal, but documentation seems to fail to explain how to set a saved 'normal' value for the brightness. I don't know. Searching 'brightness' for bugs result in lots of bugs, that seems to confirm that this is not only happenning on Dell mini 10. (Well, I did about one month ago, but I expect things have not changed much since). -- g-p-m brightness not applied anymore after rebooting https://bugs.launchpad.net/bugs/503577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 503577] Re: g-p-m brightness not applied anymore after rebooting
I am trying to summarise some info take from other bugs here.
In bug #230421, we learn that the following changed in the acpi-support package
in Ubuntu 9.10:
* Drop events/video_brightness{down,up}, video_brightness{up,down}.sh: at
least some platforms that use these ACPI sequences are seeing them
correctly translated to input events, so those users will see duplicate
events unless we drop them. LP: #178860.
Mike, can you please run the 'acpi_listen' command, and report here any
output produced when you press the brightness keys?
This bug also suggest to look at the
https://wiki.ubuntu.com/Hotkeys/Troubleshooting page.
Bug #385723 seems the general missing backlight control for Linux
kernel.
Bug #320874, is very interesting, and was fixed in kernel 2.6.29:
http://bugzilla.kernel.org/show_bug.cgi?id=12249 (reading fast, could be BIOS
related).
Bug #388216 (because KMS)
What I call sub-bug 3, (brightness not saved) is in bug #35223, and they did
fill a bug directly to gnome project:
https://bugzilla.gnome.org/show_bug.cgi?id=335673
Bug #131650, brightness keys not working on Vaio SZ-140p.
Sony Vaio have LOTS of bug reports...
Bug #223954 (brightness controls still has major bugs) (mostly about going back
to 100% when opening lid), asked to do:
Thanks for your report but we need more information about your bug. Please, run
gnome-power-bugreport.sh and gconftool -a /apps/gnome-power-manager/backlight.
Bug #406515, for Lenovo, but showing how to determine keycodes, also
link to Lnux kernel bugs.
Ok, I'll stop there for now, just to show that there is many kernel
issues going on around this.
** Bug watch added: Linux Kernel Bug Tracker #12249
http://bugzilla.kernel.org/show_bug.cgi?id=12249
** Bug watch added: GNOME Bug Tracker #335673
https://bugzilla.gnome.org/show_bug.cgi?id=335673
--
g-p-m brightness not applied anymore after rebooting
https://bugs.launchpad.net/bugs/503577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501323] Re: HP DV5 - Can't suspend, get a Lock Screen instad of suspend
you did the 'sudo update-grub'? Then rebooted? I would probably try with 'acpi=strict' if I were you. Did you, or do you intend to update the BIOS? -- HP DV5 - Can't suspend, get a Lock Screen instad of suspend https://bugs.launchpad.net/bugs/501323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501323] Re: HP DV5 - Can't suspend, get a Lock Screen instad of suspend
Just for testing 'acpi=strict' it is easier to just type 'e' after booting in Grub, then edit the line with 'e', then do Ctrl-X to boot with the temporarily modified version. -- HP DV5 - Can't suspend, get a Lock Screen instad of suspend https://bugs.launchpad.net/bugs/501323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 406515] Re: [Karmic] Brightness fn keys lost functionality (multiple laptops)
From bug #503577, on a Dell mini 10, 'apci_backlight=vendor' kernel parameter seems to make it work. acpi_backlight=[HW,ACPI] acpi_backlight=vendor acpi_backlight=video If set to vendor, prefer vendor specific driver (e.g. thinkpad_acpi, sony_acpi, etc.) instead of the ACPI video.ko driver. -- [Karmic] Brightness fn keys lost functionality (multiple laptops) https://bugs.launchpad.net/bugs/406515 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490152] Re: screen doesn't dim when switching to battery
*** This bug is a duplicate of bug 384304 *** https://bugs.launchpad.net/bugs/384304 ** Also affects: devicekit-power (Ubuntu) Importance: Undecided Status: New ** Changed in: devicekit-power (Ubuntu) Status: New = Confirmed ** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete = Invalid ** This bug has been marked a duplicate of bug 384304 devicekit-power fails to realize I'm on battery after AC disconnect -- screen doesn't dim when switching to battery https://bugs.launchpad.net/bugs/490152 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501323] Re: HP DV5 - Can't suspend, get a Lock Screen instad of suspend
I see from your BootDmesg.txt file:
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic
root=UUID=1257db60-9fbe-4a1c-aad6-9303cbff6640 ro quiet splash noacpi
The noacpi option here is not the default as far as I know, you did add it?
From http://www.kernel.org/doc/Documentation/kernel-parameters.txt :
acpi= [HW,ACPI,X86]
Advanced Configuration and Power Interface
Format: { force | off | ht | strict | noirq | rsdt }
force -- enable ACPI if default was off
off -- disable ACPI if default was on
noirq -- do not use ACPI for IRQ routing
ht -- run only enough ACPI to enable Hyper Threading
strict -- Be less tolerant of platforms that are not
strictly ACPI specification compliant.
rsdt -- prefer RSDT over (default) XSDT
See also Documentation/power/pm.txt, pci=noacpi
Well, I am not a developer, just a bug triager. But it looks like you
are saying by this noacpi option, not to use Advanced Configuration and
Power Interface (ACPI) which seems likely not to help suspending.
Now that we are using Grub2 rather than plain old grub, I think I am a
bit lost as to where it must be changed. But I guess you can test
different values by pressing 'e' to edit the command in grub menu before
doing Enter.
Also, although it does make sense for me to update BIOS, it can be risky
(especially if current goes out during the procedure)... so you have to
know and accept the risk.
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
HP DV5 - Can't suspend, get a Lock Screen instad of suspend
https://bugs.launchpad.net/bugs/501323
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501323] Re: HP DV5 - Can't suspend, get a Lock Screen instad of suspend
I suggest you first try to use 'e' to edit the command line in Grub menu when you boot first. Then if you want to do permanent change: Oh, reading about Grub2 at: http://doc.ubuntu-fr.org/grub-pc (I speak french too ^^), then I think that the file to be edited is: gksudo gedit /etc/default/grub Then edit the line GRUB_CMDLINE_LINUX_DEFAULT=quiet splash and remove the 'noacpi' if it is there. Then type 'sudo update-grub' in the terminal to update the Grub menu for real. -- HP DV5 - Can't suspend, get a Lock Screen instad of suspend https://bugs.launchpad.net/bugs/501323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501323] Re: HP DV5 - Can't suspend, get a Lock Screen instad of suspend
It could be link to relatively old bug #301353, which suggest (from http://bugzilla.kernel.org/show_bug.cgi?id=12113#c13) that bios update from HP (F21) solves the problem. Can you determinate the BIOS version you have? maybe 'dmidecode' command can help you. A message on HP forum from May 29, 2009: HP: Please fix the dv5 BIOS! http://h30434.www3.hp.com/t5/Hardware/HP-Please-fix-the-dv5-BIOS/m-p/71945 From http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?sw_lang=17lc=endlc=encc=uslang=enproduct=3755994 There seems to be a firmware update for some Hard Disks of this model, which is different than a BIOS update, but maybe usefull. Ah... maybe not, that seems to fix something else: - Fixes an issue where following error message is displayed after powering ON the laptop: 1720 - SMART Hard Drive detects imminent failure (Failing attr: 0¤). ** Bug watch added: Linux Kernel Bug Tracker #12113 http://bugzilla.kernel.org/show_bug.cgi?id=12113 ** Changed in: gnome-power-manager (Ubuntu) Status: New = Incomplete ** Package changed: gnome-power-manager (Ubuntu) = linux (Ubuntu) -- HP DV5 - Can't suspend, get a Lock Screen instad of suspend https://bugs.launchpad.net/bugs/501323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501323] Re: HP DV5 - Can't suspend, get a Lock Screen instad of suspend
BTW, it could be a bit like on my computer... when I hibernate, computer did seems to shut down, but it looks like an event wakes it up less than 1 second after, and then it does resume, and show the lock screen which is normal after a successfull resume as far as I know. Since I have changed the package of this bug to 'linux' kernel, you will need to rerun 'apport-collect 501323' AFTER logging in after a 'failed' suspend-to-disk would give better log files. Note that a web page describing some test you can do is at: https://wiki.ubuntu.com/DebuggingKernelSuspend which suggest also: http://lxr.linux.no/#linux+v2.6.32/Documentation/power/basic-pm-debugging.txt -- HP DV5 - Can't suspend, get a Lock Screen instad of suspend https://bugs.launchpad.net/bugs/501323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500666] Re: Toshiba M505-S4972 The Fan does not work unless i suspend and bring it back up
I note the following from BootDMesg.txt: [0.262168] ACPI: Power Resource [PF0] (on) [0.262211] ACPI: Power Resource [PF1] (on) [0.262252] ACPI: Power Resource [PF2] (on) [0.262293] ACPI: Power Resource [PF3] (on) [0.262334] ACPI: Power Resource [PF4] (on) [0.262377] ACPI: Power Resource [PF5] (on) [0.262482] ACPI Warning: Incorrect checksum in table [OEMB] - D5, should be 92 20090521 tbutils-246 [0.263168] ACPI Warning: Incorrect checksum in table [GSCI] - C0, should be 22 20090521 tbutils-246 ... [0.560317] fan PNP0C0B:00: registered as cooling_device0 [0.560323] ACPI: Fan [FAN0] (on) [0.560456] fan PNP0C0B:01: registered as cooling_device1 [0.560461] ACPI: Fan [FAN1] (on) [0.560591] fan PNP0C0B:02: registered as cooling_device2 [0.560598] ACPI: Fan [FAN2] (on) [0.560726] fan PNP0C0B:03: registered as cooling_device3 [0.560732] ACPI: Fan [FAN3] (on) [0.560860] fan PNP0C0B:04: registered as cooling_device4 [0.560865] ACPI: Fan [FAN4] (on) [0.560995] fan PNP0C0B:05: registered as cooling_device5 [0.561000] ACPI: Fan [FAN5] (on) ** Changed in: linux (Ubuntu) Status: New = Confirmed -- Toshiba M505-S4972 The Fan does not work unless i suspend and bring it back up https://bugs.launchpad.net/bugs/500666 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501500] Re: wrong charge level computed/reported
DevkitPower.txt says that the battery is fully-charged (state): Device: /org/freedesktop/DeviceKit/Power/devices/battery_BAT0 native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C09:00/PNP0C0A:00/power_supply/BAT0 vendor: SANYO model:42T4504 serial: 8098 power supply: yes updated: Thu Jan 14 23:03:29 2010 (12 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: fully-charged energy: 18.57 Wh energy-empty:0 Wh energy-full: 48.98 Wh energy-full-design: 56.16 Wh energy-rate: 0 W voltage: 11.494 V percentage: 37.9134% capacity:87.2151% technology: lithium-ion So I guess this is NOT a gnome-power-manager bug. Not sure which package to move it to however. -- wrong charge level computed/reported https://bugs.launchpad.net/bugs/501500 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 503577] Re: g-p-m brightness not applied anymore after rebooting
** Summary changed: - Gnome power manager ignores screen settings + g-p-m brightness not applied anymore after rebooting -- g-p-m brightness not applied anymore after rebooting https://bugs.launchpad.net/bugs/503577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 503577] Re: g-p-m brightness not applied anymore after rebooting
Could it be: acpi_backlight= [HW,ACPI] acpi_backlight=vendor acpi_backlight=video If set to vendor, prefer vendor specific driver (e.g. thinkpad_acpi, sony_acpi, etc.) instead of the ACPI video.ko driver. rather than acpi_brightness ? which I don't find in: http://www.kernel.org/doc/Documentation/kernel-parameters.txt Also, is it the brightness control you were using from http://library.gnome.org/users/gnome-power-manager/stable/applets- general.html.en ? ** Changed in: gnome-power-manager (Ubuntu) Status: Invalid = Incomplete -- g-p-m brightness not applied anymore after rebooting https://bugs.launchpad.net/bugs/503577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492832] Re: Cannot get laptop panel brightness after upgrade to Jaunty samsung nc10
Reporter of bug #503577, suggest that adding kernel boot options: apci_brightness=vendor although I believe it must be: acpi_backlight=vendor because I don't find acpi_brightness kernel option. As explained in http://ubuntuforums.org/showpost.php?p=8612908postcount=828 But I guess it has to be considered a workaround, FOR A DIFFERENT HARDWARE THAN YOURS, but may be worth to try. -- Cannot get laptop panel brightness after upgrade to Jaunty samsung nc10 https://bugs.launchpad.net/bugs/492832 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490152] Re: screen doesn't dim when switching to battery
I think it could be a duplicate of bug #384304 That would means your bug would happens when your battery if almost full. Also, the output of devkit-power -d would show near the end: on-battery: no when in fact you are on-battery (AC unplug). Could you confirm that? -- screen doesn't dim when switching to battery https://bugs.launchpad.net/bugs/490152 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501500] Re: wrong charge level computed/reported
** Also affects: devicekit-power (Ubuntu) Importance: Undecided Status: New -- wrong charge level computed/reported https://bugs.launchpad.net/bugs/501500 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501500] Re: wrong charge level computed/reported
** Changed in: gnome-power-manager (Ubuntu) Status: New = Confirmed ** Changed in: devicekit-power (Ubuntu) Status: New = Confirmed -- wrong charge level computed/reported https://bugs.launchpad.net/bugs/501500 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501323] Re: HP DV5 - Can't suspend, get a Lock Screen instad of suspend
As I understand the results you got from 'apport-collect 501323' , a new window or tab should have opened in your browser executing this, or you could copy the link to the authorization page; but you did not seems to have given the permission to apport-collect to run on this web page. I suggest you retry 'apport-collect 501323' but take time to authorize apport in the web page, before continuing. Also, https://wiki.ubuntu.com/DebuggingGNOMEPowerManager seems to suggest that you try: dbus-send --system --print-reply --dest=org.freedesktop.Hal /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0 at the $ prompt of Accessoires/Terminal... If it does the same problem that way, that would suggest that this is a kernel bug rather than a gnome-power-manager bug. Maybe I will mark this bug to the kernel too, so that apport-collect also collect information for a kernel bug if that becomes one. -- HP DV5 - Can't suspend, get a Lock Screen instad of suspend https://bugs.launchpad.net/bugs/501323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500666] Re: Toshiba M505-S4972 The Fan does not work unless i suspend and bring it back up
I note from http://ubuntuforums.org/showthread.php?t=1282161: I purchased new Toshiba Satellite M505-S4945 laptop and installed 64-bit Jaunty. Everything works great except that the fan cannot be turned on due to broken ACPI tables from Phoenix BIOS. The fan makes a big difference (40C vs 70+C). I found an omnibook module from sourceforge that is supposed to fix some issues with Satellite laptops, but I was unsuccessful compiling it, probably because the types of supported laptops do not include Satellite M505. I am not a developer nor a programmer, so I cannot fix the source code of omnibook module myself to add my specific model nor can I find it from terminal. They seems to get to the conclusion that: $ cat /proc/acpi/thermal_zone/*/trip_points critical (S5): 108 C passive: 101 C: tc1=30 tc2=30 tsp=50 devices=CPU0 CPU1 active[0]: 94 C: devices=FAN0 active[1]: 82 C: devices=FAN1 active[2]: 72 C: devices=FAN2 active[3]: 52 C: devices=FAN3 active[4]: 42 C: devices=FAN4 is wrong. What is the result of: cat /proc/acpi/thermal_zone/*/trip_points for you in a terminal window? I believe this is more a kernel bug. So I'll update the package. ** Package changed: gnome-power-manager (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New = Incomplete -- Toshiba M505-S4972 The Fan does not work unless i suspend and bring it back up https://bugs.launchpad.net/bugs/500666 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500666] Re: Toshiba M505-S4972 The Fan does not work unless i suspend and bring it back up
As I have changed the package of this bug to the kernel (from gnome-power-manager), please type: apport-collect -p linux 500666 to attach newly needed information to this bug. -- Toshiba M505-S4972 The Fan does not work unless i suspend and bring it back up https://bugs.launchpad.net/bugs/500666 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504811] Re: display server is broken
As I read the link you have given ( http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and- blanking-removal-of-bodges/ ), then going to: https://bugs.launchpad.net/bugs/413168 I would suspect that this bug was fixed in: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/413168/comments/23 xorg-server (2:1.6.3-1ubuntu7) karmic; urgency=low * Add 187_lastdeviceeventtime-no-reset.patch: Avoids resetting IDLETIME on DPMS events. Cherrypick from upstream. (LP: #397839) Can you give the output of: apt-cache policy xserver-xorg-core in a terminal window? ** Changed in: gnome-power-manager (Ubuntu) Status: New = Incomplete ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New = Incomplete -- display server is broken https://bugs.launchpad.net/bugs/504811 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 503577] Re: Gnome power manager ignores screen settings
Well, in http://ubuntuforums.org/showpost.php?p=8612908postcount=828 suggest that: adding nolapic allows to use dell smbios for changing backlight (brightness) in grub. Although I have not used gnome-power-manager brightness feature, I believe it is not a bug. If I read: http://library.gnome.org/users/gnome-power-manager/stable/applets-general.html.en I understand this is a temporary brightness level. So, I'll mark this bug as invalid. Please feel free to reopen if you think I misunderstood. ** Changed in: gnome-power-manager (Ubuntu) Status: New = Invalid -- Gnome power manager ignores screen settings https://bugs.launchpad.net/bugs/503577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
