Re: dscape git

2006-07-17 Thread Erik Mouw
/git/jbenc/dscape.git dscape The "--reference" parameter tells git that I have a local repository called "linux-2.6" (which just follow Linus' 2.6 tree) which can be used to pull the shared git objects from. Saves quite some disk space. Erik -- +-- Erik Mouw -- www.hardd

Re: Private driver support emails should be avoided.

2006-08-04 Thread Erik Mouw
uk/pipermail/linux-arm-kernel/2006-August/035259.html Daniel Jacobowitz came up with this URL which could be uses as a starting point: http://www.eyrie.org/~eagle/faqs/questions.html Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 X

Support for Intel 82562V-2?

2007-08-06 Thread Erik Mouw
Hi, Just got a brand new Dell Vostro and it appears to have an unsupported Intel network card: 00:19.0 Ethernet controller: Intel Corporation 82562V-2 10/100 Network Connection (rev 02) Subsystem: Dell Unknown device 0238 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop

Re: Support for Intel 82562V-2?

2007-08-06 Thread Erik Mouw
On Mon, Aug 06, 2007 at 10:54:56AM -0700, Allan, Bruce W wrote: > While that is a "10/100 network connection", it is actually a GigE MAC > with a 10/100 PHY and will be supported by the e1000e driver that is > currently in the process of final cleanup before getting into the > upstream kernel. Ah

Re: [RFC/PATCH 1/2] in-kernel sockets API

2006-06-14 Thread Erik Mouw
n-kernel use of sockets. There is however one for user space. Erik (IANAL, etc) -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To unsubscribe from this list: send the line "unsubscribe netdev" in the

Re: Memory corruption in 8390.c ?

2006-06-22 Thread Erik Mouw
lot! :-) It sure is. Back in the old days I could saturate a 10 Mbit ethernet segment using a Western Digital 8003 (the 8 bit ISA card) in a 386DX40 (running Linux 1.0, 1.2, and 1.3). Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26

Re: eth interface enumeration order

2006-08-23 Thread Erik Mouw
the network devices (on 2.6 that should be done using udev). Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of

Re: [PATCH 11/21] nbd: limit blk_queue

2006-09-06 Thread Erik Mouw
t;); So what happens if the noop scheduler isn't compiled into the kernel? Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To unsubscribe from this list: send the line "unsubscribe netdev" in

Re: RFC/T: Possible fix for bcm43xx periodic work bug

2006-09-08 Thread Erik Mouw
On Thu, Sep 07, 2006 at 01:17:05PM -0500, Larry Finger wrote: > I think I have a fix for the bcm43xx bug that leads to NETDEV WATCHDOG tx > timeouts and would like it > to get as much testing as possible as this bug affects V2.6.18-rcX. If the > problem is truly > fixed, I hope to get the fix int

Re: RFC/T: Possible fix for bcm43xx periodic work bug

2006-09-08 Thread Erik Mouw
e problem, can we try to get it merged before 2.6.18 closes? I don't know if vanilla 2.6.18-rc6 locks up on other hardware as well, but if it does it would be a major regression against 2.6.17. Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftec

Re: RFC/T: Possible fix for bcm43xx periodic work bug

2006-09-11 Thread Erik Mouw
On Fri, Sep 08, 2006 at 08:36:36AM -0500, Larry Finger wrote: > Erik Mouw wrote: > > Thanks for the information, pulled wireless-2.6 and recompiling kernel. > > If this really fixes the problem, can we try to get it merged before > > 2.6.18 closes? I don't know if vani

Re: [PATCH] bcm43xx: fix netdev watchdog timeouts

2006-09-14 Thread Erik Mouw
2.6.18 together with this patch or we will see regression reports against 2.6.17. Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To unsubscribe from this list: send the line "unsubscribe netdev" i

Re: Bcm43xx softMac Driver in 2.6.18

2006-09-22 Thread Erik Mouw
Hunk #1 FAILED at 3182. 1 out of 1 hunk FAILED -- saving rejects to file drivers/net/wireless/bcm43xx/bcm43xx_main.c.rej Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To unsubscribe from this list:

[BUG NET/PCMCIA 2.6.17-rc1] Oops with cardctl eject

2006-04-06 Thread Erik Mouw
cking error or a network error, so I'm sending this message to lkml and netdev. If you need more information, feel free to ask. Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To unsubscribe from thi

[PATCH] bcm43xx: iw_priv_args names should be <16 characters

2006-04-13 Thread Erik Mouw
ot;set_swencryption", and "get_swencryption" private calls. Patch is against 2.6.17-rc1. Signed-off-by: Erik Mouw <[EMAIL PROTECTED]> diff --git a/drivers/net/wireless/bcm43xx/bcm43xx_wx.c b/drivers/net/wireless/bcm43xx/bcm43xx_wx.c index 3daee82..3edbb48 100644 --- a/drivers/net/w

Re: [PATCH] bcm43xx: iw_priv_args names should be <16 characters

2006-04-14 Thread Erik Mouw
On Thu, Apr 13, 2006 at 10:29:19AM -0700, Stephen Hemminger wrote: > On Thu, 13 Apr 2006 15:02:27 +0200 > Erik Mouw <[EMAIL PROTECTED]> wrote: > > > The room for the names in bcm43xx_priv_wx_args[] are IFNAMSIZ long and > > IFNAMSIZ is defined as 16, so the names in

Re: Linux v2.6.17-rc4

2006-05-12 Thread Erik Mouw
nuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1485:bcm43xx_find_lopair() ieee80211_crypt: registered algorithm 'WEP' Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To un

Re: Linux v2.6.17-rc4

2006-05-12 Thread Erik Mouw
ix this. If it's non-fatal, could you remove the assertion, or make it print something that sounds less fatal? Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To unsubscribe from this list: send

Re: How to submit a new module to linux kernel?

2006-05-22 Thread Erik Mouw
rocess take? See Documentation/SubmittingPatches in your kernel tree. Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To unsubscribe from this list: send the line "unsubscribe netdev" in the

Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing

2006-05-23 Thread Erik Mouw
andled the portnumbers. I'll check the ieee website to see how it > works, tnx! IEEE doesn't handle port numbers. Port numbers are for whatever is layered on top of ethernet, so you need to register those with the appropriate authorities (IANA for IP). Erik -- +-- Erik Mouw -- www

Transmit timeout with E1000

2006-01-10 Thread Erik Mouw
Hi, I have lots of transmit timeouts with an Intel E1000 card during large TCP transmissions (remotely viewing a 3000x2000 jpeg image using XV is an excellent way to trigger it). This is what I get in linux-2.6.8.1: Jan 10 15:24:41 zurix kernel: NETDEV WATCHDOG: eth0: transmit timed out Jan 10 15

Re: [E1000-devel] Transmit timeout with E1000

2006-01-11 Thread Erik Mouw
based? We have an E1000 dual interface server adapter on a dual Athlon with AMD 762 chipset running fine, and also the same kind of adapter on a dual Athlon64 with AMD-8111 chipset running fine. > On Tue, 10 Jan 2006, Erik Mouw wrote: > >And this is with linux-2.6.15: > > >

Re: [E1000-devel] Transmit timeout with E1000

2006-01-11 Thread Erik Mouw
On Wed, Jan 11, 2006 at 01:59:46PM +0100, Erik Mouw wrote: > On Tue, Jan 10, 2006 at 09:46:29AM -0800, Jesse Brandeburg wrote: > > sorry to hear you're having a problem, and cool, thanks for the test, > > we'll have to try it here. We've classically had problems re

Re: [E1000-devel] Transmit timeout with E1000

2006-01-11 Thread Erik Mouw
On Wed, Jan 11, 2006 at 02:22:08PM +0100, Erik Mouw wrote: > On Wed, Jan 11, 2006 at 01:59:46PM +0100, Erik Mouw wrote: > > On Tue, Jan 10, 2006 at 09:46:29AM -0800, Jesse Brandeburg wrote: > > > sorry to hear you're having a problem, and cool, thanks for the test, > >

Lots of "BUG eth1 code -5 qlen 0" messages in 2.6.24

2008-01-29 Thread Erik Mouw
Hi, I've just started to use 2.6.24 on my home firewall (before it was running 2.6.24-rc2 for about 65 days) and I noticed a couple of error messages I've never seen before: Jan 29 07:50:54 gateway kernel: BUG eth1 code -5 qlen 0 Jan 29 08:28:30 gateway kernel: BUG eth1 code -5 qlen 0 Jan 29 08:5

Re: Lots of "BUG eth1 code -5 qlen 0" messages in 2.6.24

2008-01-29 Thread Erik Mouw
On Tue, Jan 29, 2008 at 03:57:23PM -0500, jamal wrote: > On Tue, 2008-29-01 at 11:57 -0800, Waskiewicz Jr, Peter P wrote: > > > I've just started to use 2.6.24 on my home firewall (before > > > it was running 2.6.24-rc2 for about 65 days) and I noticed a > > > couple of error messages I've never

Re: Lots of "BUG eth1 code -5 qlen 0" messages in 2.6.24

2008-02-01 Thread Erik Mouw
On Tue, Jan 29, 2008 at 06:08:28PM -0500, jamal wrote: > On Tue, 2008-29-01 at 22:45 +0100, Erik Mouw wrote: > > > > The driver seems buggy. Make it return NETDEV_TX_BUSY instead of -EIO > > > in xircom_start_xmit() and the messages will go away. > > > >

[PATCH] xircom_cb should return NETDEV_TX_BUSY when there are no descriptors available

2008-02-04 Thread Erik Mouw
NETDEV_TX_BUSY instead. This was discussed on the netdev list before, see http://thread.gmane.org/gmane.linux.network/84603 . Signed-off-by: Erik Mouw <[EMAIL PROTECTED]> diff --git a/drivers/net/tulip/xircom_cb.c b/drivers/net/tulip/xircom_cb.c index 8fc7274..6b93d01 100644 --- a/drivers/net

Re: [PATCH] xircom_cb should return NETDEV_TX_BUSY when there are no descriptors available

2008-02-04 Thread Erik Mouw
On Mon, Feb 04, 2008 at 06:56:54PM +0100, Erik Mouw wrote: > Changes in other networking paths uncovered a bug in the xircom_cb > driver which made the kernel spew lots of the following error messages: > > BUG eth1 code -5 qlen 0 > > It turned out that the driver returned -