[Bug 1728388] Re: Infinite loop on boot when loading ACPI
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728388 Title: Infinite loop on boot when loading ACPI To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1728388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728388] Re: Infinite loop on boot when loading ACPI
The issue is still present on a 5.15 kernel. On a HP Pavilion 17-0e50sf (Hybrid Graphics: Intel_i915/AMD_radeon ), the system hangs for about 40 seconds after the user login (tested with gdm, lightdm / GNOME, Weston, xfce / Xorg, Wayland). dmesg output: ACPI Error: Aborting method \AMD3._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20210730/psparse-529) acpi device:02: Failed to change power state to D0 [drm] PCIE gen 3 link speeds already enabled [drm] PCIE GART of 2048M enabled (table at 0x0004). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 radeon :01:00.0: fence driver on ring 1 use gpu addr 0x4c04 radeon :01:00.0: fence driver on ring 2 use gpu addr 0x4c08 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c radeon :01:00.0: fence driver on ring 4 use gpu addr 0x4c10 debugfs: File 'radeon_ring_gfx' in directory '1' already present! debugfs: File 'radeon_ring_cp1' in directory '1' already present! debugfs: File 'radeon_ring_cp2' in directory '1' already present! debugfs: File 'radeon_ring_dma1' in directory '1' already present! debugfs: File 'radeon_ring_dma2' in directory '1' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 1 succeeded in 1 usecs [drm] ring test on 2 succeeded in 1 usecs [drm] ring test on 3 succeeded in 3 usecs [drm] ring test on 4 succeeded in 3 usecs [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 1 succeeded in 0 usecs [drm] ib test on ring 2 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs [drm] ib test on ring 4 succeeded in 0 usecs Tried with both radeon and amdgpu kernel modules: same issue. Also tried to call ACPI method \AMD3._ON with acpi_call module: it returns an error after 30 seconds. Blacklisting the radeon and amdgpu modules allows me to work around the problem ** Tags added: regression-release ** Tags added: kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728388 Title: Infinite loop on boot when loading ACPI To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1728388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728388] Re: Infinite loop on boot when loading ACPI
** Also affects: ubuntu Importance: Undecided Status: New ** Also affects: debian Importance: Undecided Status: New ** Also affects: archlinux 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/1728388 Title: Infinite loop on boot when loading ACPI To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1728388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931301] Re: NIC unavailable after suspend to RAM
I have the exact same issue with the "alx" module and Network Manager. But it seems that reloading this module with the "wake on lan" option enabled resolves the problem (sudo modprobe alx enable_wol = on). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1620037] Re: Sync gnustep-gui 0.25.0-4 (universe) from Debian unstable (main)
Le 04/09/2016 à 21:07, Jeremy Bicha a écrit : > Eric, does this require a rebuild of all the GNUstep packages? > > ** Bug watch added: Debian Bug tracker #835894 >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835894 > > ** Also affects: gnustep-gui (Debian) via >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835894 >Importance: Unknown >Status: Unknown > #835894 is a severe bug in gnustep-gui 0.25.0, and it affects all gnustep apps built with lignustep-gui-dev 0.25.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620037 Title: Sync gnustep-gui 0.25.0-4 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnustep-gui/+bug/1620037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1620037] Re: Sync gnustep-gui 0.25.0-4 (universe) from Debian unstable (main)
Le 04/09/2016 à 21:07, Jeremy Bicha a écrit : > Eric, does this require a rebuild of all the GNUstep packages? Yes, it does > > ** Bug watch added: Debian Bug tracker #835894 >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835894 > > ** Also affects: gnustep-gui (Debian) via >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835894 >Importance: Unknown >Status: Unknown > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620037 Title: Sync gnustep-gui 0.25.0-4 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnustep-gui/+bug/1620037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620037] [NEW] Sync gnustep-gui 0.25.0-4 (universe) from Debian unstable (main)
Public bug reported: Please sync gnustep-gui 0.25.0-4 (universe) from Debian unstable (main) Changelog entries since current yakkety version 0.25.0-3: gnustep-gui (0.25.0-4) unstable; urgency=medium * Delete debian/libgnustep-gui0.25.symbols file (Closes: #835894). * Override lintian warning about symbols control file. -- Eric Heintzmann <heintzmann.e...@free.fr> Fri, 02 Sep 2016 19:42:42 +0200 ** Affects: gnustep-gui (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/1620037 Title: Sync gnustep-gui 0.25.0-4 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnustep-gui/+bug/1620037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90376] Re: Firefox doesn't know how to communicate with the server
I can confirm this bug Since latest security update in Dapper, I cannot anymore browse to any https sites ! I reinstalled firefox, firefox-gnome-support, libnspr4, libnss3 ( firefox 1.5.dfsg+1.5.0.10-0ubuntu0.6.06.2 source), it solved partially the problem. Now some https sites are browsable, but some not. See also: http://ubuntuforums.org/showthread.php?p=2239540 -- Firefox doesn't know how to communicate with the server https://launchpad.net/bugs/90376 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90376] Re: Firefox doesn't know how to communicate with the server
Are we all using proxy servers or is that another red herring ? In my case, I don't use any proxy (only direct connection). -- Firefox doesn't know how to communicate with the server https://launchpad.net/bugs/90376 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
