The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH RT] kstopmachine has legit preempt_enable_no_resched (was: 2.6.15-rt12 bugs)
Date: Tue, 24 Jan 2006 16:37:47 +0100	[thread overview]
Message-ID: <6bffcb0e0601240737u3e77245g@mail.gmail.com> (raw)
In-Reply-To: <1138112388.6695.26.camel@localhost.localdomain>

Hi,

On 24/01/06, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 2006-01-24 at 14:33 +0100, Michal Piotrowski wrote:
[snip]
> > And problems while loading ipv6 module
> > Running ntpdate to synchronize clockCould not allocate 4 bytes percpu data
> > modprobe: FATAL: Error inserting ipv6
> > (/lib/modules/2.6.15-rt14/kernel/net/ipv6/ipv6.ko): Cannot allocate
> > memory
> >
> > Could not allocate 4 bytes percpu data
> > modprobe: FATAL: Error inserting ipv6
> > (/lib/modules/2.6.15-rt14/kernel/net/ipv6/ipv6.ko): Cannot allocate
> > memory
>
> Is this new with the -rt14? or has this happened before. If it has
> happened before, then could you tell us when it started.

It's very hard to track down, because earlier versions of -rt ware too
buggy for me and most of them doesn't compile/boot.

Regards,
Michal Piotrowski

  reply	other threads:[~2006-01-24 15:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 13:21 2.6.15-rt12 bugs Michal Piotrowski
2006-01-24  0:24 ` Steven Rostedt
2006-01-24  1:23 ` [PATCH RT] kstopmachine has legit preempt_enable_no_resched (was: 2.6.15-rt12 bugs) Steven Rostedt
2006-01-24  7:45   ` Ingo Molnar
2006-01-24 13:33   ` Michal Piotrowski
2006-01-24 14:19     ` Steven Rostedt
2006-01-24 15:37       ` Michal Piotrowski [this message]
2006-01-24 18:11         ` Steven Rostedt
2006-01-24 21:00           ` Michal Piotrowski
2006-01-24 21:17             ` Steven Rostedt
2006-01-26 17:47               ` Michal Piotrowski

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=6bffcb0e0601240737u3e77245g@mail.gmail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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