Announcement

Collapse
No announcement yet.

lock up without active eth0

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    lock up without active eth0

    From the time I installed 32 bit Kubuntu 11.04 alongside Windows 7 that came with a new Acer Aspire 5250, the system freezes while trying to enter passwd or shortly after, unless an active cable is plugged into eth0 or I've recently finished a Windows 7 entertainment and quickly booted Linux. No mouse or keyboard works. ^ - Alt – Fn doesn't work. ^ - Alt – BS doesn't restart X. Alt – SysReq – r . . . doesn't work. Only the power switch works. I've tried other suggested fixes but nothing works
    but to plug in eth0 and cycle the power.
    OpenGLI unsafe=false >> true did nothing.
    [ifupdown]
    managed=false >> true did nothing.
    ~/_$sudo apt-get --reinstall install kubuntu-desktop did nothing.

    The system log entries from the time eth0 was unplugged until the reboot after the inevitable lock up:
    g 9 13:23:10 agk-acer ntfs-3g[2059]: Mounted /dev/sda3 (Read-Write, label "Acer", NTFS 3.1)
    Aug 9 13:23:10 agk-acer ntfs-3g[2059]: Cmdline options: rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=100,dm ask=0077,fmask=0177
    Aug 9 13:23:10 agk-acer ntfs-3g[2059]: Mount options: rw,nosuid,nodev,uhelper=udisks,allow_other,nonempt y,relatime,fsname=/dev/sda3,blkdev,blksize=4096,default_permissions
    Aug 9 13:23:10 agk-acer ntfs-3g[2059]: Global ownership and permissions enforced, configuration type 1
    ************* unplug eth0 [or deactivate dsl or whatever is on the other end of the cable such as back to back with another ethernet] ************
    Aug 9 13:35:04 agk-acer NetworkManager[673]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
    Aug 9 13:35:04 agk-acer kernel: [ 893.002099] atl1c 0000:06:00.0: atl1c: eth0 NIC Link is Down
    Aug 9 13:35:06 agk-acer NetworkManager[673]: <info> (eth0): carrier now ON (device state 8)
    Aug 9 13:35:06 agk-acer kernel: [ 894.516302] atl1c 0000:06:00.0: atl1c: eth0 NIC Link is Up<10 Mbps Full Duplex>
    Aug 9 13:35:07 agk-acer kernel: [ 895.428584] atl1c 0000:06:00.0: atl1c: eth0 NIC Link is Down
    Aug 9 13:35:07 agk-acer NetworkManager[673]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
    Aug 9 13:35:11 agk-acer NetworkManager[673]: <info> (eth0): device state change: 8 -> 2 (reason 40)
    Aug 9 13:35:11 agk-acer NetworkManager[673]: <info> (eth0): deactivating device (reason: 40).
    Aug 9 13:35:11 agk-acer avahi-daemon[669]: Withdrawing address record for 192.168.113.78 on eth0.
    Aug 9 13:35:11 agk-acer avahi-daemon[669]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.113.78.
    Aug 9 13:35:11 agk-acer avahi-daemon[669]: Interface eth0.IPv4 no longer relevant for mDNS.
    Aug 9 13:35:11 agk-acer NetworkManager[673]: <info> Policy set 'wagknet' (wlan0) as default for IPv4 routing and DNS.
    Aug 9 14:20:59 agk-acer kernel: imklog 4.6.4, log source = /proc/kmsg started.
    Aug 9 14:20:59 agk-acer rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="737" x-info="http://www.rsyslog.com"] (re)start

    I'd originally installed 64 bit version. Everything else OK but lockups still occurred. Several reinstalls of 32 bit followed but nothing helped.


    If you've experienced this phenomenon, please help.
    Tags: None
    • Top
    • Bottom
    #2
    Re: lock up without active eth0

    That model of Acer One has been sold with Broadcom, Realtek and Atheros wifi chips. Which one does your system have? (lspic in Konsole).

    The Acer 5250 Driver Site may be useful later on.
    "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
    – John F. Kennedy, February 26, 1962.
    • Top
    • Bottom

    Comment

      #3
      Re: lock up without active eth0

      GreyGeek,

      GreyGeek,
      Thanks for responding. I understand the instinctual suspicion of drivers. Software geeks always point fingers at the hardware engineers and vice versa. But operator error, the scapegoat for both, is not likely I think.

      Both eth0 and wlan0 use Atheros contollers. Both controllers work flawlessly in either Windows or 11.04. When rebooting after a Windows session, no lock up occurs when eth0 is unplugged. Wlan0 hooks up and network connectivity is normal.
      When cold booting Linux, the system hangs at login, unless eth0 is plugged in. If I break the connection during the session, wlan0 takes over just before the system locks up.
      I want to approach this as I did during my working life as an electronics engineer specializing in computer interfaces and low level software/firmware. I don't believe trial and error troubleshooting with drivers is the right course at this time. This maybe an initialization or event handling script problem. Can you point me in likely directions to explore?


      Thanks ,
      agk
      • Top
      • Bottom

      Comment

        #4
        Re: lock up without active eth0

        Someone by the name of "Scorbot" (Is that you?) posted a similar question on the Ubuntu forum a couple weeks ago. Here is the thread. Posting #3 has a possible work around.

        Personally, I don't use NetworkManager. I install the wicd (all 5 packages) and then totally remove NetworkManager, including the runtime, configure wicid and reboot.
        "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
        – John F. Kennedy, February 26, 1962.
        • Top
        • Bottom

        Comment

          #5
          Re: lock up without active eth0

          No, GreyGeek, I'm not Scorbett, just agkaiser. I'm a young kid of 65.
          8/9/11 7:45p
          Moved network boot above HDD with CD and USB above net.
          Three minutes and no lockup.
          Got a missing cable warning from BIOS before grub menu but OK otherwise. I wonder what happens when the cable is plugged in? I'll plug in before restart and see what happens now.
          Plugged in and it hooked up immediately. Now what will BIOS do on reboot? First I'll pull the plug and see what happens. If it freezes I'll record it here next time. 7:54P

          8:00P and still working. Time to reboot with eth0

          8:05P BIOS tries to get DHCP address but it's ESCapable. Goes to grub. OK.
          8:08P pull plug again. Hooked up wireless. Still here at 8:15
          Hmm? I never did like Network Manager. Too patronizingly presumptuous, like Microsucks. This seems to work for now but I'll check out wicd soon.
          • Top
          • Bottom

          Comment

            #6
            Re: lock up without active eth0

            A youngster, heh?

            mmm... a BIOS warning msg about a missing cable. This is before upstart is fired, so that's why your logs didn't show any connect or disconnect problems.

            It looks like you have things sorted out.
            "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
            – John F. Kennedy, February 26, 1962.
            • Top
            • Bottom

            Comment

              #7
              Re: lock up without active eth0

              I read a comment of your where you identified yourself as a physicist. So you know what it means to know a thing.

              I don't have the problem sorted out satisfactorily. The cable, as BIOS warned, was unplugged. Only after that expression by the usually silent agent of the hardware, did the Network Manager see the obvious and compensate by hooking up the wireless and allowing the OS to go forward with its usual function. So, while I have a workaround, I still don't know why KDE didn't handle things in the first place or why it has to be tricked into working properly. If you know what's happening here, please , help me understand.
              agk

              PS The log from Aug 9 clearly showed the shutdown of eth0 and the startup of wlan0 just before the crash, power off and reboot. Before I pushed the net boot up in BIOS, the lack or loss of eth0's connection to the dsl triggered a lock up.

              ************* unplug eth0 [or deactivate dsl or whatever is on the other end of the cable such as back to back with another ethernet] ************

              Aug 9 13:35:04 agk-acer NetworkManager[673]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
              Aug 9 13:35:04 agk-acer kernel: [ 893.002099] atl1c 0000:06:00.0: atl1c: eth0 NIC Link is Down
              Aug 9 13:35:06 agk-acer NetworkManager[673]: <info> (eth0): carrier now ON (device state Cool
              Aug 9 13:35:06 agk-acer kernel: [ 894.516302] atl1c 0000:06:00.0: atl1c: eth0 NIC Link is Up<10 Mbps Full Duplex>
              Aug 9 13:35:07 agk-acer kernel: [ 895.428584] atl1c 0000:06:00.0: atl1c: eth0 NIC Link is Down
              Aug 9 13:35:07 agk-acer NetworkManager[673]: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
              Aug 9 13:35:11 agk-acer NetworkManager[673]: <info> (eth0): device state change: 8 -> 2 (reason 40)
              Aug 9 13:35:11 agk-acer NetworkManager[673]: <info> (eth0): deactivating device (reason: 40).
              Aug 9 13:35:11 agk-acer avahi-daemon[669]: Withdrawing address record for 192.168.113.78 on eth0.
              Aug 9 13:35:11 agk-acer avahi-daemon[669]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.113.78.
              Aug 9 13:35:11 agk-acer avahi-daemon[669]: Interface eth0.IPv4 no longer relevant for mDNS.
              Aug 9 13:35:11 agk-acer NetworkManager[673]: <info> Policy set 'wagknet' (wlan0) as default for IPv4 routing and DNS.
              last entry before crash at 13:35:11

              didn't restart for 45 minutes:
              Aug 9 14:20:59 agk-acer kernel: imklog 4.6.4, log source = /proc/kmsg started.
              Aug 9 14:20:59 agk-acer rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="737" x-info="http://www.rsyslog.com"] (re)start

              • Top
              • Bottom

              Comment

              Previous template Next
              Working...
              X