On Mon, Jun 8, 2020 at 1:48 PM Stefan Sperling wrote:
>
> On Fri, May 22, 2020 at 01:48:28PM -0400, sven falempin wrote:
> > After a few days ... (free size too small 288 < 1024 /2 )
> >
> > Maybe this can help make the driver better.
> >
> > printf '%x\n' $((0x350+0xf7)) ; grep -A2 'if_iwx.c:51
On Fri, May 22, 2020 at 01:48:28PM -0400, sven falempin wrote:
> After a few days ... (free size too small 288 < 1024 /2 )
>
> Maybe this can help make the driver better.
>
> printf '%x\n' $((0x350+0xf7)) ; grep -A2 'if_iwx.c:515' /tmp/iwx.dis
> 447
> /usr/src/sys/dev/pci/if_iwx.c:515
> 4
On Fri, May 15, 2020 at 11:17 AM Stefan Sperling wrote:
> On Fri, May 15, 2020 at 11:11:44AM -0400, sven falempin wrote:
> > Index: if_iwx.c
> > ===
> > RCS file: /cvs/src/sys/dev/pci/if_iwx.c,v
> > retrieving revision 1.11
> > diff
On Fri, May 15, 2020 at 11:11:44AM -0400, sven falempin wrote:
> Index: if_iwx.c
> ===
> RCS file: /cvs/src/sys/dev/pci/if_iwx.c,v
> retrieving revision 1.11
> diff -u -p -r1.11 if_iwx.c
> --- if_iwx.c29 Apr 2020 13:13:30 -
On Thu, May 14, 2020 at 5:55 AM Stefan Sperling wrote:
> On Wed, May 13, 2020 at 07:55:02PM -0400, sven falempin wrote:
> > 'good news'
> >
> > I build a custom kernel with the DEBUG flag for the driver
>
> > I 'works' ,
>
> This means that the driver is doing something too fast on your hardware,
On Wed, May 13, 2020 at 07:55:02PM -0400, sven falempin wrote:
> 'good news'
>
> I build a custom kernel with the DEBUG flag for the driver
> I 'works' ,
This means that the driver is doing something too fast on your hardware,
and some miscommunication happens with the card as a result.
One way
'good news'
I build a custom kernel with the DEBUG flag for the driver
ugen0 at uhub3 port 3 "Intel product 0x0029" rev 2.01/0.01 addr 2
iwx_cmd_done: command 0x88 done
iwx_cmd_done: command 0x88 done
iwx_cmd_done: command 0x88 done
iwx_cmd_done: command 0x88 done
iwx_cmd_done: command 0x88 done
On Wed, May 13, 2020 at 2:24 PM Stuart Henderson wrote:
>
> On 2020/05/13 13:46, sven falempin wrote:
> > *Please*
> > advise how to squeeze more information to thwart that problem.
>
> If I had a card using a newly developed driver that was doing that,
> I would remove the card, offer to send it
On 2020/05/13 13:46, sven falempin wrote:
> *Please*
> advise how to squeeze more information to thwart that problem.
If I had a card using a newly developed driver that was doing that,
I would remove the card, offer to send it to somebody working on the
driver if they want it, and replace it with
>
> OpenBSD 6.7 (GENERIC.MP) #182: Thu May 7 11:11:58 MDT 2020
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 7975399424 (7605MB)
> avail mem = 7721070592 (7363MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SM
On Mon, May 11, 2020 at 5:52 AM Stefan Sperling wrote:
> On Sun, May 10, 2020 at 04:17:46PM -0400, sven falempin wrote:
> > On Sun, May 10, 2020 at 4:51 AM Stefan Sperling wrote:
> >
> > > On Sat, May 09, 2020 at 04:23:08PM -0400, sven falempin wrote:
> > > > "no config, interface is down", Did
On Sun, May 10, 2020 at 04:17:46PM -0400, sven falempin wrote:
> On Sun, May 10, 2020 at 4:51 AM Stefan Sperling wrote:
>
> > On Sat, May 09, 2020 at 04:23:08PM -0400, sven falempin wrote:
> > > "no config, interface is down", Did not do anything special,
> > > upgrade => Plug card => boot => cra
On Sun, May 10, 2020 at 4:51 AM Stefan Sperling wrote:
> On Sat, May 09, 2020 at 04:23:08PM -0400, sven falempin wrote:
> > "no config, interface is down", Did not do anything special,
> > upgrade => Plug card => boot => crash
>
> > I tested with the intel firmware it does the same.
>
> I'm sorry
On Sat, May 09, 2020 at 04:23:08PM -0400, sven falempin wrote:
> "no config, interface is down", Did not do anything special,
> upgrade => Plug card => boot => crash
> I tested with the intel firmware it does the same.
I'm sorry, but there is really not enough information in your messages
that wo
On Sat, May 9, 2020 at 4:14 AM Stefan Sperling wrote:
> On Fri, May 08, 2020 at 11:51:50AM -0400, sven falempin wrote:
> > I upgraded to 6.7 - beta a tftp server i use
> >
> > Not much to report as the device is basic but i wanted to test some wifi
> on
> > it.
> >
> > iwx0 at pci8 dev 0 function
On Fri, May 08, 2020 at 11:51:50AM -0400, sven falempin wrote:
> I upgraded to 6.7 - beta a tftp server i use
>
> Not much to report as the device is basic but i wanted to test some wifi on
> it.
>
> iwx0 at pci8 dev 0 function 0 "Intel Wi-Fi 6 AX200" rev 0x1a, msix
>
> The firmware crashes at s
I upgraded to 6.7 - beta a tftp server i use
Not much to report as the device is basic but i wanted to test some wifi on
it.
iwx0 at pci8 dev 0 function 0 "Intel Wi-Fi 6 AX200" rev 0x1a, msix
The firmware crashes at start, no config down:
iwx0: dumping device error log
iwx0: Start Error Log Dum
17 matches
Mail list logo
