public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Han Boetes <han@mijncomputer.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: panic with 2.6.0 and jfs which doesn't happen with test11
Date: Thu, 18 Dec 2003 20:03:08 +0100	[thread overview]
Message-ID: <20031218190330.GD28497@boetes.org> (raw)
In-Reply-To: <20031218140936.GA2216@boetes.org>

Han Boetes wrote:
> I just compiled 2.6.0 and after booting I got a panic:
> 
> INIT: cannont execute "/etc/rc.d/rc.sysinit"
> 
> This problem doesn't occur with 2.6.0-test11 with the same config.
> 
> 
> To do some testing I booted the kernel in with `260 init=/bin/sh' and
> then tried: `ls -la /etc/fstab'
> 
> It took about two seconds to answer, printed:
> 
> -rw-r--r--    1 root     root          868 nov  2 22:58 /etc/fstab\n
> 
> and then hanged.
> 
> 
> I tried this a few times and it's really consistent.

Sorry, I was dead wrong there. This is a gcc-3.3.2 related problem:

  http://marc.theaimsgroup.com/?l=mandrake-cooker&m=107166064321438&w=2



# Han

      reply	other threads:[~2003-12-18 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 14:09 panic with 2.6.0 and jfs which doesn't happen with test11 Han Boetes
2003-12-18 19:03 ` Han Boetes [this message]

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=20031218190330.GD28497@boetes.org \
    --to=han@mijncomputer.nl \
    --cc=linux-kernel@vger.kernel.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