Up to [cvs.NetBSD.org] / src / sys / dev / ic
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: netbsd-5-1-2-RELEASE
Revision 1.18.4.4 / (download) - annotate - [select for diffs], Sun Mar 28 16:21:18 2010 UTC (14 years ago) by snj
Branch: netbsd-5
CVS Tags: netbsd-5-1-RELEASE,
netbsd-5-1-RC4,
netbsd-5-1-RC3,
netbsd-5-1-RC2,
netbsd-5-1-RC1,
netbsd-5-1-5-RELEASE,
netbsd-5-1-4-RELEASE,
netbsd-5-1-3-RELEASE,
netbsd-5-1-2-RELEASE,
netbsd-5-1-1-RELEASE,
netbsd-5-1,
matt-nb5-pq3-base
Branch point for: matt-nb5-pq3
Changes since 1.18.4.3: +20 -7
lines
Diff to previous 1.18.4.3 (colored) to branchpoint 1.18 (colored)
Pull up following revision(s) (requested by bouyer in ticket #1317): sys/dev/ic/ahcisata_core.c: revision 1.23, 1.24 Move ahci_channel_start() after BSY has cleared (what seems to matter here is not touching SError while BSY is asserted). Fix random behavior (serial console corruption/misfunction, misbehavior of USB controllers, crasy interrupts crashing the Xen hypervisor, ...) of Intel ESB2 controller with some brand of hitachi drives. -- ahcisata_core.c 1.23 cause long drive probe (31s, reported by Roy Marples), or other devices misbehavior probably due to interrupts issues (reported by Jukka Ruohonen). Back it out and do the following changes: - clear port interrupt register before ahci_channel_start() which enables interrupts - wait 500ms after sata_reset_interface() before touching SERROR register. This is what seems to fix the issue I'm seeming on ESB2 controller. - The 31s delay didn't cause the probe to fail because of a mismatch in loop index comparison; use a #define for delay after reset instead of numeric values, to avoid this kind of bugs in the future.