On Sat, Mar 15, 2014 at 9:11 PM, Johannes Berg
wrote:
> On Sat, 2014-03-15 at 21:03 +0530, Krishna Chaitanya wrote:
>
>> > > what RC are u using? Default should be minstrel, i dont see
>> > > a reason for rc alloc to fail (remote reason kmalloc failure),
>> > > so did you disable RC completely?
On Sat, 2014-03-15 at 21:03 +0530, Krishna Chaitanya wrote:
> > > what RC are u using? Default should be minstrel, i dont see
> > > a reason for rc alloc to fail (remote reason kmalloc failure),
> > > so did you disable RC completely? No prints either w.r.t RC either in
> > > dmesg?
> >
> > Pay
On Sat, Mar 15, 2014 at 8:50 PM, Johannes Berg
wrote:
>
> On Thu, 2014-03-13 at 02:15 +0530, Krishna Chaitanya wrote:
>
> > From the logs it looks like "rate_control_alloc" is failed,
> > causing ieee80211_register_hw to fail triggering the crash.
>
> Yes.
>
> > what RC are u using? Default
On Thu, 2014-03-13 at 02:15 +0530, Krishna Chaitanya wrote:
> From the logs it looks like "rate_control_alloc" is failed,
> causing ieee80211_register_hw to fail triggering the crash.
Yes.
> what RC are u using? Default should be minstrel, i dont see
> a reason for rc alloc to fail (remote
On Thu, 2014-03-13 at 02:15 +0530, Krishna Chaitanya wrote:
From the logs it looks like rate_control_alloc is failed,
causing ieee80211_register_hw to fail triggering the crash.
Yes.
what RC are u using? Default should be minstrel, i dont see
a reason for rc alloc to fail (remote reason
On Sat, Mar 15, 2014 at 8:50 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Thu, 2014-03-13 at 02:15 +0530, Krishna Chaitanya wrote:
From the logs it looks like rate_control_alloc is failed,
causing ieee80211_register_hw to fail triggering the crash.
Yes.
what RC are u using?
On Sat, 2014-03-15 at 21:03 +0530, Krishna Chaitanya wrote:
what RC are u using? Default should be minstrel, i dont see
a reason for rc alloc to fail (remote reason kmalloc failure),
so did you disable RC completely? No prints either w.r.t RC either in
dmesg?
Pay attention to the
On Sat, Mar 15, 2014 at 9:11 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Sat, 2014-03-15 at 21:03 +0530, Krishna Chaitanya wrote:
what RC are u using? Default should be minstrel, i dont see
a reason for rc alloc to fail (remote reason kmalloc failure),
so did you disable RC
Hi Martin,
On Wed, Mar 12, 2014 at 06:08:06PM +0100, Martin Pitt wrote:
> Hey Fengguang,
>
> Fengguang Wu [2014-03-05 21:23 +0800]:
> > git bisect start v3.10 v3.9 --
[snip]
> > git bisect bad d8efcf38b13df3e9e889cf7cc214cb85dc53600c # 04:30 0-
> >3 Merge tag 'for-linus' of
Hi Martin,
On Wed, Mar 12, 2014 at 06:08:06PM +0100, Martin Pitt wrote:
Hey Fengguang,
Fengguang Wu [2014-03-05 21:23 +0800]:
git bisect start v3.10 v3.9 --
[snip]
git bisect bad d8efcf38b13df3e9e889cf7cc214cb85dc53600c # 04:30 0-
3 Merge tag 'for-linus' of
On Wed, Mar 12, 2014 at 11:04 PM, Martin Pitt wrote:
>
> Fengguang Wu [2014-03-08 20:11 +0800]:
> > [4.429993] mac80211_hwsim: ieee80211_register_hw failed (-2)
> > [...]
> > [4.431924] [] get_device+0xf/0x17
> > [4.431924] [] driver_detach+0x38/0x8f
> > [4.431924] []
Fengguang Wu [2014-03-08 20:11 +0800]:
> [4.429993] mac80211_hwsim: ieee80211_register_hw failed (-2)
> [...]
> [4.431924] [] get_device+0xf/0x17
> [4.431924] [] driver_detach+0x38/0x8f
> [4.431924] [] bus_remove_driver+0x53/0x66
> [4.431924] [] driver_unregister+0x38/0x3d
Hey Fengguang,
Fengguang Wu [2014-03-05 21:23 +0800]:
> git bisect start v3.10 v3.9 --
> git bisect bad ff89acc563a0bd49965674f56552ad6620415fe2 # 03:01 0-
> 2 Merge branch 'rcu/urgent' of
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
> git bisect bad
Hey Fengguang,
Fengguang Wu [2014-03-05 21:23 +0800]:
git bisect start v3.10 v3.9 --
git bisect bad ff89acc563a0bd49965674f56552ad6620415fe2 # 03:01 0-
2 Merge branch 'rcu/urgent' of
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
git bisect bad
Fengguang Wu [2014-03-08 20:11 +0800]:
[4.429993] mac80211_hwsim: ieee80211_register_hw failed (-2)
[...]
[4.431924] [c12377de] get_device+0xf/0x17
[4.431924] [c123a165] driver_detach+0x38/0x8f
[4.431924] [c1239433] bus_remove_driver+0x53/0x66
[4.431924] [c123a535]
On Wed, Mar 12, 2014 at 11:04 PM, Martin Pitt martin.p...@ubuntu.com wrote:
Fengguang Wu [2014-03-08 20:11 +0800]:
[4.429993] mac80211_hwsim: ieee80211_register_hw failed (-2)
[...]
[4.431924] [c12377de] get_device+0xf/0x17
[4.431924] [c123a165] driver_detach+0x38/0x8f
[
Martin,
These are long term bug and is still showing up in linux-next.
It can be reliably reproduced with the below KVM script.
#!/bin/bash
kvm=(
qemu-system-x86_64 -cpu kvm64 -enable-kvm
-kernel $1
-smp 2
-m 256M
-net
Martin,
These are long term bug and is still showing up in linux-next.
It can be reliably reproduced with the below KVM script.
#!/bin/bash
kvm=(
qemu-system-x86_64 -cpu kvm64 -enable-kvm
-kernel $1
-smp 2
-m 256M
-net
18 matches
Mail list logo
