Karmic 64-bit
Lenovo T400 (switchable graphics.  Using ONLY Intel graphics and Ubuntu drivers.)
Seamonkey browser
 
My system keeps crashing.  I have had crashing problems since install but it it worse now.  I am using a local wireless LAN which seems to be causing problems.  Here are syslogs from the last two crashes.  This line shows where the system is restarted:  Initializing cgroup subsys cpuset
 
Crash-1
Feb 15 15:08:34 foobar avahi-daemon[1479]: Invalid query packet.Feb 15 15:08:48 foobar avahi-daemon[1479]: last message repeated 14 timesFeb 15 15:08:48 foobar avahi-daemon[1479]: Invalid response packet from host 134.60.237.66.Feb 15 15:08:55 foobar avahi-daemon[1479]: Invalid query packet.Feb 15 15:09:01 foobar avahi-daemon[1479]: last message repeated 4 timesFeb 15 15:09:01 foobar CRON[6638]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)Feb 15 15:09:16 foobar avahi-daemon[1479]: Invalid query packet.Feb 15 15:09:19 foobar avahi-daemon[1479]: last message repeated 2 timesFeb 15 15:09:19 foobar wpa_supplicant[1596]: CTRL-EVENT-SCAN-RESULTS Feb 15 15:09:39 foobar dhclient: DHCPREQUEST of 134.60.237.75 on wlan0 to 134.60.1.23 port 67Feb 15 15:09:39 foobar dhclient: DHCPACK of 134.60.237.75 from 134.60.1.23Feb 15 15:09:39 foobar dhclient: bound to 134.60.237.75 -- renewal in 76 seconds.Feb 15 15:10:34 foobar avahi-daemon[1479]: Invalid query packet.Feb 15 15:10:55 foobar avahi-daemon[1479]: last message repeated 7 timesFeb 15 15:10:55 foobar dhclient: DHCPREQUEST of 134.60.237.75 on wlan0 to 134.60.1.23 port 67Feb 15 15:10:55 foobar dhclient: DHCPACK of 134.60.237.75 from 134.60.1.23Feb 15 15:10:55 foobar dhclient: bound to 134.60.237.75 -- renewal in 80 seconds.Feb 15 15:11:19 foobar wpa_supplicant[1596]: CTRL-EVENT-SCAN-RESULTS Feb 15 15:11:22 foobar avahi-daemon[1479]: Invalid query packet.Feb 15 15:12:15 foobar avahi-daemon[1479]: last message repeated 8 timesFeb 15 15:12:15 foobar dhclient: DHCPREQUEST of 134.60.237.75 on wlan0 to 134.60.1.23 port 67Feb 15 15:12:15 foobar dhclient: DHCPACK of 134.60.237.75 from 134.60.1.23Feb 15 15:12:15 foobar dhclient: bound to 134.60.237.75 -- renewal in 77 seconds.Feb 15 15:12:24 foobar avahi-daemon[1479]: Invalid query packet.Feb 15 15:13:19 foobar avahi-daemon[1479]: last message repeated 8 timesFeb 15 15:13:19 foobar wpa_supplicant[1596]: CTRL-EVENT-SCAN-RESULTS Feb 15 15:13:22 foobar avahi-daemon[1479]: Invalid query packet.Feb 15 15:13:32 foobar avahi-daemon[1479]: last message repeated 5 timesFeb 15 15:13:32 foobar dhclient: DHCPREQUEST of 134.60.237.75 on wlan0 to 134.60.1.23 port 67Feb 15 15:13:32 foobar dhclient: DHCPACK of 134.60.237.75 from 134.60.1.23Feb 15 15:13:32 foobar dhclient: bound to 134.60.237.75 -- renewal in 72 seconds.Feb 15 15:13:41 foobar avahi-daemon[1479]: Invalid query packet.Feb 15 15:16:03 foobar kernel: imklog 4.2.0, log source = /var/run/rsyslog/kmsg started.Feb 15 15:16:03 foobar rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1379" x-info="http://www.rsyslog.com"] (re)startFeb 15 15:16:03 foobar rsyslogd: rsyslogd's groupid changed to 103Feb 15 15:16:03 foobar rsyslogd: rsyslogd's userid changed to 101Feb 15 15:16:03 foobar rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]Feb 15 15:16:03 foobar kernel: [    0.000000] Initializing cgroup subsys cpusetFeb 15 15:16:03 foobar kernel: [    0.000000] Initializing cgroup subsys cpu
 
 
Crash-2
 
Feb 15 15:20:40 foobar dhclient: bound to 134.60.237.75 -- renewal in 74 seconds.Feb 15 15:20:53 foobar avahi-daemon[1506]: Invalid query packet.Feb 15 15:21:43 foobar avahi-daemon[1506]: last message repeated 17 timesFeb 15 15:21:43 foobar wpa_supplicant[1768]: CTRL-EVENT-SCAN-RESULTS Feb 15 15:21:44 foobar avahi-daemon[1506]: Invalid query packet.Feb 15 15:21:54 foobar avahi-daemon[1506]: last message repeated 9 timesFeb 15 15:21:54 foobar dhclient: DHCPREQUEST of 134.60.237.75 on wlan0 to 134.60.1.23 port 67Feb 15 15:21:54 foobar dhclient: DHCPACK of 134.60.237.75 from 134.60.1.23Feb 15 15:21:54 foobar dhclient: bound to 134.60.237.75 -- renewal in 76 seconds.Feb 15 15:21:55 foobar avahi-daemon[1506]: Invalid query packet.Feb 15 15:23:02 foobar avahi-daemon[1506]: last message repeated 24 timesFeb 15 15:23:10 foobar avahi-daemon[1506]: last message repeated 3 timesFeb 15 15:23:10 foobar dhclient: DHCPREQUEST of 134.60.237.75 on wlan0 to 134.60.1.23 port 67Feb 15 15:23:10 foobar dhclient: DHCPACK of 134.60.237.75 from 134.60.1.23Feb 15 15:23:10 foobar dhclient: bound to 134.60.237.75 -- renewal in 83 seconds.Feb 15 15:23:10 foobar avahi-daemon[1506]: Invalid query packet.Feb 15 15:24:36 foobar kernel: imklog 4.2.0, log source = /var/run/rsyslog/kmsg started.Feb 15 15:24:36 foobar rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1379" x-info="http://www.rsyslog.com"] (re)startFeb 15 15:24:36 foobar rsyslogd: rsyslogd's groupid changed to 103Feb 15 15:24:36 foobar rsyslogd: rsyslogd's userid changed to 101Feb 15 15:24:36 foobar rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]Feb 15 15:24:36 foobar kernel: [    0.000000] Initializing cgroup subsys cpusetFeb 15 15:24:36 foobar kernel: [    0.000000] Initializing cgroup subsys cpu
 
Thanks

1 answers, votes, 1381 views
solidstate's picture
asked by solidstate
1 year 50 weeks ago



1 Answers

  • Thanks for the answer!
    I ran Memtest86+ (V2.something)  and it produced no memory errors.
    I'm hoping Ubuntu 10.4 is more stable.  I'm just going to wait until it is released and do a fresh install.
     
    The crashes happen even when the WLAN card is turned off with the hardware switch.

    - Visitor 1 year 44 weeks ago
  • Bad Ram or parts in the cpu bad?
    as it crashes on the calling of cpuset .
    Since your running Intel graphics you can probably test lucid see if its any different in that regard.
    Actually a google points to wireless driver.  If I had to bet its broadcom proprietary.  Broadcom wireless drivers do that sometimes especially the first few karmic ones did.
    Your best bet is to use the ones in Lucid, broadcom-sta-* or bcmwl-*
    You can probably just use files from lucid in karmic actually
    https://launchpad.net/ubuntu/+source/bcmwl

    - Visitor 1 year 50 weeks ago
  • Answer

    Bad Ram or parts in the cpu bad?
    as it crashes on the calling of cpuset .
    Since your running Intel graphics you can probably test lucid see if its any different in that regard.
    Actually a google points to wireless driver.  If I had to bet its
    broadcom proprietary.  Broadcom wireless drivers do that sometimes
    especially the first few karmic ones did.
    Your best bet is to use the ones in Lucid, broadcom-sta-* or bcmwl-*

    You can probably just use files from lucid in karmic actually https://launchpad.net/ubuntu/+source/bcmwl

    Visitor's picture
    answer by Visitor
    1 year 44 weeks ago

    Ubuntu 11.04 released!

    Ubuntu 11.04 code named natty narwhal is released download ubuntu 11.04

    Read ubuntu 11.10 reviews and share yours now!!

    View in your own language!

    Stay Connected

    Ubun2.com on Facebook Ubun2.com on Twitter RSS Feeds

    Poll

    Favorite desktop environment?: