From: Andrew Morton <akpm@osdl.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: seriel console support broken in -mm4 and -mm5
Date: Mon, 29 Mar 2004 11:28:56 -0800 [thread overview]
Message-ID: <20040329112856.0b103c66.akpm@osdl.org> (raw)
In-Reply-To: <190920000.1080584708@[10.10.2.4]>
"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> > 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?
drivers/char/cyclades.c~linus
drivers/char/efirtc.c~linus
drivers/char/istallion.c~bk-driver-core
drivers/char/Kconfig~kconfig-url-fixes
drivers/char/keyboard.c~kgdb-ga
drivers/char/mem.c~get_user_pages-handle-VM_IO
drivers/char/mem.c~linus
drivers/char/n_tty.c~move-job-control-stuff-tosignal_struct
drivers/char/random.c~urandom-scalability-fix
drivers/char/rocket.c~move-job-control-stuff-tosignal_struct
drivers/char/rtc.c~linus
drivers/char/sn_serial.c~linus
drivers/char/sonypi.h~linus
drivers/char/stallion.c~bk-driver-core
drivers/char/sx.c~move-job-control-stuff-tosignal_struct
drivers/char/sysrq.c~kgdb-ga
drivers/char/tipar.c~bk-driver-core
drivers/char/tpqic02.c~bk-driver-core
drivers/char/tty_io.c~move-job-control-stuff-tosignal_struct
drivers/char/tty_io.c~remove-down_tty_sem
drivers/char/tty_io.c~tty-locking-again
drivers/char/vc_screen.c~bk-driver-core
drivers/char/viocons.c~linus
drivers/char/viotape.c~linus
drivers/char/vt.c~bk-driver-core
drivers/char/vt.c~con_open-speedup
drivers/char/vt.c~linus
drivers/char/vt.c~move-job-control-stuff-tosignal_struct
drivers/char/vt.c~vt-cleanup
drivers/char/vt_ioctl.c~move-job-control-stuff-tosignal_struct
next prev parent reply other threads:[~2004-03-29 19:29 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 [this message]
2004-03-31 16:17 ` Martin J. Bligh
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=20040329112856.0b103c66.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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®