All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Mike Galbraith <efault@gmx.de>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [2 regressions] Current git cannot find root device on x86-64(HP nx6325), NFS broken
Date: Tue, 07 Apr 2009 14:30:24 -0500	[thread overview]
Message-ID: <49DBA9D0.7080400@lwfinger.net> (raw)
In-Reply-To: <200904072113.20703.rjw@sisk.pl>

Rafael J. Wysocki wrote:
> On Tuesday 07 April 2009, Larry Finger wrote:
>> My system also fails to load modules from initrd unless 9cb610d is reverted.
>> Something is wrong with the "module: remove the SHF_ALLOC flag on the __versions
>> section" patch.
> 
> This is fixed in the current -git, although I had to apply the patch from
> http://patchwork.kernel.org/patch/16776/
> to fix an Oops on boot.

Thanks for the heads-up, particularly on the 16776 patch above. I was in the
middle of a bisection to isolate that one.

Do you know anything about a regression that leads to "phy0: Failed to
initialize wep: -2" messages? It is the 3rd one that I'm chasing and seems to
affect all wireless drivers. For this one, removing and reinserting the driver
corrects the problem.

Larry




  reply	other threads:[~2009-04-07 19:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 14:58 [2 regressions] Current git cannot find root device on x86-64(HP nx6325), NFS broken Larry Finger
2009-04-07 19:13 ` Rafael J. Wysocki
2009-04-07 19:30   ` Larry Finger [this message]
2009-04-07 20:49     ` Rafael J. Wysocki
2009-04-07 20:57       ` Larry Finger
2009-04-07 21:10         ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2009-04-06 22:47 [2 regressions] Current git cannot find root device on x86-64 (HP " Rafael J. Wysocki
2009-04-06 23:46 ` Trond Myklebust
2009-04-07 19:18   ` Rafael J. Wysocki
2009-04-07  5:39 ` Mike Galbraith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49DBA9D0.7080400@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.