How to report this bug?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
Most bugs are impossible to report. You have to have a package. Well, this is multiple packages, Ubuntu itself, and hardware/firmware related. How the heck do I file it? ubuntu-bug requires a single package. It's not automatically triggering the built-in Ubuntu bug reporter.
When I close the lid of XPS 9560, and wake up, a lot of stuff is wrong. The GUI will freeze and unfreeze every few seconds, as something is grinding it to a halt. The wifi can't reactivate. It can't even try to scan for networks, much less join one.
Here's recent dmesg output:
[43548.249307] ath10k_warn: 129 callbacks suppressed
[43548.249309] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.285609] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.316369] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.347057] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.382893] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.419305] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.455788] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.492277] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.523109] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.553793] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43551.161054] ath10k_pci 0000:02:00.0: failed to read device register, device is gone
[43551.270391] ath10k_pci 0000:02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468)
[43551.270394] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[43551.270396] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[43551.270803] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[43551.271233] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
[43551.271235] ath10k_pci 0000:02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[43551.271242] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -28
[43551.271243] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[43551.417001] ath10k_pci 0000:02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
[43551.562682] ath10k_pci 0000:02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
[43551.708407] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
[43551.841610] ath10k_pci 0000:02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
[43551.975925] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
[43552.108938] ath10k_pci 0000:02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
[43552.254895] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
[43552.400652] ath10k_pci 0000:02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
[43552.400689] ath10k_pci 0000:02:00.0: failed to reset chip: -5
[43552.400690] ath10k_pci 0000:02:00.0: Could not init hif: -5
18.04
add a comment |Â
up vote
1
down vote
favorite
Most bugs are impossible to report. You have to have a package. Well, this is multiple packages, Ubuntu itself, and hardware/firmware related. How the heck do I file it? ubuntu-bug requires a single package. It's not automatically triggering the built-in Ubuntu bug reporter.
When I close the lid of XPS 9560, and wake up, a lot of stuff is wrong. The GUI will freeze and unfreeze every few seconds, as something is grinding it to a halt. The wifi can't reactivate. It can't even try to scan for networks, much less join one.
Here's recent dmesg output:
[43548.249307] ath10k_warn: 129 callbacks suppressed
[43548.249309] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.285609] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.316369] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.347057] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.382893] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.419305] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.455788] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.492277] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.523109] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.553793] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43551.161054] ath10k_pci 0000:02:00.0: failed to read device register, device is gone
[43551.270391] ath10k_pci 0000:02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468)
[43551.270394] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[43551.270396] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[43551.270803] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[43551.271233] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
[43551.271235] ath10k_pci 0000:02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[43551.271242] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -28
[43551.271243] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[43551.417001] ath10k_pci 0000:02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
[43551.562682] ath10k_pci 0000:02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
[43551.708407] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
[43551.841610] ath10k_pci 0000:02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
[43551.975925] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
[43552.108938] ath10k_pci 0000:02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
[43552.254895] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
[43552.400652] ath10k_pci 0000:02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
[43552.400689] ath10k_pci 0000:02:00.0: failed to reset chip: -5
[43552.400690] ath10k_pci 0000:02:00.0: Could not init hif: -5
18.04
I would report it again the kernel
â Panther
2 days ago
But this still is related to 1 package: firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1 is probably the thing to go on). You probably need to turn off power management for the time being :)
â Rinzwind
2 days ago
How do I report it against the kernel or the firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1)? If I ubuntu-bug, what's the argument afterward, and should it be kernel or firmware?
â Tom Mercer
yesterday
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Most bugs are impossible to report. You have to have a package. Well, this is multiple packages, Ubuntu itself, and hardware/firmware related. How the heck do I file it? ubuntu-bug requires a single package. It's not automatically triggering the built-in Ubuntu bug reporter.
When I close the lid of XPS 9560, and wake up, a lot of stuff is wrong. The GUI will freeze and unfreeze every few seconds, as something is grinding it to a halt. The wifi can't reactivate. It can't even try to scan for networks, much less join one.
Here's recent dmesg output:
[43548.249307] ath10k_warn: 129 callbacks suppressed
[43548.249309] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.285609] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.316369] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.347057] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.382893] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.419305] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.455788] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.492277] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.523109] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.553793] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43551.161054] ath10k_pci 0000:02:00.0: failed to read device register, device is gone
[43551.270391] ath10k_pci 0000:02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468)
[43551.270394] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[43551.270396] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[43551.270803] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[43551.271233] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
[43551.271235] ath10k_pci 0000:02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[43551.271242] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -28
[43551.271243] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[43551.417001] ath10k_pci 0000:02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
[43551.562682] ath10k_pci 0000:02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
[43551.708407] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
[43551.841610] ath10k_pci 0000:02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
[43551.975925] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
[43552.108938] ath10k_pci 0000:02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
[43552.254895] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
[43552.400652] ath10k_pci 0000:02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
[43552.400689] ath10k_pci 0000:02:00.0: failed to reset chip: -5
[43552.400690] ath10k_pci 0000:02:00.0: Could not init hif: -5
18.04
Most bugs are impossible to report. You have to have a package. Well, this is multiple packages, Ubuntu itself, and hardware/firmware related. How the heck do I file it? ubuntu-bug requires a single package. It's not automatically triggering the built-in Ubuntu bug reporter.
When I close the lid of XPS 9560, and wake up, a lot of stuff is wrong. The GUI will freeze and unfreeze every few seconds, as something is grinding it to a halt. The wifi can't reactivate. It can't even try to scan for networks, much less join one.
Here's recent dmesg output:
[43548.249307] ath10k_warn: 129 callbacks suppressed
[43548.249309] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.285609] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.316369] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.347057] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.382893] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.419305] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.455788] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.492277] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.523109] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43548.553793] ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
[43551.161054] ath10k_pci 0000:02:00.0: failed to read device register, device is gone
[43551.270391] ath10k_pci 0000:02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468)
[43551.270394] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[43551.270396] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[43551.270803] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[43551.271233] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
[43551.271235] ath10k_pci 0000:02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[43551.271242] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -28
[43551.271243] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[43551.417001] ath10k_pci 0000:02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
[43551.562682] ath10k_pci 0000:02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
[43551.708407] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
[43551.841610] ath10k_pci 0000:02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
[43551.975925] ath10k_pci 0000:02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
[43552.108938] ath10k_pci 0000:02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
[43552.254895] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
[43552.400652] ath10k_pci 0000:02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
[43552.400689] ath10k_pci 0000:02:00.0: failed to reset chip: -5
[43552.400690] ath10k_pci 0000:02:00.0: Could not init hif: -5
18.04
edited 2 days ago
N0rbert
13.5k32664
13.5k32664
asked 2 days ago
Tom Mercer
5441322
5441322
I would report it again the kernel
â Panther
2 days ago
But this still is related to 1 package: firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1 is probably the thing to go on). You probably need to turn off power management for the time being :)
â Rinzwind
2 days ago
How do I report it against the kernel or the firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1)? If I ubuntu-bug, what's the argument afterward, and should it be kernel or firmware?
â Tom Mercer
yesterday
add a comment |Â
I would report it again the kernel
â Panther
2 days ago
But this still is related to 1 package: firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1 is probably the thing to go on). You probably need to turn off power management for the time being :)
â Rinzwind
2 days ago
How do I report it against the kernel or the firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1)? If I ubuntu-bug, what's the argument afterward, and should it be kernel or firmware?
â Tom Mercer
yesterday
I would report it again the kernel
â Panther
2 days ago
I would report it again the kernel
â Panther
2 days ago
But this still is related to 1 package: firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1 is probably the thing to go on). You probably need to turn off power management for the time being :)
â Rinzwind
2 days ago
But this still is related to 1 package: firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1 is probably the thing to go on). You probably need to turn off power management for the time being :)
â Rinzwind
2 days ago
How do I report it against the kernel or the firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1)? If I ubuntu-bug, what's the argument afterward, and should it be kernel or firmware?
â Tom Mercer
yesterday
How do I report it against the kernel or the firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1)? If I ubuntu-bug, what's the argument afterward, and should it be kernel or firmware?
â Tom Mercer
yesterday
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1062123%2fhow-to-report-this-bug%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I would report it again the kernel
â Panther
2 days ago
But this still is related to 1 package: firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1 is probably the thing to go on). You probably need to turn off power management for the time being :)
â Rinzwind
2 days ago
How do I report it against the kernel or the firmware-atheros (WLAN.RM.4.4.1-00079-QCARMSWPZ-1)? If I ubuntu-bug, what's the argument afterward, and should it be kernel or firmware?
â Tom Mercer
yesterday