From: Jan Kiszka <jan.kiszka@domain.hid>
To: Chris Cole <clecol@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] bug: patch support for intel atom n270
Date: Thu, 18 Feb 2010 10:23:31 +0100 [thread overview]
Message-ID: <4B7D0713.5080602@domain.hid> (raw)
In-Reply-To: <4B7AEF36.6030304@domain.hid>
Chris Cole wrote:
> Jan Kiszka wrote:
>> Jan Kiszka wrote:
>>
>>> Chris Cole wrote:
>>>
>>>>> Also, I realize that the patch / kernels do not match up 100%
>>>>> (although the patch applied successfully),
>>>>> so I'm trying that same patch on 2.6.32.7 now to see if I get the
>>>>> same behavior.
>>>>>
>>>>> Chris
>>>>>
>>>>>
>>>> Indeed, with the adeos patch for 2.6.32.7 and a vanilla 2.6.32.7, my
>>>> system is un-bootable. Is there
>>>> anything I can do to debug it? I'd be willing to help get a fix out
>>>> but I'm not really sure where to
>>>> look.
>>>>
>>> Let's start with looking at and playing with .configs. Could you provide
>>> yours?
>>>
>>
>> Also interesting: What does "unbootable" mean? Where does it hang, what
>> is dumped to the serial kernel console up to that point?
>>
>>
> Jan,
> My config is attached, and by "unbootable" I mean, it says something like
> "Booting the kernel" and then just hangs.
For the time being, you could retry with CONFIG_M586TSC or better.
Adjusting the CPU type is recommended anyway to avoid using legacy
PIC/PIT. And please attach a serial cable and enable console=ttyS0
(maybe even earlycon) so that we get more info about your failing boot.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2010-02-18 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 19:31 [Adeos-main] bug: patch support for intel atom n270 Chris Cole
2010-02-15 19:48 ` Philippe Gerum
2010-02-15 21:15 ` Chris Cole
2010-02-16 14:03 ` Chris Cole
2010-02-16 15:13 ` Chris Cole
2010-02-16 16:27 ` Jan Kiszka
2010-02-16 16:48 ` Jan Kiszka
2010-02-16 19:17 ` Chris Cole
2010-02-18 9:23 ` Jan Kiszka [this message]
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=4B7D0713.5080602@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--cc=clecol@domain.hid \
/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.