kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

** This bug is no longer a duplicate of bug 965213
   ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/279693

Title:
  Regression Sata hard disk unable to mount after upgrade 2.6.27 generic
  kernel

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Description:	Ubuntu intrepid (development branch)
  Release:	8.10

  
  After Intrepid beta clean installation every thing worked fine. I made the last updates.  From kernel 2.6.27-4-generic to 2.6.27-6-generic now I can't boot because my second serial ata  hard disk ( Maxtor 6V250F0) fails to mount in /media/sdb1 on start up.

  After remove this sdb from fstab I could start.

  But If I want to mount this device I have the same kernel error and I
  cant access to this harddisk.

  The kernel log is:

  ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
  Oct  7 17:49:59 deflagmator kernel: [   86.604091] ata4.00: cmd ca/00:08:fc:86:bb/00:00:00:00:00/e0 tag 0 dma 4096 out
  Oct  7 17:49:59 deflagmator kernel: [   86.604094]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  Oct  7 17:49:59 deflagmator kernel: [   86.604101] ata4.00: status: { DRDY }
  Oct  7 17:49:59 deflagmator kernel: [   86.604113] ata4: hard resetting link
  Oct  7 17:50:00 deflagmator kernel: [   87.080072] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  Oct  7 17:50:00 deflagmator kernel: [   87.105231] ata4.00: configured for UDMA/133
  Oct  7 17:50:00 deflagmator kernel: [   87.105262] ata4: EH complete

  I tried to change the jumper to 1,5 GB instead to 3GB and every works
  fine.

  
  I think is an error in this last update. 
  THIS COULD HELP . Yesterday I tried  debian lenny. (clean installation) after the upgrade with last kernel available I also have the same problem. 

  Maybe is an incompatibility with this Maxtor hard disk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/279693/+subscriptions