All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>, davem@davemloft.net
Cc: 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: Mon, 18 Dec 2006 03:20:03 +0000	[thread overview]
Message-ID: <20061218032003.GU10316@stusta.de> (raw)
In-Reply-To: <200612131856.kBDIuk8U028993@laptop13.inf.utfsm.cl>

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?

Is this issue still present in the latest -git?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>, davem@davemloft.net
Cc: 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: Mon, 18 Dec 2006 04:20:03 +0100	[thread overview]
Message-ID: <20061218032003.GU10316@stusta.de> (raw)
In-Reply-To: <200612131856.kBDIuk8U028993@laptop13.inf.utfsm.cl>

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?

Is this issue still present in the latest -git?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-12-18  3:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 18:56 2.6.19 (current from git) on SPARC64: Can't mount / Horst H. von Brand
2006-12-18  3:20 ` Adrian Bunk [this message]
2006-12-18  3:20   ` Adrian Bunk
2006-12-18  3:29   ` Dennis Gilmore
2006-12-18  3:29     ` Dennis Gilmore
2006-12-27 20:38   ` Horst H. von Brand
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=20061218032003.GU10316@stusta.de \
    --to=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 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.