On Monday 04 September 2006 06:38, Larry Finger wrote:
> John,
>
> Please queue the following patch for wireless-2.6. It removes some code that
> was made obsolete by
> the wireless statistics changes of several weeks ago, but was not noticed
> them.
>
> Thanks,
>
> Larry
>
> ===
Hi Stephen !
To try to validate some PCIe code we have around, I got myself a
SysKonnect SK-9Exx card (one x1 lane one port and one x4 lanes 2 ports
actually, though I've only tested the first one at this point, based on
a 88E8061 Marvell chip).
I've used the sky2 driver as of a random last week'
John,
Please queue the following patch for wireless-2.6. It removes some code that was made obsolete by
the wireless statistics changes of several weeks ago, but was not noticed them.
Thanks,
Larry
=
This patch removes code that was make obsolete when the wireless statistics
On Mon, Sep 04, 2006 at 09:44:02AM +0900, Horms wrote:
> On Mon, Sep 04, 2006 at 01:09:59AM +0200, Patrick McHardy wrote:
> > Horms wrote:
> > > I'm not entirely sure what happens in the case of a valid port,
> > > at best it'll be silently ignored. This patch ignores them a little
> > > more verbo
On Mon, Sep 04, 2006 at 01:09:59AM +0200, Patrick McHardy wrote:
> Horms wrote:
> > I'm not entirely sure what happens in the case of a valid port,
> > at best it'll be silently ignored. This patch ignores them a little
> > more verbosely.
> >
> > Signed-Off-By: Simon Horman <[EMAIL PROTECTED]>
>
Hey Jesse, thanks for your reply. Here is the stuff on /procs. The weird
part is that I have several other identical systems and only one is
affected. Today I moved the hard drive to another similar system and I am
not seeing the problem so I am wondering if is something maybe wrong with
the ca
Horms wrote:
> I'm not entirely sure what happens in the case of a valid port,
> at best it'll be silently ignored. This patch ignores them a little
> more verbosely.
>
> Signed-Off-By: Simon Horman <[EMAIL PROTECTED]>
> Index: linux-2.6/net/ipv4/ipvs/ip_vs_ftp.c
>
Philip Molter wrote:
Michael Chan wrote:
On Tue, 2006-08-08 at 01:24 +0200, Bernd Schubert wrote:
tg3.c:v3.49 (Feb 2, 2006)
acpi_bus-0201 [01] bus_set_power : Device is not power
manageable
eth1: Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)]
(PCIX:100MHz:64-bit) 10/100/1000BaseT Eth
Joerg Roedel wrote:
> On Fri, Sep 01, 2006 at 06:24:56PM +0200, Patrick McHardy wrote:
>>
>>>+fl.oif = 0;
>>>+fl.nl_u.ip4_u.daddr = tunnel->parms.iph.daddr;
>>>+fl.nl_u.ip4_u.saddr = tunnel->parms.iph.saddr;
>>>+fl.nl_u.ip4_u.saddr = 0;
>>>+fl.proto = IPPROTO_ETHERIP;
>>
>>This
Sorry - reply-all got a bounce, didn't check the bad netdev address...
-- Forwarded message --
From: Alessandro Suardi <[EMAIL PROTECTED]>
Date: Sep 4, 2006 12:07 AM
Subject: Re: Problems with ipv4 part of Kernels post-2.6.16
To: Willy Tarreau <[EMAIL PROTECTED]>
Cc: Rogério Brito
Francois Romieu wrote:
> Larry Finger <[EMAIL PROTECTED]> :
>> When booting the latest version of Linville's wireless-dev
>> and starting my BCM4306 with WPA-PSK TKIP, the I get the
>> following INFO printout that indicates a possible circular locking dependency
>> involving 80211 and wpa_supplican
Larry Finger <[EMAIL PROTECTED]> :
> When booting the latest version of Linville's wireless-dev
> and starting my BCM4306 with WPA-PSK TKIP, the I get the
> following INFO printout that indicates a possible circular locking dependency
> involving 80211 and wpa_supplicant.
Please try the patch belo
Herbert Xu wrote:
> [NET]: Drop tx lock in dev_watchdog_up
>
> On Sat, Sep 02, 2006 at 08:39:28PM +, Krzysztof Halasa wrote:
>> ===
>> [ INFO: possible circular locking dependency detected ]
>>
On Fri, Sep 01, 2006 at 06:24:56PM +0200, Patrick McHardy wrote:
Hello Patrick,
Thank you very much for reviewing my driver. I will fix the issues you
mentioned. But I have some explanations and questions left.
> Joerg Roedel wrote:
> > + fl.oif = 0;
> > + fl.nl_u.ip4_u.daddr = tunnel->parms
On 9/2/06, Paul Aviles <[EMAIL PROTECTED]> wrote:
I am getting "e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang" using
stock 2.6.17.11, 2.6.17.5 or 2.6.17.4 kernels on centos 4.3.
The server is a Tyan GS12 ( 82541GI/PI and 82547GI) and is connected to a
Netgear GS724T Gig switch. I can
When booting the latest version of Linville's wireless-dev and starting my
BCM4306 with WPA-PSK
TKIP, the I get the following INFO printout that indicates a possible circular
locking dependency
involving 80211 and wpa_supplicant.
Thanks,
Larry
kernel: ==
Michael Buesch wrote:
>
> John, please apply the following patch to wireless-dev.
> (And please apply all the other patches, too, as I'm still
> waiting to pull ;) )
>
> --
>
> Don't disable IRQs in PHY init.
>
> Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>
>
The patch fixes the problem
In article <[EMAIL PROTECTED]> (at Sun, 3 Sep 2006 10:28:30 +0300), Rémi
Denis-Courmont <[EMAIL PROTECTED]> says:
> This patch should add support for -1 as "default" IPv6 traffic class, as
> specified in IETF RFC3542 §6.5. Within the kernel, it seems tclass < 0
> is already handled, but setsock
On Sunday 03 September 2006 05:42, Larry Finger wrote:
> The latest git pull from wireless-dev (g7844a579) is calling a sleeping
> function with irq's
> disabled. The kernel is a UP version with preemption disabled. The dump is as
> follows:
>
> kernel: bcm43xx_d80211: Virtual interface added (t
Herbert Xu <[EMAIL PROTECTED]> writes:
> [NET]: Drop tx lock in dev_watchdog_up
> --- a/net/sched/sch_generic.c
> +++ b/net/sched/sch_generic.c
> @@ -238,9 +238,7 @@ void __netdev_watchdog_up(struct net_dev
>
> static void dev_watchdog_up(struct net_device *dev)
> {
> - netif_tx_lock_bh(de
jamal wrote:
> Could you point me to it? I can look at it over the weekend.
I posted it here on netdev, look for nl80211.
> It may be we need to add another feature to genl to accomodate this.
> Example by setting a flag to indicate supportability. However, it does
> sound like this is something
On Sun, Sep 03, 2006 at 01:26:59AM +, Dave Jones wrote:
> Seen during boot of a 2.6.18rc5-git1 based kernel.
>
> ===
> [ INFO: possible circular locking dependency detected ]
> 2.6.17-1.2608.fc6 #1
> --
[NET]: Drop tx lock in dev_watchdog_up
On Sat, Sep 02, 2006 at 08:39:28PM +, Krzysztof Halasa wrote:
>
> ===
> [ INFO: possible circular locking dependency detected ]
> ---
> swapper/0 is t
hi Stephen,
you can check these:
http://bcm43xx.berlios.de/
http://madwifi.org/
R
/frank
From: Stephen Hemminger <[EMAIL PROTECTED]>
To: "Frank Schneider" <[EMAIL PROTECTED]>
CC: netdev@vger.kernel.org
Subject: Re: Loop detected - calling function from different modules
Date: Wed, 30 Aug
Francois Romieu <[EMAIL PROTECTED]> writes:
> dev_activate takes BH disabling locks only. How could a softirq happen
> on the same cpu and trigger a deadlock ?
That's BTW "possible circular locking dependency" and there is only
one CPU (no HT, single core - an old mobile Celeron P3).
I have to a
Hello,
This patch should add support for -1 as "default" IPv6 traffic class, as
specified in IETF RFC3542 §6.5. Within the kernel, it seems tclass < 0
is already handled, but setsockopt, getsockopt and recvmsg calls won't
accept it from userland.
Signed-off-by: Remi Denis-Courmont <[EM
26 matches
Mail list logo