* Re: [PATCH] eeepc-laptop: fix hot-unplug on resume
From: Alan Jenkins @ 2009-06-29 14:22 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Corentin Chary, linux acpi, linux-kernel,
linux-wireless@vger.kernel.org
In-Reply-To: <200906291616.57440.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> On Monday 29 June 2009, Alan Jenkins wrote:
>
>> The patch below fixes a regression introduced by the rfkill rewrite.
>> Please consider it for inclusion in 2.6.31 via the ACPI tree.
>>
>
> Is there a Bugzilla # for this regression?
>
> Rafael
>
No.
I found it in testing, a few days after I'd submitted the change myself :-/.
Thanks
Alan
^ permalink raw reply
* Re: [PATCH] eeepc-laptop: fix hot-unplug on resume
From: Rafael J. Wysocki @ 2009-06-29 14:16 UTC (permalink / raw)
To: Alan Jenkins
Cc: Corentin Chary, linux acpi, linux-kernel,
linux-wireless@vger.kernel.org
In-Reply-To: <4A48A196.3060409@tuffmail.co.uk>
On Monday 29 June 2009, Alan Jenkins wrote:
> The patch below fixes a regression introduced by the rfkill rewrite.
> Please consider it for inclusion in 2.6.31 via the ACPI tree.
Is there a Bugzilla # for this regression?
Rafael
> -------------------->
>
> From d0265f0bfe63086816d61c69ee4b2dc4cb491d06 Mon Sep 17 00:00:00 2001
> From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
> Date: Mon, 29 Jun 2009 09:40:07 +0100
> Subject: [PATCH] eeepc-laptop: fix hot-unplug on resume
>
> OOPS on resume when the wireless adaptor is disabled during suspend was
> introduced by "eeepc-laptop: read rfkill soft-blocked state on resume".
>
> Unable to handle kernel NULL pointer dereference
>
> Process s2disk
> Tainted: G W
> IP: klist_put
>
> Call trace:
> ? klist_del
> ? device_del
> ? device_unregister
> ? pci_stop_dev
> ? pci_stop_bus
> ? pci_remove_device
> ? eeepc_rfkill_hotplug [eeepc_laptop]
> ? eeepc_hotk_resume [eeepc_laptop]
> ? acpi_device_resume
> ? device_resume
> ? hibernation_snapshot
>
> It appears the PCI device is removed twice. The eeepc_rfkill_hotplug()
> call from the resume handler is racing against the call from the ACPI
> notifier callback. The ACPI notification is triggered by the resume
> handler when it refreshes the value of CM_ASL_WLAN.
>
> The fix is to serialize hotplug calls using a workqueue.
>
> Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
> ---
> drivers/platform/x86/eeepc-laptop.c | 9 ++++++---
> 1 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/platform/x86/eeepc-laptop.c b/drivers/platform/x86/eeepc-laptop.c
> index ec560f1..222ffb8 100644
> --- a/drivers/platform/x86/eeepc-laptop.c
> +++ b/drivers/platform/x86/eeepc-laptop.c
> @@ -143,6 +143,7 @@ struct eeepc_hotk {
> struct rfkill *bluetooth_rfkill;
> struct rfkill *wwan3g_rfkill;
> struct hotplug_slot *hotplug_slot;
> + struct work_struct hotplug_work;
> };
>
> /* The actual device the driver binds to */
> @@ -660,7 +661,7 @@ static int eeepc_get_adapter_status(struct hotplug_slot *hotplug_slot,
> return 0;
> }
>
> -static void eeepc_rfkill_hotplug(void)
> +static void eeepc_hotplug_work(struct work_struct *work)
> {
> struct pci_dev *dev;
> struct pci_bus *bus = pci_find_bus(0, 1);
> @@ -701,7 +702,7 @@ static void eeepc_rfkill_notify(acpi_handle handle, u32 event, void *data)
> if (event != ACPI_NOTIFY_BUS_CHECK)
> return;
>
> - eeepc_rfkill_hotplug();
> + schedule_work(&ehotk->hotplug_work);
> }
>
> static void eeepc_hotk_notify(struct acpi_device *device, u32 event)
> @@ -892,7 +893,7 @@ static int eeepc_hotk_resume(struct acpi_device *device)
>
> rfkill_set_sw_state(ehotk->wlan_rfkill, wlan != 1);
>
> - eeepc_rfkill_hotplug();
> + schedule_work(&ehotk->hotplug_work);
> }
>
> if (ehotk->bluetooth_rfkill)
> @@ -1093,6 +1094,8 @@ static int eeepc_rfkill_init(struct device *dev)
> {
> int result = 0;
>
> + INIT_WORK(&ehotk->hotplug_work, eeepc_hotplug_work);
> +
> eeepc_register_rfkill_notifier("\\_SB.PCI0.P0P6");
> eeepc_register_rfkill_notifier("\\_SB.PCI0.P0P7");
^ permalink raw reply
* Re: Using a Debian box as an AP with wireless testing and hostapd
From: Javier Gálvez Guerrero @ 2009-06-29 14:05 UTC (permalink / raw)
To: Pavel Roskin; +Cc: linux-wireless
In-Reply-To: <1246277392.21239.6.camel@mj>
Hi Pavel,
Thanks a lot for your answer. I successfully uninstalled the
compat-wireless package and no it is running properly. Anyway, I'm
experiencing a problem while configuring the box as a DHCP server. I
will tell you my problem, but if you consider this is not the place to
discuss such issue I will understand.
I configured dhcpd like this:
--> /etc/dhcp3/dhcpd.conf:Jun 29 16:01:12 faye dhcpd: Wrote 0 leases
to leases file.
Jun 29 16:01:12 faye dhcpd:
Jun 29 16:01:12 faye dhcpd: No subnet declaration for wlan0 (0.0.0.0).
Jun 29 16:01:12 faye dhcpd: ** Ignoring requests on wlan0. If this is not what
Jun 29 16:01:12 faye dhcpd: you want, please write a subnet declaration
Jun 29 16:01:12 faye dhcpd: in your dhcpd.conf file for the network segment
Jun 29 16:01:12 faye dhcpd: to which interface wlan0 is attached. **
Jun 29 16:01:12 faye dhcpd:
Jun 29 16:01:12 faye dhcpd:
Jun 29 16:01:12 faye dhcpd: Not configured to listen on any interfaces!
ddns-update-style none;
option domain-name-servers 147.83.2.3, 147.83.2.10;
default-lease-time 86400;
max-lease-time 604800;
authoritative;
subnet 192.168.3.0 netmask 255.255.255.0 {
range 192.168.3.2 192.168.3.254;
option domain-name-servers 147.83.2.3,147.83.2.10;
option routers 192.168.3.1;
option broadcast-address 192.168.3.255;
default-lease-time 100000;
max-lease-time 100000;
}
--> /etc/default/dhcp3-server:
# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/dhcp3-server by the maintainer scripts
#
# This is a POSIX shell fragment
#
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES="wlan0"
AFAIK, I just need this to configure the DHCP server in my box. Next,
I should configure some NATting with iptables. However, when issuing
/etc/init.d/dhcp3-server start I get this message:
faye:/home/dulceangustia# /etc/init.d/dhcp3-server start
Starting DHCP server: dhcpd3check syslog for diagnostics. failed!
failed!
And in /var/log/syslog I see:
Jun 29 16:01:12 faye dhcpd: Wrote 0 leases to leases file.
Jun 29 16:01:12 faye dhcpd:
Jun 29 16:01:12 faye dhcpd: No subnet declaration for wlan0 (0.0.0.0).
Jun 29 16:01:12 faye dhcpd: ** Ignoring requests on wlan0. If this is not what
Jun 29 16:01:12 faye dhcpd: you want, please write a subnet declaration
Jun 29 16:01:12 faye dhcpd: in your dhcpd.conf file for the network segment
Jun 29 16:01:12 faye dhcpd: to which interface wlan0 is attached. **
Jun 29 16:01:12 faye dhcpd:
Jun 29 16:01:12 faye dhcpd:
Jun 29 16:01:12 faye dhcpd: Not configured to listen on any interfaces!
BTW, the leases file do exist as I 'touch'ed it.
I can't understand why it says that the dhcp server is not configured
to listen on any interfaces. Seems I'm missing some easy configuration
but after some time googling it seems that I should already have it
running.
Any idea on how to carry on configuring my AP?
Thanks for your time and sorry for the inconvenience,
Javi
2009/6/29 Pavel Roskin <proski@gnu.org>:
> On Mon, 2009-06-29 at 11:00 +0200, Javier Gálvez Guerrero wrote:
>> Hi all,
>>
>> I'm trying to use my Debian box as an AP using the latest wireless
>> testing kernel (2.6.30-wl) and a WiFi card Asus WL-138G v2 PCI but I'm
>> experiencing a weird problem, hope you can guide me through it.
>>
>> First, I'll tell what and how I setup it. I downloaded the wireless
>> testing kernel and installed it (make && make modules && make
>> modules_install && make install), prepared the boot images and updated
>> the grub; fine. Next I installed compat-wireless, wireless regdb,
>> crda, libnl, hostapd and iw following this tutorial
>> (http://acx100.erley.org/git.html), with slight modifications: install
>> some missing packages (m2crypto, libgcrypt-dev and libssl-dev) and,
>> after installing compat-wireless, 'make unload' as suggested by the
>> 'make install' output.
>
> You don't need compat-wireless with 2.6.30-wl. The whole point of
> compat-wireless is to backport the latest drivers from the "-wl" kernel
> to older kernels.
>
> Please remove /lib/modules/2.6.30-wl and reinstall the kernel by running
> "make modules_install install".
>
> --
> Regards,
> Pavel Roskin
>
^ permalink raw reply
* Re: rt73usb (rt2x00) crash bug on (big-endian) ARM
From: Gert Boddaert @ 2009-06-29 13:20 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <loom.20090625T114232-539@post.gmane.org>
We found the culprit of the 'crash' for problem 1:
our watchdog implementation.
The high load on the device, stops the watchdog refresh... hence crash and reset.
We disabled the watchdog to do further testing... next.
However, when the load on the RX side gets to high, after a while (a few seconds
of sustained RX load),
the connection is not dropped but we are unable to get
any more packets through. This state does not resolve itself.
^ permalink raw reply
* Re: [PATCH] eeepc-laptop: fix hot-unplug on resume
From: Corentin Chary @ 2009-06-29 12:44 UTC (permalink / raw)
To: Len Brown
Cc: linux acpi, linux-kernel, linux-wireless@vger.kernel.org,
Alan Jenkins
In-Reply-To: <4A48A196.3060409@tuffmail.co.uk>
On Mon, Jun 29, 2009 at 1:12 PM, Alan
Jenkins<alan-jenkins@tuffmail.co.uk> wrote:
> The patch below fixes a regression introduced by the rfkill rewrite.
> Please consider it for inclusion in 2.6.31 via the ACPI tree.
>
> Thanks
> Alan
Hi Len,
Please merge this patch in ACPI tree.
Thanks,
--
Corentin Chary
http://xf.iksaif.net - http://uffs.org
^ permalink raw reply
* Re: Repeater Bridge Mode with ar9170?
From: Johannes Berg @ 2009-06-29 12:25 UTC (permalink / raw)
To: Jon Loeliger; +Cc: linux-wireless@vger.kernel.org
In-Reply-To: <1245881310.13356.10.camel@jdl-desktop>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
On Wed, 2009-06-24 at 17:08 -0500, Jon Loeliger wrote:
> OK, so, in the other (non-mac80211) drivers, there was a mode
> called IW_MODE_REPEATER that implemented 4-address framing for
> clients that provided the bridging ability.
>
> That same functionality is currently not implemented in the
> mac80211 code (ie, no NL80211_IFTYPE_REPEATER mode).
Actually, the IW_MODE_REPEATER was never quite clearly defined afaict
and we made it WDS instead.
> My perhaps mistaken understanding of what it would take to
> make this work would be to create a new NL80211_IFTYPE_REPEATER
> mode that was a hybrid between _STATION and _WDS modes. In
> particular, it would act like _STATION as far as association
> and authentication are concerned, but would also have _WDS-like
> 4-address frame handling.
>
> Does that seem about right to you guys? Are folks opposed to
> or willing to accept development down those lines? Or has
> anyone already done such work and is willing to share?
That seems acceptable, though I don't necessarily see a need for adding
a new mode since you can very easily detect that you need to use 4addr
frames, and then it is up to the AP whether to accept them or not.
As far as the AP is concerned, it would probably be violating 802.1X to
accept such frames. Thus, it seems like some fairly obscure
functionality you would only want to enable with a Kconfig option even
on the client side?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* Re: Using a Debian box as an AP with wireless testing and hostapd
From: Pavel Roskin @ 2009-06-29 12:09 UTC (permalink / raw)
To: javier.galvez; +Cc: linux-wireless
In-Reply-To: <145d4e1a0906290200v4a45d83esf8eab021f6d094f9@mail.gmail.com>
On Mon, 2009-06-29 at 11:00 +0200, Javier Gálvez Guerrero wrote:
> Hi all,
>
> I'm trying to use my Debian box as an AP using the latest wireless
> testing kernel (2.6.30-wl) and a WiFi card Asus WL-138G v2 PCI but I'm
> experiencing a weird problem, hope you can guide me through it.
>
> First, I'll tell what and how I setup it. I downloaded the wireless
> testing kernel and installed it (make && make modules && make
> modules_install && make install), prepared the boot images and updated
> the grub; fine. Next I installed compat-wireless, wireless regdb,
> crda, libnl, hostapd and iw following this tutorial
> (http://acx100.erley.org/git.html), with slight modifications: install
> some missing packages (m2crypto, libgcrypt-dev and libssl-dev) and,
> after installing compat-wireless, 'make unload' as suggested by the
> 'make install' output.
You don't need compat-wireless with 2.6.30-wl. The whole point of
compat-wireless is to backport the latest drivers from the "-wl" kernel
to older kernels.
Please remove /lib/modules/2.6.30-wl and reinstall the kernel by running
"make modules_install install".
--
Regards,
Pavel Roskin
^ permalink raw reply
* [PATCH] eeepc-laptop: fix hot-unplug on resume
From: Alan Jenkins @ 2009-06-29 11:12 UTC (permalink / raw)
To: Corentin Chary; +Cc: linux acpi, linux-kernel, linux-wireless@vger.kernel.org
The patch below fixes a regression introduced by the rfkill rewrite.
Please consider it for inclusion in 2.6.31 via the ACPI tree.
Thanks
Alan
-------------------->
>From d0265f0bfe63086816d61c69ee4b2dc4cb491d06 Mon Sep 17 00:00:00 2001
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Date: Mon, 29 Jun 2009 09:40:07 +0100
Subject: [PATCH] eeepc-laptop: fix hot-unplug on resume
OOPS on resume when the wireless adaptor is disabled during suspend was
introduced by "eeepc-laptop: read rfkill soft-blocked state on resume".
Unable to handle kernel NULL pointer dereference
Process s2disk
Tainted: G W
IP: klist_put
Call trace:
? klist_del
? device_del
? device_unregister
? pci_stop_dev
? pci_stop_bus
? pci_remove_device
? eeepc_rfkill_hotplug [eeepc_laptop]
? eeepc_hotk_resume [eeepc_laptop]
? acpi_device_resume
? device_resume
? hibernation_snapshot
It appears the PCI device is removed twice. The eeepc_rfkill_hotplug()
call from the resume handler is racing against the call from the ACPI
notifier callback. The ACPI notification is triggered by the resume
handler when it refreshes the value of CM_ASL_WLAN.
The fix is to serialize hotplug calls using a workqueue.
Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
---
drivers/platform/x86/eeepc-laptop.c | 9 ++++++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/platform/x86/eeepc-laptop.c b/drivers/platform/x86/eeepc-laptop.c
index ec560f1..222ffb8 100644
--- a/drivers/platform/x86/eeepc-laptop.c
+++ b/drivers/platform/x86/eeepc-laptop.c
@@ -143,6 +143,7 @@ struct eeepc_hotk {
struct rfkill *bluetooth_rfkill;
struct rfkill *wwan3g_rfkill;
struct hotplug_slot *hotplug_slot;
+ struct work_struct hotplug_work;
};
/* The actual device the driver binds to */
@@ -660,7 +661,7 @@ static int eeepc_get_adapter_status(struct hotplug_slot *hotplug_slot,
return 0;
}
-static void eeepc_rfkill_hotplug(void)
+static void eeepc_hotplug_work(struct work_struct *work)
{
struct pci_dev *dev;
struct pci_bus *bus = pci_find_bus(0, 1);
@@ -701,7 +702,7 @@ static void eeepc_rfkill_notify(acpi_handle handle, u32 event, void *data)
if (event != ACPI_NOTIFY_BUS_CHECK)
return;
- eeepc_rfkill_hotplug();
+ schedule_work(&ehotk->hotplug_work);
}
static void eeepc_hotk_notify(struct acpi_device *device, u32 event)
@@ -892,7 +893,7 @@ static int eeepc_hotk_resume(struct acpi_device *device)
rfkill_set_sw_state(ehotk->wlan_rfkill, wlan != 1);
- eeepc_rfkill_hotplug();
+ schedule_work(&ehotk->hotplug_work);
}
if (ehotk->bluetooth_rfkill)
@@ -1093,6 +1094,8 @@ static int eeepc_rfkill_init(struct device *dev)
{
int result = 0;
+ INIT_WORK(&ehotk->hotplug_work, eeepc_hotplug_work);
+
eeepc_register_rfkill_notifier("\\_SB.PCI0.P0P6");
eeepc_register_rfkill_notifier("\\_SB.PCI0.P0P7");
--
1.6.3.2
^ permalink raw reply related
* Re: [PATCH] p54: re-enable power save feature
From: Johannes Berg @ 2009-06-29 11:01 UTC (permalink / raw)
To: Christian Lamparter; +Cc: linux-wireless, John W. Linville
In-Reply-To: <200906280232.45959.chunkeey@web.de>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On Sun, 2009-06-28 at 02:32 +0200, Christian Lamparter wrote:
> This patch re-enables p54's power save features and adds a workaround
> which temporarily alters the device's power state in order to allow
> ps-polls to be sent and buffered data to be retrieved during psm.
>
> Signed-off-by: Christian Lamparter <chunkeey@web.de>
> ---
> Johannes,
>
> can you please give this patch a go with your cisco ap?
No, the patch doesn't (currently) apply.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* Re: [2.6.31-rc1] iwlagn (4965): regression when hardware rf switch is used
From: Johannes Berg @ 2009-06-29 9:53 UTC (permalink / raw)
To: Frans Pop; +Cc: linux-wireless, Netdev, linux-kernel
In-Reply-To: <200906291148.55386.elendil@planet.nl>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
On Mon, 2009-06-29 at 11:48 +0200, Frans Pop wrote:
> On Monday 29 June 2009, Johannes Berg wrote:
> > > [enable]
> > > usb 3-1: new full speed USB device using uhci_hcd and address 3
> > > usb 3-1: configuration #1 chosen from 1 choice
> >
> > That is completely unrelated. You plugged in a USB device too :)
>
> No, it's my "bluetooth + wlan" device. Note that disabling wireless with
> the hardware switch also gives 'usb 3-1: USB disconnect, address 2'.
>
> From lsusb:
> Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth +
> WLAN) Interface [Integrated Module]
Ah :) That's just bluetooth then though, not wifi.
> > > A lot uglier with those errors. And after that I have to run
> > > ifdown/ifup before networking is up again (ifup only does not work as
> > > it will complain "interface already configured"):
> >
> > And that's actually expected, and/or a bug in the debian networking
> > scripts.
> > (You can trigger the same problem by doing
> > ifup wlan0
> > ip link set wlan0 down
> > ifup wlan0 -> error)
>
> OK, I can accept that. Wonder why it does work with 2.6.30 then. But it
> can certainly wait until the driver problem you mentioned is resolved.
2.6.30 didn't have the "ip link set wlan0 down" on rfkill behaviour, but
overall that makes life for everybody (except people who actually use
ifup/down) much easier.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* Re: [2.6.31-rc1] iwlagn (4965): regression when hardware rf switch is used
From: Frans Pop @ 2009-06-29 9:48 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless, Netdev, linux-kernel
In-Reply-To: <1246268022.7775.24.camel@johannes.local>
On Monday 29 June 2009, Johannes Berg wrote:
> > [enable]
> > usb 3-1: new full speed USB device using uhci_hcd and address 3
> > usb 3-1: configuration #1 chosen from 1 choice
>
> That is completely unrelated. You plugged in a USB device too :)
No, it's my "bluetooth + wlan" device. Note that disabling wireless with
the hardware switch also gives 'usb 3-1: USB disconnect, address 2'.
>From lsusb:
Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth +
WLAN) Interface [Integrated Module]
> > A lot uglier with those errors. And after that I have to run
> > ifdown/ifup before networking is up again (ifup only does not work as
> > it will complain "interface already configured"):
>
> And that's actually expected, and/or a bug in the debian networking
> scripts.
> (You can trigger the same problem by doing
> ifup wlan0
> ip link set wlan0 down
> ifup wlan0 -> error)
OK, I can accept that. Wonder why it does work with 2.6.30 then. But it
can certainly wait until the driver problem you mentioned is resolved.
> To get your network connection back automatically we will require
> changes to userland tools to listen to rfkill events.
>
> > BTW, would it make sense to bring back the first two lines shown with
> > .30 (or at least the first one):
> > iwlagn 0000:10:00.0: Radio Frequency Kill Switch is On:
> > Kill switch must be turned off for wireless networking to work.
> > IMHO it's good to register the reason for the disconnect.
>
> I guess something like that could be added to cfg80211:
> phy0: taking interfaces down due to rfkill
Yes, that would be nice.
Thanks,
FJP
^ permalink raw reply
* Re: [2.6.31-rc1] iwlagn (4965): regression when hardware rf switch is used
From: Johannes Berg @ 2009-06-29 9:33 UTC (permalink / raw)
To: Frans Pop; +Cc: linux-wireless, Netdev, linux-kernel
In-Reply-To: <200906291128.05639.elendil@planet.nl>
[-- Attachment #1: Type: text/plain, Size: 1758 bytes --]
Now that I took a closer look...
> I've tried .31-rc1 on my HP 2510p notebook and noticed a problem when
> using the hardware rf kill switch.
> But with 2.6.31 I get this:
> [disable]
> wlan0: deauthenticating by local choice (reason=3)
> iwlagn 0000:10:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
> mac80211-phy0: failed to remove key (0, 00:14:c1:38:e5:15) from hardware (-5)
> iwlagn 0000:10:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
> mac80211-phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5)
> usb 3-1: USB disconnect, address 2
These errors are a driver problem.
> [enable]
> usb 3-1: new full speed USB device using uhci_hcd and address 3
> usb 3-1: configuration #1 chosen from 1 choice
That is completely unrelated. You plugged in a USB device too :)
> A lot uglier with those errors. And after that I have to run ifdown/ifup
> before networking is up again (ifup only does not work as it will complain
> "interface already configured"):
And that's actually expected, and/or a bug in the debian networking
scripts.
(You can trigger the same problem by doing
ifup wlan0
ip link set wlan0 down
ifup wlan0 -> error)
To get your network connection back automatically we will require
changes to userland tools to listen to rfkill events.
> BTW, would it make sense to bring back the first two lines shown with .30
> (or at least the first one):
> iwlagn 0000:10:00.0: Radio Frequency Kill Switch is On:
> Kill switch must be turned off for wireless networking to work.
> IMHO it's good to register the reason for the disconnect.
I guess something like that could be added to cfg80211:
phy0: taking interfaces down due to rfkill
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* [2.6.31-rc1] iwlagn (4965): regression when hardware rf switch is used
From: Frans Pop @ 2009-06-29 9:28 UTC (permalink / raw)
To: linux-wireless; +Cc: Netdev, linux-kernel
(Reported earlier in 'no wireless due to RFKILL problem' thread, but
Johannes suggested opening a new thread as it is a separate issue.)
I've tried .31-rc1 on my HP 2510p notebook and noticed a problem when
using the hardware rf kill switch.
If disable wireless using the hardware switch and the enable it again
almost immediately after on 2.6.30, I get:
[disable]
iwlagn 0000:10:00.0: Radio Frequency Kill Switch is On:
Kill switch must be turned off for wireless networking to work.
usb 3-1: USB disconnect, address 2
[enable]
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
usb 3-1: new full speed USB device using uhci_hcd and address 3
usb 3-1: configuration #1 chosen from 1 choice
wlan0: no probe response from AP 00:14:c1:38:e5:15 - disassociating
iwlagn 0000:10:00.0: index 0 not used in uCode key table.
wlan0: authenticate with AP 00:14:c1:38:e5:15
wlan0: authenticate with AP 00:14:c1:38:e5:15
wlan0: authenticated
wlan0: associate with AP 00:14:c1:38:e5:15
wlan0: RX ReassocResp from 00:14:c1:38:e5:15 (capab=0x411 status=0 aid=1)
wlan0: associated
And without any other action networking is up again.
But with 2.6.31 I get this:
[disable]
wlan0: deauthenticating by local choice (reason=3)
iwlagn 0000:10:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
mac80211-phy0: failed to remove key (0, 00:14:c1:38:e5:15) from hardware (-5)
iwlagn 0000:10:00.0: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
mac80211-phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5)
usb 3-1: USB disconnect, address 2
[enable]
usb 3-1: new full speed USB device using uhci_hcd and address 3
usb 3-1: configuration #1 chosen from 1 choice
A lot uglier with those errors. And after that I have to run ifdown/ifup
before networking is up again (ifup only does not work as it will complain
"interface already configured"):
[ifdown wlan0]
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ifup wlan 0]
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with AP 00:14:c1:38:e5:15
wlan0: authenticated
wlan0: associate with AP 00:14:c1:38:e5:15
wlan0: RX AssocResp from 00:14:c1:38:e5:15 (capab=0x411 status=0 aid=1)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
BTW, would it make sense to bring back the first two lines shown with .30
(or at least the first one):
iwlagn 0000:10:00.0: Radio Frequency Kill Switch is On:
Kill switch must be turned off for wireless networking to work.
IMHO it's good to register the reason for the disconnect.
>From lspci:
10:00.0 Network controller [0280]: Intel Corporation PRO/Wireless
4965 AG or AGN [Kedron] Network Connection [8086:4229] (rev 61)
Cheers,
FJP
^ permalink raw reply
* Using a Debian box as an AP with wireless testing and hostapd
From: Javier Gálvez Guerrero @ 2009-06-29 9:00 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <145d4e1a0906290158y4710d68ej270907f297335d42@mail.gmail.com>
Hi all,
I'm trying to use my Debian box as an AP using the latest wireless
testing kernel (2.6.30-wl) and a WiFi card Asus WL-138G v2 PCI but I'm
experiencing a weird problem, hope you can guide me through it.
First, I'll tell what and how I setup it. I downloaded the wireless
testing kernel and installed it (make && make modules && make
modules_install && make install), prepared the boot images and updated
the grub; fine. Next I installed compat-wireless, wireless regdb,
crda, libnl, hostapd and iw following this tutorial
(http://acx100.erley.org/git.html), with slight modifications: install
some missing packages (m2crypto, libgcrypt-dev and libssl-dev) and,
after installing compat-wireless, 'make unload' as suggested by the
'make install' output.
The problem is that, after rebooting, I miss the wlan0 interface
forever (I checked with the b43 driver prior to installing the
wireless testing kernel that I could get the wlan0 attached and
properly working). I always get these messages during boot time and
when trying to modprobe the corresponding modules:
...
[ 14.024804] cfg80211: exports duplicate symbol __dev_addr_unsync
(owned by kernel)
[ 14.073839] parport_pc 00:09: reported by Plug and Play ACPI
[ 14.073940] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
[ 14.203976] mac80211: Unknown symbol cfg80211_ibss_wext_giwessid
[ 14.204327] mac80211: Unknown symbol cfg80211_send_assoc_timeout
[ 14.204805] mac80211: Unknown symbol cfg80211_ibss_wext_siwessid
[ 14.205483] mac80211: Unknown symbol cfg80211_scan_done
[ 14.206193] mac80211: Unknown symbol cfg80211_wext_siwfrag
[ 14.206498] mac80211: Unknown symbol cfg80211_send_auth_timeout
[ 14.206945] mac80211: Unknown symbol cfg80211_wext_giwrts
[ 14.207193] mac80211: Unknown symbol regulatory_hint_11d
[ 14.207436] mac80211: Unknown symbol cfg80211_send_deauth
[ 14.207679] mac80211: Unknown symbol cfg80211_wext_giwscan
[ 14.208182] mac80211: Unknown symbol cfg80211_wext_giwname
[ 14.208688] mac80211: Unknown symbol cfg80211_wext_siwmlme
[ 14.209039] mac80211: Unknown symbol cfg80211_wext_siwencodeext
[ 14.209385] mac80211: Unknown symbol cfg80211_wext_giwmode
[ 14.209869] mac80211: Unknown symbol cfg80211_wext_giwrange
[ 14.210531] mac80211: Unknown symbol cfg80211_classify8021d
[ 14.210777] mac80211: Unknown symbol wiphy_register
[ 14.211020] mac80211: Unknown symbol wiphy_new
[ 14.211266] mac80211: Unknown symbol cfg80211_put_bss
[ 14.211545] mac80211: Unknown symbol cfg80211_wext_siwrts
[ 14.212538] mac80211: Unknown symbol cfg80211_ibss_joined
[ 14.212998] mac80211: Unknown symbol cfg80211_wext_giwfrag
[ 14.213381] mac80211: Unknown symbol cfg80211_hold_bss
[ 14.213697] mac80211: Unknown symbol cfg80211_ibss_wext_siwfreq
[ 14.214056] mac80211: Unknown symbol cfg80211_michael_mic_failure
[ 14.214310] mac80211: Unknown symbol cfg80211_send_rx_auth
[ 14.214820] mac80211: Unknown symbol cfg80211_ibss_wext_giwap
[ 14.215325] mac80211: Unknown symbol wiphy_unregister
[ 14.215775] mac80211: Unknown symbol cfg80211_send_disassoc
[ 14.216194] mac80211: Unknown symbol ieee80211_radiotap_iterator_init
[ 14.216545] mac80211: Unknown symbol cfg80211_get_bss
[ 14.216886] mac80211: Unknown symbol __ieee80211_get_channel
[ 14.217235] mac80211: Unknown symbol rfc1042_header
[ 14.217835] mac80211: Unknown symbol cfg80211_wext_siwmode
[ 14.218275] mac80211: Unknown symbol ieee80211_data_to_8023
[ 14.218524] mac80211: Unknown symbol cfg80211_send_rx_assoc
[ 14.218776] mac80211: Unknown symbol ieee80211_radiotap_iterator_next
[ 14.219072] mac80211: Unknown symbol ieee80211_channel_to_frequency
[ 14.219322] mac80211: Unknown symbol cfg80211_wext_siwretry
[ 14.219571] mac80211: Unknown symbol cfg80211_wext_giwtxpower
[ 14.220085] mac80211: Unknown symbol cfg80211_wext_giwretry
[ 14.220721] mac80211: Unknown symbol ieee80211_hdrlen
[ 14.221059] mac80211: Unknown symbol cfg80211_wext_siwscan
[ 14.221409] mac80211: Unknown symbol cfg80211_ibss_wext_siwap
[ 14.221747] mac80211: Unknown symbol cfg80211_inform_bss_frame
[ 14.222243] mac80211: Unknown symbol ieee80211_frequency_to_channel
[ 14.222703] mac80211: Unknown symbol cfg80211_unhold_bss
[ 14.222952] mac80211: Unknown symbol bridge_tunnel_header
[ 14.223318] mac80211: Unknown symbol cfg80211_ibss_wext_giwfreq
[ 14.223767] mac80211: Unknown symbol cfg80211_wext_siwencode
[ 14.224039] mac80211: Unknown symbol cfg80211_unlink_bss
[ 14.224288] mac80211: Unknown symbol wiphy_free
[ 14.224606] mac80211: Unknown symbol cfg80211_wext_giwencode
[ 14.224890] mac80211: Unknown symbol cfg80211_wext_siwtxpower
[ 14.488924] b43: Unknown symbol ieee80211_get_response_rate
[ 14.490682] b43: Unknown symbol ieee80211_free_hw
[ 14.491589] b43: Unknown symbol ieee80211_alloc_hw
[ 14.492239] b43: Unknown symbol ieee80211_register_hw
[ 14.492930] b43: Unknown symbol __ieee80211_get_radio_led_name
[ 14.493187] b43: Unknown symbol ieee80211_generic_frame_duration
[ 14.493441] b43: Unknown symbol ieee80211_wake_queue
[ 14.494261] b43: Unknown symbol __ieee80211_get_tx_led_name
[ 14.494514] b43: Unknown symbol ieee80211_tx_status_irqsafe
[ 14.494760] b43: Unknown symbol wiphy_rfkill_set_hw_state
[ 14.495293] b43: Unknown symbol __ieee80211_get_rx_led_name
[ 14.496713] b43: Unknown symbol ieee80211_ctstoself_get
[ 14.498008] b43: Unknown symbol ieee80211_stop_queue
[ 14.498758] b43: Unknown symbol __ieee80211_get_assoc_led_name
[ 14.499044] b43: Unknown symbol wiphy_rfkill_start_polling
[ 14.500087] b43: Unknown symbol ieee80211_unregister_hw
[ 14.500855] b43: Unknown symbol ieee80211_hdrlen
[ 14.501125] b43: Unknown symbol ieee80211_rts_get
[ 14.501445] b43: Unknown symbol ieee80211_beacon_get
[ 14.502682] b43: Unknown symbol ieee80211_rx_irqsafe
...
And if I try to launch the hostapd process (hostapd -dd
/etc/hostapd.conf) I get this error according to the previous issue:
# hostapd -dd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
ctrl_interface_group=0
nl80211: 'nl80211' generic netlink not found
nl80211 driver initialization failed.
wlan0: Unable to setup interface.
Flushing old station entries
Deauthenticate all stations
rmdir[ctrl_interface]: No such file or directory
I would like to know what should I've done or where is my mistake.
Some missing headers? Any missing kernel option in .config? I'm quite
interested in getting this environment ready to perform some
networking trials, so I hope you can help me in solving this.
Thans for your time,
Javi
^ permalink raw reply
* [PATCH 2.6.31] hp-wmi: fix rfkill bug
From: Johannes Berg @ 2009-06-29 8:53 UTC (permalink / raw)
To: John Linville; +Cc: linux-wireless, Maciej Rutecki, Frans Pop
Fix the third (I think) polarity error I accidentally
introduced in the rfkill rewrite to make wireless work
again on (certain?) HP laptops.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Tested-by: Maciej Rutecki <maciej.rutecki@gmail.com>
---
drivers/platform/x86/hp-wmi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- wireless-testing.orig/drivers/platform/x86/hp-wmi.c 2009-06-29 10:51:45.000000000 +0200
+++ wireless-testing/drivers/platform/x86/hp-wmi.c 2009-06-29 10:51:55.000000000 +0200
@@ -157,7 +157,7 @@ static int hp_wmi_dock_state(void)
static int hp_wmi_set_block(void *data, bool blocked)
{
unsigned long b = (unsigned long) data;
- int query = BIT(b + 8) | ((!!blocked) << b);
+ int query = BIT(b + 8) | ((!blocked) << b);
return hp_wmi_perform_query(HPWMI_WIRELESS_QUERY, 1, query);
}
^ permalink raw reply
* Re: [RFC 00/11] cfg80211 connect API + wireless extension move
From: Johannes Berg @ 2009-06-29 8:35 UTC (permalink / raw)
To: Dave; +Cc: Luis R. Rodriguez, linux-wireless
In-Reply-To: <4A473730.3000409@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
On Sun, 2009-06-28 at 10:26 +0100, Dave wrote:
> Johannes Berg wrote:
> > Yes. Mind you, I was not only talking about iwpriv, but also about
> > things like orinoco's spy support or get/set sensitivity. The latter we
> > don't quite understand -- can you tell us what it actually does? Spy
> > support should just be removed, I think.
>
> I've had a closer look at this.
Thanks!
> The sensitivity basically controls the roaming threshold when handled by
> firmware. It is a firmware setting, though the Agere driver also
> validates the multicast rates based on it. The drivers/firmware use
> terms like system scale, AP density, distance between APs.
>
> There are 3 valid values:
>
> 3 - high density of APs. Maintain 11Mbps by roaming.
> 2 - medium density of APs. Maintain 2Mbps.
> 1 - low density. Maintain 1Mbps.
>
> Although the values are defined in terms of the usable bitrate, the
> (Intersil) documentation states that the implementation is based on SNR.
That's actually what people suspected when I asked around at the summit,
and it seemed the general consensus is that we need a proper setting for
that in nl80211 along with some of the roaming capability exports.
So until that happens, the last patch won't get in anyway, and we'll see
about the NEED_... stuff later.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* Re: [PATCH] wireless: Compare ethernet addresses by unaligned safe way
From: Johannes Berg @ 2009-06-29 8:23 UTC (permalink / raw)
To: ivan.kuten; +Cc: linux-wireless, Yauhen Kharuzhy
In-Reply-To: <4A475F82.9040007@promwad.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On Sun, 2009-06-28 at 15:18 +0300, Ivan Kuten wrote:
> Hello,
>
> In net/wireless/scan.c : cfg80211_wext_siwscan there seems also unaligned allocations
> for creq->ssids and creq->channels. Should it be something like that?
>
> Modified: trunk/uClinux-dist-2008R1-RC8/compat-wireless-2009-06-11/net/wireless/scan.c
> ==============================================================================
> --- trunk/uClinux-dist-2008R1-RC8/compat-wireless-2009-06-11/net/wireless/scan.c (original)
> +++ trunk/uClinux-dist-2008R1-RC8/compat-wireless-2009-06-11/net/wireless/scan.c Fri Jun 26 14:00:52 2009
> @@ -619,7 +619,7 @@
> if (wiphy->bands[band])
> n_channels += wiphy->bands[band]->n_channels;
>
> - creq = kzalloc(sizeof(*creq) + sizeof(struct cfg80211_ssid) +
> + creq = kzalloc(roundup(sizeof(*creq), 4) + roundup(sizeof(struct cfg80211_ssid), 4) +
> n_channels * sizeof(void *),
> GFP_ATOMIC);
Also, that should be sizeof(void *) instead of "4".
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* Re: [PATCH] wireless: Compare ethernet addresses by unaligned safe way
From: Johannes Berg @ 2009-06-29 7:58 UTC (permalink / raw)
To: ivan.kuten; +Cc: linux-wireless, Yauhen Kharuzhy
In-Reply-To: <4A475F82.9040007@promwad.com>
[-- Attachment #1: Type: text/plain, Size: 3071 bytes --]
On Sun, 2009-06-28 at 15:18 +0300, Ivan Kuten wrote:
> Hello,
>
> In net/wireless/scan.c : cfg80211_wext_siwscan there seems also unaligned allocations
> for creq->ssids and creq->channels. Should it be something like that?
Seems alright, but there is more than one instance of this, maybe you
can make a function to allocate a scan request properly and have it be
called from all the places it's needed.
johannes
> Modified: trunk/uClinux-dist-2008R1-RC8/compat-wireless-2009-06-11/net/wireless/scan.c
> ==============================================================================
> --- trunk/uClinux-dist-2008R1-RC8/compat-wireless-2009-06-11/net/wireless/scan.c (original)
> +++ trunk/uClinux-dist-2008R1-RC8/compat-wireless-2009-06-11/net/wireless/scan.c Fri Jun 26 14:00:52 2009
> @@ -619,7 +619,7 @@
> if (wiphy->bands[band])
> n_channels += wiphy->bands[band]->n_channels;
>
> - creq = kzalloc(sizeof(*creq) + sizeof(struct cfg80211_ssid) +
> + creq = kzalloc(roundup(sizeof(*creq), 4) + roundup(sizeof(struct cfg80211_ssid), 4) +
> n_channels * sizeof(void *),
> GFP_ATOMIC);
> if (!creq) {
> @@ -629,8 +629,8 @@
>
> creq->wiphy = wiphy;
> creq->ifidx = dev->ifindex;
> - creq->ssids = (void *)(creq + 1);
> - creq->channels = (void *)(creq->ssids + 1);
> + creq->ssids = (void *)creq + roundup(sizeof(*creq), 4);
> + creq->channels = (void *)creq->ssids + roundup(sizeof(*creq->ssids), 4);
> creq->n_channels = n_channels;
> creq->n_ssids = 1;
>
> Regards,
> Ivan
>
> > On Tue, 2009-06-16 at 13:54 +0300, Yauhen Kharuzhy wrote:
> >> When we try to run RTL8187 driver on AD BlackFin platform, we got
> >> messages from kernel about unaligned memory access at
> >> compare_ether_addr() calls.
> >>
> >> Replacing of compare_ether_addr() by memcmp() fixes this problem.
> >
> > This shouldn't be necessary. Which operand is unaligned?
> >
> >> --- a/net/mac80211/ibss.c
> >> +++ b/net/mac80211/ibss.c
> >> @@ -395,7 +395,7 @@ struct sta_info *ieee80211_ibss_add_sta(struct ieee80211_sub_if_data *sdata,
> >> return NULL;
> >> }
> >>
> >> - if (compare_ether_addr(bssid, sdata->u.ibss.bssid))
> >> + if (memcmp(bssid, sdata->u.ibss.bssid, ETH_ALEN))
> >> return NULL;
> >
> > So in this case it seems that it is possible that u.ibss.bssid is not
> > aligned, consider fixing by doing
> >
> > --- ieee80211_i.h
> > +++ ieee80211_i.h
> > - u8 bssid[ETH_ALEN];
> > + u8 bssid[ETH_ALEN] __align(2);
> >
> > or so instead.
> >
> >> --- a/net/wireless/scan.c
> >> +++ b/net/wireless/scan.c
> >> @@ -134,7 +134,7 @@ static bool is_bss(struct cfg80211_bss *a,
> >> {
> >> const u8 *ssidie;
> >>
> >> - if (bssid && compare_ether_addr(a->bssid, bssid))
> >> + if (bssid && memcmp(a->bssid, bssid, ETH_ALEN))
> >
> > Since a->bssid is after a pointer I can't see how it would be unaligned,
> > and bssid should be unaligned only if the call trace shows it's coming
> > from the above u.ibss.bssid.
> >
> > johannes
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* Re: [2.6.31-rc1] iwlagn (4965): no wireless due to RFKILL problem
From: Johannes Berg @ 2009-06-26 20:28 UTC (permalink / raw)
To: Frans Pop
Cc: Maciej Rutecki, linux-wireless, Netdev, linux-kernel,
Alan Jenkins
In-Reply-To: <200906261410.58808.elendil@planet.nl>
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
On Fri, 2009-06-26 at 14:10 +0200, Frans Pop wrote:
> Well, with 2.6.30 hp-wmi worked together with rfkill without problems.
> Looking at the commit logs, it looks like the rfkill rewrite by Johannes
> and Alan is the cause here. CCs added.
Hmm, looks like there might be another polarity error, try this:
- int query = BIT(b + 8) | ((!!blocked) << b);
+ int query = BIT(b + 8) | ((!blocked) << b);
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* Re: [PATCH 0/3] wireless extensions improvements
From: Johannes Berg @ 2009-06-26 20:12 UTC (permalink / raw)
To: David Miller; +Cc: netdev, linux-wireless
In-Reply-To: <20090625.161817.112930127.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Thu, 2009-06-25 at 16:18 -0700, David Miller wrote:
> These changes look fine to me, so I'll likely put them into
> net-next-2.6 as soon as I open that up.
Alright, sounds good.
> FWIW, I bet we could make read() easily work properly to for the
> compat stuff, and it would be nice to shore up that one minor hole.
Yes, but I think that would require introducing compat_sys_read() and
touching all architectures.
One other thing I just thought about -- the things you were mentioning
wrt. u64 alignment, is that relevant for sendmsg() as well? This doesn't
cover that at all, so far, obviously. If that would be needed, we'd also
need more work there, we can of course do that as we go along and add
code to deal with just the kernel->userspace messages where necessary.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* 2.6.31-rc1-git3: Reported regressions 2.6.29 -> 2.6.30
From: Rafael J. Wysocki @ 2009-06-29 0:26 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Andrew Morton, Linus Torvalds, Natalie Protasevich,
Kernel Testers List, Network Development, Linux ACPI,
Linux PM List, Linux SCSI List, Linux Wireless List, DRI
[NOTES:
* I hope you notice the jump of the number of reported regressions after 2.6.30
was released.
* Please let me know which of these bugs have been fixed already (ideally
please also provide the name of the fix commit).
* The post-2.6.30 reports were flooded by the megre window noise that made
them very difficult to track.]
This message contains a list of some regressions introduced between 2.6.29 and
2.6.30, for which there are no fixes in the mainline I know of. If any of them
have been fixed already, please let me know.
If you know of any other unresolved regressions introduced between 2.6.29
and 2.6.30, please let me know either and I'll add them to the list.
Also, please let me know if any of the entries below are invalid.
Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.
Listed regressions statistics:
Date Total Pending Unresolved
----------------------------------------
2009-06-29 133 46 43
2009-06-07 110 35 31
2009-05-31 100 32 27
2009-05-24 92 34 27
2009-05-16 81 36 33
2009-04-25 55 36 26
2009-04-17 37 35 28
Unresolved regressions
----------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13669
Subject : Kernel bug with dock driver
Submitter : Joerg Platte <jplatte@naasa.net>
Date : 2009-06-14 21:00 (15 days old)
References : http://lkml.org/lkml/2009/6/14/216
Handled-By : Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13668
Subject : Can't boot 2.6.30 powerpc kernel under qemu.
Submitter : Rob Landley <rob@landley.net>
Date : 2009-06-27 18:08 (2 days old)
References : http://lkml.org/lkml/2009/6/27/159
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13660
Subject : Crashes during boot on 2.6.30 / 2.6.31-rc, random programs
Submitter : Joao Correia <joaomiguelcorreia@gmail.com>
Date : 2009-06-27 16:07 (2 days old)
References : http://lkml.org/lkml/2009/6/27/95
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13651
Subject : Anyone know what happened with PC speaker in 2.6.30?
Submitter : Michael Tokarev <mjt@tls.msk.ru>
Date : 2009-06-15 14:41 (14 days old)
References : http://marc.info/?l=linux-kernel&m=124507695427817&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13649
Subject : Bad page state in process with various applications
Submitter : Maxim Levitsky <maximlevitsky@gmail.com>
Date : 2009-06-20 15:27 (9 days old)
References : http://marc.info/?l=linux-mm&m=124551168828090&w=4
Handled-By : Mel Gorman <mel@csn.ul.ie>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13648
Subject : nfsd: page allocation failure
Submitter : Justin Piszcz <jpiszcz@lucidpixels.com>
Date : 2009-06-22 12:08 (7 days old)
References : http://lkml.org/lkml/2009/6/22/309
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13647
Subject : fb/mmap lockdep report.
Submitter : Dave Jones <davej@redhat.com>
Date : 2009-06-21 13:33 (8 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=513adb58685615b0b1d47a3f0d40f5352beff189
References : http://lkml.org/lkml/2009/6/21/90
http://lkml.org/lkml/2009/6/21/122
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13646
Subject : warn_on tty_io.c, broken bluetooth
Submitter : Pavel Machek <pavel@ucw.cz>
Date : 2009-06-19 17:05 (10 days old)
References : http://lkml.org/lkml/2009/6/19/187
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13644
Subject : hibernation/swsusp lockup due to acpi-cpufreq
Submitter : Johannes Stezenbach <js@sig21.net>
Date : 2009-06-16 01:27 (13 days old)
References : http://lkml.org/lkml/2009/6/15/630
Handled-By : Rafael J. Wysocki <rjw@sisk.pl>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13634
Subject : [drm:drm_wait_vblank] failed to acquire vblank counter
Submitter : Cijoml Cijomlovic Cijomlov <cijoml@volny.cz>
Date : 2009-06-27 07:02 (2 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13624
Subject : usb: wrong autosuspend initialization
Submitter : <list@phuk.ath.cx>
Date : 2009-06-25 18:18 (4 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13621
Subject : xfs hangs with assertion failed
Submitter : Johannes Engel <jcnengel@googlemail.com>
Date : 2009-06-25 10:07 (4 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13620
Subject : acpi_enforce_resources broken - conflicting i2c module loaded on some EeePCs
Submitter : Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Date : 2009-06-25 08:31 (4 days old)
References : <http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2009-June/002316.html>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13613
Subject : lockups with JFS (inconsistent lock state)
Submitter : Jan "Yenya" Kasprzak <kas@fi.muni.cz>
Date : 2009-06-24 09:35 (5 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13581
Subject : ath9k doesn't work with newer kernels
Submitter : Matteo <rootkit85@yahoo.it>
Date : 2009-06-19 12:04 (10 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13558
Subject : Tracelog during resume
Submitter : Cijoml Cijomlovic Cijomlov <cijoml@volny.cz>
Date : 2009-06-17 11:32 (12 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13554
Subject : linux-image-2.6.30-1-686, KMS enabled: black screen, no X window
Submitter : Jos van Wolput <wolput@onsneteindhoven.nl>
Date : 2009-06-17 06:28 (12 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13528
Subject : au0828: major drop in reception quality between 2.6.29.4 and 2.6.30 on HVR-950q
Submitter : Jim Faulkner <jfaulkne@ccs.neu.edu>
Date : 2009-06-13 19:34 (16 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13518
Subject : slab grows with NFS write activity.
Submitter : Andrew Randrianasulu <randrik@mail.ru>
Date : 2009-06-12 09:51 (17 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13514
Subject : acer_wmi causes stack corruption
Submitter : Rus <harbour@sfinx.od.ua>
Date : 2009-06-12 08:13 (17 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13512
Subject : D43 on 2.6.30 doesn't suspend anymore
Submitter : Daniel Smolik <marvin@mydatex.cz>
Date : 2009-06-11 20:12 (18 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13502
Subject : GPE storm causes polling mode, which causes /proc/acpi/battery read to take 4 seconds - MacBookPro4,1
Submitter : <sveina@gmail.com>
Date : 2009-06-10 20:04 (19 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13472
Subject : Oops with minicom and USB serial
Submitter : Peter Chubb <peterc@gelato.unsw.edu.au>
Date : 2009-06-05 1:37 (24 days old)
References : http://marc.info/?l=linux-kernel&m=124416901026700&w=4
Handled-By : Alan Stern <stern@rowland.harvard.edu>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13471
Subject : Loading parport_pc kills the keyboard if ACPI is enabled
Submitter : Ozan Çağlayan <ozan@pardus.org.tr>
Date : 2009-06-04 9:12 (25 days old)
References : http://marc.info/?l=linux-kernel&m=124410667532558&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13424
Subject : possible deadlock when doing governor switching
Submitter : Shaohua Li <shaohua.li@intel.com>
Date : 2009-05-31 16:36 (29 days old)
References : http://www.spinics.net/lists/cpufreq/msg00711.html
Handled-By : Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13408
Subject : Performance regression in 2.6.30-rc7
Submitter : Diego Calleja <diegocg@gmail.com>
Date : 2009-05-30 18:51 (30 days old)
References : http://lkml.org/lkml/2009/5/30/146
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13407
Subject : adb trackpad disappears after suspend to ram
Submitter : Jan Scholz <scholz@fias.uni-frankfurt.de>
Date : 2009-05-28 7:59 (32 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2ed8d2b3a81bdbb0418301628ccdb008ac9f40b7
References : http://marc.info/?l=linux-kernel&m=124349762314976&w=4
Handled-By : Rafael J. Wysocki <rjw@sisk.pl>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13401
Subject : pktcdvd writing is really slow with CFQ scheduler (bisected)
Submitter : Laurent Riffard <laurent.riffard@free.fr>
Date : 2009-05-28 18:43 (32 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13374
Subject : reiserfs blocked for more than 120secs
Submitter : Harald Dunkel <harald.dunkel@t-online.de>
Date : 2009-05-23 8:52 (37 days old)
References : http://marc.info/?l=linux-kernel&m=124306880410811&w=4
http://lkml.org/lkml/2009/5/29/389
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13373
Subject : fbcon, intelfb, i915: INFO: possible circular locking dependency detected
Submitter : Miles Lane <miles.lane@gmail.com>
Date : 2009-05-23 5:08 (37 days old)
References : http://marc.info/?l=linux-kernel&m=124305538130702&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13362
Subject : rt2x00: slow wifi with correct basic rate bitmap
Submitter : Alejandro Riveira <ariveira@gmail.com>
Date : 2009-05-22 13:32 (38 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13351
Subject : 2.6.30 corrupts my system after suspend resume with readonly mounted hard disk
Submitter : <unggnu@googlemail.com>
Date : 2009-05-20 14:09 (40 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=78a8b35bc7abf8b8333d6f625e08c0f7cc1c3742
Handled-By : Yinghai Lu <yinghai@kernel.org>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13341
Subject : Random Oops at boot at loading ip6tables rules
Submitter : <patrick@ostenberg.de>
Date : 2009-05-19 09:08 (41 days old)
Handled-By : Rusty Russell <rusty@rustcorp.com.au>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13337
Subject : [post 2.6.29 regression] hang during suspend of b44/b43 modules
Submitter : Tomas Janousek <tomi@nomi.cz>
Date : 2009-05-18 10:59 (42 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13328
Subject : b44: eth0: BUG! Timeout waiting for bit 00000002 of register 42c to clear.
Submitter : Francis Moreau <francis.moro@gmail.com>
Date : 2009-05-03 16:22 (57 days old)
References : http://marc.info/?l=linux-kernel&m=124136778012280&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13319
Subject : Page allocation failures with b43 and p54usb
Submitter : Larry Finger <Larry.Finger@lwfinger.net>
Date : 2009-04-29 21:01 (61 days old)
References : http://marc.info/?l=linux-kernel&m=124103897101088&w=4
http://lkml.org/lkml/2009/6/7/136
Handled-By : Johannes Berg <johannes@sipsolutions.net>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13318
Subject : AGP doesn't work anymore on nforce2
Submitter : Karsten Mehrhoff <kawime@gmx.de>
Date : 2009-04-30 8:51 (60 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=59de2bebabc5027f93df999d59cc65df591c3e6e
References : http://marc.info/?l=linux-kernel&m=124108156417560&w=4
Handled-By : Shaohua Li <shaohua.li@intel.com>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13306
Subject : hibernate slow on _second_ run
Submitter : Johannes Berg <johannes@sipsolutions.net>
Date : 2009-05-14 09:34 (46 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13277
Subject : 2.6.30 regression - hang on 2nd resume - bisected - Thinkpad X40
Submitter : Daniel Vetter <daniel@ffwll.ch>
Date : 2009-05-11 10:08 (49 days old)
Handled-By : Len Brown <len.brown@intel.com>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13219
Subject : Intel 440GX: Since kernel 2.6.30-rc1, computers hangs randomly but not with kernel <= 2.6.29.4
Submitter : David Hill <hilld@binarystorm.net>
Date : 2009-05-01 16:57 (59 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13179
Subject : CD-R: wodim intermittent failures
Submitter : Andy Isaacson <adi@hexapodia.org>
Date : 2009-04-21 1:52 (69 days old)
References : http://marc.info/?l=linux-kernel&m=124027879214231&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13119
Subject : Trouble with make-install from a NFS mount
Submitter : Gregory Haskins <ghaskins@novell.com>
Date : 2009-04-14 21:32 (76 days old)
References : http://marc.info/?l=linux-kernel&m=123974482327044&w=4
Handled-By : H. Peter Anvin <hpa@zytor.com>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13109
Subject : High latency on /sys/class/thermal
Submitter : Tiago Simões Batista <tiagosbatista@gmail.com>
Date : 2009-04-11 14:56 (79 days old)
References : http://marc.info/?l=linux-kernel&m=123946182301248&w=4
Handled-By : Zhang Rui <rui.zhang@intel.com>
Alexey Starikovskiy <astarikovskiy@suse.de>
Regressions with patches
------------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13663
Subject : suspend to ram regression (IDE related)
Submitter : Etienne Basset <etienne.basset@numericable.fr>
Date : 2009-06-26 17:40 (3 days old)
References : http://lkml.org/lkml/2009/6/26/242
Handled-By : Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Patch : http://patchwork.kernel.org/patch/32719/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13475
Subject : suspend/hibernate lockdep warning
Submitter : Dave Young <hidave.darkstar@gmail.com>
Date : 2009-06-02 10:00 (27 days old)
References : http://marc.info/?l=linux-kernel&m=124393723321241&w=4
Handled-By : Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Patch : http://patchwork.kernel.org/patch/28660/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13389
Subject : Warning 'Invalid throttling state, reset' gets displayed when it should not be
Submitter : Frans Pop <elendil@planet.nl>
Date : 2009-05-26 15:24 (34 days old)
Handled-By : Frans Pop <elendil@planet.nl>
Patch : http://bugzilla.kernel.org/attachment.cgi?id=21671
http://bugzilla.kernel.org/attachment.cgi?id=21672
For details, please visit the bug entries and follow the links given in
references.
As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions introduced
between 2.6.29 and 2.6.30, unresolved as well as resolved, at:
http://bugzilla.kernel.org/show_bug.cgi?id=13070
Please let me know if there are any Bugzilla entries that should be added to
the list in there.
Thanks,
Rafael
^ permalink raw reply
* 2.6.31-rc1-git3: Reported regressions from 2.6.30
From: Rafael J. Wysocki @ 2009-06-28 23:51 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Adrian Bunk, Andrew Morton, Linus Torvalds, Natalie Protasevich,
Kernel Testers List, Network Development, Linux ACPI,
Linux PM List, Linux SCSI List, Linux Wireless List, DRI
This message contains a list of some regressions from 2.6.30, for which there
are no fixes in the mainline I know of. If any of them have been fixed already,
please let me know.
If you know of any other unresolved regressions from 2.6.30, please let me know
either and I'll add them to the list. Also, please let me know if any of the
entries below are invalid.
Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.
Listed regressions statistics:
Date Total Pending Unresolved
----------------------------------------
2009-06-29 22 22 15
Unresolved regressions
----------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13667
Subject : drm: display arifacts when X.Org is stopped
Submitter : Frans Pop <elendil@planet.nl>
Date : 2009-06-27 18:52 (2 days old)
References : http://lkml.org/lkml/2009/6/27/105
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13666
Subject : WARNING: at mm/page_alloc.c:1743 __alloc_pages_nodemask
Submitter : Thomas Meyer <thomas@m3y3r.de>
Date : 2009-06-27 16:15 (2 days old)
References : http://lkml.org/lkml/2009/6/27/75
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13661
Subject : warning in smp_call_function_single while S2R
Submitter : Thomas Meyer <thomas@m3y3r.de>
Date : 2009-06-27 17:12 (2 days old)
References : http://lkml.org/lkml/2009/6/27/80
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13657
Subject : Linux-2.6.31-rc1 Fails To Recognize Some USB Disks
Submitter : Tarkan Erimer <tarkan.erimer@turknet.net.tr>
Date : 2009-06-26 10:03 (3 days old)
References : http://lkml.org/lkml/2009/6/26/34
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13656
Subject : 2.6.31-rc1 crashes randomly on my Machine.
Submitter : Zeno Davatz <zdavatz@gmail.com>
Date : 2009-06-26 08:56 (3 days old)
References : http://lkml.org/lkml/2009/6/26/27
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13652
Subject : scheduling while atomic: pptpgw
Submitter : Sergey Senozhatsky <sergey.senozhatsky@mail.by>
Date : 2009-06-19 21:15 (10 days old)
References : http://lkml.org/lkml/2009/6/19/237
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13650
Subject : Problem with alloc_arch_preferred_bootmem() on powerpc
Submitter : Sean MacLennan <smaclennan@pikatech.com>
Date : 2009-06-20 19:48 (9 days old)
References : http://marc.info/?l=linuxppc-embedded&m=124552732411775&w=4
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13645
Subject : NULL pointer dereference at (null) (level2_spare_pgt)
Submitter : poornima nayak <mpnayak@linux.vnet.ibm.com>
Date : 2009-06-17 17:56 (12 days old)
References : http://lkml.org/lkml/2009/6/17/194
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13643
Subject : Touchpad lost synchronization after resume from suspend to RAM
Submitter : Cijoml Cijomlovic Cijomlov <cijoml@volny.cz>
Date : 2009-06-28 10:42 (1 days old)
References : http://lkml.org/lkml/2009/6/23/365
http://lkml.org/lkml/2009/6/25/256
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13633
Subject : [bisected] No sound on HDA Intel (ALC268)
Submitter : Brian Rogers <brian@xyzw.org>
Date : 2009-06-27 04:42 (2 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13627
Subject : Tunnel device ignores TCP/UDP traffic
Submitter : Paul Martin <pm@debian.org>
Date : 2009-06-26 14:45 (3 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13610
Subject : radeon kms invalid edid data at lvds
Submitter : Nicolas Reinecke <pl4nkton@googlemail.com>
Date : 2009-06-23 19:53 (6 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13601
Subject : Hard crash connecting via Huawei E169 + umtsmon
Submitter : Clemens Eisserer <linuxhippy@gmail.com>
Date : 2009-06-22 13:58 (7 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13592
Subject : Root partition is not found
Submitter : François Valenduc <francois.valenduc@tvcablenet.be>
Date : 2009-06-21 08:42 (8 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13522
Subject : BUG: scheduling while atomic
Submitter : Sergey Senozhatsky <sergey.senozhatsky@mail.by>
Date : 2009-06-12 19:29 (17 days old)
Regressions with patches
------------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13665
Subject : commit 69c854817566 causes OOMs
Submitter : David Howells <dhowells@redhat.com>
Date : 2009-06-27 08:12 (2 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=69c854817566db82c362797b4a6521d0b00fe1d8
References : http://lkml.org/lkml/2009/6/27/28
Handled-By : Wu Fengguang <fengguang.wu@intel.com>
Patch : http://patchwork.kernel.org/patch/32740/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13662
Subject : broken alpha smp build
Submitter : maximilian attems <max@stro.at>
Date : 2009-06-25 11:08 (4 days old)
References : http://lkml.org/lkml/2009/6/25/108
Handled-By : Tejun Heo <tj@kernel.org>
Patch : http://patchwork.kernel.org/patch/32714/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13659
Subject : iwlagn (4965): no wireless due to RFKILL problem
Submitter : Frans Pop <elendil@planet.nl>
Date : 2009-06-26 13:36 (3 days old)
References : http://lkml.org/lkml/2009/6/26/127
Handled-By : Johannes Berg <johannes@sipsolutions.net>
Patch : http://lkml.org/lkml/2009/6/27/35
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13658
Subject : parisc: multiple PCI BAR collisions
Submitter : Alexander Beregalov <a.beregalov@gmail.com>
Date : 2009-06-26 12:58 (3 days old)
References : http://lkml.org/lkml/2009/6/26/87
Handled-By : Matthew Wilcox <matthew@wil.cx>
Patch : http://patchwork.kernel.org/patch/32593/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13655
Subject : [Oops] 2.6.31-rc1: tun
Submitter : Sergei Trofimovich <slyich@gmail.com>
Date : 2009-06-25 23:53 (4 days old)
References : http://lkml.org/lkml/2009/6/25/435
Handled-By : Herbert Xu <herbert@gondor.apana.org.au>
Patch : http://patchwork.kernel.org/patch/32672/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13654
Subject : possible recursive locking detected at kmem_cache_free
Submitter : Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
Date : 2009-06-25 11:59 (4 days old)
References : http://lkml.org/lkml/2009/6/25/373
Handled-By : Pekka J Enberg <penberg@cs.helsinki.fi>
Patch : http://patchwork.kernel.org/patch/32525/
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13653
Subject : system hangs after resume from suspend to disk, mce related
Submitter : Maciej Rutecki <maciej.rutecki@gmail.com>
Date : 2009-06-21 19:02 (8 days old)
References : http://lkml.org/lkml/2009/6/21/86
Handled-By : Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Patch : http://patchwork.kernel.org/patch/32062/
For details, please visit the bug entries and follow the links given in
references.
As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions from 2.6.30,
unresolved as well as resolved, at:
http://bugzilla.kernel.org/show_bug.cgi?id=13615
Please let me know if there are any Bugzilla entries that should be added to
the list in there.
Thanks,
Rafael
^ permalink raw reply
* [PATCH 1/2] ath5k: remove permissions from debugfs files
From: Jiri Slaby @ 2009-06-28 21:25 UTC (permalink / raw)
To: linville; +Cc: ath5k-devel, ath9k-devel, linux-wireless, linux-kernel,
Jiri Slaby
Don't allow users to open debugfs files, because it can cause oopses.
When a user opens some file, driver unlinks it and frees the
corresponding structure, we will dereference freed memory.
Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
---
drivers/net/wireless/ath/ath5k/debug.c | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/net/wireless/ath/ath5k/debug.c b/drivers/net/wireless/ath/ath5k/debug.c
index 4904a07..747508c 100644
--- a/drivers/net/wireless/ath/ath5k/debug.c
+++ b/drivers/net/wireless/ath/ath5k/debug.c
@@ -380,13 +380,15 @@ ath5k_debug_init_device(struct ath5k_softc *sc)
sc->debug.debugfs_phydir = debugfs_create_dir(wiphy_name(sc->hw->wiphy),
ath5k_global_debugfs);
- sc->debug.debugfs_debug = debugfs_create_file("debug", S_IWUSR | S_IRUGO,
+ sc->debug.debugfs_debug = debugfs_create_file("debug",
+ S_IWUSR | S_IRUSR,
sc->debug.debugfs_phydir, sc, &fops_debug);
- sc->debug.debugfs_registers = debugfs_create_file("registers", S_IRUGO,
+ sc->debug.debugfs_registers = debugfs_create_file("registers", S_IRUSR,
sc->debug.debugfs_phydir, sc, &fops_registers);
- sc->debug.debugfs_beacon = debugfs_create_file("beacon", S_IWUSR | S_IRUGO,
+ sc->debug.debugfs_beacon = debugfs_create_file("beacon",
+ S_IWUSR | S_IRUSR,
sc->debug.debugfs_phydir, sc, &fops_beacon);
sc->debug.debugfs_reset = debugfs_create_file("reset", S_IWUSR,
--
1.6.3.2
^ permalink raw reply related
* [PATCH 2/2] ath9k: remove permissions from debugfs files
From: Jiri Slaby @ 2009-06-28 21:25 UTC (permalink / raw)
To: linville; +Cc: ath5k-devel, ath9k-devel, linux-wireless, linux-kernel,
Jiri Slaby
In-Reply-To: <1246224328-11826-1-git-send-email-jirislaby@gmail.com>
Don't allow users to open debugfs files, because it can cause oopses.
When a user opens some file, driver unlinks it and frees the
corresponding structure, we will dereference freed memory.
Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
---
drivers/net/wireless/ath/ath9k/debug.c | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/debug.c b/drivers/net/wireless/ath/ath9k/debug.c
index 6d20725..9f99f00 100644
--- a/drivers/net/wireless/ath/ath9k/debug.c
+++ b/drivers/net/wireless/ath/ath9k/debug.c
@@ -500,31 +500,31 @@ int ath9k_init_debug(struct ath_softc *sc)
goto err;
sc->debug.debugfs_debug = debugfs_create_file("debug",
- S_IRUGO | S_IWUSR, sc->debug.debugfs_phy, sc, &fops_debug);
+ S_IRUSR | S_IWUSR, sc->debug.debugfs_phy, sc, &fops_debug);
if (!sc->debug.debugfs_debug)
goto err;
- sc->debug.debugfs_dma = debugfs_create_file("dma", S_IRUGO,
+ sc->debug.debugfs_dma = debugfs_create_file("dma", S_IRUSR,
sc->debug.debugfs_phy, sc, &fops_dma);
if (!sc->debug.debugfs_dma)
goto err;
sc->debug.debugfs_interrupt = debugfs_create_file("interrupt",
- S_IRUGO,
+ S_IRUSR,
sc->debug.debugfs_phy,
sc, &fops_interrupt);
if (!sc->debug.debugfs_interrupt)
goto err;
sc->debug.debugfs_rcstat = debugfs_create_file("rcstat",
- S_IRUGO,
+ S_IRUSR,
sc->debug.debugfs_phy,
sc, &fops_rcstat);
if (!sc->debug.debugfs_rcstat)
goto err;
sc->debug.debugfs_wiphy = debugfs_create_file(
- "wiphy", S_IRUGO | S_IWUSR, sc->debug.debugfs_phy, sc,
+ "wiphy", S_IRUSR | S_IWUSR, sc->debug.debugfs_phy, sc,
&fops_wiphy);
if (!sc->debug.debugfs_wiphy)
goto err;
--
1.6.3.2
^ permalink raw reply related
* Re: [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb_alloc)
From: Sitsofe Wheeler @ 2009-06-28 20:23 UTC (permalink / raw)
To: Bob Copeland
Cc: Jiri Slaby, Nick Kossifidis, Frederic Weisbecker, linux-kernel,
linux-wireless, ath5k-devel, Luis R. Rodriguez
In-Reply-To: <20090526211029.GA2011@sucs.org>
On Tue, May 26, 2009 at 10:10:30PM +0100, Sitsofe Wheeler wrote:
> On Fri, May 22, 2009 at 10:39:31AM +0100, Sitsofe Wheeler wrote:
> > On Mon, May 18, 2009 at 11:05:40AM +0100, Sitsofe Wheeler wrote:
> > > On Fri, May 15, 2009 at 12:09:04AM -0400, Bob Copeland wrote:
> > > >
> > > > This is too ugly to live, but I'd like to know if you can reproduce
> > > > with this patch. If it still happens, then I guess it's back to
> >
> > The poison message has not reappeared but this morning there was a
>
> Yet again, I spoke too soon. This evening the following was in dmesg:
>
> I'm pretty certain this kernel had your previous patch (although the
> directory that held the kernel has since been cleaned away on the server
> on which it was compiled).
OK I'm still trying to follow this. I forwarded your patch to 2.6.31-rc1
but this time I have kmemleak enabled. I left it streaming radio for the
past few hours and the following appeared in the logs:
Jun 28 17:01:34 eeepc kernel: [ 744.083787] kmemleak: unreferenced object 0xf5845770 (size 64):
Jun 28 17:01:34 eeepc kernel: [ 744.083795] kmemleak: comm "swapper", pid 1, jiffies 4294673468
Jun 28 17:01:34 eeepc kernel: [ 744.083799] kmemleak: backtrace:
Jun 28 17:01:34 eeepc kernel: [ 744.083811] kmemleak: [<c01a749d>] kmemleak_alloc+0x11d/0x2a0
Jun 28 17:01:34 eeepc kernel: [ 744.083818] kmemleak: [<c01a4376>] __kmalloc+0x136/0x210
Jun 28 17:01:34 eeepc kernel: [ 744.083828] kmemleak: [<c043f923>] ieee80211_register_hw+0x83/0x4b0
Jun 28 17:01:34 eeepc kernel: [ 744.083837] kmemleak: [<c04630d5>] ath5k_pci_probe+0xee5/0x1100
Jun 28 17:01:34 eeepc kernel: [ 744.083849] kmemleak: [<c0279ab3>] local_pci_probe+0x13/0x20
Jun 28 17:01:34 eeepc kernel: [ 744.083856] kmemleak: [<c027a608>] pci_device_probe+0x68/0x90
Jun 28 17:01:34 eeepc kernel: [ 744.083864] kmemleak: [<c0312670>] driver_probe_device+0x70/0x140
Jun 28 17:01:34 eeepc kernel: [ 744.083872] kmemleak: [<c031293a>] __driver_attach+0x7a/0x80
Jun 28 17:01:34 eeepc kernel: [ 744.083881] kmemleak: [<c0311af9>] bus_for_each_dev+0x49/0x70
Jun 28 17:01:34 eeepc kernel: [ 744.083888] kmemleak: [<c031250e>] driver_attach+0x1e/0x20
Jun 28 17:01:34 eeepc kernel: [ 744.083896] kmemleak: [<c0312188>] bus_add_driver+0xd8/0x290
Jun 28 17:01:34 eeepc kernel: [ 744.083904] kmemleak: [<c0312a6f>] driver_register+0x5f/0x120
Jun 28 17:01:34 eeepc kernel: [ 744.083911] kmemleak: [<c027a443>] __pci_register_driver+0x53/0xc0
Jun 28 17:01:34 eeepc kernel: [ 744.083922] kmemleak: [<c061d82d>] init_ath5k_pci+0x1d/0x40
Jun 28 17:01:34 eeepc kernel: [ 744.083929] kmemleak: [<c0101122>] do_one_initcall+0x32/0x1d0
Jun 28 17:01:34 eeepc kernel: [ 744.083939] kmemleak: [<c05fe8aa>] kernel_init+0xba/0x110
Jun 28 17:01:34 eeepc kernel: [ 744.084074] kmemleak: unreferenced object 0xf5845b60 (size 64):
Jun 28 17:01:34 eeepc kernel: [ 744.084080] kmemleak: comm "swapper", pid 1, jiffies 4294683694
Jun 28 17:01:34 eeepc kernel: [ 744.084085] kmemleak: backtrace:
Jun 28 17:01:34 eeepc kernel: [ 744.084093] kmemleak: [<c01a749d>] kmemleak_alloc+0x11d/0x2a0
Jun 28 17:01:34 eeepc kernel: [ 744.084100] kmemleak: [<c01a4376>] __kmalloc+0x136/0x210
Jun 28 17:01:34 eeepc kernel: [ 744.084111] kmemleak: [<c0239880>] __crypto_alloc_tfm+0x40/0x170
Jun 28 17:01:34 eeepc kernel: [ 744.084120] kmemleak: [<c0239cbc>] crypto_alloc_base+0x3c/0x80
Jun 28 17:01:34 eeepc kernel: [ 744.084128] kmemleak: [<c04420ff>] ieee80211_wep_init+0x2f/0x80
Jun 28 17:01:34 eeepc kernel: [ 744.084136] kmemleak: [<c043fa9d>] ieee80211_register_hw+0x1fd/0x4b0
Jun 28 17:01:34 eeepc kernel: [ 744.084144] kmemleak: [<c04630d5>] ath5k_pci_probe+0xee5/0x1100
Jun 28 17:01:34 eeepc kernel: [ 744.084153] kmemleak: [<c0279ab3>] local_pci_probe+0x13/0x20
Jun 28 17:01:34 eeepc kernel: [ 744.084160] kmemleak: [<c027a608>] pci_device_probe+0x68/0x90
Jun 28 17:01:34 eeepc kernel: [ 744.084168] kmemleak: [<c0312670>] driver_probe_device+0x70/0x140
Jun 28 17:01:34 eeepc kernel: [ 744.084175] kmemleak: [<c031293a>] __driver_attach+0x7a/0x80
Jun 28 17:01:34 eeepc kernel: [ 744.084184] kmemleak: [<c0311af9>] bus_for_each_dev+0x49/0x70
Jun 28 17:01:34 eeepc kernel: [ 744.084191] kmemleak: [<c031250e>] driver_attach+0x1e/0x20
Jun 28 17:01:34 eeepc kernel: [ 744.084199] kmemleak: [<c0312188>] bus_add_driver+0xd8/0x290
Jun 28 17:01:34 eeepc kernel: [ 744.084207] kmemleak: [<c0312a6f>] driver_register+0x5f/0x120
Jun 28 17:01:34 eeepc kernel: [ 744.084214] kmemleak: [<c027a443>] __pci_register_driver+0x53/0xc0
There were quite a few leaks before this. I dunno if kmemleak is
spurious or not. As always, any ideas?
--
Sitsofe | http://sucs.org/~sits/
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox