From: jamal <hadi@cyberus.ca>
To: Stefan Lippers-Hollmann <s.L-H@gmx.de>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
davem@davemloft.net, stable@kernel.org
Subject: Re: patch net-restore-ip-source-validation.patch added to 2.6.32-stable tree
Date: Thu, 04 Feb 2010 06:13:31 -0500 [thread overview]
Message-ID: <1265282011.4204.12.camel@bigi> (raw)
In-Reply-To: <201002032114.59960.s.L-H@gmx.de>
Hi there,
I am downloading 2.6.32-7 to see if i can reproduce it. My gut is
telling me it will be hard to see in my setup.
Can you try to see if it something in your boot initialization i.e with
no init e.g something like init=/bin/sh and then initcall_debug?
cheers,
jamal
On Wed, 2010-02-03 at 21:14 +0100, Stefan Lippers-Hollmann wrote:
>
> This patch, as part of the current 2.6.32 stable queue, breaks booting with
> an oops very early, before the framebuffer got a chance to initialize
> (unfortunately most of it is cut with the unavoidable vga=0, so I didn't
> write it down yet), on amd64 and i386 (kernel configs attached). Removing
> just this patch from queue-2.6.32 fixes the problem for me; kernel 2.6.33
> HEAD doesn't seem to be affected.
>
> Regards
> Stefan Lippers-Hollmann
>
next prev parent reply other threads:[~2010-02-04 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1265060041850@kroah.org>
2010-02-03 20:14 ` patch net-restore-ip-source-validation.patch added to 2.6.32-stable tree Stefan Lippers-Hollmann
2010-02-04 11:13 ` jamal [this message]
2010-02-04 17:50 ` Stefan Lippers-Hollmann
2010-02-04 18:14 ` jamal
2010-02-04 18:19 ` David Miller
2010-02-04 18:29 ` jamal
2010-02-04 18:31 ` Stefan Lippers-Hollmann
2010-02-04 18:38 ` jamal
2010-02-04 19:49 ` Stefan Lippers-Hollmann
2010-02-04 19:57 ` jamal
2010-02-04 20:03 ` David Miller
2010-02-04 19:50 ` jamal
2010-02-04 20:03 ` David Miller
2010-02-05 16:50 ` Greg KH
2010-02-04 20:24 ` Stefan Lippers-Hollmann
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=1265282011.4204.12.camel@bigi \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=s.L-H@gmx.de \
--cc=stable@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