lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 18 Sep 2009 09:00:28 +0200
From:	Ivo Van Doorn <ivdoorn@...il.com>
To:	Julian Calaby <julian.calaby@...il.com>
Cc:	Alejandro Riveira Fernández <ariveira@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"John W. Linville" <linville@...driver.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: [rt2x00] rt2500pci is spamming syslogd since upgrade to 2.6.31

On Fri, Sep 18, 2009 at 8:37 AM, Julian Calaby <julian.calaby@...il.com> wrote:
> 2009/9/16 Ivo van Doorn <ivdoorn@...il.com>:
>> Hi,
>>
>>>  Hi; my syslog has many entries like this since the upgrade to 2.6.31
>>>
>>>  phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
>>>
>>>  Sometimes the driver just start spamming like crazy sometimes is at less rate
>>>  sometimes it does not appear.
>>>
>>>  I'm running 2.6.31 with a revert [1] config follows. If more info is needed
>>>  just ask
>>>
>>>  [1] http://bugzilla.kernel.org/show_bug.cgi?id=13362
>>
>> Try disabling powersaving,
>>
>>        iwconfig wlan0 power off
>
> I have an identical problem, which is fixed by this command.
>
> It is possible to detect that the chip doesn't, for whatever reason,
> support powersaving and disable it in the driver?

Well I simply have to:
a) fix the driver to handle powersaving better
b) disable powersaving support for the driver

It will probably be (b) first followed by (a) much later if I ever
get the time to look into the issue.

Ivo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ