The extended rates element is only needed if there are more than 8 rates
to report - which is normal for G operation, but not necessary. It only
exists because a particularly popular old 11b MAC codebase crashed when
the normal rate element had more than 8 elements, and this hurt
interoperability w
Stephen Hemminger wrote:
On Tue, 05 Sep 2006 21:36:24 -0400
Daniel Drake <[EMAIL PROTECTED]> wrote:
There's a strange sky2 bug on the Gentoo bugzilla:
http://bugs.gentoo.org/show_bug.cgi?id=136508
sky2 seems to work OK, but breaks as soon as the iptables ruleset is
loaded. Nothing can be pinge
Jesse, today the server froze and was not able to see anything in the logs.
Nothing at all about any error, just plain froze. Just in case, this is a
different unit altogether, still the same model as the units having the Tx
Unit Hang, but different memory, motherboard and CPU. The only 1 thing
please consider for 2.6.18 -- thanks!
[ATM]: potential NULL pointer dereference in clip_mkip()
http://article.gmane.org/gmane.linux.kernel/445717
When re-processing received data, a struct sk_buff pointer skb may be
dereferenced after a free operation.
From: Frederik Deweerdt <[EMAIL PROTECTED]
please consider for 2.6.18 -- thanks!
[ATM]: [he] don't hold the device lock when upcalling
This can create a deadlock/lock ordering problem with other layers that
want to use the transmit (or other) path of the card at that time.
Signed-off-by: Chas Williams <[EMAIL PROTECTED]>
---
commit fc6b
please consider for 2.6.18 -- thanks!
[ATM]: [he] he_init_one() is declared __devinit, but calls __init functions
he_init_one() is declared __devinit, but calls lots of init functions
that are marked __init. However, if CONFIG_HOTPLUG is enabled,
__devinit functions go into normal .text, which l
On Sun, 17 Sep 2006 00:19:48 +0200
bert hubert <[EMAIL PROTECTED]> wrote:
> The bad news is that I haven't yet been able to capture traces.
> Once every three days or so I get a crash of 2.6.18-rc[67] which
> *probably* end in tcp_ack(), but I don't have the exact dump.
>
> My .config is indeed
The bad news is that I haven't yet been able to capture traces.
Once every three days or so I get a crash of 2.6.18-rc[67] which
*probably* end in tcp_ack(), but I don't have the exact dump.
My .config is indeed heavy on TCP congestion stuff:
$ zcat /proc/config.gz | grep -i tcp
CONFIG_INET_TCP_
On Saturday 16 September 2006 01:50, mabbas wrote:
> I see your point here, although some one will file some bugs against the
> driver about showing G while associating with B-mode AP. By the way how
> can you figure if the AP is B/G other than the rates?
I don't think this will happen.
This nev
On Mon, Jun 19, 2006 at 05:24:31PM +0200, Andi Kleen wrote:
>
> > If you use "pmtmr" try to reboot with kernel option "clock=tsc".
>
> That's dangerous advice - when the system choses not to use
> TSC it often has a reason.
I just found out that TSC clocksource is not implemented on x86-64.
Kern
The patch which introduces the BEET mode and which previously was sent to this
mailing list is valid also for
http://www.kernel.org/git/?p=linux/kernel/git/davem/net-2.6.19.git;a=summary
branch.
However there are probably some errors in attaching inline the patch to the
mail.
I retry to reattach
11 matches
Mail list logo
