It's a warning, not an error; but I didn't expect it to be quite soGood to hear that it was just a warning and not a bug/problem ;-)
voluminous in terms of log messages. We have a proper fix for it
queued up for 2.6.30, but it was considered too invasive. So the fix
was to print a warning which we ratelimited, but it looks like it's
even with the printk_ratelimit the warnings are too annoying to let
live. I'll probably fix it to only printk the message once.
- Ted