All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
Cc: Mikhail Goryunov
	<gormih78-o+MxOtu4lMCHXe+LvDLADg@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: upstream kernel 3.8.5: tegra_defconfig not working on Seco QSeven QuadMo747-X/T20
Date: Thu, 11 Apr 2013 09:26:43 -0600	[thread overview]
Message-ID: <5166D633.8060308@wwwdotorg.org> (raw)
In-Reply-To: <1365687847.1938.1.camel@antimon>

On 04/11/2013 07:44 AM, Lucas Stach wrote:
> Am Donnerstag, den 11.04.2013, 16:15 +0400 schrieb Mikhail Goryunov:
>> When building the kernel with the option tegra_defconfig loading occurs in the following way:
>> Loading file "/boot/boot.scr" from usb device 0:1 (usbda1)
>> 319 bytes read
>> ## Executing script at 00408000
>> USB boot...
>> Loading file "/boot/uImage" from usb device 0:1 (usbda1)
>> 3733096 bytes read
>> ## Booting kernel from Legacy Image at 04080000 ...
>>    Image Name:   Linux-3.8.5
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    3733032 Bytes = 3.6 MiB
>>    Load Address: 00008000
>>    Entry Point:  00008000
>>    Verifying Checksum ... OK
>>    Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>>
>> and system freezes
> 
> ... You may also want to enable the
> earlyconsole support in kernel to see if it comes up at all.

i.e. enable the following Kconfig options:

CONFIG_DEBUG_LL=y
CONFIG_EARLY_PRINTK=y
CONFIG_TEGRA_DEBUG_UART_XXX=y

(where XXX above is the serial port you're using; look in menuconfig)

and add "earlyprintk" to the kernel command-line. That should hopefully
show the cause of the crash/hang.

BTW, what is your kernel command-line?

  reply	other threads:[~2013-04-11 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 12:15 upstream kernel 3.8.5: tegra_defconfig not working on Seco QSeven QuadMo747-X/T20 Mikhail Goryunov
     [not found] ` <1039301365682542-0lqHHmzNcNNxpj1cXAZ9Bg@public.gmane.org>
2013-04-11 13:44   ` Lucas Stach
2013-04-11 15:26     ` Stephen Warren [this message]
     [not found]       ` <5166D633.8060308-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-04-12  7:18         ` Mikhail Goryunov
     [not found]           ` <1688621365751094-5488f72fhnJxpj1cXAZ9Bg@public.gmane.org>
2013-04-12 15:31             ` Stephen Warren
     [not found]               ` <516828ED.4090403-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-04-18 13:24                 ` Mikhail Goryunov

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=5166D633.8060308@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org \
    --cc=gormih78-o+MxOtu4lMCHXe+LvDLADg@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.