* [PATCH] bcm43xx: Fix loss of association after resume @ 2007-02-09 16:18 ` Larry Finger 0 siblings, 0 replies; 26+ messages in thread From: Larry Finger @ 2007-02-09 16:18 UTC (permalink / raw) To: John Linville; +Cc: Michael Buesch, netdev, Bcm43xx-dev, linux-wireless After a suspend/resume cycle, bcm43xx-softmac has lost its association with the AP and requires manual intervention. This situation is fixed by making one of softmac's internal routines public and calling it. Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net> --- Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c =================================================================== --- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c +++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c @@ -4278,6 +4278,7 @@ static int bcm43xx_resume(struct pci_dev { struct net_device *net_dev = pci_get_drvdata(pdev); struct bcm43xx_private *bcm = bcm43xx_priv(net_dev); + struct ieee80211softmac_device *mac = ieee80211_priv(net_dev); int err = 0; dprintk(KERN_INFO PFX "Resuming...\n"); @@ -4299,6 +4300,9 @@ static int bcm43xx_resume(struct pci_dev } netif_device_attach(net_dev); + if (mac->associnfo.associated) + ieee80211softmac_try_reassoc(mac); + dprintk(KERN_INFO PFX "Device resumed.\n"); return 0; Index: linux-2.6/include/net/ieee80211softmac.h =================================================================== --- linux-2.6.orig/include/net/ieee80211softmac.h +++ linux-2.6/include/net/ieee80211softmac.h @@ -254,6 +254,7 @@ struct ieee80211softmac_device { }; extern void ieee80211softmac_scan_finished(struct ieee80211softmac_device *sm); +extern void ieee80211softmac_try_reassoc(struct ieee80211softmac_device *mac); static inline void * ieee80211softmac_priv(struct net_device *dev) { Index: linux-2.6/net/ieee80211/softmac/ieee80211softmac_assoc.c =================================================================== --- linux-2.6.orig/net/ieee80211/softmac/ieee80211softmac_assoc.c +++ linux-2.6/net/ieee80211/softmac/ieee80211softmac_assoc.c @@ -441,6 +441,7 @@ ieee80211softmac_try_reassoc(struct ieee schedule_delayed_work(&mac->associnfo.work, 0); spin_unlock_irqrestore(&mac->lock, flags); } +EXPORT_SYMBOL_GPL(ieee80211softmac_try_reassoc); int ieee80211softmac_handle_disassoc(struct net_device * dev, ^ permalink raw reply [flat|nested] 26+ messages in thread
* [PATCH] bcm43xx: Fix loss of association after resume @ 2007-02-09 16:18 ` Larry Finger 0 siblings, 0 replies; 26+ messages in thread From: Larry Finger @ 2007-02-09 16:18 UTC (permalink / raw) To: John Linville Cc: netdev-u79uwXL29TY76Z2rM5mHXA, linux-wireless-u79uwXL29TY76Z2rM5mHXA, Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w, Michael Buesch After a suspend/resume cycle, bcm43xx-softmac has lost its association with the AP and requires manual intervention. This situation is fixed by making one of softmac's internal routines public and calling it. Signed-off-by: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org> --- Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c =================================================================== --- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c +++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c @@ -4278,6 +4278,7 @@ static int bcm43xx_resume(struct pci_dev { struct net_device *net_dev = pci_get_drvdata(pdev); struct bcm43xx_private *bcm = bcm43xx_priv(net_dev); + struct ieee80211softmac_device *mac = ieee80211_priv(net_dev); int err = 0; dprintk(KERN_INFO PFX "Resuming...\n"); @@ -4299,6 +4300,9 @@ static int bcm43xx_resume(struct pci_dev } netif_device_attach(net_dev); + if (mac->associnfo.associated) + ieee80211softmac_try_reassoc(mac); + dprintk(KERN_INFO PFX "Device resumed.\n"); return 0; Index: linux-2.6/include/net/ieee80211softmac.h =================================================================== --- linux-2.6.orig/include/net/ieee80211softmac.h +++ linux-2.6/include/net/ieee80211softmac.h @@ -254,6 +254,7 @@ struct ieee80211softmac_device { }; extern void ieee80211softmac_scan_finished(struct ieee80211softmac_device *sm); +extern void ieee80211softmac_try_reassoc(struct ieee80211softmac_device *mac); static inline void * ieee80211softmac_priv(struct net_device *dev) { Index: linux-2.6/net/ieee80211/softmac/ieee80211softmac_assoc.c =================================================================== --- linux-2.6.orig/net/ieee80211/softmac/ieee80211softmac_assoc.c +++ linux-2.6/net/ieee80211/softmac/ieee80211softmac_assoc.c @@ -441,6 +441,7 @@ ieee80211softmac_try_reassoc(struct ieee schedule_delayed_work(&mac->associnfo.work, 0); spin_unlock_irqrestore(&mac->lock, flags); } +EXPORT_SYMBOL_GPL(ieee80211softmac_try_reassoc); int ieee80211softmac_handle_disassoc(struct net_device * dev, ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume @ 2007-02-09 16:53 ` Michael Buesch 0 siblings, 0 replies; 26+ messages in thread From: Michael Buesch @ 2007-02-09 16:53 UTC (permalink / raw) To: Larry Finger; +Cc: John Linville, netdev, Bcm43xx-dev, linux-wireless On Friday 09 February 2007 17:18, Larry Finger wrote: > After a suspend/resume cycle, bcm43xx-softmac has lost its association with > the AP and requires manual intervention. This situation is fixed by making > one of softmac's internal routines public and calling it. > > Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net> Ack, this is good as workaround. > > Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c > =================================================================== > --- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c > +++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c > @@ -4278,6 +4278,7 @@ static int bcm43xx_resume(struct pci_dev > { > struct net_device *net_dev = pci_get_drvdata(pdev); > struct bcm43xx_private *bcm = bcm43xx_priv(net_dev); > + struct ieee80211softmac_device *mac = ieee80211_priv(net_dev); > int err = 0; > > dprintk(KERN_INFO PFX "Resuming...\n"); > @@ -4299,6 +4300,9 @@ static int bcm43xx_resume(struct pci_dev > } > netif_device_attach(net_dev); > > + if (mac->associnfo.associated) > + ieee80211softmac_try_reassoc(mac); > + > dprintk(KERN_INFO PFX "Device resumed.\n"); > > return 0; > Index: linux-2.6/include/net/ieee80211softmac.h > =================================================================== > --- linux-2.6.orig/include/net/ieee80211softmac.h > +++ linux-2.6/include/net/ieee80211softmac.h > @@ -254,6 +254,7 @@ struct ieee80211softmac_device { > }; > > extern void ieee80211softmac_scan_finished(struct ieee80211softmac_device *sm); > +extern void ieee80211softmac_try_reassoc(struct ieee80211softmac_device *mac); > > static inline void * ieee80211softmac_priv(struct net_device *dev) > { > Index: linux-2.6/net/ieee80211/softmac/ieee80211softmac_assoc.c > =================================================================== > --- linux-2.6.orig/net/ieee80211/softmac/ieee80211softmac_assoc.c > +++ linux-2.6/net/ieee80211/softmac/ieee80211softmac_assoc.c > @@ -441,6 +441,7 @@ ieee80211softmac_try_reassoc(struct ieee > schedule_delayed_work(&mac->associnfo.work, 0); > spin_unlock_irqrestore(&mac->lock, flags); > } > +EXPORT_SYMBOL_GPL(ieee80211softmac_try_reassoc); > > int > ieee80211softmac_handle_disassoc(struct net_device * dev, > - > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- Greetings Michael. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume @ 2007-02-09 16:53 ` Michael Buesch 0 siblings, 0 replies; 26+ messages in thread From: Michael Buesch @ 2007-02-09 16:53 UTC (permalink / raw) To: Larry Finger Cc: netdev-u79uwXL29TY76Z2rM5mHXA, linux-wireless-u79uwXL29TY76Z2rM5mHXA, John Linville, Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w On Friday 09 February 2007 17:18, Larry Finger wrote: > After a suspend/resume cycle, bcm43xx-softmac has lost its association with > the AP and requires manual intervention. This situation is fixed by making > one of softmac's internal routines public and calling it. > > Signed-off-by: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org> Ack, this is good as workaround. > > Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c > =================================================================== > --- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c > +++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c > @@ -4278,6 +4278,7 @@ static int bcm43xx_resume(struct pci_dev > { > struct net_device *net_dev = pci_get_drvdata(pdev); > struct bcm43xx_private *bcm = bcm43xx_priv(net_dev); > + struct ieee80211softmac_device *mac = ieee80211_priv(net_dev); > int err = 0; > > dprintk(KERN_INFO PFX "Resuming...\n"); > @@ -4299,6 +4300,9 @@ static int bcm43xx_resume(struct pci_dev > } > netif_device_attach(net_dev); > > + if (mac->associnfo.associated) > + ieee80211softmac_try_reassoc(mac); > + > dprintk(KERN_INFO PFX "Device resumed.\n"); > > return 0; > Index: linux-2.6/include/net/ieee80211softmac.h > =================================================================== > --- linux-2.6.orig/include/net/ieee80211softmac.h > +++ linux-2.6/include/net/ieee80211softmac.h > @@ -254,6 +254,7 @@ struct ieee80211softmac_device { > }; > > extern void ieee80211softmac_scan_finished(struct ieee80211softmac_device *sm); > +extern void ieee80211softmac_try_reassoc(struct ieee80211softmac_device *mac); > > static inline void * ieee80211softmac_priv(struct net_device *dev) > { > Index: linux-2.6/net/ieee80211/softmac/ieee80211softmac_assoc.c > =================================================================== > --- linux-2.6.orig/net/ieee80211/softmac/ieee80211softmac_assoc.c > +++ linux-2.6/net/ieee80211/softmac/ieee80211softmac_assoc.c > @@ -441,6 +441,7 @@ ieee80211softmac_try_reassoc(struct ieee > schedule_delayed_work(&mac->associnfo.work, 0); > spin_unlock_irqrestore(&mac->lock, flags); > } > +EXPORT_SYMBOL_GPL(ieee80211softmac_try_reassoc); > > int > ieee80211softmac_handle_disassoc(struct net_device * dev, > - > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- Greetings Michael. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume @ 2007-02-10 17:11 ` Rafael J. Wysocki 0 siblings, 0 replies; 26+ messages in thread From: Rafael J. Wysocki @ 2007-02-10 17:11 UTC (permalink / raw) To: Larry Finger Cc: bcm43xx-dev, Michael Buesch, netdev, linux-wireless, John Linville On Friday, 9 February 2007 17:53, Michael Buesch wrote: > On Friday 09 February 2007 17:18, Larry Finger wrote: > > After a suspend/resume cycle, bcm43xx-softmac has lost its association with > > the AP and requires manual intervention. This situation is fixed by making > > one of softmac's internal routines public and calling it. > > > > Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net> > > Ack, this is good as workaround. I'm running with this patch applied right now, but the association is lost after the resume anyway. I have to reload bcm43xx to make it associate with the AP again (no big deal). Greetings, Rafael -- If you don't have the time to read, you don't have the time or the tools to write. - Stephen King ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume @ 2007-02-10 17:11 ` Rafael J. Wysocki 0 siblings, 0 replies; 26+ messages in thread From: Rafael J. Wysocki @ 2007-02-10 17:11 UTC (permalink / raw) To: Larry Finger Cc: bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w, Michael Buesch, netdev-u79uwXL29TY76Z2rM5mHXA, linux-wireless-u79uwXL29TY76Z2rM5mHXA, John Linville On Friday, 9 February 2007 17:53, Michael Buesch wrote: > On Friday 09 February 2007 17:18, Larry Finger wrote: > > After a suspend/resume cycle, bcm43xx-softmac has lost its association with > > the AP and requires manual intervention. This situation is fixed by making > > one of softmac's internal routines public and calling it. > > > > Signed-off-by: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org> > > Ack, this is good as workaround. I'm running with this patch applied right now, but the association is lost after the resume anyway. I have to reload bcm43xx to make it associate with the AP again (no big deal). Greetings, Rafael -- If you don't have the time to read, you don't have the time or the tools to write. - Stephen King - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-10 17:11 ` Rafael J. Wysocki (?) @ 2007-02-10 20:33 ` Larry Finger 2007-02-11 12:56 ` Rafael J. Wysocki -1 siblings, 1 reply; 26+ messages in thread From: Larry Finger @ 2007-02-10 20:33 UTC (permalink / raw) To: Rafael J. Wysocki Cc: bcm43xx-dev, Michael Buesch, wireless, linux-wireless, John Linville Rafael, Rafael J. Wysocki wrote: > > I'm running with this patch applied right now, but the association is lost > after the resume anyway. I have to reload bcm43xx to make it associate with > the AP again (no big deal). Please send me the output of iwconfig and ifconfig after the resume, but before you reload bcm43xx. Will the interface recover with any measure less drastic than reloading? Does an ifdown/ifup sequence do the trick? Thanks, Larry ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-10 20:33 ` Larry Finger @ 2007-02-11 12:56 ` Rafael J. Wysocki 2007-02-11 13:07 ` Michael Buesch 0 siblings, 1 reply; 26+ messages in thread From: Rafael J. Wysocki @ 2007-02-11 12:56 UTC (permalink / raw) To: Larry Finger; +Cc: bcm43xx-dev, Michael Buesch, wireless, John Linville On Saturday, 10 February 2007 21:33, Larry Finger wrote: > Rafael, > > Rafael J. Wysocki wrote: > > > > I'm running with this patch applied right now, but the association is lost > > after the resume anyway. I have to reload bcm43xx to make it associate with > > the AP again (no big deal). > > > Please send me the output of iwconfig and ifconfig after the resume, but before you reload bcm43xx. albercik:~ # iwconfig lo no wireless extensions. eth0 no wireless extensions. eth1 IEEE 802.11b/g ESSID:"DI524" Nickname:"Broadcom 4311" Mode:Managed Frequency=2.484 GHz Access Point: Invalid Bit Rate=1 Mb/s Tx-Power=18 dBm RTS thr:off Fragment thr:off Encryption key:off Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 albercik:~ # ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:14:A5:BE:95:31 inet addr:192.168.100.101 Bcast:192.168.100.255 Mask:255.255.255.0 inet6 addr: fe80::214:a5ff:febe:9531/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:5137 errors:0 dropped:120 overruns:0 frame:0 TX packets:5703 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4569090 (4.3 Mb) TX bytes:156826797 (149.5 Mb) Interrupt:18 albercik:~ # ifconfig eth1 down albercik:~ # ifconfig eth1 up SIOCSIFFLAGS: No such device Reloading the driver helps. ;-) Greetings, Rafael ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 12:56 ` Rafael J. Wysocki @ 2007-02-11 13:07 ` Michael Buesch 2007-02-11 14:02 ` Rafael J. Wysocki 0 siblings, 1 reply; 26+ messages in thread From: Michael Buesch @ 2007-02-11 13:07 UTC (permalink / raw) To: bcm43xx-dev; +Cc: Rafael J. Wysocki, Larry Finger, wireless, John Linville On Sunday 11 February 2007 13:56, Rafael J. Wysocki wrote: > On Saturday, 10 February 2007 21:33, Larry Finger wrote: > > Rafael, > > > > Rafael J. Wysocki wrote: > > > > > > I'm running with this patch applied right now, but the association is lost > > > after the resume anyway. I have to reload bcm43xx to make it associate with > > > the AP again (no big deal). > > > > > > Please send me the output of iwconfig and ifconfig after the resume, but before you reload bcm43xx. > > albercik:~ # iwconfig > lo no wireless extensions. > > eth0 no wireless extensions. > > eth1 IEEE 802.11b/g ESSID:"DI524" Nickname:"Broadcom 4311" > Mode:Managed Frequency=2.484 GHz Access Point: Invalid > Bit Rate=1 Mb/s Tx-Power=18 dBm > RTS thr:off Fragment thr:off > Encryption key:off > Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > albercik:~ # ifconfig eth1 > eth1 Link encap:Ethernet HWaddr 00:14:A5:BE:95:31 > inet addr:192.168.100.101 Bcast:192.168.100.255 Mask:255.255.255.0 > inet6 addr: fe80::214:a5ff:febe:9531/64 Scope:Link > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:5137 errors:0 dropped:120 overruns:0 frame:0 > TX packets:5703 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:4569090 (4.3 Mb) TX bytes:156826797 (149.5 Mb) > Interrupt:18 > > albercik:~ # ifconfig eth1 down > albercik:~ # ifconfig eth1 up > SIOCSIFFLAGS: No such device ^^^^^ I'd like to see dmesg, please. -- Greetings Michael. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 13:07 ` Michael Buesch @ 2007-02-11 14:02 ` Rafael J. Wysocki 2007-02-11 14:14 ` Michael Buesch 0 siblings, 1 reply; 26+ messages in thread From: Rafael J. Wysocki @ 2007-02-11 14:02 UTC (permalink / raw) To: Michael Buesch; +Cc: bcm43xx-dev, Larry Finger, wireless, John Linville On Sunday, 11 February 2007 14:07, Michael Buesch wrote: > On Sunday 11 February 2007 13:56, Rafael J. Wysocki wrote: > > On Saturday, 10 February 2007 21:33, Larry Finger wrote: > > > Rafael, > > > > > > Rafael J. Wysocki wrote: > > > > > > > > I'm running with this patch applied right now, but the association is lost > > > > after the resume anyway. I have to reload bcm43xx to make it associate with > > > > the AP again (no big deal). > > > > > > > > > Please send me the output of iwconfig and ifconfig after the resume, but before you reload bcm43xx. > > > > albercik:~ # iwconfig > > lo no wireless extensions. > > > > eth0 no wireless extensions. > > > > eth1 IEEE 802.11b/g ESSID:"DI524" Nickname:"Broadcom 4311" > > Mode:Managed Frequency=2.484 GHz Access Point: Invalid > > Bit Rate=1 Mb/s Tx-Power=18 dBm > > RTS thr:off Fragment thr:off > > Encryption key:off > > Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > albercik:~ # ifconfig eth1 > > eth1 Link encap:Ethernet HWaddr 00:14:A5:BE:95:31 > > inet addr:192.168.100.101 Bcast:192.168.100.255 Mask:255.255.255.0 > > inet6 addr: fe80::214:a5ff:febe:9531/64 Scope:Link > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:5137 errors:0 dropped:120 overruns:0 frame:0 > > TX packets:5703 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:4569090 (4.3 Mb) TX bytes:156826797 (149.5 Mb) > > Interrupt:18 > > > > albercik:~ # ifconfig eth1 down > > albercik:~ # ifconfig eth1 up > > SIOCSIFFLAGS: No such device > ^^^^^ > > I'd like to see dmesg, please. Appended. It covers one suspend-resume cycle (suspend to disk). I have filtered HID-related messages out of it. Greetings, Rafael ton.000e = 0 usb 3-1: usb auto-resume ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS PES CCS usb 3-1: finish resume usb usb1: usb auto-resume usb usb1: finish resume hub 1-0:1.0: hub_resume ehci_hcd 0000:00:13.2: resume root hub hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0000 usb 3-1: usb auto-suspend hub 1-0:1.0: hub_suspend usb usb1: usb auto-suspend PM: Adding info for No Bus:vcs8 PM: Adding info for No Bus:vcsa8 SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 Stopping tasks ... done. Shrinking memory... \b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\bdone (113015 pages freed) Freed 452060 kbytes in 1.44 seconds (313.93 MB/s) Suspending console(s) usbhid 3-4:1.0: freeze usb 3-4: freeze usbhid 3-4:1.0: suspend usb 3-4: usb suspend usbdev3.18: PM: suspend 0->1, parent 3-1 already 2 usbdev3.18_ep02: PM: suspend 0->1, parent 3-1:1.0 already 2 usbdev3.18_ep81: PM: suspend 0->1, parent 3-1:1.0 already 2 usb 3-1:1.0: PM: suspend 2-->1 usb 3-1:1.0: PM: suspend 2->1, parent 3-1 already 2 usbdev3.18_ep00: PM: suspend 0->1, parent 3-1 already 2 usb 3-1: PM: suspend 2-->1 usb 2-2:1.3: freeze usb 2-2:1.2: freeze hci_usb 2-2:1.1: freeze hci_usb 2-2:1.0: freeze usb 2-2: freeze usb 2-2: usb suspend serio serio6: freeze platform bluetooth: freeze hub 3-0:1.0: freeze usb usb3: freeze hub 3-0:1.0: hub_suspend ohci_hcd 0000:00:13.1: suspend root hub usb usb3: usb suspend hub 2-0:1.0: freeze usb usb2: freeze hub 2-0:1.0: hub_suspend ohci_hcd 0000:00:13.0: suspend root hub usb usb2: usb suspend usbdev1.1: PM: suspend 0->1, parent usb1 already 2 usbdev1.1_ep81: PM: suspend 0->1, parent 1-0:1.0 already 2 hub 1-0:1.0: PM: suspend 2-->1 hub 1-0:1.0: PM: suspend 2->1, parent usb1 already 2 usbdev1.1_ep00: PM: suspend 0->1, parent usb1 already 2 usb usb1: PM: suspend 2-->1 ide-cdrom 0.0: freeze psmouse serio4: freeze serio serio3: freeze serio serio2: freeze serio serio1: freeze atkbd serio0: freeze i8042 i8042: freeze sd 0:0:0:0: freeze serial8250 serial8250: freeze vesafb vesafb.0: freeze pci_express 0000:00:06.0:pcie03: freeze pci_express 0000:00:06.0:pcie01: freeze pci_express 0000:00:06.0:pcie00: freeze pci_express 0000:00:05.0:pcie03: freeze pci_express 0000:00:05.0:pcie01: freeze pci_express 0000:00:05.0:pcie00: freeze pci_express 0000:00:04.0:pcie03: freeze pci_express 0000:00:04.0:pcie01: freeze pci_express 0000:00:04.0:pcie00: freeze pcspkr pcspkr: freeze sdhci 0000:02:04.3: freeze ACPI: PCI interrupt for device 0000:02:04.3 disabled tifm_7xx1 0000:02:04.2: freeze ACPI: PCI interrupt for device 0000:02:04.2 disabled ohci1394 0000:02:04.1: freeze ohci1394 does not fully support suspend and resume yet ieee1394: hpsb_bus_reset called while bus reset already in progress yenta_cardbus 0000:02:04.0: freeze tg3 0000:02:01.0: freeze PM: Writing back config space on device 0000:02:01.0 at offset b (was 3ed173b, writing 30b0103c) PM: Writing back config space on device 0000:02:01.0 at offset 3 (was 0, writing 4010) PM: Writing back config space on device 0000:02:01.0 at offset 2 (was 2000000, writing 2000003) PM: Writing back config space on device 0000:02:01.0 at offset 1 (was 2b00000, writing 2b00006) PM: Writing back config space on device 0000:02:01.0 at offset 0 (was 3ed173b, writing 169c14e4) bcm43xx 0000:30:00.0: freeze bcm43xx: Suspending... PM: Removing info for No Bus:hw_random bcm43xx: Radio turned off bcm43xx: DMA-32 0x0200 (RX) max used slots: 3/64 bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0220 (TX) max used slots: 3/512 bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512 ACPI: PCI interrupt for device 0000:30:00.0 disabled bcm43xx: Device suspended. pci 0000:01:05.0: freeze k8temp 0000:00:18.3: freeze pci 0000:00:18.2: freeze pci 0000:00:18.1: freeze pci 0000:00:18.0: freeze pci 0000:00:14.4: freeze pci 0000:00:14.3: freeze HDA Intel 0000:00:14.2: freeze ACPI: PCI interrupt for device 0000:00:14.2 disabled ATIIXP_IDE 0000:00:14.1: freeze piix4_smbus 0000:00:14.0: freeze ehci_hcd 0000:00:13.2: freeze ACPI: PCI interrupt for device 0000:00:13.2 disabled ehci_hcd 0000:00:13.2: --> PCI D3 ohci_hcd 0000:00:13.1: freeze ACPI: PCI interrupt for device 0000:00:13.1 disabled ohci_hcd 0000:00:13.1: --> PCI D0/legacy ohci_hcd 0000:00:13.0: freeze ACPI: PCI interrupt for device 0000:00:13.0 disabled ohci_hcd 0000:00:13.0: --> PCI D0/legacy sata_sil 0000:00:12.0: freeze pcieport-driver 0000:00:06.0: freeze pcieport-driver 0000:00:05.0: freeze pcieport-driver 0000:00:04.0: freeze pci 0000:00:01.0: freeze pci 0000:00:00.0: freeze ACPI Thermal Zone Driver thermal:03: freeze ACPI Thermal Zone Driver thermal:02: freeze ACPI Thermal Zone Driver thermal:01: freeze ACPI Fan Driver PNP0C0B:03: freeze ACPI Fan Driver PNP0C0B:02: freeze ACPI: Transitioning device [C351] to D0 ACPI: Transitioning device [C351] to D0 ACPI Fan Driver PNP0C0B:01: freeze ACPI: Transitioning device [C350] to D0 ACPI: Transitioning device [C350] to D0 ACPI Fan Driver PNP0C0B:00: freeze ACPI: Transitioning device [C34F] to D0 ACPI: Transitioning device [C34F] to D0 ACPI Power Resource Driver power_resource:06: freeze ACPI Power Resource Driver power_resource:05: freeze ACPI Power Resource Driver power_resource:04: freeze ACPI Power Resource Driver power_resource:03: freeze acpi thermal:00: freeze acpi PNP0C02:02: freeze acpi PNP0C14:00: freeze ACPI Button Driver PNP0C0D:00: freeze ACPI Button Driver PNP0C0E:00: freeze ACPI AC Adapter Driver ACPI0003:00: freeze ACPI Battery Driver PNP0C0A:01: freeze ACPI Battery Driver PNP0C0A:00: freeze acpi HPQ0006:00: freeze acpi PNP0C02:01: freeze acpi device:49: freeze acpi device:48: freeze acpi device:47: freeze acpi device:46: freeze acpi device:45: freeze acpi device:44: freeze acpi device:43: freeze acpi device:42: freeze acpi device:41: freeze acpi device:40: freeze acpi device:3f: freeze acpi device:3e: freeze acpi device:3d: freeze acpi device:3c: freeze acpi device:3b: freeze acpi device:3a: freeze acpi device:39: freeze acpi device:38: freeze acpi device:37: freeze acpi device:36: freeze acpi device:35: freeze acpi device:34: freeze acpi device:33: freeze ACPI PCI Interrupt Link Driver PNP0C0F:07: freeze ACPI PCI Interrupt Link Driver PNP0C0F:06: freeze ACPI PCI Interrupt Link Driver PNP0C0F:05: freeze ACPI PCI Interrupt Link Driver PNP0C0F:04: freeze ACPI PCI Interrupt Link Driver PNP0C0F:03: freeze ACPI PCI Interrupt Link Driver PNP0C0F:02: freeze ACPI PCI Interrupt Link Driver PNP0C0F:01: freeze ACPI PCI Interrupt Link Driver PNP0C0F:00: freeze acpi device:32: freeze acpi device:31: freeze acpi device:30: freeze acpi device:2f: freeze acpi device:2e: freeze acpi device:2d: freeze acpi device:2c: freeze acpi device:2b: freeze acpi device:2a: freeze acpi device:29: freeze acpi device:28: freeze acpi device:27: freeze acpi device:26: freeze acpi device:25: freeze acpi device:24: freeze acpi device:23: freeze acpi device:22: freeze acpi device:21: freeze acpi device:20: freeze acpi device:1f: freeze acpi device:1e: freeze acpi device:1d: freeze acpi device:1c: freeze acpi device:1b: freeze acpi device:1a: freeze acpi device:19: freeze acpi device:18: freeze acpi device:17: freeze acpi device:16: freeze acpi device:15: freeze acpi device:14: freeze acpi device:13: freeze acpi device:12: freeze acpi device:11: freeze acpi device:10: freeze acpi PNP0C02:00: freeze acpi PNP0000:00: freeze ACPI Power Resource Driver power_resource:02: freeze acpi SYN0118:00: freeze acpi PNP0303:00: freeze acpi PNP0B00:00: freeze acpi PNP0800:00: freeze acpi PNP0200:00: freeze acpi PNP0100:00: freeze acpi PNP0C04:00: freeze acpi IFX0102:00: freeze ACPI Power Resource Driver power_resource:01: freeze acpi PNP0401:00: freeze ACPI container driver PNP0A06:00: freeze ACPI Embedded Controller Driver PNP0C09:00: freeze acpi device:0f: freeze acpi device:0e: freeze ACPI Power Resource Driver power_resource:00: freeze acpi device:0d: freeze acpi device:0c: freeze acpi device:0b: freeze acpi device:0a: freeze acpi device:09: freeze acpi device:08: freeze acpi device:07: freeze acpi device:06: freeze acpi device:05: freeze acpi device:04: freeze acpi device:03: freeze acpi device:02: freeze acpi video:00: freeze acpi device:01: freeze ACPI PCI Root Bridge Driver PNP0A03:00: freeze acpi PNP0C01:00: freeze acpi device:00: freeze ACPI Processor Driver ACPI0007:01: freeze ACPI Processor Driver ACPI0007:00: freeze ACPI Button Driver button_power:00: freeze acpi acpi_system:00: freeze Disabling non-boot CPUs ... CPU 1 is now offline SMP alternatives: switching to UP code CPU1 is down platform bluetooth: LATE freeze i8042 i8042: LATE freeze serial8250 serial8250: LATE freeze vesafb vesafb.0: LATE freeze pcspkr pcspkr: LATE freeze sdhci 0000:02:04.3: LATE freeze tifm_7xx1 0000:02:04.2: LATE freeze ohci1394 0000:02:04.1: LATE freeze yenta_cardbus 0000:02:04.0: LATE freeze tg3 0000:02:01.0: LATE freeze bcm43xx 0000:30:00.0: LATE freeze pci 0000:01:05.0: LATE freeze k8temp 0000:00:18.3: LATE freeze pci 0000:00:18.2: LATE freeze pci 0000:00:18.1: LATE freeze pci 0000:00:18.0: LATE freeze pci 0000:00:14.4: LATE freeze pci 0000:00:14.3: LATE freeze HDA Intel 0000:00:14.2: LATE freeze ATIIXP_IDE 0000:00:14.1: LATE freeze piix4_smbus 0000:00:14.0: LATE freeze pcieport-driver 0000:00:06.0: LATE freeze pcieport-driver 0000:00:05.0: LATE freeze pcieport-driver 0000:00:04.0: LATE freeze pci 0000:00:01.0: LATE freeze pci 0000:00:00.0: LATE freeze Extended CMOS year: 2000 swsusp: critical section: swsusp: Need to copy 95157 pages swsusp: Normal pages needed: 95157 + 1024 + 20, available pages: 134073 Extended CMOS year: 2000 pci 0000:00:00.0: EARLY resume pci 0000:00:01.0: EARLY resume pcieport-driver 0000:00:04.0: EARLY resume pcieport-driver 0000:00:05.0: EARLY resume pcieport-driver 0000:00:06.0: EARLY resume sata_sil 0000:00:12.0: EARLY resume ohci_hcd 0000:00:13.0: EARLY resume ohci_hcd 0000:00:13.1: EARLY resume ehci_hcd 0000:00:13.2: EARLY resume piix4_smbus 0000:00:14.0: EARLY resume ATIIXP_IDE 0000:00:14.1: EARLY resume HDA Intel 0000:00:14.2: EARLY resume pci 0000:00:14.3: EARLY resume pci 0000:00:14.4: EARLY resume pci 0000:00:18.0: EARLY resume pci 0000:00:18.1: EARLY resume pci 0000:00:18.2: EARLY resume k8temp 0000:00:18.3: EARLY resume pci 0000:01:05.0: EARLY resume bcm43xx 0000:30:00.0: EARLY resume tg3 0000:02:01.0: EARLY resume yenta_cardbus 0000:02:04.0: EARLY resume ohci1394 0000:02:04.1: EARLY resume tifm_7xx1 0000:02:04.2: EARLY resume sdhci 0000:02:04.3: EARLY resume pcspkr pcspkr: EARLY resume vesafb vesafb.0: EARLY resume serial8250 serial8250: EARLY resume i8042 i8042: EARLY resume platform bluetooth: EARLY resume Enabling non-boot CPUs ... SMP alternatives: switching to SMP code Booting processor 1/2 APIC 0x1 Initializing CPU#1 Calibrating delay using timer specific routine.. 3990.23 BogoMIPS (lpj=7980462) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: Physical Processor ID: 0 CPU: Processor Core ID: 1 AMD Turion(tm) 64 X2 Mobile Technology TL-60 stepping 02 CPU 1: Syncing TSC to CPU 0. CPU 1: synchronized TSC with CPU 0 (last diff 0 cycles, maxerr 510 cycles) powernow-k8: 0 : fid 0xc (2000 MHz), vid 0x13 powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x15 powernow-k8: 2 : fid 0x8 (1600 MHz), vid 0x17 powernow-k8: 3 : fid 0x0 (800 MHz), vid 0x1e CPU1 is up acpi acpi_system:00: resuming ACPI Button Driver button_power:00: resuming ACPI Processor Driver ACPI0007:00: resuming ACPI Processor Driver ACPI0007:01: resuming acpi device:00: resuming acpi PNP0C01:00: resuming ACPI PCI Root Bridge Driver PNP0A03:00: resuming acpi device:01: resuming acpi video:00: resuming acpi device:02: resuming acpi device:03: resuming acpi device:04: resuming acpi device:05: resuming acpi device:06: resuming acpi device:07: resuming acpi device:08: resuming acpi device:09: resuming acpi device:0a: resuming acpi device:0b: resuming acpi device:0c: resuming acpi device:0d: resuming ACPI Power Resource Driver power_resource:00: resuming acpi device:0e: resuming acpi device:0f: resuming ACPI Embedded Controller Driver PNP0C09:00: resuming ACPI container driver PNP0A06:00: resuming acpi PNP0401:00: resuming ACPI Power Resource Driver power_resource:01: resuming acpi IFX0102:00: resuming acpi PNP0C04:00: resuming acpi PNP0100:00: resuming acpi PNP0200:00: resuming acpi PNP0800:00: resuming acpi PNP0B00:00: resuming acpi PNP0303:00: resuming acpi SYN0118:00: resuming ACPI Power Resource Driver power_resource:02: resuming acpi PNP0000:00: resuming acpi PNP0C02:00: resuming acpi device:10: resuming acpi device:11: resuming acpi device:12: resuming acpi device:13: resuming acpi device:14: resuming acpi device:15: resuming acpi device:16: resuming acpi device:17: resuming acpi device:18: resuming acpi device:19: resuming acpi device:1a: resuming acpi device:1b: resuming acpi device:1c: resuming acpi device:1d: resuming acpi device:1e: resuming acpi device:1f: resuming acpi device:20: resuming acpi device:21: resuming acpi device:22: resuming acpi device:23: resuming acpi device:24: resuming acpi device:25: resuming acpi device:26: resuming acpi device:27: resuming acpi device:28: resuming acpi device:29: resuming acpi device:2a: resuming acpi device:2b: resuming acpi device:2c: resuming acpi device:2d: resuming acpi device:2e: resuming acpi device:2f: resuming acpi device:30: resuming acpi device:31: resuming acpi device:32: resuming ACPI PCI Interrupt Link Driver PNP0C0F:00: resuming ACPI PCI Interrupt Link Driver PNP0C0F:01: resuming ACPI PCI Interrupt Link Driver PNP0C0F:02: resuming ACPI PCI Interrupt Link Driver PNP0C0F:03: resuming ACPI PCI Interrupt Link Driver PNP0C0F:04: resuming ACPI PCI Interrupt Link Driver PNP0C0F:05: resuming ACPI PCI Interrupt Link Driver PNP0C0F:06: resuming ACPI PCI Interrupt Link Driver PNP0C0F:07: resuming acpi device:33: resuming acpi device:34: resuming acpi device:35: resuming acpi device:36: resuming acpi device:37: resuming acpi device:38: resuming acpi device:39: resuming acpi device:3a: resuming acpi device:3b: resuming acpi device:3c: resuming acpi device:3d: resuming acpi device:3e: resuming acpi device:3f: resuming acpi device:40: resuming acpi device:41: resuming acpi device:42: resuming acpi device:43: resuming acpi device:44: resuming acpi device:45: resuming acpi device:46: resuming acpi device:47: resuming acpi device:48: resuming acpi device:49: resuming acpi PNP0C02:01: resuming acpi HPQ0006:00: resuming ACPI Battery Driver PNP0C0A:00: resuming ACPI Battery Driver PNP0C0A:01: resuming ACPI AC Adapter Driver ACPI0003:00: resuming ACPI Button Driver PNP0C0E:00: resuming ACPI Button Driver PNP0C0D:00: resuming acpi PNP0C14:00: resuming acpi PNP0C02:02: resuming acpi thermal:00: resuming ACPI Power Resource Driver power_resource:03: resuming ACPI Power Resource Driver power_resource:04: resuming ACPI Power Resource Driver power_resource:05: resuming ACPI Power Resource Driver power_resource:06: resuming ACPI Fan Driver PNP0C0B:00: resuming ACPI: Transitioning device [C34F] to D0 ACPI: Transitioning device [C34F] to D0 ACPI Fan Driver PNP0C0B:01: resuming ACPI: Transitioning device [C350] to D0 ACPI: Transitioning device [C350] to D0 ACPI Fan Driver PNP0C0B:02: resuming ACPI: Transitioning device [C351] to D0 ACPI: Transitioning device [C351] to D0 ACPI Fan Driver PNP0C0B:03: resuming ACPI Thermal Zone Driver thermal:01: resuming ACPI Thermal Zone Driver thermal:02: resuming ACPI Thermal Zone Driver thermal:03: resuming pci 0000:00:00.0: resuming pci 0000:00:01.0: resuming pcieport-driver 0000:00:04.0: resuming PCI: Setting latency timer of device 0000:00:04.0 to 64 pcieport-driver 0000:00:05.0: resuming PCI: Setting latency timer of device 0000:00:05.0 to 64 pcieport-driver 0000:00:06.0: resuming PCI: Setting latency timer of device 0000:00:06.0 to 64 sata_sil 0000:00:12.0: resuming ohci_hcd 0000:00:13.0: resuming ohci_hcd 0000:00:13.0: PCI legacy resume ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 19 (level, low) -> IRQ 19 ohci_hcd 0000:00:13.1: resuming ohci_hcd 0000:00:13.1: PCI legacy resume ACPI: PCI Interrupt 0000:00:13.1[A] -> GSI 19 (level, low) -> IRQ 19 ehci_hcd 0000:00:13.2: resuming ehci_hcd 0000:00:13.2: PCI D0, from previous PCI D3 ACPI: PCI Interrupt 0000:00:13.2[A] -> GSI 19 (level, low) -> IRQ 19 PM: Writing back config space on device 0000:00:13.2 at offset 1 (was 2b00007, writing 2b00017) ehci_hcd 0000:00:13.2: lost power, restarting usb usb1: root hub lost power or was reset ehci_hcd 0000:00:13.2: reset command 080002 (park)=0 ithresh=8 period=1024 Reset HALT ehci_hcd 0000:00:13.2: MWI active piix4_smbus 0000:00:14.0: resuming ATIIXP_IDE 0000:00:14.1: resuming ACPI: PCI Interrupt 0000:00:14.1[A] -> GSI 16 (level, low) -> IRQ 16 HDA Intel 0000:00:14.2: resuming PM: Writing back config space on device 0000:00:14.2 at offset f (was 10a, writing a) PM: Writing back config space on device 0000:00:14.2 at offset 1 (was 4100006, writing 4100002) ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 16 pci 0000:00:14.3: resuming pci 0000:00:14.4: resuming PM: Writing back config space on device 0000:00:14.4 at offset 6 (was 40030200, writing 40060200) pci 0000:00:18.0: resuming pci 0000:00:18.1: resuming pci 0000:00:18.2: resuming k8temp 0000:00:18.3: resuming pci 0000:01:05.0: resuming bcm43xx 0000:30:00.0: resuming bcm43xx: Resuming... ACPI: PCI Interrupt 0000:30:00.0[A] -> GSI 18 (level, low) -> IRQ 18 bcm43xx: PHY connected bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) bcm43xx: Radio turned on bcm43xx: Radio enabled by hardware ata2: SATA link down (SStatus 0 SControl 300) bcm43xx: Chip initialized bcm43xx: 32-bit DMA initialized bcm43xx: Keys cleared bcm43xx: Selected 802.11 core (phytype 2) PM: Adding info for No Bus:hw_random bcm43xx: Device resumed. tg3 0000:02:01.0: resuming PM: Writing back config space on device 0000:02:01.0 at offset b (was 3ed173b, writing 30b0103c) PM: Writing back config space on device 0000:02:01.0 at offset 3 (was 0, writing 4010) PM: Writing back config space on device 0000:02:01.0 at offset 2 (was 2000000, writing 2000003) PM: Writing back config space on device 0000:02:01.0 at offset 1 (was 2b00000, writing 2b00006) PM: Writing back config space on device 0000:02:01.0 at offset 0 (was 3ed173b, writing 169c14e4) SoftMAC: Associate: Scanning for networks first. yenta_cardbus 0000:02:04.0: resuming PM: Writing back config space on device 0000:02:04.0 at offset f (was 3c4010a, writing 5c0010a) PM: Writing back config space on device 0000:02:04.0 at offset 3 (was 824010, writing 82a810) ohci1394 0000:02:04.1: resuming ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[20] MMIO=[d4011000-d40117ff] Max Packet=[2048] IR/IT contexts=[4/8] tifm_7xx1 0000:02:04.2: resuming ACPI: PCI Interrupt 0000:02:04.2[A] -> GSI 20 (level, low) -> IRQ 20 sdhci 0000:02:04.3: resuming ACPI: PCI Interrupt 0000:02:04.3[A] -> GSI 20 (level, low) -> IRQ 20 pcspkr pcspkr: resuming pci_express 0000:00:04.0:pcie00: resuming pci_express 0000:00:04.0:pcie01: resuming pci_express 0000:00:04.0:pcie03: resuming pci_express 0000:00:05.0:pcie00: resuming pci_express 0000:00:05.0:pcie01: resuming pci_express 0000:00:05.0:pcie03: resuming pci_express 0000:00:06.0:pcie00: resuming pci_express 0000:00:06.0:pcie01: resuming pci_express 0000:00:06.0:pcie03: resuming vesafb vesafb.0: resuming serial8250 serial8250: resuming sd 0:0:0:0: resuming i8042 i8042: resuming atkbd serio0: resuming serio serio1: resuming serio serio2: resuming serio serio3: resuming psmouse serio4: resuming synaptics reset failed synaptics reset failed synaptics reset failed SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 ide-cdrom 0.0: resuming usb usb1: resuming usb usb1: usb resume usb usb1: finish resume hub 1-0:1.0: hub_resume ehci_hcd 0000:00:13.2: resume root hub after power loss usb usb2: resuming usb usb2: usb resume usb usb2: finish resume hub 2-0:1.0: hub_resume ohci_hcd 0000:00:13.0: BIOS/SMM active, control 008 usb usb2: root hub lost power or was reset ohci_hcd 0000:00:13.0: resetting from state 'reset', control = 0x8 ohci_hcd 0000:00:13.0: OHCI controller state ohci_hcd 0000:00:13.0: OHCI 1.0, NO legacy support registers ohci_hcd 0000:00:13.0: control 0x083 HCFS=operational CBSR=3 ohci_hcd 0000:00:13.0: cmdstatus 0x00000 SOC=0 ohci_hcd 0000:00:13.0: intrstatus 0x00000004 SF ohci_hcd 0000:00:13.0: intrenable 0x8000005a MIE RHSC UE RD WDH ohci_hcd 0000:00:13.0: hcca frame #0005 ohci_hcd 0000:00:13.0: roothub.a 02000204 POTPGT=2 NPS NDP=4(4) ohci_hcd 0000:00:13.0: roothub.b 00000000 PPCM=0000 DR=0000 ohci_hcd 0000:00:13.0: roothub.status 00008000 DRWE ohci_hcd 0000:00:13.0: roothub.portstatus [0] 0x00000100 PPS ohci_hcd 0000:00:13.0: roothub.portstatus [1] 0x00010100 CSC PPS ohci_hcd 0000:00:13.0: roothub.portstatus [2] 0x00000100 PPS ohci_hcd 0000:00:13.0: roothub.portstatus [3] 0x00000100 PPS ohci_hcd 0000:00:13.0: restart complete hub 2-0:1.0: resuming usb usb3: resuming usb usb3: usb resume usb usb3: finish resume hub 3-0:1.0: hub_resume ohci_hcd 0000:00:13.1: BIOS/SMM active, control 008 usb usb3: root hub lost power or was reset ohci_hcd 0000:00:13.1: resetting from state 'reset', control = 0x8 ohci_hcd 0000:00:13.1: OHCI controller state ohci_hcd 0000:00:13.1: OHCI 1.0, NO legacy support registers ohci_hcd 0000:00:13.1: control 0x083 HCFS=operational CBSR=3 ohci_hcd 0000:00:13.1: cmdstatus 0x00000 SOC=0 ohci_hcd 0000:00:13.1: intrstatus 0x00000004 SF ohci_hcd 0000:00:13.1: intrenable 0x8000005a MIE RHSC UE RD WDH ohci_hcd 0000:00:13.1: hcca frame #0005 ohci_hcd 0000:00:13.1: roothub.a 02000204 POTPGT=2 NPS NDP=4(4) ohci_hcd 0000:00:13.1: roothub.b 00000000 PPCM=0000 DR=0000 ohci_hcd 0000:00:13.1: roothub.status 00008000 DRWE ohci_hcd 0000:00:13.1: roothub.portstatus [0] 0x00010100 CSC PPS ohci_hcd 0000:00:13.1: roothub.portstatus [1] 0x00000100 PPS ohci_hcd 0000:00:13.1: roothub.portstatus [2] 0x00000100 PPS ohci_hcd 0000:00:13.1: roothub.portstatus [3] 0x00010100 CSC PPS ohci_hcd 0000:00:13.1: restart complete hub 3-0:1.0: resuming platform bluetooth: resuming serio serio6: resuming usb 2-2: resuming usbdev2.10_ep00: PM: resume from 0, parent 2-2 still 1 hci_usb 2-2:1.0: PM: resume from 1, parent 2-2 still 1 hci_usb 2-2:1.0: resuming hci0: PM: resume from 0, parent 2-2:1.0 still 1 usbdev2.10_ep81: PM: resume from 0, parent 2-2:1.0 still 1 usbdev2.10_ep82: PM: resume from 0, parent 2-2:1.0 still 1 usbdev2.10_ep02: PM: resume from 0, parent 2-2:1.0 still 1 hci_usb 2-2:1.1: PM: resume from 1, parent 2-2 still 1 hci_usb 2-2:1.1: resuming usbdev2.10_ep83: PM: resume from 0, parent 2-2:1.1 still 1 usbdev2.10_ep03: PM: resume from 0, parent 2-2:1.1 still 1 usb 2-2:1.2: PM: resume from 1, parent 2-2 still 1 usb 2-2:1.2: resuming usbdev2.10_ep84: PM: resume from 0, parent 2-2:1.2 still 1 usbdev2.10_ep04: PM: resume from 0, parent 2-2:1.2 still 1 usb 2-2:1.3: PM: resume from 1, parent 2-2 still 1 usb 2-2:1.3: resuming usbdev2.10: PM: resume from 0, parent 2-2 still 1 usbdev3.18_ep00: PM: resume from 0, parent 3-1 still 2 usbdev3.18_ep81: PM: resume from 0, parent 3-1:1.0 still 2 usbdev3.18_ep02: PM: resume from 0, parent 3-1:1.0 still 2 usbdev3.18: PM: resume from 0, parent 3-1 still 2 usb 3-4: resuming usbdev3.19_ep00: PM: resume from 0, parent 3-4 still 1 usbhid 3-4:1.0: PM: resume from 1, parent 3-4 still 1 usbhid 3-4:1.0: resuming usbdev3.19_ep81: PM: resume from 0, parent 3-4:1.0 still 1 usbdev3.19: PM: resume from 0, parent 3-4 still 1 Restarting tasks ... <7>hub 2-0:1.0: state 7 ports 4 chg 0004 evt 001e ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s done. PM: Removing info for No Bus:vcs8 PM: Removing info for No Bus:vcsa8 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/100 SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00010100 CSC PPS hub 2-0:1.0: port 2, status 0100, change 0001, 12 Mb/s usb 2-2: USB disconnect, address 10 usb 2-2: unregistering device usb 2-2: usb_disable_device nuking all URBs usb 2-2: unregistering interface 2-2:1.0 PM: Removing info for No Bus:usbdev2.10_ep81 usbdev2.10_ep81: ep_device_release called for usbdev2.10_ep81 PM: Removing info for No Bus:usbdev2.10_ep82 usbdev2.10_ep82: ep_device_release called for usbdev2.10_ep82 PM: Removing info for No Bus:usbdev2.10_ep02 usbdev2.10_ep02: ep_device_release called for usbdev2.10_ep02 PM: Removing info for No Bus:hci0 PM: Removing info for usb:2-2:1.0 usb 2-2:1.0: uevent usb 2-2: unregistering interface 2-2:1.1 PM: Removing info for No Bus:usbdev2.10_ep83 usbdev2.10_ep83: ep_device_release called for usbdev2.10_ep83 PM: Removing info for No Bus:usbdev2.10_ep03 usbdev2.10_ep03: ep_device_release called for usbdev2.10_ep03 PM: Removing info for usb:2-2:1.1 usb 2-2:1.1: uevent usb 2-2: unregistering interface 2-2:1.2 PM: Removing info for No Bus:usbdev2.10_ep84 usbdev2.10_ep84: ep_device_release called for usbdev2.10_ep84 PM: Removing info for No Bus:usbdev2.10_ep04 usbdev2.10_ep04: ep_device_release called for usbdev2.10_ep04 PM: Removing info for usb:2-2:1.2 usb 2-2:1.2: uevent usb 2-2: unregistering interface 2-2:1.3 PM: Removing info for usb:2-2:1.3 usb 2-2:1.3: uevent PM: Removing info for No Bus:usbdev2.10 PM: Removing info for No Bus:usbdev2.10_ep00 usbdev2.10_ep00: ep_device_release called for usbdev2.10_ep00 PM: Removing info for usb:2-2 usb 2-2: uevent SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x100 ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [2] = 0x00010100 CSC PPS hub 2-0:1.0: port 3, status 0100, change 0001, 12 Mb/s hub 2-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x100 ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [3] = 0x00010100 CSC PPS hub 2-0:1.0: port 4, status 0100, change 0001, 12 Mb/s hub 2-0:1.0: debounce: port 4: total 100ms stable 100ms status 0x100 hub 3-0:1.0: state 7 ports 4 chg 0012 evt 001e ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS hub 3-0:1.0: port 1, status 0100, change 0001, 12 Mb/s usb 3-1: USB disconnect, address 18 usb 3-1: unregistering device usb 3-1: usb_disable_device nuking all URBs usb 3-1: unregistering interface 3-1:1.0 PM: Removing info for No Bus:usbdev3.18_ep81 usbdev3.18_ep81: ep_device_release called for usbdev3.18_ep81 PM: Removing info for No Bus:usbdev3.18_ep02 usbdev3.18_ep02: ep_device_release called for usbdev3.18_ep02 PM: Removing info for usb:3-1:1.0 usb 3-1:1.0: uevent PM: Removing info for No Bus:usbdev3.18 PM: Removing info for No Bus:usbdev3.18_ep00 usbdev3.18_ep00: ep_device_release called for usbdev3.18_ep00 PM: Removing info for usb:3-1 usb 3-1: uevent hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [1] = 0x00010100 CSC PPS hub 3-0:1.0: port 2, status 0100, change 0001, 12 Mb/s hub 3-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x100 ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [2] = 0x00010100 CSC PPS hub 3-0:1.0: port 3, status 0100, change 0001, 12 Mb/s hub 3-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x100 ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [3] = 0x00010100 CSC PPS hub 3-0:1.0: port 4, status 0100, change 0001, 12 Mb/s usb 3-4: USB disconnect, address 19 usb 3-4: unregistering device usb 3-4: usb_disable_device nuking all URBs usb 3-4: unregistering interface 3-4:1.0 PM: Removing info for No Bus:usbdev3.19_ep81 usbdev3.19_ep81: ep_device_release called for usbdev3.19_ep81 PM: Removing info for usb:3-4:1.0 usb 3-4:1.0: uevent PM: Removing info for No Bus:usbdev3.19 PM: Removing info for No Bus:usbdev3.19_ep00 usbdev3.19_ep00: ep_device_release called for usbdev3.19_ep00 PM: Removing info for usb:3-4 usb 3-4: uevent hub 3-0:1.0: debounce: port 4: total 100ms stable 100ms status 0x100 hub 1-0:1.0: state 7 ports 8 chg 0000 evt 010c ehci_hcd 0000:00:13.2: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT hub 1-0:1.0: port 2, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501 ehci_hcd 0000:00:13.2: port 2 full speed --> companion ehci_hcd 0000:00:13.2: GetStatus port 2 status 003801 POWER OWNER sig=j CONNECT hub 1-0:1.0: port 2 not reset yet, waiting 50ms ehci_hcd 0000:00:13.2: GetStatus port 2 status 003002 POWER OWNER sig=se0 CSC ehci_hcd 0000:00:13.2: GetStatus port 3 status 001803 POWER sig=j CSC CONNECT hub 1-0:1.0: port 3, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x501 ehci_hcd 0000:00:13.2: port 3 full speed --> companion ehci_hcd 0000:00:13.2: GetStatus port 3 status 003801 POWER OWNER sig=j CONNECT hub 1-0:1.0: port 3 not reset yet, waiting 50ms ehci_hcd 0000:00:13.2: GetStatus port 3 status 003002 POWER OWNER sig=se0 CSC ehci_hcd 0000:00:13.2: GetStatus port 8 status 001403 POWER sig=k CSC CONNECT hub 1-0:1.0: port 8, status 0501, change 0001, 480 Mb/s hub 1-0:1.0: debounce: port 8: total 100ms stable 100ms status 0x501 ehci_hcd 0000:00:13.2: port 8 low speed --> companion ehci_hcd 0000:00:13.2: GetStatus port 8 status 003002 POWER OWNER sig=se0 CSC hub 2-0:1.0: state 7 ports 4 chg 0000 evt 0004 ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00010101 CSC PPS CCS hub 2-0:1.0: port 2, status 0101, change 0001, 12 Mb/s hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x101 ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: new full speed USB device using ohci_hcd and address 11 ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS usb 2-2: skipped 1 descriptor after interface usb 2-2: default language 0x0409 usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-2: Product: HP Integrated Module usb 2-2: Manufacturer: Broadcom Corp PM: Adding info for usb:2-2 usb 2-2: uevent usb 2-2: usb_probe_device PM: Adding info for No Bus:usbdev2.11_ep00 usb 2-2: configuration #1 chosen from 1 choice usb 2-2: adding 2-2:1.0 (config #1, interface 0) PM: Adding info for usb:2-2:1.0 usb 2-2:1.0: uevent hci_usb 2-2:1.0: usb_probe_interface hci_usb 2-2:1.0: usb_probe_interface - got id PM: Adding info for No Bus:hci0 PM: Adding info for No Bus:usbdev2.11_ep81 PM: Adding info for No Bus:usbdev2.11_ep82 PM: Adding info for No Bus:usbdev2.11_ep02 usb 2-2: adding 2-2:1.1 (config #1, interface 1) PM: Adding info for usb:2-2:1.1 usb 2-2:1.1: uevent PM: Adding info for No Bus:usbdev2.11_ep83 PM: Adding info for No Bus:usbdev2.11_ep03 usb 2-2: adding 2-2:1.2 (config #1, interface 2) PM: Adding info for usb:2-2:1.2 usb 2-2:1.2: uevent hci_usb 2-2:1.2: usb_probe_interface hci_usb 2-2:1.2: usb_probe_interface - got id PM: Adding info for No Bus:usbdev2.11_ep84 PM: Adding info for No Bus:usbdev2.11_ep04 usb 2-2: adding 2-2:1.3 (config #1, interface 3) PM: Adding info for usb:2-2:1.3 usb 2-2:1.3: uevent hci_usb 2-2:1.3: usb_probe_interface hci_usb 2-2:1.3: usb_probe_interface - got id PM: Adding info for No Bus:usbdev2.11 drivers/usb/core/inode.c: creating file '011' hub 3-0:1.0: state 7 ports 4 chg 0000 evt 0012 ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00010101 CSC PPS CCS hub 3-0:1.0: port 1, status 0101, change 0001, 12 Mb/s hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101 ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS usb 3-1: new full speed USB device using ohci_hcd and address 20 ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS usb 3-1: ep0 maxpacket = 8 usb 3-1: default language 0x0409 usb 3-1: new device strings: Mfr=0, Product=1, SerialNumber=0 usb 3-1: Product: Fingerprint Sensor PM: Adding info for usb:3-1 usb 3-1: uevent usb 3-1: usb_probe_device PM: Adding info for No Bus:usbdev3.20_ep00 usb 3-1: configuration #1 chosen from 1 choice usb 3-1: adding 3-1:1.0 (config #1, interface 0) PM: Adding info for usb:3-1:1.0 usb 3-1:1.0: uevent PM: Adding info for No Bus:usbdev3.20_ep81 PM: Adding info for No Bus:usbdev3.20_ep02 PM: Adding info for No Bus:usbdev3.20 drivers/usb/core/inode.c: creating file '020' ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [3] = 0x00010301 CSC LSDA PPS CCS hub 3-0:1.0: port 4, status 0301, change 0001, 1.5 Mb/s hub 3-0:1.0: debounce: port 4: total 100ms stable 100ms status 0x301 ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [3] = 0x00100303 PRSC LSDA PPS PES CCS usb 3-4: new low speed USB device using ohci_hcd and address 21 ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [3] = 0x00100303 PRSC LSDA PPS PES CCS usb 3-4: skipped 1 descriptor after interface usb 3-4: default language 0x0409 usb 3-4: new device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-4: Product: USB Receiver usb 3-4: Manufacturer: Logitech PM: Adding info for usb:3-4 usb 3-4: uevent usb 3-4: usb_probe_device PM: Adding info for No Bus:usbdev3.21_ep00 usb 3-4: configuration #1 chosen from 1 choice usb 3-4: adding 3-4:1.0 (config #1, interface 0) PM: Adding info for usb:3-4:1.0 usb 3-4:1.0: uevent usbhid 3-4:1.0: usb_probe_interface usbhid 3-4:1.0: usb_probe_interface - got id INPUT[INPUT] Field(0) Physical(GenericDesktop.Pointer) Usage(8) Button.0001 Button.0002 Button.0003 Button.0004 Button.0005 Button.0006 Button.0007 Button.0008 Logical Minimum(0) Logical Maximum(1) Report Size(1) Report Count(8) Report Offset(0) Flags( Variable Absolute ) Field(1) Physical(GenericDesktop.Pointer) Usage(3) GenericDesktop.X GenericDesktop.Y GenericDesktop.Wheel Logical Minimum(-127) Logical Maximum(127) Report Size(8) Report Count(3) Report Offset(8) Flags( Variable Relative ) Field(2) Physical(GenericDesktop.Pointer) Usage(1) Consumer.HorizontalWheel Logical Minimum(-127) Logical Maximum(127) Report Size(8) Report Count(1) Report Offset(32) Flags( Variable Relative ) Field(3) Usage(8) LED.GenericIndicator LED.GenericIndicator LED.GenericIndicator LED.GenericIndicator LED.GenericIndicator LED.GenericIndicator LED.GenericIndicator LED.GenericIndicator Logical Minimum(0) Logical Maximum(1) Report Size(1) Report Count(8) Report Offset(40) Flags( Variable Absolute ) Field(4) Usage(8) Button.0009 Button.000a Button.000b Button.000c Button.000d Button.000e Button.000f Button.0010 Logical Minimum(0) Logical Maximum(1) Report Size(1) Report Count(8) Report Offset(48) Flags( Variable Absolute ) FEATURE[FEATURE] Field(0) Usage(1) GenericDesktop.MotionWakeup Logical Minimum(0) Logical Maximum(1) Report Size(1) Report Count(1) Report Offset(0) Flags( Variable Absolute NoPrefferedState ) Mapping: Button.0001 ---> Key.LeftBtn Mapping: Button.0002 ---> Key.RightBtn Mapping: Button.0003 ---> Key.MiddleBtn Mapping: Button.0004 ---> Key.SideBtn Mapping: Button.0005 ---> Key.ExtraBtn Mapping: Button.0006 ---> Key.ForwardBtn Mapping: Button.0007 ---> Key.BackBtn Mapping: Button.0008 ---> Key.TaskBtn Mapping: GenericDesktop.X ---> Relative.X Mapping: GenericDesktop.Y ---> Relative.Y Mapping: GenericDesktop.Wheel ---> Relative.Wheel Mapping: Consumer.HorizontalWheel ---> Relative.HWheel Mapping: LED.GenericIndicator ---> LED.Misc Mapping: LED.GenericIndicator ---> LED.? Mapping: LED.GenericIndicator ---> LED.? Mapping: LED.GenericIndicator ---> LED.? Mapping: LED.GenericIndicator ---> LED.? Mapping: LED.GenericIndicator ---> LED.? Mapping: LED.GenericIndicator ---> LED.? Mapping: LED.GenericIndicator ---> LED.? Mapping: Button.0009 ---> Key.? Mapping: Button.000a ---> Key.? Mapping: Button.000b ---> Key.? Mapping: Button.000c ---> Key.? Mapping: Button.000d ---> Key.? Mapping: Button.000e ---> Key.? Mapping: Button.000f ---> Key.? Mapping: Button.0010 ---> Key.? input: Logitech USB Receiver as /class/input/input16 hid-pidff: starting pid init hid-pidff: not a PID device, no output report input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:13.1-4 PM: Adding info for No Bus:usbdev3.21_ep81 PM: Adding info for No Bus:usbdev3.21 drivers/usb/core/inode.c: creating file '021' hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0100 hub 2-0:1.0: state 7 ports 4 chg 0000 evt 0004 hub 3-0:1.0: state 7 ports 4 chg 0000 evt 0002 usb 3-1: usb auto-suspend SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 hub 1-0:1.0: hub_suspend usb usb1: usb auto-suspend SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 PM: Removing info for No Bus:hw_random bcm43xx: Radio turned off bcm43xx: DMA-32 0x0200 (RX) max used slots: 0/64 bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0220 (TX) max used slots: 56/512 bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512 PM: Adding info for No Bus:0000:30:00.0 PM: Removing info for No Bus:0000:30:00.0 PM: Adding info for No Bus:0000:30:00.0 PM: Removing info for No Bus:0000:30:00.0 PM: Adding info for No Bus:0000:30:00.0 PM: Removing info for No Bus:0000:30:00.0 PM: Adding info for No Bus:0000:30:00.0 PM: Removing info for No Bus:0000:30:00.0 bcm43xx: IRQ_READY timeout bcm43xx: core_up for active 802.11 core failed (-19) usb 3-1: usb auto-resume ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS PES CCS usb 3-1: finish resume usb usb1: usb auto-resume usb usb1: finish resume hub 1-0:1.0: hub_resume ehci_hcd 0000:00:13.2: resume root hub hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0000 usb 3-1: usb auto-suspend hub 1-0:1.0: hub_suspend usb usb1: usb auto-suspend ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 14:02 ` Rafael J. Wysocki @ 2007-02-11 14:14 ` Michael Buesch 2007-02-11 14:41 ` Johannes Berg 2007-02-11 15:59 ` Larry Finger 0 siblings, 2 replies; 26+ messages in thread From: Michael Buesch @ 2007-02-11 14:14 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: bcm43xx-dev, Larry Finger, wireless, John Linville On Sunday 11 February 2007 15:02, Rafael J. Wysocki wrote: > On Sunday, 11 February 2007 14:07, Michael Buesch wrote: > > On Sunday 11 February 2007 13:56, Rafael J. Wysocki wrote: > > > On Saturday, 10 February 2007 21:33, Larry Finger wrote: > > > > Rafael, > > > > > > > > Rafael J. Wysocki wrote: > > > > > > > > > > I'm running with this patch applied right now, but the association is lost > > > > > after the resume anyway. I have to reload bcm43xx to make it associate with > > > > > the AP again (no big deal). > > > > > > > > > > > > Please send me the output of iwconfig and ifconfig after the resume, but before you reload bcm43xx. > > > > > > albercik:~ # iwconfig > > > lo no wireless extensions. > > > > > > eth0 no wireless extensions. > > > > > > eth1 IEEE 802.11b/g ESSID:"DI524" Nickname:"Broadcom 4311" > > > Mode:Managed Frequency=2.484 GHz Access Point: Invalid > > > Bit Rate=1 Mb/s Tx-Power=18 dBm > > > RTS thr:off Fragment thr:off > > > Encryption key:off > > > Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm > > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > > > albercik:~ # ifconfig eth1 > > > eth1 Link encap:Ethernet HWaddr 00:14:A5:BE:95:31 > > > inet addr:192.168.100.101 Bcast:192.168.100.255 Mask:255.255.255.0 > > > inet6 addr: fe80::214:a5ff:febe:9531/64 Scope:Link > > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > > RX packets:5137 errors:0 dropped:120 overruns:0 frame:0 > > > TX packets:5703 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:4569090 (4.3 Mb) TX bytes:156826797 (149.5 Mb) > > > Interrupt:18 > > > > > > albercik:~ # ifconfig eth1 down > > > albercik:~ # ifconfig eth1 up > > > SIOCSIFFLAGS: No such device > > ^^^^^ > > > > I'd like to see dmesg, please. > > Appended. It covers one suspend-resume cycle (suspend to disk). I have > filtered HID-related messages out of it. > > Greetings, > Rafael > > > ton.000e = 0 > usb 3-1: usb auto-resume > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00040103 PSSC PPS PES CCS > usb 3-1: finish resume > usb usb1: usb auto-resume > usb usb1: finish resume > hub 1-0:1.0: hub_resume > ehci_hcd 0000:00:13.2: resume root hub > hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0000 > usb 3-1: usb auto-suspend > hub 1-0:1.0: hub_suspend > usb usb1: usb auto-suspend > PM: Adding info for No Bus:vcs8 > PM: Adding info for No Bus:vcsa8 > SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 > Stopping tasks ... done. > Shrinking memory... \b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\bdone (113015 pages freed) > Freed 452060 kbytes in 1.44 seconds (313.93 MB/s) > Suspending console(s) > usbhid 3-4:1.0: freeze > usb 3-4: freeze > usbhid 3-4:1.0: suspend > usb 3-4: usb suspend > usbdev3.18: PM: suspend 0->1, parent 3-1 already 2 > usbdev3.18_ep02: PM: suspend 0->1, parent 3-1:1.0 already 2 > usbdev3.18_ep81: PM: suspend 0->1, parent 3-1:1.0 already 2 > usb 3-1:1.0: PM: suspend 2-->1 > usb 3-1:1.0: PM: suspend 2->1, parent 3-1 already 2 > usbdev3.18_ep00: PM: suspend 0->1, parent 3-1 already 2 > usb 3-1: PM: suspend 2-->1 > usb 2-2:1.3: freeze > usb 2-2:1.2: freeze > hci_usb 2-2:1.1: freeze > hci_usb 2-2:1.0: freeze > usb 2-2: freeze > usb 2-2: usb suspend > serio serio6: freeze > platform bluetooth: freeze > hub 3-0:1.0: freeze > usb usb3: freeze > hub 3-0:1.0: hub_suspend > ohci_hcd 0000:00:13.1: suspend root hub > usb usb3: usb suspend > hub 2-0:1.0: freeze > usb usb2: freeze > hub 2-0:1.0: hub_suspend > ohci_hcd 0000:00:13.0: suspend root hub > usb usb2: usb suspend > usbdev1.1: PM: suspend 0->1, parent usb1 already 2 > usbdev1.1_ep81: PM: suspend 0->1, parent 1-0:1.0 already 2 > hub 1-0:1.0: PM: suspend 2-->1 > hub 1-0:1.0: PM: suspend 2->1, parent usb1 already 2 > usbdev1.1_ep00: PM: suspend 0->1, parent usb1 already 2 > usb usb1: PM: suspend 2-->1 > ide-cdrom 0.0: freeze > psmouse serio4: freeze > serio serio3: freeze > serio serio2: freeze > serio serio1: freeze > atkbd serio0: freeze > i8042 i8042: freeze > sd 0:0:0:0: freeze > serial8250 serial8250: freeze > vesafb vesafb.0: freeze > pci_express 0000:00:06.0:pcie03: freeze > pci_express 0000:00:06.0:pcie01: freeze > pci_express 0000:00:06.0:pcie00: freeze > pci_express 0000:00:05.0:pcie03: freeze > pci_express 0000:00:05.0:pcie01: freeze > pci_express 0000:00:05.0:pcie00: freeze > pci_express 0000:00:04.0:pcie03: freeze > pci_express 0000:00:04.0:pcie01: freeze > pci_express 0000:00:04.0:pcie00: freeze > pcspkr pcspkr: freeze > sdhci 0000:02:04.3: freeze > ACPI: PCI interrupt for device 0000:02:04.3 disabled > tifm_7xx1 0000:02:04.2: freeze > ACPI: PCI interrupt for device 0000:02:04.2 disabled > ohci1394 0000:02:04.1: freeze > ohci1394 does not fully support suspend and resume yet > ieee1394: hpsb_bus_reset called while bus reset already in progress > yenta_cardbus 0000:02:04.0: freeze > tg3 0000:02:01.0: freeze > PM: Writing back config space on device 0000:02:01.0 at offset b (was 3ed173b, writing 30b0103c) > PM: Writing back config space on device 0000:02:01.0 at offset 3 (was 0, writing 4010) > PM: Writing back config space on device 0000:02:01.0 at offset 2 (was 2000000, writing 2000003) > PM: Writing back config space on device 0000:02:01.0 at offset 1 (was 2b00000, writing 2b00006) > PM: Writing back config space on device 0000:02:01.0 at offset 0 (was 3ed173b, writing 169c14e4) > bcm43xx 0000:30:00.0: freeze > bcm43xx: Suspending... > PM: Removing info for No Bus:hw_random > bcm43xx: Radio turned off > bcm43xx: DMA-32 0x0200 (RX) max used slots: 3/64 > bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512 > bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512 > bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512 > bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512 > bcm43xx: DMA-32 0x0220 (TX) max used slots: 3/512 > bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512 > ACPI: PCI interrupt for device 0000:30:00.0 disabled > bcm43xx: Device suspended. > pci 0000:01:05.0: freeze > k8temp 0000:00:18.3: freeze > pci 0000:00:18.2: freeze > pci 0000:00:18.1: freeze > pci 0000:00:18.0: freeze > pci 0000:00:14.4: freeze > pci 0000:00:14.3: freeze > HDA Intel 0000:00:14.2: freeze > ACPI: PCI interrupt for device 0000:00:14.2 disabled > ATIIXP_IDE 0000:00:14.1: freeze > piix4_smbus 0000:00:14.0: freeze > ehci_hcd 0000:00:13.2: freeze > ACPI: PCI interrupt for device 0000:00:13.2 disabled > ehci_hcd 0000:00:13.2: --> PCI D3 > ohci_hcd 0000:00:13.1: freeze > ACPI: PCI interrupt for device 0000:00:13.1 disabled > ohci_hcd 0000:00:13.1: --> PCI D0/legacy > ohci_hcd 0000:00:13.0: freeze > ACPI: PCI interrupt for device 0000:00:13.0 disabled > ohci_hcd 0000:00:13.0: --> PCI D0/legacy > sata_sil 0000:00:12.0: freeze > pcieport-driver 0000:00:06.0: freeze > pcieport-driver 0000:00:05.0: freeze > pcieport-driver 0000:00:04.0: freeze > pci 0000:00:01.0: freeze > pci 0000:00:00.0: freeze > ACPI Thermal Zone Driver thermal:03: freeze > ACPI Thermal Zone Driver thermal:02: freeze > ACPI Thermal Zone Driver thermal:01: freeze > ACPI Fan Driver PNP0C0B:03: freeze > ACPI Fan Driver PNP0C0B:02: freeze > ACPI: Transitioning device [C351] to D0 > ACPI: Transitioning device [C351] to D0 > ACPI Fan Driver PNP0C0B:01: freeze > ACPI: Transitioning device [C350] to D0 > ACPI: Transitioning device [C350] to D0 > ACPI Fan Driver PNP0C0B:00: freeze > ACPI: Transitioning device [C34F] to D0 > ACPI: Transitioning device [C34F] to D0 > ACPI Power Resource Driver power_resource:06: freeze > ACPI Power Resource Driver power_resource:05: freeze > ACPI Power Resource Driver power_resource:04: freeze > ACPI Power Resource Driver power_resource:03: freeze > acpi thermal:00: freeze > acpi PNP0C02:02: freeze > acpi PNP0C14:00: freeze > ACPI Button Driver PNP0C0D:00: freeze > ACPI Button Driver PNP0C0E:00: freeze > ACPI AC Adapter Driver ACPI0003:00: freeze > ACPI Battery Driver PNP0C0A:01: freeze > ACPI Battery Driver PNP0C0A:00: freeze > acpi HPQ0006:00: freeze > acpi PNP0C02:01: freeze > acpi device:49: freeze > acpi device:48: freeze > acpi device:47: freeze > acpi device:46: freeze > acpi device:45: freeze > acpi device:44: freeze > acpi device:43: freeze > acpi device:42: freeze > acpi device:41: freeze > acpi device:40: freeze > acpi device:3f: freeze > acpi device:3e: freeze > acpi device:3d: freeze > acpi device:3c: freeze > acpi device:3b: freeze > acpi device:3a: freeze > acpi device:39: freeze > acpi device:38: freeze > acpi device:37: freeze > acpi device:36: freeze > acpi device:35: freeze > acpi device:34: freeze > acpi device:33: freeze > ACPI PCI Interrupt Link Driver PNP0C0F:07: freeze > ACPI PCI Interrupt Link Driver PNP0C0F:06: freeze > ACPI PCI Interrupt Link Driver PNP0C0F:05: freeze > ACPI PCI Interrupt Link Driver PNP0C0F:04: freeze > ACPI PCI Interrupt Link Driver PNP0C0F:03: freeze > ACPI PCI Interrupt Link Driver PNP0C0F:02: freeze > ACPI PCI Interrupt Link Driver PNP0C0F:01: freeze > ACPI PCI Interrupt Link Driver PNP0C0F:00: freeze > acpi device:32: freeze > acpi device:31: freeze > acpi device:30: freeze > acpi device:2f: freeze > acpi device:2e: freeze > acpi device:2d: freeze > acpi device:2c: freeze > acpi device:2b: freeze > acpi device:2a: freeze > acpi device:29: freeze > acpi device:28: freeze > acpi device:27: freeze > acpi device:26: freeze > acpi device:25: freeze > acpi device:24: freeze > acpi device:23: freeze > acpi device:22: freeze > acpi device:21: freeze > acpi device:20: freeze > acpi device:1f: freeze > acpi device:1e: freeze > acpi device:1d: freeze > acpi device:1c: freeze > acpi device:1b: freeze > acpi device:1a: freeze > acpi device:19: freeze > acpi device:18: freeze > acpi device:17: freeze > acpi device:16: freeze > acpi device:15: freeze > acpi device:14: freeze > acpi device:13: freeze > acpi device:12: freeze > acpi device:11: freeze > acpi device:10: freeze > acpi PNP0C02:00: freeze > acpi PNP0000:00: freeze > ACPI Power Resource Driver power_resource:02: freeze > acpi SYN0118:00: freeze > acpi PNP0303:00: freeze > acpi PNP0B00:00: freeze > acpi PNP0800:00: freeze > acpi PNP0200:00: freeze > acpi PNP0100:00: freeze > acpi PNP0C04:00: freeze > acpi IFX0102:00: freeze > ACPI Power Resource Driver power_resource:01: freeze > acpi PNP0401:00: freeze > ACPI container driver PNP0A06:00: freeze > ACPI Embedded Controller Driver PNP0C09:00: freeze > acpi device:0f: freeze > acpi device:0e: freeze > ACPI Power Resource Driver power_resource:00: freeze > acpi device:0d: freeze > acpi device:0c: freeze > acpi device:0b: freeze > acpi device:0a: freeze > acpi device:09: freeze > acpi device:08: freeze > acpi device:07: freeze > acpi device:06: freeze > acpi device:05: freeze > acpi device:04: freeze > acpi device:03: freeze > acpi device:02: freeze > acpi video:00: freeze > acpi device:01: freeze > ACPI PCI Root Bridge Driver PNP0A03:00: freeze > acpi PNP0C01:00: freeze > acpi device:00: freeze > ACPI Processor Driver ACPI0007:01: freeze > ACPI Processor Driver ACPI0007:00: freeze > ACPI Button Driver button_power:00: freeze > acpi acpi_system:00: freeze > Disabling non-boot CPUs ... > CPU 1 is now offline > SMP alternatives: switching to UP code > CPU1 is down > platform bluetooth: LATE freeze > i8042 i8042: LATE freeze > serial8250 serial8250: LATE freeze > vesafb vesafb.0: LATE freeze > pcspkr pcspkr: LATE freeze > sdhci 0000:02:04.3: LATE freeze > tifm_7xx1 0000:02:04.2: LATE freeze > ohci1394 0000:02:04.1: LATE freeze > yenta_cardbus 0000:02:04.0: LATE freeze > tg3 0000:02:01.0: LATE freeze > bcm43xx 0000:30:00.0: LATE freeze > pci 0000:01:05.0: LATE freeze > k8temp 0000:00:18.3: LATE freeze > pci 0000:00:18.2: LATE freeze > pci 0000:00:18.1: LATE freeze > pci 0000:00:18.0: LATE freeze > pci 0000:00:14.4: LATE freeze > pci 0000:00:14.3: LATE freeze > HDA Intel 0000:00:14.2: LATE freeze > ATIIXP_IDE 0000:00:14.1: LATE freeze > piix4_smbus 0000:00:14.0: LATE freeze > pcieport-driver 0000:00:06.0: LATE freeze > pcieport-driver 0000:00:05.0: LATE freeze > pcieport-driver 0000:00:04.0: LATE freeze > pci 0000:00:01.0: LATE freeze > pci 0000:00:00.0: LATE freeze > Extended CMOS year: 2000 > swsusp: critical section: > swsusp: Need to copy 95157 pages > swsusp: Normal pages needed: 95157 + 1024 + 20, available pages: 134073 > Extended CMOS year: 2000 > pci 0000:00:00.0: EARLY resume > pci 0000:00:01.0: EARLY resume > pcieport-driver 0000:00:04.0: EARLY resume > pcieport-driver 0000:00:05.0: EARLY resume > pcieport-driver 0000:00:06.0: EARLY resume > sata_sil 0000:00:12.0: EARLY resume > ohci_hcd 0000:00:13.0: EARLY resume > ohci_hcd 0000:00:13.1: EARLY resume > ehci_hcd 0000:00:13.2: EARLY resume > piix4_smbus 0000:00:14.0: EARLY resume > ATIIXP_IDE 0000:00:14.1: EARLY resume > HDA Intel 0000:00:14.2: EARLY resume > pci 0000:00:14.3: EARLY resume > pci 0000:00:14.4: EARLY resume > pci 0000:00:18.0: EARLY resume > pci 0000:00:18.1: EARLY resume > pci 0000:00:18.2: EARLY resume > k8temp 0000:00:18.3: EARLY resume > pci 0000:01:05.0: EARLY resume > bcm43xx 0000:30:00.0: EARLY resume > tg3 0000:02:01.0: EARLY resume > yenta_cardbus 0000:02:04.0: EARLY resume > ohci1394 0000:02:04.1: EARLY resume > tifm_7xx1 0000:02:04.2: EARLY resume > sdhci 0000:02:04.3: EARLY resume > pcspkr pcspkr: EARLY resume > vesafb vesafb.0: EARLY resume > serial8250 serial8250: EARLY resume > i8042 i8042: EARLY resume > platform bluetooth: EARLY resume > Enabling non-boot CPUs ... > SMP alternatives: switching to SMP code > Booting processor 1/2 APIC 0x1 > Initializing CPU#1 > Calibrating delay using timer specific routine.. 3990.23 BogoMIPS (lpj=7980462) > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > CPU: L2 Cache: 512K (64 bytes/line) > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 1 > AMD Turion(tm) 64 X2 Mobile Technology TL-60 stepping 02 > CPU 1: Syncing TSC to CPU 0. > CPU 1: synchronized TSC with CPU 0 (last diff 0 cycles, maxerr 510 cycles) > powernow-k8: 0 : fid 0xc (2000 MHz), vid 0x13 > powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x15 > powernow-k8: 2 : fid 0x8 (1600 MHz), vid 0x17 > powernow-k8: 3 : fid 0x0 (800 MHz), vid 0x1e > CPU1 is up > acpi acpi_system:00: resuming > ACPI Button Driver button_power:00: resuming > ACPI Processor Driver ACPI0007:00: resuming > ACPI Processor Driver ACPI0007:01: resuming > acpi device:00: resuming > acpi PNP0C01:00: resuming > ACPI PCI Root Bridge Driver PNP0A03:00: resuming > acpi device:01: resuming > acpi video:00: resuming > acpi device:02: resuming > acpi device:03: resuming > acpi device:04: resuming > acpi device:05: resuming > acpi device:06: resuming > acpi device:07: resuming > acpi device:08: resuming > acpi device:09: resuming > acpi device:0a: resuming > acpi device:0b: resuming > acpi device:0c: resuming > acpi device:0d: resuming > ACPI Power Resource Driver power_resource:00: resuming > acpi device:0e: resuming > acpi device:0f: resuming > ACPI Embedded Controller Driver PNP0C09:00: resuming > ACPI container driver PNP0A06:00: resuming > acpi PNP0401:00: resuming > ACPI Power Resource Driver power_resource:01: resuming > acpi IFX0102:00: resuming > acpi PNP0C04:00: resuming > acpi PNP0100:00: resuming > acpi PNP0200:00: resuming > acpi PNP0800:00: resuming > acpi PNP0B00:00: resuming > acpi PNP0303:00: resuming > acpi SYN0118:00: resuming > ACPI Power Resource Driver power_resource:02: resuming > acpi PNP0000:00: resuming > acpi PNP0C02:00: resuming > acpi device:10: resuming > acpi device:11: resuming > acpi device:12: resuming > acpi device:13: resuming > acpi device:14: resuming > acpi device:15: resuming > acpi device:16: resuming > acpi device:17: resuming > acpi device:18: resuming > acpi device:19: resuming > acpi device:1a: resuming > acpi device:1b: resuming > acpi device:1c: resuming > acpi device:1d: resuming > acpi device:1e: resuming > acpi device:1f: resuming > acpi device:20: resuming > acpi device:21: resuming > acpi device:22: resuming > acpi device:23: resuming > acpi device:24: resuming > acpi device:25: resuming > acpi device:26: resuming > acpi device:27: resuming > acpi device:28: resuming > acpi device:29: resuming > acpi device:2a: resuming > acpi device:2b: resuming > acpi device:2c: resuming > acpi device:2d: resuming > acpi device:2e: resuming > acpi device:2f: resuming > acpi device:30: resuming > acpi device:31: resuming > acpi device:32: resuming > ACPI PCI Interrupt Link Driver PNP0C0F:00: resuming > ACPI PCI Interrupt Link Driver PNP0C0F:01: resuming > ACPI PCI Interrupt Link Driver PNP0C0F:02: resuming > ACPI PCI Interrupt Link Driver PNP0C0F:03: resuming > ACPI PCI Interrupt Link Driver PNP0C0F:04: resuming > ACPI PCI Interrupt Link Driver PNP0C0F:05: resuming > ACPI PCI Interrupt Link Driver PNP0C0F:06: resuming > ACPI PCI Interrupt Link Driver PNP0C0F:07: resuming > acpi device:33: resuming > acpi device:34: resuming > acpi device:35: resuming > acpi device:36: resuming > acpi device:37: resuming > acpi device:38: resuming > acpi device:39: resuming > acpi device:3a: resuming > acpi device:3b: resuming > acpi device:3c: resuming > acpi device:3d: resuming > acpi device:3e: resuming > acpi device:3f: resuming > acpi device:40: resuming > acpi device:41: resuming > acpi device:42: resuming > acpi device:43: resuming > acpi device:44: resuming > acpi device:45: resuming > acpi device:46: resuming > acpi device:47: resuming > acpi device:48: resuming > acpi device:49: resuming > acpi PNP0C02:01: resuming > acpi HPQ0006:00: resuming > ACPI Battery Driver PNP0C0A:00: resuming > ACPI Battery Driver PNP0C0A:01: resuming > ACPI AC Adapter Driver ACPI0003:00: resuming > ACPI Button Driver PNP0C0E:00: resuming > ACPI Button Driver PNP0C0D:00: resuming > acpi PNP0C14:00: resuming > acpi PNP0C02:02: resuming > acpi thermal:00: resuming > ACPI Power Resource Driver power_resource:03: resuming > ACPI Power Resource Driver power_resource:04: resuming > ACPI Power Resource Driver power_resource:05: resuming > ACPI Power Resource Driver power_resource:06: resuming > ACPI Fan Driver PNP0C0B:00: resuming > ACPI: Transitioning device [C34F] to D0 > ACPI: Transitioning device [C34F] to D0 > ACPI Fan Driver PNP0C0B:01: resuming > ACPI: Transitioning device [C350] to D0 > ACPI: Transitioning device [C350] to D0 > ACPI Fan Driver PNP0C0B:02: resuming > ACPI: Transitioning device [C351] to D0 > ACPI: Transitioning device [C351] to D0 > ACPI Fan Driver PNP0C0B:03: resuming > ACPI Thermal Zone Driver thermal:01: resuming > ACPI Thermal Zone Driver thermal:02: resuming > ACPI Thermal Zone Driver thermal:03: resuming > pci 0000:00:00.0: resuming > pci 0000:00:01.0: resuming > pcieport-driver 0000:00:04.0: resuming > PCI: Setting latency timer of device 0000:00:04.0 to 64 > pcieport-driver 0000:00:05.0: resuming > PCI: Setting latency timer of device 0000:00:05.0 to 64 > pcieport-driver 0000:00:06.0: resuming > PCI: Setting latency timer of device 0000:00:06.0 to 64 > sata_sil 0000:00:12.0: resuming > ohci_hcd 0000:00:13.0: resuming > ohci_hcd 0000:00:13.0: PCI legacy resume > ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 19 (level, low) -> IRQ 19 > ohci_hcd 0000:00:13.1: resuming > ohci_hcd 0000:00:13.1: PCI legacy resume > ACPI: PCI Interrupt 0000:00:13.1[A] -> GSI 19 (level, low) -> IRQ 19 > ehci_hcd 0000:00:13.2: resuming > ehci_hcd 0000:00:13.2: PCI D0, from previous PCI D3 > ACPI: PCI Interrupt 0000:00:13.2[A] -> GSI 19 (level, low) -> IRQ 19 > PM: Writing back config space on device 0000:00:13.2 at offset 1 (was 2b00007, writing 2b00017) > ehci_hcd 0000:00:13.2: lost power, restarting > usb usb1: root hub lost power or was reset > ehci_hcd 0000:00:13.2: reset command 080002 (park)=0 ithresh=8 period=1024 Reset HALT > ehci_hcd 0000:00:13.2: MWI active > piix4_smbus 0000:00:14.0: resuming > ATIIXP_IDE 0000:00:14.1: resuming > ACPI: PCI Interrupt 0000:00:14.1[A] -> GSI 16 (level, low) -> IRQ 16 > HDA Intel 0000:00:14.2: resuming > PM: Writing back config space on device 0000:00:14.2 at offset f (was 10a, writing a) > PM: Writing back config space on device 0000:00:14.2 at offset 1 (was 4100006, writing 4100002) > ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 16 > pci 0000:00:14.3: resuming > pci 0000:00:14.4: resuming > PM: Writing back config space on device 0000:00:14.4 at offset 6 (was 40030200, writing 40060200) > pci 0000:00:18.0: resuming > pci 0000:00:18.1: resuming > pci 0000:00:18.2: resuming > k8temp 0000:00:18.3: resuming > pci 0000:01:05.0: resuming > bcm43xx 0000:30:00.0: resuming > bcm43xx: Resuming... > ACPI: PCI Interrupt 0000:30:00.0[A] -> GSI 18 (level, low) -> IRQ 18 > bcm43xx: PHY connected > bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) > bcm43xx: Radio turned on > bcm43xx: Radio enabled by hardware > ata2: SATA link down (SStatus 0 SControl 300) > bcm43xx: Chip initialized > bcm43xx: 32-bit DMA initialized > bcm43xx: Keys cleared > bcm43xx: Selected 802.11 core (phytype 2) > PM: Adding info for No Bus:hw_random > bcm43xx: Device resumed. > tg3 0000:02:01.0: resuming > PM: Writing back config space on device 0000:02:01.0 at offset b (was 3ed173b, writing 30b0103c) > PM: Writing back config space on device 0000:02:01.0 at offset 3 (was 0, writing 4010) > PM: Writing back config space on device 0000:02:01.0 at offset 2 (was 2000000, writing 2000003) > PM: Writing back config space on device 0000:02:01.0 at offset 1 (was 2b00000, writing 2b00006) > PM: Writing back config space on device 0000:02:01.0 at offset 0 (was 3ed173b, writing 169c14e4) > SoftMAC: Associate: Scanning for networks first. > yenta_cardbus 0000:02:04.0: resuming > PM: Writing back config space on device 0000:02:04.0 at offset f (was 3c4010a, writing 5c0010a) > PM: Writing back config space on device 0000:02:04.0 at offset 3 (was 824010, writing 82a810) > ohci1394 0000:02:04.1: resuming > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[20] MMIO=[d4011000-d40117ff] Max Packet=[2048] IR/IT contexts=[4/8] > tifm_7xx1 0000:02:04.2: resuming > ACPI: PCI Interrupt 0000:02:04.2[A] -> GSI 20 (level, low) -> IRQ 20 > sdhci 0000:02:04.3: resuming > ACPI: PCI Interrupt 0000:02:04.3[A] -> GSI 20 (level, low) -> IRQ 20 > pcspkr pcspkr: resuming > pci_express 0000:00:04.0:pcie00: resuming > pci_express 0000:00:04.0:pcie01: resuming > pci_express 0000:00:04.0:pcie03: resuming > pci_express 0000:00:05.0:pcie00: resuming > pci_express 0000:00:05.0:pcie01: resuming > pci_express 0000:00:05.0:pcie03: resuming > pci_express 0000:00:06.0:pcie00: resuming > pci_express 0000:00:06.0:pcie01: resuming > pci_express 0000:00:06.0:pcie03: resuming > vesafb vesafb.0: resuming > serial8250 serial8250: resuming > sd 0:0:0:0: resuming > i8042 i8042: resuming > atkbd serio0: resuming > serio serio1: resuming > serio serio2: resuming > serio serio3: resuming > psmouse serio4: resuming > synaptics reset failed > synaptics reset failed > synaptics reset failed > SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 > ide-cdrom 0.0: resuming > usb usb1: resuming > usb usb1: usb resume > usb usb1: finish resume > hub 1-0:1.0: hub_resume > ehci_hcd 0000:00:13.2: resume root hub after power loss > usb usb2: resuming > usb usb2: usb resume > usb usb2: finish resume > hub 2-0:1.0: hub_resume > ohci_hcd 0000:00:13.0: BIOS/SMM active, control 008 > usb usb2: root hub lost power or was reset > ohci_hcd 0000:00:13.0: resetting from state 'reset', control = 0x8 > ohci_hcd 0000:00:13.0: OHCI controller state > ohci_hcd 0000:00:13.0: OHCI 1.0, NO legacy support registers > ohci_hcd 0000:00:13.0: control 0x083 HCFS=operational CBSR=3 > ohci_hcd 0000:00:13.0: cmdstatus 0x00000 SOC=0 > ohci_hcd 0000:00:13.0: intrstatus 0x00000004 SF > ohci_hcd 0000:00:13.0: intrenable 0x8000005a MIE RHSC UE RD WDH > ohci_hcd 0000:00:13.0: hcca frame #0005 > ohci_hcd 0000:00:13.0: roothub.a 02000204 POTPGT=2 NPS NDP=4(4) > ohci_hcd 0000:00:13.0: roothub.b 00000000 PPCM=0000 DR=0000 > ohci_hcd 0000:00:13.0: roothub.status 00008000 DRWE > ohci_hcd 0000:00:13.0: roothub.portstatus [0] 0x00000100 PPS > ohci_hcd 0000:00:13.0: roothub.portstatus [1] 0x00010100 CSC PPS > ohci_hcd 0000:00:13.0: roothub.portstatus [2] 0x00000100 PPS > ohci_hcd 0000:00:13.0: roothub.portstatus [3] 0x00000100 PPS > ohci_hcd 0000:00:13.0: restart complete > hub 2-0:1.0: resuming > usb usb3: resuming > usb usb3: usb resume > usb usb3: finish resume > hub 3-0:1.0: hub_resume > ohci_hcd 0000:00:13.1: BIOS/SMM active, control 008 > usb usb3: root hub lost power or was reset > ohci_hcd 0000:00:13.1: resetting from state 'reset', control = 0x8 > ohci_hcd 0000:00:13.1: OHCI controller state > ohci_hcd 0000:00:13.1: OHCI 1.0, NO legacy support registers > ohci_hcd 0000:00:13.1: control 0x083 HCFS=operational CBSR=3 > ohci_hcd 0000:00:13.1: cmdstatus 0x00000 SOC=0 > ohci_hcd 0000:00:13.1: intrstatus 0x00000004 SF > ohci_hcd 0000:00:13.1: intrenable 0x8000005a MIE RHSC UE RD WDH > ohci_hcd 0000:00:13.1: hcca frame #0005 > ohci_hcd 0000:00:13.1: roothub.a 02000204 POTPGT=2 NPS NDP=4(4) > ohci_hcd 0000:00:13.1: roothub.b 00000000 PPCM=0000 DR=0000 > ohci_hcd 0000:00:13.1: roothub.status 00008000 DRWE > ohci_hcd 0000:00:13.1: roothub.portstatus [0] 0x00010100 CSC PPS > ohci_hcd 0000:00:13.1: roothub.portstatus [1] 0x00000100 PPS > ohci_hcd 0000:00:13.1: roothub.portstatus [2] 0x00000100 PPS > ohci_hcd 0000:00:13.1: roothub.portstatus [3] 0x00010100 CSC PPS > ohci_hcd 0000:00:13.1: restart complete > hub 3-0:1.0: resuming > platform bluetooth: resuming > serio serio6: resuming > usb 2-2: resuming > usbdev2.10_ep00: PM: resume from 0, parent 2-2 still 1 > hci_usb 2-2:1.0: PM: resume from 1, parent 2-2 still 1 > hci_usb 2-2:1.0: resuming > hci0: PM: resume from 0, parent 2-2:1.0 still 1 > usbdev2.10_ep81: PM: resume from 0, parent 2-2:1.0 still 1 > usbdev2.10_ep82: PM: resume from 0, parent 2-2:1.0 still 1 > usbdev2.10_ep02: PM: resume from 0, parent 2-2:1.0 still 1 > hci_usb 2-2:1.1: PM: resume from 1, parent 2-2 still 1 > hci_usb 2-2:1.1: resuming > usbdev2.10_ep83: PM: resume from 0, parent 2-2:1.1 still 1 > usbdev2.10_ep03: PM: resume from 0, parent 2-2:1.1 still 1 > usb 2-2:1.2: PM: resume from 1, parent 2-2 still 1 > usb 2-2:1.2: resuming > usbdev2.10_ep84: PM: resume from 0, parent 2-2:1.2 still 1 > usbdev2.10_ep04: PM: resume from 0, parent 2-2:1.2 still 1 > usb 2-2:1.3: PM: resume from 1, parent 2-2 still 1 > usb 2-2:1.3: resuming > usbdev2.10: PM: resume from 0, parent 2-2 still 1 > usbdev3.18_ep00: PM: resume from 0, parent 3-1 still 2 > usbdev3.18_ep81: PM: resume from 0, parent 3-1:1.0 still 2 > usbdev3.18_ep02: PM: resume from 0, parent 3-1:1.0 still 2 > usbdev3.18: PM: resume from 0, parent 3-1 still 2 > usb 3-4: resuming > usbdev3.19_ep00: PM: resume from 0, parent 3-4 still 1 > usbhid 3-4:1.0: PM: resume from 1, parent 3-4 still 1 > usbhid 3-4:1.0: resuming > usbdev3.19_ep81: PM: resume from 0, parent 3-4:1.0 still 1 > usbdev3.19: PM: resume from 0, parent 3-4 still 1 > Restarting tasks ... <7>hub 2-0:1.0: state 7 ports 4 chg 0004 evt 001e > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS > hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s > done. > PM: Removing info for No Bus:vcs8 > PM: Removing info for No Bus:vcsa8 > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata1.00: configured for UDMA/100 > SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB) > sda: Write Protect is off > sda: Mode Sense: 00 3a 00 00 > SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA > hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00010100 CSC PPS > hub 2-0:1.0: port 2, status 0100, change 0001, 12 Mb/s > usb 2-2: USB disconnect, address 10 > usb 2-2: unregistering device > usb 2-2: usb_disable_device nuking all URBs > usb 2-2: unregistering interface 2-2:1.0 > PM: Removing info for No Bus:usbdev2.10_ep81 > usbdev2.10_ep81: ep_device_release called for usbdev2.10_ep81 > PM: Removing info for No Bus:usbdev2.10_ep82 > usbdev2.10_ep82: ep_device_release called for usbdev2.10_ep82 > PM: Removing info for No Bus:usbdev2.10_ep02 > usbdev2.10_ep02: ep_device_release called for usbdev2.10_ep02 > PM: Removing info for No Bus:hci0 > PM: Removing info for usb:2-2:1.0 > usb 2-2:1.0: uevent > usb 2-2: unregistering interface 2-2:1.1 > PM: Removing info for No Bus:usbdev2.10_ep83 > usbdev2.10_ep83: ep_device_release called for usbdev2.10_ep83 > PM: Removing info for No Bus:usbdev2.10_ep03 > usbdev2.10_ep03: ep_device_release called for usbdev2.10_ep03 > PM: Removing info for usb:2-2:1.1 > usb 2-2:1.1: uevent > usb 2-2: unregistering interface 2-2:1.2 > PM: Removing info for No Bus:usbdev2.10_ep84 > usbdev2.10_ep84: ep_device_release called for usbdev2.10_ep84 > PM: Removing info for No Bus:usbdev2.10_ep04 > usbdev2.10_ep04: ep_device_release called for usbdev2.10_ep04 > PM: Removing info for usb:2-2:1.2 > usb 2-2:1.2: uevent > usb 2-2: unregistering interface 2-2:1.3 > PM: Removing info for usb:2-2:1.3 > usb 2-2:1.3: uevent > PM: Removing info for No Bus:usbdev2.10 > PM: Removing info for No Bus:usbdev2.10_ep00 > usbdev2.10_ep00: ep_device_release called for usbdev2.10_ep00 > PM: Removing info for usb:2-2 > usb 2-2: uevent > SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 > hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x100 > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [2] = 0x00010100 CSC PPS > hub 2-0:1.0: port 3, status 0100, change 0001, 12 Mb/s > hub 2-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x100 > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [3] = 0x00010100 CSC PPS > hub 2-0:1.0: port 4, status 0100, change 0001, 12 Mb/s > hub 2-0:1.0: debounce: port 4: total 100ms stable 100ms status 0x100 > hub 3-0:1.0: state 7 ports 4 chg 0012 evt 001e > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00010100 CSC PPS > hub 3-0:1.0: port 1, status 0100, change 0001, 12 Mb/s > usb 3-1: USB disconnect, address 18 > usb 3-1: unregistering device > usb 3-1: usb_disable_device nuking all URBs > usb 3-1: unregistering interface 3-1:1.0 > PM: Removing info for No Bus:usbdev3.18_ep81 > usbdev3.18_ep81: ep_device_release called for usbdev3.18_ep81 > PM: Removing info for No Bus:usbdev3.18_ep02 > usbdev3.18_ep02: ep_device_release called for usbdev3.18_ep02 > PM: Removing info for usb:3-1:1.0 > usb 3-1:1.0: uevent > PM: Removing info for No Bus:usbdev3.18 > PM: Removing info for No Bus:usbdev3.18_ep00 > usbdev3.18_ep00: ep_device_release called for usbdev3.18_ep00 > PM: Removing info for usb:3-1 > usb 3-1: uevent > hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100 > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [1] = 0x00010100 CSC PPS > hub 3-0:1.0: port 2, status 0100, change 0001, 12 Mb/s > hub 3-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x100 > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [2] = 0x00010100 CSC PPS > hub 3-0:1.0: port 3, status 0100, change 0001, 12 Mb/s > hub 3-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x100 > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [3] = 0x00010100 CSC PPS > hub 3-0:1.0: port 4, status 0100, change 0001, 12 Mb/s > usb 3-4: USB disconnect, address 19 > usb 3-4: unregistering device > usb 3-4: usb_disable_device nuking all URBs > usb 3-4: unregistering interface 3-4:1.0 > PM: Removing info for No Bus:usbdev3.19_ep81 > usbdev3.19_ep81: ep_device_release called for usbdev3.19_ep81 > PM: Removing info for usb:3-4:1.0 > usb 3-4:1.0: uevent > PM: Removing info for No Bus:usbdev3.19 > PM: Removing info for No Bus:usbdev3.19_ep00 > usbdev3.19_ep00: ep_device_release called for usbdev3.19_ep00 > PM: Removing info for usb:3-4 > usb 3-4: uevent > hub 3-0:1.0: debounce: port 4: total 100ms stable 100ms status 0x100 > hub 1-0:1.0: state 7 ports 8 chg 0000 evt 010c > ehci_hcd 0000:00:13.2: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT > hub 1-0:1.0: port 2, status 0501, change 0001, 480 Mb/s > hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501 > ehci_hcd 0000:00:13.2: port 2 full speed --> companion > ehci_hcd 0000:00:13.2: GetStatus port 2 status 003801 POWER OWNER sig=j CONNECT > hub 1-0:1.0: port 2 not reset yet, waiting 50ms > ehci_hcd 0000:00:13.2: GetStatus port 2 status 003002 POWER OWNER sig=se0 CSC > ehci_hcd 0000:00:13.2: GetStatus port 3 status 001803 POWER sig=j CSC CONNECT > hub 1-0:1.0: port 3, status 0501, change 0001, 480 Mb/s > hub 1-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x501 > ehci_hcd 0000:00:13.2: port 3 full speed --> companion > ehci_hcd 0000:00:13.2: GetStatus port 3 status 003801 POWER OWNER sig=j CONNECT > hub 1-0:1.0: port 3 not reset yet, waiting 50ms > ehci_hcd 0000:00:13.2: GetStatus port 3 status 003002 POWER OWNER sig=se0 CSC > ehci_hcd 0000:00:13.2: GetStatus port 8 status 001403 POWER sig=k CSC CONNECT > hub 1-0:1.0: port 8, status 0501, change 0001, 480 Mb/s > hub 1-0:1.0: debounce: port 8: total 100ms stable 100ms status 0x501 > ehci_hcd 0000:00:13.2: port 8 low speed --> companion > ehci_hcd 0000:00:13.2: GetStatus port 8 status 003002 POWER OWNER sig=se0 CSC > hub 2-0:1.0: state 7 ports 4 chg 0000 evt 0004 > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00010101 CSC PPS CCS > hub 2-0:1.0: port 2, status 0101, change 0001, 12 Mb/s > hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x101 > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS > usb 2-2: new full speed USB device using ohci_hcd and address 11 > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS > usb 2-2: skipped 1 descriptor after interface > usb 2-2: default language 0x0409 > usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=0 > usb 2-2: Product: HP Integrated Module > usb 2-2: Manufacturer: Broadcom Corp > PM: Adding info for usb:2-2 > usb 2-2: uevent > usb 2-2: usb_probe_device > PM: Adding info for No Bus:usbdev2.11_ep00 > usb 2-2: configuration #1 chosen from 1 choice > usb 2-2: adding 2-2:1.0 (config #1, interface 0) > PM: Adding info for usb:2-2:1.0 > usb 2-2:1.0: uevent > hci_usb 2-2:1.0: usb_probe_interface > hci_usb 2-2:1.0: usb_probe_interface - got id > PM: Adding info for No Bus:hci0 > PM: Adding info for No Bus:usbdev2.11_ep81 > PM: Adding info for No Bus:usbdev2.11_ep82 > PM: Adding info for No Bus:usbdev2.11_ep02 > usb 2-2: adding 2-2:1.1 (config #1, interface 1) > PM: Adding info for usb:2-2:1.1 > usb 2-2:1.1: uevent > PM: Adding info for No Bus:usbdev2.11_ep83 > PM: Adding info for No Bus:usbdev2.11_ep03 > usb 2-2: adding 2-2:1.2 (config #1, interface 2) > PM: Adding info for usb:2-2:1.2 > usb 2-2:1.2: uevent > hci_usb 2-2:1.2: usb_probe_interface > hci_usb 2-2:1.2: usb_probe_interface - got id > PM: Adding info for No Bus:usbdev2.11_ep84 > PM: Adding info for No Bus:usbdev2.11_ep04 > usb 2-2: adding 2-2:1.3 (config #1, interface 3) > PM: Adding info for usb:2-2:1.3 > usb 2-2:1.3: uevent > hci_usb 2-2:1.3: usb_probe_interface > hci_usb 2-2:1.3: usb_probe_interface - got id > PM: Adding info for No Bus:usbdev2.11 > drivers/usb/core/inode.c: creating file '011' > hub 3-0:1.0: state 7 ports 4 chg 0000 evt 0012 > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00010101 CSC PPS CCS > hub 3-0:1.0: port 1, status 0101, change 0001, 12 Mb/s > hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101 > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS > usb 3-1: new full speed USB device using ohci_hcd and address 20 > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS > usb 3-1: ep0 maxpacket = 8 > usb 3-1: default language 0x0409 > usb 3-1: new device strings: Mfr=0, Product=1, SerialNumber=0 > usb 3-1: Product: Fingerprint Sensor > PM: Adding info for usb:3-1 > usb 3-1: uevent > usb 3-1: usb_probe_device > PM: Adding info for No Bus:usbdev3.20_ep00 > usb 3-1: configuration #1 chosen from 1 choice > usb 3-1: adding 3-1:1.0 (config #1, interface 0) > PM: Adding info for usb:3-1:1.0 > usb 3-1:1.0: uevent > PM: Adding info for No Bus:usbdev3.20_ep81 > PM: Adding info for No Bus:usbdev3.20_ep02 > PM: Adding info for No Bus:usbdev3.20 > drivers/usb/core/inode.c: creating file '020' > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [3] = 0x00010301 CSC LSDA PPS CCS > hub 3-0:1.0: port 4, status 0301, change 0001, 1.5 Mb/s > hub 3-0:1.0: debounce: port 4: total 100ms stable 100ms status 0x301 > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [3] = 0x00100303 PRSC LSDA PPS PES CCS > usb 3-4: new low speed USB device using ohci_hcd and address 21 > ohci_hcd 0000:00:13.1: GetStatus roothub.portstatus [3] = 0x00100303 PRSC LSDA PPS PES CCS > usb 3-4: skipped 1 descriptor after interface > usb 3-4: default language 0x0409 > usb 3-4: new device strings: Mfr=1, Product=2, SerialNumber=0 > usb 3-4: Product: USB Receiver > usb 3-4: Manufacturer: Logitech > PM: Adding info for usb:3-4 > usb 3-4: uevent > usb 3-4: usb_probe_device > PM: Adding info for No Bus:usbdev3.21_ep00 > usb 3-4: configuration #1 chosen from 1 choice > usb 3-4: adding 3-4:1.0 (config #1, interface 0) > PM: Adding info for usb:3-4:1.0 > usb 3-4:1.0: uevent > usbhid 3-4:1.0: usb_probe_interface > usbhid 3-4:1.0: usb_probe_interface - got id > INPUT[INPUT] > Field(0) > Physical(GenericDesktop.Pointer) > Usage(8) > Button.0001 > Button.0002 > Button.0003 > Button.0004 > Button.0005 > Button.0006 > Button.0007 > Button.0008 > Logical Minimum(0) > Logical Maximum(1) > Report Size(1) > Report Count(8) > Report Offset(0) > Flags( Variable Absolute ) > Field(1) > Physical(GenericDesktop.Pointer) > Usage(3) > GenericDesktop.X > GenericDesktop.Y > GenericDesktop.Wheel > Logical Minimum(-127) > Logical Maximum(127) > Report Size(8) > Report Count(3) > Report Offset(8) > Flags( Variable Relative ) > Field(2) > Physical(GenericDesktop.Pointer) > Usage(1) > Consumer.HorizontalWheel > Logical Minimum(-127) > Logical Maximum(127) > Report Size(8) > Report Count(1) > Report Offset(32) > Flags( Variable Relative ) > Field(3) > Usage(8) > LED.GenericIndicator > LED.GenericIndicator > LED.GenericIndicator > LED.GenericIndicator > LED.GenericIndicator > LED.GenericIndicator > LED.GenericIndicator > LED.GenericIndicator > Logical Minimum(0) > Logical Maximum(1) > Report Size(1) > Report Count(8) > Report Offset(40) > Flags( Variable Absolute ) > Field(4) > Usage(8) > Button.0009 > Button.000a > Button.000b > Button.000c > Button.000d > Button.000e > Button.000f > Button.0010 > Logical Minimum(0) > Logical Maximum(1) > Report Size(1) > Report Count(8) > Report Offset(48) > Flags( Variable Absolute ) > FEATURE[FEATURE] > Field(0) > Usage(1) > GenericDesktop.MotionWakeup > Logical Minimum(0) > Logical Maximum(1) > Report Size(1) > Report Count(1) > Report Offset(0) > Flags( Variable Absolute NoPrefferedState ) > Mapping: Button.0001 ---> Key.LeftBtn > Mapping: Button.0002 ---> Key.RightBtn > Mapping: Button.0003 ---> Key.MiddleBtn > Mapping: Button.0004 ---> Key.SideBtn > Mapping: Button.0005 ---> Key.ExtraBtn > Mapping: Button.0006 ---> Key.ForwardBtn > Mapping: Button.0007 ---> Key.BackBtn > Mapping: Button.0008 ---> Key.TaskBtn > Mapping: GenericDesktop.X ---> Relative.X > Mapping: GenericDesktop.Y ---> Relative.Y > Mapping: GenericDesktop.Wheel ---> Relative.Wheel > Mapping: Consumer.HorizontalWheel ---> Relative.HWheel > Mapping: LED.GenericIndicator ---> LED.Misc > Mapping: LED.GenericIndicator ---> LED.? > Mapping: LED.GenericIndicator ---> LED.? > Mapping: LED.GenericIndicator ---> LED.? > Mapping: LED.GenericIndicator ---> LED.? > Mapping: LED.GenericIndicator ---> LED.? > Mapping: LED.GenericIndicator ---> LED.? > Mapping: LED.GenericIndicator ---> LED.? > Mapping: Button.0009 ---> Key.? > Mapping: Button.000a ---> Key.? > Mapping: Button.000b ---> Key.? > Mapping: Button.000c ---> Key.? > Mapping: Button.000d ---> Key.? > Mapping: Button.000e ---> Key.? > Mapping: Button.000f ---> Key.? > Mapping: Button.0010 ---> Key.? > input: Logitech USB Receiver as /class/input/input16 > hid-pidff: starting pid init > hid-pidff: not a PID device, no output report > input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:13.1-4 > PM: Adding info for No Bus:usbdev3.21_ep81 > PM: Adding info for No Bus:usbdev3.21 > drivers/usb/core/inode.c: creating file '021' > hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0100 > hub 2-0:1.0: state 7 ports 4 chg 0000 evt 0004 > hub 3-0:1.0: state 7 ports 4 chg 0000 evt 0002 > usb 3-1: usb auto-suspend > SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 > hub 1-0:1.0: hub_suspend > usb usb1: usb auto-suspend > SoftMAC: Scanning finished: scanned 14 channels starting with channel 1 > PM: Removing info for No Bus:hw_random > bcm43xx: Radio turned off > bcm43xx: DMA-32 0x0200 (RX) max used slots: 0/64 > bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512 > bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512 > bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512 > bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512 > bcm43xx: DMA-32 0x0220 (TX) max used slots: 56/512 > bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512 > PM: Adding info for No Bus:0000:30:00.0 > PM: Removing info for No Bus:0000:30:00.0 > PM: Adding info for No Bus:0000:30:00.0 > PM: Removing info for No Bus:0000:30:00.0 > PM: Adding info for No Bus:0000:30:00.0 > PM: Removing info for No Bus:0000:30:00.0 > PM: Adding info for No Bus:0000:30:00.0 > PM: Removing info for No Bus:0000:30:00.0 > bcm43xx: IRQ_READY timeout > bcm43xx: core_up for active 802.11 core failed (-19) I never tried suspend to disk with the driver. Larry, an idea why the microcode doesn't respond? -- Greetings Michael. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 14:14 ` Michael Buesch @ 2007-02-11 14:41 ` Johannes Berg 2007-02-11 14:45 ` Rafael J. Wysocki 2007-02-11 15:59 ` Larry Finger 1 sibling, 1 reply; 26+ messages in thread From: Johannes Berg @ 2007-02-11 14:41 UTC (permalink / raw) To: Michael Buesch Cc: Rafael J. Wysocki, bcm43xx-dev, Larry Finger, wireless, John Linville [-- Attachment #1: Type: text/plain, Size: 312 bytes --] On Sun, 2007-02-11 at 15:14 +0100, Michael Buesch wrote: > > bcm43xx: IRQ_READY timeout > > bcm43xx: core_up for active 802.11 core failed (-19) > > I never tried suspend to disk with the driver. > Larry, an idea why the microcode doesn't respond? Rafael, is bcm43xx built in or modular? johannes [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 190 bytes --] ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 14:41 ` Johannes Berg @ 2007-02-11 14:45 ` Rafael J. Wysocki 2007-02-11 14:48 ` Johannes Berg 0 siblings, 1 reply; 26+ messages in thread From: Rafael J. Wysocki @ 2007-02-11 14:45 UTC (permalink / raw) To: Johannes Berg Cc: Michael Buesch, bcm43xx-dev, Larry Finger, wireless, John Linville On Sunday, 11 February 2007 15:41, Johannes Berg wrote: > On Sun, 2007-02-11 at 15:14 +0100, Michael Buesch wrote: > > > > bcm43xx: IRQ_READY timeout > > > bcm43xx: core_up for active 802.11 core failed (-19) > > > > I never tried suspend to disk with the driver. > > Larry, an idea why the microcode doesn't respond? > > Rafael, is bcm43xx built in or modular? Modular. Otherwise I wouldn't have been able to reload it. :-) Rafael ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 14:45 ` Rafael J. Wysocki @ 2007-02-11 14:48 ` Johannes Berg 0 siblings, 0 replies; 26+ messages in thread From: Johannes Berg @ 2007-02-11 14:48 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Michael Buesch, bcm43xx-dev, Larry Finger, wireless, John Linville [-- Attachment #1: Type: text/plain, Size: 715 bytes --] On Sun, 2007-02-11 at 15:45 +0100, Rafael J. Wysocki wrote: > On Sunday, 11 February 2007 15:41, Johannes Berg wrote: > > On Sun, 2007-02-11 at 15:14 +0100, Michael Buesch wrote: > > > > > > bcm43xx: IRQ_READY timeout > > > > bcm43xx: core_up for active 802.11 core failed (-19) > > > > > > I never tried suspend to disk with the driver. > > > Larry, an idea why the microcode doesn't respond? > > > > Rafael, is bcm43xx built in or modular? > > Modular. Otherwise I wouldn't have been able to reload it. :-) Guess I should've paid more attention. No idea what causes this then. Could you try increasing the timeout loop for that wait? (search for the message in the source code) johannes [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 190 bytes --] ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 14:14 ` Michael Buesch 2007-02-11 14:41 ` Johannes Berg @ 2007-02-11 15:59 ` Larry Finger 2007-02-11 16:03 ` Michael Buesch 2007-02-12 0:50 ` Rafael J. Wysocki 1 sibling, 2 replies; 26+ messages in thread From: Larry Finger @ 2007-02-11 15:59 UTC (permalink / raw) To: Michael Buesch; +Cc: Rafael J. Wysocki, bcm43xx-dev, wireless, John Linville Michael Buesch wrote: > On Sunday 11 February 2007 15:02, Rafael J. Wysocki wrote: >> PM: Removing info for No Bus:0000:30:00.0 >> bcm43xx: IRQ_READY timeout >> bcm43xx: core_up for active 802.11 core failed (-19) > > I never tried suspend to disk with the driver. This implies that suspend to RAM works. Is that true? > Larry, an idea why the microcode doesn't respond? Is this code snippet supposed to keep the firmware loaded when the system is suspended? bcm->firmware_norelease = 1; bcm43xx_free_board(bcm); bcm->firmware_norelease = 0; If so, that may be the problem. What would force it to be reloaded when resuming after a suspend to disk and subsequent power off? That would certainly explain why a reload is successful. Is there a volatile location that would safely indicate that the firmware is not good? Perhaps, we need to bite the bullet and reload the firmware after every resume. The patch below should do that. I am also working on a case where the user has troubles with a suspend to disk from Windows followed by a reboot to Linux, and warm reboots from Windows to Linux. In these cases, he gets a firmware file-format error; however, his firmware is fine from a cold boot. Larry Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c =================================================================== --- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c +++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c @@ -4296,6 +4297,7 @@ static int bcm43xx_resume(struct pci_dev printk(KERN_ERR PFX "Resume failed!\n"); return err; } + bcm43xx_request_firmware(bcm); netif_device_attach(net_dev); dprintk(KERN_INFO PFX "Device resumed.\n"); ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 15:59 ` Larry Finger @ 2007-02-11 16:03 ` Michael Buesch 2007-02-11 16:16 ` Michael Buesch 2007-02-11 16:17 ` Larry Finger 2007-02-12 0:50 ` Rafael J. Wysocki 1 sibling, 2 replies; 26+ messages in thread From: Michael Buesch @ 2007-02-11 16:03 UTC (permalink / raw) To: Larry Finger; +Cc: Rafael J. Wysocki, bcm43xx-dev, wireless, John Linville On Sunday 11 February 2007 16:59, Larry Finger wrote: > Michael Buesch wrote: > > On Sunday 11 February 2007 15:02, Rafael J. Wysocki wrote: > >> PM: Removing info for No Bus:0000:30:00.0 > >> bcm43xx: IRQ_READY timeout > >> bcm43xx: core_up for active 802.11 core failed (-19) > > > > I never tried suspend to disk with the driver. > > This implies that suspend to RAM works. Is that true? No. > > Larry, an idea why the microcode doesn't respond? > > Is this code snippet supposed to keep the firmware loaded when the system is suspended? Well, eh, no. Don't confuse suspend-to-ram with suspend-to-disk. On suspend-to-disk the kernel is (mostly) reloaded as usual. Just userspace is restored. So the driver enters through the probe routine on resume from disk. -- Greetings Michael. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 16:03 ` Michael Buesch @ 2007-02-11 16:16 ` Michael Buesch 2007-02-11 16:17 ` Larry Finger 1 sibling, 0 replies; 26+ messages in thread From: Michael Buesch @ 2007-02-11 16:16 UTC (permalink / raw) To: Larry Finger; +Cc: Rafael J. Wysocki, bcm43xx-dev, wireless, John Linville On Sunday 11 February 2007 17:03, Michael Buesch wrote: > On Sunday 11 February 2007 16:59, Larry Finger wrote: > > Michael Buesch wrote: > > > On Sunday 11 February 2007 15:02, Rafael J. Wysocki wrote: > > >> PM: Removing info for No Bus:0000:30:00.0 > > >> bcm43xx: IRQ_READY timeout > > >> bcm43xx: core_up for active 802.11 core failed (-19) > > > > > > I never tried suspend to disk with the driver. > > > > This implies that suspend to RAM works. Is that true? > > No. > > > > Larry, an idea why the microcode doesn't respond? > > > > Is this code snippet supposed to keep the firmware loaded when the system is suspended? > > Well, eh, no. Don't confuse suspend-to-ram with suspend-to-disk. > On suspend-to-disk the kernel is (mostly) reloaded as usual. > Just userspace is restored. > So the driver enters through the probe routine on resume from disk. I've been told this is wrong. Well, ok. Anyway. I don't think we need to re-request the fw, as it's restored, too. Can you try bcm43xx-d80211 from my tree? There it reinitializes the device completely on resume. So it might work there. -- Greetings Michael. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 16:03 ` Michael Buesch 2007-02-11 16:16 ` Michael Buesch @ 2007-02-11 16:17 ` Larry Finger 1 sibling, 0 replies; 26+ messages in thread From: Larry Finger @ 2007-02-11 16:17 UTC (permalink / raw) To: Michael Buesch; +Cc: Rafael J. Wysocki, bcm43xx-dev, wireless, John Linville Michael Buesch wrote: > On Sunday 11 February 2007 16:59, Larry Finger wrote: >> Michael Buesch wrote: >>> On Sunday 11 February 2007 15:02, Rafael J. Wysocki wrote: >>>> PM: Removing info for No Bus:0000:30:00.0 >>>> bcm43xx: IRQ_READY timeout >>>> bcm43xx: core_up for active 802.11 core failed (-19) >>> I never tried suspend to disk with the driver. >> This implies that suspend to RAM works. Is that true? > > No. > >>> Larry, an idea why the microcode doesn't respond? >> Is this code snippet supposed to keep the firmware loaded when the system is suspended? > > Well, eh, no. Don't confuse suspend-to-ram with suspend-to-disk. > On suspend-to-disk the kernel is (mostly) reloaded as usual. > Just userspace is restored. > So the driver enters through the probe routine on resume from disk. > Does it then call the resume entry? Rafael's dmesg output has the line "bcm43xx: Resuming..." that only gets printed if the resume routine was called. Larry ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-11 15:59 ` Larry Finger 2007-02-11 16:03 ` Michael Buesch @ 2007-02-12 0:50 ` Rafael J. Wysocki 2007-02-12 1:18 ` Larry Finger 1 sibling, 1 reply; 26+ messages in thread From: Rafael J. Wysocki @ 2007-02-12 0:50 UTC (permalink / raw) To: Larry Finger; +Cc: Michael Buesch, bcm43xx-dev, wireless, John Linville On Sunday, 11 February 2007 16:59, Larry Finger wrote: > Michael Buesch wrote: > > On Sunday 11 February 2007 15:02, Rafael J. Wysocki wrote: > >> PM: Removing info for No Bus:0000:30:00.0 > >> bcm43xx: IRQ_READY timeout > >> bcm43xx: core_up for active 802.11 core failed (-19) > > > > I never tried suspend to disk with the driver. > > This implies that suspend to RAM works. Is that true? > > > Larry, an idea why the microcode doesn't respond? > > Is this code snippet supposed to keep the firmware loaded when the system is suspended? > > bcm->firmware_norelease = 1; > bcm43xx_free_board(bcm); > bcm->firmware_norelease = 0; > > If so, that may be the problem. What would force it to be reloaded when resuming after a suspend to > disk and subsequent power off? That would certainly explain why a reload is successful. Is there a > volatile location that would safely indicate that the firmware is not good? Perhaps, we need to bite > the bullet and reload the firmware after every resume. The patch below should do that. > > I am also working on a case where the user has troubles with a suspend to disk from Windows followed > by a reboot to Linux, and warm reboots from Windows to Linux. In these cases, he gets a firmware > file-format error; however, his firmware is fine from a cold boot. > > Larry > > Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c > =================================================================== > --- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c > +++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c > @@ -4296,6 +4297,7 @@ static int bcm43xx_resume(struct pci_dev > printk(KERN_ERR PFX "Resume failed!\n"); > return err; > } > + bcm43xx_request_firmware(bcm); > netif_device_attach(net_dev); > > dprintk(KERN_INFO PFX "Device resumed.\n"); It doesn't help in my case. The behavior is similar to that without the patch, but also with the patch it loses the association entirely. Greetings, Rafael ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-12 0:50 ` Rafael J. Wysocki @ 2007-02-12 1:18 ` Larry Finger 2007-02-12 20:48 ` Rafael J. Wysocki 0 siblings, 1 reply; 26+ messages in thread From: Larry Finger @ 2007-02-12 1:18 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: wireless, bcm43xx-dev, Michael Buesch, John Linville Rafael J. Wysocki wrote: > > It doesn't help in my case. The behavior is similar to that without the patch, > but also with the patch it loses the association entirely. Thanks for trying. Do you have this patch installed? If you do, please try increasing the 100 to 200. Larry --- Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx.h =================================================================== --- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx.h +++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx.h @@ -21,7 +21,7 @@ #define PFX KBUILD_MODNAME ": " #define BCM43xx_SWITCH_CORE_MAX_RETRIES 50 -#define BCM43xx_IRQWAIT_MAX_RETRIES 50 +#define BCM43xx_IRQWAIT_MAX_RETRIES 100 #define BCM43xx_IO_SIZE 8192 ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-12 1:18 ` Larry Finger @ 2007-02-12 20:48 ` Rafael J. Wysocki 2007-02-12 22:20 ` Larry Finger 0 siblings, 1 reply; 26+ messages in thread From: Rafael J. Wysocki @ 2007-02-12 20:48 UTC (permalink / raw) To: Larry Finger; +Cc: wireless, bcm43xx-dev, Michael Buesch, John Linville On Monday, 12 February 2007 02:18, Larry Finger wrote: > Rafael J. Wysocki wrote: > > > > It doesn't help in my case. The behavior is similar to that without the patch, > > but also with the patch it loses the association entirely. > > Thanks for trying. > > Do you have this patch installed? If you do, please try increasing the 100 to 200. Hm, but it wouldn't help to get the microcode to respond after the resume ... I'm still thinking the problem is with the firmware. Where exactly is it stored? > > > Larry > --- > Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx.h > =================================================================== > --- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx.h > +++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx.h > @@ -21,7 +21,7 @@ > #define PFX KBUILD_MODNAME ": " > > #define BCM43xx_SWITCH_CORE_MAX_RETRIES 50 > -#define BCM43xx_IRQWAIT_MAX_RETRIES 50 > +#define BCM43xx_IRQWAIT_MAX_RETRIES 100 > > #define BCM43xx_IO_SIZE 8192 > Greetings, Rafael ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-12 20:48 ` Rafael J. Wysocki @ 2007-02-12 22:20 ` Larry Finger 2007-02-12 23:08 ` Rafael J. Wysocki 0 siblings, 1 reply; 26+ messages in thread From: Larry Finger @ 2007-02-12 22:20 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: wireless, bcm43xx-dev, Michael Buesch, John Linville Rafael J. Wysocki wrote: > On Monday, 12 February 2007 02:18, Larry Finger wrote: >> Rafael J. Wysocki wrote: >>> It doesn't help in my case. The behavior is similar to that without the patch, >>> but also with the patch it loses the association entirely. >> Thanks for trying. >> >> Do you have this patch installed? If you do, please try increasing the 100 to 200. > > Hm, but it wouldn't help to get the microcode to respond after the resume ... Yes it would. That count is how long the system waits for the firmware to respond. > I'm still thinking the problem is with the firmware. Where exactly is it > stored? In the memory of the microprocessor on the card. Please do what I asked. Larry ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-12 22:20 ` Larry Finger @ 2007-02-12 23:08 ` Rafael J. Wysocki 2007-02-12 23:18 ` Larry Finger 2007-02-12 23:24 ` Michael Buesch 0 siblings, 2 replies; 26+ messages in thread From: Rafael J. Wysocki @ 2007-02-12 23:08 UTC (permalink / raw) To: Larry Finger; +Cc: wireless, bcm43xx-dev, Michael Buesch, John Linville On Monday, 12 February 2007 23:20, Larry Finger wrote: > Rafael J. Wysocki wrote: > > On Monday, 12 February 2007 02:18, Larry Finger wrote: > >> Rafael J. Wysocki wrote: > >>> It doesn't help in my case. The behavior is similar to that without the patch, > >>> but also with the patch it loses the association entirely. > >> Thanks for trying. > >> > >> Do you have this patch installed? If you do, please try increasing the 100 to 200. > > > > Hm, but it wouldn't help to get the microcode to respond after the resume ... > > Yes it would. That count is how long the system waits for the firmware to respond. > > > I'm still thinking the problem is with the firmware. Where exactly is it > > stored? > > In the memory of the microprocessor on the card. > > Please do what I asked. With or without the previous patch? Rafael ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-12 23:08 ` Rafael J. Wysocki @ 2007-02-12 23:18 ` Larry Finger 2007-02-12 23:24 ` Michael Buesch 1 sibling, 0 replies; 26+ messages in thread From: Larry Finger @ 2007-02-12 23:18 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: wireless, bcm43xx-dev, Michael Buesch, John Linville Rafael J. Wysocki wrote: > On Monday, 12 February 2007 23:20, Larry Finger wrote: >> Rafael J. Wysocki wrote: >>> On Monday, 12 February 2007 02:18, Larry Finger wrote: >>>> Rafael J. Wysocki wrote: >>>>> It doesn't help in my case. The behavior is similar to that without the patch, >>>>> but also with the patch it loses the association entirely. >>>> Thanks for trying. >>>> >>>> Do you have this patch installed? If you do, please try increasing the 100 to 200. >>> Hm, but it wouldn't help to get the microcode to respond after the resume ... >> Yes it would. That count is how long the system waits for the firmware to respond. >> >>> I'm still thinking the problem is with the firmware. Where exactly is it >>> stored? >> In the memory of the microprocessor on the card. >> >> Please do what I asked. > > With or without the previous patch? With the change to BCM43xx_IRQWAIT_MAX_RETRIES, but not the one that tries to reload the firmware. Larry ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-12 23:08 ` Rafael J. Wysocki 2007-02-12 23:18 ` Larry Finger @ 2007-02-12 23:24 ` Michael Buesch 2007-02-13 16:25 ` Rafael J. Wysocki 1 sibling, 1 reply; 26+ messages in thread From: Michael Buesch @ 2007-02-12 23:24 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Larry Finger, wireless, bcm43xx-dev, John Linville On Tuesday 13 February 2007 00:08, Rafael J. Wysocki wrote: > On Monday, 12 February 2007 23:20, Larry Finger wrote: > > Rafael J. Wysocki wrote: > > > On Monday, 12 February 2007 02:18, Larry Finger wrote: > > >> Rafael J. Wysocki wrote: > > >>> It doesn't help in my case. The behavior is similar to that without the patch, > > >>> but also with the patch it loses the association entirely. > > >> Thanks for trying. > > >> > > >> Do you have this patch installed? If you do, please try increasing the 100 to 200. > > > > > > Hm, but it wouldn't help to get the microcode to respond after the resume ... > > > > Yes it would. That count is how long the system waits for the firmware to respond. > > > > > I'm still thinking the problem is with the firmware. Where exactly is it > > > stored? > > > > In the memory of the microprocessor on the card. > > > > Please do what I asked. > > With or without the previous patch? Both, please. -- Greetings Michael. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] bcm43xx: Fix loss of association after resume 2007-02-12 23:24 ` Michael Buesch @ 2007-02-13 16:25 ` Rafael J. Wysocki 0 siblings, 0 replies; 26+ messages in thread From: Rafael J. Wysocki @ 2007-02-13 16:25 UTC (permalink / raw) To: Michael Buesch; +Cc: Larry Finger, wireless, bcm43xx-dev, John Linville On Tuesday, 13 February 2007 00:24, Michael Buesch wrote: > On Tuesday 13 February 2007 00:08, Rafael J. Wysocki wrote: > > On Monday, 12 February 2007 23:20, Larry Finger wrote: > > > Rafael J. Wysocki wrote: > > > > On Monday, 12 February 2007 02:18, Larry Finger wrote: > > > >> Rafael J. Wysocki wrote: > > > >>> It doesn't help in my case. The behavior is similar to that without the patch, > > > >>> but also with the patch it loses the association entirely. > > > >> Thanks for trying. > > > >> > > > >> Do you have this patch installed? If you do, please try increasing the 100 to 200. > > > > > > > > Hm, but it wouldn't help to get the microcode to respond after the resume ... > > > > > > Yes it would. That count is how long the system waits for the firmware to respond. > > > > > > > I'm still thinking the problem is with the firmware. Where exactly is it > > > > stored? > > > > > > In the memory of the microprocessor on the card. > > > > > > Please do what I asked. > > > > With or without the previous patch? > > Both, please. It doesn't help in either case. I get albercik:~ # ifconfig eth1 down albercik:~ # ifconfig eth1 up SIOCSIFFLAGS: No such device in both cases. I think the problem is that the firmware is not present and requesting it doesn't work for some reason. Greetings, Rafael ^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2007-02-13 16:29 UTC | newest] Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2007-02-09 16:18 [PATCH] bcm43xx: Fix loss of association after resume Larry Finger 2007-02-09 16:18 ` Larry Finger 2007-02-09 16:53 ` Michael Buesch 2007-02-09 16:53 ` Michael Buesch 2007-02-10 17:11 ` Rafael J. Wysocki 2007-02-10 17:11 ` Rafael J. Wysocki 2007-02-10 20:33 ` Larry Finger 2007-02-11 12:56 ` Rafael J. Wysocki 2007-02-11 13:07 ` Michael Buesch 2007-02-11 14:02 ` Rafael J. Wysocki 2007-02-11 14:14 ` Michael Buesch 2007-02-11 14:41 ` Johannes Berg 2007-02-11 14:45 ` Rafael J. Wysocki 2007-02-11 14:48 ` Johannes Berg 2007-02-11 15:59 ` Larry Finger 2007-02-11 16:03 ` Michael Buesch 2007-02-11 16:16 ` Michael Buesch 2007-02-11 16:17 ` Larry Finger 2007-02-12 0:50 ` Rafael J. Wysocki 2007-02-12 1:18 ` Larry Finger 2007-02-12 20:48 ` Rafael J. Wysocki 2007-02-12 22:20 ` Larry Finger 2007-02-12 23:08 ` Rafael J. Wysocki 2007-02-12 23:18 ` Larry Finger 2007-02-12 23:24 ` Michael Buesch 2007-02-13 16:25 ` Rafael J. Wysocki
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.