public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	Tejun Heo <htejun@gmail.com>
Subject: [2 regressions] Current git cannot find root device on x86-64 (HP nx6325), NFS broken
Date: Tue, 7 Apr 2009 00:47:55 +0200	[thread overview]
Message-ID: <200904070047.56172.rjw@sisk.pl> (raw)

Hi,

Current mainline (commit 22ae77bc7ac115b9d518d5cbc13d39317079b2b0) can't
find the root device (it's handled by statically compiled-in sata_sil) and
generally causes the "invalid module format" message to appear for all modules
loaded from the initrd on my HP nx6325 (the distro is openSUSE 11.1).

I don't know which commit might have made this happen, but the breakage was
introduced during the last three days (commit
601cc11d054ae4b5e9b5babec3d8e4667a2cb9b5 is certainly good).  I'll bisect
tomorrow if there are no ideas.

Also, mounting directories over NFS doesn't work (I think it oopses, but
didn't have the time to look at it more closely).

Thanks,
Rafael

             reply	other threads:[~2009-04-06 22:48 UTC|newest]

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

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=200904070047.56172.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=Trond.Myklebust@netapp.com \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox