On 09/10/2013 01:21 PM, Jeff Simmons issued this missive:
Install Fedora 19.1 (XFCE spin 64b) on a Samsung netbook, Atom N550. Everything looks good. Run 'yum update', take a break while it runs through 786 operations. Reboot. LIttle F appears in the center of the screen and fills in. Screen goes to text mode and announces: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement) brcmsmac bcma0:0: brcms_ops_config: change-powersave-mode: false (implement) (timestamps delided) and hangs. The only input that does anything is CTL-ALT-DEL, which reboots system and repeats above. Happens for updated kernel boot, old kernel boot, and rescue boot. So, reboot and wait ten minutes. Suddenly, the screen saver unlocker appears. I enter my password, and up pops Fedora as if nothing had happened. Quick check of dmesg shows the above announcement near the very end (last 12 lines of dmesg): [ 29.827065] Ebtables v2.0 registered [ 30.059665] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 33.669448] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 33.669640] brcmsmac bcma0:0: brcms_ops_config: change power-save mode: false (implement) [ 33.670461] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready [ 33.744830] sky2 0000:09:00.0 p3p1: enabling interface [ 33.745964] IPv6: ADDRCONF(NETDEV_UP): p3p1: link is not ready [ 33.769149] rtl8192cu: MAC auto ON okay! [ 33.812090] rtl8192cu: Tx queue select: 0x05 [ 34.191539] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u7: link is not ready [ 35.306178] sky2 0000:09:00.0 p3p1: Link is up at 100 Mbps, full duplex, flow control rx [ 35.306178] IPv6: ADDRCONF(NETDEV_CHANGE): p3p1: link becomes ready Anybody got a clue what's going on?
The messages indicate that your network card is now getting IPV6 addresses (not all routers, gateways or ISPs handle that well). There was a bit of a big time delay for that. You might try disabling IPV6 and see if that improves things. If you're running sendmail or anything that demands network I/O, they can hold things up until the network goes active and they can do their thing or the app times out. IIRC, sendmail can delay for quite a while depending on what the queue scan period is. It's bitten us before. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - IGNORE that man behind the keyboard! - - - The Wizard of OS - ---------------------------------------------------------------------- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
