4 ports SATA-II problem.

Bug #73101 reported by Ujemny
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Cristian Aravena Romero

Bug Description

When Ubuntu starts I see something like this:

[17179587.796000] ata1: SATA max UDMA/133 cmd 0xE083E580 ctl 0x0 bmdma 0x0 irq 50
[17179587.796000] ata2: SATA max UDMA/133 cmd 0xE083E580 ctl 0x0 bmdma 0x0 irq 50
[17179587.800000] ata3: SATA max UDMA/133 cmd 0xE083E600 ctl 0x0 bmdma 0x0 irq 50
[17179587.800000] ata4: SATA max UDMA/133 cmd 0xE083E680 ctl 0x0 bmdma 0x0 irq 50

[17179588.176000] ata1: SATA link up 1.5 Gbps (SStatus 113)
[17179588.180000] ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3469 86:3c01 87:4023 88:047f
[17179588.180000] ata1: dev 0 ATA-7, max UDMA/133, 156301488 sectors: LBA48
[17179588.180000] ata1: dev 0 configured for UDMA/133
[17179588.180000] scsi0 : ahci
[17179589.100000] ata2: SATA link down (SStatus 0)
[17179619.124000] ata2: qc timeout (cmd 0xec)
[17179619.124000] ata2: dev 0 failed to IDENTIFY (I/O error)
[17179619.124000] scsi1 : ahci
[17179620.044000] ata3: SATA link down (SStatus 0)
[17179650.064000] ata3: qc timeout (cmd 0xec)
[17179650.064000] ata3: dev 0 failed to IDENTIFY (I/O error)
[17179650.064000] scsi2 : ahci
[17179650.984000] ata4: SATA link down (SStatus 0)
[17179681.004000] ata4: qc timeout (cmd 0xec)
[17179681.004000] ata4: dev 0 failed to IDENTIFY (I/O error)

I have K9NU Neo-V mainboard by MSI, with 4 SATA II ports (M1697).
I only use 1 port to connect my HDD (Seagate), and 3 ports are free. After I see [17179589.100000] I have to wait 2 minut for system startup. Why Ubuntu what to detection somthing that not exist?

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Which release of Ubuntu?

description: updated
Revision history for this message
Ujemny (ujemny) wrote : Re: [Bug 73101] Re: 4 ports SATA-II problem.

Ubuntu 6.10

2006/11/24, Scott James Remnant <email address hidden>:
>
> Which release of Ubuntu?
>
> ** Changed in: upstart (Ubuntu)
> Sourcepackagename: upstart => linux-source-2.6.17
>
> ** Description changed:
>
> - Binary package hint: startup-tasks
> -
> When Ubuntu starts I see something like this:
>
> [17179587.796000] ata1: SATA max UDMA/133 cmd 0xE083E580 ctl 0x0 bmdma
> 0x0 irq 50
> [17179587.796000] ata2: SATA max UDMA/133 cmd 0xE083E580 ctl 0x0 bmdma
> 0x0 irq 50
> [17179587.800000] ata3: SATA max UDMA/133 cmd 0xE083E600 ctl 0x0 bmdma
> 0x0 irq 50
> [17179587.800000] ata4: SATA max UDMA/133 cmd 0xE083E680 ctl 0x0 bmdma
> 0x0 irq 50
>
> [17179588.176000] ata1: SATA link up 1.5 Gbps (SStatus 113)
> [17179588.180000] ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023
> 85:3469 86:3c01 87:4023 88:047f
> [17179588.180000] ata1: dev 0 ATA-7, max UDMA/133, 156301488 sectors:
> LBA48
> [17179588.180000] ata1: dev 0 configured for UDMA/133
> [17179588.180000] scsi0 : ahci
> [17179589.100000] ata2: SATA link down (SStatus 0)
> [17179619.124000] ata2: qc timeout (cmd 0xec)
> [17179619.124000] ata2: dev 0 failed to IDENTIFY (I/O error)
> [17179619.124000] scsi1 : ahci
> [17179620.044000] ata3: SATA link down (SStatus 0)
> [17179650.064000] ata3: qc timeout (cmd 0xec)
> [17179650.064000] ata3: dev 0 failed to IDENTIFY (I/O error)
> [17179650.064000] scsi2 : ahci
> [17179650.984000] ata4: SATA link down (SStatus 0)
> [17179681.004000] ata4: qc timeout (cmd 0xec)
> [17179681.004000] ata4: dev 0 failed to IDENTIFY (I/O error)
>
> I have K9NU Neo-V mainboard by MSI, with 4 SATA II ports (M1697).
> I only use 1 port to connect my HDD (Seagate), and 3 ports are free.
> After I see [17179589.100000] I have to wait 2 minut for system startup.
> Why Ubuntu what to detection somthing that not exist?
>
> --
> 4 ports SATA-II problem.
> https://launchpad.net/bugs/73101
>

--
Pozdrawiam,
Darek

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available here: <http://wiki.ubuntu.com/DebuggingKernelProblems> Thanks!

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Change Status of Unconfirmed to Needs Info.

Changed in linux-source-2.6.17:
status: Unconfirmed → Needs Info
Changed in linux-source-2.6.17:
assignee: nobody → caravena
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at [WWW] https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in linux-source-2.6.17:
status: Incomplete → Invalid
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Sorry copy/paste mistake the reason is:
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.