Ever since R5 releases came out, I think around R5A10, I can't get lircd to work on my mythbox to change channels. It gets some stupid Kernel BUG about SMP. I read somewhere it's faulty kernel in 2.6.11.x. Can anyone confirm this? If this is the case, when can we expect Knoppmyth to adopt a "fixed" kernel version? I tried upgrading my kernel, compiling the latest from kernel.org but that broke everything and I gave up. It's disappointing not having a working mythbox for 6+ months now!!

Any help is appreciated! Thanks!

well what kernel is "fixed" the current knoppmyth kernel is 2.6.13 based.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Unfortunately, I don't know what kernel version would fix it. All I can reference is these links:

http://www.nabble.com/BUG%3A-using-smp_ ... 62240.html

http://mysettopbox.tv/phpBB2/viewtopic. ... &start=15&

http://www.gossamer-threads.com/lists/m ... id;#150238

I'm getting that same "BUG: using smp_processor_id() in preemptible [00000001] code: lircd/2485" log message when running irsend. It definitely cropped up around R5A16.... so starting with 2.6.11.9? One would hope the issue (if it is in fact kernel related) is fixed in 2.6.14.3?

Along these lines, is it possiable to install Knoppmyth without SMP support in the kernel? Like a command line option when booting the CD? I know it can be done via recompiling the kernel, but as many times as I've recompiled kernels (on other boxes), something always goes wonky on Knoppmyth when I compile its kernel... Maybe I'm just not doing something right.

anyone know a fix? ...or for that matter, how to upgrade the kernel in knoppmyth without major issues?

There is only one kernel and that includes SMP support. If you want uniprocessor, you'll have to recompile. If you search teh forum, you'll find details on recompiling...

_________________
cesman

When the source is open, the possibilities are endless!

I have the exact same bug when I use irsend:

BUG: using smp_processor_id() in preemptible [00000001] code: lircd

Anyone have a solution. I had it working great on an earlier version of knoppmyth.

Has anyone tried re-compiling without smp support.

What is SMP support? Do I need it? does it do anything to mythtv?

Please help, I can't control my DSS box anymore so my pvr is almost useless.

-Joe

SMP is symmetric multiprocessing, it is needed for multi processors. It is most cases is harmless for uniprocessor systems.

_________________
cesman

When the source is open, the possibilities are endless!

I know it's alot to ask, but would it be possible for you to package R5A30+ with dual kernels, one SMP and one UP and let the user choose or have the script intelligently detect it at install time? I see no point whatsoever in including SMP support in a default HTPC install...other than to support hyperthreading (which has it's own bugs) and dual-core chips. Overall it's alot more trouble than it's worth considering this nasty lirc_serial bug.

I have to agree, I see other SMP errors come up but none cause any issues except the lirc problem. I re-built a kernel, but that caused its own issues (still didn't get serial to work).

I am sure there are a lot of people using the SMP, but it would really help to not add so many things to the kernel for those of us trying to keep a cost effective solution.

-Joseph

well anything is possible, but you must realize that what you are asking is a very large task. First you have to actually build and test two kernels for every release, then you have to figure some way out to allow a choice of which one gets installed during the install, which would mean a major overhaul of the installation routine. (this won't happen right now as the installer is already undergoing a major rewrite to be graphical. once that is finished who knows what might happen) As for only having uniproc kernel the PIV hyperthreaded cpu's get a giant performance increase with the smp kernel and they are the current recommended proc for hdtv, not to mention the fact that anything that doesn't work right really needs to be fixed in the kernel anyways, as all modules really should be thread safe these days.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

I'm having second thoughts about the lirc smp bug now that my box is working perfectly. Previously my IR blaster didn't seem to work right and the syslog was stacking up lots of lirc BUG messages. Now that I have the IR blaster working perfectly, the syslog is still filling up with lirc bug output. So, that goes to show that even though the lirc_serial module is complaining, it's still doing it's job, and maybe the lirc bug is a non-issue.

Afrosheen- I have the same problem, logs full of SMP bug messages. I have re-built the kernel to remove multi-processor support, the IR blaster works a treat, ivtv works, but I am now trying to get the PVR350 remote working. I guess I need to recompile the lirc package which handles the PVR350 remote.

Alan.

I'm seeing the SMP messages for every call to 'irsend?', but it works.

Now, if only I could get my 350 receiver to work

Using R5A30.2

Got rid of the SMP bug by removing SMP option and re-compiling kernel.

Got pvr 350 working by re-compiling lirc as follows:

1. go to /usr/src
2. unpack lirc source with tar -xjf lirc-0.7.2pvr150.tar.bz2
3. cd lirc-0.7.2pvr150
4. ./setup.sh
5. Select driver configuration, select TV card, Select Hauppauge TV card (new I2C layer required)
6. Select save & configure
7. make, make install, update-modules.
8. If all is well, you should be able to modprobe lirc_i2c and lirc_dev
9. Reboot.

Note, the remote was working through the pvr 350 prior to me re-compiling the kernel, so my config files were all ok.

Hope this helps,

Algenon.

p.s. congratulations to the Knoppmyth team for producing a fantastic package!