Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

[Yuri]

On 07/03/18 18:13, Rodney W. Grimes wrote:

Do you get the same failure condition if you use the
wpa_supplicant from the base system?



Same failure with the base wpa_supplicant.

Creating wlan0 by hand helps, but this should happen automatically. 
restarting devd service also helps.



I think wlan0 creation happens before wpa_supplicant due to the 
instruction 'wlans_run0="wlan0"'.


Something changed in /etc/network.subr or /etc/rc.d/netif or in devd or 
its configuration.


It definitely did create the run0 interface before, and now it doesn't.


Yuri



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

Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

[Linus Sundqvist]

Hi,

I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64 12.0 
disk1 ISO (20180628) using UEFI on a Dell PowerEdge R430 by getting this error:
https://imgur.com/a/Idljfhm

The bootonly ISOs seems to show the same error message.

Changing the server to boot via BIOS loads the setup correctly, however, I want 
to use UEFI on all our servers, which I have done before.

The 11.1 ISO boots without any trouble at all using both UEFI and BIOS.

I was helped by koobs in #freebsd @ Freenode who asked me to send an e-mail 
this way and linking to these commits as a reference:

https://reviews.freebsd.org/D13784
https://svnweb.freebsd.org/base?view=revision&revision=332416

So far I've tried to UEFI boot the 11.2 ISO and 12.0 ISO with the following 
Dell PowerEdge models without success:

R440
R630
R430
FC430
R330
R620
R420
R610

-- 
Med vänlig hälsning/Best Regards
Linus Sundqvist
System Engineer, Loopia AB



signature.asc
Description: OpenPGP digital signature

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

[Toomas Soome]

Can you post lsdev -v output?

Also, could you try ls command? Like, ls cd0:   

Rgds,
Toomas

Sent from my iPhone

> On 4 Jul 2018, at 12:28, Linus Sundqvist  wrote:
> 
> Hi,
> 
> I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64 
> 12.0 disk1 ISO (20180628) using UEFI on a Dell PowerEdge R430 by getting this 
> error:
> https://imgur.com/a/Idljfhm
> 
> The bootonly ISOs seems to show the same error message.
> 
> Changing the server to boot via BIOS loads the setup correctly, however, I 
> want to use UEFI on all our servers, which I have done before.
> 
> The 11.1 ISO boots without any trouble at all using both UEFI and BIOS.
> 
> I was helped by koobs in #freebsd @ Freenode who asked me to send an e-mail 
> this way and linking to these commits as a reference:
> 
> https://reviews.freebsd.org/D13784
> https://svnweb.freebsd.org/base?view=revision&revision=332416
> 
> So far I've tried to UEFI boot the 11.2 ISO and 12.0 ISO with the following 
> Dell PowerEdge models without success:
> 
> R440
> R630
> R430
> FC430
> R330
> R620
> R420
> R610
> 
> -- 
> Med vänlig hälsning/Best Regards
> Linus Sundqvist
> System Engineer, Loopia AB
> 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

[Linus Sundqvist]

Hi,

Sure, while using the 12.0 ISO here is lsdev -v and ls cd0:
https://imgur.com/RmYpg7u

and here is ls cd1:
https://imgur.com/FPsixOw

Med vänlig hälsning/Best Regards
Linus Sundqvist
System Engineer, Loopia AB

On 04/07/18 15:08, Toomas Soome wrote:
> Can you post lsdev -v output?
> 
> Also, could you try ls command? Like, ls cd0:   
> 
> Rgds,
> Toomas
> 
> Sent from my iPhone
> 
>> On 4 Jul 2018, at 12:28, Linus Sundqvist  wrote:
>>
>> Hi,
>>
>> I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64 
>> 12.0 disk1 ISO (20180628) using UEFI on a Dell PowerEdge R430 by getting 
>> this error:
>> https://imgur.com/a/Idljfhm
>>
>> The bootonly ISOs seems to show the same error message.
>>
>> Changing the server to boot via BIOS loads the setup correctly, however, I 
>> want to use UEFI on all our servers, which I have done before.
>>
>> The 11.1 ISO boots without any trouble at all using both UEFI and BIOS.
>>
>> I was helped by koobs in #freebsd @ Freenode who asked me to send an e-mail 
>> this way and linking to these commits as a reference:
>>
>> https://reviews.freebsd.org/D13784
>> https://svnweb.freebsd.org/base?view=revision&revision=332416
>>
>> So far I've tried to UEFI boot the 11.2 ISO and 12.0 ISO with the following 
>> Dell PowerEdge models without success:
>>
>> R440
>> R630
>> R430
>> FC430
>> R330
>> R620
>> R420
>> R610
>>
>> -- 
>> Med vänlig hälsning/Best Regards
>> Linus Sundqvist
>> System Engineer, Loopia AB
>>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 



signature.asc
Description: OpenPGP digital signature

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

[Rodney W. Grimes]

[ Charset UTF-8 unsupported, converting... ]
> On 07/03/18 18:13, Rodney W. Grimes wrote:
> > Do you get the same failure condition if you use the
> > wpa_supplicant from the base system?
> 
> 
> Same failure with the base wpa_supplicant.
> 
> Creating wlan0 by hand helps, but this should happen automatically. 
> restarting devd service also helps.
> 
> 
> I think wlan0 creation happens before wpa_supplicant due to the 
> instruction 'wlans_run0="wlan0"'.
> 
> Something changed in /etc/network.subr or /etc/rc.d/netif or in devd or 
> its configuration.

Devd/devmatch is one of the largest changes recently,
it could be something in that code path.

Do you get the if_run.ko module loaded?  What does kldstat show
immediately after boot and before you try to "fix" anything with
ifconfig.


> It definitely did create the run0 interface before, and now it doesn't.

I wonder if the kernel module is no longer loading...


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

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

[Rodney W. Grimes]

> Hi,
> 
> I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64 
> 12.0 disk1 ISO (20180628) using UEFI on a Dell PowerEdge R430 by getting this 
> error:
> https://imgur.com/a/Idljfhm
> 
> The bootonly ISOs seems to show the same error message.

Are you booting from a USB thumb drive,
an actual CD drive,
or the emulated CD drive from a Dell DRAC?

It appears that you have the boot media in cd1: not cd0:,
I am not sure the code handles this well.

> 
> Changing the server to boot via BIOS loads the setup correctly, however, I 
> want to use UEFI on all our servers, which I have done before.
> 
> The 11.1 ISO boots without any trouble at all using both UEFI and BIOS.

Does it show you booted from cd1:?

> 
> I was helped by koobs in #freebsd @ Freenode who asked me to send an e-mail 
> this way and linking to these commits as a reference:
> 
> https://reviews.freebsd.org/D13784
> https://svnweb.freebsd.org/base?view=revision&revision=332416
> 
> So far I've tried to UEFI boot the 11.2 ISO and 12.0 ISO with the following 
> Dell PowerEdge models without success:
> 
> R440
> R630
> R430
> FC430
> R330
> R620
> R420
> R610

Try the following at the OK prompt:
OK  load cd1:/boot/kernel/kernel
OK  boot


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

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

[Toomas Soome]

set currdev=cd1:
include /boot/loader.rc

This should give menu/boot.

Rgds,
Toomas

Sent from my iPhone

> On 4 Jul 2018, at 16:25, Linus Sundqvist  wrote:
> 
> Hi,
> 
> Sure, while using the 12.0 ISO here is lsdev -v and ls cd0:
> https://imgur.com/RmYpg7u
> 
> and here is ls cd1:
> https://imgur.com/FPsixOw
> 
> Med vänlig hälsning/Best Regards
> Linus Sundqvist
> System Engineer, Loopia AB
> 
>> On 04/07/18 15:08, Toomas Soome wrote:
>> Can you post lsdev -v output?
>> 
>> Also, could you try ls command? Like, ls cd0:   
>> 
>> Rgds,
>> Toomas
>> 
>> Sent from my iPhone
>> 
>>> On 4 Jul 2018, at 12:28, Linus Sundqvist  wrote:
>>> 
>>> Hi,
>>> 
>>> I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64 
>>> 12.0 disk1 ISO (20180628) using UEFI on a Dell PowerEdge R430 by getting 
>>> this error:
>>> https://imgur.com/a/Idljfhm
>>> 
>>> The bootonly ISOs seems to show the same error message.
>>> 
>>> Changing the server to boot via BIOS loads the setup correctly, however, I 
>>> want to use UEFI on all our servers, which I have done before.
>>> 
>>> The 11.1 ISO boots without any trouble at all using both UEFI and BIOS.
>>> 
>>> I was helped by koobs in #freebsd @ Freenode who asked me to send an e-mail 
>>> this way and linking to these commits as a reference:
>>> 
>>> https://reviews.freebsd.org/D13784
>>> https://svnweb.freebsd.org/base?view=revision&revision=332416
>>> 
>>> So far I've tried to UEFI boot the 11.2 ISO and 12.0 ISO with the following 
>>> Dell PowerEdge models without success:
>>> 
>>> R440
>>> R630
>>> R430
>>> FC430
>>> R330
>>> R620
>>> R420
>>> R610
>>> 
>>> -- 
>>> Med vänlig hälsning/Best Regards
>>> Linus Sundqvist
>>> System Engineer, Loopia AB
>>> 
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>> 
> 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Crash in udp6_input on -HEAD

[Larry Rosenman]

borg.lerctr.org dumped core - see /var/crash/vmcore.0

Wed Jul  4 11:37:29 CDT 2018

FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #46 r335957: Wed Jul  
4 11:08:13 CDT 2018 
r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/VT-LER  amd64

panic: page fault

GNU gdb (GDB) 8.1 [GDB v8.1 for FreeBSD]
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd12.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /boot/kernel/kernel...Reading symbols from 
/usr/lib/debug//boot/kernel/kernel.debug...done.
done.

Unread portion of the kernel message buffer:
<118>Starting cupsd.


Fatal trap 12: page fault while in kernel mode
cpuid = 17; apic id = 05
fault virtual address   = 0x60
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80e0f61f
stack pointer   = 0x28:0xfe4288a0
frame pointer   = 0x28:0xfe4289b0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 12 (swi1: netisr 0)
trap number = 12
panic: page fault
cpuid = 17
time = 1530721146
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe428550
vpanic() at vpanic+0x1a3/frame 0xfe4285b0
panic() at panic+0x43/frame 0xfe428610
trap_fatal() at trap_fatal+0x35f/frame 0xfe428660
trap_pfault() at trap_pfault+0x49/frame 0xfe4286c0
trap() at trap+0x2ba/frame 0xfe4287d0
calltrap() at calltrap+0x8/frame 0xfe4287d0
--- trap 0xc, rip = 0x80e0f61f, rsp = 0xfe4288a0, rbp = 
0xfe4289b0 ---
udp6_input() at udp6_input+0xbdf/frame 0xfe4289b0
ip6_input() at ip6_input+0xdd8/frame 0xfe428aa0
swi_net() at swi_net+0x1b9/frame 0xfe428b20
intr_event_execute_handlers() at intr_event_execute_handlers+0x99/frame 
0xfe428b60
ithread_loop() at ithread_loop+0xb7/frame 0xfe428bb0
fork_exit() at fork_exit+0x84/frame 0xfe428bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe428bf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
Uptime: 1m3s
Dumping 6608 out of 130994 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%

__curthread () at ./machine/pcpu.h:231
231 __asm("movq %%gs:%1,%0" : "=r" (td)
(kgdb) #0  __curthread () at ./machine/pcpu.h:231
#1  doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:366
#2  0x80b909b2 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:446
#3  0x80b90f93 in vpanic (fmt=, ap=0xfe4285f0)
at /usr/src/sys/kern/kern_shutdown.c:863
#4  0x80b90fe3 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:790
#5  0x8107291f in trap_fatal (frame=0xfe4287e0, eva=96)
at /usr/src/sys/amd64/amd64/trap.c:892
#6  0x81072979 in trap_pfault (frame=0xfe4287e0, usermode=0)
at /usr/src/sys/amd64/amd64/trap.c:728
#7  0x81071f9a in trap (frame=0xfe4287e0)
at /usr/src/sys/amd64/amd64/trap.c:427
#8  
#9  udp6_input (mp=, offp=, 
proto=) at /usr/src/sys/netinet6/udp6_usrreq.c:424
#10 0x80df0c18 in ip6_input (m=0xf80237299400)
at /usr/src/sys/netinet6/ip6_input.c:962
#11 0x80cb6919 in netisr_process_workstream_proto (
nwsp=, proto=)
at /usr/src/sys/net/netisr.c:901
#12 swi_net (arg=) at /usr/src/sys/net/netisr.c:948
#13 0x80b52289 in intr_event_execute_handlers (p=, 
ie=0xf8012088e500) at /usr/src/sys/kern/kern_intr.c:1013
#14 0x80b529c7 in ithread_execute_handlers (ie=, 
p=) at /usr/src/sys/kern/kern_intr.c:1026
#15 ithread_loop (arg=0xf8012088e100)
at /usr/src/sys/kern/kern_intr.c:1106
#16 0x80b4f704 in fork_exit (
callout=0x80b52910 , arg=0xf8012088e100, 
frame=0xfe428c00) at /usr/src/sys/kern/kern_fork.c:1057
#17 
(kgdb) 


vmcore *IS* available, as is a 2nd one.

This is after an upgrade from 
FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #45 r335610: Sun Jun 
24 17:12:56 CDT 2018 
r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/VT-LER  amd64 1200069 
1200071
to r335957.



Ideas?
-- 
Larry Rosenman https://people.FreeBSD.org/~ler/
Phone: +1 214-642-9640   

Re: Crash in udp6_input on -HEAD

[Hans Petter Selasky]

On 07/04/18 18:51, Larry Rosenman wrote:

borg.lerctr.org dumped core - see /var/crash/vmcore.0




Ideas?


https://svnweb.freebsd.org/changeset/base/335958
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Crash in udp6_input on -HEAD

[Larry Rosenman]

On Wed, Jul 04, 2018 at 06:57:19PM +0200, Hans Petter Selasky wrote:
> On 07/04/18 18:51, Larry Rosenman wrote:
> > borg.lerctr.org dumped core - see /var/crash/vmcore.0
> 
> > 
> > Ideas?
> > 
> https://svnweb.freebsd.org/changeset/base/335958

Thanks!  That fixes it for me.
-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

[Yuri]

On 07/04/18 07:27, Rodney W. Grimes wrote:

Devd/devmatch is one of the largest changes recently,
it could be something in that code path.

Do you get the if_run.ko module loaded?  What does kldstat show
immediately after boot and before you try to "fix" anything with
ifconfig.



It definitely did create the run0 interface before, and now it doesn't.

I wonder if the kernel module is no longer loading...



if_run.ko isn't loaded after boot. But I think it is supposed to be 
loaded by devd too.



Yuri


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

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

[Rodney W. Grimes]

> On 07/04/18 07:27, Rodney W. Grimes wrote:
> > Devd/devmatch is one of the largest changes recently,
> > it could be something in that code path.
> >
> > Do you get the if_run.ko module loaded?  What does kldstat show
> > immediately after boot and before you try to "fix" anything with
> > ifconfig.
> >
> >
> >> It definitely did create the run0 interface before, and now it doesn't.
> > I wonder if the kernel module is no longer loading...
> 
> 
> if_run.ko isn't loaded after boot. But I think it is supposed to be 
> loaded by devd too.

Just for fun to see if this can clear up your issue add
if_run_load="YES"
to /boot/loader.conf


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

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

[Yuri]

On 07/04/18 12:00, Rodney W. Grimes wrote:

Just for fun to see if this can clear up your issue add
if_run_load="YES"
to /boot/loader.conf



This doesn't help. In the presence of preloaded if_run.ko wpa_supplicant 
still can't initialize wlan0.



Yuri


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

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

[Kevin Oberman]

On Wed, Jul 4, 2018 at 11:49 AM, Yuri  wrote:

> On 07/04/18 07:27, Rodney W. Grimes wrote:
>
>> Devd/devmatch is one of the largest changes recently,
>> it could be something in that code path.
>>
>> Do you get the if_run.ko module loaded?  What does kldstat show
>> immediately after boot and before you try to "fix" anything with
>> ifconfig.
>>
>>
>> It definitely did create the run0 interface before, and now it doesn't.
>>>
>> I wonder if the kernel module is no longer loading...
>>
>
>
> if_run.ko isn't loaded after boot. But I think it is supposed to be loaded
> by devd too.
>
>
> Yuri
>

A quick perusal of /etc/devd.conf does not indicate that devd will load the
driver. It is possible that I missed something, but "run" i only referenced
as a part of long regex to stop or start pccard-ether.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

[Warner Losh]

On Wed, Jul 4, 2018, 2:13 PM Kevin Oberman  wrote:

> On Wed, Jul 4, 2018 at 11:49 AM, Yuri  wrote:
>
> > On 07/04/18 07:27, Rodney W. Grimes wrote:
> >
> >> Devd/devmatch is one of the largest changes recently,
> >> it could be something in that code path.
> >>
> >> Do you get the if_run.ko module loaded?  What does kldstat show
> >> immediately after boot and before you try to "fix" anything with
> >> ifconfig.
> >>
> >>
> >> It definitely did create the run0 interface before, and now it doesn't.
> >>>
> >> I wonder if the kernel module is no longer loading...
> >>
> >
> >
> > if_run.ko isn't loaded after boot. But I think it is supposed to be
> loaded
> > by devd too.
> >
> >
> > Yuri
> >
>
> A quick perusal of /etc/devd.conf does not indicate that devd will load the
> driver. It is possible that I missed something, but "run" i only referenced
> as a part of long regex to stop or start pccard-ether.
>

Look at etc/devd/devmatch.conf

Warner

--
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

[Kevin Oberman]

On Wed, Jul 4, 2018 at 12:06 PM, Yuri  wrote:

> On 07/04/18 12:00, Rodney W. Grimes wrote:
>
>> Just for fun to see if this can clear up your issue add
>> if_run_load="YES"
>> to /boot/loader.conf
>>
>
>
> This doesn't help. In the presence of preloaded if_run.ko wpa_supplicant
> still can't initialize wlan0.
>
>
> Yuri


This is a shot in the dark, but I have a possibly similar issue with my
Intel  6205 (iwn) card. It appears that thee is a race involving the timing
of the iwn (wlan0) coming up and the start of the wpa_supplicant.

I see the interface start, and aesociate but immediately go down. dhclient
starts, but fails. If I kill the interface (service netif stop wlan0) and
manually start it (ifconfig wlan0 up), it comes up fine. I can then start
the wpa_supplicant and dhclient to get it working. From this point, it
remains stable.

If I just let it bounce up and down, it usually will eventually come up,
but it can take some time and, on occasion it simply fails to some up
unless I intervene.
wlans_iwn0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

[Kevin Oberman]

On Wed, Jul 4, 2018 at 12:17 PM, Warner Losh  wrote:

>
>
> On Wed, Jul 4, 2018, 2:13 PM Kevin Oberman  wrote:
>
>> On Wed, Jul 4, 2018 at 11:49 AM, Yuri  wrote:
>>
>> > On 07/04/18 07:27, Rodney W. Grimes wrote:
>> >
>> >> Devd/devmatch is one of the largest changes recently,
>> >> it could be something in that code path.
>> >>
>> >> Do you get the if_run.ko module loaded?  What does kldstat show
>> >> immediately after boot and before you try to "fix" anything with
>> >> ifconfig.
>> >>
>> >>
>> >> It definitely did create the run0 interface before, and now it doesn't.
>> >>>
>> >> I wonder if the kernel module is no longer loading...
>> >>
>> >
>> >
>> > if_run.ko isn't loaded after boot. But I think it is supposed to be
>> loaded
>> > by devd too.
>> >
>> >
>> > Yuri
>> >
>>
>> A quick perusal of /etc/devd.conf does not indicate that devd will load
>> the
>> driver. It is possible that I missed something, but "run" i only
>> referenced
>> as a part of long regex to stop or start pccard-ether.
>>
>
> Look at etc/devd/devmatch.conf
>
> Warner
>

Oops! That's why I said "quick perusal". (On my 11.2-STABLE system, it's in
/etc/devd/usb.conf) I don't have a system HEAD running here ATM.

Thanks!
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

kvm_swap: ksw_devname too short

[Jamie Landeg-Jones]

kvm_swap.ksw_devname is defined in  as 32 characters. It's easy to
exceed this (e.g. /dev/diskid/DISK-4C441001130129435304p2)

I suppose setting an automatic glabel would be the solution, but how much
hassle would bumping this field cause? I notice that swap with such long
names still actually works...

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

Re: atomic changes break drm-next-kmod?

[Cy Schubert]

In message <20180703170223.266db...@thor.intern.walstatt.dynvpn.de>, 
"O. Hartma
nn" writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Tue, 3 Jul 2018 10:19:57 -0400
> Michael Butler  schrieb:
>
> > It seems recent changes (SVN r335873?) may have broken drm-next-kmod ..
> > 
> > --- i915_drv.o ---
> > In file included from i915_drv.c:30:
> > In file included from
> > /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/inclu
> de/linux/acpi.h:26:
> > In file included from
> > /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/inclu
> de/linux/device.h:4:
> > In file included from
> > /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
> > In file included from
> > /usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
> > In file included from /usr/src/sys/sys/systm.h:44:
> > ./machine/atomic.h:450:29: error: invalid operand for instruction
> > ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
> > ^
> > :1:7: note: instantiated into assembly here
> > andq $9223372036854775807,40672(%r14)
> >  ^
> > 1 error generated.
> > *** [i915_drv.o] Error code 1
> > 
> > make[3]: stopped in
> > /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
> > --- i915_gem.o ---
> > In file included from i915_gem.c:28:
> > In file included from
> > /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:3
> 8:
> > In file included from /usr/src/sys/sys/malloc.h:42:
> > In file included from /usr/src/sys/sys/systm.h:44:
> > ./machine/atomic.h:449:29: error: invalid operand for instruction
> > ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
> > ^
> > :1:6: note: instantiated into assembly here
> > orq $-9223372036854775808,40672(%r14)
> > ^~
> > 1 error generated.
> > *** [i915_gem.o] Error code 1
> > 
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
>
> It breaks also graphics/drm-stable-kmod (see PR 229484,
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same error as you d
> escribed
> above) and also emulators/virtualbox-ose-kmod. As long as CURRENT revision is
>  < r335873,
> those kmod compile well.

The virtualbox-ose-kmod issue is different. It's namespace pollution 
caused by the inclusion of sys/param.h in sys/systm.h when _KERNEL is 
defined. sys/param.h includes sys/priority.h if LOCORE is not defined. 
virtualbox typedefs PVM as a struct whereas sys/priority.h defines it 
as a constant. Virtualbox undefines PVM in some headers, usually after 
including sys/param.h. I haven't looked at it further than this with 
the limited time I have tonight but I suspect one of the #undef PVM 
statements needs to move.

> - -- 
> O. Hartmann
>
> Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
> Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
> -BEGIN PGP SIGNATURE-
>
> iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWzuQGgAKCRDS528fyFhY
> lKHnAf0fIVHnw1xBVHzogeQQo4v+he17R2ln6l25lNR/pUE1AZOsFzPDamAkqbY+
> f1+Usr+P5o7jn26Bh4ob3UmIj25DAf4tJZpeZS4iGZ374lrCAemYFb53+MJ1fClW
> aBLI6DVOiBiOt/UpLXZf1whl/dtQvo5yd1xywfYOwi9Jh8teHcNW
> =mtMH
> -END PGP SIGNATURE-
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


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

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

[Linus Sundqvist]

Running these commands makes the boot menu show up, and then takes me to the 
BSD installer!

Med vänlig hälsning/Best Regards
Linus Sundqvist
System Engineer, Loopia AB

On 04/07/18 16:50, Toomas Soome wrote:
> set currdev=cd1:
> include /boot/loader.rc
> 
> This should give menu/boot.
> 
> Rgds,
> Toomas
> 
> Sent from my iPhone
> 
>> On 4 Jul 2018, at 16:25, Linus Sundqvist  wrote:
>>
>> Hi,
>>
>> Sure, while using the 12.0 ISO here is lsdev -v and ls cd0:
>> https://imgur.com/RmYpg7u
>>
>> and here is ls cd1:
>> https://imgur.com/FPsixOw
>>
>> Med vänlig hälsning/Best Regards
>> Linus Sundqvist
>> System Engineer, Loopia AB
>>
>>> On 04/07/18 15:08, Toomas Soome wrote:
>>> Can you post lsdev -v output?
>>>
>>> Also, could you try ls command? Like, ls cd0:   
>>>
>>> Rgds,
>>> Toomas
>>>
>>> Sent from my iPhone
>>>
 On 4 Jul 2018, at 12:28, Linus Sundqvist  wrote:

 Hi,

 I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64 
 12.0 disk1 ISO (20180628) using UEFI on a Dell PowerEdge R430 by getting 
 this error:
 https://imgur.com/a/Idljfhm

 The bootonly ISOs seems to show the same error message.

 Changing the server to boot via BIOS loads the setup correctly, however, I 
 want to use UEFI on all our servers, which I have done before.

 The 11.1 ISO boots without any trouble at all using both UEFI and BIOS.

 I was helped by koobs in #freebsd @ Freenode who asked me to send an 
 e-mail this way and linking to these commits as a reference:

 https://reviews.freebsd.org/D13784
 https://svnweb.freebsd.org/base?view=revision&revision=332416

 So far I've tried to UEFI boot the 11.2 ISO and 12.0 ISO with the 
 following Dell PowerEdge models without success:

 R440
 R630
 R430
 FC430
 R330
 R620
 R420
 R610

 -- 
 Med vänlig hälsning/Best Regards
 Linus Sundqvist
 System Engineer, Loopia AB

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



signature.asc
Description: OpenPGP digital signature