From nobody  Sat Feb  8 08:16:58 1997
Received: (from nobody@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA18384;
          Sat, 8 Feb 1997 08:16:58 -0800 (PST)
Message-Id: <199702081616.IAA18384@freefall.freebsd.org>
Date: Sat, 8 Feb 1997 08:16:58 -0800 (PST)
From: garman@phs.k12.ar.us
To: freebsd-gnats-submit@freebsd.org
Subject: sio1 (16540 serial port) is not recognized by GENERIC boot kernel
X-Send-Pr-Version: www-1.0

>Number:         2695
>Category:       kern
>Synopsis:       sio1 (16540 serial port) is not recognized by GENERIC boot kernel
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Feb  8 08:20:01 PST 1997
>Closed-Date:    Fri Aug 18 03:10:36 PDT 2000
>Last-Modified:  Fri Aug 18 03:12:50 PDT 2000
>Originator:     Jason Garman
>Release:        2.2-GAMMA as of yesterday
>Organization:
individual
>Environment:
(could not install, so this can't be determined)
>Description:
The internal modem on my machine (on sio1) is recognized fine by
2.1.x kernels, but when booting 2.2 (any version i've tried) the boot
messages report that it can't be found.

I turned on verbose probe using flags 0x80 and it tells me:

sio1: probe test 5 failed
sio1: probe test 6 failed
sio1 not found at 0x2f8

My working 2.1.6.1-RELEASE kernel reports:

sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16450
>How-To-Repeat:
boot a 2.2-gamma kernel with my modem installed on com2 :-)
>Fix:
not enough delay to allow the modem to respond to probes, perhaps?
>Release-Note:
>Audit-Trail:

From: Bruce Evans <bde@zeta.org.au>
To: freebsd-gnats-submit@freebsd.org, garman@phs.k12.ar.us
Cc:  Subject: Re: kern/2695: sio1 (16540 serial port) is not recognized by GENERIC boot kernel
Date: Sun, 9 Feb 1997 09:06:46 +1100

 >I turned on verbose probe using flags 0x80 and it tells me:
 >
 >sio1: probe test 5 failed
 >sio1: probe test 6 failed
 >sio1 not found at 0x2f8
 >
 >My working 2.1.6.1-RELEASE kernel reports:
 >
 >sio1 at 0x2f8-0x2ff irq 3 on isa
 >sio1: type 16450
 >>How-To-Repeat:
 >boot a 2.2-gamma kernel with my modem installed on com2 :-)
 >>Fix:
 >not enough delay to allow the modem to respond to probes, perhaps?
 
 2.2 delays 1000 usec longer than 2.1.6 between test4 and test 5.
 
 I have seen failures for test 3 and test 4 on a UMC8669F (16550
 incompatible).  I guess this is caused by fifo mode and possibly some
 other things not being cleared after a crash, and bugs in UMC's control
 registers.  I recently found that the UMC's fifo control register
 doesn't work either - if it is written to while input is arriving,
 then the fifo trigger level is not changed until input stops arriving.
 There are also problems with writing to the divisor latch registers
 while input is arriving.  So initialization of the divisor latch and
 the fifo in the probe can't be trusted to work (the fifo isn't
 initialized now).
 
 Bruce

From: Johan Karlsson <k@numeri.campus.luth.se>
To: freebsd-gnats-submit@freebsd.org, garman@phs.k12.ar.us
Cc:  
Subject: Re: kern/2695: sio1 (16540 serial port) is not recognized by GENERIC 
 boot kernel
Date: Sun, 06 Aug 2000 10:58:47 +0200

 Hi Jason
 
 Can you tell us if this problem still exists in more recent 
 Releases of FreeBSD, eg FreeBSD 4.1.
 
 Thanks
 Johan K
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Mon Aug 7 04:56:14 PDT 2000 
State-Changed-Why:  
waiting for feedback on a more recent release. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=2695 
State-Changed-From-To: feedback->closed 
State-Changed-By: johan 
State-Changed-When: Fri Aug 18 03:10:36 PDT 2000 
State-Changed-Why:  
I received this from Jason: 
Date: Thu, 17 Aug 2000 18:11:49 -0400 (Fri 00:11 CEST) 
From: Jason Garman <jgarman@wedgie.org> 
To: Johan Karlsson <k@numeri.campus.luth.se> 
Subject: Re: kern/2695: sio1 (16540 serial port) is not recognized by GENERIC boot kernel 

On Sun, Aug 06, 2000 at 10:58:47AM +0200, Johan Karlsson wrote: 
> Hi Jason 
>  
> Can you tell us if this problem still exists in more recent  
> Releases of FreeBSD, eg FreeBSD 4.1. 
>  
i would suggest closing that pr :) its been way too long, i don't even 
have that hardware anymore. 

thanks 
--  
Jason Garman                                         http://web.wedgie.org/ 
Student, University of Maryland                          jgarman@wedgie.org 


And this was in the 2.2-gamma days and alot has happened since then. 
If someone else experience this problem please submit a new PR for 
a newer release. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=2695 
>Unformatted:
