[luxid] [linux-rt] BUG: scheduling while atomic: sirq-tasklet/1/0x00000001/23, CPU#1

[pablomme]

This oops just happened and I'm unsure as to whether there will be system instability as a consequence. Running lucid installed afresh from alpha 3.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
Date: Mon Mar 8 13:55:54 2010
DistroRelease: Ubuntu 10.04
Failure: oops
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-10-rt 2.6.31-10.153
ProcVersionSignature: Ubuntu 2.6.31-10.153-rt
SourcePackage: linux-rt
Title: BUG: scheduling while atomic: sirq-tasklet/1/0x00000001/23, CPU#1
Uname: Linux 2.6.31-10-rt x86_64

[pablomme (pablomme)]

I've encountered more instances of this oops, including one involving VirtualBox instead of the tasklet process. In no case has the system become unstable.

[Alessio Igor Bogani (abogani)]

Hi,

Could you check this bug against -realtime kernel available on my PPA, please?

This is the PPA:
https://launchpad.net/~abogani/+archive/ppa

This is the install instructions:
https://launchpad.net/+help/soyuz/ppa-sources-list.html

Please consider that on this kernel closed drivers don't works so you should disable these first.

As general rule you should disable all driver with "Proprietary" license in System -> Administration -> Hardware Drivers

Thanks a lot!

[pablomme (pablomme)]

@Alessio: the kernel oops is not easy to trigger, it appears to happen mostly at random, and I haven't encountered one in a couple of days. That means that to test your kernel I would have to use it regularly for a few days and report back if I don't see any oopses. I don't have any problem with that by itself, but it is rather inconvenient if I can't use the nvidia driver. Can your kernel be made to work with it? Why can't it anyway? Shouldn't DKMS just take care of compiling the kernel interface as usual?

[pablomme (pablomme)]

Answering myself, DKMS does take care of it, and the nvidia driver works with this kernel.

I'll set this kernel as the default in /etc/default/grub, and I'll report back in a few days if I don't bump into any oopses, or earlier if I do. Thanks.

[Alessio Igor Bogani (abogani)]

Thanks you very much!

[pablomme (pablomme)]

Ok, I've just had apport pop up with a "Serious kernel problem" (which I assume is the oops) after running VirtualBox, but it would not produce a report because it's not an official Ubuntu kernel, and I can't for the life of me find the oops message under /var/log -- where is it supposed to be reported?

[pablomme (pablomme)]

Ah, found the apport report. Attached. It was indeed the same oops, so whatever the change is in this kernel, it's not helping. Unless you were trying to address the tasklet problem specifically, in which case I still haven't encountered any oopses to report.

[Alessio Igor Bogani (abogani)]

> life of me find the oops message under /var/log -- where is it supposed
> to be reported?

/var/log/kern.log

[pablomme (pablomme)]

> > life of me find the oops message under /var/log -- where is it supposed
> > to be reported?
>
> /var/log/kern.log

That was my first try and there was no relevant message there. What I attached above is from /var/crash.

[Andras Muranyi (muranyia)]

@alessio: i'm having this problem with 2.6.33-29-realtime kernel from your PPA.
The are no drivers shown in System -> Administration -> Hardware Drivers
I'm using NVIDIA-Linux-x86_64-260.19.21 patched manually by these instructions: http://ubuntuforums.org/showpost.php?p=9233282&postcount=5