From: Pavel Machek <pavel@ucw.cz>
To: Daniel Ribeiro <drwyrm@gmail.com>
Cc: Eric Miao <eric.y.miao@gmail.com>,
rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>,
Dirk@opfer-online.de, arminlitzel@web.de,
Cyril Hrubis <metan@ucw.cz>,
thommycheck@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
dbaryshkov@gmail.com, omegamoon@gmail.com
Subject: Re: 2.6.30-rc1: touchscreen BUG() on spitz
Date: Fri, 10 Apr 2009 18:29:15 +0200 [thread overview]
Message-ID: <20090410162915.GA27805@elf.ucw.cz> (raw)
In-Reply-To: <1239360967.14324.2.camel@brutus>
Hi!
> > > After update to 2.6.30-rc1, sharp zaurus c-3000 fails to boot with
> > > white screen (with stripes). That's a regression w.r.t. 2.6.29.
> >
> > What kind of white stripes? Does it look like the LCD controller
> > stops working or something.
> >
> > There is a regression which caused X server hang during bootup,
> > with commit id 66c1ca0, which you can revert and have another
> > try.
>
> As spitz also use cs_control for pxa2xx_spi, i believe that this is the
> same issue i found wednesday.
>
> See the "Kernel freeze caused by
> a7bb3909b3293d503211d7f6af8ed62c1644b686" thread.
Ok, I'll try changing ASSERT->DEASSERT and see what happens. Hmm, it
now boots, with these messages:
WARNING: at kernel/irq/handle.c:366
BUG: IRQ handler called from non-hardirq context!
just after loading touchscreen device.
Thanks!
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-04-10 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 10:34 2.6.30-rc1: white screen during boot (regression) " Pavel Machek
2009-04-10 10:50 ` Eric Miao
2009-04-10 10:56 ` Daniel Ribeiro
2009-04-10 16:29 ` Pavel Machek [this message]
2009-04-10 19:35 ` 2.6.30-rc1: touchscreen BUG() " Dmitry Eremin-Solenikov
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=20090410162915.GA27805@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Dirk@opfer-online.de \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=drwyrm@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.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®