[Removed XXX from subject in order to get past VGER spam filter]
On 20/06/11 11:30, Alan Jenkins wrote:
## Summary of bug report ##
Confidence: high.
(Bisected. Crash message captured, see end of message).
Severity: low.
(Users can easily avoid the trigger for this crash).
## Scenario
Alan Jenkins wrote:
Alan Stern wrote:
On Thu, 18 Jun 2009, Alan Jenkins wrote:
Unfortunately this makes it worse. My eeepc-laptop hacks are now in
wireless-testing. If I apply the above patch to wireless-testing and
remove the device while suspended, I get a soft hang
Bob Copeland wrote:
On Mon, Jun 15, 2009 at 09:58:30PM +0200, Rafael J. Wysocki wrote:
On Monday 15 June 2009, Alan Stern wrote:
I'm not sure whether the example is trustworthy. There was some
discussion quite a while ago regarding whether drivers should free
their IRQs during
Alan Stern wrote:
On Thu, 18 Jun 2009, Alan Jenkins wrote:
Unfortunately this makes it worse. My eeepc-laptop hacks are now in
wireless-testing. If I apply the above patch to wireless-testing and
remove the device while suspended, I get a soft hang on resume.
Is this different
Hi,
I triggered a WARNING while hacking on eeepc-laptop's
rfkill-by-pci-hotplug. I saw Trying to free already-free IRQ in
ath5k_pci_remove(), because the IRQ was already freed by
ath5k_pci_suspend(). My changes to eeepc-laptop had allowed the PCI
device to be removed while suspended.
Are
Alan Stern wrote:
On Mon, 15 Jun 2009, Alan Jenkins wrote:
Hi,
I triggered a WARNING while hacking on eeepc-laptop's
rfkill-by-pci-hotplug. I saw Trying to free already-free IRQ in
ath5k_pci_remove(), because the IRQ was already freed by
ath5k_pci_suspend(). My changes to eeepc
On 5/30/09, Johannes Berg johan...@sipsolutions.net wrote:
On Sat, 2009-05-30 at 00:33 +0200, Tobias Doerffel wrote:
Could you try to work against v11
of my rfkill patch, or better even against the cfg80211 rfkill instead?
I didn't look at both of them yet. However I think we first should
Alan Jenkins wrote:
Hi, today I tested wireless-testing +rfkill rewrite v11, +2.6.30-rc7
for some recent eeepc-laptop updates. See attached dmesg.
It boils down to this (during/immediately after resume, following a
couple of rfkill initiated hotplug cycles):
[ 327.859777] ath5k phy5: Atheros
John W. Linville wrote:
On Wed, Apr 15, 2009 at 11:58:39AM +0100, Alan Jenkins wrote:
[Corrected Luis address]
On 4/15/09, Alan Jenkins sourcejedi.l...@googlemail.com wrote:
Looking at the code, I think it does need fixing. There's even a
comment which says this finds them
Hi, while testing latest Git (i.e. 2.6.30-rc1 + a bit), I hit a bug
which killed my keyboard. SysRQ keys worked, but I couldn't type in X
or on the console. I've not been able to reproduce it so far. After
rebooting, I extracted the following from syslog:
[4.513996] usual_tables: module
Alan Jenkins wrote:
Hi, while testing latest Git (i.e. 2.6.30-rc1 + a bit), I hit a bug
which killed my keyboard. SysRQ keys worked, but I couldn't type in X
or on the console.
This happened when ath5k was loaded dynamically, in response to my
pressing the wireless toggle key. (rfkill
Pavel Roskin wrote:
On Fri, 2009-04-10 at 11:11 -0700, Luis R. Rodriguez wrote:
Thanks pavel, please try this patch:
I checked ath5k, ath9k and b43, and in all cases last_request is
initialized before it's used by the code changed in your patch. In
fact, last_request is
Maxim Levitsky wrote:
I have just bought an Aspire one A150, XP version,
as it was the only available here, and installed ubuntu on it.
Bugs I discovered so far:
** 1 - embedded controler works in polling mode, due to this:
[0.708571] ACPI: EC: non-query interrupt received,
Jiri Slaby wrote:
Alan Jenkins napsal(a):
Revert part of 3e4242b99ce46fed82aa7f40ad5a1817a2b3bd45,
Ath5k: suspend/resume fixes. This commit broke ath5k after a
suspend/resume cycle on my EeePC.
The problem code disables MSI on suspend and enables it on resume.
However MSI was intentionally
-merged code from a wireless-testing snapshot says that enabling
MSI results in no interrupts, seems msi support is still buggy.
Signed-off-by: Alan Jenkins [EMAIL PROTECTED]
---
Please accept this as an urgent fix to avoid a regression in 2.6.27.
I hope it is straightforward to review.
diff --git
Jiri Slaby wrote:
Bob Copeland napsal(a):
On Fri, Aug 1, 2008 at 4:14 AM, Andrew Morton [EMAIL PROTECTED] wrote:
On Fri, 01 Aug 2008 11:03:37 +0300 Pekka Enberg [EMAIL PROTECTED] wrote:
Jiri Slaby wrote:
Dave Young napsal(a):
In the
Frédéric Weisbecker wrote:
Yes I have the same problem.
I think I found the origin.
That's because wme_qdiscop_destroy in net/mac80211/wme.c passes a bad
pointer in tcf_destroy_chain.
It requires a struct tcf_proto **fl and not a struct tcf_proto *fl
Here is a patch, I can't test it because
I downloaded Nicks snapshot
http://www.kernel.org/pub/linux/kernel/people/mickflemm/compat-wireless-2008-07-03-ath5k.tar.bz2
and successfully compiled against v2.6.26. And it works! It's looking
up for my EeePC.
Range seems to be reduced (relative to madwifi), but I can successfully
connect
Alan Jenkins wrote:
I downloaded Nicks snapshot
http://www.kernel.org/pub/linux/kernel/people/mickflemm/compat-wireless-2008-07-03-ath5k.tar.bz2
and successfully compiled against v2.6.26. And it works! It's looking
up for my EeePC.
It panics if I unload it though. Fatal exception
19 matches
Mail list logo
