https://bugzilla.novell.com/show_bug.cgi?id=479516
Summary: lots of error messages sr0: CDROM not ready. Make sure there is a disc in the drive. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: doiggl@velocitynet.com.au QAContact: qa@suse.de Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.19) Gecko/20081213 SUSE/1.1.14-1.1 SeaMonkey/1.1.14
Lots of error messages in dmesg the cdrom drive is empty.
sr0: CDROM not ready. Make sure there is a disc in the drive. The number is increasing - even after 10 minutes.
# dmesg | grep -i "sr0: CDROM not ready. Make sure there is a disc in the drive." | wc -l 1199 # dmesg | grep -i "sr0: CDROM not ready. Make sure there is a disc in the drive." | wc -l 1203 # dmesg | grep -i "sr0: CDROM not ready. Make sure there is a disc in the drive." | wc -l 1221 # dmesg | grep -i "sr0: CDROM not ready. Make sure there is a disc in the drive." | wc -l 1225 # dmesg | grep -i "sr0: CDROM not ready. Make sure there is a disc in the drive." | wc -l 1562
Reproducible: Always
Steps to Reproduce: 1. Turn on the laptop 2. Look at dmesg
Expected Results: Wondering what causes the error
https://bugzilla.novell.com/show_bug.cgi?id=479516
User doiggl@velocitynet.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=479516#c1
--- Comment #1 from Glenn Doig doiggl@velocitynet.com.au 2009-02-25 06:14:23 MST --- Created an attachment (id=275340) --> (https://bugzilla.novell.com/attachment.cgi?id=275340) hwinfo detail
https://bugzilla.novell.com/show_bug.cgi?id=479516
Chuanye Han cyhan@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cyhan@novell.com AssignedTo|bnc-team-screening@forge.pr |dkukawka@novell.com |ovo.novell.com |
https://bugzilla.novell.com/show_bug.cgi?id=479516
User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=479516#c2
Danny Kukawka dkukawka@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |doiggl@velocitynet.com.au
--- Comment #2 from Danny Kukawka dkukawka@novell.com 2009-02-27 01:22:11 MST --- Please provide a part of /var/log/messages to see the full messages.
https://bugzilla.novell.com/show_bug.cgi?id=479516
User rbausdorf@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=479516#c3
Robert Bausdorf rbausdorf@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbausdorf@googlemail.com
--- Comment #3 from Robert Bausdorf rbausdorf@googlemail.com 2009-03-01 04:15:49 MST --- I've got the same effect after the last online-update of suse 11.1.
After disconnecting both of my DVD-Drives the problem was (of course) gone. After restart there was a error message from kscd - maybe this program causes the error.
https://bugzilla.novell.com/show_bug.cgi?id=479516
User doiggl@velocitynet.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=479516#c4
Glenn Doig doiggl@velocitynet.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|doiggl@velocitynet.com.au |
--- Comment #4 from Glenn Doig doiggl@velocitynet.com.au 2009-03-01 20:59:02 MST --- I don`t see the error now. It may have scrolled off the top. Ive restarted my pc. # dmesg | grep -i "sr0: CDROM not ready" | wc -l 0
https://bugzilla.novell.com/show_bug.cgi?id=479516
User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=479516#c5
Danny Kukawka dkukawka@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID
--- Comment #5 from Danny Kukawka dkukawka@novell.com 2009-03-02 01:01:03 MST --- Okay, then I close the bug now. Feel free to reopen if this happens again and if you can provide /var/log/messages in this case.