From: Daniel Walker <dwalker@codeaurora.org>
To: Tomasz Sterna <tomek@xiaoka.com>
Cc: linux-arm-msm@vger.kernel.org, Bradley Smith <brad@brad-smith.co.uk>
Subject: Re: [PATCH] [Streak] Add workaround for TTY kernel OOPS at the cost of performance.
Date: Fri, 01 Oct 2010 08:47:26 -0700 [thread overview]
Message-ID: <1285948046.22265.12.camel@m0nster> (raw)
In-Reply-To: <1285923176.16981.53.camel@ubuntu>
On Fri, 2010-10-01 at 10:52 +0200, Tomasz Sterna wrote:
> If you start an android-msm-2.6.29 or msm-2.6.35 (these are the ones I
> tested) with MSM_FB driver compiled in and use 'console=tty' kernel
> commandline option, kernel starts with proper console output on screen
> and oopses in the middle of the process.
> I don't know the exact nature of the problem. Maybe Brad would shed some
> light.
>
> If you're unable to reproduce the problem, I will rebuild the kernel
> without the workaround and retype the OOPS message for you.
I don't have access to Streak hardware, and I've not talked to anyone
that does. But if you give us the OOPS message we can try to figure out
what's going on..
BTW did Dell release a kernel for Streak? They might already have a
workaround in their kernel.
Daniel
--
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum.
next prev parent reply other threads:[~2010-10-01 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 22:42 [PATCH] [Streak] Add workaround for TTY kernel OOPS at the cost of performance Tomasz Sterna
2010-09-30 23:04 ` Daniel Walker
2010-10-01 8:52 ` Tomasz Sterna
2010-10-01 15:47 ` Daniel Walker [this message]
2010-10-01 20:07 ` Tomasz Sterna
2010-10-02 0:26 ` Daniel Walker
2010-10-01 21:11 ` Tomasz Sterna
[not found] ` <AANLkTimVpsmWLpXwuLyFgC3sOSMVCbF38DNRL13_5bgk@mail.gmail.com>
2010-10-02 10:14 ` Bradley Smith
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=1285948046.22265.12.camel@m0nster \
--to=dwalker@codeaurora.org \
--cc=brad@brad-smith.co.uk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=tomek@xiaoka.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