[Bug 1908559] Re: Steam or discord: "pushModal: invocation of begin_modal failed"
It seems like disabling these plugins have made these particular log entries go away for me. Thank you for your assistance Daniel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908559] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444716/+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/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908559] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444719/+files/monitors.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908559] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444715/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908559] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444717/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908559] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444718/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908559] Re: Steam or discord: "pushModal: invocation of begin_modal failed"
apport information ** Tags added: apport-collected groovy third-party-packages ** Description changed: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.3 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2018-12-30 (718 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + Package: gnome-shell 3.38.1-1ubuntu1.1 + PackageArchitecture: amd64 + RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 + Tags: third-party-packages groovy + Uname: Linux 5.9.12-050912-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-12-12 (5 days ago) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1908559/+attachment/5444714/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908559] [NEW] Steam or discord: "pushModal: invocation of begin_modal failed"
Public bug reported: Roughly every 10 minutes two entries of the heading is printed to the logs ``` $ journalctl -b | grep "pushModal: invocation of begin_modal failed" des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed ``` I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission ``` ps -ef | grep 8626 centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam ``` ** Affects: steam (Ubuntu) Importance: Undecided Status: New ** Package changed: mutter (Ubuntu) => ubuntu ** Description changed: - TBD + Roughly every 10 minutes two entries of the heading is printed to the logs + ``` + $ journalctl -b | grep "pushModal: invocation of begin_modal failed" + des. 17 19:38:53 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 19:45:15 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 19:45:18 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 19:54:00 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 19:54:02 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 20:03:34 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + des. 17 20:03:37 vega gnome-shell[8626]: pushModal: invocation of begin_modal failed + ``` + + I'm suspecting this is caused by either the discord snap, or steam missing some kind of permission + ``` + ps -ef | grep 8626 + centx 86268293 3 19:18 ?00:01:38 /usr/bin/gnome-shell + centx 86928626 0 19:18 ?00:00:00 ibus-daemon --panel disable --xim + centx 184538626 0 19:39 ?00:00:13 /snap/discord/119/usr/share/discord/Discord --no-sandbox + centx 192378626 0 19:41 ?00:00:00 /bin/sh -e /usr/games/steam + ``` ** Package changed: ubuntu => steam (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908559 Title: Steam or discord: "pushModal: invocation of begin_modal failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1908559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881423] Re: error channel closing too late to send/recv
I still have this (or a very similar issue) after having upgraded to 20.04 ``` gnome-shell[4128]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881423 Title: error channel closing too late to send/recv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1881423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852079] [NEW] Desktop freezes - requiring restart
Public bug reported: Desktop froze while doing light web-browsing listening to music (spotify) and running some containers in docker (with low load). The following error in logs indicating that the freeze is related to the nvidia drivers (best effort guess from my side) Probably relevant sys-log entry (fetched using journalctl -b -1) 5337 Nov 11 13:57:50 octarine kernel: NVRM: GPU at PCI::41:00: GPU-ad30cb16-3a1a-2a6a-04a9-2b79e1e6b86c 5338 Nov 11 13:57:50 octarine kernel: NVRM: GPU Board Serial Number: 5339 Nov 11 13:57:50 octarine kernel: NVRM: Xid (PCI::41:00): 79, pid=1996, GPU has fallen off the bus. 5340 Nov 11 13:57:50 octarine kernel: NVRM: GPU :41:00.0: GPU has fallen off the bus. 5341 Nov 11 13:57:50 octarine kernel: NVRM: GPU :41:00.0: GPU is on Board . 5342 Nov 11 13:57:50 octarine kernel: NVRM: A GPU crash dump has been created. If possible, please run 5343 NVRM: nvidia-bug-report.sh as root to collect this data before 5344 NVRM: the NVIDIA kernel module is unloaded. lsb_release -rd: Description:Ubuntu 19.10 Release:19.10 Expected to happen: Normal working order What happened instead: Both displays froze, showing a static image with input not affecting visuals. Music continued to play I used REISUB to reboot, this worked fine. I have the full journalctl output that I can provide (either in scrubbed form, or original form if provided privately) if that is useful. sudo lshw -C display: *-display description: VGA compatible controller product: TU117 [GeForce GTX 1650] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:41:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:134 memory:ab00-abff memory:9000-9fff memory:a000-a1ff ioport:8000(size=128) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 14:11:14 2019 InstallationDate: Installed on 2019-11-07 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan nvidia ** Description changed: Desktop froze while doing light web-browsing listening to music (spotify) and running some containers in docker (with low load). The following error in logs indicating that the freeze is related to the nvidia drivers (best effort guess from my side) Probably relevant sys-log entry (fetched using journalctl -b -1) - 5337 Nov 11 13:57:50 octarine kernel: NVRM: GPU at PCI::41:00: GPU-ad30cb16-3a1a-2a6a-04a9-2b79e1e6b86c - 5338 Nov 11 13:57:50 octarine kernel: NVRM: GPU Board Serial Number: 5339 Nov 11 13:57:50 octarine kernel: NVRM: Xid (PCI::41:00): 79, pid=1996, GPU has fallen off the bus. - 5340 Nov 11 13:57:50 octarine kernel: NVRM: GPU :41:00.0: GPU has fallen off the bus. - 5341 Nov 11 13:57:50 octarine kernel: NVRM: GPU :41:00.0: GPU is on Board . - 5342 Nov 11 13:57:50 octarine kernel: NVRM: A GPU crash dump has been created. If possible, please run 5343 NVRM: nvidia-bug-report.sh as root to collect this data before
[Bug 1851807] [NEW] xdg-desktop-portal-gtk spams logs
Public bug reported: Every minute I get a log entry that looks like > xdg-desktop-por[ ]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error: org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Upstream bug-report: https://github.com/flatpak/xdg-desktop-portal- gtk/issues/222 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xdg-desktop-portal-gtk 1.4.0-2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 10:51:30 2019 InstallationDate: Installed on 2019-11-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: xdg-desktop-portal-gtk UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851807 Title: xdg-desktop-portal-gtk spams logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1851807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] Re: Mouse clicks ignored in Wayland
I also got this issue on 17.10 after installing linux kernel 4.15.1 (amd64, lot-latency) from Ubuntu kernel-ppa[1] and Vesa components from Padoka PPA[2] to get better support for my Vega 56 GPU [1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/ [2]: https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280571] Re: NetworkManager does not auto-connect to VPNs marked Connect Automatically
Just wanted to share the application vpnautoconnect as apo mentioned above. http://sourceforge.net/projects/vpnautoconnect/ Maybe someone could incorporate the ideas from here into NM's autoconnect or something. I've had this problem for years, and now it seems, that with this rather clunky program, it finally works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/280571 Title: NetworkManager does not auto-connect to VPNs marked Connect Automatically -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681617] [NEW] pptp stops receiving packets when bandwidth spike
Public bug reported: Binary package hint: pptp-linux I've had this problem since long ago, when downloading at high speed (ubuntu images from my uni's network and similar) my network connection would become unresponsive, and I had to reconnect. This hit me real hard today, as it kept happening while I was browsing a single youtube clip. My dorm uses PPTP to connect to the net, and we have a fairly juicy line (~100mbps). I've researched a bit, and tried to adjust the MISSING_WINDOW in pqueue.h to 6000 from 300 (per [1] and [2]), and I think this fixed my problem. I guess this could've been fixed upstream already, but still would be nice to have this backported if possible. If nothing else, this bug- report might help someone else with the same problem. [1]http://blog.gmane.org/gmane.comp.misc.pptpclient.devel/month=20100801 [2]https://bugzilla.novell.com/show_bug.cgi?id=628537 someone else with the same problem: http://ubuntuforums.org/showthread.php?p=10163284#post10163284 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: pptp-linux 1.7.2-4 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Thu Nov 25 23:42:53 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: pptp-linux ** Affects: pptp-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- pptp stops receiving packets when bandwidth spike https://bugs.launchpad.net/bugs/681617 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 681617] Re: pptp stops receiving packets when bandwidth spike
-- pptp stops receiving packets when bandwidth spike https://bugs.launchpad.net/bugs/681617 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 423999] Re: [RV790] [ati] black X screen on startup with karmic hd4890
I can confirm that this bug is no longer present for me on my hardware configuration as of Lucid Lynx beta at least -- [RV790] [ati] black X screen on startup with karmic hd4890 https://bugs.launchpad.net/bugs/423999 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 409950] Re: black screen on live-cd startup
As I no longer has access to the 3850, I can't tell if this bug still is relevant or not. -- black screen on live-cd startup https://bugs.launchpad.net/bugs/409950 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 382140] Re: karmic: high-pitched noise from snd-hda-intel
** Bug watch added: Red Hat Bugzilla #523340 https://bugzilla.redhat.com/show_bug.cgi?id=523340 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=523340 Importance: Unknown Status: Unknown -- karmic: high-pitched noise from snd-hda-intel https://bugs.launchpad.net/bugs/382140 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 423999] Re: [ati] black X screen on startup with karmic hd4890
Tested the pre-release of fedora 12 (https://fedoraproject.org/wiki/Test_Day:2009-09-09_Radeon#Results), and this specific bug seems to be fixed there. (they might be running a newer kernel though). I'll see if I can get the rest of the bugs resolved too, AFAIK they will be pushed upstream, and come to ubuntu sooner or later. ** Also affects: xserver-xorg-video-ati (Fedora) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-ati (Fedora) Status: New = Fix Released -- [ati] black X screen on startup with karmic hd4890 https://bugs.launchpad.net/bugs/423999 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 423999] [NEW] [ati] black X screen on startup with karmic hd4890
Public bug reported: Binary package hint: xserver-xorg-video-ati I just tried booting karmic desktop alpha live on my new computer, and got a black X with a waiting cursor when GDM was supposed to load, after the xsplash. steps to reproduce: 1. boot the cd 2. choose english language and local keymap (norwegian) 3. choose safe graphics or normal boot -usplash pops up, does some waiting -xsplash pops up (looks nice so far, at this point I can change to vt's with alt+fx) -some screen flickering -black screen with a waiting cursor on, cursor animating -freeze, at this point the computer doesn't respond to any input from mouse/keyboard, alt+fx doesn't change vt, and ctrl+alt+bsp doesn't kill x (nozap anyway I guess...) the following output is from my current 9.04(running fglrx and 2.6.30), I'll do it with 9.10 if I can, but seeing as I don't really have access to a computer to do remote debugging atm. (no xorg.log.0, since this is a different X running). lspci -nn |grep -i vga: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9460] ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: ati gdm lockup x-freeze x.org -- [ati] black X screen on startup with karmic hd4890 https://bugs.launchpad.net/bugs/423999 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 423999] Re: [ati] black X screen on startup with karmic hd4890
** Attachment added: full lspci -vvnn http://launchpadlibrarian.net/31289826/lspci.txt -- [ati] black X screen on startup with karmic hd4890 https://bugs.launchpad.net/bugs/423999 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 178659] Re: e2fsck freezes whole system
Seems to be fixed by the new kernel update, and it does not seem to be a problem with the ubuntu HH alpha 4 either. ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- e2fsck freezes whole system https://bugs.launchpad.net/bugs/178659 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178659] Re: e2fsck freezes whole system
NP =) I tried installing it on with the live-cd first, but this failed to work. I think maybe lvm is dependent on some kernel-module, I don't know. As it comes to mind, I could have tried to load the module (if any) manually, but I didn't try that. I will try again at first opportunity, but that will probably not be before next week or so. -- e2fsck freezes whole system https://bugs.launchpad.net/bugs/178659 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178659] Re: e2fsck freezes whole system
I tried making an updated hardy heron livecd with remastersys inside a virtualbox virtual computer, this proved, upon booting from the media, to be unsuccessful as the media didn't boot correctly. Any tips to how to get this checked would be appreciated. -- e2fsck freezes whole system https://bugs.launchpad.net/bugs/178659 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178659] Re: e2fsck freezes whole system
Tried the hardy heron alpha 3 livecd, but to no avail. The live-cd doesn't have the required lvm2 packages for setting up the lvm- partitions I need to scan for testing. Any ideas? Is it possible to make a custom cd with lvm on? or does f.ex the alternate cd contain lvm? if so, is this a live-cd? -- e2fsck freezes whole system https://bugs.launchpad.net/bugs/178659 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178659] Re: e2fsck freezes whole system
I'll try with a live-cd as soon as possible, should I report my findings in this task, or in a new? -- e2fsck freezes whole system https://bugs.launchpad.net/bugs/178659 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178659] Re: e2fsck freezes whole machine
OK, I was just assuming it was e2fsck since I can use disk normally (I think). Is this a known bug? And is there a need for more data?(and what?) or has this issue been fixed in a newer version? ** Summary changed: - e2fsck freezes whole machine + e2fsck freezes whole system -- e2fsck freezes whole system https://bugs.launchpad.net/bugs/178659 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178659] e2fsck freezes whole machine
Public bug reported: Binary package hint: e2fsprogs During bootup this happens: 1. message about /dev/StoragePool/Storage has been mounted so and so many times, needs to be checked 2. e2fsck (I assume) starts checking the disk (a lvm virtual disk that is, its roughly 1.3 TB big) 3. after some time it starts spewing out errors mentioning ATA4.00 4. and then it just freezes Now, I've tried running e2fsck on the virtual drive manually, by using a livecd to remove the relevant line in fstab, and booting ubuntu from hdd again (standard livecd dosn't have lvm2), but this results in the same or similar error, mentioning ATA4.00, and freeze. It could be worth mentioning that just mounting the virtual drive works, though I suspect from hdparm -tT output that one of the disks has gone bad (actually, now it doesn't give abnormal output), but still, for e2fsck to freeze the machine can't be right. Now I also have a theory about it being a NCQ error or something (https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/147858) I don't know how to find what device ATA4 is, so I could give a hdparm -i ouput of that device(disk) if someone knows how to trace it. grep -i ata4 /var/log/messages.0 |tail -n 40: [CODE]Dec 24 23:40:04 Xeon kernel: [ 1400.944115] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:40:04 Xeon kernel: [ 1400.984500] ata4.00: configured for UDMA/33 Dec 24 23:40:04 Xeon kernel: [ 1400.984515] ata4: EH complete Dec 24 23:40:05 Xeon kernel: [ 1401.463153] ata4: soft resetting port Dec 24 23:40:05 Xeon kernel: [ 1401.618824] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:40:05 Xeon kernel: [ 1401.655219] ata4.00: configured for UDMA/33 Dec 24 23:40:05 Xeon kernel: [ 1401.655228] ata4: EH complete Dec 24 23:40:08 Xeon kernel: [ 1405.403661] ata4: soft resetting port Dec 24 23:40:09 Xeon kernel: [ 1405.559385] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:40:09 Xeon kernel: [ 1405.595778] ata4.00: configured for UDMA/33 Dec 24 23:40:09 Xeon kernel: [ 1405.595791] ata4: EH complete Dec 24 23:40:10 Xeon kernel: [ 1406.765090] ata4: soft resetting port Dec 24 23:40:10 Xeon kernel: [ 1406.920815] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:40:10 Xeon kernel: [ 1406.961217] ata4.00: configured for UDMA/33 Dec 24 23:40:10 Xeon kernel: [ 1406.961226] ata4: EH complete Dec 24 23:49:17 Xeon kernel: [ 49.318107] ata4: SATA max UDMA/133 cmd 0xf88382 80 ctl 0xf88382b8 bmdma 0x irq 19 Dec 24 23:49:17 Xeon kernel: [ 50.295688] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:49:17 Xeon kernel: [ 50.333900] ata4.00: ATA-7: WDC WD3200KS-00PFB0, 21.00M21, max UDMA/133 Dec 24 23:49:17 Xeon kernel: [ 50.333982] ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/1) Dec 24 23:49:17 Xeon kernel: [ 50.340095] ata4.00: configured for UDMA/133 Dec 25 02:49:09 Xeon kernel: [ 48.120041] ata4: SATA max UDMA/133 cmd 0xf88142 80 ctl 0xf88142b8 bmdma 0x irq 17 Dec 25 02:49:09 Xeon kernel: [ 49.089943] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 25 02:49:09 Xeon kernel: [ 49.122674] ata4.00: ATA-7: WDC WD3200KS-00PFB0, 21.00M21, max UDMA/133 Dec 25 02:49:09 Xeon kernel: [ 49.122679] ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/1) Dec 25 02:49:09 Xeon kernel: [ 49.130331] ata4.00: configured for UDMA/133 Dec 25 14:27:27 Xeon kernel: [ 48.466519] ata4: SATA max UDMA/133 cmd 0xf88142 80 ctl 0xf88142b8 bmdma 0x irq 16 Dec 25 14:27:27 Xeon kernel: [ 49.436401] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 25 14:27:27 Xeon kernel: [ 49.460547] ata4.00: ATA-7: WDC WD3200KS-00PFB0, 21.00M21, max UDMA/133 Dec 25 14:27:27 Xeon kernel: [ 49.460552] ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/1) Dec 25 14:27:27 Xeon kernel: [ 49.468812] ata4.00: configured for UDMA/133 Dec 25 19:20:42 Xeon kernel: [ 53.037964] ata4: SATA max UDMA/133 cmd 0xf88363 80 ctl 0xf88363b8 bmdma 0x irq 19 Dec 25 19:20:42 Xeon kernel: [ 55.025896] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 25 19:20:42 Xeon kernel: [ 55.063110] ata4.00: ATA-7: WDC WD3200KS-00PFB0, 21.00M21, max UDMA/133 Dec 25 19:20:42 Xeon kernel: [ 55.063114] ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/1) Dec 25 19:20:42 Xeon kernel: [ 55.070294] ata4.00: configured for UDMA/133 Dec 26 00:47:50 Xeon kernel: [ 48.479339] ata4: SATA max UDMA/133 cmd 0xf88383 80 ctl 0xf88383b8 bmdma 0x irq 18 Dec 26 00:47:50 Xeon kernel: [ 50.451175] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 26 00:47:50 Xeon kernel: [ 50.485966] ata4.00: ATA-7: WDC WD3200KS-00PFB0, 21.00M21, max UDMA/133 Dec 26 00:47:50 Xeon kernel: [ 50.485970] ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/1) Dec 26 00:47:50 Xeon kernel: [ 50.491568] ata4.00: configured for UDMA/133 [/CODE] ** Affects: e2fsprogs (Ubuntu)
[Bug 178659] Re: e2fsck freezes whole machine
** Description changed: Binary package hint: e2fsprogs During bootup this happens: 1. message about /dev/StoragePool/Storage has been mounted so and so many times, needs to be checked 2. e2fsck (I assume) starts checking the disk (a lvm virtual disk that is, its roughly 1.3 TB big) 3. after some time it starts spewing out errors mentioning ATA4.00 4. and then it just freezes - Now, I've tried running e2fsck on the virtual drive manually, by using a - livecd to remove the relevant line in fstab, and booting ubuntu from hdd - again (standard livecd dosn't have lvm2), but this results in the same - or similar error, mentioning ATA4.00, and freeze. It could be worth - mentioning that just mounting the virtual drive works, though I suspect - from hdparm -tT output that one of the disks has gone bad (actually, now - it doesn't give abnormal output), but still, for e2fsck to freeze the - machine can't be right. Now I also have a theory about it being a NCQ - error or something (https://bugs.launchpad.net/ubuntu/+source/linux- - source-2.6.22/+bug/147858) + uname -a: Linux xeon 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux + Now, I've tried running e2fsck on the virtual drive manually, by using a livecd to remove the relevant line in fstab, and booting ubuntu from hdd again (standard livecd dosn't have lvm2), but this results in the same or similar error, mentioning ATA4.00, and freeze. It could be worth mentioning that just mounting the virtual drive works, though I suspect from hdparm -tT output that one of the disks has gone bad (actually, now it doesn't give abnormal output), but still, for e2fsck to freeze the machine can't be right. Now I also have a theory about it being a NCQ error or something (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/147858) I don't know how to find what device ATA4 is, so I could give a hdparm -i ouput of that device(disk) if someone knows how to trace it. grep -i ata4 /var/log/messages.0 |tail -n 40: [CODE]Dec 24 23:40:04 Xeon kernel: [ 1400.944115] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:40:04 Xeon kernel: [ 1400.984500] ata4.00: configured for UDMA/33 Dec 24 23:40:04 Xeon kernel: [ 1400.984515] ata4: EH complete Dec 24 23:40:05 Xeon kernel: [ 1401.463153] ata4: soft resetting port Dec 24 23:40:05 Xeon kernel: [ 1401.618824] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:40:05 Xeon kernel: [ 1401.655219] ata4.00: configured for UDMA/33 Dec 24 23:40:05 Xeon kernel: [ 1401.655228] ata4: EH complete Dec 24 23:40:08 Xeon kernel: [ 1405.403661] ata4: soft resetting port Dec 24 23:40:09 Xeon kernel: [ 1405.559385] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:40:09 Xeon kernel: [ 1405.595778] ata4.00: configured for UDMA/33 Dec 24 23:40:09 Xeon kernel: [ 1405.595791] ata4: EH complete Dec 24 23:40:10 Xeon kernel: [ 1406.765090] ata4: soft resetting port Dec 24 23:40:10 Xeon kernel: [ 1406.920815] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:40:10 Xeon kernel: [ 1406.961217] ata4.00: configured for UDMA/33 Dec 24 23:40:10 Xeon kernel: [ 1406.961226] ata4: EH complete Dec 24 23:49:17 Xeon kernel: [ 49.318107] ata4: SATA max UDMA/133 cmd 0xf88382 80 ctl 0xf88382b8 bmdma 0x irq 19 Dec 24 23:49:17 Xeon kernel: [ 50.295688] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 24 23:49:17 Xeon kernel: [ 50.333900] ata4.00: ATA-7: WDC WD3200KS-00PFB0, 21.00M21, max UDMA/133 Dec 24 23:49:17 Xeon kernel: [ 50.333982] ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/1) Dec 24 23:49:17 Xeon kernel: [ 50.340095] ata4.00: configured for UDMA/133 Dec 25 02:49:09 Xeon kernel: [ 48.120041] ata4: SATA max UDMA/133 cmd 0xf88142 80 ctl 0xf88142b8 bmdma 0x irq 17 Dec 25 02:49:09 Xeon kernel: [ 49.089943] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 25 02:49:09 Xeon kernel: [ 49.122674] ata4.00: ATA-7: WDC WD3200KS-00PFB0, 21.00M21, max UDMA/133 Dec 25 02:49:09 Xeon kernel: [ 49.122679] ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/1) Dec 25 02:49:09 Xeon kernel: [ 49.130331] ata4.00: configured for UDMA/133 Dec 25 14:27:27 Xeon kernel: [ 48.466519] ata4: SATA max UDMA/133 cmd 0xf88142 80 ctl 0xf88142b8 bmdma 0x irq 16 Dec 25 14:27:27 Xeon kernel: [ 49.436401] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Dec 25 14:27:27 Xeon kernel: [ 49.460547] ata4.00: ATA-7: WDC WD3200KS-00PFB0, 21.00M21, max UDMA/133 Dec 25 14:27:27 Xeon kernel: [ 49.460552] ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/1) Dec 25 14:27:27 Xeon kernel: [ 49.468812] ata4.00: configured for UDMA/133 Dec 25 19:20:42 Xeon kernel: [ 53.037964] ata4: SATA max UDMA/133 cmd 0xf88363 80 ctl 0xf88363b8 bmdma 0x irq 19 Dec 25 19:20:42
[Bug 140967] Re: package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Think I have the same bug, not using a Dell keyboard, but a Logitech one. [CODE] [SNIPPED] . ldconfig deferred processing now taking place Setting up hotkey-setup (0.1-17ubuntu19) ... KDSETKEYCODE: Invalid argument failed to set scancode 6f to keycode 113 KDSETKEYCODE: Invalid argument failed to set scancode 6d to keycode 115 KDSETKEYCODE: Invalid argument failed to set scancode 6e to keycode 114 invoke-rc.d: initscript hotkey-setup, action start failed. dpkg: error processing hotkey-setup (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of ubuntu-desktop: ubuntu-desktop depends on hotkey-setup; however: Package hotkey-setup is not configured yet. dpkg: error processing ubuntu-desktop (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: hotkey-setup ubuntu-desktop E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up hotkey-setup (0.1-17ubuntu19) ... KDSETKEYCODE: Invalid argument failed to set scancode 6f to keycode 113 KDSETKEYCODE: Invalid argument failed to set scancode 6d to keycode 115 KDSETKEYCODE: Invalid argument failed to set scancode 6e to keycode 114 invoke-rc.d: initscript hotkey-setup, action start failed. dpkg: error processing hotkey-setup (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of ubuntu-desktop: ubuntu-desktop depends on hotkey-setup; however: Package hotkey-setup is not configured yet. dpkg: error processing ubuntu-desktop (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: hotkey-setup ubuntu-desktop Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Writing extended state information... Done Building tag database... Done [/CODE] -- package hotkey-setup 0.1-17ubuntu19 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/140967 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78709] Re: PS/2 keyboard and mouse plugs doesnt work with SMP
** Summary changed: - System freeze at startup + PS/2 keyboard and mouse plugs doesnt work with SMP ** Description changed: - With a stock Ubuntu 6.10 bootCD, or SMPenabled 6.06 kernel, my system freezes at startup + The system seemed to freeze, but it really was problems with the PS/2 + ports, seems like ubuntu with SMP doesnt recognice my PS/2 plugged + devices at startup. + + Original messsage: + With a stock Ubuntu 6.10 bootCD, or SMPenabled 6.06 kernel, my system freezes at startup with no errors or any sign of faults. Except of course from the fact that i can in no way - interact with the computer. It doesnt react to the mouse nor the keyboard at all. + interact with the computer. It doesnt react to the mouse nor the keyboard at all. + info here - uname -a : Linux xeon 2.6.15-27-386 #1 PREEMPT Fri Dec 8 17:51:56 UTC 2006 i686 GNU/Linux dmesg : [17179569.184000] Linux version 2.6.15-27-386 ([EMAIL PROTECTED]) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Fri Dec 8 17:51:56 UTC 2006 [17179569.184000] BIOS-provided physical RAM map: [17179569.184000] BIOS-e820: - 0009f800 (usable) [17179569.184000] BIOS-e820: 0009f800 - 000a (reserved) [17179569.184000] BIOS-e820: 000f - 0010 (reserved) [17179569.184000] BIOS-e820: 0010 - 5fee (usable) [17179569.184000] BIOS-e820: 5fee - 5fee3000 (ACPI NVS) [17179569.184000] BIOS-e820: 5fee3000 - 5fef (ACPI data) [17179569.184000] BIOS-e820: 5fef - 5ff0 (reserved) [17179569.184000] BIOS-e820: fec0 - 0001 (reserved) [17179569.184000] 638MB HIGHMEM available. [17179569.184000] 896MB LOWMEM available. [17179569.184000] found SMP MP-table at 000f5bd0 [17179569.184000] On node 0 totalpages: 392928 [17179569.184000] DMA zone: 4096 pages, LIFO batch:0 [17179569.184000] DMA32 zone: 0 pages, LIFO batch:0 [17179569.184000] Normal zone: 225280 pages, LIFO batch:31 [17179569.184000] HighMem zone: 163552 pages, LIFO batch:31 [17179569.184000] DMI 2.3 present. [17179569.184000] ACPI: RSDP (v000 IntelR) @ 0x000f7c60 [17179569.184000] ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x) @ 0x5fee3040 [17179569.184000] ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x) @ 0x5fee30c0 [17179569.184000] ACPI: MADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x) @ 0x5fee71c0 [17179569.184000] ACPI: DSDT (v001 INTELR AWRDACPI 0x1000 MSFT 0x010e) @ 0x [17179569.184000] ACPI: PM-Timer IO Port: 0x408 [17179569.184000] ACPI: Local APIC address 0xfee0 [17179569.184000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [17179569.184000] Processor #0 15:3 APIC version 20 [17179569.184000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled) [17179569.184000] Processor #6 15:3 APIC version 20 [17179569.184000] WARNING: NR_CPUS limit of 1 reached. Processor ignored. [17179569.184000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [17179569.184000] Processor #1 15:3 APIC version 20 [17179569.184000] WARNING: NR_CPUS limit of 1 reached. Processor ignored. [17179569.184000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled) [17179569.184000] Processor #7 15:3 APIC version 20 [17179569.184000] WARNING: NR_CPUS limit of 1 reached. Processor ignored. [17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [17179569.184000] ACPI: IOAPIC (id[0x04] address[0xfec0] gsi_base[0]) [17179569.184000] IOAPIC[0]: apic_id 4, version 32, address 0xfec0, GSI 0-23 [17179569.184000] ACPI: IOAPIC (id[0x05] address[0xfec1] gsi_base[24]) [17179569.184000] IOAPIC[1]: apic_id 5, version 32, address 0xfec1, GSI 24-47 [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [17179569.184000] ACPI: IRQ0 used by override. [17179569.184000] ACPI: IRQ2 used by override. [17179569.184000] ACPI: IRQ9 used by override. [17179569.184000] Enabling APIC mode: Flat. Using 2 I/O APICs [17179569.184000] Using ACPI (MADT) for SMP configuration information [17179569.184000] Allocating PCI resources starting at 6000 (gap: 5ff0:9ed0) [17179569.184000] Built 1 zonelists [17179569.184000] Kernel command line: root=/dev/sdd2 ro quiet splash [17179569.184000] mapped APIC to d000 (fee0) [17179569.184000] mapped IOAPIC to c000 (fec0) [17179569.184000] mapped IOAPIC to b000 (fec1) [17179569.184000] Initializing CPU#0 [17179569.184000] PID hash table
[Bug 78709] System freeze at startup
Public bug reported: With a stock Ubuntu 6.10 bootCD, or SMPenabled 6.06 kernel, my system freezes at startup with no errors or any sign of faults. Except of course from the fact that i can in no way interact with the computer. It doesnt react to the mouse nor the keyboard at all. info here - uname -a : Linux xeon 2.6.15-27-386 #1 PREEMPT Fri Dec 8 17:51:56 UTC 2006 i686 GNU/Linux dmesg : [17179569.184000] Linux version 2.6.15-27-386 ([EMAIL PROTECTED]) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Fri Dec 8 17:51:56 UTC 2006 [17179569.184000] BIOS-provided physical RAM map: [17179569.184000] BIOS-e820: - 0009f800 (usable) [17179569.184000] BIOS-e820: 0009f800 - 000a (reserved) [17179569.184000] BIOS-e820: 000f - 0010 (reserved) [17179569.184000] BIOS-e820: 0010 - 5fee (usable) [17179569.184000] BIOS-e820: 5fee - 5fee3000 (ACPI NVS) [17179569.184000] BIOS-e820: 5fee3000 - 5fef (ACPI data) [17179569.184000] BIOS-e820: 5fef - 5ff0 (reserved) [17179569.184000] BIOS-e820: fec0 - 0001 (reserved) [17179569.184000] 638MB HIGHMEM available. [17179569.184000] 896MB LOWMEM available. [17179569.184000] found SMP MP-table at 000f5bd0 [17179569.184000] On node 0 totalpages: 392928 [17179569.184000] DMA zone: 4096 pages, LIFO batch:0 [17179569.184000] DMA32 zone: 0 pages, LIFO batch:0 [17179569.184000] Normal zone: 225280 pages, LIFO batch:31 [17179569.184000] HighMem zone: 163552 pages, LIFO batch:31 [17179569.184000] DMI 2.3 present. [17179569.184000] ACPI: RSDP (v000 IntelR) @ 0x000f7c60 [17179569.184000] ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x) @ 0x5fee3040 [17179569.184000] ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x) @ 0x5fee30c0 [17179569.184000] ACPI: MADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x) @ 0x5fee71c0 [17179569.184000] ACPI: DSDT (v001 INTELR AWRDACPI 0x1000 MSFT 0x010e) @ 0x [17179569.184000] ACPI: PM-Timer IO Port: 0x408 [17179569.184000] ACPI: Local APIC address 0xfee0 [17179569.184000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [17179569.184000] Processor #0 15:3 APIC version 20 [17179569.184000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled) [17179569.184000] Processor #6 15:3 APIC version 20 [17179569.184000] WARNING: NR_CPUS limit of 1 reached. Processor ignored. [17179569.184000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [17179569.184000] Processor #1 15:3 APIC version 20 [17179569.184000] WARNING: NR_CPUS limit of 1 reached. Processor ignored. [17179569.184000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled) [17179569.184000] Processor #7 15:3 APIC version 20 [17179569.184000] WARNING: NR_CPUS limit of 1 reached. Processor ignored. [17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [17179569.184000] ACPI: IOAPIC (id[0x04] address[0xfec0] gsi_base[0]) [17179569.184000] IOAPIC[0]: apic_id 4, version 32, address 0xfec0, GSI 0-23 [17179569.184000] ACPI: IOAPIC (id[0x05] address[0xfec1] gsi_base[24]) [17179569.184000] IOAPIC[1]: apic_id 5, version 32, address 0xfec1, GSI 24-47 [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [17179569.184000] ACPI: IRQ0 used by override. [17179569.184000] ACPI: IRQ2 used by override. [17179569.184000] ACPI: IRQ9 used by override. [17179569.184000] Enabling APIC mode: Flat. Using 2 I/O APICs [17179569.184000] Using ACPI (MADT) for SMP configuration information [17179569.184000] Allocating PCI resources starting at 6000 (gap: 5ff0:9ed0) [17179569.184000] Built 1 zonelists [17179569.184000] Kernel command line: root=/dev/sdd2 ro quiet splash [17179569.184000] mapped APIC to d000 (fee0) [17179569.184000] mapped IOAPIC to c000 (fec0) [17179569.184000] mapped IOAPIC to b000 (fec1) [17179569.184000] Initializing CPU#0 [17179569.184000] PID hash table entries: 4096 (order: 12, 65536 bytes) [17179569.184000] Detected 2800.573 MHz processor. [17179569.184000] Using pmtmr for high-res timesource [17179569.184000] Console: colour VGA+ 80x25 [17179570.208000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [17179570.208000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [17179570.268000] Memory: 1547356k/1571712k available (1976k kernel code, 23028k reserved, 606k data, 288k init, 654208k highmem) [17179570.268000] Checking if this processor honours the WP bit even in supervisor mode... Ok. [17179570.348000] Calibrating
