http://bugzilla.suse.com/show_bug.cgi?id=1082504
http://bugzilla.suse.com/show_bug.cgi?id=1082504#c55
--- Comment #55 from Ivan Levshin ---
The only conf file doesn't belonging to any package is vmware-fuse.conf -
that's true as it was created by VMware Player I'm using on this machine, all
other files are marked as belonging to different packages:
ivan@mynote:~> LANG=c rpm -qf /etc/modprobe.d/*.conf
suse-module-tools-12.4-4.5.x86_64
suse-module-tools-12.4-4.5.x86_64
alsa-1.1.6-1.1.x86_64
sysconfig-0.84.2-2.1.x86_64
bluez-5.49-2.1.x86_64
wireless-tools-30.pre9-38.1.x86_64
wireless-tools-30.pre9-38.1.x86_64
rdma-core-16.4-3.1.x86_64
wireless-tools-30.pre9-38.1.x86_64
suse-module-tools-12.4-4.5.x86_64
firewalld-0.5.2-2.1.noarch
rdma-core-16.4-3.1.x86_64
rdma-core-16.4-3.1.x86_64
tuned-2.8.0-3.1.noarch
file /etc/modprobe.d/vmware-fuse.conf is not owned by any package
I also tried to unload/load btusb, all I got are:
[ 6059.650391] usbcore: deregistering interface driver btusb
[ 6066.858030] usbcore: registered new interface driver btusb
All dmesg archives contains 2 dmesg outputs: one before ath3k and btusb unload
and another - after reload.
Takashi, could you please remind me why it's not possible to use the fix you
applied before? Before something happened with ath10k everything was working
like a charm. You told me that there were some changes applied to ath10k and
these changes are rolled back now, so it seems like fix will be working again,
isn't it? Sorry for stupid questions :)
--
You are receiving this mail because:
You are on the CC list for the bug.