Marco Scholz [t...@disroot.org] wrote:
> Hello.
> My laptop (Lenovo Thinkpad T495s AMD Ryzen) reports an iwm0 fatal
> firmware error. I'm running 6.9 #29.
> System gets quite hot, systat shows 40-50% interrupt while idling.
> Networking works fine.
>
> Anybody else ha
On Mon, May 24, 2021 at 02:35:02PM +0200, Marco Scholz wrote:
> Hello.
> My laptop (Lenovo Thinkpad T495s AMD Ryzen) reports an iwm0 fatal
> firmware error. I'm running 6.9 #29.
> System gets quite hot, systat shows 40-50% interrupt while idling.
> Networking works fine.
>
Hello.
My laptop (Lenovo Thinkpad T495s AMD Ryzen) reports an iwm0 fatal
firmware error. I'm running 6.9 #29.
System gets quite hot, systat shows 40-50% interrupt while idling.
Networking works fine.
Anybody else has this issue?
Regards, Marco.
OpenBSD 6.9-current (GENERIC.MP) #29: Fri M
On 24 Sep 12:24, Jan Stary wrote:
> On Sep 24 11:36:24, h...@stare.cz wrote:
> > This is 6.8-beta/amd64 on a Dell Latitude E5570 (dmesg below).
> > iwm stopped working, saying
> >
> > iwm0: hw rev 0x200, fw ver 34.0.1, address e4:a4:71:40:21:08
> > iwm0:
4.0.1, address e4:a4:71:40:21:08
> > > iwm0: fatal firmware error
> > > iwm0: could not remove MAC context (error 35)
> > > iwm0: fatal firmware error
> > > iwm0: could not remove MAC context (error 35)
> > > iwm0: fatal firmware error
> > >
On 2020-09-24, Jan Stary wrote:
> This is 6.8-beta/amd64 on a Dell Latitude E5570 (dmesg below).
> iwm stopped working, saying
>
> iwm0: hw rev 0x200, fw ver 34.0.1, address e4:a4:71:40:21:08
> iwm0: fatal firmware error
> iwm0: could not remove MAC contex
On Sep 24 11:36:24, h...@stare.cz wrote:
> This is 6.8-beta/amd64 on a Dell Latitude E5570 (dmesg below).
> iwm stopped working, saying
>
> iwm0: hw rev 0x200, fw ver 34.0.1, address e4:a4:71:40:21:08
> iwm0: fatal firmware error
> iwm0: could not remove MAC
This is 6.8-beta/amd64 on a Dell Latitude E5570 (dmesg below).
iwm stopped working, saying
iwm0: hw rev 0x200, fw ver 34.0.1, address e4:a4:71:40:21:08
iwm0: fatal firmware error
iwm0: could not remove MAC context (error 35)
iwm0: fatal firmware error
iwm0
On Mon, May 4, 2015 at 6:10 AM, Stefan Sperling wrote:
>> Is the following thread of any use:
>>
>> http://openbsd-archive.7691.n7.nabble.com/iwm0-fatal-firmware-error-on-current-td267434.html
>
> That might be it. Maximilian, can you please try this patch which was
>
On Mon, May 04, 2015 at 08:56:08AM +0100, Dennis Davis wrote:
> > iwm0: hw rev: 0x140, fw ver 25.228 (API ver 9), address f8:16:54:dd:a7:0c
> > iwm0: fatal firmware error
> > iwm0: could not initiate scan
>
> Don't have an iwm interface. But is the firmware ins
On Mon, 4 May 2015, Maximilian Pichler wrote:
> From: Maximilian Pichler
> To: misc@openbsd.org
> Date: Mon, 4 May 2015 06:19:13
> Subject: iwm0: fatal firmware error / could not initiate scan
>
> I'm getting these console errors on startup and each time I run
> &quo
Hi,
I'm getting these console errors on startup and each time I run
"ifconfig iwm0 scan":
iwm0: fatal firmware error
iwm0: could not initiate scan
Not sure how to diagnose the problem better. I tried rebooting, but to
no avail. Full dmesg below.
Best,
Max
OpenBSD 5.7 (GENERI
On Sun, Mar 22, 2015 at 11:03 PM, Jonathan Gray wrote:
> On Sun, Mar 22, 2015 at 06:27:19PM +0100, Mattieu Baptiste wrote:
>> On Sun, Mar 22, 2015 at 2:06 PM, Jonathan Gray wrote:
>> > On Sun, Mar 22, 2015 at 06:49:33AM -0400, Ted Unangst wrote:
>> >> Jonathan Gray wrote:
>> >> > On Sun, Mar 22,
On Sun, Mar 22, 2015 at 06:27:19PM +0100, Mattieu Baptiste wrote:
> On Sun, Mar 22, 2015 at 2:06 PM, Jonathan Gray wrote:
> > On Sun, Mar 22, 2015 at 06:49:33AM -0400, Ted Unangst wrote:
> >> Jonathan Gray wrote:
> >> > On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
> >> > >
> >>
On Sun, Mar 22, 2015 at 2:06 PM, Jonathan Gray wrote:
> On Sun, Mar 22, 2015 at 06:49:33AM -0400, Ted Unangst wrote:
>> Jonathan Gray wrote:
>> > On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
>> > >
>> > > If the firmare image is not present at boot, no interface is created.
>>
On Sun, Mar 22, 2015 at 06:49:33AM -0400, Ted Unangst wrote:
> Jonathan Gray wrote:
> > On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
> > >
> > > If the firmare image is not present at boot, no interface is created.
> > > After installing the firmware with fw_update (which succe
Jonathan Gray wrote:
> On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
> >
> > If the firmare image is not present at boot, no interface is created.
> > After installing the firmware with fw_update (which succeeds because
> > it looks for "iwm" in dmesg not ifconfig) there is no w
On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
> On Sun, Mar 22, 2015 at 01:45:45PM +1100, Jonathan Gray wrote:
> > Try the following.
>
> This diff re-introduces an unrelated problem fixed in r1.7.
>
> Interface attachment is moved back to the attach-hook, and the driver
> trie
On Sun, Mar 22, 2015 at 01:45:45PM +1100, Jonathan Gray wrote:
> Try the following.
This diff re-introduces an unrelated problem fixed in r1.7.
Interface attachment is moved back to the attach-hook, and the driver
tries to load the firmware from disk before creating an interface.
If the firmare
On Thu, Mar 19, 2015 at 08:20:41PM +1100, Jonathan Gray wrote:
> On Thu, Mar 19, 2015 at 09:59:39AM +0100, Mattieu Baptiste wrote:
> > On Thu, Mar 19, 2015 at 9:09 AM, Jonathan Gray wrote:
> > >> It doesn't change anything.
> > >> As soon as I set an address on the interface (manually or with
> >
On Thu, Mar 19, 2015 at 09:59:39AM +0100, Mattieu Baptiste wrote:
> On Thu, Mar 19, 2015 at 9:09 AM, Jonathan Gray wrote:
> >> It doesn't change anything.
> >> As soon as I set an address on the interface (manually or with
> >> dhclient), "mode 11g" is resetted and the errors in the logs are the
>
On Thu, Mar 19, 2015 at 9:09 AM, Jonathan Gray wrote:
>> It doesn't change anything.
>> As soon as I set an address on the interface (manually or with
>> dhclient), "mode 11g" is resetted and the errors in the logs are the
>> same.
>
> Can you include the output of pcidump -v?
>
> It's possible yo
On Thu, Mar 19, 2015 at 08:50:11AM +0100, Mattieu Baptiste wrote:
> On Thu, Mar 19, 2015 at 12:38 AM, Stefan Sperling wrote:
> >> Ok, so I tried reverting one by one every commit. Starting with rev.
> >> 1.33 of if_iwm.c, the interface cannot be brought up (no carrier).
> >> With rev. 1.32, the co
On Thu, Mar 19, 2015 at 12:38 AM, Stefan Sperling wrote:
>> Ok, so I tried reverting one by one every commit. Starting with rev.
>> 1.33 of if_iwm.c, the interface cannot be brought up (no carrier).
>> With rev. 1.32, the connection is OK and rather stable.
>>
>> My AP is capable of 802.11a/b/g/n
On Wed, Mar 18, 2015 at 10:45:16PM +0100, Mattieu Baptiste wrote:
> On Wed, Mar 18, 2015 at 7:01 PM, Stefan Sperling wrote:
> > On Wed, Mar 18, 2015 at 06:31:03PM +0100, Mattieu Baptiste wrote:
> >> Anyone seeing this?
> >
> > Yes, all the time.
> >
> >> I'll try to find this night the commit whic
On Wed, Mar 18, 2015 at 7:01 PM, Stefan Sperling wrote:
> On Wed, Mar 18, 2015 at 06:31:03PM +0100, Mattieu Baptiste wrote:
>> Anyone seeing this?
>
> Yes, all the time.
>
>> I'll try to find this night the commit which is
>> causing this regression.
>
> If there was particular commit that made it
On Wed, Mar 18, 2015 at 06:31:03PM +0100, Mattieu Baptiste wrote:
> Anyone seeing this?
Yes, all the time.
> I'll try to find this night the commit which is
> causing this regression.
If there was particular commit that made it much worse, that would
be good to know.
But I believe this problem
54:55 westvleteren /bsd: iwm0: fatal firmware error
Mar 18 17:54:56 westvleteren /bsd: iwm0: could not initiate scan
Here is a dmesg:
OpenBSD 5.7-current (GENERIC.MP) #893: Sun Mar 15 19:04:07 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3951230976 (3
28 matches
Mail list logo
