On Tue, Oct 11, 2016 at 11:32:27PM +0200, Jan Stary wrote:
> On Oct 06 12:46:21, s...@stsp.name wrote:
> > Disable the detailed fatal firmware error log in iwn(4) by default.
>
> These are my iwm errors of today
> on a Dell Latitude E5570.
> I sure don't know what to do with them,
> but I'm glad
On Oct 06 12:46:21, s...@stsp.name wrote:
> Disable the detailed fatal firmware error log in iwn(4) by default.
These are my iwm errors of today
on a Dell Latitude E5570.
Oct 11 16:26:56 dell /bsd: iwm0: fatal firmware error
Oct 11 16:26:56 dell /bsd: iwm0: device timeout
Oct 11 16:26:56 dell /bs
> Date: Thu, 6 Oct 2016 12:46:21 +0200
> From: Stefan Sperling
>
> Disable the detailed fatal firmware error log in iwn(4) by default.
You're the best judge on how useful this information is.
ok kettenis@
> Index: if_iwn.c
> ===
>
Disable the detailed fatal firmware error log in iwn(4) by default.
Index: if_iwn.c
===
RCS file: /cvs/src/sys/dev/pci/if_iwn.c,v
retrieving revision 1.172
diff -u -p -r1.172 if_iwn.c
--- if_iwn.c5 Sep 2016 08:18:18 - 1.
Stefan Sperling wrote:
> On Fri, Feb 05, 2016 at 01:23:18AM -0500, Michael McConville wrote:
> > When forcing my laptop to swap, I almost immediately got the following
> > firmware error. I'm not sure whether this is expected. Restarting the
> > interface brought things back to normal.
> >
> > dme
On Fri, Feb 05, 2016 at 01:23:18AM -0500, Michael McConville wrote:
> When forcing my laptop to swap, I almost immediately got the following
> firmware error. I'm not sure whether this is expected. Restarting the
> interface brought things back to normal.
>
> dmesg follows.
Looks like the firmwar
When forcing my laptop to swap, I almost immediately got the following
firmware error. I'm not sure whether this is expected. Restarting the
interface brought things back to normal.
dmesg follows.
Feb 5 01:19:04 thinkpad /bsd: iwn0: fatal firmware error
Feb 5 01:19:04 thinkpad /bsd: firmware er
On Tue, Jan 12, 2016 at 11:59 +0100, Stefan Sperling wrote:
> On Sat, Jan 09, 2016 at 10:25:45PM +0100, Stefan Sperling wrote:
> > I've run into an issue where iwn(4) fails to init the hardware.
> >
> > Running 'ifconfig iwn0 scan' resulted in:
> >
> > setting configuration
> > iwn0: fatal firmwa
On Tue, Jan 12, 2016 at 11:59:08AM +0100, Stefan Sperling wrote:
> On Sat, Jan 09, 2016 at 10:25:45PM +0100, Stefan Sperling wrote:
> > I've run into an issue where iwn(4) fails to init the hardware.
> >
> > Running 'ifconfig iwn0 scan' resulted in:
> >
> > setting configuration
> > iwn0: fatal f
Stefan Sperling wrote:
> I've run into an issue where iwn(4) fails to init the hardware.
>
> Running 'ifconfig iwn0 scan' resulted in:
>
> setting configuration
> iwn0: fatal firmware error
> firmware error log:
> error type = "SYSASSERT" (0x0005)
> program counter = 0x00022088
> s
On Sat, Jan 09, 2016 at 10:25:45PM +0100, Stefan Sperling wrote:
> I've run into an issue where iwn(4) fails to init the hardware.
>
> Running 'ifconfig iwn0 scan' resulted in:
>
> setting configuration
> iwn0: fatal firmware error
> firmware error log:
> error type = "SYSASSERT" (0x00
I've run into an issue where iwn(4) fails to init the hardware.
Running 'ifconfig iwn0 scan' resulted in:
setting configuration
iwn0: fatal firmware error
firmware error log:
error type = "SYSASSERT" (0x0005)
program counter = 0x00022088
source line = 0x00A4
error data
12 matches
Mail list logo
