Bug 5887 - Erratic messages for a CDROM reader/writer
Summary: Erratic messages for a CDROM reader/writer
Status: CLOSED UNREPRODUCIBLE
Alias: None
Product: SCSI Drivers
Classification: Unclassified
Component: sym53c8xx (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Matthew Wilcox
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-13 14:37 UTC by JP Pozzi
Modified: 2006-04-20 12:13 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.14
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description JP Pozzi 2006-01-13 14:37:55 UTC
Most recent kernel where this bug did not occur:2.6.14 last and 2.6.15
Distribution:Debian
Hardware Environment:AMD MP
Software Environment:Debian
Problem Description:

I get messages every 2 seconds when my CD reader/writer has no Disk :
... Make sure there is a disk in the drive

and other messages when a CD is in the drive :

... sr 2:0:2:0: phase change 2-3 12@.....

also every 2 seconds.

In either case the unit was not mounted, I had to revert to an older kernel
version I think 2.6.14 (.4 ?) as the console is unusable with so many
messages.

The message is since the last 2.6.14 and I get the same messages
with the 2.6.15 (last from Debian I suppose it is 2.6.15-2).

Steps to reproduce: ????
Comment 1 Andrew Morton 2006-01-13 14:56:50 UTC
Does everything otherwise work OK?

If so, should we just nuke that printk, or give it a suitable facility level?
Comment 2 Matthew Wilcox 2006-04-20 06:40:02 UTC
That printk tells us that something moderately nasty is going on on the scsi
bus, so I think it has the appropriate facility level.  I'd like a lot more
detail in this bug report, such as:

 - lspci output
 - lsscsi output
 - At what point in 2.6.15 development did this start happening?
 - Has this stopped happening with the 2.6.17-rc2?

I don't know if this is a sym2 bug or whether it's something the rest of the
stack is doing to perturb this poor device.
Comment 3 JP Pozzi 2006-04-20 11:57:53 UTC
Hello,

The erratic message was only present in 2.6.14, I never see it with the last
2.6.14 and never see it since (I run now 2.6.16-8).

Regards

JP Pozzi



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