From: Dennis Gilmore <dennis@ausil.us>
To: Adrian Bunk <bunk@stusta.de>
Cc: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>,
davem@davemloft.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org
Subject: Re: 2.6.19 (current from git) on SPARC64: Can't mount /
Date: Sun, 17 Dec 2006 21:29:59 -0600 [thread overview]
Message-ID: <200612172130.00346.dennis@ausil.us> (raw)
In-Reply-To: <20061218032003.GU10316@stusta.de>
Once upon a time Sunday 17 December 2006 9:20 pm, Adrian Bunk wrote:
> On Wed, Dec 13, 2006 at 03:56:46PM -0300, Horst H. von Brand wrote:
> > I've been running kernel du jour straight from git on my SPARC Ultra 1
> > for some time now on Aurora Corona (Fedora relative, development branch).
> > For a few days now 2.6.19 panics on boot, it can't mount /. 2.6.19 worked
> > fine, as does 2.6.19.1 (Aurora changed gcc, mkinitrd, ... in between, so
> > I had to rebuild a kernel to check if the problem lay elsewhere).
> > Unpacking the initrds for 2.6.19 and 2.6.19.1 shows the same (nash
> > script) /init and the same modules in both (ext3 + jbd, scsi_mod, sd_mod,
> > esp, others).
> >
> > I'm stumped. Any clue?
not 100% sure here. Check the size of the initrd. kinda sounds like an issue
that hit rawhide last week that needed a new mkinitrd. if its smaller grab
the srpm from the Fedora Development tree for mkinitrd and rebuild it. then
recreate your initrd and see if that works.
Dennis
next prev parent reply other threads:[~2006-12-18 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 18:56 Horst H. von Brand
2006-12-18 3:20 ` Adrian Bunk
2006-12-18 3:29 ` Dennis Gilmore [this message]
2006-12-27 20:38 ` Horst H. von Brand
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=200612172130.00346.dennis@ausil.us \
--to=dennis@ausil.us \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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
all inboxes | Powered by JetHome®