public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sébastien Bernard" <seb@frankengul.org>
To: debian-sparc@lists.debian.org, linux-kernel@vger.kernel.org
Subject: Re: Weird kernel 2.6.17.[67] behaviour
Date: Thu, 27 Jul 2006 01:15:32 +0200	[thread overview]
Message-ID: <44C7F794.3080304@frankengul.org> (raw)
In-Reply-To: <20060726135526.GA11310@frankengul.org>

seb@frankengul.org a écrit :
> I got a perfectly workable kernel 2.6.17.1 using mkinitramfs on my U60.
> 
> I applied 2 days ago the patches to update the kernel to the 2.6.17.7.
> And to my surprise when rebooting, the boot process hanged for now
> reason.
> 
> More surprising is that when boot continues if I press one key on the
> keyboard or one button on the mouse.
> 
> The hangs happens several times in the start process and each time the
> boot resume when I press a key or a button.
> 
> I never saw such a behaviour and was looking forward the change that
> caused this.
> 
> It is not the compiler since it is the same version used for building
> the 2.6.17.1 and this one is working.
> 
> It is not the mkinitramfs tools since I tried the yaird to regenerate a
> new initrd and it hangs in the same way.
> 
> Can you shed some lights on this dark corner of linux ?
> 
> 	Seb
> 
> 

I have searched which patch is the culprit.
I appears that the 2.6.17.3 kernel is OK and the 2.6.17.4 is showing the
problem..


diff --git a/kernel/sys.c b/kernel/sys.c
index 0b6ec0e..59273f7 100644
--- a/kernel/sys.c
+++ b/kernel/sys.c
@@ -1991,7 +1991,7 @@ asmlinkage long sys_prctl(int option, un
                        error = current->mm->dumpable;
                        break;
                case PR_SET_DUMPABLE:
-                       if (arg2 < 0 || arg2 > 2) {
+                       if (arg2 < 0 || arg2 > 1) {
                                error = -EINVAL;
                                break;
                        }

I've checked and this is really the culprit.
Recompiling the 2.6.17.7 whith the patch reversed got the kernel on
track again.

I can't figure why this cause the problem.
Can you have an explanation for this ?

       reply	other threads:[~2006-07-26 23:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060726135526.GA11310@frankengul.org>
2006-07-26 23:15 ` Sébastien Bernard [this message]
2006-07-26 23:41   ` Weird kernel 2.6.17.[67] behaviour Adam Henley
2006-07-27 10:07     ` seb
2006-07-28 17:06       ` Jan Engelhardt
2006-07-29  0:15       ` Adam Henley

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=44C7F794.3080304@frankengul.org \
    --to=seb@frankengul.org \
    --cc=debian-sparc@lists.debian.org \
    --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