Bug 693121

Summary: failed to set xfermode hang prior to plymouth
Product: [Fedora] Fedora Reporter: Peter Gückel <pgueckel>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-11 03:31:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Peter Gückel 2011-04-02 19:48:33 UTC 
Description of problem:
When booting the system, after grub, a black screen appears and ata5:00 failed to set xfermode (err_mask=0x100) appears on the screen. Bootup pauses and another line or two of other ata messages appear, then plymouth finally launches and all seem ok, except that kde lauched extremely slowly, taking nearly 2 minutes from the time kdm ran until the desktop appears (kde issue might not be related).

Version-Release number of selected component (if applicable):
kernel-2.6.38-1.fc15.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
This problem appeared when I switched from f14 to f15 alpha test candidate 1. I do not recall ever seeing it in any other release of fedora, but it has affected my system since the earliest tests of f15. I should add that ata5 is the DVD/CD reader/writer. None of the other drives report this problem.
Comment 1 Peter Gückel 2011-04-02 22:55:17 UTC 
My laptop (i686) does not have this problem. It has a CD reader-writer/DVD reader.

The laptop is about 4 years old, while the desktop (x86_64) has a 1-year old motherboard.
Comment 2 Peter Gückel 2011-04-02 23:07:29 UTC 
I just booted into f14 and the problem does not exist there. I have not updated f14 for some time, as I use f15 now (different partition, same computer), so the kernel is: 2.6.35.10-74.fc14.x86_64.
Comment 3 Peter Gückel 2011-04-03 00:38:47 UTC 
I'm back in f15 now. As the system booted (I should add that the kernel is now 2.6.38.2-8.fc15.x86_64), the xfermode message did not appear.

Instead, I got:

ata5: COMRESET failed (errno=-16)

In case it is relevant, here is the full output of dmesg|grep ata (minus the obviously irrelevant stuff):

[    0.155358] libata version 3.00 loaded.
[    2.888600] ata1: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625100 irq 47
[    2.888604] ata2: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625180 irq 47
[    2.888608] ata3: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625200 irq 47
[    2.888611] ata4: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625280 irq 47
[    2.888615] ata5: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625300 irq 47
[    2.888618] ata6: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625380 irq 47
[    2.888689] ata_piix 0000:00:1f.5: version 2.13
[    2.888700] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    2.888706] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[    2.888747] ata_piix 0000:00:1f.5: setting latency timer to 64
[    2.889128] scsi6 : ata_piix
[    2.889226] scsi7 : ata_piix
[    2.889292] ata7: SATA max UDMA/133 cmd 0xf170 ctl 0xf160 bmdma 0xf130 irq 19
[    2.889297] ata8: SATA max UDMA/133 cmd 0xf150 ctl 0xf140 bmdma 0xf138 irq 19
[    3.193035] ata2: SATA link down (SStatus 0 SControl 300)
[    3.193058] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.194040] ata6: SATA link down (SStatus 0 SControl 300)
[    3.194079] ata4: SATA link down (SStatus 0 SControl 300)
[    3.294378] ata1.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
[    3.294382] ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    3.294405] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.305352] ata8: SATA link down (SStatus 0 SControl 300)
[    3.337722] ata1.00: configured for UDMA/133
[    3.349691] ata3.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
[    3.349695] ata3.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    3.407997] ata3.00: configured for UDMA/133
[    8.343019] ata5: link is slow to respond, please be patient (ready=0)
[    8.394027] ata7: link is slow to respond, please be patient (ready=-19)
[   12.933023] ata5: COMRESET failed (errno=-16)
[   12.944061] ata7: SATA link down (SStatus 0 SControl 301)
[   13.247029] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   13.249618] ata5.00: ATAPI: TSSTcorpCD/DVDW SH-S183L, SB00, max UDMA/33
[   13.249622] ata5.00: applying bridge limits
[   13.252670] ata5.00: configured for UDMA/33
[   14.033200] ata_generic 0000:00:03.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[   14.033236] ata_generic 0000:00:03.2: setting latency timer to 64
[   14.036308] scsi8 : ata_generic
[   14.037221] scsi9 : ata_generic
[   14.037298] ata9: PATA max UDMA/100 cmd 0xf210 ctl 0xf200 bmdma 0xf1d0 irq 18
[   14.037302] ata10: PATA max UDMA/100 cmd 0xf1f0 ctl 0xf1e0 bmdma 0xf1d8 irq 18
Comment 4 Peter Gückel 2011-04-03 04:13:16 UTC 
Before, after leaving f14 and returning to f14, I had rebooted. Just out of curiosity, I turned the computer off completely and back on again. I got the original xfermode error again, with kernel-2.6.38.2-8.fc15.x86_64.
Comment 5 Peter Gückel 2011-04-03 04:14:04 UTC 
(In reply to comment #4)
> after leaving f14 and returning to f14...

That was supposed to read:

after leaving f14 and returning to f15
Comment 6 Peter Gückel 2011-04-03 18:07:09 UTC 
I upgraded to kernel-2.6.38.2-9.fc15.x86_64.

The output is now completely different, but still not good:

[    0.154451] libata version 3.00 loaded.
[    2.889589] ata1: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625100 irq 47
[    2.889593] ata2: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625180 irq 47
[    2.889596] ata3: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625200 irq 47
[    2.889600] ata4: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625280 irq 47
[    2.889603] ata5: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625300 irq 47
[    2.889607] ata6: SATA max UDMA/133 abar m2048@0xe0625000 port 0xe0625380 irq 47
[    2.889681] ata_piix 0000:00:1f.5: version 2.13
[    2.889691] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    2.889697] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[    2.889740] ata_piix 0000:00:1f.5: setting latency timer to 64
[    2.890122] scsi6 : ata_piix
[    2.890211] scsi7 : ata_piix
[    2.890281] ata7: SATA max UDMA/133 cmd 0xf170 ctl 0xf160 bmdma 0xf130 irq 19
[    2.890285] ata8: SATA max UDMA/133 cmd 0xf150 ctl 0xf140 bmdma 0xf138 irq 19
[    3.194034] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.194060] ata2: SATA link down (SStatus 0 SControl 300)
[    3.195049] ata4: SATA link down (SStatus 0 SControl 300)
[    3.195075] ata6: SATA link down (SStatus 0 SControl 300)
[    3.195099] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.295347] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x40)
[    3.306389] ata8: SATA link down (SStatus 0 SControl 300)
[    8.295041] ata1.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
[    8.295045] ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    8.295077] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    8.323212] ata1.00: configured for UDMA/133
[    8.339056] ata3.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
[    8.339060] ata3.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    8.397358] ata3.00: configured for UDMA/133
[    8.495024] ata7: link is slow to respond, please be patient (ready=-19)
[    8.600029] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    8.602891] ata5.00: ATAPI: TSSTcorpCD/DVDW SH-S183L, SB00, max UDMA/33
[    8.602896] ata5.00: applying bridge limits
[    8.605966] ata5.00: configured for UDMA/33
[   12.932023] ata7: SRST failed (errno=-16)
[   12.932091] ata5: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
[   12.932130] ata5: irq_stat 0x00400000, PHY RDY changed
[   12.932166] ata5: SError: { PHYRdyChg }
[   12.932201] ata5: hard resetting link
[   13.649031] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   13.654687] ata5.00: configured for UDMA/33
[   13.655828] ata5: EH complete
[   13.692056] ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   14.441172] ata_generic 0000:00:03.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[   14.441208] ata_generic 0000:00:03.2: setting latency timer to 64
[   14.451934] scsi8 : ata_generic
[   14.455032] scsi9 : ata_generic
[   14.455118] ata9: PATA max UDMA/100 cmd 0xf210 ctl 0xf200 bmdma 0xf1d0 irq 18
[   14.455122] ata10: PATA max UDMA/100 cmd 0xf1f0 ctl 0xf1e0 bmdma 0xf1d8 irq 18
Comment 7 Peter Gückel 2011-04-10 17:59:42 UTC 
A little more information:

All appeared to work normally in f13. In f14, there were no error messages, but often the system did not even detect the presence of the cd/dvd drive. In f15, the drive is again detected and I think it is usable, but these error messages appear. I still have f13 and f14 on other partitions, so I could check, if need be. f13 will be overwritten with f16 alpha tc1, so this is a limited time offer.
Comment 8 Chuck Ebbert 2011-04-14 01:35:58 UTC 
(In reply to comment #8)
> Description of problem:
> When booting the system, after grub, a black screen appears and ata5:00 failed
> to set xfermode (err_mask=0x100) appears on the screen. Bootup pauses and
> another line or two of other ata messages appear, then plymouth finally
> launches and all seem ok, except that kde lauched extremely slowly, taking
> nearly 2 minutes from the time kdm ran until the desktop appears (kde issue
> might not be related).

Can you disconnect the problem drive and see if the boot goes faster?

Looks like this is one of those infamous PATA drives with a SATA bridge built-in...
Comment 9 Peter Gückel 2011-04-14 05:55:44 UTC 
(In reply to comment #8)
> (In reply to comment #8)
> > Description of problem:
> > When booting the system, after grub, a black screen appears and ata5:00 failed
> > to set xfermode (err_mask=0x100) appears on the screen. Bootup pauses and
> > another line or two of other ata messages appear, then plymouth finally
> > launches and all seem ok, except that kde lauched extremely slowly, taking
> > nearly 2 minutes from the time kdm ran until the desktop appears (kde issue
> > might not be related).
> 
> Can you disconnect the problem drive and see if the boot goes faster?
> 
> Looks like this is one of those infamous PATA drives with a SATA bridge
> built-in...

The KDE problem appears to have resolved itself, probably due to the release of kde-4.6.2 a couple of days ago, so the login is snappy now.

Yes, there still is a bit of a delay between grub and plymouth, where these error messages appear.

This is definitely a sata dvd-drive. I built the computer myself, so I know that it has a sata jack. Or are you referring to some kind of internal conversion, so that it appears to be a sata drive, while inside...?

Aw... look. I don't feel like opening up the case and disconnecting the drive right now. Really. It is a pain. I have to turn off the computer, crawl under the table, open up the case, unplug the drive, boot up, see if it runs faster, power down again, plug it back in again, and boot up again. I know for a fact that if I disconnect the drive, the error messages will go away, so I don't see what this is going to prove. If you absolutely must have some information, tell me what you need and I'll see what I can do the next time it snows or something and I don't have anything to do for a half hour.