Le 09/02/2015 10:12, Marc Balmer a écrit :
I intend to remove the compat-FreeBSD support from the system.
[...]
This is what motivates my proposal.
Ok?
Generally it would be a good idea, but there are obviously some tw_cli
users. So they need a working alternative first, imo. Maybe
Le 13/02/2015 13:33, Marc Balmer a écrit :
Am 13.02.15 um 12:34 schrieb Maxime Villard:
Le 09/02/2015 10:12, Marc Balmer a écrit :
I intend to remove the compat-FreeBSD support from the system.
[...]
This is what motivates my proposal.
Ok?
Generally it would be a good idea, but there
Apparently, compat-FreeBSD is needed by tw_cli users.
Therefore I think I will just disable it by default in the GENERIC kernels,
unless anyone disagrees.
Le 07/02/2015 12:19, Maxime Villard a écrit :
Hi,
I intend to remove the compat-FreeBSD support from the system.
It has a limited
Joerg Sonnenberger jo...@britannica.bec.de writes:
From what I see from the original message, there are two issues:
(1) It's a shared interrupt.
(2) uhci is generated interrupts when it should not.
Also ehci. Here are the updated counters, with usage info:
interrupt total
On Fri, Feb 13, 2015 at 01:19:49PM +0100, Joerg Sonnenberger wrote:
On Thu, Feb 12, 2015 at 09:02:37PM -0500, Thor Lancelot Simon wrote:
On Thu, Feb 12, 2015 at 07:52:10PM +0100, Tom Ivar Helbekkmo wrote:
Tom Ivar Helbekkmo t...@hamartun.priv.no writes:
The uhci pins on the ioapics
Maxime Villard m...@m00nbsd.net writes:
Apparently, compat-FreeBSD is needed by tw_cli users.
Therefore I think I will just disable it by default in the GENERIC kernels,
unless anyone disagrees.
Our norms for significant changes are more or less about consensus or
preponderance of opinion.
Tom Ivar Helbekkmo t...@hamartun.priv.no writes:
uhci0, uhci2, and ehci0 are all getting lots of erroneous interrupts,
Also, studying my log of a ping that's sending one ICMP ECHO per second
to the machine from another host on the local network, I see that
whereas without Jörg's changes I had
On 08/02/2015 14:10, Greg Troxel wrote:
Roy Marples r...@marples.name writes:
I don't fully understand what you are saying. But do you have an idea of
how this can be fixed then without dhcpcd having to learn the routing
table at load time?
It seems to me that on a diskless client, the only
Am 13.02.15 um 12:35 schrieb Maxime Villard:
Apparently, compat-FreeBSD is needed by tw_cli users.
Therefore I think I will just disable it by default in the GENERIC kernels,
unless anyone disagrees.
I disagree. People still use it.
In article 20150208103806.ga1...@norite.fritz.box,
Izaak yitz...@inbox.ru wrote:
Hi,
Sorry for my silence on the aprint project. I was busy in the last
while, but I have more time to dedicate to it now.
Anyway, I am currently working on the first task, converting printf to
the appropriate
jo...@britannica.bec.de (Joerg Sonnenberger) writes:
... As such I find disabling COMPAT_FREEBSD by default a very good
idea for increasing the visibility of the problem.
Disabling it by default makes it invisible and forces it to bitrot.
And I tend to believe that that's the intention behind
On Fri, Feb 13, 2015 at 07:05:00PM +0100, Maxime Villard wrote:
Le 13/02/2015 15:26, Greg Troxel a écrit :
Maxime Villard m...@m00nbsd.net writes:
Apparently, compat-FreeBSD is needed by tw_cli users.
Therefore I think I will just disable it by default in the GENERIC kernels,
On Fri, Feb 13, 2015 at 05:17:24PM +, Christos Zoulas wrote:
In article 20150208103806.ga1...@norite.fritz.box, Izaak
yitz...@inbox.ru wrote:
Having read through many files, I have found that often printf is
wrapped in a macro like 'DPRINTF', which is occasionally used both in
the
Date: Fri, 13 Feb 2015 20:24:19 +0100
From: Joerg Sonnenberger jo...@britannica.bec.de
On Fri, Feb 13, 2015 at 09:26:48AM -0500, Greg Troxel wrote:
Our norms for significant changes are more or less about consensus or
preponderance of opinion. So far you've said that you want to
On Fri, Feb 13, 2015 at 09:26:48AM -0500, Greg Troxel wrote:
Maxime Villard m...@m00nbsd.net writes:
Apparently, compat-FreeBSD is needed by tw_cli users.
Therefore I think I will just disable it by default in the GENERIC kernels,
unless anyone disagrees.
Our norms for significant
m...@m00nbsd.net (Maxime Villard) writes:
Hi,
this may be a stupid question; in ufs/ffs/ffs_vfsops.c, l.1153:
if (fs-fs_sbsize SBLOCKSIZE)
brelse(bp, BC_INVAL);
else
brelse(bp, 0);
However 'fs-fs_sbsize' is *always* smaller than SBLOCKSIZE. So only
Greg Troxel wrote:
Maxime Villard m...@m00nbsd.net writes:
Apparently, compat-FreeBSD is needed by tw_cli users.
Therefore I think I will just disable it by default in the GENERIC kernels,
unless anyone disagrees.
Our norms for significant changes are more or less about consensus or
In article 20150213192419.gb5...@britannica.bec.de,
Joerg Sonnenberger jo...@britannica.bec.de wrote:
On Fri, Feb 13, 2015 at 09:26:48AM -0500, Greg Troxel wrote:
Maxime Villard m...@m00nbsd.net writes:
Apparently, compat-FreeBSD is needed by tw_cli users.
Therefore I think I will just
On 13 Feb 2015, at 19:18, Maxime Villard m...@m00nbsd.net wrote:
Hi,
this may be a stupid question; in ufs/ffs/ffs_vfsops.c, l.1153:
if (fs-fs_sbsize SBLOCKSIZE)
brelse(bp, BC_INVAL);
else
brelse(bp, 0);
However 'fs-fs_sbsize' is *always*
In article 2015021322.g...@norite.fritz.box,
Izaak yitz...@inbox.ru wrote:
On Fri, Feb 13, 2015 at 05:17:24PM +, Christos Zoulas wrote:
In article 20150208103806.ga1...@norite.fritz.box, Izaak
yitz...@inbox.ru wrote:
Having read through many files, I have found that often printf is
If you are going to disable COMPAT_FREEBSD in GENERIC kernels, then
you probably also need to disable twe(4) and twa(4) as well. I would not
be in favor of this. Several people have written saying they use tw_cli.
I've not written, but I too use tw_cli to manage 3ware cards under NetBSD.
On Feb 13, 2015, at 2:14 PM, Christos Zoulas chris...@astron.com wrote:
In article 20150213192419.gb5...@britannica.bec.de,
Joerg Sonnenberger jo...@britannica.bec.de wrote:
I have asked the same question a long time ago when we pruned a bunch of
other obsolete emulations. From a
On Thu, Feb 12, 2015 at 09:02:37PM -0500, Thor Lancelot Simon wrote:
On Thu, Feb 12, 2015 at 07:52:10PM +0100, Tom Ivar Helbekkmo wrote:
Tom Ivar Helbekkmo t...@hamartun.priv.no writes:
The uhci pins on the ioapics are chalking up a few interrupts, but not
many, and no bursts.
Am 13.02.15 um 12:34 schrieb Maxime Villard:
Le 09/02/2015 10:12, Marc Balmer a écrit :
I intend to remove the compat-FreeBSD support from the system.
[...]
This is what motivates my proposal.
Ok?
Generally it would be a good idea, but there are obviously some tw_cli
users. So they
On February 13, 2015 9:36:13 PM EST, Brian Buhrow buh...@nfbcal.org wrote:
Hello. The point I was trying to make is that if you break
COMPAT_FREEBSD by taking it out of the GENERIC kernel, you lose the
ability to manage the
twa(4) or twe(4) cards through the OS unless you recompile a
On Fri, Feb 13, 2015 at 10:17:29PM +, Christos Zoulas wrote:
Perhaps it is best to just change the printfs to aprint_debug_dev, but
leave the other printf flavors (tprintf uprintf) alone? This at least
will not change behavior?
Yes, that is what I was planning to do, thereby also following
Christos Zoulas writes:
In article 2015021322.g...@norite.fritz.box,
Izaak yitz...@inbox.ru wrote:
On Fri, Feb 13, 2015 at 05:17:24PM +, Christos Zoulas wrote:
In article 20150208103806.ga1...@norite.fritz.box, Izaak
yitz...@inbox.ru wrote:
Having read through many files, I
Hello. The point I was trying to make is that if you break
COMPAT_FREEBSD by taking it out of the GENERIC kernel, you lose the ability to
manage the
twa(4) or twe(4) cards through the OS unless you recompile a kernel with
COMPAT_FREEBSD back in. (Having an auto-loading module seems like
In article 201502132346.t1dnkqgd005...@lothlorien.nfbcal.org,
Brian Buhrow buh...@nfbcal.org wrote:
If you are going to disable COMPAT_FREEBSD in GENERIC kernels, then
you probably also need to disable twe(4) and twa(4) as well. I would not
be in favor of this. Several people have
On February 13, 2015 6:46:52 PM EST, Brian Buhrow buh...@nfbcal.org wrote:
If you are going to disable COMPAT_FREEBSD in GENERIC kernels, then
you probably also need to disable twe(4) and twa(4) as well. I would
not
be in favor of this. Several people have written saying they use
tw_cli.
On Fri, Feb 13, 2015 at 07:05:00PM +0100, Maxime Villard wrote:
Our norms for significant changes are more or less about consensus or
preponderance of opinion. So far you've said that you want to
remove/disable this, and a number of people have said they use it. No
one else has spoke
31 matches
Mail list logo
