Re: Quick question about libata and hdparm



Hi, Alan. Thanks for your mail.

On Apr 20 2009, Alan Cox wrote:
Can you comment on the dmesg log attached? I'd like to, at least,
understand what is happening, since I'm starting to consider using
libata with all my computers.

Its logging a couple of transmission errors. The CRC is computed by
hardware each end and compared (by hardware).

Right. I don't remember the kernel logging out errors when I was using a
custom kernel and pure Debian userland with the promise IDE controller
on this ASUS K7V motherboard (which has a VIA KT-133 chipset, not a
KT-133A).

I can try to test that again, but now I have installed Ubuntu for my
girlfriend. I have two spare IDE HDs here that I can use for testing
purposes and trash everything. If more testing is desired, please let me
know.

This computer, in particular, uses an IDE drive with a 40 ribbon
cable (and, thus, no UDMA/66). The cable is well put (checked two
times already) and I believe that everything is OK with this cable,
since I substituted it was already substituting one that gave me the
same results.

It's tuned down to UDMA33 which looks correct.

Yes, that looks fine, as I only have the 40 ribbon cable.

If I saw a lot of these I'd suspect something like a controller timing
setup error, but you seem to just have occasional ones in the log which
really does look like genuine CRC errors from electrical noise or
similar.

Hummm, now that you mention it, I will see if the loudspeakers installed
may have any impact on it.

You don't happen to have any amateur radio transmitters or telsa coils in
the room with it ;) ?

No, I don't. :-) But I do have an open embedded computer (with its own
IDE HD) at less than 10cm of this desktop and said speakers. I will try
to find any other source of electromagnetic noise.

I can try many things here to try to fix that. I want libata to not have
that experimental warning for IDE devices.


Thanks, Rogério Brito.

--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: Computers and Power Use
    ... Maybe I have IDE and SCSI confused, I last diddled about seriously with IDE about 5 years ago. ... I *have* given the subject thought before, and frankly, and regretfully off topic this is why I don't leave any of the older computers running, like the IBM 9595A or Server 720. ... Quite coincidentally, after reading that article that you pointed out, not 15 minutes later I as reading in my newspaper this morning about electric rate increases here in Cincinnati Ohio. ... A feature I have always like and why I prefer IDE drives that spin down. ...
    (comp.sys.ibm.ps2.hardware)
  • Re: Track Domain User Logons and Logoffs
    ... >>In Kerberos, computers are actually logging in and out, ... > principal logging in. ... > logon and which to the logoff... ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Restricting few users only to logon to a PC in a Windows 2003
    ... I would suggest that you listen to what young Mr. Desmond is saying. ... and there are five people who keep on logging on to computers in a specific ... from logging on to this computer.... ... I have a Windows XP Sp 2 machine in my Windows 2003 domain. ...
    (microsoft.public.windows.server.active_directory)
  • WndDbg Advise - Location of Source and Symbols
    ... Having concluded that I need visibility beneath the level of the VC6 IDE ... computers, and I have the two computers connected on a simple Windows peer ... IDE, symbols and source on the Host, and use the Target only for program ... VC++ Debugger weblog. ...
    (microsoft.public.vc.mfc)
  • Re: Use of .WSX file types...
    ... Last night, using one of the affected computers, logging in as someone else and the WorkSaver program worked. ... > (speaking for myself and doing this in my free time) ...
    (microsoft.public.windowsmedia.player)