Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UHD 4.6.0 disrupting gqrx #1331

Open
wcostrino opened this issue Jan 2, 2024 · 2 comments
Open

UHD 4.6.0 disrupting gqrx #1331

wcostrino opened this issue Jan 2, 2024 · 2 comments
Labels

Comments

@wcostrino
Copy link

Hello,

After I installed the new version of UHD, 4.6.0, in debian Trixie, there is no recognition of any hardware in gqr:

[10252.061462] traps: gqrx[1884553] general protection fault ip:7fb818344cd6 sp:7fb7e97f57d0 error:0
[10252.061462] gqrx[1884556]: segfault at f4 ip 00007fb818344cd6 sp 00007fb7b3ffb870 error 4
[10252.061464] gqrx[1884554]: segfault at f4 ip 00007fb818344cd6 sp 00007fb7e8ff3870 error 4
[10252.061469] traps: gqrx[1884550] general protection fault ip:7fb818344cd6 sp:7fb7eaff73d0 error:0
[10252.061470] in libuhd.so.4.6.0[7fb818121000+a5e000]
[10252.061470] in libuhd.so.4.6.0[7fb818121000+a5e000]
[10252.061470] in libuhd.so.4.6.0[7fb818121000+a5e000]
[10252.061472] likely on CPU 15 (core 7, socket 0)
[10252.061472] likely on CPU 12 (core 4, socket 0)
[10252.061474] in libuhd.so.4.6.0[7fb818121000+a5e000]
[10252.061474] Code: ec 78 64 48 8b 04 25 28 00 00 00 48 89 44 24 68 31 c0 80 bf c0 00 00 00 00 0f 85 ed 00 00 00 48 8b 45 30 48 8b 9d d0 00 00 00 <44> 8b b8 f4 00 00 00 48 85 db 0f 84 3a 01 00 00 48 8b 43 18 48 89
[10252.061476] Code: ec 78 64 48 8b 04 25 28 00 00 00 48 89 44 24 68 31 c0 80 bf c0 00 00 00 00 0f 85 ed 00 00 00 48 8b 45 30 48 8b 9d d0 00 00 00 <44> 8b b8 f4 00 00 00 48 85 db 0f 84 3a 01 00 00 48 8b 43 18 48 89

I couldn't revert to the older version to really test if its the issue.

Thanks!

@argilo
Copy link
Member

argilo commented Jan 2, 2024

I would suggest reporting this to Debian, as it appears to be a packaging issue.

@wcostrino
Copy link
Author

@argilo thanks... I will do that!

@argilo argilo added the bug label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants