ata: abnormal status 0x7F on port 0x0001f607

Bug #119640 reported by wyg1258
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Medium
Unassigned

Bug Description

when i install ubuntu(i have tried 6.06~7.10alpha1),it shows me this message:

[]ata: abnormal status 0x7F on port 0x0001f607

then,just a "busybox"

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Do you mean that this happens after you install Ubuntu or that his happens when booting from the Live CD? Thanks in advance.

Revision history for this message
wyg1258 (wyg1258) wrote : 回复:[Bug 119640] Re: ata: abnormal status 0x7F on port 0x0001f607

when booting from the Live CD ,it shows me that.
 finally i found that ubuntu can't recognize my sata harddisk(WDC WD800jd-00LSA0) .

 the harddisk is on the Channel 3 Secondary (my cd-rom is on the Channel 1 Primary ),i tried fedora 7 too,but it's the same.

 but opensuse can find my harddisk and boot without any problem.

 ------------------ 原始邮件 ------------------
  发件人: "Brian Murray"<email address hidden>;
 发送时间: 2007年7月25日(星期三) 上午07:53
 收件人: "wyg1258"<email address hidden>;

 主题: [Bug 119640] Re: ata: abnormal status 0x7F on port 0x0001f607

 Thank you for taking the time to report this bug and helping to make
Ubuntu better. Do you mean that this happens after you install Ubuntu
or that his happens when booting from the Live CD? Thanks in advance.

** Changed in: Ubuntu
   Importance: Undecided => Medium
     Assignee: (unassigned) => Brian Murray
       Status: New => Incomplete

--
ata: abnormal status 0x7F on port 0x0001f607
https://bugs.launchpad.net/bugs/119640
You received this bug notification because you are a direct subscriber
of the bug.

Revision history for this message
Brian Murray (brian-murray) wrote :

The output of 'lspci -vv' and 'lspci -vvn' from your opensuse system would be helpful for your bug report then. Please add them as attachments. Thanks again!

Revision history for this message
wyg1258 (wyg1258) wrote :

  my ata information is below (On-chip ATA setting : Auto-mode):

IDE 0 Channel Primary ASUS-CDROM
IDE 0 Channel Primary none
## i don't know why there doesn't has "IDE 1" ,but windows and opensuse could normally boot

IDE 2 Channel Primary WDC WD800JD-00LS
IDE 2 Channel Primary none
IDE 3 Channel Primary none
IDE 3 Channel Primary none

Revision history for this message
EsbenMoseHansen (kde-mosehansen) wrote :

I get this too. It seems to happen for any kernels after 2.6.19 or so. This is a P5K-E motherboard, with a plexer DVD drive. Please tell me if I can do anything to help resolve this; also any ideas of workarounds would be much appreciated.

Revision history for this message
Brian Murray (brian-murray) wrote :

EsbenMoseHansen - Could you please test this with the latest development release of Ubuntu, the Gutsy Gibbon, and report back? You can learn more about the development release at http://www.ubuntu.com/testing/ .

Revision history for this message
EsbenMoseHansen (kde-mosehansen) wrote :

Well, all my testing has been with gutsy gibbon, downloaded a few days ago. The problem seems to be that the ata_piix module grabs the ide channel without being able to drive them. This page http://www.thinkwiki.org/wiki/Problems_with_SATA_and_Linux suggest several workaround, of which I tested (on the busybox line, so no install was possible) unloading ata_piix, load ide_generic and then load ata_piix. That seemed to work, but I don't know how to resume the installation after doing that bit of magic.

Revision history for this message
Brian Murray (brian-murray) wrote :

Esben - Could you try booting the Gutsy Gibbon Live CD by appending the kernel option 'all_generic_ide' to the kernel boot line? You can learn more about modifying boot options at https://help.ubuntu.com/community/GrubHowto . Thanks again!

Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

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

Other bug subscribers

Bug attachments

Remote bug watches

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