Xin,
fixed by r353492
On Sun, Oct 13, 2019 at 11:45:46PM -0700, Xin Li wrote:
X>
X>
X> On 2019-10-09 08:07, Gleb Smirnoff wrote:
X> > Yes, I we should allow sleep in ifioctl handlers. So this is my fault, I'll
X> > handle it today.
X>
X> It seems that -CURRENT as of today would panic with:
X
On 2019-10-09 08:07, Gleb Smirnoff wrote:
> Yes, I we should allow sleep in ifioctl handlers. So this is my fault, I'll
> handle it today.
It seems that -CURRENT as of today would panic with:
(kgdb) #0 doadump (textdump=1) at src/sys/amd64/include/pcpu_aux.h:55
#1 0x80bbe550 in kern_r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241223
Kubilay Kocak changed:
What|Removed |Added
Keywords||regression
Flags|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241223
Anthony Cornehl changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241223
--- Comment #5 from Gleb Smirnoff ---
Please try with kernel after r353484.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241223
--- Comment #4 from Anthony Cornehl ---
(In reply to Gleb Smirnoff from comment #3)
It was built after a svn update of /usr/src from base/head.
--
You are receiving this mail because:
You are on the CC list for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241223
--- Comment #3 from Gleb Smirnoff ---
> I recompiled with r353461...
Did you cherry-pick r353461 or did you update all of your kernel sources up to
r353461?
--
You are receiving this mail because:
You are on the CC list for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241223
Kubilay Kocak changed:
What|Removed |Added
Summary|E1000: panic: sleeping in |em(4): E1000 panic:
2019-10-09 06:36, Yuri Pankov wrote:
M> > >>> Tried updating from r353072 to r353334 and getting the following panic
M> > >>> reproducibly on boot (starting dhclient?):
M> > >>>
M> > >>> panic: sleeping in an ep
r353072 to r353334 and getting the following panic
reproducibly on boot (starting dhclient?):
panic: sleeping in an epoch section
cpuid = 5
time = 1570591558
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe00af780140
vpanic() at vpanic+0x19d/frame
072 to r353334 and getting the following panic
> >>> reproducibly on boot (starting dhclient?):
> >>>
> >>> panic: sleeping in an epoch section
> >>> cpuid = 5
> >>> time = 1570591558
> >>> KDB: stack backtrace:
> >>> d
On 2019-10-09 15:56, Mark Johnston wrote:
On Wed, Oct 09, 2019 at 10:40:04AM +0200, Hans Petter Selasky wrote:
On 2019-10-09 06:36, Yuri Pankov wrote:
Tried updating from r353072 to r353334 and getting the following panic
reproducibly on boot (starting dhclient?):
panic: sleeping in an epoch
On Wed, Oct 09, 2019 at 10:40:04AM +0200, Hans Petter Selasky wrote:
> On 2019-10-09 06:36, Yuri Pankov wrote:
> > Tried updating from r353072 to r353334 and getting the following panic
> > reproducibly on boot (starting dhclient?):
> >
> > panic: sleeping in an
On 2019-10-09 06:36, Yuri Pankov wrote:
Tried updating from r353072 to r353334 and getting the following panic
reproducibly on boot (starting dhclient?):
panic: sleeping in an epoch section
cpuid = 5
time = 1570591558
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b
Tried updating from r353072 to r353334 and getting the following panic
reproducibly on boot (starting dhclient?):
panic: sleeping in an epoch section
cpuid = 5
time = 1570591558
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe00af780140
vpanic() at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232362
Harald Schmalzbauer changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232362
--- Comment #3 from Harald Schmalzbauer ---
Just a short note that r339547 (vlan: Fix panic with lagg and vlan) doesn't
influence this problem and, like expected, hasn't changed the panic (locally
merged to 12-stable).
Likewise r339587 (Res
)
|panic: sleeping in an epoch |panic: sleeping in an epoch
|section (igb, e1000_82575, |section (igb, e1000_82575,
|actiall 82576 in use) |actually 82576 in use)
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232362
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
Keywords|
on a if_lagg(4) parent with a if_igb(4)
port also leads to a panic, like when rc(8) is doing it. I tested with i210
and 82576.
Here's the i210 backtrace:
panic: sleeping in an epoch section
cpuid = 2
time = 1539941673
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232362
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232362
Andrey V. Elsukov changed:
What|Removed |Added
Keywords||IntelNetworking
Assi
Am 08.05.2018 um 11:52 schrieb Kevin Bowling:
On Tue, May 8, 2018 at 2:43 AM, Harry Schmalzbauer wrote:
Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:26 (localtime):
iflib in stable/11 only affects bnxt at this time.
You should try out HEAD and let us know for the rest of your questio
23 matches
Mail list logo
