Closed
Bug 819603
Opened 12 years ago
Closed 12 years ago
Booting on Panda often fails with wpa_driver_nl80211_driver_cmd: Unsupported command SCAN-ACTIVE
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jgriffin, Unassigned)
References
Details
Booting B2G on the panda often fails with the message:
I/wpa_supplicant( 1398): wpa_driver_nl80211_driver_cmd: Unsupported command SCAN-ACTIVE
D/wpa_supplicant( 1398): WPS: Building WPS IE for Probe Request
D/wpa_supplicant( 1398): WPS: * Version (hardcoded 0x10)
D/wpa_supplicant( 1398): WPS: * Request Type
D/wpa_supplicant( 1398): WPS: * Config Methods (2388)
D/wpa_supplicant( 1398): WPS: * UUID-E
D/wpa_supplicant( 1398): WPS: * Primary Device Type
D/wpa_supplicant( 1398): WPS: * RF Bands (3)
D/wpa_supplicant( 1398): WPS: * Association State
D/wpa_supplicant( 1398): WPS: * Configuration Error (0)
D/wpa_supplicant( 1398): WPS: * Device Password ID (0)
D/wpa_supplicant( 1398): WPS: * Manufacturer
D/wpa_supplicant( 1398): WPS: * Model Name
D/wpa_supplicant( 1398): WPS: * Model Number
D/wpa_supplicant( 1398): WPS: * Device Name
D/wpa_supplicant( 1398): WPS: * Version2 (0x20)
D/wpa_supplicant( 1398): Scan requested (ret=0) - scan timeout 10 seconds
D/wpa_supplicant( 1398): nl80211: Event message available
D/wpa_supplicant( 1398): nl80211: Scan trigger
I/wpa_supplicant( 1398): wpa_driver_nl80211_driver_cmd: Unsupported command SCAN-ACTIVE
As soon as this appears in logcat, the panda reboots itself. It will repeat this cycle for somewhere from 1 to 10 times before finally coming up correctly.
See also bug 817730.
Comment 1•12 years ago
|
||
Normally, the unsupported command should not be a problem. I also see it in logcat.
We just reverted some kernel and libc changes. Could you try again and see if anything has changed?
Reporter | ||
Comment 2•12 years ago
|
||
I am still seeing nearly the same behavior, except that I no longer see
I/wpa_supplicant( 1398): wpa_driver_nl80211_driver_cmd: Unsupported command SCAN-ACTIVE
in logcat; the last line is now:
D/wpa_supplicant( 1398): nl80211: Scan trigger
In the serial output, I see these errors (from three different instances) right before the panda restarts itself:
[ 45.241302] omapdss HDMI: ENTER hdmi_display_enable
[ 45.355163] omapdss DISPC error: timeout waiting for EVSYNC
[ 46.248321] misc dsscomp: [eca2ac00] ignoring set failure -22
[ 41.592712] omapdss HDMI: Enter omapdss_hdmi_display_set_mode
[ 41.609741] omapdss HDMI: Enter hdmi_display_disable
[ 41.623199] hdmi: clearing EDID info
[ 41.628204] omapdss HDMI: ENTER hdmi_display_enable
[ 41.736175] omapdss DISPC error: timeout waiting for EVSYNC
[ 42.076690] misc dsscomp: [ecffac00] ignoring set failure -22
[ 42.086029] mgr_blank while GO is set
[ 45.949523] hdmi: clearing EDID info
[ 45.954376] omapdss HDMI: ENTER hdmi_display_enable
[ 46.066040] omapdss DISPC error: timeout waiting for EVSYNC
[ 46.394500] misc dsscomp: [ecf2ec00] ignoring set failure -22
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Jonathan Griffin (:jgriffin) from comment #2)
>
> [ 45.949523] hdmi: clearing EDID info
>
> [ 45.954376] omapdss HDMI: ENTER hdmi_display_enable
>
> [ 46.066040] omapdss DISPC error: timeout waiting for EVSYNC
>
> [ 46.394500] misc dsscomp: [ecf2ec00] ignoring set failure -22
I also see this error when it finally boots correctly.
Comment 4•12 years ago
|
||
All these errors are not much of a problem. I see them as well. In fact, they are even in the kernels that come from upstream.
Reporter | ||
Comment 5•12 years ago
|
||
Seems to have been fixed since bug 817730 was addressed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•