Messages in this thread | | | Subject | Re: "BUG: MAX_STACK_TRACE_ENTRIES too low!" - reason for concern? | From | Peter Zijlstra <> | Date | Sun, 14 Dec 2008 13:41:25 +0100 |
| |
On Sun, 2008-12-14 at 02:38 +0100, Stefan Richter wrote: > Is the following anything that anybody should do something about? > > # unloading IEEE 1394 drivers (as slightly before linux1394-2.6.git) > > Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[3-00:1023] GUID[00d0f5200800613d] > Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[2-00:1023] GUID[0010dc5600fed2d4] > Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[1-01:1023] GUID[0030bd051800064f] > Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[1-00:1023] GUID[0012870035000f94] > Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[0-08:1023] GUID[080028560000319b] > > # reloading IEEE 1394 drivers (as in linux1394-2.6.git) > > Dec 14 01:23:29 stein BUG: MAX_STACK_TRACE_ENTRIES too low!
lockdep resource allocation is pretty simple wrt to modules, it will not re-use anything, therefore cycling modules will let it run out of its resources pretty quickly.
I suppose one could go add all kinds of smart and complicate the whole thing, but I'm not sure its worth it.
| |