public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin Mattock" <justinmattock@gmail.com>
To: "Bernard Pidoux" <bpidoux@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: spinlock lockup on CPU#0
Date: Sun, 27 Apr 2008 02:00:47 +0000	[thread overview]
Message-ID: <dd18b0c30804261900m1a2edebld6a796e1de85c19e@mail.gmail.com> (raw)
In-Reply-To: <200804270215.23739.bpidoux@free.fr>

On Sun, Apr 27, 2008 at 12:15 AM, Bernard Pidoux <bpidoux@free.fr> wrote:
> Hi,
>
>  cpu_idle bug is also present in 2.6.24.4 kernel.
>
>  I hope this helps.
>
>  Bernard Pidoux
>
>
>
>
>

Cool, you're welcome.
I've just pulled the latest update and rebooted, eveything looks good
except for my wireless
just spent two hours trying to tweak it to go, but can't figure out
what is happening
madwifi is   giving me a *** TARGET i386-elf is invalid.
aside from that is there a patch for athk5 for the macbook's?
if not, thats O.K. I'm going to have a look into what I might have
wrong on my part maybee (make) is too old.
regards;

-- 
Justin P. Mattock

  reply	other threads:[~2008-04-27  2:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 21:33 spinlock lockup on CPU#0 Bernard Pidoux
2008-04-27  0:15 ` Bernard Pidoux
2008-04-27  2:00   ` Justin Mattock [this message]
2008-04-27  2:13     ` Bob Copeland
2008-04-27  2:20       ` Justin Mattock
2008-04-27  2:41         ` Bob Copeland
2008-04-27  6:11           ` Justin Mattock
  -- strict thread matches above, loose matches on Subject: below --
2008-04-24  1:41 Justin Mattock
2008-04-26 18:29 ` Andrew Morton
2008-04-26 18:39   ` Justin Mattock
2008-04-26 19:14   ` Ingo Molnar
2008-04-26 19:32     ` Justin Mattock
2008-04-26 21:06     ` Bob Copeland
2008-04-26 21:48       ` Justin Mattock
2008-04-28 20:38         ` Venki Pallipadi
2008-04-28 22:02           ` Justin Mattock
2008-04-26 23:04     ` Hugh Dickins

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=dd18b0c30804261900m1a2edebld6a796e1de85c19e@mail.gmail.com \
    --to=justinmattock@gmail.com \
    --cc=bpidoux@free.fr \
    --cc=linux-kernel@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