mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: seriel console support broken in -mm4 and -mm5
Date: Wed, 31 Mar 2004 08:17:03 -0800	[thread overview]
Message-ID: <37860000.1080749822@[10.10.2.4]> (raw)
In-Reply-To: <20040329112856.0b103c66.akpm@osdl.org>

>> > It works fine in -rc2.
>> > 
>> > -mm4 prints jibberish (wrong speed / settings?) for serial console, but
>> > the getty stuff comes out file. shutdown just prints more jibberish.
>> > 
>> > -mm5 prints about half as much jibberish as -mm4 then hangs, seemingly
>> > halfway through boot.
>> > 
>> > I guess I'll try linus.patch from -mm4 next, unless you have any other
>> > suggestions that'd be more fruitful ...
>> 
>> OK, so -mm5 actually does the same as mm4 on my second try, so maybe the
>> hang is intermittent, or something.
>> 
>> However, linus.patch from -mm4 works fine, so the culprit is one of the
>> other patches in your tree ... any suggestions for which to shoot first? ;-)
>> 
> 
> Not really.  Are you using early printk?
> 
> The only patches I have which touch drivers/serial/ are
> 8250-resource-management-fix, linus, pmac_zilog-oops-fix, kgdb-ga.
> 
> Lots of patches against drivers/char/*, but I don't see how any of those
> can futz the serial settings.  I'm assuming you're using 8250?

Sometimes my own idleness saves my arse. I finally got around to debugging
it, and it's gone in rc3-mm2 ;-) Yes, was 8250 ...

Thanks,

M



      reply	other threads:[~2004-03-31 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 18:00 Martin J. Bligh
2004-03-29 18:25 ` Martin J. Bligh
2004-03-29 19:28   ` Andrew Morton
2004-03-31 16:17     ` Martin J. Bligh [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='37860000.1080749822@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=akpm@osdl.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

all inboxes | Powered by JetHome®