From: Heikki Lindholm <holindho@domain.hid>
To: Philippe Gerum <philippe.gerum@domain.hid>
Cc: Stelian Pop <stelian@domain.hid>, adeos-main@gna.org
Subject: Re: [Adeos-main] adeos i386 and ppc patches forward ported to 2.6.13
Date: Sun, 04 Sep 2005 09:41:24 +0300 [thread overview]
Message-ID: <431A9714.6030809@domain.hid> (raw)
In-Reply-To: <20050901164619.pn5h4cg34s0w4gok@domain.hid>
Philippe Gerum kirjoitti:
> Quoting Stelian Pop <stelian@domain.hid>:
>
>> Le jeudi 01 septembre 2005 à 15:52 +0200, Philippe Gerum a écrit :
>>
>>> >> Are you sure this is not the same I was experiencing, eg. missed
>>> >> decrementer interrupt that stalls the machine (looks like hard
>>> lock-up)
>>> >> for two minutes.
>>> >
>>> > I tried waiting (at least 5 minutes) and nothing happened.
>>> >
>>>
>>> Here is a revisited version of Heikki's patch applicable against an
>>> Adeos-patched kernel, and which is expected to solve the lagging
>>> interrupt sync
>>> issue; tested on a mpc8541 board. I'd be interested to know if this
>>> still fixes
>>> the issue discovered on ppc64, and maybe on the G4.
>>
>>
>> Does not change a thing on the G4.
>>
>
> Of, so if Heikki confirms that this patch works on ppc64, I guess that
> we have a
> brand new shiny bug to chase, with lots of headbanging sessions ahead.
> And I'm
> not talking about dance style here...
I've now tried both 32- and 64-bit kernels on the G5 with and without
the patch and the results seem consistent with the G4. Without the
patch, stalls happen always with nucleus loaded, but I didn't observe
any with the patch. However, I'm still not happy with how the patch
handles the !threaded case: If everyone had handlers like
my_handler(...);
{
traps++;
return PROPAGATE;
}
the patch wouldn't help at all. I'd prefer something more along the
lines of my original posting.
-- Heikki Lindholm
next prev parent reply other threads:[~2005-09-04 6:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 13:40 [Adeos-main] adeos i386 and ppc patches forward ported to 2.6.13 Stelian Pop
2005-08-31 17:37 ` Philippe Gerum
2005-08-31 21:14 ` Stelian Pop
2005-09-01 8:47 ` Philippe Gerum
2005-09-01 12:20 ` Stelian Pop
2005-09-01 12:44 ` Philippe Gerum
2005-09-01 12:47 ` Stelian Pop
2005-09-01 13:03 ` Stelian Pop
2005-09-01 13:09 ` Heikki Lindholm
2005-09-01 13:30 ` Stelian Pop
2005-09-01 13:52 ` Philippe Gerum
2005-09-01 14:12 ` Stelian Pop
2005-09-01 14:46 ` Philippe Gerum
2005-09-01 14:49 ` Stelian Pop
2005-09-03 6:47 ` Heikki Lindholm
2005-09-03 21:09 ` Stelian Pop
2005-09-04 6:41 ` Heikki Lindholm [this message]
2005-09-04 6:46 ` Heikki Lindholm
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=431A9714.6030809@domain.hid \
--to=holindho@domain.hid \
--cc=adeos-main@gna.org \
--cc=philippe.gerum@domain.hid \
--cc=stelian@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.