SUPERH platform development
 help / color / mirror / Atom feed
From: Cao Minh Hiep <cm-hiep@jinso.co.jp>
To: linux-sh@vger.kernel.org
Subject: Re: Can't boot kernel v4.0-rc2 on Koelsch
Date: Tue, 10 Mar 2015 09:03:15 +0000	[thread overview]
Message-ID: <54FEB353.8090005@jinso.co.jp> (raw)
In-Reply-To: <2263226.JPOqZgiCRj@avalon>

Hi Nobuhiro-san

On 2015年03月10日 17:05, Nobuhiro Iwamatsu wrote:
> Hi, all.
>
> This is user land issue.
> Hiep, if you have not changed ttySCX in inittab, you will need to change.
> Could you check your inittab?
>
> --- a/inittab    2015-03-10 15:01:58.986609389 +0900
> +++ b/inittab    2015-03-10 15:00:32.132094877 +0900
> @@ -28,7 +28,7 @@
>   l6:6:wait:/etc/init.d/rc 6
>   # Normally not reached, but fallthrough in case of emergency.
>   z6:6:respawn:/sbin/sulogin
> -SC6:12345:respawn:/sbin/getty -L 38400 ttySC6
> +SC0:12345:respawn:/sbin/getty -L 38400 ttySC0
>   # /sbin/getty invocations for the runlevels.
>   #
>   # The "id" field MUST be the same as the last
There is no inittab file in Linaro userland that I am using.
But I tried to change it in Yocto. Then I can boot my boards well.

Best Regards,
Hiep.

> Best regards,
>    Nobuhiro
>
> 2015-03-10 8:49 GMT+09:00 Laurent Pinchart <laurent.pinchart@ideasonboard.com>:
>> Hello Hiep-san,
>>
>> (CC'ing Geert)
>>
>> On Monday 09 March 2015 18:43:54 Cao Minh Hiep wrote:
>>> On 2015年03月09日 16:06, Laurent Pinchart wrote:
>>>> On Monday 09 March 2015 10:07:04 Cao Minh Hiep wrote:
>>>>> Hi Laurent-san
>>>>>
>>>>> I am Hiep from Jinzai Solution.
>>>>> I'm sorry to bother you again!
>>>> No worries.
>>>>
>>>>> We are testing the linux ver v4.0-rc2 on Koelsch, We can not boot the
>>>>> kernel v4.0-rc2 on Koelsch,
>>>>> Then we found a patch has changed as below:
>>>>> "1f75cda ARM: shmobile: koelsch: Rename SCIF[01] serial ports to
>>>>> ttySC[01]"
>>>>>
>>>>> Please see it when you have time!
>>>> Could you please detail your boot failure ? You might need to change your
>>>> /etc/inittab to adjust to the serial port new name, but apart from that
>>>> there shouldn't be any issue. I can boot my Koelsch board on 4.0-v2.
>>> Sure, I use the rootfs of Linaro-nano 2014.09 to test v4.0-rc2.
>>> When booting kernel with default config, bootlogs showed until these
>>> messages appearing.
>>> "init: auto-serial-console main process ended, respawning
>>> init: auto-serial-console main process ended, respawning
>>> init: auto-serial-console main process ended, respawning
>>> init: tty1 main process (1449) killed by TERM signal
>>> init: auto-serial-console respawning too fast, stopped"
>>>
>>> Then, my Koelsch board stoped here.(my Lager board is the same)
>>> (I attached the bootlogs_file)
>>>
>>> So, When I tried to add "console=ttySC0," into bootargs (at .dts file),
>>> i can boot my Koelsch board without any problems.
>>> And these are the same on Lager board.
>> Thank you for the information.
>>
>> Geert, it looks like the console= kernel command line argument is used by
>> userspace to figure out the console device on which to spawn a terminal. What
>> would you think about adding it back ?
>>
>>> Thank you!
>>> Jinso/Hiep
>>> ====>>> information:
>>> Actually, on v4.0-rc2, we have two patches related each other as below:
>>> 79e69d1 ARM: shmobile: koelsch dts:Drop console= bootargs parameter BAD.
>>> 1f75cda ARM: shmobile: koelsch: Rename SCIF01 serial ports to ttySC01
>>>
>>> And for Lager:
>>> 569dd56 ARM: shmobile: lager dts: Drop console= bootargs parameter
>>> 78c11ec ARM: shmobile: lager: Rename SCIFA[01] serial ports to ttySC[01]
>>>
>>> There is only 79e69d1 patch on v3.19-rcX, I also had a problem with
>>> bootting Koelsch on v3.19-rcX
>>> (using linaro-nano 2014.09). But it was good on Yocto and
>>> linaro-nano-2013.02
>> --
>> Regards,
>>
>> Laurent Pinchart
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>


  parent reply	other threads:[~2015-03-10  9:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09  7:06 Can't boot kernel v4.0-rc2 on Koelsch Laurent Pinchart
2015-03-09  9:43 ` Cao Minh Hiep
2015-03-09 23:49 ` Laurent Pinchart
2015-03-10  1:14 ` Simon Horman
2015-03-10  1:53 ` Cao Minh Hiep
2015-03-10  4:14 ` Simon Horman
2015-03-10  8:05 ` Nobuhiro Iwamatsu
2015-03-10  8:38 ` Cao Minh Hiep
2015-03-10  9:03 ` Cao Minh Hiep [this message]
2015-03-10 11:32 ` Geert Uytterhoeven
2015-03-11  0:01 ` Simon Horman
2015-03-11  4:51 ` Cao Minh Hiep
2015-03-11  6:45 ` Laurent Pinchart
2015-03-11 15:56 ` Ben Hutchings

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=54FEB353.8090005@jinso.co.jp \
    --to=cm-hiep@jinso.co.jp \
    --cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox