Ticket #2267 (closed defect: fixed)
[wifi] kernel oops when starting wpa_supplicant
| Reported by: | tilman2 | Owned by: | openmoko-devel |
|---|---|---|---|
| Priority: | high | Milestone: | stable-kernel-2009.1 |
| Component: | unknown | Version: | unspecified |
| Severity: | normal | Keywords: | wpa_supplicant wlan oops |
| Cc: | Blocked By: | ||
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | yes | PatchReviewResult: | positive |
| Reproducible: |
Description
I'm running shr-unstable from April 9th:
http://build.shr-project.org/shr-unstable/images/om-gta02/openmoko-shr-lite-image-glibc-ipk--20090409-om-gta02.rootfs.jffs2
http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-2.6.28-oe1+gitr119783+901d73fe51f33032b34b2ae5612eb863ec90532a-r3.1-om-gta02.bin
The kernel version reported is 2.6.29-rc3.
When starting wpa_supplicant, the kernel oopses. I'll attach the output of dmesg and my wpa_supplicant.conf.
Attachments
Change History
comment:1 Changed 4 years ago by mwester@…
The following patch seems to resolve this; I really can't say if this is the correct resolution, but it seems to work for me:
diff --git a/drivers/ar6000/ar6000/wireless_ext.c b/drivers/ar6000/ar6000/wireless_ext.c
index d9a5920..ecba5c9 100644
--- a/drivers/ar6000/ar6000/wireless_ext.c
+++ b/drivers/ar6000/ar6000/wireless_ext.c
@@ -976,6 +976,14 @@ static int ar6000_ioctl_giwpower(struct net_device *dev,
{
AR_SOFTC_T *ar = (AR_SOFTC_T *)netdev_priv(dev);
+ if (ar->arWlanState == WLAN_DISABLED) {
+ return -EIO;
+ }
+
+ if (ar->arWmiReady == FALSE) {
+ return -EIO;
+ }
+
return wmi_get_power_mode_cmd(ar->arWmi);
}
comment:2 Changed 4 years ago by arhuaco
- Priority changed from normal to high
- Milestone set to stable-kernel-2009.1
comment:3 follow-up: ↓ 4 Changed 4 years ago by arhuaco
- Keywords wpa_supplicant wlan oops added
- HasPatchForReview set
Mwester, it seems like a good solution (until someone tell us otherwise). Can I create a patch with your fix and add a Signed-off-by for you with your email address?
comment:4 in reply to: ↑ 3 Changed 4 years ago by mwester@…
Replying to arhuaco:
Mwester, it seems like a good solution (until someone tell us otherwise). Can I create a patch with your fix and add a Signed-off-by for you with your email address?
Certainly; we can back it out if there is a "more correct" way to solve this.
comment:5 Changed 4 years ago by arhuaco
- Status changed from new to closed
- PatchReviewResult set to positive
- Resolution set to fixed
Commited. Closing bug.
http://git.openmoko.org/?p=kernel.git;a=commit;h=2bea5c68313577b214b872b0edc5968db0cf3b68

output of dmesg after the oops