Failed to open Xillybus device file(s): No such file

Questions and discussions about the Xillybus IP core and drivers

Failed to open Xillybus device file(s): No such file

Postby Guest »

I have loaded the modules correctly. But error occuring while opening xillybus device file.
"Failed to open Xillybus device file(s): No such file or directory"
In the dmesg output, it is showing "xillybus_core: module verification failed: signature and/or required key missing - tainting kernel"
lsmod , lspci and dmesg commands outputs included below

https://docs.google.com/document/d/1nuN ... sp=sharing
Guest
 

Re: Failed to open Xillybus device file(s): No such file

Postby support »

Hello,

The dmesg line you pointed at is no reason for alarm. It just says that the driver isn't signed (you compiled it yourself, I suppose) but it was loaded properly. if so, I would ask why you didn't rely on the driver that comes with the kernel.

Or maybe you accidentally used your compiled xillybus_core with the kernel's original xillybus_pcie or vice versa? That's the most reasonable explanation I can come up with for the weird thing that happened:

Code: Select all
[    2.771389] WARNING: CPU: 3 PID: 359 at /build/linux-hwe-0EwvTm/linux-hwe-4.15.0/lib/iomap.c:44 bad_io_access+0x2a/0x30
[    2.771389] Modules linked in: xillybus_pcie(+) eeepc_wmi(+) asus_wmi sparse_keymap wmi_bmof serio_raw snd mei_me soundcore xillybus_core(OE) mei shpchp fjes(-) acpi_pad mac_hid coretemp parport_pc ppdev lp parport autofs4 mxm_wmi e1000e psmouse ptp pps_core ahci libahci wmi video
[    2.771402] CPU: 3 PID: 359 Comm: systemd-udevd Tainted: G           OE    4.15.0-54-generic #58~16.04.1-Ubuntu
[    2.771403] Hardware name: System manufacturer System Product Name/STRIX B250F GAMING, BIOS 0606 03/23/2017
[    2.771404] RIP: 0010:bad_io_access+0x2a/0x30
[    2.771405] RSP: 0018:ffffb83c433039c0 EFLAGS: 00010282

[ ... ]

[    2.771414] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[    2.771414] Call Trace:
[    2.771417]  iowrite32+0x2c/0x40
[    2.771419]  xillybus_endpoint_discovery+0x8f/0x5a0 [xillybus_core]
[    2.771422]  ? request_threaded_irq+0xfd/0x1a0
[    2.771424]  xilly_probe+0x172/0x2b3 [xillybus_pcie]
[    2.771426]  ? xilly_probe+0x172/0x2b3 [xillybus_pcie]

What we see here is a failure to access the device's register. This has never happened before (I'm talking about hundreds of users at least using this same driver with no problems).

So either there's a serious problem in your computer's memory manager (but the computer would crash like crazy if that was the case), or you're doing something very unusual there.

Or, we have a mixture between two pieces of the driver with possibly slight version differences. Which could lead to all kind of weird stuff, like the one you're experiencing.

Bottom line: Please use the drivers that go with the kernel, or alternatively, make sure they're not loaded automatically by accident.

Regards,
Eli
support
 
Posts: 802
Joined:

Re: Failed to open Xillybus device file(s): No such file

Postby Guest »

I have found the issue. Actually, this issue is occurring only if i am using linux-headers-4.15.0-54-generic. But, it is working fine with linux-headers-4.4.0-150-generic. Thank you for your valuable response.
Guest
 

Re: Failed to open Xillybus device file(s): No such file

Postby support »

Hello,

Unfortunately, this doesn't sound like a solution at all, but rather solving one quirk with another. Xillybus' driver works with the entire range of kernels since 2.6.something, so there's no reason it should work with one kernel version and not the other.

Apparently, you've managed to load the drivers after making that workaround. However without finding the root cause for this weirdness, you might face other problems, possibly without realizing they are related to whatever is wrong there.

So I would warmly suggest getting to the bottom of this. Once again, either use the drivers that come with the distribution, or make sure they're not loaded. And if you compile the drivers yourself, do so with the headers belonging to the kernel used.

Regards,
Eli
support
 
Posts: 802
Joined:


Return to Xillybus