[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: [rtl] RTL2.0 experiences
yodaiken@fsmlabs.com wrote:
> > When "insmod"ing the 3dfx-Modul, the machine crashes with
> >
> > >>>>
> > Kernel panic: nmi!
>
> Are you using the frightful 2.2.14 ?
No, it's 2.2.13.
> Otherwise, are you sure you are recompiling 3dfx-module?
yes, absolutly!
> This is probably a simple error. We forbid cross CPU changes of period, but
> you report what may be the result of the cpu field on the task not being
> set properly.
So, i have to bind a task to a specific CPU to be able to change
the period within the task?
IMHO, at least it it a good idea to not let a rt-task jump
across several CPU, since the not-well deterministic
intel-architecture would be even less deterministic
due to cache-flushes and MESI-Protocol.
Although, from technical point of view, it would be more
interessting to be able to fix the task to a subset of CPUs,
like it is in RTAI/RTHAL :-)
> > RedHat 6.1/RTL2.0 on Kernel 2.2.13
>
> So you claim to not be using 2.2.14 ? I'll check today.
Yes, absolutly!
[reiserfs]
>
> That is cool, but it will encourage poor programming practice by
> kernel programmers since the consequences are less -)
Are you talking about the guys in redmond? :-)
Bernhard
BTW: if it would help, i can give you remote-access to my
system to determine the problem with the 3dfx-module.
IMHO, the "setperiod across CPUs"-Problem is only due to
wrong programming ... i will check that later.
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail majordomo@rtlinux.cs.nmt.edu OR
echo "unsubscribe rtl <Your_email>" | mail majordomo@rtlinux.cs.nmt.edu
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/