All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2(sorta)] Unexpected-continuation-frame-printk flood avoidance
@ 2015-02-24  6:25 Gregory M. Turner
  2015-02-24  6:25 ` [PATCH v2(sorta) 1/2] bluetooth: Add BT_{INFO,ERR,DBG}_RATELIMITED Gregory M. Turner
  2015-02-24  6:25 ` [PATCH v2(sorta) 2/2] " Gregory M. Turner
  0 siblings, 2 replies; 6+ messages in thread
From: Gregory M. Turner @ 2015-02-24  6:25 UTC (permalink / raw)
  To: Marcel Holtmann; +Cc: linux-bluetooth

Mitigation for those with floods of:

  Bluetooth: Unexpected Continuation Frame (len 0)

in their logs.  The underlying cause of this is still far from crystal clear
(at least, not to me), but, anyhow, I'm sold on Marcel's advice to solve this
by placing my dongle in the garbage.

Previously I suggested dropping the printk entirely but ratelimiting is
better, since the printk is not wrong (or, if it were wrong, this would
at least be indicative of a problem elsewhere).

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-03-19 18:54 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-24  6:25 [PATCH v2(sorta)] Unexpected-continuation-frame-printk flood avoidance Gregory M. Turner
2015-02-24  6:25 ` [PATCH v2(sorta) 1/2] bluetooth: Add BT_{INFO,ERR,DBG}_RATELIMITED Gregory M. Turner
2015-03-03  1:07   ` Marcel Holtmann
2015-03-14 19:01     ` Greg Turner
2015-03-19 18:54   ` [PATCH v3 1/1] bluetooth: l2cap_core: ratelimit continuation frame printk gmt
2015-02-24  6:25 ` [PATCH v2(sorta) 2/2] " Gregory M. Turner

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.