FS#11041 - Lirc 0.8.2 causes kernel oops. Fix included in bug report.

Attached to Project: Arch Linux
Opened by Jeremy Sands (georgia_tech_swagger) - Tuesday, 29 July 2008, 04:00 GMT
Last edited by Eric Belanger (Snowman) - Sunday, 10 August 2008, 21:12 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: When using existing lirc 0.8.2 in extra, and trying to use remote, it throws a kernel oops. See this thread:
http://bbs.archlinux.org/viewtopic.php?id=52414

Simply pushing out a new package for lirc 0.8.3 fixes this problem. However the PKGBUILD can lose its unnecessary patch references. I have attached just such a fixed PKGBUILD that works fine for me. It uses the existing lirc.install file.

I put this under major since it essentially completely hoses lirc and ivtv until you reboot. A localized "kernel panic" if you will.
This task depends upon

Closed by  Eric Belanger (Snowman)
Sunday, 10 August 2008, 21:12 GMT
Reason for closing:  Fixed
Additional comments about closing:  lirc 0.8.3-1 is now in extra repo.
Comment by Jeremy Sands (georgia_tech_swagger) - Tuesday, 29 July 2008, 04:21 GMT
Try #2 to attach the PKGBUILD
   PKGBUILD (1.5 KiB)
Comment by Jeremy Sands (georgia_tech_swagger) - Tuesday, 29 July 2008, 04:40 GMT
A patch file if you prefer to see the exact changes.
   lirc-0.8.2-to-lirc-0.8.3.patch (1.5 KiB)
Comment by Eric Belanger (Snowman) - Tuesday, 29 July 2008, 18:18 GMT
The kernel in testing along with lirc 0.8.3 will soon be moved to core. Fixing the package currently in extra implies updating both lirc and lirc-utils plus bumping the pkgrel of the packages in testing. That is quite some work so we'll just wait for the kernel move especially you are the only one who has the issue AFAIK and got it fixed. Other users can fix it like you did or use the kernel in testing.

FTR, I don't maintian the lirc packages; they are orphaned. I only helped updating/rebuilding them for the kernel in testing.
Comment by Jeremy Sands (georgia_tech_swagger) - Tuesday, 29 July 2008, 19:09 GMT
If I do all those packages for you as well will you push the changes?
Comment by Eric Belanger (Snowman) - Tuesday, 29 July 2008, 23:42 GMT
No. I won't put packages built by untrusted source in the repos. No offence intended. I know you from the forum and probably you are well intentionned but I prefer being safe than sorry. If I had known about that before submitting the package for testing, I would've probably updated the package for extra but now it's just too late. Too much work for a very short term fix.
BTW, as these packages have been in the repo for a long time and you are the first one to report this problem, I would say that this problem is not very widespread so it can wait the few days before 2.6.26 hits core.
Comment by dillweed (dillweed) - Tuesday, 05 August 2008, 22:20 GMT
Just to let you all know, that I'm getting the same kernel opps. I'm anxious for .26 to come out, hopefully I can use my remote again.

Loading...