I'm getting more comfortable with leds, and troubles begin.
When I enable timer-base led triggering and start even just two leds in
short succession (in a shell script), I start seeing:
[ 1210.586990] Trying to free nonexistent resource <000000000000002e-000000000000002f>
[ 1211.227414] Trying to free nonexistent resource <000000000000002e-000000000000002f>
[ 1211.867890] Trying to free nonexistent resource <000000000000002e-000000000000002f>
[ 1212.508299] Trying to free nonexistent resource <000000000000002e-000000000000002f>
[ 1213.148734] Trying to free nonexistent resource <000000000000002e-000000000000002f>
[ 1213.789172] Trying to free nonexistent resource <000000000000002e-000000000000002f>
[ 1214.429607] Trying to free nonexistent resource <000000000000002e-000000000000002f>
2e-2f is the range of the SuperIO, which is requested & released by
(at least) gpio-f7188x:
[ 535.653716] gpio-f7188x: Found f71869a at 0x2e, revision 32
Unloading all other modules accessing the SuperIO (fintek-cir and
f71882fg), I can still reproduce the message.
Also, when this error happens, tty screen can become corrupted (areas
become blank, as if space char was replacing large rectangles).
Unloading my module (which unregisters leds, in turn unregistering GPIO
pins) clears the corruption ("hidden" chars appear again).
Enabling usb-host triggering, the messages appears without a single
other led trigger set to something else than "none".
I do not speak C fluently enough to tell if this is a re-entry kind of
problem (same module accessing GPIO pins right next to each other at
about the same time by different timers).
How can I debug this further ?
--
Vincent Pelletier
--
To unsubscribe from this list: send the line "unsubscribe linux-leds" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
