Difference between revisions of "Talk:How to hotswap Ultrabay devices"
m |
m |
||
| Line 14: | Line 14: | ||
--[[User:gsmenden|gsmenden]] 15:29, 23 May 2006 (EST) | --[[User:gsmenden|gsmenden]] 15:29, 23 May 2006 (EST) | ||
| + | ---- | ||
| + | |||
| + | Works fine here on 2.6.16. | ||
| + | I got only one crash with Suspend to Ram, which I'm unable to reproduce yet. | ||
| + | I renamed the acpi event files because at least my acpid doesn't read files that ends with .conf | ||
| + | |||
| + | --[[User:Defiant|Defiant]] 21:09, 28 May 2006 (CEST) | ||
Revision as of 21:22, 28 May 2006
I recently tried using the libata-tj patch tarball for 2.6.16.16, applying this against the newly released 2.6.16.18 kernel (released today.) Patch applied cleanly. Upon boot, I immediately get a multitude of "weird" errors -- strange lockups, programs segmentation fault (running "top" resulted in a seg fault), and ultimately a hard lockup.
I booted back to my vanilla 2.6.16.16, ran fsck (appeared to just replay a few transactions, no major damage), and am back to normal. However, it successfully scared me off - unfortunately can't risk too much downtime (or worse, subtle fs corruption) right now on my main system. Anybody have experiences with this on a T43p using piix driver?
--gsmenden 00:00, 23 May 2006 (EST)
The 2.6.16.16 patch works fine on my T43. There's a git tree (mentioned on the patch's webpage) which is closer to 2.6.18, but AFAIK no simple unified patch was prepred.
--Thinker 08:37, 23 May 2006 (CEST)
Cool. If I get brave I'll try it again on the 43p against 2.6.16.16 proper and report back.
--gsmenden 15:29, 23 May 2006 (EST)
Works fine here on 2.6.16. I got only one crash with Suspend to Ram, which I'm unable to reproduce yet. I renamed the acpi event files because at least my acpid doesn't read files that ends with .conf
--Defiant 21:09, 28 May 2006 (CEST)
