2.6.20-10 regression from 2.6.20-9, Macbook Pro no longer boots

Bug #91940 reported by James Troup on 2007-03-13
50
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

2.6.20-10 will not boot on a Macbook Pro in the office. It gets past the USB, starts to probe the ATA devices and then stalls there. 2.6.20-9 works fine.

Sorry for the lack of detail, but the laptop is someone's work laptop - I'll get some exact error messages later on.

Tollef Fog Heen (tfheen) wrote :

Milestoning for beta.

Mike Basinger (mike.basinger) wrote :

Same here
Here is a message I get in recovery mode.
ATA: abnormal status 0x7F on port 0x40DF

James Troup (elmo) on 2007-03-13
Changed in linux-source-2.6.20:
status: Unconfirmed → Confirmed
Anthony Mercatante (tonio) wrote :

Same problem here, with the same error

desrt (desrt) wrote :

copying (possibly) useful log data out of the duplicate bug:

If I boot with the newest kernel 2.6.20-10.17, linux won't boot. I get the following errors:

  ATA: abnormal status 0x7F on port 0x40CF
  ATA: abnormal status 0x7F on port 0x40CF
  ATA: abnormal status 0x7F on port 0x40CF
  ata1.01: qc timeout (cmd 0x27)
  ata1.01: failed to set xfermode (err_mask=0x40)
  ata1.01: limiting speed to PIO0
  ata1: failed to recover some devices, retrying in 5 secs
  ATA: abnormal status 0x7F on port 0x40CF
  ATA: abnormal status 0x7F on port 0x40CF
  ATA: abnormal status 0x7F on port 0x40CF
  ata1.01: qc timeout (cmd 0x27)
  ata1.01: failed to set xfermode (err_mask=0x40)
  ata1.01: disabled
  scsi1: ata_piix
  ATA: abnormal status 0x7F on port 0x40C7
  hda: ATAPI 24x DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
  Uniform CD-ROM driver Revision: 3.20

Done.

       Check root= bootarg cat /proc/cmdline or missing modules, devices: cat /proc/modules ls /dev
ALERT! /dev/disk/by-uuid/228d13f9-92fd-4569-836b-9c7f75cb94c6 does not exist. Dropping to a shell.

with kernel 2.6.20-9.16 I can boot without problems. Though I get three "ATA: abnormal mode" lines as well, but it still finds the HD:

[ 5.044000] ata1: SATA max UDMA/133 cmd 0x40C8 ctl 0x40E6 bmdma 0x40A0 irq 20
[ 5.044000] ata2: SATA max UDMA/133 cmd 0x40C0 ctl 0x40E2 bmdma 0x40A8 irq 20
[ 5.044000] scsi0 : ata_piix
[ 5.208000] ATA: abnormal status 0x7F on port 0x40CF
[ 5.220000] ATA: abnormal status 0x7F on port 0x40CF
[ 5.244000] ata1.01: ATA-8, max UDMA/100, 234441648 sectors: LBA48 NCQ (depth 0/32)
[ 5.244000] ata1.01: ata1: dev 1 multi count 16
[ 5.268000] ata1.01: configured for UDMA/100
[ 5.268000] scsi1 : ata_piix
[ 5.432000] ATA: abnormal status 0x7F on port 0x40C7
[ 5.432000] scsi 0:0:1:0: Direct-Access ATA FUJITSU MHW2120B 0081 PQ: 0 ANSI: 5

I'm running a MacBook Pro 15" with Feisty.

old_toby

ProblemType: Bug
Architecture: i386
Date: Wed Mar 14 19:41:53 2007
DistroRelease: Ubuntu 7.04
Uname: Linux landroval 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

desrt (desrt) wrote :

the "abnormal status" messages exist at least as far back as 2.6.20-5. maybe long before then.

(white 1st gen macbook here with the problem, btw)

Anthony Mercatante (tonio) wrote :

Problem remains with 2.6.20-11.18.
Still getting the "ALERT! /dev/disk/by-uuid/..." while booting in recovery mode as Ryan does.

Tyler Brock (tjb13) wrote :

I can confirm that this is a huge problem and happened for me as well on a MacBook Pro 15" after installing feisty herd 5, which worked fine, and installing the updates, after which booting was impossible.

Colin Watson (cjwatson) wrote :

I'm seeing this on an Intel iMac as well.

Bruno Santos (bsantos) wrote :

White 2nd gen with same problem on 2.6.20-{10,11}.

Darren Albers (dalbers) wrote :

Same problem on an intel Mac-Mini

prp22 (prp-doc) wrote :

Yes, I have the same problem on a Macbook Pro (1st generation) with 2.6.20-11.

old_toby (simon-hornweb) wrote :

Actually, to keep it simple, I guess that problem exists on any intel-mac, so I don't think it's necessary to post every single machine that shows the bug.

@ maintainers

I'd mark the bug as severe, 'cause if the problem remains in the final feisty release, it would prevent any mactel-users from installing it.

Darren Albers (dalbers) wrote :

2.6.10-12 seems to have fixed this for me!

Changed in linux-source-2.6.20:
status: Confirmed → Fix Released
Anthony Mercatante (tonio) wrote :

Same for me, although I noticed that my computer refused to boot twice on about 10 boots...
No way to log this as this doesn't happen in a specific case and is hard to reproduce...
I'll try to get logs next time that happens.

Joey Stanford (joey) wrote :

as per my comment in 92309, this is happening on my System76 Darter Ultra that I use for work. I can boot up normally and login but every 60 seconds or so the computer locks up for 30 seconds to 60 seconds and syslog records an error similar to the above. This is occuring on 2.6.20-12-generic

Stefan Jones (stefanajones) wrote :

I get this problem also on a:
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)
on a dell dimension 8300. Using;
ii linux-image-2.6.20-12-generic 2.6.20-12.20

The boot would hang giving the following messages. I can speed it up by opening and closing the CDROM drives a few times.

I fixed it by recompiling the ata_piix driver from source using the patch I found at:

http://lkml.org/lkml/2007/3/4/259

Hope you include it or another fix in edge. Thanks for the good work.

[ 66.302321] ata2.01: qc timeout (cmd 0xef)
[ 66.302380] ata2.01: failed to set xfermode (err_mask=0x4)
[ 66.302432] ata2: failed to recover some devices, retrying in 5 secs
[ 72.112049] ata2.00: configured for UDMA/33
[ 102.037474] ata2.01: qc timeout (cmd 0xef)
[ 102.037531] ata2.01: failed to set xfermode (err_mask=0x4)
[ 102.037584] ata2.01: limiting speed to UDMA/33:PIO3
[ 102.037635] ata2: failed to recover some devices, retrying in 5 secs
[ 107.847204] ata2.00: configured for UDMA/33
[ 137.772631] ata2.01: qc timeout (cmd 0xef)
[ 137.772687] ata2.01: failed to set xfermode (err_mask=0x4)
[ 137.772739] ata2.01: disabled
[ 137.772787] ata2: failed to recover some devices, retrying in 5 secs
[ 142.768212] ata2.00: failed to set xfermode (err_mask=0x40)
[ 142.768268] ata2: failed to recover some devices, retrying in 5 secs
[ 148.422327] ata2.00: configured for UDMA/33

Stefan Jones (stefanajones) wrote :

I can confirm that the problems was fixed for me with:
linux-image-2.6.20-13-generic 2.6.20-13.21

( cannot see what patch was used though :-( )

Thanks

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

Duplicates of this bug

Other bug subscribers