[Bug 229331] panic: refcount == 0 in in6m_release_deferred()

2018-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229331

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Killer E2500 network driver

2018-06-25 Thread Rodney W. Grimes
> On 24/06/2018 22:29, Rodney W. Grimes wrote:
> >> On 24/06/2018 17:16, Rodney W. Grimes wrote:
>  Hi All,
> 
>  This list states that 10-Stable supports Killer E2500 Gigabit Ethernet
>  controller:
> 
>  https://www.freebsd.org/relnotes/10-STABLE/hardware/support.html
> 
>  However, similar list for 11-Stable doesn't list that driver:
> 
>  https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
> 
>  Does it mean that the driver has been removed, and if yes then why?
> >>> I believe it was a "added" feature in 10 stable, my 11 stable
> >>> alc(4) man page lists the E2500 as supported.
> >>>
> >>>The alc device driver provides support for the following Ethernet
> >>>controllers:
> >>>
> >>>o   Atheros AR8131 PCI Express Gigabit Ethernet controller
> >>>o   Atheros AR8132 PCI Express Fast Ethernet controller
> >>>o   Atheros AR8151 v1.0 PCI Express Gigabit Ethernet controller
> >>>o   Atheros AR8151 v2.0 PCI Express Gigabit Ethernet controller
> >>>o   Atheros AR8152 v1.1 PCI Express Fast Ethernet controller
> >>>o   Atheros AR8152 v2.0 PCI Express Fast Ethernet controller
> >>>o   Atheros AR8161 PCI Express Gigabit Ethernet controller
> >>>o   Atheros AR8162 PCI Express Fast Ethernet controller
> >>>o   Atheros AR8171 PCI Express Gigabit Ethernet controller
> >>>o   Atheros AR8172 PCI Express Fast Ethernet controller
> >>>o   Killer E2200 Gigabit Ethernet controller
> >>>o   Killer E2400 Gigabit Ethernet controller
> >>>o   Killer E2500 Gigabit Ethernet controller
> >>>
> >> Yeah, listing drivers in alc shows support for that card. But the whole
> >> alc driver isn't listed on the hardware support page for 11-Stable. So
> >> wanted to check if it's an omission or it was removed deliberately.
> > Which page are you looking at, it needs fixed.
> >
> > @x230a:/ # ls -lag /boot/kernel/if_alc.ko
> > -r-xr-xr-x  1 root  wheel  84912 Jul 21  2017 /boot/kernel/if_alc.ko
> > @x230a:/ # uname -UK
> > 1101001 1101001
> >
> 
> The one listed in my email:
> 
> https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
> 
> alc(4) isn't listed there.

Thank you, I should of reread the whole of the message before I
asked you to repeat your self.

I have checked the 11.0R 11.1R release notes at:
https://www.freebsd.org/releases/11.0R/relnotes.html
https://www.freebsd.org/releases/11.1R/relnotes.html

and the infact do list alc(4) correctly, so I have sent an internal
mail to Release Engineering so that we can track down why the
release notes at
https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
are not reflecting this.

I suspect this happened in a transition that recently occured 
to the repository location that the release notes are stored in/
generated from.

Thank you for calling this documentation error to our attention.

Regards,
-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


usb ethernet adapter does not work after reboot

2018-06-25 Thread Masachika ISHIZUKA
  Hi.

  I'm using DELL XPS12 notebook pc.
  This machine has not ethernet card and I use AX88179 usb ethernet
adapter.
  This works well on 11.2-RC3 and 12-current after first bootup.
  But if I reboot pc, this adapter is not seen any more.

  So I was using 'shutdown and bootup' instead of reboot.

  I found that I can use this usb ethernet adapter after reboot with
the following sequence .

(1) sync the disks
(2) usbconfig -d ugenX.Y power_off
(3) wait for a few seconds
(4) usbconfig -d ugenX.Y power_off
(5) reboot

I wrote this sequence to shell script as follows.

ugen=`/usr/sbin/usbconfig list | /usr/bin/sed -n 's/^\(ugen[0-9]*\.[0-9]*\): .* 
AX88179\>.*/\1/p'`
/bin/sync
/bin/sync
/bin/sync
/usr/sbin/usbconfig -d $ugen power_off
/bin/sleep 3
/usr/sbin/usbconfig -d $ugen power_off
/sbin/shutdown -r now
-- 
Masachika ISHIZUKA
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Handheld Inkjet Printer with 3.5 Inch Touch Screen

2018-06-25 Thread kelly
Dear Manager,


Good day!


We independently developed a handheld inkjet printer with good quality, which 
is widely used and popular throughout different countries. Hope the below 
product can help you save the costs.


Following is one of our model:
Item: Handheld Inkjet Printer with Solvent Ink (Quick Dry)


- With 3.5 inch touchable screen that you can edit the contents directly via 
screen or imported the contents from U-disk.
- Portable, simple interface and easy to operate.
- It can print on different kinds of materials, such as papers, cartons, 
plastics, glasses, woods, stones, walls, steels pipes, metals, cables, film 
materials, etc.
- It can print Chinese, English letters, numbers, QR code, scan code, barcode, 
batch code, expiry date, time, counter, symbols, logo, marks, small pictures 
etc.
-We have large data store up to 200 messages.
-We have different colors ink: black, red, bule,yellow, white and invisible UV 
light ink.

Any interests please contact us for more information.We can show you our 
brochure and video. Sample are available, too!
 
Thanks and Regards,
--

Kelly Chen
Sales Representative
Shenzhen Swaroniki Technology Co., Ltd. 
Mobile & Whatsapp:86-13266685669
Skype: kelly_3167
Web:www.beshengprinters.com
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Killer E2500 network driver

2018-06-25 Thread Glen Barber
On Mon, Jun 25, 2018 at 07:31:53AM -0700, Rodney W. Grimes wrote:
> > On 24/06/2018 22:29, Rodney W. Grimes wrote:
> > >> On 24/06/2018 17:16, Rodney W. Grimes wrote:
> >  Hi All,
> > 
> >  This list states that 10-Stable supports Killer E2500 Gigabit Ethernet
> >  controller:
> > 
> >  https://www.freebsd.org/relnotes/10-STABLE/hardware/support.html
> > 
> >  However, similar list for 11-Stable doesn't list that driver:
> > 
> >  https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
> > 
> >  Does it mean that the driver has been removed, and if yes then why?
> > >>> I believe it was a "added" feature in 10 stable, my 11 stable
> > >>> alc(4) man page lists the E2500 as supported.
> > >>>
> > >>>The alc device driver provides support for the following Ethernet
> > >>>controllers:
> > >>>
> > >>>o   Atheros AR8131 PCI Express Gigabit Ethernet controller
> > >>>o   Atheros AR8132 PCI Express Fast Ethernet controller
> > >>>o   Atheros AR8151 v1.0 PCI Express Gigabit Ethernet controller
> > >>>o   Atheros AR8151 v2.0 PCI Express Gigabit Ethernet controller
> > >>>o   Atheros AR8152 v1.1 PCI Express Fast Ethernet controller
> > >>>o   Atheros AR8152 v2.0 PCI Express Fast Ethernet controller
> > >>>o   Atheros AR8161 PCI Express Gigabit Ethernet controller
> > >>>o   Atheros AR8162 PCI Express Fast Ethernet controller
> > >>>o   Atheros AR8171 PCI Express Gigabit Ethernet controller
> > >>>o   Atheros AR8172 PCI Express Fast Ethernet controller
> > >>>o   Killer E2200 Gigabit Ethernet controller
> > >>>o   Killer E2400 Gigabit Ethernet controller
> > >>>o   Killer E2500 Gigabit Ethernet controller
> > >>>
> > >> Yeah, listing drivers in alc shows support for that card. But the whole
> > >> alc driver isn't listed on the hardware support page for 11-Stable. So
> > >> wanted to check if it's an omission or it was removed deliberately.
> > > Which page are you looking at, it needs fixed.
> > >
> > > @x230a:/ # ls -lag /boot/kernel/if_alc.ko
> > > -r-xr-xr-x  1 root  wheel  84912 Jul 21  2017 /boot/kernel/if_alc.ko
> > > @x230a:/ # uname -UK
> > > 1101001 1101001
> > >
> > 
> > The one listed in my email:
> > 
> > https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
> > 
> > alc(4) isn't listed there.
> 
> Thank you, I should of reread the whole of the message before I
> asked you to repeat your self.
> 
> I have checked the 11.0R 11.1R release notes at:
> https://www.freebsd.org/releases/11.0R/relnotes.html
> https://www.freebsd.org/releases/11.1R/relnotes.html
> 
> and the infact do list alc(4) correctly, so I have sent an internal
> mail to Release Engineering so that we can track down why the
> release notes at
> https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
> are not reflecting this.
> 
> I suspect this happened in a transition that recently occured 
> to the repository location that the release notes are stored in/
> generated from.
> 

For 11.x, no, this is not the case.  That change was only in 12-CURRENT,
and was not retroactively applied to stable branches due to a problem
that is outstanding with the hardware page generation for 12.

That said, I'll try to track down where exactly this driver went missing
from the hardware page, but it is too late to fix it for the 11.2
release.  It can be noted in an errata entry, however, and a link to the
11-STABLE page once it is fixed there.

Glen



signature.asc
Description: PGP signature


Re: [PATCH]: The 6to4 stf0 interface flapping in/out of tentative in FreeBSD 11

2018-06-25 Thread Viktor Dukhovni



> On Jun 22, 2018, at 1:41 PM, Andrey V. Elsukov  wrote:
> 
> Your change looks reasonable due to IPv6 DAD procedure does check for
> presence of IFF_DRV_RUNNING flag. But actually it seems the right
> solution should be disabling DAD for if_stf(4) interface.
> IPv6 DAD requires that given interface should be multicast capable, but
> for if_stf(4) it is not true.
> Will it help if you use `ifconfig stf0 inet6 no_dad` before assigning
> IPv6 address?

For the record, per off-list email, just disabling DAD was not enough.
Anything else you'd like me to try?

-- 
Viktor.

___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Killer E2500 network driver

2018-06-25 Thread Grzegorz Junka

On 25/06/2018 15:00, Glen Barber wrote:

On Mon, Jun 25, 2018 at 07:31:53AM -0700, Rodney W. Grimes wrote:

On 24/06/2018 22:29, Rodney W. Grimes wrote:

On 24/06/2018 17:16, Rodney W. Grimes wrote:

Hi All,

This list states that 10-Stable supports Killer E2500 Gigabit Ethernet
controller:

https://www.freebsd.org/relnotes/10-STABLE/hardware/support.html

However, similar list for 11-Stable doesn't list that driver:

https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html

Does it mean that the driver has been removed, and if yes then why?

I believe it was a "added" feature in 10 stable, my 11 stable
alc(4) man page lists the E2500 as supported.

The alc device driver provides support for the following Ethernet
controllers:

o   Atheros AR8131 PCI Express Gigabit Ethernet controller
o   Atheros AR8132 PCI Express Fast Ethernet controller
o   Atheros AR8151 v1.0 PCI Express Gigabit Ethernet controller
o   Atheros AR8151 v2.0 PCI Express Gigabit Ethernet controller
o   Atheros AR8152 v1.1 PCI Express Fast Ethernet controller
o   Atheros AR8152 v2.0 PCI Express Fast Ethernet controller
o   Atheros AR8161 PCI Express Gigabit Ethernet controller
o   Atheros AR8162 PCI Express Fast Ethernet controller
o   Atheros AR8171 PCI Express Gigabit Ethernet controller
o   Atheros AR8172 PCI Express Fast Ethernet controller
o   Killer E2200 Gigabit Ethernet controller
o   Killer E2400 Gigabit Ethernet controller
o   Killer E2500 Gigabit Ethernet controller


Yeah, listing drivers in alc shows support for that card. But the whole
alc driver isn't listed on the hardware support page for 11-Stable. So
wanted to check if it's an omission or it was removed deliberately.

Which page are you looking at, it needs fixed.

@x230a:/ # ls -lag /boot/kernel/if_alc.ko
-r-xr-xr-x  1 root  wheel  84912 Jul 21  2017 /boot/kernel/if_alc.ko
@x230a:/ # uname -UK
1101001 1101001


The one listed in my email:

https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html

alc(4) isn't listed there.

Thank you, I should of reread the whole of the message before I
asked you to repeat your self.

I have checked the 11.0R 11.1R release notes at:
https://www.freebsd.org/releases/11.0R/relnotes.html
https://www.freebsd.org/releases/11.1R/relnotes.html

and the infact do list alc(4) correctly, so I have sent an internal
mail to Release Engineering so that we can track down why the
release notes at
https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
are not reflecting this.

I suspect this happened in a transition that recently occured
to the repository location that the release notes are stored in/
generated from.


For 11.x, no, this is not the case.  That change was only in 12-CURRENT,
and was not retroactively applied to stable branches due to a problem
that is outstanding with the hardware page generation for 12.

That said, I'll try to track down where exactly this driver went missing
from the hardware page, but it is too late to fix it for the 11.2
release.  It can be noted in an errata entry, however, and a link to the
11-STABLE page once it is fixed there.

Glen

Great, thanks Glen and Rodney. Am I then to understand that this is a 
documentation issue, rather than the actual driver being removed?


___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Killer E2500 network driver

2018-06-25 Thread Glen Barber
On Mon, Jun 25, 2018 at 08:59:08PM +, Grzegorz Junka wrote:
> On 25/06/2018 15:00, Glen Barber wrote:
> > On Mon, Jun 25, 2018 at 07:31:53AM -0700, Rodney W. Grimes wrote:
> > > > On 24/06/2018 22:29, Rodney W. Grimes wrote:
> > > > > > On 24/06/2018 17:16, Rodney W. Grimes wrote:
> > > > > > > > Hi All,
> > > > > > > > 
> > > > > > > > This list states that 10-Stable supports Killer E2500 Gigabit 
> > > > > > > > Ethernet
> > > > > > > > controller:
> > > > > > > > 
> > > > > > > > https://www.freebsd.org/relnotes/10-STABLE/hardware/support.html
> > > > > > > > 
> > > > > > > > However, similar list for 11-Stable doesn't list that driver:
> > > > > > > > 
> > > > > > > > https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
> > > > > > > > 
> > > > > > > > Does it mean that the driver has been removed, and if yes then 
> > > > > > > > why?
> > > > > > > I believe it was a "added" feature in 10 stable, my 11 stable
> > > > > > > alc(4) man page lists the E2500 as supported.
> > > > > > > 
> > > > > > > The alc device driver provides support for the following 
> > > > > > > Ethernet
> > > > > > > controllers:
> > > > > > > 
> > > > > > > o   Atheros AR8131 PCI Express Gigabit Ethernet controller
> > > > > > > o   Atheros AR8132 PCI Express Fast Ethernet controller
> > > > > > > o   Atheros AR8151 v1.0 PCI Express Gigabit Ethernet 
> > > > > > > controller
> > > > > > > o   Atheros AR8151 v2.0 PCI Express Gigabit Ethernet 
> > > > > > > controller
> > > > > > > o   Atheros AR8152 v1.1 PCI Express Fast Ethernet 
> > > > > > > controller
> > > > > > > o   Atheros AR8152 v2.0 PCI Express Fast Ethernet 
> > > > > > > controller
> > > > > > > o   Atheros AR8161 PCI Express Gigabit Ethernet controller
> > > > > > > o   Atheros AR8162 PCI Express Fast Ethernet controller
> > > > > > > o   Atheros AR8171 PCI Express Gigabit Ethernet controller
> > > > > > > o   Atheros AR8172 PCI Express Fast Ethernet controller
> > > > > > > o   Killer E2200 Gigabit Ethernet controller
> > > > > > > o   Killer E2400 Gigabit Ethernet controller
> > > > > > > o   Killer E2500 Gigabit Ethernet controller
> > > > > > > 
> > > > > > Yeah, listing drivers in alc shows support for that card. But the 
> > > > > > whole
> > > > > > alc driver isn't listed on the hardware support page for 11-Stable. 
> > > > > > So
> > > > > > wanted to check if it's an omission or it was removed deliberately.
> > > > > Which page are you looking at, it needs fixed.
> > > > > 
> > > > > @x230a:/ # ls -lag /boot/kernel/if_alc.ko
> > > > > -r-xr-xr-x  1 root  wheel  84912 Jul 21  2017 /boot/kernel/if_alc.ko
> > > > > @x230a:/ # uname -UK
> > > > > 1101001 1101001
> > > > > 
> > > > The one listed in my email:
> > > > 
> > > > https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
> > > > 
> > > > alc(4) isn't listed there.
> > > Thank you, I should of reread the whole of the message before I
> > > asked you to repeat your self.
> > > 
> > > I have checked the 11.0R 11.1R release notes at:
> > > https://www.freebsd.org/releases/11.0R/relnotes.html
> > > https://www.freebsd.org/releases/11.1R/relnotes.html
> > > 
> > > and the infact do list alc(4) correctly, so I have sent an internal
> > > mail to Release Engineering so that we can track down why the
> > > release notes at
> > > https://www.freebsd.org/relnotes/11-STABLE/hardware/support.html
> > > are not reflecting this.
> > > 
> > > I suspect this happened in a transition that recently occured
> > > to the repository location that the release notes are stored in/
> > > generated from.
> > > 
> > For 11.x, no, this is not the case.  That change was only in 12-CURRENT,
> > and was not retroactively applied to stable branches due to a problem
> > that is outstanding with the hardware page generation for 12.
> > 
> > That said, I'll try to track down where exactly this driver went missing
> > from the hardware page, but it is too late to fix it for the 11.2
> > release.  It can be noted in an errata entry, however, and a link to the
> > 11-STABLE page once it is fixed there.
> > 
> > Glen
> > 
> Great, thanks Glen and Rodney. Am I then to understand that this is a
> documentation issue, rather than the actual driver being removed?

That is correct.

Glen



signature.asc
Description: PGP signature


unloading pf causes desktop system to freeze since ~ r335381

2018-06-25 Thread Dave Cottlehuber
[cross-posting for advice on general debugging + network-specific thoughts]

TLDR since a week or so, probably around r335381 I can reliably get my machine 
to hang*** by unloading pf, while there's network traffic (e.g. video streaming 
or rsync) and waiting a minute or two  I still see it with r335576 a few times 
today. config & logs below, h/w is intel xeon v2667v4 on supermicro X10SRA-F 
dual igb nics.

However each time there's no crashdump, & the usual ctrl-alt-esc does't work 
either.

I'm a bit lost as to what I can do here to capture something useful. A few 
minutes later, the machine spontaneously reboots, I assume due to a h/w 
watchdog kicking up, and  there is no crashdump info present in /var/crash/ as 
I'd normally expect.

***hang means simultaneously:

- keyboard is unresponsive (capslock/numlock keys don't cause keyboard LEDs to 
toggle state)
- control-alt-esc doesn't work to get to the debugger
- music playing via mpd to an external USB DAC stops
- network sessions & tap interfaces fail
- X session contents freeze but remain visible

Is there some way I can get a kernel dump even though the system has fully hung?

- dmesg, rc.conf, ifconfig,  sysctls etc https://git.io/f4HQZ
- supermicro X10SRA-F bios v2.0a settings https://git.io/f4HQb


A+
Dave
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: usb ethernet adapter does not work after reboot

2018-06-25 Thread Kevin Oberman
On Mon, Jun 25, 2018 at 7:45 AM, Masachika ISHIZUKA 
wrote:

>   Hi.
>
>   I'm using DELL XPS12 notebook pc.
>   This machine has not ethernet card and I use AX88179 usb ethernet
> adapter.
>   This works well on 11.2-RC3 and 12-current after first bootup.
>   But if I reboot pc, this adapter is not seen any more.
>
>   So I was using 'shutdown and bootup' instead of reboot.
>
>   I found that I can use this usb ethernet adapter after reboot with
> the following sequence .
>
> (1) sync the disks
> (2) usbconfig -d ugenX.Y power_off
> (3) wait for a few seconds
> (4) usbconfig -d ugenX.Y power_off
> (5) reboot
>
> I wrote this sequence to shell script as follows.
>
> ugen=`/usr/sbin/usbconfig list | /usr/bin/sed -n
> 's/^\(ugen[0-9]*\.[0-9]*\): .* AX88179\>.*/\1/p'`
> /bin/sync
> /bin/sync
> /bin/sync
> /usr/sbin/usbconfig -d $ugen power_off
> /bin/sleep 3
> /usr/sbin/usbconfig -d $ugen power_off
> /sbin/shutdown -r now
> --
> Masachika ISHIZUKA
>

Many people seem to not understand the difference between "shutdown -r" and
"reboot". For most cases, it makes little difference, but in some the
difference can be very significant.

reboot(8) is a brute force shutdown. It does the bare minimum to shutdown
the system fairly safely. It's step up from pulling the plug, but not by
much. It is fine from a standalone system, but is really ill advised to use
it from multi-user mode. It does not run the "stop" scripts in all of the
rc.d scripts to cleanly stop things. "shutdown -r" does run all rc.d
scripts that contain "stop" routines. This is especially critical for
database users to avoid corrupt DBs, but many other things also work best
if cleanly stopped before the system goes down.

BTW, the triple "sync" is a waste of... well, not much except your time in
typing it into your script. The rule to sync discs three times assumes that
you are actually typing it. It is to allow enough time for the file
system(s) to complete syncing before the system is halted (halt(8)) or
power is removed. Both reboot(8) and shutdown(8) now take care of this.
Only the first sync(8) really does anything. Typing it three times on a
teletype takes long enough for metadata to be written.

The man page for sync(8) really needs updating. It is unchanged other than
fixing wording and formatting since 4.4-lite and probably that was largely
unchanged from AT&T V4. I probably should open a ticket.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"