Bug 20992

Summary:

kern/tty_subr.c, b_to_q to a clist with no reserved cblocks

Product:

Base System

Reporter:

shikut <shikut>

Component:

kern

Assignee:

freebsd-bugs (Nobody) <bugs>

Status:

Closed FIXED

Severity:

Affects Only Me

Priority:

Normal

Version:

3.5.1-RELEASE

Hardware:

Any

OS:

Any

Attachments:

Description	Flags
dmesg.rpt	none
sysctl.rpt	none
BRUS.dat	none

Description shikut 2000-09-02 07:50:00 UTC

Computer description: 586-100Mhz, 32Mb RAM, 2Gb HDD, Digiboard PC/Xe (on isa), 8 Telebit XPresso modems.
This kernel message appear some times imediatly after modems disconnection, but not always. It's very strange for me, cause on FreeBSD 3.3.0 there are no such messages.

Solution of this problem is very important for me, cause am trying to setup 3.5.1 on uucp server with more then 800 users. If it possible, answer to me as quickly as it possible.

Fix: 

No fix.
How-To-Repeat: I don't know.

Comment 1 Sheldon Hearn 2000-09-04 16:01:50 UTC

Hi gents,

Could you two take a look at PR kern/20992?  The reported error message
was introduced by Peter, but it looks like it may have been tickled by
Poul-Henning's change to the dgb(4) driver.

Thanks,
Sheldon.

Comment 2 Poul-Henning Kamp 2000-09-04 16:14:23 UTC

In message <56677.968079710@axl.fw.uunet.co.za>, Sheldon Hearn writes:
>
>Hi gents,
>
>Could you two take a look at PR kern/20992?  The reported error message
>was introduced by Peter, but it looks like it may have been tickled by
>Poul-Henning's change to the dgb(4) driver.

Hmm, I think I have to pass on this one.  I just checked the changes
I've made and I don't see any which I can implicate in this.

Are you sure there are enough kernel resources for your needs ?
Consider yanking maxusers up a bit...

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

Comment 3 Sheldon Hearn freebsd_committer

2000-09-04 16:19:51 UTC

State Changed
From-To: open->feedback

What's the value associated with maxusers in your kernel config?

Comment 4 shikut 2000-09-04 17:55:35 UTC

>Synopsis: kern/tty_subr.c, b_to_q to a clist with no reserved cblocks
>
>State-Changed-From-To: open->feedback
>State-Changed-By: sheldonh
>State-Changed-When: Mon Sep 4 08:19:51 PDT 2000
>State-Changed-Why: 
>What's the value associated with maxusers in your kernel config?
>
>http://www.freebsd.org/cgi/query-pr.cgi?pr=20992
    maxuser value in kernel config is 32...

Comment 5 shikut 2000-09-04 18:10:06 UTC

>Synopsis: kern/tty_subr.c, b_to_q to a clist with no reserved cblocks
>
>State-Changed-From-To: open->feedback
>State-Changed-By: sheldonh
>State-Changed-When: Mon Sep 4 08:19:51 PDT 2000
>State-Changed-Why:
>What's the value associated with maxusers in your kernel config?
>
>http://www.freebsd.org/cgi/query-pr.cgi?pr=20992
    May be You also need dmesg and "sysctl -a" output? There are
attachments, plus my kernel config.

    Dmitry (shikut@belpak.brest.by).

Comment 6 Bruce Evans 2000-09-05 16:15:23 UTC

On Mon, 4 Sep 2000, Sheldon Hearn wrote:

> Subject: re: kern/20992: kern/tty_subr.c, b_to_q to a clist with no reserved cblocks
>  ...
>  Could you two take a look at PR kern/20992?  The reported error message
>  was introduced by Peter, but it looks like it may have been tickled by
>  Poul-Henning's change to the dgb(4) driver.

tty_subr.c and dgb didn't change between 3.3 and 3.5, and the driver
may be sio anyway.  (Who knows what is in 3.5.1?  It isn't tagged.)
sio.c has some small probably-unrelated changes.  if_sl.c has some small
possibly-related changes.  I think the only way there can be no reserved
cblocks is when slip of ppp sets the reservation to 0 and the reservation
for termios discipline somehow doesn't get restored.

Bruce

Comment 7 Sheldon Hearn freebsd_committer

2002-01-17 16:12:05 UTC

State Changed
From-To: feedback->closed

Automatic feedback timeout.  If additional feedback that warrants 
the re-opening of this PR is available but not included in the 
audit trail, please include the feedback in a reply to this message 
(preserving the Subject line) and ask that the PR be re-opened.