LWN: Comments on "Kernel release status" https://lwn.net/Articles/82519/ This is a special feed containing comments posted to the individual LWN article titled "Kernel release status". en-us Sun, 02 Nov 2025 01:34:30 +0000 Sun, 02 Nov 2025 01:34:30 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Kernel release status https://lwn.net/Articles/84062/ https://lwn.net/Articles/84062/ nobrowser What happened to the ext[23] htree feature? It was promised for 2.4.26 but<br>it's not there; and now 2.4 seems to be nearing death.<br> Fri, 07 May 2004 17:49:49 +0000 2.6.6-rc3 crashes, here -- FIXED https://lwn.net/Articles/83058/ https://lwn.net/Articles/83058/ Duncan Seems that mine has been fixed with the 2.6.6-rc3-bk3, which I'm now <br>running. I expected it was, when I saw this in the log: <br> <br>&lt;quote&gt; <br> <br>ChangeSet@1.1638, 2004-04-30 14:51:54-07:00, akpm@osdl.org <br>[PATCH] task_struct alignment fix <br> <br>The recent slab alignment changes broke [many archs] (parisc and x86_64 <br>for sure) by causing task_structs to be insufficiently aligned. [C]hange <br>[it back] to L1_CACHE_BYTES, [as] we used to have, via <br>SLAB_HW_CACHE_ALIGN. <br> <br>&lt;/quote&gt; <br> <br>I figured that must be what I saw on x86_64, but I can boot the new kernel <br>again, now, and as a bonus I now know what the nightly bk snapshots are <br>(as mentioned in /something/ I was reading, recently, either on the Gentoo <br>lists or on LWN) and where to find and how to apply them. =:^) <br> <br>Duncan <br> Sat, 01 May 2004 16:52:30 +0000 2.6.6-rc3 crashes, here. https://lwn.net/Articles/82981/ https://lwn.net/Articles/82981/ Duncan I don't think it's the same bug, then, as I'm running rc2 without issue. <br> <br>Unless it was in rc1 (which I didn't have time to try), somehow got masked <br>at least for my combination of hardware and kernel config for rc2, and <br>then reappeared in rc3.. <br> <br>I suppose that's possible, if it's something under current rapid <br>development. However, I wouldn't think it all that likely.. <br> <br>Maybe I'll have to go pull rc1, compile it, and see, if 2.6.6 doesn't fix <br>it or is delayed until after the weekend. Right now, I have the sleep I <br>SHOULD have been doing when I was working on the computer, to catch up on. <br>&lt;g&gt; <br> <br>Duncan <br> Fri, 30 Apr 2004 17:09:40 +0000 2.6.6-rc3 crashes, here. https://lwn.net/Articles/82954/ https://lwn.net/Articles/82954/ corbet FWIW, I believe I'm begin bitten by the same bug; it was introduced in -rc1. I'm trying to track it down in my spare time... Fri, 30 Apr 2004 14:21:39 +0000 2.6.6-rc3 crashes, here. https://lwn.net/Articles/82945/ https://lwn.net/Articles/82945/ Duncan 2.6.6-rc3 crashes, here. It compiles fine, but it crashes either at /proc <br>mount or shortly thereafter, giving me an error about sleeping with a lock <br>held, and preemption. <br> <br>I'm running dual Opteron 242s, thus AMD64 in SMP mode. The problem quite <br>likely is some 64-bit unclean code somewhere, very possibly not triggered <br>and possibly compiled out, unless SMP and/or preemption are on. <br> <br>Unfortunately, I don't know enough about kernel bug reporting to know how <br>or what to do about it, or even how to check to see if anyone else has <br>reported something similar, so it's just wait and see if it's fixed in <br>2.6.6 proper, right now. If not, I'll have to go read up on all that and <br>figure it out. (I may have done so already, except the hard crash took <br>out my video card and it took me several hours to figure out exactly what <br>it was and fix it.. in part because the card would come back after some <br>twiddling around for awhile, as if certain crashes stuffed up a <br>configuration register that took some time to stabilize due to capacitance <br>bleed-off, but the card now seems to have quit for good.. it's not coming <br>back any more.. Oh, well, it was only an ATI Radeon 7200 dual monitor <br>out, so not TOO expensive.) <br> <br>Duncan <br> Fri, 30 Apr 2004 14:12:27 +0000