Difference between revisions of "Talk:How to hotswap Ultrabay devices"

From ThinkWiki
Jump to: navigation, search
(one nit about ultrabay_close script / patch against 2.6.17 available)
(one nit about ultrabay_close script / patch against 2.6.17 available)
Line 42: Line 42:
  
 
Hmmm... My post looks different from others.  This wasn't intentional.  Just don't know how to add normal discussion entry.  Sorry.
 
Hmmm... My post looks different from others.  This wasn't intentional.  Just don't know how to add normal discussion entry.  Sorry.
 +
 +
--tj
 +
----
 +
 +
Right, it works fine without "sleep 3" using the new patches. Sleep removed.
 +
 +
--[[User:Thinker|Thinker]] 12:35, 1 July 2006 (CEST)
 +
----

Revision as of 12:35, 1 July 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)


Update - patched against 2.6.16.19, works fine. It appears my previous problems were due to a disk error unrelated to the patch. Excellent!

--gsmenden 00:57, 31 May 2006 (EST)

Anybody have time to make a patch of the libata(-tj) .git tree against the recently released 2.6.17? I hope to make one in the future if not...

--gsmenden 22:08, 19 Jun 2006 (EST)

one nit about ultrabay_close script / patch against 2.6.17 available

Howdy,

In ultrabay_close, there is 'sleep 3' for disk spinup, which isn't necessary. libata itself waits for disk spinup and if something breaks (e.g. first reset fails w/ timeout or something), it's libata's fault. Please remove that line and see if anything breaks.

Also, I've uploaded patch against 2.6.17/2.6.17.1 today.

http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17-20060625-1.tar.bz2

Hmmm... My post looks different from others. This wasn't intentional. Just don't know how to add normal discussion entry. Sorry.

--tj


Right, it works fine without "sleep 3" using the new patches. Sleep removed.

--Thinker 12:35, 1 July 2006 (CEST)