https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218579
--- Comment #11 from Cy Schubert ---
(In reply to NK from comment #10)
Sketchy details. There's nothing to go on.
The WOL patch was developed for 12-CURRENT only. The only issue is a system
will not halt -p after being woken by WOL, but wi
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
Yuri Pankov wrote:
[dd]
> >>
> >> I have not found rtsold in /etc/rc.d/netif or similar startup script.
> >
> >
> > The rtsol command will send a single router solicitation. It's probably
> > getting invoked on startup. Or, you might've just gotten lucky and heard an
> > unsolicited router adve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #17 from Lev A. Serebryakov ---
I have all crashdumps saved, and I have corresponding kernel.full saved, too,
so I could provide any additional information which could be extracted with
"kgdb" from these.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #16 from Lev A. Serebryakov ---
And third non-debug crash
Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer = 0x20:0x806dab77
stack pointer = 0x28:0xff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #15 from Lev A. Serebryakov ---
Other crash without debug options
Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; cpuid = 1; apic id = 01
instruction pointer = 0x20:0x806585ea
stack pointer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #14 from Lev A. Serebryakov ---
One crash without debug options
Fatal trap 9: general protection fault while in kernel mode
cpuid = 1; apic id = 01
instruction pointer = 0x20:0x806585ea
cpuid = 0; apic id = 00
instr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #13 from Lev A. Serebryakov ---
Without debug options in kernel crashes are all different, but it is always
GPE. Looks like memory corruption.
Please note, that without SAD/SDP everything works. And with "null" SAD
everything w
alan somers wrote:
On Sat, Sep 29, 2018, 11:24 PM Victor Sudakov wrote:
Alan Somers wrote:
When running FreeBSD as an IPv6 host im SLAAC mode, is
"rtsold_enable=YES" really necessary? I did not enable rtsold and IPv6
still works fine only with
fconfig_re0=""
ifconfig_re0_ipv6="inet6 accept_
On Sat, Sep 29, 2018, 11:24 PM Victor Sudakov wrote:
> Alan Somers wrote:
> > >
> > > When running FreeBSD as an IPv6 host im SLAAC mode, is
> > > "rtsold_enable=YES" really necessary? I did not enable rtsold and IPv6
> > > still works fine only with
> > >
> > > fconfig_re0=""
> > > ifconfig_re0_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
Eugene Grosbein changed:
What|Removed |Added
Summary|12-ALPHA7 r338900 crashes |[em] 12-ALPHA7 r338900
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
Lev A. Serebryakov changed:
What|Removed |Added
Keywords||IntelNetworking
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659
--- Comment #12 from Lev A. Serebryakov ---
Ok. Now I have kernel with INVARIANTs and WITNESS and I have space fro
crashdumps.
I've got 3 crashdumps with exactly same panic message:
Assertion (staterr & E1000_RXD_STAT_DD) != 0 failed at
/d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231416
--- Comment #5 from Lev A. Serebryakov ---
I can add one more datapoint: 82574L Gigabit Network Connection (which is shown
as "em") doesn't have this problem on same FreeBSD revision.
--
You are receiving this mail because:
You are the as
14 matches
Mail list logo
