https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Ngie Cooper changed:
What|Removed |Added
Status|Closed |Open
Flags|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Julian Elischer changed:
What|Removed |Added
CC||jul...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
--- Comment #20 from Julian Elischer ---
previous comment shoudl have read "I strongly request that the bug be closed
again".
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
--- Comment #21 from Miroslav Lachman <000.f...@quip.cz> ---
(In reply to Julian Elischer from comment #20)
Why?
To miss the opportunity to remove deprecated code for the next major release
again?
Then why we even put warnings to outdated c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #22 fro
On Wednesday, April 26, 2017 09:18:48 AM Sepherosa Ziehau wrote:
> On Wed, Apr 26, 2017 at 4:36 AM, John Baldwin wrote:
> > On Thursday, April 20, 2017 02:29:30 AM Dexuan Cui wrote:
> >> > From: John Baldwin [mailto:j...@freebsd.org]
> >> > Sent: Thursday, April 20, 2017 02:34
> >> > > Can we add
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
--- Comment #23 from Miroslav Lachman <000.f...@quip.cz> ---
(In reply to Warner Losh from comment #22)
I think it turns in to bikeshed now. Are we talking about rc.conf variables to
configure jails or about this as dependency for ezjail?
N
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849
Jamie Gritton changed:
What|Removed |Added
CC||ja...@freebsd.org
--- Comment #24
It'll be supported as much as someone is willing to pay for it.
It isn't out of the realm of possibility to implement an if_transmit
style layer for altq, etc so it could be a generic queue discipline.
It'd be nice to have a multi-queue version of this but we're not there
yet.
Thanks,
-adrian
can you file a bugzilla bug with this information in it? What's
triggering the interrupt?
-a
On 20 April 2017 at 02:05, Johannes Lundberg wrote:
> I found another solution. Modifying the DSDT file by removing
>
> Method (_L06, 0, NotSerialized) // _Lxx: Level-Triggered GPE
> {
Tom Uffner wrote:
Andrey V. Elsukov wrote:
I think the most of these panics should be fixed in r315956.
thanks. I'll give it a try and report back as soon as I have a result.
r315956 panicked about 22 min after boot. failed to dump a core.
___
free
There's a rather lengthy theory about it here
https://bugs.freedesktop.org/show_bug.cgi?id=98501
On Wed, Apr 26, 2017 at 11:15 PM, Adrian Chadd wrote:
> can you file a bugzilla bug with this information in it? What's
> triggering the interrupt?
>
>
> -a
>
>
> On 20 April 2017 at 02:05, Johannes
12 matches
Mail list logo