https://www.thinkwiki.org/w/api.php?action=feedcontributions&feedformat=atom&user=Tj 2026-05-23T15:14:26Z User contributions MediaWiki 1.31.12 https://www.thinkwiki.org/w/index.php?title=Talk:How_to_hotswap_Ultrabay_devices&diff=22901 2006-06-25T14:23:55Z

<p>Tj: /* one nit about ultrabay_close script / patch against 2.6.17 available */</p> <hr /> <div>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 &quot;weird&quot; errors -- strange lockups, programs segmentation fault (running &quot;top&quot; resulted in a seg fault), and ultimately a hard lockup.<br /> <br /> 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?<br /> <br /> --[[User:gsmenden|gsmenden]] 00:00, 23 May 2006 (EST)<br /> ----<br /> <br /> 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.<br /> <br /> --[[User:Thinker|Thinker]] 08:37, 23 May 2006 (CEST)<br /> ----<br /> <br /> Cool. If I get brave I'll try it again on the 43p against 2.6.16.16 proper and report back.<br /> <br /> --[[User:gsmenden|gsmenden]] 15:29, 23 May 2006 (EST)<br /> ----<br /> <br /> Works fine here on 2.6.16.<br /> I got only one crash with Suspend to Ram, which I'm unable to reproduce yet.<br /> I renamed the acpi event files because at least my acpid doesn't read files that ends with .conf<br /> <br /> --[[User:Defiant|Defiant]] 21:09, 28 May 2006 (CEST)<br /> <br /> ----<br /> 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!<br /> <br /> --[[User:gsmenden|gsmenden]] 00:57, 31 May 2006 (EST)<br /> <br /> 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...<br /> <br /> --[[User:gsmenden|gsmenden]] 22:08, 19 Jun 2006 (EST)<br /> <br /> == one nit about ultrabay_close script / patch against 2.6.17 available ==<br /> <br /> Howdy,<br /> <br /> 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.<br /> <br /> Also, I've uploaded patch against 2.6.17/2.6.17.1 today.<br /> <br /> http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17-20060625-1.tar.bz2<br /> <br /> Hmmm... My post looks different from others. This wasn't intentional. Just don't know how to add normal discussion entry. Sorry.</div>

Tj https://www.thinkwiki.org/w/index.php?title=Talk:How_to_hotswap_Ultrabay_devices&diff=22900 2006-06-25T14:19:37Z

<p>Tj: one nit about ultrabay_close script / patch against 2.6.17 available</p> <hr /> <div>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 &quot;weird&quot; errors -- strange lockups, programs segmentation fault (running &quot;top&quot; resulted in a seg fault), and ultimately a hard lockup.<br /> <br /> 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?<br /> <br /> --[[User:gsmenden|gsmenden]] 00:00, 23 May 2006 (EST)<br /> ----<br /> <br /> 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.<br /> <br /> --[[User:Thinker|Thinker]] 08:37, 23 May 2006 (CEST)<br /> ----<br /> <br /> Cool. If I get brave I'll try it again on the 43p against 2.6.16.16 proper and report back.<br /> <br /> --[[User:gsmenden|gsmenden]] 15:29, 23 May 2006 (EST)<br /> ----<br /> <br /> Works fine here on 2.6.16.<br /> I got only one crash with Suspend to Ram, which I'm unable to reproduce yet.<br /> I renamed the acpi event files because at least my acpid doesn't read files that ends with .conf<br /> <br /> --[[User:Defiant|Defiant]] 21:09, 28 May 2006 (CEST)<br /> <br /> ----<br /> 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!<br /> <br /> --[[User:gsmenden|gsmenden]] 00:57, 31 May 2006 (EST)<br /> <br /> 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...<br /> <br /> --[[User:gsmenden|gsmenden]] 22:08, 19 Jun 2006 (EST)<br /> <br /> == one nit about ultrabay_close script / patch against 2.6.17 available ==<br /> <br /> Howdy,<br /> <br /> 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.<br /> <br /> Also, I've uploaded patch against 2.6.17/2.6.17.1 today.<br /> <br /> http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17-20060625-1.tar.bz2</div>

Tj