[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2008-03-11 Thread Leann Ogasawara 
Marking Fix Released as patch appears to be available in the Feisty
kernel.

** Changed in: linux-source-2.6.20 (Ubuntu)
   Status: Fix Committed = Fix Released

-- 
UDMA 33 instead of UDMA 100 used 
https://bugs.launchpad.net/bugs/95921
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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2008-02-11 Thread Leann Ogasawara 
This bug report was marked Fix Committed a while ago but there hasn't
been any recent activity.  Can you just verify this bug has been
resolved and we'll go ahead and mark this bug report as Fix Released.
Thanks in advance.

-- 
UDMA 33 instead of UDMA 100 used 
https://bugs.launchpad.net/bugs/95921
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2007-04-05 Thread Giovanni Condello 
Same issue here and same dmesg output (same laptop too?)

-- 
UDMA 33 instead of UDMA 100 used 
https://launchpad.net/bugs/95921

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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2007-04-05 Thread Luís Silva 
Well, the patch resolved the problem with UDMA and now my hard drive is
detected as UDMA100 as expected... But in what relates to the ATA:
abnormal status 0x7F on port 0x000101f7 message, she's still there...
:(

-- 
UDMA 33 instead of UDMA 100 used 
https://launchpad.net/bugs/95921

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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2007-04-04 Thread Ben Collins 
** Changed in: linux-source-2.6.20 (Ubuntu)
   Importance: Undecided = Medium
 Assignee: (unassigned) = Ben Collins
   Status: Confirmed = Fix Committed

-- 
UDMA 33 instead of UDMA 100 used 
https://launchpad.net/bugs/95921

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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2007-04-01 Thread Giovanni Condello 
Sent patch to launchpad

** Attachment added: LKML patch which has been reported to work
   http://librarian.launchpad.net/7097877/patch.patch

-- 
UDMA 33 instead of UDMA 100 used 
https://launchpad.net/bugs/95921

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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2007-03-28 Thread Luís Silva 
Apparently there's already a patch that fixes this problem... I'm going
to try it against kernel 2.6.21-rc5 in a few moments...

The patch can be found here http://lkml.org/lkml/2007/3/22/47

-- 
UDMA 33 instead of UDMA 100 used 
https://launchpad.net/bugs/95921

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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2007-03-28 Thread Olivier Lacroix 
Nice.

are we supposed to let the devs know about it in any particular way ?

** Changed in: Ubuntu
Sourcepackagename: None = linux-source-2.6.20

-- 
UDMA 33 instead of UDMA 100 used 
https://launchpad.net/bugs/95921

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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2007-03-27 Thread Luís Silva 
I too have been having some problems with a laptop (asus Z96J) since
upgrade to feisty. Sometimes it takes for ages to boot... Other times it
boots normally, but with a strange error in the logs (ATA: abnormal
status 0x7F on port 0x000101f7)...

I'm going to attach copies of dmesg (named dmesg.x.orig) and dmesg |
grep -i ata (named dmesg.x.ata) to this bug in all the three situations.
dmesg.0 corresponds to a situation where it took for ages to boot,
dmesg.1 is the following boot (with no changes, just reboot). And
dmesg.2 is for a boot with a hand compiled kernel (2.6.20.4, compiled
the debian (or ubuntu ;)) way.

** Attachment added: All dmesg described in comment
   http://librarian.launchpad.net/6995726/debug.tar.gz

-- 
UDMA 33 instead of UDMA 100 used 
https://launchpad.net/bugs/95921

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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2007-03-25 Thread Sascha 

** Attachment added: Complete dmesg output
   http://librarian.launchpad.net/6932564/dmesg.txt

-- 
UDMA 33 instead of UDMA 100 used 
https://launchpad.net/bugs/95921

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

[Bug 95921] Re: UDMA 33 instead of UDMA 100 used

2007-03-25 Thread Olivier Lacroix 
I get the same problem.

** Changed in: Ubuntu
   Status: Unconfirmed = Confirmed

-- 
UDMA 33 instead of UDMA 100 used 
https://launchpad.net/bugs/95921

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