Bug 112723 - Null TTY tty_fasync appears on console and in dmesg
Null TTY tty_fasync appears on console and in dmesg
Status: CLOSED DUPLICATE of bug 78616
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i686 Linux
high Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-12-29 16:09 EST by Gene Dellinger
Modified: 2007-03-27 00:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:00:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gene Dellinger 2003-12-29 16:09:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; 

Description of problem:
The following kernel warning appears on the console, in dmesg and 
in /var/log/messages.
null TTY for (fd:00) in tty_fasync

Need to know what it is and how to fix it.

Version-Release number of selected component (if applicable):

How reproducible:
Didn't try

Steps to Reproduce:

Actual Results:  NA

Expected Results:  NA

Additional info:
Comment 1 Arjan van de Ven 2004-01-09 13:42:49 EST
seems to be the (crappy) broadcom binary only winmodem driver..

*** This bug has been marked as a duplicate of 78616 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:00:31 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.