public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Peter Tseng <tsenpet09@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: linux-omap-pm troubles on Gumstix Overo
Date: Wed, 07 Apr 2010 15:01:50 -0700	[thread overview]
Message-ID: <87ochuapm9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <87tyrnfe8c.fsf@deeprootsystems.com> (Kevin Hilman's message of "Wed\, 07 Apr 2010 08\:56\:35 -0700")

Kevin Hilman <khilman@deeprootsystems.com> writes:

> Peter Tseng <tsenpet09@gmail.com> writes:
>
>> Hey there,
>>
>> My name's Peter and I'm working with the linux-omap-pm kernel on the
>> Gumstix Overo board for an academic project.
>>
>> Back when the linux-omap-pm branch was still on 2.6.33-rc8, I could
>> compile and run the kernel on the Overo without any problems. Suspend to
>> memory (via mem > /sys/power/state) worked just fine. Unfortunately,
>> ever since 2.6.34-rcX releases started coming out, I have been running
>> into problems:
>>

[...]

>>
>> I have no idea if it simply hangs here, or it is working and simply not
>> printing anything to the serial console. (If it helps at all, the
>> processor *seems* warm, but I cannot be sure of this).
>
> What's your commandline?
>
> Can you try enabling CONFIG_DEBUG_LL=y and and CONFIG_EARLY_PRINTK=y
> and append 'earlyprintk' on the kernel command line.
>
> This will hopefully give more detailed reasons for the dump.
>
> I seem to have corrupted the flash on my overo so it's not booting
> currently, but the current PM branch kernel does boot fine on my
> beagle C3.

OK, after some more digging, the Overo was hitting the same boot
problem I've been trying to track on Zoom3.  I have now fixed this and
the PM branch omap3_pm_defconfig should boot again for Overo and
Zoom3.

I've updated the PM branch now which includes a fix for a problem
introduced in in 2.6.34 due to early enabling of interrupts (see
details on LKML[1]).  Interstingly, this was seen on PM branch where I
use the SLUB allocator by default, and not on l-o master where the
SLAB allocator is still used by default.

Please pull a fresh PM branch and see if you get it booting on Overo.

Thanks,

Kevin


[1] http://lkml.org/lkml/2010/4/7/301

  parent reply	other threads:[~2010-04-07 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07  3:12 linux-omap-pm troubles on Gumstix Overo Peter Tseng
2010-04-07 15:56 ` Kevin Hilman
2010-04-07 16:04   ` Kevin Hilman
2010-04-07 22:01   ` Kevin Hilman [this message]
2010-04-08  0:12     ` Peter Tseng
2010-04-08 17:15       ` Kevin Hilman
2010-04-08 19:11         ` Kevin Hilman

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=87ochuapm9.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tsenpet09@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