On Fri, 2019-09-20 at 16:57 +0100, Anton Ivanov wrote:
> Looks like the culprit is a different default elf start address on 5.x
>
> What changes is not the sbrk(0) or _end - these are pretty much
> identical as in 4.x. It is the START which after some "fixups" in
> arch/um/kernel/uml.lds.S becom
Hi,
> >> To summarise, a WPA-TKIP managed connection stops passing traffic and
> >> the kernel log shows the message "WPA: Group rekeying". This apparently
> >> doesn't happen if the connection is in heavy use at the time or with
> >> module parameter swcrypto=1. WPA2 is not affected either.
> >
Hi Ben,
Thanks for the report.
On Mon, 2012-02-27 at 05:33 +, Ben Hutchings wrote:
> Several Debian users (cc'd) have reported a regression in iwlagn in
> Linux 3.1, not fixed in 3.2. The full bug log is at:
>
> http://bugs.debian.org/651199
>
> To summarise, a WPA-TKIP managed connection
On Wed, 2011-11-09 at 05:44 +, Ben Hutchings wrote:
> +static bool init_blocked = false;
> +
> +/* Initial state set by 'radio' parameter, as in the fsaa1655g driver */
> +module_param_named(radio, init_blocked, invbool, 0);
I wonder what you need this for -- it shouldn't be necessary and the
On Wed, 2010-10-13 at 17:17 +0200, Julien Cristau wrote:
> Getting lots of those in dmesg:
> iwlagn :0c:00.0: Too many chunks: 2
>
> Doesn't seem to prevent the network from working though.
It'll at least leak lots of memory though. But I think the check there
is just wrong -- there are TFDs
On Sun, 2010-10-10 at 20:03 +0100, Ben Hutchings wrote:
> > I have, however much more recently than that kernel, cleaned this up in
> > commit ff0d91c3eea6e25b47258349b455671f98f1b0cd -- this particular
> > allocation is now 2048 or 4096 bytes depending on the architecture (32
> > vs 64 bit pointe
On Wed, 2010-10-06 at 22:54 +0100, Ben Hutchings wrote:
> On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote:
> > Package: linux-2.6
> > Version: 2.6.32-23
> > Oct 6 21:05:02 radis kernel: [378665.326381] NetworkManager: page
> > allocation failure. order:4, mode:0x40d0
> > Oct 6 21:05:02
rather than returning NULL, and change
> ieee80211_add_key() accordingly.
>
> Compile-tested only.
Looks good to me.
Acked-by: Johannes Berg
> Reported-by: Marcin Owsiany
> Signed-off-by: Ben Hutchings
> ---
> net/mac80211/aes_ccm.c |6 ++
> net/mac8
Hi,
Thanks for the report.
On Mon, 2009-12-21 at 23:50 +, Ben Hutchings wrote:
> > [ 65.034652] ath0: direct probe to AP 00:11:95:77:e0:b0 (try 1)
> > [ 65.036737] ath0: direct probe responded
> > [ 65.036746] ath0: authenticate with AP 00:11:95:77:e0:b0 (try 1)
> > [ 65.038335] ath0
On Mon, 2009-06-01 at 11:45 +0200, Josselin Mouette wrote:
> Le lundi 01 juin 2009 à 10:35 +0100, Ben Hutchings a écrit :
> > Unfortunately no-one involved in g-p-m ever specified exactly what the
> > kernel bug is or was that they believed was responsible. I am as much
> > in the dark as you are.
On Tue, 2008-11-11 at 20:05 +0100, Andreas Henriksson wrote:
> On tis, 2008-11-11 at 19:03 +0100, Johannes Berg wrote:
> > Did you get around to looking at this? I just ran into this again.
>
> The conclusion was that it was a kernel problem. Patrick McHardy sent a
> patch,
On Sat, 2008-07-05 at 14:19 +0200, Andreas Henriksson wrote:
> On lör, 2008-07-05 at 13:48 +0200, Johannes Berg wrote:
> > ip link set wlan0 down
> > iwconfig wlan0 mode repeater # set WDS mode but no peer address
> > ip link set wlan0 up
>
> Unfortunately, this fai
On Wed, 2008-07-02 at 18:27 -0500, Larry Finger wrote:
> Johannes Berg wrote:
> > On Thu, 2008-07-03 at 01:08 +0200, Rafael J. Wysocki wrote:
> >> On Thursday, 3 of July 2008, Johannes Berg wrote:
> >>> Rafael, you misled me :) This is a completely different thing.
&
On Thu, 2008-07-03 at 01:08 +0200, Rafael J. Wysocki wrote:
> On Thursday, 3 of July 2008, Johannes Berg wrote:
> > On Wed, 2008-07-02 at 23:40 +0200, Rafael J. Wysocki wrote:
> > > On Wednesday, 2 of July 2008, Giacomo Mulas wrote:
> > > > I tried searching on the
On Wed, 2008-07-02 at 23:40 +0200, Rafael J. Wysocki wrote:
> On Wednesday, 2 of July 2008, Giacomo Mulas wrote:
> > I tried searching on the list for this, before posting, but searching the
> > mailing list archives with keywords such as b43, suspend, resume... brings
> > up such a ludicrous amoun
On Wed, 2008-07-02 at 17:32 -0500, Larry Finger wrote:
> Johannes Berg wrote:
> >>> I think you need the appended patch, but it only applies to linux-next.
> >> A different version has been merged into what will become 2.6.26. I'll
> >> see what
On Wed, 2008-07-02 at 23:40 +0200, Rafael J. Wysocki wrote:
> On Wednesday, 2 of July 2008, Giacomo Mulas wrote:
> > I tried searching on the list for this, before posting, but searching the
> > mailing list archives with keywords such as b43, suspend, resume... brings
> > up such a ludicrous amoun
> > I think you need the appended patch, but it only applies to linux-next.
>
> A different version has been merged into what will become 2.6.26. I'll
> see what we can do about stable.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ef3a62d272f033989e83eb1f26505f
Package: linux-image-powerpc64
Severity: normal
This bug report exists upstream but for your information and for tracking...
The wireless extensions used by wpa supplicant, wireless-tools and various
other programs are broken for 32-bit programs running on 64-bit kernels
because they use pointers
Package: linux-2.6
Severity: normal
On my new quad powermac, the debian installer kernel fails to boot properly
-- it hangs early in the kernel boot process.
A custom netinstall iso with Linus current git tree works fine (my head is
d89b8f40fca43cab829fea5c0e7d3951db2fb4bd which is this commit:
h
20 matches
Mail list logo
