[Bug 881164] Re: massive syslog entries (GHES: Failed ...) after upgrade to oneiric
This is still a problem on 32bit, is this patch going to be included in the next kernel update?, if so when?. For now, I disabled GHES using ghes.disable=1 to the kernel boot options. Though, I see a log message ghes: Unknown parameter 'disable', the spewing of messages are gone!. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881164 Title: massive syslog entries (GHES: Failed ...) after upgrade to oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/881164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881164] Re: massive syslog entries (GHES: Failed ...) after upgrade to oneiric
Mine is 32bit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881164 Title: massive syslog entries (GHES: Failed ...) after upgrade to oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/881164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881164] Re: massive syslog entries (GHES: Failed ...) after upgrade to oneiric
Here is mine as well. ** Attachment added: output of acpidump acpi.dump 21 https://bugs.launchpad.net/ubuntu/+bug/881164/+attachment/2597700/+files/acpi.dump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881164 Title: massive syslog entries (GHES: Failed ...) after upgrade to oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/881164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881164] Re: massive syslog entries (GHES: Failed ...) after upgrade to oneiric
This is affecting several (possibly all) PowerEdge models, can this issue be assigned to someone to take a look?. I'd be glad to provide any further details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881164 Title: massive syslog entries (GHES: Failed ...) after upgrade to oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/881164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881164] Re: massive syslog entries (GHES: Failed ...) after upgrade to oneiric
Additional details of the system components from lspci, lshw, and lsusb. ** Attachment added: output of lspci,lsusb lshw https://bugs.launchpad.net/ubuntu/+bug/881164/+attachment/2571644/+files/lsusb-lspci-lshw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881164 Title: massive syslog entries (GHES: Failed ...) after upgrade to oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/881164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881164] [NEW] massive syslog entries (GHES: Failed ...) after upgrade to oneiric
Public bug reported: After the upgrade of my natty (server version) to oneiric, my syslog is flooded with massive amount (6 or 7 of these messages below per second) of the messages shown below. I had to filter out this message in my rsyslog configuration to err level to avoid this flooding. Oct 24 08:26:11 gorilla kernel: [67636.418784] [Firmware Warn]: GHES: Failed to read error status block address for hardware error source: 49376. Oct 24 08:26:11 gorilla kernel: [67636.418790] [Firmware Warn]: GHES: Failed to read error status block address for hardware error source: 49377. Oct 24 08:26:11 gorilla kernel: [67636.418794] [Firmware Warn]: GHES: Failed to read error status block address for hardware error source: 49378. Machine/Model: Dell PowerEdge T110 root@gorilla:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=11.10 DISTRIB_CODENAME=oneiric DISTRIB_DESCRIPTION=Ubuntu 11.10 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881164 Title: massive syslog entries (GHES: Failed ...) after upgrade to oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/881164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)
Like many here, I had the same problem when upgrading natty server to oneiric server. The conversion/migration of /var/run to /run during the upgrade process is buggy causing all sorts of problems until the content of /var/run and /var/lock are moved to /run and symlinks are created shown below as per comment #18. ls -l /var/run /var/lock lrwxrwxrwx 1 root root 9 2011-10-23 12:24 /var/lock - /run/lock/ lrwxrwxrwx 1 root root 4 2011-10-23 12:23 /var/run - /run/ PS: The strange thing is, I upgraded my desktop version last week from natty-oneiric, the upgrade went just fine with the migration done properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858122 Title: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252145] Re: ipw2100 - timesout/failure on DHCP request on boot
Update: I figured out the reason... the wpa_supplicant is not ready/up at the time udev tries to activate the network on boot. The simple solution is to disabled the udev ACTION=add rule in /etc/udv/rules.d/85-ifupdown.rules and let the network manager activate the interface instead which works just fine. -- ipw2100 - timesout/failure on DHCP request on boot https://bugs.launchpad.net/bugs/252145 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 182473] Re: rtl8187 drops connection
Wayne, Are you using WPA?, if so I'd change the algorithm/proto to AES+TKIP. The driver does not work after some amount of time (usually an hour or so... may be certain amount of data transfer). Thanks -Arul -- rtl8187 drops connection https://bugs.launchpad.net/bugs/182473 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 252145] [NEW] ipw2100 - timesout/failure on DHCP request on boot
Public bug reported: Since turning on WPA on my router, my ipw2100 based network interface, appears to be failing OR timing out on DHCP request. I had to manually restart networking to get it to work after boot. I have never had this issue before I switched to WPA on my home network. Anyone noticed the issue or have any solution?. Here are details. Version: Ubuntu 2.6.24-19.36-generic, Ubuntu 8.04.1 ifconfig after boot: -- eth1 Link encap:Ethernet HWaddr xxx UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:5 Base address:0xa000 Memory:fafee000-fafeefff eth1:avahi Link encap:Ethernet HWaddr x inet addr:169.254.9.24 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 Interrupt:5 Base address:0xa000 Memory:fafee000-fafeefff Restart networking: -- [EMAIL PROTECTED]:~$ sudo /etc/init.d/networking restart * Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth1.pid with pid 5478 killed old client process, removed PID file ... snip bound to 192.168.1.102 -- renewal in 930400594 seconds. ifconfig after network restart: -- eth1 Link encap:Ethernet HWaddr inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:41 errors:1 dropped:1 overruns:0 frame:0 TX packets:39 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5721 (5.5 KB) TX bytes:3571 (3.4 KB) Interrupt:5 Memory:fafee000-fafeefff ** Affects: ipw2100 (Ubuntu) Importance: Undecided Status: New -- ipw2100 - timesout/failure on DHCP request on boot https://bugs.launchpad.net/bugs/252145 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 182473] Re: rtl8187 drops connection
I had the same problem on Hardy with rtl8187 driver i.e. works just fine for a while after reboot and eventually drops connection after series of CTS protection disabled/enabled pair messages. I finally figured out that the *AES only* option I selected was the problem. The driver can't handle AES but seem to work just fine on TKIP, so I changed my APs mode to WPA with AES+TKIP and the driver started to work continually. It still spewes some CTS messages every now and then but continues to work without having to do ifdown/rmmod/insmod/ifup which was a pain! Thanks -Arul -- rtl8187 drops connection https://bugs.launchpad.net/bugs/182473 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 145696] Re: firefox and xgl cause 100% CPU
Qilz, If xgl is hogging CPU, then you don't have OpenGL direct rendering turned on or your driver does not support it. Try the following and see if you have direct rendering on. [EMAIL PROTECTED]:~$ glxinfo |grep direct direct rendering: Yes If it is No and you believe your driver supports it, then enable it on xorg.conf Section Module Loadglx EndSection --- I have a similar issue where firefox hangs using up max CPU, mostly it happens when you right click to open a link on a new window consistently. Has anyone experienced this on fresh install of gusty with latest firefox?. PID USER PR NI VIRTRESSHR S %CPU %MEMTIME+ COMMAND 5679 home 25 0 249m 91m25m R 97.4 9.12:53.94 firefox-bin -Arul -- firefox and xgl cause 100% CPU https://bugs.launchpad.net/bugs/145696 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 158301] Re: Firefox CPU over use freeze
I have a similar issue where firefox hangs using up max CPU, mostly it happens when you right click to open a link on a new window at random time. Has anyone experienced this on fresh install of gusty with latest firefox?. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5679 home 25 0 249m 91m 25m R 97.4 9.1 2:53.94 firefox-bin -Arul -- Firefox CPU over use freeze https://bugs.launchpad.net/bugs/158301 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
