[PATCH] RFC: don't aggravate kernel panics

Andy Green andy at openmoko.com
Tue Jan 20 15:45:00 CET 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

| So I wonder if this is good enough or if someone has any plans to
| make a better solution ?

| +	if (in_atomic()) {
| +		printk(KERN_ERR
| +		    "gta02_bl_set_intensity called while atomic\n");
| +		return;
| +	}

What we could do with is this business of spawning a new kernel to
report a panic in a controlled way.  But, I read on trac about it that
the config option needed is not available in Arm.

Another way to come at that would be stash the syslog somewhere safe
near the end of memory, set a signature there and reboot off the panic
into the recovery kernel, and show it there.

Anyway this patch doesn't hurt anything since we need interrupts to do
I2C stuff anyway, so I sent it on andy-tracking.  But the
git.openmoko.org box seems down at the moment.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkl142wACgkQOjLpvpq7dMpbkACfQuEhNhzunHPD5HySIYAzZpTN
gTEAniRdSA+uObcK+f0S46NbawFcuWoN
=CK64
-----END PGP SIGNATURE-----



More information about the openmoko-kernel mailing list