Re: possibly bug in 8139cp? (WAS Re: BUG: 2.4.23-pre3 + ifconfig)

From: Abraham van der Merwe (abz_at_frogfoot.net)
Date: 09/08/03

  • Next message: Dave Olien: "Badness in as_completed_request warning" 
    Date:	Mon, 8 Sep 2003 18:46:08 +0200
To: Fedor Karpelevitch <fedor@karpelevitch.net>

    Hi Fedor >@2003.09.08_18:43:25_+0200

    Not sure if you've stumbled onto the same bug as me.

    My server have 2 Netgear cards and I'm using the National Semiconductor
    dp8381x driver included with 2.4.23-pre3.

    Also, my system doesn't lock up after `ifconfig lo down', ifconfig just
    hangs and becomes unkillable and I can't reboot the machine, use ifconfig
    anymore, etc.

    > Actually for me this happens when I do "pump -i eth0"
    > The system is frozen dead (even SysRq-B does not work)
    > That's when I am using 8139cp driver (no problem in 2.4.22)
    > I tried using 8139too (I believe it is supposed to work, right?) - I
    > do not get this lockup, but instead it starts printing "too much work
    > at interrupt " messages all the time. It could be connected to the
    > latest changes in 8139 drivers...
    >
    > Fedor
    >
    > On ?????????????????????? 07 ???????????????? 2003 12:15 pm, Abraham van der Merwe wrote:
    > > Hi Fedor
    > > >@2003.09.07_21:17:02_+0200
    > >
    > > > > I just installed 2.4.23-pre3 on one of our servers. If I
    > > > > up/down the loopback device multiple times ifconfig hangs on
    > > > > the second down (as in unkillable) and afterwards ifconfig
    > > > > stops functioning and I can't reboot the machine, etc.
    > > > >
    > > > > No oopses, kernel panics, messages or anything. The system is
    > > > > still alive, it is just as if some system call is hung.
    > > > >
    > > > > If anyone is interested, I can send my .config or any other
    > > > > relevant details.
    > > >
    > > > I have the same problem. Did you find any solution?
    > >
    > > No :P Not even sure if anyone on lkml noticed my bug report.
    > 

    -- 
Regards
 Abraham
Moderation in all things.
		-- Publius Terentius Afer [Terence]
___________________________________________________
 Abraham vd Merwe - Frogfoot Networks CC
 9 Kinnaird Court, 33 Main Street, Newlands, 7700
 Phone: +27 21 686 1665 Cell: +27 82 565 4451
 Http: http://www.frogfoot.net/ Email: abz@frogfoot.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Dave Olien: "Badness in as_completed_request warning"

    Relevant Pages

    • Re: Broadcom gigabit solution for Jeff.
      ... > have this bug fixed in the tg3 driver. ... doing ifconfig down/up changes a few bytes of memory and starts things working ... Here is a before/after diff of lspci -xxx. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: PATCH: VLAN support for 3c59x/3c90x
      ... >> Why is this a module parameter at all? ... Can't you set it using ifconfig? ... > no, because the driver has no change_mtufunction, so it uses the generic ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: net: generic netdev_ioaddr
      ... > ifconfig I think: ... > But it should be something like a description text set by the driver ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: nfe driver 6.2 stable
      ... inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x ... I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig ... this driver safe to use on them? ...
      (freebsd-stable)
    • Re: Latest Broadcom NDIS driver requires 4 additional functions
      ... >> I'm trying to upgrade my ndis driver from version 3.100.64.0 to ... but when I try to load the driver I get a Fatal trap 12 ... doing a ifconfig, ... I implemented the MmGetPhysicalAddress using pmap_kextract, ...
      (freebsd-current)