Steve Langasek <[EMAIL PROTECTED]> writes: > On Mon, May 09, 2005 at 07:39:20PM -0700, Russ Allbery wrote:
>> * Handle modules named either with or without the .mp extension on SMP >> hosts. (Closes: #305389, #307280, #307797) >> Judging from the bug reports, it caused a fair amount of confusion and >> one problem at the important severity level because it can hit people >> during upgrades. See the log for #305389 for most of the analysis. > If a minimally-intrusive solution can be found, I would probably accept > it into sarge. That's no problem; the fix is fairly straightforward and should be reviewable: afs.rc.linux | 31 ++++++++++++++++++++++++------- 1 files changed, 24 insertions(+), 7 deletions(-) a fair chunk of which is a comment. > FYI: > $ grep PREEMPT /boot/config-2.6.8-2-686-smp > CONFIG_PREEMPT=y Oh, interesting! I completely didn't think to check that. In that case.... > Well, if you've tested the sarge 2.6 kernels and not been able to > reproduce the problem, then it's pretty definitely not RC. :) ...this may not be as serious of a problem as I feared, since I did indeed test the sarge 2.6 kernel and was able to mount and unmount /afs without any difficulty at all. So it sounds like, at least on i386, one needs both preempt *and* a newer kernel (2.6.11 is where most of the reported problems start) in order to trigger this bug. In that case, I think the documentation route is best. I'll prepare a documentation and init script upload for testing-proposed-updates, then, after 1.3.81-5 (which has the init script fix) has aged a few days in unstable without any trouble. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
