From: Kumar Gala <galak@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: rmk+kernel@arm.linux.org.uk, LKML List <linux-kernel@vger.kernel.org>
Subject: Re: 8250 serial console fixes -- issue
Date: Thu, 2 Feb 2006 11:10:38 -0600 [thread overview]
Message-ID: <7A548B5C-4473-4786-93FF-BBAFADA906F8@kernel.crashing.org> (raw)
In-Reply-To: <6E8F349B-CD5A-473E-A2E1-21CFD949E83E@kernel.crashing.org>
On Feb 2, 2006, at 2:05 AM, Kumar Gala wrote:
>
> On Feb 1, 2006, at 11:54 PM, Kumar Gala wrote:
>
>>
>> On Feb 1, 2006, at 7:47 PM, Alan Cox wrote:
>>
>>> On Mer, 2006-02-01 at 19:21 -0600, Kumar Gala wrote:
>>>> This patch introduces an issue for me an embedded PowerPC SoC
>>>> using the
>>>> 8250 driver.
>>>>
>>>> The simple description of my issue is this: I'm using the
>>>> serial port for
>>>> both a terminal and console. I run fdisk on a /dev/hda. Before
>>>> this
>>>> patch I would get the prompt for fdisk immediately. After this
>>>> patch I
>>>> have to hit return before the prompt is displayed.
>>>>
>>>> I know that's not a lot of info, but just let me know what else
>>>> you need
>>>> to help debug this.
>>>>
>>>> I'm guessing something about the UARTs on the PowerPC maybe bit
>>>> a little
>>>> non-standard.
>>>
>>> I wonder if I've swapped one race for another. Can you revert
>>> just the
>>> line which forces THRI on and test with the rest of the change
>>> please.
>>
>> This doesn't seem to help.
>
> I realized a bit later that the kernel I build with your suggested
> change wasn't the one I was testing. After loading the proper
> kernel this does make the issue I was seeing go away.
After some further testing with this change, the majority of issues I
was seeing go away. However, able to lock the console up. If I
revert the wait_for_xmitr() to always use BOTH_EMPTY the lock up goes
away. (Obviously, this is effectively reverting the whole patch).
- kumar
next prev parent reply other threads:[~2006-02-02 17:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 1:21 Kumar Gala
2006-02-02 1:47 ` Alan Cox
2006-02-02 5:54 ` Kumar Gala
2006-02-02 8:05 ` Kumar Gala
2006-02-02 17:10 ` Kumar Gala [this message]
2006-02-03 1:58 ` Glen Turner
2006-02-03 9:40 ` Russell King
2006-02-03 14:27 ` Glen Turner
2006-02-03 16:02 ` Russell King
2006-02-03 17:08 ` Glen Turner
2006-02-03 22:23 ` Russell King
2006-02-04 11:15 ` Russell King
2006-02-04 16:18 ` Krzysztof Halasa
2006-02-04 23:16 ` Russell King
2006-02-04 23:54 ` Krzysztof Halasa
2006-02-05 0:00 ` Russell King
2006-02-05 12:57 ` Krzysztof Halasa
2006-02-03 17:46 ` Krzysztof Halasa
2006-02-03 22:13 ` Russell King
2006-02-04 16:08 ` Krzysztof Halasa
2006-02-04 23:20 ` Russell King
2006-02-05 3:12 ` Glen Turner
2006-02-05 21:26 ` Krzysztof Halasa
2006-02-06 9:47 ` Russell King
2006-02-07 3:27 ` Glen Turner
2006-02-03 15:05 ` Kumar Gala
2006-02-06 20:26 ` Pavel Machek
2006-02-06 20:55 ` Russell King
2006-02-07 4:00 ` Glen Turner
2006-02-07 9:18 ` Pavel Machek
2006-02-07 17:43 ` Russell King
2006-02-07 22:23 ` Krzysztof Halasa
2006-02-08 0:59 ` Junio C Hamano
2006-02-08 1:19 ` Lee Revell
2006-02-03 10:00 linux
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=7A548B5C-4473-4786-93FF-BBAFADA906F8@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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®