Re: JMB363 false hotplug detections

From: Tejun Heo
Date: Tue Jan 19 2010 - 03:58:55 EST


On 01/18/2010 05:19 AM, Krzysztof Halasa wrote:

Definitely looks like electrical problem to me. The controller is
repeatedly reporting spurious hotplug events and the problem is not
universal to the controller either. I've played with several
different jmb363s and they all worked just fine. It would be
interesting to see whether the problem is reproducible on different
boards of the same model.

> BTW setting the JMB363 mode in BIOS setup from IDE to AHCI or RAID
> (thus enabling JMB363 BIOS) changes nothing.

That's expected. The controller is always put into ahci mode during
intialization regardless of the mode programmed by the bios.

> The only weird thing is that some time ago the problems weren't there.
> It could be genuine hardware problem. I have full kernel logs. Sometimes
> the same kernel (build) is "good" at one time and "bad" at another.
> I had booted the board (with JMB363 and the driver enabled) 57 times.
> Out of these, there was no problems 16 times (date-hrs-result):
> There are no significant kernel log differences between *good and *bad
> (excluding the AHCI messages). Sometimes the exceptions were sporadic,
> like in 09-01-12:53-bad case:
> Sep 1 12:53:38 Machine booted
> Sep 1 13:02:33 ata8: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
> Sep 1 13:02:33 ata8: irq_stat 0x00000040, connection status changed
> Sep 1 13:02:33 ata8: SError: { CommWake DevExch }
> Sep 1 13:02:33 ata8: hard resetting link
> Sep 1 13:02:34 ata8: SATA link down (SStatus 0 SControl 300)
> Sep 1 13:02:34 ata8: EH complete
> Sep 1 15:47:12 Machine rebooted
> Perhaps I should really check these resistors around the JMB363 chip,
> and maybe using a vacuum cleaner is a good idea? I think I will do.
> It's certaing there was nothing connected do JMB363 SATA. I don't know
> BIOS versions and CMOS (BIOS) configs.

They don't matter. Once the OS takes over, the controller is forced
into multi function ahci mode and the kernel version wouldn't have any
effect on it either. That part of code hasn't changed for years now.
So, yeah, looks like a genuine hardware problem to me.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at