Bug 680177

Summary: fedora 14 / 2-nd cdrw drive /dev/sr1 not created
Product: [Fedora] Fedora Reporter: Emmanuel Bigler <bigler>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: bigler, gansalmon, harald, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-29 18:05:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
output of dmesg command
none
dmesg output same hardware but from debian-live 6.0.0 kernel 2.6.32 none

Description Emmanuel Bigler 2011-02-24 15:08:29 UTC
Created attachment 480777 [details]
output of dmesg command

Description of problem:

after upgrading to fedora 14, a 2-nd cd-rom RW drive is not recognised.

/dev/sr0 is created as well as various IDE and USB hard drives, but not my 2-nd CD-ROM RW drive.

Version-Release number of selected component (if applicable):
Linux version 2.6.35.11-83.fc14.i686 (mockbuild.fedoraproject.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #1 SMP Mon Feb 7 07:04:18 UTC 2011

I suspect  a udev problem ?
I have quickly tested with a recent live debian 6.0.0 kernel 2.6.32, and /dev/sr1 is created and accessible, so it is should not be not a hardware failure ??

How reproducible:
The disk simply does not show up in fedora 14 whereas is does as usual under a recent debian .


  
Actual results:
only /dev/sr0 and alias /dev/cdrom is created
/proc/scsi/scsi does correctly list all my hard drives IDE + USB plus cdrom sr0 but not the 2-nd cdrom /dev/sr1
both are ATAPI cdroms, about 10 years old.


Expected results:
/dev/sr0 and /dev/sr1 should be created plus aliases like :dev/cdrw and /dev/cdrom1.


full dmesg attached.
Additional info:

Comment 1 Harald Hoyer 2011-02-25 08:30:06 UTC
can you show me the output of:
$ cat /proc/scsi/scsi
$ cat /proc/sys/dev/cdrom/info

Comment 2 Emmanuel Bigler 2011-02-25 10:20:51 UTC
cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST340015A        Rev: 3.01
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: ATA      Model: Maxtor 6K040L0   Rev: NAR6
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: ATAPI-CD Model: ROM-DRIVE-56MAX  Rev: 56E4
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: HDS72251 Model: 6VLAT20          Rev: V34O
  Type:   Direct-Access                    ANSI  SCSI revision: 00
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: SAMSUNG  Model: HD103SI          Rev: 0041
  Type:   Direct-Access                    ANSI  SCSI revision: 00



cat /proc/sys/dev/cdrom/info
CD-ROM information, Id: cdrom.c 3.20 2003/12/17

drive name:             sr0
drive speed:            56
drive # of slots:       1
Can close tray:         1
Can open tray:          1
Can lock tray:          1
Can change speed:       1
Can select disk:        0
Can read multisession:  1
Can read MCN:           1
Reports media changed:  1
Can play audio:         1
Can write CD-R:         0
Can write CD-RW:        0
Can read DVD:           0
Can write DVD-R:        0
Can write DVD-RAM:      0
Can read MRW:           1
Can write MRW:          1
Can write RAM:          1

-------------

Comments :
on scsi0 I have 2 internal IDE hard drives, formerly seen as hda and hdb ; now seen as sda and sdb : OK no problem

on scsi1 I should see 2 cd-roms, previously seen as hdc and hdd, now should be sr0 and sr1 ; no sign of life of hdd/sr1.

on scsi2 and scsi3 I have two external usb hard drives OK.

I should mention that I have a "real" SCSI card and "real" SCSI peripherals (a hard disk and a tape drive) but they are switched off most of the time. I have recently used the SCSI external drive (not seen here, switched off)  without problem under fedora 14.

To try and see what could be the reason, I have tested the same hardware configuration with a temporary reboot on a live debian 6.0.0 kernel 2.32 and both cd-roms are seen OK ; I could read and write data correctly to the CD RW sr1, so this does not look as a hardware failure.
I have been using this hardware under various redhat + fedora configurations for a long time. My last fedora before upgrade to fc14 was quite old, it was a FC3 for which I was still operating with IDE drivers HDA / HDB (internal hard disks) and HDC and HDD (2 internal cd-roms) without trouble.
I did not change anything to the hardware configuration, never re-opened the box since my last fedora upgrade.

Comment 3 Harald Hoyer 2011-02-25 10:45:42 UTC
> cat /proc/sys/dev/cdrom/info
> CD-ROM information, Id: cdrom.c 3.20 2003/12/17
> 
> drive name:             sr0
> drive speed:            56
> drive # of slots:       1
> Can close tray:         1
> Can open tray:          1
> Can lock tray:          1
> Can change speed:       1
> Can select disk:        0
> Can read multisession:  1
> Can read MCN:           1
> Reports media changed:  1
> Can play audio:         1
> Can write CD-R:         0
> Can write CD-RW:        0
> Can read DVD:           0
> Can write DVD-R:        0
> Can write DVD-RAM:      0
> Can read MRW:           1
> Can write MRW:          1
> Can write RAM:          1
> 

This indicates, that it is a kernel problem and not a udev problem.

Comment 4 Emmanuel Bigler 2011-02-25 14:59:10 UTC
Created attachment 481012 [details]
dmesg output same hardware but from debian-live 6.0.0 kernel 2.6.32

I have added as an attached file the dmesg output, exactly same hardware, from a debian-live 6.0.0
kernel  2.6.32, where both cd-roms are recognised

Comment 5 Emmanuel Bigler 2011-02-25 15:13:10 UTC
Thanks for your prompt reply.
I have to apologize since I'll not be able to follow this thread next week (I'll be off-town and off-line for about one week) so do not mind if I do not answer until March 7.

As a sumry this is what dmesg says whan both cd-roms are seen
...
ata2.00: ATAPI: ATAPI-CD ROM-DRIVE-56MAX, Ver 56E4, max UDMA/33
ata2.01: ATAPI: PLEXTOR CD-R   PX-W5224A, 1.01, max UDMA/33
....
scsi 1:0:0:0: CD-ROM            ATAPI-CD ROM-DRIVE-56MAX  56E4 PQ: 0 ANSI: 5
scsi 1:0:1:0: CD-ROM            PLEXTOR  CD-R   PX-W5224A 1.01 PQ: 0 ANSI: 5
...
sr 1:0:0:0: Attached scsi CD-ROM sr0
sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
sr 1:0:1:0: Attached scsi CD-ROM sr1

Comment 6 Chuck Ebbert 2011-02-25 19:58:46 UTC
(In reply to comment #5)
> ata2.00: ATAPI: ATAPI-CD ROM-DRIVE-56MAX, Ver 56E4, max UDMA/33
> ata2.01: ATAPI: PLEXTOR CD-R   PX-W5224A, 1.01, max UDMA/33

And here we see:
[    1.748286] ata2.01: link status unknown, clearing UNKNOWN to NONE
[    1.751625] ata2.00: ATAPI: ATAPI-CD ROM-DRIVE-56MAX, Ver 56E4, max UDMA/33

These drives are on PATA cables, are you sure the cabling is right?

Comment 7 Emmanuel Bigler 2011-03-09 10:10:46 UTC
Hello !
I'm back to this debugging discussion, thanks for your help so far.

from Chuck Ebbert :
>> These drives are on PATA cables, are you sure the cabling is right?

Well, the drives were installed by the vendor, I never touched them, and for about 10 years I have had no problem with various Redhat & Fedora releases. 
And the current debian kernel 2.6.32 does recognize them.

So what should I do ? I am interesting in opening the box and checking for hardware problems, but what could be wrong with the cabling ? How do I check this ? Apart form disconnecting and re-connecting, what can I do ?
Present hardware is considered as good by two recent debians (5.0.7 and 6.0.0) debian and fails with fedora 14 ??
I am  a bit puzzled and of course interested in any advice to check the cabling and solve the bug.

Comment 8 Emmanuel Bigler 2011-03-10 10:55:03 UTC
Additional tests.
I have tested the LIVE FEDORA 14 CD and it works fine, recognizes both CD drives.
This is really WEIRD ! Since the kernel on the live fedora 14 CD looks identical to one of those I have on my hard drive, but do not recognize the drive  !!!

Same identification for both kernels :
2.6.35.6-45.fc14.i686 (mockbuild.fedoraproject.org) #1 SMP Mon Oct 18 23:56:17 UTC 2010


Summary :
- all three FC-14 kernels installed on my hard, from which I can choose at the  GRUB/BOOT level, fail to recognize the 2-nd CD-ROM drive and do not create  /dev/sr1 ; error message is : 
ata2.01: link status unknown, clearing UNKNOWN to NONE

buggy kernels: 
vmlinuz-2.6.35.10-74.fc14.i686 = BUG
vmlinuz-2.6.35.11-83.fc14.i686 = BUG
vmlinuz-2.6.35.6-45.fc14.i686  = BUG when booted from my disk ??
Both files vmlinuz0 on the live CD, and vmlinuz-2.6.35.6-45.fc14.i686 are byte-to-byte identical !

extracted from the dmesg, Fedora 14 installed on my hard disk, same kernel
as live CD 2.6.35.6-45 

[    0.000000] Linux version 2.6.35.6-45.fc14.i686 (mockbuild.fedoraproject.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #1 SMP Mon Oct 18 23:56:17 UTC 2010
..........skip...........
[    1.578252] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x2800 irq 14
[    1.578258] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x2808 irq 15
..........skip...........
[    1.733227] ata2.01: link status unknown, clearing UNKNOWN to NONE
[    1.736619] ata2.00: ATAPI: ATAPI-CD ROM-DRIVE-56MAX, Ver 56E4, max UDMA/33
[    1.739512] ata1.00: ATA-6: ST340015A, 3.01, max UDMA/100




------------------------------------

- two other kernels work fine :
1/ Fedora-14 on live CD kernel 2.6.35.6-45 = OK no bug when booting from the live CD !!! 

extracted from the dmesg, live Fedora 14 CD :

[    0.000000] Linux version 2.6.35.6-45.fc14.i686 (mockbuild.fedoraproject.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #1 SMP Mon Oct 18 23:56:17 UTC 2010
..........skip...........
[    1.371482] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x2800 irq 14
[    1.371489] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x2808 irq 15
..........skip...........
[    1.533616] ata2.00: ATAPI: ATAPI-CD ROM-DRIVE-56MAX, Ver 56E4, max UDMA/33
[    1.533669] ata2.01: ATAPI: PLEXTOR CD-R   PX-W5224A, 1.01, max UDMA/33
[    1.533974] ata1.00: ATA-6: ST340015A, 3.01, max UDMA/100
..........skip...........
[    1.550149] scsi 1:0:0:0: CD-ROM            ATAPI-CD ROM-DRIVE-56MAX  56E4 PQ: 0 ANSI: 5
[    1.554631] sr0: scsi3-mmc drive: 56x/56x cd/rw xa/form2 cdda tray
[    1.554637] Uniform CD-ROM driver Revision: 3.20
[    1.554833] sr 1:0:0:0: Attached scsi CD-ROM sr0
[    1.554944] sr 1:0:0:0: Attached scsi generic sg2 type 5
[    1.555671]  sda1 sda2 sda3 sda4 <
[    1.555930] scsi 1:0:1:0: CD-ROM            PLEXTOR  CD-R   PX-W5224A 1.01 PQ: 0 ANSI: 5
[    1.558273] sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
[    1.558461] sr 1:0:1:0: Attached scsi CD-ROM sr1
[    1.558573] sr 1:0:1:0: Attached scsi generic sg3 type 5



Other kernel/configuration that works :

2/ debian 6.0.0 on live CD kernel 2.6.32 = OK

I have stored all dmesg messages for all 5 configurations, available if required.

Comment 9 Emmanuel Bigler 2011-03-10 11:27:46 UTC
WORK-AROUND FOUND !

Comment 10 Emmanuel Bigler 2011-03-10 11:33:07 UTC
I simply loaded a non-bootable CD in the CD-ROM #1, and CD-ROM#2 was recognized.
So it is not a question of kernel version, but question of BIOS / HARDWARE interacting with recent kernels ?

Now all 5 configuations work, all 3 Fedora-14 kernels installed on my hard disk boot & recognize /dev/sr1 when a non-bootable data disk is inserted in /dev/sr0.

This behaviour explained why booting on a live-CD solved the bug... since there was a non-empty /dev/sr0 at boot time...

May be this is another well-documented bug ??

However now I have a simple solution to use my CD-ROM #2.
Thanks all for your help.