mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Abraham van der Merwe <abz@frogfoot.net>
To: Fedor Karpelevitch <fedor@karpelevitch.net>
Cc: Linux Kernel Discussions <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: possibly bug in 8139cp? (WAS Re: BUG: 2.4.23-pre3 + ifconfig)
Date: Mon, 8 Sep 2003 18:46:08 +0200	[thread overview]
Message-ID: <20030908164608.GA1936@oasis.frogfoot.net> (raw)
In-Reply-To: <200309080943.26254.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


  parent reply	other threads:[~2003-09-08 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-04 18:05 BUG: 2.4.23-pre3 + ifconfig Abraham van der Merwe
     [not found] ` <200309071217.03470.fedor@karpelevitch.net>
2003-09-07 19:15   ` Abraham van der Merwe
     [not found]     ` <200309080943.26254.fedor@karpelevitch.net>
2003-09-08 16:46       ` Abraham van der Merwe [this message]
2003-09-08 17:26       ` possibly bug in 8139cp? (WAS Re: BUG: 2.4.23-pre3 + ifconfig) Jeff Garzik
2003-09-08 20:32         ` Andrew Morton
2003-09-08 23:59           ` Jeff Garzik
2003-09-09  0:09             ` Andrew Morton
2003-09-09  0:41               ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030908164608.GA1936@oasis.frogfoot.net \
    --to=abz@frogfoot.net \
    --cc=fedor@karpelevitch.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®