From: Doug Chapman <doug.chapman@hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Linus' tree broken?
Date: Mon, 23 Jul 2007 23:07:56 +0000 [thread overview]
Message-ID: <1185232076.7158.56.camel@dchapman.boston.redhat.com> (raw)
In-Reply-To: <46A4B026.9030307@sgi.com>
On Mon, 2007-07-23 at 15:42 -0700, Luck, Tony wrote:
> > I am hitting this on my rx2620, rx6600 and rx2600 (i.e. everywhere I
> > have tried it) and the bisection is showing that it appears to have been
> > broken before -rc1.
>
> Are you booting a generic kernel, or a zx1_defconfig based one? Look
My config is a custom config based on the RHEL/Fedora builds.
> back in the linux-ia64 archives a few days for a post titled:
>
> "Regression in serial console on ia64 after 2.6.22"
>
> Perhaps you are hitting this?
I don't think I am seeing the same thing. My console is OK, it just
panics. I had suspected that same patch mentioned in the post you point
to as a possible culprit but backing it out did not appear to fix my
issue.
Also, I am not passing any console= arg to the kernel and letting it
automagically determine the right thing (which is still working).
In fact I am not passing _any_ args to the kernel. perhaps that is the
difference?
- Doug
next prev parent reply other threads:[~2007-07-23 23:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 13:41 Linus' tree broken? Jes Sorensen
2007-07-23 16:05 ` Luck, Tony
2007-07-23 16:32 ` Jes Sorensen
2007-07-23 17:00 ` Luck, Tony
2007-07-23 17:21 ` Doug Chapman
2007-07-23 17:40 ` Luck, Tony
2007-07-23 17:47 ` Len Brown
2007-07-23 20:22 ` Jes Sorensen
2007-07-23 20:39 ` Doug Chapman
2007-07-23 20:42 ` Luck, Tony
2007-07-23 21:03 ` Russ Anderson
2007-07-23 21:17 ` Peter Chubb
2007-07-23 22:24 ` Doug Chapman
2007-07-23 22:42 ` Luck, Tony
2007-07-23 23:07 ` Doug Chapman [this message]
2007-07-24 8:30 ` Jes Sorensen
2007-07-24 8:50 ` Jes Sorensen
2007-07-24 23:21 ` Russ Anderson
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=1185232076.7158.56.camel@dchapman.boston.redhat.com \
--to=doug.chapman@hp.com \
--cc=linux-ia64@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