unreportable kernel oops / bluetooth

[SternData]

I get kerneloops reports that I can't pass on because the kernel is
tained by the virtualbox drivers.

The oops occurs when a previously paired bluetooth device becomes
discoverable.  My F20 systems sees the device and connects, then
disconnects, then the oops occurs.  If I put the device back into
discoverable mode, I can use the bluetooth preference panel to connect
manually.

Any suggestions about how to debug/fix this?

[D. Hugh Redelmeier]

| From: Steven Stern

| I get kerneloops reports that I can't pass on because the kernel is
| tained by the virtualbox drivers.
...
| Any suggestions about how to debug/fix this?

See if you can repeat this without the virtualbox drivers installed.

If so: report to Fedora bugzilla.
If not: report to Oracle (publishers).

[SternData]

On 05/05/2014 01:37 PM, D. Hugh Redelmeier wrote:
> | From: Steven Stern
>
> | I get kerneloops reports that I can't pass on because the kernel is
> | tained by the virtualbox drivers.
> ...
> | Any suggestions about how to debug/fix this?
>
> See if you can repeat this without the virtualbox drivers installed.
>
> If so: report to Fedora bugzilla.
> If not: report to Oracle (publishers).

With VirtualBox disabled, it all works very nicely.