From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Trenton D. Adams" Subject: Re: 2.6.29 on MacBook 2,1 fails to reboot (was Re: 2.6.29-git13: Reported regressions from 2.6.28) Date: Tue, 7 Apr 2009 12:22:01 -0600 Message-ID: <9b1675090904071122k6a53295fwfffc336011edee8e@mail.gmail.com> References: <49DB7C77.1000702@s5r6.in-berlin.de> <9b1675090904070944m798ed608i1d9194ebd1ed3961@mail.gmail.com> <49DB8909.3000905@s5r6.in-berlin.de> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hESHAF78lmL2mhPG/VLQTzVokR1YIDmiy++pqC8nHKU=; b=OS0cGf28Z+kp7GBqoveZlc+EM6GB7hZJYWCiRSOlvZ58X9Sn8rZrwnepWQfJ5RMkaj LK7zoYGhnks3IK7QMu6pdgC2n4vxh0WVY8wOlOD4gUNjFeokvH/uPOF+yQZT8squbAan SyjNcLgKs7KaBIn/Y0++DkL9hT8zyG4LHqBXI= In-Reply-To: <49DB8909.3000905@s5r6.in-berlin.de> Sender: netdev-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: Stefan Richter Cc: Linus Torvalds , "Rafael J. Wysocki" , Linux Kernel Mailing List , Adrian Bunk , Andrew Morton , Natalie Protasevich , Kernel Testers List , Network Development , Linux ACPI , Linux PM List , Linux SCSI List , Takashi Iwai On Tue, Apr 7, 2009 at 11:10 AM, Stefan Richter wrote: > Trenton D. Adams wrote: > Interdependencies between ALSA modules have changed. =A0The Gentoo in= it > scripts attempted to unload them in an order which deadlocked modprob= e > due to dependencies. =A0The fix for Gentoo is to just not unload the > modules on system shutdown. =A0My Gentoo/amd64 Mac mini was affected = by > this too; fixed by userland update. > While that is interesting, I am not seeing that problem on my Gentoo box (the macbook), which is completely up-to-date. 2.6.28 works, and 2.6.29 doesn't. Same init scripts, different kernels. And sure, I could put a comment on the rmmod, in the init script, but IMO that would be a hack around a _bug_. Which is fine for me. But, is it worth leaving the issue in the kernel?