From: Mark Orr <markorr@intersurf.com>
To: "Roeland Th. Jansen" <roel@grobbebol.xs4all.nl>
Cc: miquels@cistron.nl, arobinso@nyx.net, linux-kernel@vger.kernel.org
Subject: RE: esp causing crashes..
Date: Thu, 01 Feb 2001 15:38:28 -0600 (CST) [thread overview]
Message-ID: <XFMail.20010201153828.markorr@intersurf.com> (raw)
In-Reply-To: <20010129175752.A657@grobbebol.xs4all.nl>
On 29-Jan-2001 Roeland Th. Jansen wrote:
> [mike -- included you for refs only]
>
> recently I started to dive into a problem that causes 2.2.x and 2.4.x to
> crash at shutdown and when minicom/mgetty is used. e.g. shutdown almost
> always crashed the system; if a fax is received, 3 out of 4 faxes ok,
> but also crashes system.
>
> I tried to contact the author of the hayes esp also but he seems to be
> pretty busy...
>
> Initially I thought that killall5, mike's product, somehow caused the
> mentioned crash but diving deeper into it I found that killall5 tries to
> kill mgetty -- and crashes the system. I tried a source version as well.
> same stuff (I use suse 7.0)
I dont like to be the sort of person who, when people report problems,
fires back "it works fine here!"...but...just as a point of reference,
I have a Hayes ESP too -- it's connected to a 56k modem. I havent
had any crashes or hangs related to it, but I dont use mgetty. (I use
rungetty, a variant of mingetty, for VC's). Seeing this, I will
compile up mgetty here to see if I can replicate it.
(once in a while, communications becomes non-responsive -- but I
suspect that it's just my Zoom modem, which clams up for no apparent
reason. The port seems to be doing it's thing.)
> the IRQ is 11, not using DMA, IRQ is set to legacy in the BIOS.
> it happens with any 2.2.xx version and also happens with 2.4.0.
I'm running 2.4.0-ac12 here. ESP is set to 180h, IRQ 3, DMA 3.
(I disabled my onboard serial ports). CPU is a classic Pentium.
I've been running it w/ rx_timeout=1 (the minimum usable value,
since it seems to give lower ping times)
Got this ESP off eBay -- in fact, I got it after reading Mr. Jansen's
recommendation 2 years ago in the comp.dcom.* groups (probably ISDN),
noting how flexible and tweakable the ESP drivers are. FWIW, I was
getting mountains of TCP errors before I got this card, and they all
disappeared once I installed the ESP. It's an amazing card.
--
Mark Orr
markorr@intersurf.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-01 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 17:57 Roeland Th. Jansen
2001-02-01 21:38 ` Mark Orr [this message]
2001-02-01 23:18 ` Roeland Th. Jansen
2001-02-02 9:44 ` Mark Orr
2001-02-02 11:43 ` Roeland Th. Jansen
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=XFMail.20010201153828.markorr@intersurf.com \
--to=markorr@intersurf.com \
--cc=arobinso@nyx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=roel@grobbebol.xs4all.nl \
/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®