[Bug 560804] Re: mouse pointer disappears when screen is turned off and on
may be a duplicate of 552058 which is on i915 chipset -- mouse pointer disappears when screen is turned off and on https://bugs.launchpad.net/bugs/560804 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 552058] Re: [915GM] Mouse cursor disappears when laptop lid closed
Confirming on my IBM Thinkpad X41 running 10.4 also seen reported on bug 560804 which is similar or same behavior on Intel Corporation 82852/855GM Integrated Graphics Device -- [915GM] Mouse cursor disappears when laptop lid closed https://bugs.launchpad.net/bugs/552058 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check https://bugs.launchpad.net/bugs/274995 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 306567] [NEW] package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal script returned error exit status 123
Public bug reported: Binary package hint: snort package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre- removal script returned error exit status 123 This report was initiated by the crash-reporting process. I am adding the following information manually. Used Synaptic Package Manager to install snort and, after dependencies, 5 packages were selected. After install, I ran snort a couple of times (it didn't seem to start, gave me the message you've got to tell me to do something (both without sudo and with, and I don't know what I'm doing so my command line arguments were probably incomplete). After looking over the options, I decided it probably wasn't what I was looking for and I selected the 5 packages for removal (not Complete Removal). Today's dpkg.log 2008-12-09 07:28:22 startup archives unpack 2008-12-09 07:28:35 install libprelude2 none 0.9.17.2-1ubuntu1 2008-12-09 07:28:35 status half-installed libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:35 status triggers-pending man-db 2.5.2-2 2008-12-09 07:28:36 status half-installed libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:36 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:36 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:36 install snort-common-libraries none 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:36 install snort-rules-default none 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:36 install snort-common none 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort-common 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort-common 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-common 2.7.0-19ubuntu1 2008-12-09 07:28:36 status unpacked snort-common 2.7.0-19ubuntu1 2008-12-09 07:28:36 install snort none 2.7.0-19ubuntu1 2008-12-09 07:28:36 status half-installed snort 2.7.0-19ubuntu1 2008-12-09 07:28:37 status half-installed snort 2.7.0-19ubuntu1 2008-12-09 07:28:37 status unpacked snort 2.7.0-19ubuntu1 2008-12-09 07:28:37 status unpacked snort 2.7.0-19ubuntu1 2008-12-09 07:28:37 install oinkmaster none 2.0-2 2008-12-09 07:28:37 status half-installed oinkmaster 2.0-2 2008-12-09 07:28:37 status half-installed oinkmaster 2.0-2 2008-12-09 07:28:37 status unpacked oinkmaster 2.0-2 2008-12-09 07:28:37 status unpacked oinkmaster 2.0-2 2008-12-09 07:28:38 trigproc man-db 2.5.2-2 2.5.2-2 2008-12-09 07:28:38 status half-configured man-db 2.5.2-2 2008-12-09 07:28:39 status installed man-db 2.5.2-2 2008-12-09 07:28:40 startup packages configure 2008-12-09 07:28:40 configure libprelude2 0.9.17.2-1ubuntu1 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status unpacked libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status half-configured libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status installed libprelude2 0.9.17.2-1ubuntu1 2008-12-09 07:28:40 status triggers-pending libc6 2.8~20080505-0ubuntu7 2008-12-09 07:28:40 configure snort-common-libraries 2.7.0-19ubuntu1 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:40 status half-configured snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:40 status installed snort-common-libraries 2.7.0-19ubuntu1 2008-12-09 07:28:40 configure snort-rules-default 2.7.0-19ubuntu1 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40 status unpacked snort-rules-default 2.7.0-19ubuntu1 2008-12-09 07:28:40
[Bug 306567] Re: package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal script returned error exit status 123
** Attachment added: Screenshot - Synaptic Package Manager console window following error message http://launchpadlibrarian.net/20323448/Screenshot-Changes%20applied.png ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/20323455/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/20323459/DpkgTerminalLog.txt -- package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal script returned error exit status 123 https://bugs.launchpad.net/bugs/306567 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 306567] Re: package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal script returned error exit status 123
I am attaching a second Screenshot - Synaptic Package Manager console window following error message which is the scrolled-down view. I also notice that there seems to be some DpkgTerminalLog.txt info from a previous session, but today's information also appears toward the bottom of that log. SEVERITY/PRIORITY SUGGESTION - Unless further investigations see deeper impacts than are apparent to me, I suggest that this is not a critical- priority bug as the exception appears to be detected, and when coupled with Synaptic Package Manager, it is logically handled following rather intuitive steps (simply try again). However, it is also not Low as the error messages are neither user-friendly (Error 123) and appear scary (big-red Stop indicator, Crash Detector appears in Gnome). HTH good luck! ** Attachment added: Screenshot - Synaptic Package Manager console window following error message -- scrolled down http://launchpadlibrarian.net/20323674/synaptic-console2.png -- package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-removal script returned error exit status 123 https://bugs.launchpad.net/bugs/306567 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 301430] Re: ipv6 /etc/hosts missing localhost hostname
Proposed change for ubiquity/scripts/install.py -- I am not on the dev team so someone needs to review/sponsor this change. This would solve the issue for future new installs. This does not solve the issue for the currently installed base. === modified file 'scripts/install.py' --- scripts/install.py 2008-10-30 17:34:58 + +++ scripts/install.py 2008-12-09 16:58:04 + @@ -1522,7 +1522,7 @@ print hosts, textwrap.dedent(\ # The following lines are desirable for IPv6 capable hosts -::1 ip6-localhost ip6-loopback +::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes -- ipv6 /etc/hosts missing localhost hostname https://bugs.launchpad.net/bugs/301430 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301430] Re: ipv6 /etc/hosts missing localhost hostname
question answered, several examples provided ** Changed in: netcfg (Ubuntu) Status: Incomplete = Confirmed -- ipv6 /etc/hosts missing localhost hostname https://bugs.launchpad.net/bugs/301430 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301430] Re: ipv6 /etc/hosts missing localhost hostname
I think this bug lives in ubuntu-installer/ubiquity/ currently line 1525 /scripts/install.py (revision 2954) 1515hosts = open(os.path.join(self.target, 'etc/hosts'), 'w') 1516997 print hosts, 127.0.0.1\tlocalhost 15171772if domain: 1518print hosts, 127.0.1.1\t%s.%s\t%s % (hostname, domain, 1519 hostname) 1520else: 1521print hosts, 127.0.1.1\t%s % hostname 1522997 print hosts, textwrap.dedent(\ 1523996 1524997 # The following lines are desirable for IPv6 capable hosts 1525::1 ip6-localhost ip6-loopback 1526fe00::0 ip6-localnet 1527ff00::0 ip6-mcastprefix 1528ff02::1 ip6-allnodes 1529ff02::2 ip6-allrouters 1530ff02::3 ip6-allhosts) 1531996 hosts.close() ** Also affects: ubiquity Importance: Undecided Status: New -- ipv6 /etc/hosts missing localhost hostname https://bugs.launchpad.net/bugs/301430 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
+ ***Important summary for those experiencing this bug*** + Kernel versions where this bug is fixed: + 1) 2.6.27-10 from intrepid-proposed CORRECT + Kernel versions where this bug is NOT fixed (if you are running one of these, please upgrade to known working kernel): + 1) 2.6.27-7 from intrepid + 2) 2.6.27-9 from intrepid-updates and intrepid-security CORRECT + If you are experiencing this bug, please remove the linux-backports- + modules packages too, as they don't contain a fix I have read that here, but I can't vouch for it as I'm not running backports. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
@Jens -- whatever DNS server you are using while connected to VPN probably doesn't quickly return an answer for a query for localhost, while your non-VPN DNS does. alsa-utils 1.0.17-0ubuntu3 should avoid it in all cases. Also, see below. @kungmidas -- when I change my DNS to some bogus address, I see this delay. When I use good DNS servers, the delay is gone. alsa-utils 1.0.17-0ubuntu3 should avoid it in all cases. Also, see below. @all, please see https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/274995/comments/273 -- if you were seeing a delay -- even if it is fixed now, you probably also have or had that separate network configuration bug 301430 that allows DNS queries for localhost -- however generated -- to escape your local machine and network. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check https://bugs.launchpad.net/bugs/274995 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 301430] Re: ipv6 /etc/hosts missing localhost hostname
Hi Steve, I'm glad you identified the right package. It was difficult for me to figure out what actually initially creates /etc/hosts! What was in your /etc/hosts, if not this? Exactly what you posted, except for the localhost entry in the ::1 line. This condition is common across two fresh installs here at home. 127.0.0.1 localhost 127.0.1.1 topol015 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Also, hopefully helpful ... - My installs were from the Live CD Gnome desktop Live User environment (I did not install from the CD without booting up the Gnome session first). - My installs were on a SOHO LAN with an IPv4 router that was also the DNS server and was not responding to IPv6 DNS queries (in case netcfg or some other tool makes choices based on IPv6 reachability) However, - Dovel mentioned in https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/274995/comments/230 that neither his upgraded installation contained the correct /etc/hosts line, nor did his installation direct from CD. (His upgraded installation may have had a different audio configuration or some other factor, it did not experience the delay in 274995.) (If I understand it correctly,) The bug in 274995 (a condition with a delay noticed by a large number of users) involves attempts to reach a user-session Pulseaudio daemon during /etc/init.d/alsa-tools stop. Of course, the daemon had shut down with the end of the user session, but the alsa-tools seemed oblivious to that and still treated them as part of the default audio system. To experience the delay, there had to be no IPv6 localhost in /etc/hosts AND ALSO no timely response to the resulting DNS queries for localhost. This is an indicator that the number of users without localhost for ipv6 in /etc/hosts may be quite high. -- ipv6 /etc/hosts missing localhost hostname https://bugs.launchpad.net/bugs/301430 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
All, If you are or were experiencing this delay, there is a related bug report -- bug 301430 -- concerning the omission of localhost in the ipv6 part of /etc/hosts. While bug 274995 is fixed by the update to alsa- tools, the delay uncovered by bug 274995 was only experienced by those of us who had bug 301430 as well. Bug 301430 is marked as incomplete and will expire unfixed without confirmation that it affects others. I suspect that everyone who noticed a delay during shutdown owing to 274995 also has an IPv6 misconfiguration in the /etc/hosts file, even if they're not using IPv6 and even if the delay is now fixed. Please help out, check, and advise. WHAT YOU SHOULD DO: 1. Even if the latest alsa-tools update fixed your problem, please check your /etc/hosts and verify whether or not it was set up correctly. A CORRECTLY configured file originally had (or has) this line (the whitespace-separated word localhost is included among the hostnames in the ipv6 section of /etc/hosts): ::1 localhost ip6-localhost ip6-loopback An INCORRECTLY configured file had or has this line (the whitespace-separated word localhost is NOT included among the hostnames): ::1 ip6-localhost ip6-loopback 2. If your system was or is INCORRECTLY configured, please visit bug 301430 and indicate so via a comment. The /etc/hosts file is created as part of the network installation and configuration. It would be interesting to know whether your install was an upgrade or fresh install. Look for any other developer questions you might be able to answer or add your other relevant insights or observations. Please consider subscribing to the bug by clicking E-mail me about changes to this bug report) and indicating that the bug affects you (see the links toward the top of the report). Thanks for your help and congrats on getting bug 274995 fixed! Robb Topolski -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check https://bugs.launchpad.net/bugs/274995 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 301430] Re: ipv6 /etc/hosts missing localhost hostname
Laurent, I replied https://bugs.launchpad.net/ubuntu/+source/alsa- utils/+bug/274995/comments/275 on the alsa-utils issue. -- ipv6 /etc/hosts missing localhost hostname https://bugs.launchpad.net/bugs/301430 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
Hi Laurent, That's odd that the 274995 proposed fix doesn't solve the issue. Do you have more than 2 machines? Did you follow the steps mentioned in https://wiki.ubuntu.com/Testing/EnableProposed to upgrade? Did alsa- utils update to 1.0.17-0ubuntu3 (the proposed fix) or are you using alsa-utils 1.0.17-0ubuntu2 (the previous version)? In /etc/init.d/alsa- utils, do you find the following line?: export PULSE_INTERNAL=0 (Adding localhost to the ipv6 line doesn't actually fix the alsa-utils problem, it just masks it. The omission mentioned in bug 301430 along with the bug in 274995 causes enough delay to uncover the alsa-utils issue.) -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check https://bugs.launchpad.net/bugs/274995 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Looks like the -9 security update fixed a number of concerning-looking issues. Is that why our fix wasn't in it? I tried reapplying the patch from comment 52 into the (-9 directories instead of -7) and wound up with a system with no wireless devices. (Fortunately that process left me with .ko~ backup files I could restore. Nice!) Okay, (whew!) 1. so what do I do now to prevent kernel panics from burning up the computer or filling the disk? 2. when can I expect to trust system updates again? Thanks, Robb -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 276990] Re: iwlagn causes kernel panic on 802.11n wifi
They're ba-ack. With a patch at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 and later a 2.6.27-8 kernel update in backports (mentioned later in bug 286285), I was avoiding kernel panics on 802.11n networks. Now with 2.6.27-9, the panics are back. I am able to work around them by turning off the 802.11n capabilities of my router. -- iwlagn causes kernel panic on 802.11n wifi https://bugs.launchpad.net/bugs/276990 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 294160] Re: ALSA hangs on shutdown - Intrepid Ibex on Dell Inspiron 1525
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 @bugmenot, I suggest a new bug report. Bug 274995 is narrowing to an issue commonly seen during shutdown where 2-3 minute delays also sometimes occur. The crackling quality is usually not a symptom. Any fix for 274995 is unlikely to fix the crackling issue. Also, 274995 is a huge mess and introducing one more side issue to it would likely cause more harm than good. You can certainly mention in a new bug report that you also suffered from the effects of 274995, but if you do, I suggest that you also mention that it is a different issue near resolution and the crackling sound is not fixed by it. Thanks! Robb Topolski -- ALSA hangs on shutdown - Intrepid Ibex on Dell Inspiron 1525 https://bugs.launchpad.net/bugs/294160 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 302237] [NEW] undocumented logaudit facility, how to log unknown facilities
Public bug reported: Binary package hint: sysklogd Ubuntu 8.10 sysklogd 1.5-2ubuntu6 From syslog.conf MAN page Quote The facility is one of the following keywords: auth, authpriv, cron, daemon, ftp, kern, lpr, mail, mark, news, security (same as auth), sys‐ log, user, uucp and local0 through local7. endQuote My silly D-Link DIR-655 router puts its syslog on the Log Audit facility 13 (which is 104 in the 32-bit PRI). It took me quite a bit of reverse engineering to figure that out. I'll make the following proposal based on that finding, but it would be even better if someone could find a copy of syslog.h (mentioned in the MAN page) and extract all of the supported facility names. (I did review the source and couldn't find it myself, it's probably in some global header or config file for making inet-tools.) Proposed Change The facility is one of the following keywords: auth, authpriv, cron, daemon, ftp, kern, logaudit, lpr, mail, mark, news, security (same as auth), sys‐ log, user, uucp and local0 through local7. end I also found something else in the meantime, close and related and easy to fix... Quote ... Both parts are case insensitive and can also be specified as decimal numbers corresponding to the definitions in syslog.h. endQuote This is probably incorrect, as I was able to find an old Berkeley syslog.h and it turns out that you have to multiply the decimal number by 8. So logaudit (13) becomes 104 and both logaudit.info and 104.info works correctly in syslog.conf while 13.info does not. Here is my suggestion Quote ... Both parts are case insensitive and can also be specified as decimal numbers corresponding to the numerical code being used in the PRI part of the RFC 3164 message from the logging device. (Note: the facility's numerical code is multiplied by 8 before being used in the PRI part, and syslog.conf requires this too. For example, network news facilities have a facility identifier of 7, therefore news.local and 56.local are equivalent in syslog.conf.) endQuote Thanks Robb Topolski ** Affects: sysklogd (Ubuntu) Importance: Undecided Status: New -- undocumented logaudit facility, how to log unknown facilities https://bugs.launchpad.net/bugs/302237 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Hi Dov, I'm glad you posted. It seems I've made the bug Gods angry -- it won't show itself on my system tonight, and I can't figure out why. I hate when that happens. I tried killing pulseaudio while logged in to an X session, and it still hung while shutting down. Right. Killing pulseaudio while logged in should show the same problem when the gnome user hits reboot or shutdown. The pulseaudio daemon gets killed then the alsa utility tries to contact it. That is the crux of the issue -- should alsa be trying to contact the pulseaudio server after its killed? Or, should something in the sound configuration revert before pulseaudio gets killed so that the alsa tools don't try to contact the pulseaudio server? I don't understand the architecture well enough to know for certain. The freeze (~ 15 seconds each for 7-10 times that amixer is called to zero and mute the mixer in /etc/init.d/alsa-tools stop) occurs as amixer waits for a DNS query to time out. If the pulseaudio server is alive, the DNS query doesn't happen. If the pulseaudio server is unexpectedly gone, then amixer searches localhost for it. Since it's not found on ipv4 and ipv6 doesn't have localhost in /etc/hosts, the query goes to the WAN and things pause for 15 seconds while amixer waits for a reply. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
I'll buy the beer if this is a BIOS bug. Bug 295136 (aschuring) is the most succinct test case I've seen on this. That bug is a duplicate but shows what is going on. It should not be ignored. Key observations: ---Quote--- After dist-upgrading to intrepid, Ubuntu appears to hang when shutting down. I have traced this down to the ALSA shutdown script taking more than a minute (!) to save sound card state. More specifically: [EMAIL PROTECTED]:~$ time amixer -c0 -q set Mic 0% mute real 0m8.061s user 0m0.003s sys 0m0.012s This is reproducable only in single-user mode. When I run the amixer command when logged in into X (I can even run the command from a console, as long as X is running), the same command takes only a few milliseconds as it should. I will attach an strace log from above call. Of interest is the following line: 4.013297 ioctl(5, FIONREAD, [37]) = 0 which occurs twice in the script. It seems to be expecting data from a network socket, but I can't figure out why. ---endQuote--- - commenting out everything in /usr/share/alsa/pulse.conf: amixer responds fast (The description of this file is, PulseAudio alsa plugin configuration file to set the pulseaudio plugin as default output for applications using alsa when pulseaudio is running. However, pulseaudio is not running, wasn't running, so why does Aschuring's commenting out of lines change anything? /usr/share/alsa/pulse.conf calls its config from /usr/share/alsa/pulse-alsa.conf which appears to set pulse as the default sound device. Aschuring's tests at the single-user root prompt create a similar situation to what all these users are reporting where when the user session is ended, X and pulse are no longer running, and the alsa configuration is to use pulse.) - removing dns in /etc/nsswitch.conf or adding localhost to ipv6 ::1 in /etc/hosts amixer responds fast (This addresses the networking delay, but not whether alsa should be looking for pulse at all when the server is not running. Removing dns from nsswitch.conf is not desirable.) It's a shame that bug 295136 isn't the primary bug, because the best information is there. I don't know if launchpad etiquette allows that to happen -- but developers investigating this bug ought to be paying attention. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
@Luke, My quick test -- There was the same hang with your new file as written (without the variable being exported). THERE WAS NO HANG with export PULSE_INTERNAL=0 but there was a hang if the variable was not exported. -- Robb PS: (reproducing tip for developers and experienced users -- do not try this if you don't understand it -- If your nameserver handles queries correctly, then you may not see the delay users are seeing that is caused by the failed DNS query for localhost. Edit /etc/resolv.conf and change your working nameserver line to one with an unoccupied IP before shutting down and rebooting, for example 192.168.0.177, and the DNS query being generated will go to a address that will timeout instead of to your nameserver. I just figured this out tonight and perhaps that is why this bug is so hit and miss -- some users have nameservers that are answering NXDOMAIN (and thus no delay) and some users have nameservers that aren't answering the query.) -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
@Daniel Chen, Hi Daniel, you're over my head a little bit. Can you tell me in easier terms what you'd like me to try and I'll be happy to try it. @Any, What does the PULSE_INTERNAL variable do? Was that a potential fix or just a diagnostic test? -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Please reevaluate -- see comment 226 ** Changed in: pulseaudio (Ubuntu) Status: Invalid = New -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Please reevaluate -- see comment 226 ** Changed in: alsa-utils (Ubuntu) Status: Invalid = New -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
I am going to try and change the invalid status for pulseaudio and alsa-tools. alsa-tools, pulseaudio -- please re-evaluate. The primary issue seems to be that the alsa-tools are trying to find a pulseaudio daemon that is no longer running after the user has chosen to shutdown or reboot. It seems to me that amixer or aplay ought not try to access a pulseaudio process that doesn't exist. (The hang which is avoided by shutting down the network helps illuminate the issue, but it isn't the cause.) -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
@Dove, It's probable that everyone who uses pulseaudio as installed by Intrepid will experience this bug. The question is whether or not they'll experience the long hang that helps us notice it -- and that is determined by the networking configuration. It appears to me that users who once had an IPV4-only system and upgraded will avoid the wait for timeout caused by the bug (the alsa- tools still look for the pulseaudio server, but fails to find it much faster). This is because the upgrade script notices the ipv6 section is missing in /etc/hosts and installs one including the localhost name in the ::1 line. Users who manually add the localhost hostname to the ::1 line in /etc/hosts also avoid this wait. My guess is that users who disable IPV6 after installing will also avoid this wait for timeout. Robb Topolski -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Thanks for agreeing with me, aschuring. :-) However, the change for 126140 certainly won't benefit you so my previous advice of wait and hope no longer makes sense for some. This is a cascade of bugs and behaviors. In bug 295136, FlagMan said, If pulseaudio is the default sound sink and you are NOT logged into X, amixer will search the pulseaudio server but there is none running on the local machine. Therefore, the network will be searched for a pulseaudio server. Most likely there is none on the local network either, and network timeouts are set to high values, so this may take some time and is the symptom we are seeing. MY THEORY (and I'm not too strong on my capture of linux sound, so beware): I think the root cause is in that first sentence -- the user is no longer logged into X, the pulseaudio daemon has been terminated when the user session ended, but pulseaudio is still sought by alsa tools. So amixer, searches fruitlessly for the daemon and it has to wait for a network timeout every time its called, and it is called numerous times in /etc/init.d/alsa-tools as the script zeros and mutes channels. (After the user logs out of gnome, I have also noticed a delay between the time that gdm appears ready for input and /usr/share/sounds/question.wav plays, which is played by gdmplay which is simply a script that calls aplay, another alsa tool trying to do something after pulseaudio has ended.) Finally, gdm.conf has this text, ---Quote--- # Program used to play sounds. Should not require any 'daemon' or anything # like that as it will be run when no one is logged in yet. SoundProgram=/usr/lib/gdmplay ---EndQuote--- This points the finger at alsa-tools OR, and I think this more likely, the ubuntu user-session implementation of pulseaudio, and here's where my lack of knowledge about these ends my usefulness -- I don't know the implications of default sinks and whether the closing gnome session can and ought to switch audio defaults back and forth. It should be noted that pulse's xsmp module is installed to load upon login, and never does. That might have everything to do with this. It is probably not a bug that the alsa tools looks for pulseaudio using network calls. This is not only very common, it works fine when the network isn't searching DNS for the localhost hostname. Even though many workarounds involve killing the network, or nfs, or uninstalling pulseaudio -- these are avoiding the symptom. There might be a bug related to whether alsa tools seeks the network correctly, and how to do that in IPv4/IPv6 LAN has been the topic of much disagreement (see below). SECONDARY ISSUES: It was found that listing localhost to :::1 in the IPv6 section of /etc/hosts avoided the long delay mentioned in this report. Some distributions, including Debian, include (or have included) that entry in /etc/hosts by default while others have not (including Ubuntu, apparently, starting with Hardy (bug 211537). However, and this is important no matter which way this goes, several VERY POPULAR network applications that have bug reports indicating that they fail or misbehave when localhost is listed twice in /etc/hosts (these reports are older and are probably fixed). How to handle localhost in lookups as everyone transitions to IPv6 has been the source of questions http://lists.debian.org/debian-ipv6/2008/07/msg0.html and heated (and infamous) discussions http://sources.redhat.com/bugzilla/show_bug.cgi?id=4980 and contradiction http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427067 (seems to indicate that localhost ought to be listed in the IPv6 section, even though it means that localhost is listed twice). I have researched this question for days and can't find which answer is right. However, as a result of this bug, and as observed by aschuring, my system ends up sending DNS lookups for localhost to the WAN. However, even though localhost lookups for IPv6 might be a bug, fixing it only hides the fact that pulseaudio is not running when the alsa tools need to find it (the root cause bug). It seems like when the user logs out and the pulseaudio daemon is not running, alsa tools should stop trying to find it. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 288863] Re: Intrepid Ibex hangs when shutting down or restarting...
** This bug is no longer a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- Intrepid Ibex hangs when shutting down or restarting... https://bugs.launchpad.net/bugs/288863 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 295262] Re: acpi seems to delay shutdown
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 ** This bug has been marked a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- acpi seems to delay shutdown https://bugs.launchpad.net/bugs/295262 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 288863] Re: Intrepid Ibex hangs when shutting down or restarting...
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 This bug 288863 as originally reported is probably a duplicate of bug 274995. However, the symptom of having to shut down using the power button even after waiting 5+ more minutes is NOT a symptom of 274995. (The hang in 274995 is usually 2-3 minutes). @Brion,Kill0u since the original of this bug is a duplicate, I'm thinking your comments (involving the never-ending hang at acpid) is different. You should search for or open a specific report. You may want to consider Bug 126140, which is a failure to shut-down, (but it is specific to Intel HDA sound). But if that's not your bug, then please open one. ** This bug has been marked a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- Intrepid Ibex hangs when shutting down or restarting... https://bugs.launchpad.net/bugs/288863 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 295136] Re: amixer timeout when muting sound card
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 ** This bug has been marked a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
This was tipped by aschuring in bug 295136 with Flagman's explanation -- here's another workaround: STEP A. sudo gedit /etc/hosts STEP B. Change the first line in the IPv6 section from # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback to # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback Wallah! No more hang at shutdown or reboot or when otherwise using amixer when no user is logged in. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
@aschuring, can anyone confirm whether they have a search ... statement in /etc/resolv.conf, and whether removing that statement fixes the delays? I did not have a search statement there, but I can see where having one could lengthen the situation. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Even though they have a lot in common, I'm convinced these issues have two different root causes, but I'm also hopeful that the change for bug 126140 will also avoid ours (bug 274995). Bug 126140 is about certain PCs that remain powered up at the end of their shutdown sequence. Anyone remember the Windows It is now safe to turn off your computer screen? That's essentially the behavior of bug 126140, minus the cheery-souding Microsoft comforting. Both that problem and ours ... can be avoided by rmmod -f snd_hda_intel (the sound driver) ... generally involved Alsa ... interrupted normal shutdown But ... 274995 is not actually a hang ... 126140 actually is a hang ... 274995 has a networking workaround ... 126140 seems to have a power-management workaround The fix for bug 126140 isn't r-e-a-l-l-y a fix because it doesn't address the root cause (which certainly could be a BIOS oddness), but it does avoid it. Before the hang, the code will now respond to a system reboot signal by releasing the interrupts. It was tested against the problem in 126140. If the net effect of releasing the interrupts is the same as rmmod -f snd_hda_intel then it should also avoid our problem as well. We should test it. If it does, we should also make sure that nothing else broke in the process -- for example, does the shutdown in /etc/init.d/alsa-tools still save and zero mixer settings like it was written to do? My suggestion is that we don't call these duplicate bugs until such testing is complete, even though we are hopeful that this one change avoids both issues. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 288863] Re: Intrepid Ibex hangs when shutting down or restarting...
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 I concur that this is not a duplicate, FWIW. My read of this (288863) bug is that the failure mode is that the computer fails to shut down, the last thing displayed is acpid exiting. The hang in 274995 isn't a hang but a long delay (about 2.5 minutes). The hang in the reports involving acpid exiting seems endless. -- Intrepid Ibex hangs when shutting down or restarting... https://bugs.launchpad.net/bugs/288863 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
@aldebx re https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/103 What is your failure symptom after the suspend or hibernation? -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Okay, that helps explain why the rc.0 one alone did nothing for me -- I'm usually rebooting! ;-/ So the workaround is to do both -- sudo ln -s /etc/init.d/NetworkManager /etc/rc0.d/K40NetworkManager sudo ln -s /etc/init.d/NetworkManager /etc/rc6.d/K40NetworkManager Great job! That's a temporary work-around, and work-arounds are very good -- but when a request to test a patch or a fix comes out, you'll want to return to the previous state and delete those symlinks so you can cleanly test. sudo rm /etc/init.d/NetworkManager /etc/rc0.d/K40NetworkManager sudo rm /etc/init.d/NetworkManager /etc/rc6.d/K40NetworkManager For those who'd rather not edit, another work-around is to disconnect network cables, disable networking in nm-applet, or hit the Wi-Fi kill switch either before or during shutdown. If done before choosing shut- down or reboot, the hang is avoided. If done during the hang, then the remaining shutdown hang at the alsa step is shortened from over 2 minutes to under 15 seconds. @Daniel T. Chen -- are you still asking for help or information on this? -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
IMPORTANT CORRECTION -- please ignore my prior message, it contained a major mistake -- this is the corrected version Okay, that helps explain why the rc.0 one alone did nothing for me -- I'm usually rebooting! ;-/ So the workaround is to do both -- sudo ln -s /etc/init.d/NetworkManager /etc/rc0.d/K40NetworkManager sudo ln -s /etc/init.d/NetworkManager /etc/rc6.d/K40NetworkManager Great job! That's a temporary work-around, and work-arounds are very good -- but when a request to test a patch or a fix comes out, you'll want to return to the previous state and delete those symlinks so you can cleanly test. sudo rm /etc/rc0.d/K40NetworkManager sudo rm /etc/rc6.d/K40NetworkManager For those who'd rather not edit, another work-around is to disconnect network cables, disable networking in nm-applet, or hit the Wi-Fi kill switch either before or during shutdown. If done before choosing shut- down or reboot, the hang is avoided. If done during the hang, then the remaining shutdown hang at the alsa step is shortened from over 2 minutes to under 15 seconds. @Daniel T. Chen -- are you still asking for help or information on this? -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 291467] Re: Delayed Intrepid Login
ATM, I'm able to avoid the delay by going to System - Preferences - Sessions and clearing the checkbox next to Gnome Login Sound. -- Delayed Intrepid Login https://bugs.launchpad.net/bugs/291467 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 291467] Re: Delayed Intrepid Login
Accepted -- it must be something else that I did. Sorry for the false alarm. -- Delayed Intrepid Login https://bugs.launchpad.net/bugs/291467 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 288863] Re: Intrepid Ibex hangs when shutting down or restarting...
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 ** This bug has been marked a duplicate of bug 274995 MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up -- Intrepid Ibex hangs when shutting down or restarting... https://bugs.launchpad.net/bugs/288863 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
Just a couple of notes on this. 1. For those with working ALSA sounds, but ALSA hangs on shutdowns lasting about 2.5 minutes, I believe our bug fix is mentioned http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27.5 -- released November 7th. (I don't know how soon we will see it through normal channels -- can anyone advise?) commit a858c06703057cfdd142184e536c3ba36c45000e Author: Takashi Iwai [EMAIL PROTECTED] Date: Thu Oct 30 19:10:15 2008 + ALSA: hda - Add reboot notifier commit 0cbf00980f0fc4cc064a15ab3dfce19b5fae9130 upstream The current snd-hda-intel driver seems blocking the power-off on some devices like eeepc. Although this is likely a BIOS problem, we can add a workaround by disabling IRQ lines before power-off operation. This patch adds the reboot notifier to achieve it. The detailed problem description is found in bug#11889: http://bugme.linux-foundation.org/show_bug.cgi?id=11889 Tested-by: Luiz Fernando N. Capitulino [EMAIL PROTECTED] Signed-off-by: Takashi Iwai [EMAIL PROTECTED] Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED] 2. It's possible that this bug report is a duplicate of bug#126140. I'm not sure. That would make this a very old bug. That reporter noted that doing an rmmod of snd_hda_intel prior to shutdown avoided the hang. A similar solution posted at http://bugzilla.kernel.org/show_bug.cgi?id=7195#c3 (status NEW for over 2 years) describes putting similar entries in a shutdown script. Another commenter at https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/126140/comments/38 says that using aggressive power saving mentioned http://www.thinkwiki.org/wiki/How_to_enable_AC97_power_saving#HDA_audio_subsystem softens the problem. More recently, many are reporting, especially on ubuntuforum, that doing an ifdown on their active network avoids this ALSA hang on shutdown -- https://bugs.launchpad.net/ubuntu/+source/alsa- utils/+bug/274995/comments/25 mentions it as well. That the workarounds are different makes me wonder whether these actually are duplicates. Good luck, all! -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Jakub, What was the date/time when the system locked up? You'll want to check your logs matching up those times to help figure out why the kernel panicked. As to the printout you provided, those look like routine firewall logs. To get help with turning that off, see http://www.ubuntu.com/support/communitysupport for different ways to get help. If I had that logging problem and couldn't find the answer by searching, I might go to http://ubuntuforums.org/forumdisplay.php?f=336 and ask. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
linux-image-2.6.27-8-generic is looking good. Beware that this doesn't yet have linux-restricted-modules or -backports-modules available, these will follow in a bit. Worth repeating. I tried to apply only linux-image-2.6.27-8-generic and Synaptic let me do so without complaint. I booted into a low-res gdm. Then I went to apply all the other proposed and still ended up with graphics-related error messages and a low-res gnome. Ultimately I went back to 2.6.27-7 to System-Administration-Hardware and turned off the Restricted Nvidia driver, I then uninstalled and reinstalled linux-image-2.6.27-8-generic which fixed whatever dependencies I broke. Now that I'm up, linux-image-2.6.27-8-generic is looking good. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 295781] Re: logs (syslog, messages, kern.log) flooded on new 8.10 installation - no wlan
*** This bug is a duplicate of bug 286285 *** https://bugs.launchpad.net/bugs/286285 Bug#295781 does not appear to be a duplicate of bug#286285, which had a root cause and is patched in wifi code. -- logs (syslog, messages, kern.log) flooded on new 8.10 installation - no wlan https://bugs.launchpad.net/bugs/295781 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 259385] Re: Intrepid Compiz hangs on login for i830MG and i845 video cards
Okay, I think I'm reading that the 845G is blacklisted from compiz, thus dodging the bug(s) causing the hang. The status here, however, is Fix Released. Is that right? Seems there is still an actual bug out there to be hunted. -- Intrepid Compiz hangs on login for i830MG and i845 video cards https://bugs.launchpad.net/bugs/259385 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Dylan, you've most probably got the correct bug report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 has a patch that will ease the issue. There is an update forthcoming in the proposed repository, but so far nobody has reported on it (it was still missing as of my last check a few hours ago). Read about it https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/73 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/80. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Hi Rocko, The problem you are describing is https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990 and a patch was available for that problem. But it gets better. The patch at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 includes the patch from bug#276990 and so it eases both problems. My suggestion today is to use the patch mentioned https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990 as testers who have tried today's intrepid-proposed fixed report that it is not helping. Robb -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 260646] Re: Help-button in gnome-appearance-properties doesn't do anything
*** This bug is a duplicate of bug 136813 *** https://bugs.launchpad.net/bugs/136813 ** This bug has been marked a duplicate of bug 136813 (Gutsy) help button does not work in gnome-appearance-properties -- Help-button in gnome-appearance-properties doesn't do anything https://bugs.launchpad.net/bugs/260646 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 136813] Re: (Gutsy) help button does not work in gnome-appearance-properties
Not FIXED in 8.10/Gnome 2.24 see http://bugzilla.gnome.org/attachment.cgi?id=122030 in http://bugzilla.gnome.org/show_bug.cgi?id=473181 -- (Gutsy) help button does not work in gnome-appearance-properties https://bugs.launchpad.net/bugs/136813 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Thank you Antonio. That helps assure me that the results I'm seeing apply to the patch. As also reported above, I now can't shutdown cleanly without hitting the wifi switch. I'm not certain whether this is a new behavior or heightened awareness of an existing issue. for clarity's sake, 11 hours ago, I removed... linux-backports-modules-intrepid linux-backports-modules-intrepid-generic linux-backports-modules-2.6.27-7-generic ...and followed that with a reboot. Then I patched and rebooted again. Then I rebooted several times and haven't seen the scheduling bug. Currently synaptic shows no backports packages installed. $ ls -lc --full-time Desktop/bug286285 total 4020 -rw-r--r-- 1 robb robb 1057703 2008-11-03 18:31:30.0 -0800 iwl3945.ko -rw-r--r-- 1 robb robb 1076975 2008-11-03 18:31:30.0 -0800 iwlagn.ko -rw-r--r-- 1 robb robb 1964712 2008-11-03 18:31:30.0 -0800 iwlcore.ko $ ls -lc --full-time /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/ total 4396 -rw-r--r-- 1 root root 1057703 2008-11-03 18:31:35.0 -0800 iwl3945.ko -rw-r--r-- 1 root root 125004 2008-11-03 18:31:35.0 -0800 iwl3945.ko~ -rw-r--r-- 1 root root 1076975 2008-11-03 18:31:35.0 -0800 iwlagn.ko -rw-r--r-- 1 root root 129776 2008-11-03 18:31:35.0 -0800 iwlagn.ko~ -rw-r--r-- 1 root root 1964712 2008-11-03 18:31:35.0 -0800 iwlcore.ko -rw-r--r-- 1 root root 111220 2008-11-03 18:31:35.0 -0800 iwlcore.ko~ $ modprobe --list | grep iwlwifi /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko $ lsmod | grep iwl iwlagn 99844 0 iwlcore91972 1 iwlagn rfkill 17176 2 iwlcore led_class 12164 1 iwlcore mac80211 216820 2 iwlagn,iwlcore cfg80211 32392 3 iwlagn,iwlcore,mac80211 HTH thanks everyone! -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Tom, I got the kern.log entry mentioned at https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990/comments/92 which is the patched (comment 85) behavior of that bug. The news is that I didn't use that patch, I used the patch from comment 52 in this bug. The patch at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 has eased both problems, the scheduling report churning into kern.log and turns the wrong command queue hang into a log event. The entry that I received is Nov 4 12:13:33 topol015 kernel: [20559.634756] [ cut here ] Nov 4 12:13:33 topol015 kernel: [20559.634774] WARNING: at drivers/net/wireless/iwlwifi/iwl-tx.c:1196 iwl_tx_cmd_complete+0x2c9/0x2d0 [iwlcore]() Nov 4 12:13:33 topol015 kernel: [20559.634781] wrong command queue 63, command id 0x0 Nov 4 12:13:33 topol015 kernel: [20559.634786] Modules linked in: aes_i586 aes_generic af_packet binfmt_misc rfcomm bridge stp bnep sco l2cap bluetooth ipv6 ppdev acpi_cpufreq cpufreq_ondemand cpufreq_userspace cpufreq_conservative cpufreq_stats freq_table cpufreq_powersave container sbs pci_slot sbshc iptable_filter ip_tables x_tables coretemp sbp2 parport_pc lp parport joydev snd_hda_intel arc4 ecb crypto_blkcipher snd_pcm_oss snd_mixer_oss snd_pcm iwlagn snd_seq_dummy iwlcore snd_seq_oss uvcvideo rfkill snd_seq_midi compat_ioctl32 led_class videodev snd_rawmidi psmouse mac80211 v4l1_compat snd_seq_midi_event serio_raw pcspkr evdev nvidia(P) snd_seq cfg80211 i2c_core snd_timer snd_seq_device sdhci_pci snd sdhci video output ricoh_mmc mmc_core battery wmi soundcore ac button iTCO_wdt iTCO_vendor_support intel_agp agpgart snd_page_alloc shpchp pci_hotplug ext3 jbd mbcache sr_mod cdrom ata_generic sd_mod crc_t10dif sg ata_piix ahci ohci1394 pata_acpi ieee1394 libata scsi_mod dock r8169 ehci_hcd uhci_hcd usbcore t Nov 4 12:13:33 topol015 kernel: ermal processor fan fbcon tileblit font bitblit softcursor fuse Nov 4 12:13:33 topol015 kernel: [20559.635009] Pid: 5617, comm: Xorg Tainted: P 2.6.27-7-generic #1 Nov 4 12:13:33 topol015 kernel: [20559.635016] [c0131d65] warn_slowpath+0x65/0x90 Nov 4 12:13:33 topol015 kernel: [20559.635035] [c0234775] ? apparmor_socket_recvmsg+0x15/0x20 Nov 4 12:13:33 topol015 kernel: [20559.635048] [c02e5036] ? __sock_recvmsg+0x66/0x80 Nov 4 12:13:33 topol015 kernel: [20559.635059] [c02e512c] ? sock_aio_read+0xdc/0x120 Nov 4 12:13:33 topol015 kernel: [20559.635069] [f8d8ef49] iwl_tx_cmd_complete+0x2c9/0x2d0 [iwlcore] Nov 4 12:13:33 topol015 kernel: [20559.635094] [c01b1f19] ? do_sync_read+0xd9/0x120 Nov 4 12:13:33 topol015 kernel: [20559.635106] [f8cb2a49] iwl_rx_handle+0xd9/0x260 [iwlagn] Nov 4 12:13:33 topol015 kernel: [20559.635125] [f8cb469d] iwl4965_irq_tasklet+0x1ad/0x2f0 [iwlagn] Nov 4 12:13:33 topol015 kernel: [20559.635140] [c01e1fce] ? inotify_inode_queue_event+0xe/0xe0 Nov 4 12:13:33 topol015 kernel: [20559.635152] [c0137258] tasklet_action+0x78/0x100 Nov 4 12:13:33 topol015 kernel: [20559.635161] [c0137682] __do_softirq+0x92/0x120 Nov 4 12:13:33 topol015 kernel: [20559.635169] [c013776d] do_softirq+0x5d/0x60 Nov 4 12:13:33 topol015 kernel: [20559.635176] [c01378e5] irq_exit+0x55/0x90 Nov 4 12:13:33 topol015 kernel: [20559.635184] [c0106c1a] do_IRQ+0x4a/0x80 Nov 4 12:13:33 topol015 kernel: [20559.635193] [c0146067] ? sys_clock_gettime+0x57/0xb0 Nov 4 12:13:33 topol015 kernel: [20559.635205] [c0105003] common_interrupt+0x23/0x30 Nov 4 12:13:33 topol015 kernel: [20559.635214] === Nov 4 12:13:33 topol015 kernel: [20559.635219] ---[ end trace 44f093d96ce74abe ]--- It happend 57.5 minutes after reassociation to a rebooted DIR-655 802.11n WPA/WPA2 router. -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 276990] Re: iwlagn causes kernel panic on 802.11n wifi
Tom (comment 93), Please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/63 for some info. --Robb -- iwlagn causes kernel panic on 802.11n wifi https://bugs.launchpad.net/bugs/276990 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
Tom, if I use apt-get to remove backports and then try the patch, is that a clean test? -- kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100 https://bugs.launchpad.net/bugs/286285 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 286285] Re: kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100
I removed backports, rebooted, then installed the patch per Tom's instructions, rebooted, and now I've rebooted several times. I cannot reproduce the original problem. However, I can't shut down without hitting the wifi killswitch. 18:45 Shut down from Gnome 18:46 Hanging... hanging... (and will continue to hang) 18:47 Flip the Wi-Fi switch 18:48 Shutdown completes /var/log/kern.log Nov 3 18:42:30 topol015 kernel: [ 158.992820] type=1503 audit(1225766550.341:14): operation=socket_create family=x25 sock_type=seqpacket protocol=0 pid=6230 profile=/usr/sbin/cupsd Nov 3 18:45:44 topol015 kernel: [ 352.808577] apm: BIOS not found. Nov 3 18:45:46 topol015 kernel: [ 355.263861] ip6_tables: (C) 2000-2006 Netfilter Core Team Nov 3 18:47:15 topol015 kernel: [ 444.087373] iwlagn: Radio Frequency Kill Switch is On: Nov 3 18:47:15 topol015 kernel: [ 444.087378] Kill switch must be turned off for wireless networking to work. Nov 3 18:47:20 topol015 kernel: [ 449.308039] wlan0: No ProbeResp from current AP 00:1e:58:f3:26:e5 - assume out of range Nov 3 18:47:20 topol015 kernel: [ 449.310549] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 Nov 3 18:47:20 topol015 kernel: [ 449.310727] mac80211-phy0: failed to remove key (0, 00:1e:58:f3:26:e5) from hardware (-5) Nov 3 18:47:20 topol015 kernel: [ 449.317281] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5 Nov 3 18:47:20 topol015 kernel: [ 449.317438] mac80211-phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5) Nov 3 18:48:31 topol015 kernel: Inspecting /boot/System.map-2.6.27-7-generic Nov 3 18:48:31 topol015 kernel: Cannot find map file. Nov 3 18:48:31 topol015 kernel: Loaded 70488 symbols from 101 modules. Nov 3 18:48:31 topol015 kernel: [0.00] Initializing cgroup subsys cpuset Nov 3 18:48:31 topol015 kernel: [0.00] Initializing cgroup subsys cpu Nov 3 18:48:31 topol015 kernel: [0.00] Linux version 2.6.27-7-generic ([EMAIL PROTECTED]) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Oct 30 04:18:38 UTC 2008 (Ubuntu 2.6.27-7.15-generic) /var/log/messages Nov 3 18:42:30 topol015 kernel: [ 158.992815] type=1503 audit(1225766550.341:13): operation=socket_create family=ash sock_type=dgram protocol=0 pid=6230 profile=/usr/sbin/cupsd Nov 3 18:42:30 topol015 kernel: [ 158.992820] type=1503 audit(1225766550.341:14): operation=socket_create family=x25 sock_type=seqpacket protocol=0 pid=6230 profile=/usr/sbin/cupsd Nov 3 18:45:40 topol015 bonobo-activation-server (robb-6323): could not associate with desktop session: Failed to connect to socket /tmp/dbus-8pCCuzghiS: Connection refused Nov 3 18:45:44 topol015 kernel: [ 352.808577] apm: BIOS not found. Nov 3 18:45:46 topol015 kernel: [ 355.263861] ip6_tables: (C) 2000-2006 Netfilter Core Team Nov 3 18:47:15 topol015 kernel: [ 444.087373] iwlagn: Radio Frequency Kill Switch is On: Nov 3 18:47:15 topol015 kernel: [ 444.087378] Kill switch must be turned off for wireless networking to work. Nov 3 18:47:38 topol015 exiting on signal 15 Nov 3 18:48:31 topol015 syslogd 1.5.0#2ubuntu6: restart. Nov 3 18:48:31 topol015 kernel: Inspecting /boot/System.map-2.6.27-7-generic Nov 3 18:48:31 topol015 kernel: Cannot find map file. Nov 3 18:48:31 topol015 kernel: Loaded 70488 symbols from 101 modules. Nov 3 18:48:31 topol015 kernel: [0.00] Initializing cgroup subsys cpuset Nov 3 18:48:31 topol015 kernel: [0.00] Initializing cgroup subsys cpu Nov 3 18:48:31 topol015 kernel: [0.00] Linux version 2.6.27-7-generic ([EMAIL PROTECTED]) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Oct 30 04:18:38 UTC 2008 (Ubuntu 2.6.27-7.15-generic) Nov 3 18:48:31 topol015 kernel: [0.00] BIOS-provided physical RAM map: /var/log/syslog Nov 3 18:40:19 topol015 kernel: [ 27.695965] Registered led device: iwl-phy0:radio Nov 3 18:40:19 topol015 kernel: [ 27.696243] Registered led device: iwl-phy0:assoc Nov 3 18:40:19 topol015 kernel: [ 27.697753] Registered led device: iwl-phy0:RX Nov 3 18:40:19 topol015 kernel: [ 27.699182] Registered led device: iwl-phy0:TX Nov 3 18:40:19 topol015 kernel: [ 27.708662] ADDRCONF(NETDEV_UP): wlan0: link is not ready Nov 3 18:40:19 topol015 NetworkManager: info (wlan0): preparing device. Nov 3 18:40:19 topol015 NetworkManager: info (wlan0): deactivating device (reason: 2). Nov 3 18:40:19 topol015 NetworkManager: info (eth0): carrier now ON (device state 2) Nov 3 18:40:19 topol015 NetworkManager: info (eth0): device state change: 2 - 3 Nov 3 18:40:19 topol015 NetworkManager: info (eth0): carrier now OFF (device state 3) Nov 3 18:40:19 topol015 NetworkManager: info (eth0): device state change: 3 - 2 Nov 3 18:40:19 topol015 NetworkManager: info (eth0): deactivating device (reason: 0). Nov 3 18:40:19 topol015 NetworkManager: info (wlan0): device state change: 2 - 3 Nov 3 18:40:19 topol015
