Hello, Michael!
I did more testing, and the results are following. It looks like the
oopses and panics on i386 were triggered by 4k stacks. x86_64 doesn't
have this option.
Now that I enabled other debug options on both platforms. but not 4k
stacks, I'm seeing exactly the same problem on each p
Removed unused code in en_dis_able_nic_intrs(), TX_DMA_INTR, RX_DMA_INTR,
TX_XGXS_INTR, MC_INTR
Signed-off-by: Sivakumar Subramani <[EMAIL PROTECTED]>
---
diff -urpN patch3/drivers/net/s2io.c patch4/drivers/net/s2io.c
--- patch3/drivers/net/s2io.c 2007-01-08 23:38:48.0 +0530
+++ patch4/d
1. Fix for updating skb->truesize properly.
2. Disable NAPI only if more than one ring configured in case of MSI/MSI-X
interrupts. Previously we were disabling NAPI irrespective of number of
rings when MSI/MSI-X interrupts were used.
3. Code cleanup.
Signed-off-by: Sivakumar Subramani <[EMAI
1. Fix for reset and link handling.
2. Allow for promiscuos mode and multicast state be maintained through
ifconfig up and down.
3. Support to print adapter serial number.
Signed-off-by: Sivakumar Subramani <[EMAIL PROTECTED]>
---
diff -urpN patch1/drivers/net/s2io.c patch2/drivers/net/s2io.c
-
This patch adds two load parameters napi and ufo. Previously NAPI was
compilation option with these changes wan enable disable NAPI using load
parameter. Also we are introducing ufo load parameter to enable/disable
ufo feature
Signed-off-by: Sivakumar Subramani <[EMAIL PROTECTED]>
---
diff -urpN o
YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]> (at Wed, 17 Jan 2007 18:51:14
> +0300), Dmitry Mishin <[EMAIL PROTECTED]> says:
>
>> ===
>> L2 network namespaces
>>
>> The most straightforward concept of network virtualization
On Wed, Jan 17, 2007 at 05:39:51PM +0300, Evgeniy Polyakov wrote:
> On Wed, Jan 17, 2007 at 07:21:42PM +0530, Suparna Bhattacharya ([EMAIL
> PROTECTED]) wrote:
> >
> > Since you are implementing new APIs here, have you considered doing an
> > aio_sendfilev to be able to send a header with the data
In article <[EMAIL PROTECTED]> (at Fri, 19 Jan 2007 01:31:08 +0900 (JST)),
Noriaki TAKAMIYA <[EMAIL PROTECTED]> says:
> >> Wed, 17 Jan 2007 13:33:22 +0100
> >> [Subject: Re: [PATCH] [IPV6] fixed the size of the netlink message
> >> notified by inet6_rt_notify().]
> >> Patrick McHardy <[EMAIL PRO
A number of the calls in the initialization routines fail to check the returned
value for
errors. This patch adds the necessary checks and logs any errors found when
appropriate.
Signed-off-by: Larry Finger <[EMAIL PROTECTED]>
---
To be applied to wireless-2.6.
Index: wireless-2.6/drivers/net
On Thu, 2007-01-18 at 17:54 -0500, Jon Smirl wrote:
> On 1/18/07, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> > On Thu, Jan 18, 2007 at 10:41:45AM -0500, Dan Williams wrote:
> > > In the future we'll likely need some layering to support the 8385
> > > SDIO/CF variant, but most likely not in way
On Thu, 2007-01-18 at 22:40 +, Christoph Hellwig wrote:
> On Thu, Jan 18, 2007 at 10:41:45AM -0500, Dan Williams wrote:
> > In the future we'll likely need some layering to support the 8385
> > SDIO/CF variant, but most likely not in way the USB support is currently
> > excessively layered and
On Thu, 2007-01-18 at 12:37 +0100, Patrick McHardy wrote:
> > Or are you proposing tc behave differently on different
> > kernel versions. (I have no problem with that, but
> > isn't it officially frowned upon?)
>
> Yes. There is no way you can make this work on old kernels,
> nobody expects that
John W. Linville wrote:
The following changes since commit 10764889c6355cbb335cf0578ce12427475d1a65:
Larry Finger (1):
bcm43xx: Fix failure to deliver PCI-E interrupts
are found in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
upstre
Adrian Bunk wrote:
"extern inline" generates a warning with -Wmissing-prototypes and I'm
currently working on getting the kernel cleaned up for adding this to
the CFLAGS since it will help us to avoid a nasty class of runtime
errors.
If there are places that really need a forced inline, __always
Adrian Bunk wrote:
The OAKNET driver:
- has been marked as BROKEN for more than two years and
- is still marked as BROKEN.
Drivers that had been marked as BROKEN for such a long time seem to be
unlikely to be revived in the forseeable future.
But if anyone wants to ever revive this driver, the
Stephen Hemminger wrote:
Speedup and cleanup the receive processing by eliminating the
mmio read and a lock round trip.
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
applied
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED
Stephen Hemminger wrote:
Cleanup receive processing some more:
* do the reserve padding of skb during setup
* don't pass constants to get_packet
* do smart prefetch of skb
* make copybreak a module parameter
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
applied
-
To unsubs
Divy Le Ray wrote:
Jeff Garzik wrote:
Divy Le Ray wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
This patch implements the main header files of
the Chelsio T3 network driver.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
Once you think it's ready, email me a URL to a single patch that adds
Adrian Bunk wrote:
hdlc_setup was exported, but this export was never used.
If a driver using it actually shows up it can still be exported again.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Acked-by: Krzysztof Halasa <[EMAIL PROTECTED]>
applied
-
To unsubscribe from this list: send the
Jay Cliburn wrote:
+static u32 atl1_get_tx_csum(struct net_device *netdev)
+{
+ return (netdev->features & NETIF_F_HW_CSUM) != 0;
+}
+
+static int atl1_set_tx_csum(struct net_device *netdev, u32 data)
+{
+ if (data)
+ netdev->features |= NETIF_F_HW_CSUM;
+ else
+
Sukadev Bhattiprolu wrote:
I get following panic on 2.6.20-rc4-mm1 on a 2-cpu AMD Opteron system.
Same basic config file seems to work with 2.6.20-rc2-mm1 on this same
system. Have not tried -rc3-mm1 yet.
Attached are config file and "lspci -vv" output. Let me know if you need
more info.
Suka
Ayaz Abdulla wrote:
This patch introduces hw statistics for older devices that supported it.
It breaks up the counters supported into separate versions.
Signed-Off-By: Ayaz Abdulla <[EMAIL PROTECTED]>
ACK patches 11-12
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
t
Ayaz Abdulla wrote:
This patch adds a limit to how much tx work can be done in each
iteration of tx processing.
Signed-Off-By: Ayaz Abdulla <[EMAIL PROTECTED]>
What about the "tail end" of the work, when the limit is reached?
Remember that delaying the completion of TX's too long increases l
Ayaz Abdulla wrote:
This patch modifys ring access by using pointers. This avoids computing
the current index and avoids accessing the base address of the rings.
Signed-Off-By: Ayaz Abdulla <[EMAIL PROTECTED]>
ACK patches 1-9.
Applied patches 1-4 successfully, patch #5 failed to apply. Plea
Auke Kok [EMAIL PROTECTED] wrote:
| Sukadev Bhattiprolu wrote:
| >I get following panic on 2.6.20-rc4-mm1 on a 2-cpu AMD Opteron system.
| >
| >Same basic config file seems to work with 2.6.20-rc2-mm1 on this same
| >system. Have not tried -rc3-mm1 yet.
| >
| >Attached are config file and "lspci -v
On Thu, 2007-01-18 at 20:59 +0100, Adrian Bunk wrote:
> Subject: CONFIG_JFFS2_FS_DEBUG=2 compile error
> References : http://lkml.org/lkml/2007/1/12/161
> Submitter : Russell King <[EMAIL PROTECTED]>
> Caused-By : Al Viro <[EMAIL PROTECTED]>
> commit 914e26379decf1fd984b22e51fd2e
I get following panic on 2.6.20-rc4-mm1 on a 2-cpu AMD Opteron system.
Same basic config file seems to work with 2.6.20-rc2-mm1 on this same
system. Have not tried -rc3-mm1 yet.
Attached are config file and "lspci -vv" output. Let me know if you need
more info.
Suka
---
[ 168.925840] Freeing
In article <[EMAIL PROTECTED]> (at Wed, 17 Jan 2007 18:51:14 +0300), Dmitry
Mishin <[EMAIL PROTECTED]> says:
> ===
> L2 network namespaces
>
> The most straightforward concept of network virtualization is complete
> separation of namespaces, covering device list,
On 1/18/07, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
On Thu, Jan 18, 2007 at 10:41:45AM -0500, Dan Williams wrote:
> In the future we'll likely need some layering to support the 8385
> SDIO/CF variant, but most likely not in way the USB support is currently
> excessively layered and abstracte
On Thu, Jan 18, 2007 at 10:41:45AM -0500, Dan Williams wrote:
> In the future we'll likely need some layering to support the 8385
> SDIO/CF variant, but most likely not in way the USB support is currently
> excessively layered and abstracted.
Yeah. Let's summarize my unfortunately a bit too nasty
Fix from http://bugzilla.kernel.org/show_bug.cgi?id=7747
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Signed-off-by: Francois Romieu <[EMAIL PROTECTED]>
---
drivers/net/sis190.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/sis19
On Thu, 2007-01-18 at 05:05 +0100, Patrick McHardy wrote:
> > Yesterday I was chatting about this at LCA 2007, and
> > it dawned on me that there is a problem with the dual
> > RTAB/STAB approach.
> >
> > Currently the lookup in the kernel is
> > time_to_transmit_a_packet = RTAB[packet_length_s
This patch removes kernel 2.4 compatibility code.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
drivers/net/irda/vlsi_ir.c | 16
drivers/net/irda/vlsi_ir.h | 33 -
2 files changed, 8 insertions(+), 41 deletions(-)
--- linux-2.6.20-rc4-m
This email lists some known regressions in 2.6.20-rc5 compared to 2.6.19
with patches available
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any othe
Jeff Garzik wrote:
> Chris Lalancette wrote:
>
>> Francois Romieu wrote:
>>
>>> Chris Lalancette <[EMAIL PROTECTED]> :
>>> [...]
>>>
>>>
Thanks for the comments. While the patch you sent will help,
there are
still other places that will have problems. For example, in
ne
On Thu, Jan 18, 2007 at 06:31:53PM +0100, Peter Zijlstra ([EMAIL PROTECTED])
wrote:
> > skbs are the most extensively used path.
> > Actually the same is applied to route - dst_entries and rtable are
> > allocated through own wrappers.
>
> Still, edit all places and perhaps forget one and make s
On Thu, 2007-01-18 at 18:50 +0300, Evgeniy Polyakov wrote:
> On Thu, Jan 18, 2007 at 04:10:52PM +0100, Peter Zijlstra ([EMAIL PROTECTED])
> wrote:
> > On Thu, 2007-01-18 at 16:58 +0300, Evgeniy Polyakov wrote:
> >
> > > Network is special in this regard, since it only has one allocation path
> >
Jeff Garzik wrote:
Kok, Auke wrote:
Hi,
This patch series contains exclusively fixes for e1000. Some of these
patches were
already sent in december, but didn't make it into any usptream tree
yet. Most
importantly, it addresses two issues in the recently merged msi interrupt
handler and dynam
Stephen Hemminger <[EMAIL PROTECTED]> writes:
> On Wed, 17 Jan 2007 19:11:52 +0300
> Dmitry Mishin <[EMAIL PROTECTED]> wrote:
>
>> Library function to create a seq_file in proc filesystem,
>> showing some information for each netdevice.
>> This code is present in the kernel in about 10 instances,
[EMAIL PROTECTED] wrote:
From: Timur Tabi <[EMAIL PROTECTED]>
The workqueue interface changed with David Howell's patch on 11/22/2006
(SHA 65f27f38446e1976cc98fd3004b110fedcddd189). Several drivers were
updated with that patch to handle the new interface, but ucc_geth.c
was not one of them. Th
Brice Goglin wrote:
Under some circumstances, using WC without the WC fifo is faster.
So we make it possible to tune wc_fifo with a module parameter.
Signed-off-by: Brice Goglin <[EMAIL PROTECTED]>
---
drivers/net/myri10ge/myri10ge.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
Ananda Raju wrote:
Hello,
List of changes in this patch:
This patch adds two load parameters napi and ufo. Previously NAPI was
compilation option with these changes wan enable disable NAPI using load
parameter. Also we are introducing ufo load parameter to enable/disable
ufo feature
S
Kok, Auke wrote:
Hi,
This patch series contains exclusively fixes for e1000. Some of these patches
were
already sent in december, but didn't make it into any usptream tree yet. Most
importantly, it addresses two issues in the recently merged msi interrupt
handler and dynamic itr code. A perform
Chris Lalancette wrote:
Francois Romieu wrote:
Chris Lalancette <[EMAIL PROTECTED]> :
[...]
Thanks for the comments. While the patch you sent will help, there are
still other places that will have problems. For example, in netpoll_send_skb,
we call local_irq_save(flags), then call dev
John W. Linville wrote:
The following changes since commit a8b3485287731978899ced11f24628c927890e78:
Linus Torvalds (1):
Linux v2.6.20-rc5
are found in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
upstream-fixes
Larry Finger (1):
Hi,
>> Wed, 17 Jan 2007 13:33:22 +0100
>> [Subject: Re: [PATCH] [IPV6] fixed the size of the netlink message notified
>> by inet6_rt_notify().]
>> Patrick McHardy <[EMAIL PROTECTED]> wrote...
> Somewhat related: I have this patch for 2.6.21 to get rid of the
> BUG_ON()s.
I think the problem i
The following changes since commit 10764889c6355cbb335cf0578ce12427475d1a65:
Larry Finger (1):
bcm43xx: Fix failure to deliver PCI-E interrupts
are found in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
upstream
Daniel Drake (6):
The following changes since commit a8b3485287731978899ced11f24628c927890e78:
Linus Torvalds (1):
Linux v2.6.20-rc5
are found in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git
upstream-fixes
Larry Finger (1):
bcm43xx: Fix failure
On Thu, Jan 18, 2007 at 04:10:52PM +0100, Peter Zijlstra ([EMAIL PROTECTED])
wrote:
> On Thu, 2007-01-18 at 16:58 +0300, Evgeniy Polyakov wrote:
>
> > Network is special in this regard, since it only has one allocation path
> > (actually it has one cache for skb, and usual kmalloc, but they are
>
On Wed, 2007-01-17 at 23:09 +, Christoph Hellwig wrote:
> On Wed, Jan 17, 2007 at 01:00:47PM -0500, Dan Williams wrote:
> > Furthermore, I might add that the entire reason this part was chosen for
> > OLPC was because it _is_ fullmac.
> >
> > To drive down power consumption, the OLPC puts the
On Wed, 2007-01-17 at 23:06 +, Christoph Hellwig wrote:
> On Wed, Jan 17, 2007 at 04:42:04PM -0200, Marcelo Tosatti wrote:
> > And using the Marvell provided firmware is a requirement for OLPC
> > machines, where the CPU will be shut down but the chip+firmware will
> > continue to forward packe
On Thu, 2007-01-18 at 16:58 +0300, Evgeniy Polyakov wrote:
> Network is special in this regard, since it only has one allocation path
> (actually it has one cache for skb, and usual kmalloc, but they are
> called from only two functions).
>
> So it would become
> ptr = network_alloc();
> and net
On Thu, Jan 18, 2007 at 01:18:44PM +0100, Peter Zijlstra ([EMAIL PROTECTED])
wrote:
> > > How would that end up being different, I would have to replace all
> > > allocations done in the full network processing path.
> > >
> > > This seems a much less invasive method, all the (allocation) code ca
Pekka Pietikainen <[EMAIL PROTECTED]> writes:
> On Wed, Jan 17, 2007 at 11:46:35AM -0500, Brandon Craig Rhodes wrote:
>> Having further reviewed my code, I have changed my mind; the
>> ieee80211_crypt_tkip routines are not designed to be responsible for
>> creating enough headroom and tailroom.
>
On Wed, Jan 17, 2007 at 11:46:35AM -0500, Brandon Craig Rhodes wrote:
> Having further reviewed my code, I have changed my mind; the
> ieee80211_crypt_tkip routines are not designed to be responsible for
> creating enough headroom and tailroom. The "hostap" driver should be
> doing this. In fact,
Dmitry Mishin <[EMAIL PROTECTED]> writes:
> On Wednesday 17 January 2007 23:16, Eric W. Biederman wrote:
>> Dmitry Mishin <[EMAIL PROTECTED]> writes:
>>
>> > Added functions and macros required to operate with network namespaces.
>> > They are required in order to switch network namespace for inc
On Tue, Jan 02, 2007 at 09:42:47PM -0500, John W. Linville wrote:
> The following changes since commit fe5f8e2a1c5c040209c598a28e19c55f30e1040d:
> Zhu Yi (1):
> ipw2100: Fix dropping fragmented small packet problem
>
> are found in the git repository at:
>
> git://git.kernel.org/pub/s
One thing I forgot is that the LED will be on only if the switch is in the on
position _AND_ the
interface is UP.
Yes I figured that out. (eventually)
>>> dhcpcd eth1 <-low transmit power???
>> Most likely. How far are you from the AP?
>
> This is a timeout issue. I tried to apply t
On Thu, 2007-01-18 at 13:41 +0300, Evgeniy Polyakov wrote:
> > > What about 'level-7' ack as you described in introduction?
> >
> > Take NFS, it does full data traffic in kernel.
>
> NFS case is exactly the situation, when you only need to generate an ACK.
No it is not, it needs the full RPC re
On Wednesday 17 January 2007 23:16, Eric W. Biederman wrote:
> Dmitry Mishin <[EMAIL PROTECTED]> writes:
>
> > Added functions and macros required to operate with network namespaces.
> > They are required in order to switch network namespace for incoming packets
> > and
> > to not extend current
On Wed, Jan 17, 2007 at 10:07:28AM +0100, Peter Zijlstra ([EMAIL PROTECTED])
wrote:
> > You operate with 'current' in different contexts without any locks which
> > looks racy and even is not allowed. What will be 'current' for
> > netif_rx() case, which schedules softirq from hard irq context -
>
On Wed, 2007-01-17 at 10:52 +0100, Michael Buesch wrote:
> Doesn't happen for me. I have no idea what's happening.
> Care to debug it?
> But it's weird that _killing_ the supplicant calls add_interface.
> I'd expect it to call remove_interface.
I'm sorry, I was actually running wpa_supplicant aga
Hi,
> My patch may seem like a huge change, but in essence the change is
> pretty simple.
>
> In my patch, the interrupt handler code will check whether the interrupted
> code is holding the swfw semaphore. If it is held, the watchdog function
> is deferred until swfw semaphore is released.
> The
On Wed, Jan 17, 2007 at 06:19:07PM -0500, Jeff Garzik wrote:
> Christoph Hellwig wrote:
> >On Wed, Jan 17, 2007 at 01:00:47PM -0500, Dan Williams wrote:
> >>allows the 8388 to continue routing other laptops' packets over the mesh
> >>*while the host CPU is asleep*.
> >
> >We're not going to put a
64 matches
Mail list logo
