2.6.30-rc1: white screen during boot (regression) on spitz

2.6.30-rc1: white screen during boot (regression) on spitz

[Pavel Machek]

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.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: 2.6.30-rc1: white screen during boot (regression) on spitz

[Eric Miao]

On Fri, Apr 10, 2009 at 6:34 PM, Pavel Machek <pavel@ucw.cz> wrote:
> 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.

>                                                                        Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>



-- 
Cheers
- eric

Re: 2.6.30-rc1: white screen during boot (regression) on spitz

[Daniel Ribeiro]

Em Sex, 2009-04-10 às 18:50 +0800, Eric Miao escreveu:
> On Fri, Apr 10, 2009 at 6:34 PM, Pavel Machek <pavel@ucw.cz> wrote:
> > 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.

-- 
Daniel Ribeiro

Re: 2.6.30-rc1: touchscreen BUG() on spitz

[Pavel Machek]

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

Re: 2.6.30-rc1: touchscreen BUG() on spitz

[Dmitry Eremin-Solenikov]

2009/4/10 Pavel Machek <pavel@ucw.cz>:
> 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.

Try reverting 044d408409cc4e1bc75c886e27ca85c270db104c as
software resent IRQs are sent from tasklet context, not from hardirq.

-- 
With best wishes
Dmitry