Peculiar failure of re(4) to active a link after a RAM upgrade

[R. Tyler Croy]

I recently upgraded my 11.2-STABLE machine from 4 to 16GB of memory. Upon
reboot the dual-NIC re(4) card which had been previously working failed to
either negotiate or activate a link (i.e. lights up :)) with my DSL modem.
ifcnofig lists the interface as 'no carrier'

I verified that both ports (re0 and re1) were working by plugging network
cables into my switch, and found that both were able to activate a link
properly.

When I plugin the DSL modem's cable into my em(4) based NIC, that activates a
link properly. Regardless of which re(4) NIC I stick the cable into, it
fails to create a link (ifconfig lists em0 as 'active'), while the same cable
works properly in an em(4) NIC.


I'm running r339079 right now, and if I remember correctly, had upgraded the
world prior to the RAM upgrade, so it _seems_ like the RAM upgrade is the only
variable which changed.

I'm really clueless as to what would even be happening underneath the covers
here, and would appreciate any pointers in the right direction for debugging
here :)


Cheers,
-R Tyler Croy

--
GitHub:  https://github.com/rtyler
Twitter: https://twitter.com/agentdero


signature.asc
Description: PGP signature

Re: FreeBSD 12 PowerPC won’t boot at all.

[Nathan Whitehorn]

This probably seems to come from the loader geli support. If I rebuild
loader with WITHOUT_LOADER_GELI=1 set, everything is fine. Could anyone
else who is having trouble try to reproduce that?
-Nathan

On 10/5/18 1:38 PM, Andreas Tobler wrote:
> On 04.10.18 13:34, Alex McKeever wrote:
>> Subject says it all, that and it inverts the boot selector when
>> selected. Tested it on my eMac G4 1.25 GHz (Retail). Last version of
>> FreeBSD that works for me is 11.1, as 11.2 doesn’t boot all the way
>> (hangs on cryptosoft0)
>
> What image did you try? ALPHA8 should boot, but is not stable yet. If
> there will be an APLHA9, it should boot and should be stable, at least
> it is here.
>
> Andreas
> ___
> freebsd-curr...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscr...@freebsd.org"
>

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

Re: early boot netisr_init() panic on older AMD SMP machine with recent 11-STABLE

[Don Lewis]

On  9 Oct, Don Lewis wrote:
> My desktop machine has an older AMD SMP CPU and tracks 11-STABLE.  For
> about six months or so it frequently panics early in boot.  If I retry a
> sufficient number of times I can get a successful boot, but this is
> rather annoying.
> 
> A normal boot looks like this:
> 
> Copyright (c) 1992-2018 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 11.2-STABLE #16 r339017M: Sat Sep 29 19:18:41 PDT 2018
> d...@mousie.catspoiler.org:/usr/obj/usr/src/sys/GENERICDDB amd64
> FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 
> 6.0.1
> )
> WARNING: WITNESS option enabled, expect reduced performance.
> VT(vga): resolution 640x480
> CPU: AMD Athlon(tm) II X3 450 Processor (3214.60-MHz K8-class CPU)
>   Origin="AuthenticAMD"  Id=0x100f53  Family=0x10  Model=0x5  Stepping=3
>   
> Features=0x178bfbff MOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
>   Features2=0x802009
>   AMD 
> Features=0xee500800>
>   AMD 
> Features2=0x37ff SKINIT,WDT>
>   SVM: NP,NRIP,NAsids=64
>   TSC: P-state invariant
> real memory  = 34359738368 (32768 MB)
> avail memory = 33275473920 (31733 MB)
> Event timer "LAPIC" quality 100
> ACPI APIC Table: 
> FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs
> FreeBSD/SMP: 1 package(s) x 3 core(s)
> ioapic0: Changing APIC ID to 2
> ioapic0  irqs 0-23 on motherboard
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #2 Launched!
> Timecounter "TSC-low" frequency 1607298818 Hz quality 800
> random: entropy device external interface
> [SNIP]
> 
> An unsuccessful boot looks like this (hand transcribed):
> [SNIP]
> ACPI APIC Table: 
> FreeBSD/SMP: Multiprocessor System Detected: 3 CPUs
> FreeBSD/SMP: 1 package(s) x 3 core(s)
> ioapic0: Changing APIC ID to 2
> ioapic0  irqs 0-23 on motherboard
> SMP: AP CPU #2 Launched!
> SMP: AP CPU #1 Launched!
> Timecounter "TSC-low" frequency 1607298818 Hz quality 800
> panic: netisr_init: not on CPU 0
> cpuid = 2
> KDB: stack backtrace:
> db_trace_selfwrapper() ...
> vpanic() ...
> doadump() ...
> netisr_init() ...
> mi_startup() ...
> btext() ...
> 
> This problem may be silently occuring on many other machines.  This
> machine is running a custom kernel with INVARIANTS and WITNESS.  The
> panic is coming from a KASSERT(), which is only checked when the kernel
> is built with INVARIANTS.
> 
> This KASSERT was removed from 12.0-CURRENT with this commit:
>   https://svnweb.freebsd.org/base/head/sys/net/netisr.c?r1=301270=302595
> 
>   Revision 302595 - (view) (download) (annotate) - [select for diffs]
>   Modified Mon Jul 11 21:25:28 2016 UTC (2 years, 2 months ago) by nwhitehorn
>   File length: 44729 byte(s)
>   Diff to previous 301270
> 
>   Remove assumptions in MI code that the BSP is CPU 0.
> 
> Perhaps this should be MFC'ed, but it seems odd that the BSP is
> non-deterministic.

I now wonder if this panic is a side effect of EARLY_AP_STARTUP, which
was enabled by default in 11-STABLE GENERIC back in May, so the
timeframe fits.  Since the panic only happens with INVARIANTS enabled,
most users are unlikely to to encounter this problem.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"