** Description changed:

- I have a GIGABYTE GA-MA78GM-S2H motherboard with integrated RAID controler 
and eSATA connector. Thr is an external port multiplier attached to this eSATA 
port, SansDigital TR4M-B with 3 1.5TB Seagate drives. 
- This combination worked perfectly for me in Intrepid, but when I upgraded to 
Jaunty and new kernel it now fails to recognize and initialize the drives in 
this external box. Dmesg shows long delays and resets when ata6 is beeing 
initialized. Sometimes, around 1 in 5 times, it manages to initialize it, but 
most of the times it fails. 
+ I have a GIGABYTE GA-MA78GM-S2H motherboard with integrated RAID controller 
and eSATA connector. There is an external port multiplier attached to this 
eSATA port, SansDigital TR4M-B with 3 1.5TB Seagate drives. 
+ This combination worked perfectly for me in Intrepid, but when I upgraded to 
Jaunty and new kernel it now fails to recognize and initialize the drives in 
this external box. Dmesg shows long delays and resets when ata6 is being 
initialized. Sometimes, around 1 in 5 times, it manages to initialize it, but 
most of the times it fails. 
  If I boot into the previous kernel (2.6.27-14) it boots smoothly as it did in 
Intrepid.
- LEt me know if ther is any additional info needed.
+ Let me know if there is any additional info needed.
  
  ProblemType: Bug
  Architecture: amd64
  CurrentDmesg: [   72.693282] lirc_imon: VFD port opened
  DistroRelease: Ubuntu 9.04
  HibernationDevice: RESUME=UUID=70bfbfb6-831b-415d-88d6-89c2e4079b2f
  MachineType: Unknow Unknow
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.28-12-generic 2.6.28-12.43 [modified: 
lib/modules/2.6.28-12-generic/kernel/ubuntu/lirc/lirc_imon/lirc_imon.ko]
  ProcCmdLine: root=LABEL=root-fs ro quiet splash
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.28-12.43-generic
  SourcePackage: linux

** Tags added: jaunty sata

-- 
Jaunty upgrade breaks SATA port multiplier
https://bugs.launchpad.net/bugs/383294
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to