Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #63094 > unrolled thread

Bug#919632: "New" firmware instantly crashes on QCA9377

Back to article view | Back to linux.debian.kernel

Contents

  Bug#919632: "New" firmware instantly crashes on QCA9377 Kevin Price <kp@osnanet.de> - 2019-01-18 06:10 +0100
    Bug#919632: "New" firmware instantly crashes on QCA9377 Kevin Price <kp@osnanet.de> - 2019-01-18 23:10 +0100
    Bug#919632: marked as done ("New" firmware instantly crashes on  QCA9377) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-05-06 23:40 +0200
    Bug#919632: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1) Kevin Price <kp@osnanet.de> - 2019-05-07 14:00 +0200
      Bug#919632: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1) Ben Hutchings <ben@decadent.org.uk> - 2019-05-07 17:40 +0200
        Bug#919632: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1) kp@osnanet.de - 2019-05-07 22:20 +0200
          Processed: Re: Bug#919632 closed by Ben Hutchings <ben@decadent.org.uk>  (Bug#919632: fixed in firmware-nonfree 20190502-1) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-05-07 22:30 +0200
          Bug#919632: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1) Ben Hutchings <ben@decadent.org.uk> - 2019-05-07 22:40 +0200
    Processed: Re: Bug#919632 closed by Ben Hutchings <ben@decadent.org.uk>  (Bug#919632: fixed in firmware-nonfree 20190502-1) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-05-07 17:40 +0200
    Processed: Re: Bug#919632: closed by Ben Hutchings  <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-05-07 22:40 +0200
    Bug#919632: marked as done ("New" firmware instantly crashes on  QCA9377) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-07-28 20:00 +0200
    Bug#919632: marked as done ("New" firmware instantly crashes on  QCA9377) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-08-23 10:10 +0200

#63094 — Bug#919632: "New" firmware instantly crashes on QCA9377

[Multipart message — attachments visible in raw view] — view raw

Package: firmware-atheros
Version: 20180518-1
Severity: important
Tags: upstream

Dear Maintainer,

I observed this while upgrading non-free firmware from stretch
(20161130-4) to stretch-backports (20180825+dfsg-1~bpo9+1) my QCA9377
quit working. Whether during boot or manually: When modprobing
ath10k_pci, the device either appears in my network stack, or it does
not, depending on the firmware version. In the latter case, that is
because its firmware instantly crashes, according to dmesg. I pinned
that down to: up to 20170823-1 works, 20180518-1 and after does not,
including 20190114-1. Looking at changelog.Debian, the break seems to
have been caused by this change:
"
firmware-nonfree (20180518-1) unstable; urgency=medium
 * New upstream version:
   - atheros:
     + QCA9377 rev 1.0 firmware version WLAN.TF.1.0-00002-QCATFSWPZ-5
"
According to dmesg, this "upgrade" replaced WLAN.TF.1.0-00267-1, which
was at least partially working for me. (only crashing occasionally as
described in #885846, and having trouble with big packet sizes, but
generally working) Comparing these QC firmware version numbers, they
look to me like the debian package upgrade actually included an upstream
downgrade. That of course would be the culprit, and a reason to rename
this bug report. You might want to check this hunch with upstream, and
with their versioning scheme. I suspect that #903437 might have the same
cause. And if there is a better QC-firmware than WLAN.TF.1.0-00267-1,
that might even resolve #885846 as well.

I'd love to see at least stretch-backports not breaking device
functionality. Please let me know about how else I may assist you in
that. FWIW, I'll attach the dmesg of when it's crashing, and my lspci
(-v and -vv) in (half-)working condition. My kernel is
linux-image-4.9.0-8-amd64_4.9.130-2 from stretch.

Best regards
Kevin Price

-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-atheros depends on no packages.

firmware-atheros recommends no packages.

Versions of packages firmware-atheros suggests:
ii  initramfs-tools  0.130

-- no debconf information

[toc] | [next] | [standalone]

#63105

I just saw that the upstream maintainer had noted the version numbering
in the very commit that broke my WiFi.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/ath10k/QCA9377/hw1.0?id=56e5de3261877e5ca9df285e0751368c72b0861a

What I've not tried is upstream's latest commit
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/ath10k/QCA9377/hw1.0?id=3e2e5d3c5bce21b4ef5bd89bad604e2be48c73b1
because it's not included in your latest 20190114-1. Would you like me
to give it a shot?

best
Kevin

[toc] | [prev] | [next] | [standalone]

#64029 — Bug#919632: marked as done ("New" firmware instantly crashes on QCA9377)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 06 May 2019 21:33:47 +0000
with message-id <E1hNlF5-0009dG-7e@fasolo.debian.org>
and subject line Bug#919632: fixed in firmware-nonfree 20190502-1
has caused the Debian Bug report #919632,
regarding "New" firmware instantly crashes on QCA9377
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
919632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919632
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#64038 — Bug#919632: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1)

[Multipart message — attachments visible in raw view] — view raw

Dear maintainer,

This didn't fix this bug.

Am 06.05.19 um 23:36 schrieb Debian Bug Tracking System:
> #919632: "New" firmware instantly crashes on QCA9377
> 
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings <ben@decadent.org.uk> by
> replying to this email.
>
> If you
> have further comments please address them to 919632@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Changes:
>  firmware-nonfree (20190502-1) unstable; urgency=medium
>    [ Ben Hutchings ]
>    * atheros: Add Qualcomm Atheros QCA9377 rev 1.0 firmware version
>      WLAN.TF.2.1-00021-QCARMSWP-1 (Closes: #903437, #919632, #927917)

I'm not affected by the only change in

  /lib/firmware/updates/ath10k/QCA9377/hw1.0 ,

which is the addition of

  firmware-6.bin . My QCA9377 loads firmware-5.bin, which has not been
changed since 2018-02-15 (upstream), so it still instantly crashes.
dmesg attached.

best
Kevin

[toc] | [prev] | [next] | [standalone]

#64041 — Bug#919632: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1)

[Multipart message — attachments visible in raw view] — view raw

Control: reopen -1

On Tue, 2019-05-07 at 13:44 +0200, Kevin Price wrote:
> Dear maintainer,
> 
> This didn't fix this bug.
> 
> Am 06.05.19 um 23:36 schrieb Debian Bug Tracking System:
> > #919632: "New" firmware instantly crashes on QCA9377
> > 
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Ben Hutchings <ben@decadent.org.uk> by
> > replying to this email.
> > 
> > If you
> > have further comments please address them to 919632@bugs.debian.org,
> > and the maintainer will reopen the bug report if appropriate.
> > 
> > Changes:
> >  firmware-nonfree (20190502-1) unstable; urgency=medium
> >    [ Ben Hutchings ]
> >    * atheros: Add Qualcomm Atheros QCA9377 rev 1.0 firmware version
> >      WLAN.TF.2.1-00021-QCARMSWP-1 (Closes: #903437, #919632, #927917)
> 
> I'm not affected by the only change in
> 
>   /lib/firmware/updates/ath10k/QCA9377/hw1.0 ,
> 
> which is the addition of
> 
>   firmware-6.bin . My QCA9377 loads firmware-5.bin, which has not been
> changed since 2018-02-15 (upstream), so it still instantly crashes.
> dmesg attached.

OK, sorry.  It looked like the problem in these three bugs was that
newer versions of the driver that preferred firmware-6.bin were
incompatible with firmware-5.bin even though they tried to use it.

Since the older driver version also fails, I suppose I should revert
the previous upstream change to firmware-5.bin.

Ben.

-- 
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.

[toc] | [prev] | [next] | [standalone]

#64047 — Bug#919632: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1)

tags 919632 - upstream
thanks

Dear Ben, thanks a lot for all your time and effort!

tl;dr: Please don't revert. I've found the culprit. See my recommended  
bug fixing procedure near the bottom of this message.

Zitat von Ben Hutchings <ben@decadent.org.uk>:
> It looked like the problem in these three bugs was that
> newer versions of the driver that preferred firmware-6.bin were
> incompatible with firmware-5.bin even though they tried to use it.

Very close. This bug is in fact dependent on the driver version. I'm  
very sorry for not having picked up that clue before, and instead  
havin tried the stretch linux-image 4.9.0 all the time. Your latest  
E-Mail led me to the correct hunch. I'm not certain about the other  
bug reports right now, but your bugfix might take care of all of them.

> Since the older driver version also fails, I suppose I should revert
> the previous upstream change to firmware-5.bin.

No, please don't do that (quite yet), for three reasons:

1. This very change might well have solved some of the other bugs you  
tagged solved.

2. The mere addition of ath10k/QCA9377/hw1.0/firmware-6.bin definitely  
didn't worsen (at least) my situation.

3. But it improved it quite a lot: I just switched linux-image from  
stretch 4.9.0-9-amd64 to stretch-backports 4.19.0-0.bpo.4-amd64, and  
*snap* that made firmware-atheros_20190502-1 work for me, (like a  
charm IDK quite yet, but at least it doesn't instantly crash any more)  
successfully using firmware-6.bin. \o/ Would you like to see my now  
working dmesg, or any other test results? (I'll need a few days before  
I return to broadband land, :-/ and also I've got a lot of AppArmor  
mess to clear up.)

My '3.' makes it look to me like the bug is really a missing  
dependency in firmware-atheros (since 20180518-1) on the specific  
kernel version when the firmware API or the ath10k_pci driver changed;  
somewhere >> 4.9.0 and <= 4.19.0. (Which one, and exactly for which  
drivers IDK, and I won't be able to run a lot of tests on that for a  
few days from now, so please bear with me.)

I strongly recommend the following procedure to fix this bug:

* Leave this bug open for now.
* Leave its severity and title (at least somewhat) the way they are,  
so that other users can easily find the cause.
* Remove its 'upstream' tag. (hereby done, I hope)
* Leave the firmware blobs the way they are in 20190502-1.
* Find out their required minimum driver/kernel version. (possibly  
with my future help)
* Add the missing dependency firmware-atheros -> linux-image  
${version}, and maybe document that in the package description, and/or  
in firmware-.*/README.Debian, and/or wherever you deem appropriate. At  
least the dependency seems important to me for all the present and  
future backports users.
* Close this bug :D

(BTW: Although ath10k_pci is compiled as a module rather than as a  
built-in, reading  
https://www.kernel.org/doc/html/latest/driver-api/firmware/direct-fs-lookup.html#firmware-and-initramfs leads me to believe that it might make sense to include the firmware blob(s) into the initrd along with the module(s). That's not the default behavior at the moment. I strongly expect this to have already been discussed somewhere within debian. @all: Would somebody please point me anywhere near that  
reasoning?)

Again, thanks a lot Ben for all your time and effort! Cheers
Kevin

[toc] | [prev] | [next] | [standalone]

#64048 — Processed: Re: Bug#919632 closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1)

Processing commands for control@bugs.debian.org:

> tags 919632 - upstream
Bug #919632 [firmware-atheros] "New" firmware instantly crashes on QCA9377
Removed tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
919632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919632
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#64050 — Bug#919632: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1)

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 upstream

On Tue, 2019-05-07 at 22:10 +0200, kp@osnanet.de wrote:
> tags 919632 - upstream
> thanks
> 
> Dear Ben, thanks a lot for all your time and effort!
> 
> tl;dr: Please don't revert. I've found the culprit. See my recommended  
> bug fixing procedure near the bottom of this message.
> 
> Zitat von Ben Hutchings <ben@decadent.org.uk>:
> > It looked like the problem in these three bugs was that
> > newer versions of the driver that preferred firmware-6.bin were
> > incompatible with firmware-5.bin even though they tried to use it.
> 
> Very close. This bug is in fact dependent on the driver version. I'm  
> very sorry for not having picked up that clue before, and instead  
> havin tried the stretch linux-image 4.9.0 all the time. Your latest  
> E-Mail led me to the correct hunch. I'm not certain about the other  
> bug reports right now, but your bugfix might take care of all of them.
> 
> > Since the older driver version also fails, I suppose I should revert
> > the previous upstream change to firmware-5.bin.
> 
> No, please don't do that (quite yet), for three reasons:
> 
> 1. This very change might well have solved some of the other bugs you  
> tagged solved.
> 
> 2. The mere addition of ath10k/QCA9377/hw1.0/firmware-6.bin definitely  
> didn't worsen (at least) my situation.

I wasn't proposing to revert that.  Only the earlier change in
firmware-5.bin.

[...]
> * Leave the firmware blobs the way they are in 20190502-1.
> * Find out their required minimum driver/kernel version. (possibly  
> with my future help)
> * Add the missing dependency firmware-atheros -> linux-image  
> ${version}, and maybe document that in the package description, and/or  
> in firmware-.*/README.Debian, and/or wherever you deem appropriate. At  
> least the dependency seems important to me for all the present and  
> future backports users.
[...]

No, that's not the correct approach.  Whenever there is an incompatible
change in a firmware blob, the filename must be changed as well. 
That's why the latest version is called firmware-6.bin.

Ben.

-- 
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.

[toc] | [prev] | [next] | [standalone]

#64040 — Processed: Re: Bug#919632 closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1)

Processing control commands:

> reopen -1
Bug #919632 {Done: Ben Hutchings <ben@decadent.org.uk>} [firmware-atheros] "New" firmware instantly crashes on QCA9377
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions firmware-nonfree/20190502-1.

-- 
919632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919632
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#64049 — Processed: Re: Bug#919632: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#919632: fixed in firmware-nonfree 20190502-1)

Processing control commands:

> tag -1 upstream
Bug #919632 [firmware-atheros] "New" firmware instantly crashes on QCA9377
Added tag(s) upstream.

-- 
919632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919632
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#64592 — Bug#919632: marked as done ("New" firmware instantly crashes on QCA9377)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 28 Jul 2019 17:49:28 +0000
with message-id <E1hrnIW-0003Em-7l@fasolo.debian.org>
and subject line Bug#919632: fixed in firmware-nonfree 20190717-1
has caused the Debian Bug report #919632,
regarding "New" firmware instantly crashes on QCA9377
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
919632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919632
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#64892 — Bug#919632: marked as done ("New" firmware instantly crashes on QCA9377)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Fri, 23 Aug 2019 07:57:01 +0000
with message-id <E1i14RR-00063f-Nt@fasolo.debian.org>
and subject line Bug#919632: fixed in firmware-nonfree 20190114-2
has caused the Debian Bug report #919632,
regarding "New" firmware instantly crashes on QCA9377
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
919632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919632
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web