Bug 35723

Summary: le(4) page doesn't warn about likely system crashes.
Product: Documentation Reporter: Gary W. Swearingen <swear>
Component: Books & ArticlesAssignee: Giorgos Keramidas <keramida>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
le.diff none

Description Gary W. Swearingen 2002-03-10 04:50:01 UTC
The le(4) man page should warn in a new "Bugs" section (placed before
the "Description", preferably) that the le driver has been causing
system panics during use of "ifconfig" since at least 4.0-RELEASE and is
no longer being supported.  (It got it with 4.5 and the only reply to my
crash dump report was a reference to the suspended PR misc/18641 on the
same symptom) and a comment that it seemed to be unsupported.)
================

Fix: 

See Description.

A PR against the driver, GENERIC, LINT, etc, should probably be entered.
Is it customary to write one or two PRs in these situations?  Should
misc/18641 get a followup?  I think I just read that obsolete stuff
stays in until the next x.0-RELEASE.
How-To-Repeat: n/a
================
Comment 1 Josh Paetzel 2002-03-15 11:05:11 UTC
Here's a patch to the man page that puts in a BUGS section, I left it 
in the traditional place, though.



*** le.4.old    Fri Mar 15 10:57:26 2002
--- le.4        Fri Mar 15 10:57:42 2002
***************
*** 93,95 ****
--- 93,99 ----
  .An Matt Thomas .
  This manual page was written by
  .An David E. O'Brien .
+ .Sh BUGS
+ This driver has been causing kernel panics since 4.0-RELEASE, and 
appears to be no
+ longer actively maintained.  PR misc/18641 describes the known 
issues that have been
+ submitted.

Josh
Comment 2 darklogik 2002-03-25 15:39:43 UTC
Ceri wrote:

> On Mon, Mar 25, 2002 at 10:21:56AM -0500, Tom Rhodes wrote:
> 
>>Ceri wrote:
>>
>>
>>>On Sun, Mar 24, 2002 at 03:14:13PM +0000, Josh Paetzel wrote:
>>>
>>>
>>>>Is there any reason not to commit this?  I ran into yet another lost 
>>>>soul on irc tonight trying to get this driver to work.
>>>>
>>>>*** le.4.old    Fri Mar 15 10:57:26 2002
>>>>--- le.4        Fri Mar 15 10:57:42 2002
>>>>***************
>>>>*** 93,95 ****
>>>>--- 93,99 ----
>>>> .An Matt Thomas .
>>>> This manual page was written by
>>>> .An David E. O'Brien .
>>>>+ .Sh BUGS
>>>>+ This driver has been causing kernel panics since 4.0-RELEASE, and 
>>>>appears to be no
>>>>+ longer actively maintained.  PR misc/18641 describes the known 
>>>>issues that have been
>>>>+ submitted.
>>>>
>>>>
>>>Well I don't think we should refer to PRs in manpages for one.
>>>
>>>
>>hmmm, Ceri, why don't we cut from the PR listing down?
>>
> 
> Well I also don't think that we should say "this driver...appears to be
> no longer actively maintained".
> Which means that I don't like two thirds of the suggested patch, which
> is really quite a lot for a 27 word patch.
> 
> Far better would something like "This driver causes kernel panics".
> And I don't like that either :)
> 
> Ceri
> 
> 

This driver causes inconsistancies (sp, use i/aspell) and can
sometimes lead to kernel panics.

This driver is currently obsolete and may cause system instability,
if this occurs please try another driver or card.

Can we email the maintainer and find out if their is another driver
that can be used in its place, maybe list that?  How do you feel
about the above sentances?  I know it will be ``raising barriers'' for
users, but they should be warned about a driver known to cause
panics.  On the other hand, I do not like mentioning the other card
idea.  Catch 22?

-- 
Tom (Darklogik) Rhodes
www.Pittgoth.com Gothic Liberation Front
www.FreeBSD.org  The Power To Serve
Comment 3 Giorgos Keramidas freebsd_committer freebsd_triage 2002-08-19 23:59:38 UTC
Adding to audit trail:

> Date: Tue, 13 Aug 2002 09:00:56 -0600
> Message-ID: <005a01c242da$3a7a6a00$2784412f@ca.nortel.com>
> From: "Samuel Chow" <cyschow@shaw.ca>
> Subject: docs/35723
>
> Hi guys,
>
>     I think docs/35723 can be closed.  The le(4) driver
>     is working now.  I tested it yesterday night on -STABLE.
>
> ---
> Samuel Chow
> cyschow@shaw.ca
Comment 4 Giorgos Keramidas freebsd_committer freebsd_triage 2002-08-20 00:04:18 UTC
State Changed
From-To: open->feedback

Gary, does the problem persist?  Samuel Chow seems to have this 
working.  Can you try with onne of the more recent 4.x RELEASE 
versions and see if this is still a problem?
Comment 5 Giorgos Keramidas freebsd_committer freebsd_triage 2002-11-23 19:12:04 UTC
State Changed
From-To: feedback->closed

Feedback from Gary at Tue, 20 Aug 2002 01:59:38 +0300 
seems to indicate that there are this is an old, saved problem. 


Comment 6 Giorgos Keramidas freebsd_committer freebsd_triage 2002-11-23 19:12:04 UTC
Responsible Changed
From-To: freebsd-doc->keramida