Bug 43112

Summary: module SYM53C8XX does excessive logging (Linux 2.4.2-2smp i686)
Product: [Retired] Red Hat Linux Reporter: Martijn Kruithof <jkf>
Component: autorunAssignee: Arjan van de Ven <arjanv>
Status: CLOSED WONTFIX QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-01-29 10:06:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martijn Kruithof 2001-05-31 21:15:41 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2smp i686; en-US; rv:0.9)
Gecko/20010511

Description of problem:
On my rh 7.1 system with SCSI CD-ROM / SCSI CD-ROM Burner and scanner
(turned off) when someone is logged in who has the autorun for automounting
CD-ROMs in the .kde Autostart file (default for kde) one gets 11 times per
device the following message in /var/log/messages 

May 29 17:28:09 user kernel: sym53c875-0-<4,0>: sync msgout: 1-3-1-c-10.
May 29 17:28:09 user kernel: sym53c875-0-<4,0>: sync msg in: 1-3-1-19-8.
May 29 17:28:09 user kernel: sym53c875-0-<4,0>: sync: per=25 scntl3=0x30
scntl4=0x0 ofs=8 fak=0 chg=0.


How reproducible:
Always

Steps to Reproduce:
1.boot system with SCSI cd-rom drive (and no scsi harddisk)
2.module is loaded automagically
3.log in in KDE and autorun is automatically started
4.The log file grows FAST
Comment 1 Arjan van de Ven 2001-05-31 21:30:36 UTC 
autorun is broken in this respect.
Comment 2 Harald Hoyer 2001-06-01 06:46:29 UTC 
What is wrong about:
open("/dev/cdrom", O_RDONLY|O_NONBLOCK) = 3
ioctl(3, CDROM_CLEAR_OPTIONS, 0x1)      = 12
ioctl(3, CDROM_LOCKDOOR, 0)                     = 671088640
ioctl(3, CDROM_DRIVE_STATUS, 0x7fffffff) = 2
close(3)                                = 0
nanosleep({1, 0}, NULL)                 = 0

??? It is a normal user program only checking for the drive status. 
What is so important for the cdrom driver to log it???