From: kevin diggs <diggskevin38@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: BootX
Date: Mon, 24 Jan 2011 11:51:23 -0600 [thread overview]
Message-ID: <AANLkTinOz+5YAGzuB_SYAAoX2oYq92FJDc0qw90KL=4z@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim6v25Sam+E8Bo9za1q0GJqWZitgqR0KBuKCoWz@mail.gmail.com>
Hi,
I've never done any real kernel debugging. Can anyone give any
pointers on how to do early boot debugging on an old world (buggy OF)
powermac? Can I do anything using a serial console?
A little reading last night suggested that spinlocks are supposed to
disappear for single processor machines. I do not understand why they
are present in 3.4.6 (at least the symbol anyway)? The 'acct_lock'
spin lock was also missing with gcc 4.2.4.
kevin
On Sat, Jan 22, 2011 at 12:24 PM, kevin diggs <diggskevin38@gmail.com> wrote:
> Hi,
>
> If I enable SMP then I can build a 2.6.28 kernel with gcc 4.3.5 that
> WILL boot on the PowerMac8600 (single 750GX). The previously mentioned
> G4 that runs is a dual cpu beast and thus also runs SMP.
>
> I at least know this (ok, I THINK I know):
>
> For non-SMP: The spinlock 'acct_lock' in kernel/acct.c that IS
> present in 3.4.6 (i.e. kernel 2.6.28 compiled with gcc 3.4.6). Not so
> much for 4.3.5. I have not yet done a general 4.3.5 compiled 2.6.28
> spinlock safari.
>
> Don't some funky, optimizery things happen to spinlocks for the NON-smp case?
>
> I'll see what the 4.2.x gcc does.
>
> Thanks!
>
> kevin
>
> P.S.: There is one other difference for the SMP 4.3.5 compiled
> 2.6.28: my 750gx cpufreq driver gets disabled. It is fairly isolated
> code though. Should not be able to nuke the spinlock in kernel/acct.c
>
> On Fri, Jan 21, 2011 at 1:26 PM, kevin diggs <diggskevin38@gmail.com> wrote:
>> Hi,
>>
>> Anyone familiar with BootX? Could my problems with the 8600 be related
>> to some interaction with BootX?
>>
>> kevin
>>
>
next prev parent reply other threads:[~2011-01-24 17:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 19:26 BootX kevin diggs
2011-01-21 21:21 ` BootX Benjamin Herrenschmidt
2011-01-22 1:48 ` BootX kevin diggs
2011-01-22 1:49 ` BootX Benjamin Herrenschmidt
2011-01-22 1:50 ` BootX Benjamin Herrenschmidt
2011-01-22 2:03 ` BootX kevin diggs
2011-01-22 2:31 ` BootX Benjamin Herrenschmidt
2011-01-22 18:24 ` BootX kevin diggs
2011-01-24 17:51 ` kevin diggs [this message]
2011-01-25 4:01 ` BootX kevin diggs
2011-02-02 19:36 ` BootX kevin diggs
2011-02-02 21:40 ` BootX Benjamin Herrenschmidt
2011-02-02 21:55 ` BootX kevin diggs
2011-02-02 22:09 ` BootX kevin diggs
2011-02-02 22:29 ` BootX Benjamin Herrenschmidt
2011-02-04 17:21 ` BootX kevin diggs
2011-02-04 20:47 ` BootX Benjamin Herrenschmidt
2011-02-11 19:16 ` BootX kevin diggs
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='AANLkTinOz+5YAGzuB_SYAAoX2oYq92FJDc0qw90KL=4z@mail.gmail.com' \
--to=diggskevin38@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).