On 2025-02-24 09:54, Mark Johnston wrote:
On Mon, Feb 24, 2025 at 03:52:14PM +0800, Zhenlei Huang wrote:
On Feb 24, 2025, at 12:42 PM, Ian FREISLICH wrote:
Hi
Building a kernel today failed with:
-Werror /usr/src/sys/net/toeplitz.c
In file included from /usr/src/sys/net/toeplitz.c:29:
In
On February 24, 2025 2:52:14 AM EST, Zhenlei Huang wrote:
>
>
>> On Feb 24, 2025, at 12:42 PM, Ian FREISLICH wrote:
>>
>> Hi
>>
>> Building a kernel today failed with:
>>
>> -Werror /usr/src/sys/net/toeplitz.c
>> In file included fr
this is a result of changes to netinet/in.h (3b281d1421a78)
which added a static inline function using ntohl() which is not defined
in kernel use.
Ian
rary
media and then use that to boot with the firmware update and chroot
install the firmware and edit loader.conf on the nvme.
The microcode update fixed it for me. I inferred from reading that
enable PCID might have a performance advantage.
Ian
All,
I can confirm that the microcode loaded early fixes the issue.
Ian
On 2025-01-27 13:12, Patrick M. Hausen
wrote:
Hi all,
Am 27.01.2025 um 18:38 schrieb Milan Obuch :
On Mon, 27 Jan 2025 12:10:43 -0500
Ian FREISLICH
, without the cpu microcode. I'll look into that
shortly.
Ian
On 2025-01-27 13:12, Patrick M. Hausen
wrote:
Hi all,
Am 27.01.2025 um 18:38 schrieb Milan Obuch :
On Mon, 27 Jan 2025 12:10:43 -0500
Ian FREISLICH wrote:
or if there's a bug in UFS2 that's
tickled by this CPU. I'll provide any debugging required.
Ian
in 'union pf_headers'; did you mean 'icmp'?
8762 | if (!pf_pull_hdr(m, *off,
&pd->hdr.icmp6, icmp_hlen,
Ian
nsec);
There are two problems with this, both the seconds and nanos are
printed incorrectly. The correct incantation would be
printf("%jd.%09ld\n", (intmax_t)ts.tv_sec, ts.tv_nsec);
-- Ian
/local
in your port makefile while you're developing on it.
-- Ian
On Wed, 2021-06-09 at 18:54 +1000, Peter Jeremy via freebsd-current
wrote:
> On 2021-Jun-08 17:13:45 -0600, Ian Lepore wrote:
> > On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wrote:
> > > There is a command for that which does or use to do a pretty
> > > decent
On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wrote:
> > On Tue, 8 Jun 2021 09:41:34 +
> > Mark Linimon wrote:
> >
> > > On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote:
> > > > Sometimes it's a real interesting exercise to fig
On Tue, 2021-06-08 at 13:47 +0200, Gary Jennejohn wrote:
> On Tue, 8 Jun 2021 09:41:34 +
> Mark Linimon wrote:
>
> > On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote:
> > > Sometimes it's a real interesting exercise to figure out where a
> > >
; remove things more widely as the stable/12 branch reaches EOL and
> after.
>
> Warner
It would be really nice if, instead of just deleting the $FreeBSD$
markers, they could be replaced with the path/filename of the file in
the source tree. Sometimes it's a real interesting exercise to figure
out where a file on your runtime system comes from in the source world.
All the source tree layout changes that happened for packaged-base
makes it even more interesting.
-- Ian
es. The amount of work required to get there
from here is almost unimaginable, and there are no big companies
funding that kind of work (which is how linux got all that code).
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.fr
s. If we keep whittling away at the backwards compatibility freebsd
is so famous for, I'll have abosolutely zero arguments left for why
$work shouldn't just switch to the much more popular and better-
supported linux.
I also hate the idea of requiring no space between -I and it
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
efb83a4312036f1f
> >
> >
>
>
> Nice! Thanks again!
>
>
> Jakob
>
Indeed, thank you for taking care of this, my $job has me way too busy
these days.
-- Ian
___
freebsd-current@freebsd.org mailing list
http
On Tue, 2021-01-12 at 19:56 +0100, Hans Petter Selasky wrote:
> On 1/12/21 7:45 PM, Ian Lepore wrote:
> > > > - for (int i = 0; i <= sc->sc_npins; i++) {
> > > > + for (int i = 0; i != sc->sc_npins; i++) {
> > > >
n I got a different result,
> > > > > > > so I
> > > > > > > most likely did something wrong the first time.
> > > > > > >
> > > > > > > ff3468ac94597efdcbc56f372528dfc98b114dac is the first bad
> > > > > > > commit
> > > >
somehow ONLY load the module if you had CPU
> support for it. The down side is that detection would probably have
> to be in the laoder as this code can be used very early on.
>
Not nearly so much as the code to support the PC/AT RTC and i8254
hardware as kernel eventtimers
pool.cache; do
> > if [ -r $cachefile ]; then
> > zpool import -c $cachefile -a -N && break
> >
> > best,
> > -harry
> >
> >
> >
>
> You can define these in /boot/loader.conf:
> #kern.ca
On Thu, 2020-09-17 at 12:49 -0700, John-Mark Gurney wrote:
> Ian Lepore wrote this message on Thu, Sep 17, 2020 at 09:01 -0600:
> > On Thu, 2020-09-17 at 18:43 +0400, Gleb Popov wrote:
> > > On Thu, Sep 17, 2020 at 6:05 PM Cy Schubert <
> > > cy.schub
bedded systems talking to
each other over a point to point link within a sealed device are not
concerned about man in the middle attacks or other modern internet
threats.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Wed, 2020-09-02 at 14:45 -0400, Dan Langille wrote:
> On Wed, Sep 2, 2020, at 2:36 PM, Ian Lepore wrote:
>
> > Seriously, Warner?
>
> Yes, seriously. We are adults. Act accordingly.
>
> Don't be confused. I also thought the message he was replying to was out
ad that
has any real value at all. Unlike everyone else, he has clearly seen
what the basic problem is (zero communications about this impending
cutover to the people who need to work with it every day), and he
summarized it in a completely practical way.
This assumption that everyone knows how to us
ate for clear_tmp_enable="YES"
> to include
> a check like this. I would think that an rc option like this should
> delete
> everything in /tmp.
>
I disagree. One of the few things those immutable flags are good for
is protecting files from things like an rc script or oth
On Sun, 2020-06-21 at 19:54 +0200, Michael Tuexen wrote:
> > On 21. Jun 2020, at 19:40, Ian Lepore wrote:
> >
> > On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote:
> > > > On 21. Jun 2020, at 14:28, Kostya Berger > > > >
> > > >
t commit here.
>
*BSD has always accepted 0 as a synonym for localhost (and iirc, linux
does not). If this no longer works, it's a regression which is going
to cause existing applications and scripts to fail. At the very least
it deserves an entry in UPDATING.
-- Ian
> Best regards
> Mich
1 message, 64 bit enabled with 1 message
cap 13[e0] = PCI Advanced Features: FLR TP
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
bsd machine that
could successfully resume from suspend, so I've never been able to
experiment with it.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ink that's a different issue.
>
Segfaults and other problems with a program named "conftest" while
building ports is normal. Autotools' configure script writes and runs
programs named conftest to detect the presence or absence of features
or bugs. That doesn't mean every
t were not being used until now. In
> particular, atomic_fcmpset_8() seems broken and hangs up
> in vm_page_bits_swap(). I think I have a fix but I want to run it
> by Ian.
>
> --Thomas
>
> Index: sys/arm/include/atomic-v6.h
> ===
On Fri, 2020-03-13 at 13:34 -0400, Ed Maste wrote:
> On Fri, 13 Mar 2020 at 13:22, Ian Lepore wrote:
> >
> > Could a.out support be a kernel config option that's off by
> > default?
>
> Probably. That seems reasonable to me.
>
> > And could its presenc
cated via sysctl in some way, so that
ldconfig could do a.out hints only if support for them is available?
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
e log attached to the original message:
> --- _bootstrap-tools-link-[ ---
> *** [_bootstrap-tools-link-[] Error code 1
> make[2]: stopped in /usr/src
I have no idea why it failed trying to create a symlink to '[' (an
alias for test(1)), but that was the first error.
-- Ian
___
ndle that stuff separately from the normal hiearchical parent/child
bus relationships.
There just isn't much that can reasonably be separated out and used in
another project, I think.
-- Ian
___
freebsd-current@freebsd.org mailing list
htt
't working, or something. I couldn't make
any sense out of your original question.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
90104 drwxr-xr-x2
> nick nick
> 512 Sep 15 2017 /usr/src/usr.sbin/btxld
> 33695644 drwxrwxr-x2
> root wheel
> 512 Jan 27 22:33 /usr/obj/
Before being freed, the memory was last used as the softc for some
device (perhaps only during probing of a device that never attached).
That device would most likely be the culprit (or a wild-pointer write
hit that block).
-- Ian
___
fr
. I should be able to use the getnanouptime() call to get a
> “clock” to look for (it’s used in print_uptime()). As long as the
> clock isn’t stopped at this time in the shutdown sequence atleast :-)
>
> *Time to write some code and test this* :-)
>
If you want to throttle something
n update -r "{date}"
The curly braces indicate you're specifying a date, which can be in a
large variety of typical formats, details here:
http://svnbook.red-bean.com/en/1.7/svn.tour.revs.specifiers.html
Curly braces are significant in some shells, so the quotes may be
required.
--
to be done on
a different thread to avoid [recursion|deadlock|whatever]."
So I'd say the first thing to do is be sure that the best solution
isn't just to pthread_create() as needed. If it turns out the cost of
pthread_create() is like 1-2% of the t
xamining every existing driver and
probably changing many of them. I'm not afraid of this aspect of any
change we decide on... it's about 30 drivers, all of which will need
minor changes.
-- Ian
___
freebsd-current@freebsd.org mailing lis
n the reverse order?
The current gpio(4) documentation really only covers gpiobus(4) and a
mentions a few of its older children and how to configure them via
hints. We need manpages for some of the newer drivers, and we
especially need a manpage that documents sys/gpio.h (which is used both
from us
lists.freebsd.org/pipermail/freebsd-arm/2015-March/010649.html
There have also been some bug reports as recently as 2017 indicating
that people are still doing this on small armv7 systems.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ole lotta stuff happens between ntpd and syscons (the
thing that configures blanktime). Try setting rc_debug=YES in rc.conf,
that should write more info to syslog about what's happening between
ntpd and the lockup point.
-- Ian
___
freebsd-current
_spin'
> spinlock_enter();
>\
> ^
> . . .
>
> (spinlock_enter was not the only example.)
>
>
My bad, I forgot to include when I switched the code to
spinlocks. Should be fixed by r352333.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Tue, 2019-09-10 at 21:41 +0200, Dimitry Andric wrote:
> On 10 Sep 2019, at 20:14, Ian Lepore wrote:
> >
> > On Tue, 2019-09-10 at 11:01 -0600, Warner Losh wrote:
> > > However, please do *NOT* remove the sys/*/compile directories.
> > >
> > > Warn
was -- I just assumed the build machinery created it because
I had accidentally done a make in a wrong directory once.
So what are those directories about? I'm not used to seeing mystery
directories appear inside a source tree.
-- Ian
___
freebsd-
ation than the average user, and would use the rlimit command
in ntp.conf.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Mon, 2019-09-09 at 21:44 +0300, Konstantin Belousov wrote:
> On Mon, Sep 09, 2019 at 12:13:24PM -0600, Ian Lepore wrote:
> > On Mon, 2019-09-09 at 09:30 -0700, Rodney W. Grimes wrote:
> > > > On Sat, 2019-09-07 at 09:28 -0700, Cy Schubert wrote:
> > > >
w only syslogd has oomprotect set to YES by default. Maybe
that's a good choice -- once we start declaring one daemon to be more
important than others, you'll discover there's a whole back lot full of
bikesheds that need painting.
So maybe we should just document ntpd_oomprotect=YES i
.
# This should not be necessary on most systems, but may improve
# performance on heavily-loaded servers experiencing enough
# memory pressure to cause ntpd to be paged out.
# rlimit memlock stacksize
Then we would need to come up with reasonable values for .
-- Ian
___
ables are
expanded. In particular, the loop variable for a .for is expanded on
each loop iteration, but doesn't yet exist during parsing. I suspect
that the .if is evaluated earlier, during parsing. For example, this
makefile:
all:
.for x in a "" b
.if empty(x)
@echo empty
.endif
@echo ${x}
.endfor
@echo done
gives this output:
revolution > make -f /tmp/Makefile
empty
a
empty
empty
b
done
The way I interpret that is that empty(x) is true during parsing, so
the for loop is generated to contain "@echo empty" and "@echo ${x}",
then the for loop actually runs and prints both "empty" and the value
of ${x} on each iteration.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
files are fine and it really is a uid
problem. But a "pkg check -s -a" as suggested in the PR couldn't hurt.
:)
-- Ian
> On Wed, Aug 28, 2019 at 5:20 PM Gary Palmer
> wrote:
> >
> > On Wed, Aug 28, 2019 at 05:09:35PM -0400, Ryan Stone wrote:
> > >
On Wed, 2019-08-14 at 13:59 -0600, Warner Losh wrote:
> On Wed, Aug 14, 2019 at 1:56 PM Ian Lepore wrote:
>
> > On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote:
> > > On 8/14/19 11:06 AM, Kyle Evans wrote:
> > > > LOCAL_MODULES="" does seem lik
7;t think it's as easy to compare the buildhost
running version with the version of source being built, unless the
build is started from the top level so that Makefile.inc1 sets the
variables.
-- Ian
___
freebsd-current@freebsd.org mailing list
https
On Wed, 2019-08-14 at 19:55 +0200, Niclas Zeising wrote:
> On 2019-08-14 19:23, Emmanuel Vadot wrote:
> > On Wed, 14 Aug 2019 10:13:48 -0700
> > John Baldwin wrote:
> >
> > > On 8/14/19 9:22 AM, Ian Lepore wrote:
> > > > This all sounds vaguely wrong,
On Wed, 2019-08-14 at 09:08 -0700, John Baldwin wrote:
> On 8/13/19 3:17 PM, Ian Lepore wrote:
> > On Tue, 2019-08-13 at 14:58 -0700, John Baldwin wrote:
> > > For developers this means even if you are doing testing on a box
> > > that doesn't use DRM, you can in
en I'm on my
amd64 machine building from /my/sources/rpi using TARGET_ARCH=armv6
it's going to find /usr/local/sys/modules/drm-current-kmod and try to
crossbuild it for armv6?
How about when I'm doing a build of 11-stable for testing, but what's
in my /usr/loc
On Sun, 2019-08-11 at 09:12 -0600, Alan Somers wrote:
> On Sun, Aug 11, 2019 at 8:57 AM Ian Lepore wrote:
> >
> > On Sun, 2019-08-11 at 09:04 +0200, Gary Jennejohn wrote:
> > > On Sun, 11 Aug 2019 02:03:10 +
> > > Rick Macklem wrote:
> > >
> >
HOLE
> > return the file's size as the offset.
> >
> > What do others think? rick
> > ps: The man page should be updated, whatever is done w.r.t. this.
> >
>
> I also vote for option 2
>
If SEEK_DATA and SEEK_HOLE don&#
bably won't
use it. But if you are using it, and you want to truly kill the dog,
you would just do "watchdog -t 0" after "service watchdogd stop". If
you really felt the need to cover that with a single service command,
then how about using "service watchdogd cancel&quo
ave to follow the rules (from style(9))...
If either or is needed, include it
before other include files. ( includes ;
do not include both.)
Typically, if you're including anything from sys/ you'll need
sys/types.h first.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
x27;t that /tmp is tmpfs, the problem is that it's being
mounted by /etc/rc.d/tmp as a 20MB filesystem because tmpsize="20m" is
the default. You could set tmpsize to some bigger value in rc.conf, or
you can add an explicit mount for /tmp in fstab so that you get the
fu
g some AI algorithm. The
> first
> part is probably written by hand, and other one is generated. I just
> wondering what's the point of this.
>
> For everyone else, message looking much like this was sent to llvm-
> dev@
> mail list too.
>
>
Everything posted
like the enumeration of busses and devices has changed.
> > > grepping for uhub and usbus of the working and broken dmesg.boot
> > > gives
> > >
> >
> > Are you able to bisect the commit introducing the bad behaviour?
> >
>
> I'll give it a shot.
elay may make even more sense, since
DELAY() is generally just polling a clock register).
Hmm, actually, it looks like iicbb hardcodes the bus frequency delay as
10us and delays after every toggle, so I guess it's really running the
bus at 50khz.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
lave devices are both i2c and smbus
compatible, and the smbus slave timeout is 35ms, so that wouldn't be a
bad default value.
I don't think ignoring the error and forging ahead is a good idea. It
should return an error, and perhaps it should use the bitbang bus-
recovery seque
On Wed, 2019-06-19 at 09:30 -0700, Rodney W. Grimes wrote:
> > In message <
> > fffbe5d47e3515c960429ab416bf2ba234f9671d.ca...@freebsd.org>
> > , Ian Le
> > pore writes:
> > > On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote:
> >
it continued to be an
> > issue
>
> Even -j1 should avoid it. For some reason I am only seeing it without
> any -j flag at all.
>
> I should have a fix in soon.
>
There's a subtle difference between -j1 and no -j at all, having to d
On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote:
> > On Jun 18, 2019, at 06:59, Enji Cooper
> > wrote:
> >
> >
> > > On Jun 18, 2019, at 06:53, Ian Lepore wrote:
> >
> > ...
> >
> > > Last Saturday, Bryan (cc'd) made a
ve been using make buildworld without -j n in the past on
> > that machine, the
> > problem seems to be introduced recently. Any idea what is the cause
> > of
> > the problem?
> >
> > Best regards
> > Michael
> > >
> >
> >
; power in a hot office.
> Commit bits used to be suspended for un-buildable code. I'll boot
> stable.
Since you seem to be so focused on mean-spirited criticism of others,
I'm sure you'll understand when I ask...
Have you *seriosly* been using and building freebsd this long and you
don't know that an opt_*.h file is generated as part of the build and
exists only in the object directory, so that searching for it under
/usr/src or /usr/include would be... let's see, how did you put it?...
Oh yeah: A double waste of CPU & human time.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
,install)
===> lib/libc (obj,all,install)
===> lib/libgcc_eh (obj,all,install)
===> lib/csu/amd64 (all)
===> lib/csu/amd64 (install)
===> lib/libgcc_s (obj,all,install)
===> lib/libcxxrt (obj,all,install)
I've seen some bad things happen in the past when parallel jobs try to
build in the same directory.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
e what
> triggered the issue, but I suspect it has to deal with an external
> [toolchain] change.
> Cheers!
> -Enji
r347992 seems like a good candidate.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/li
t have a really detailed answer because I've
never enabled the option. I've always perceived it as being something
most people don't need. WITHOUT_CLANG_EXTRAS may cut some time from
your build, but it probably won't cut it in half or anything.
-- Ian
-ng and ptxdist from Pengutronix).
>
> Is there anything comparable to
> https://releng.netbsd.org/cgi-bin/builds.cgi , but for FreeBSD?
>
> If I see 0 passed, 67 failed for NetBSD-HEAD, I figure I should wait
> for a better time. But what about FreeBSD?
>
> Tom
A co
bsd 13 and
that you plan on updating to freebsd 13 or later?"
Many of the systems that contained these old devices don't have enough
ram to run a modern version of freebsd. If you can't update the system
to 13, you don't need ongoing ed(4) support. And make no mistake,
ongoing support IS the issue -- it costs manpower we don't have much of
to maintain old device drivers.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> net.inet.ip.portrange.randomized: 1
> net.inet.ip.random_id_total: 0
> net.inet.ip.random_id_collisions: 0
> net.inet.ip.random_id_period: 0
> net.inet.ip.random_id: 0
> net.key.int_random: 60
> debug.fail_point.status_fill_kinfo_vnode__random_path: off
> debug.fail_point.fill_kinfo_vnode__random_path: off
>
nice if "currdev syntax" worked too, so you could just
enter disk3p4 or similar. I may look into adding that to the code.
-- Ian
> > GPT does not have the concept of active partition.
>
> It has "bootme" / "bootonce" attributes. And [
gptzfsboot and
> > pmbr in the drive boot record. I did not try booting an older
> > kernel
> > using the new gptzfsboot. I was concerned about the lack of ssh
> > login
> > when the computers lost their console, so I just rolled back my
> > system
> > to th
On Mon, 2019-04-29 at 10:33 -0400, Thomas Laus wrote:
> > On 2019-04-28 22:27, Ian Lepore wrote:
> > >
> > > If you're using gptzfsboot, I guess you're using zfs? I just
> > > fixed a
> > > problem with probing disks for zfs volumes a few days
sense that the "garbage" might be
different between a firstboot after power-on and a reboot.
So all in all, it wouldn't hurt to update both gptzfsboot and loader
(gpart bootcode -b and -p) to see if there's a fix lurking in my zfs
probe changes.
-- Ian
___
Thanks in advance!
>
>
I think 'devctl rescan' will do that, 'man devctl' for details.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
everything 32-bit under the bus and declare
freebsd to be a 64-bit-only OS. Netflix wins; those of us building
smaller embedded products will eventually be forced to move to linux.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.f
> You do realize some of the emails are from frustrated users
> who are trying to make FreeBSD (see for example libm).
>
And do you realize that you've trimmed away all the context so that now
it looks like Warner was talking to you, when in fact he was replying
the default driver on the major Linux distributions.
> > . . .
> >
> >
> >
> > but it seems to not have a 13-current entry. It does have
> > a 12.0-RELEASE entry.
> >
>
> Thanks. Kinda odd that freebsd-current doesn't have a manual
> page
On Fri, 2019-02-15 at 12:32 -0700, Warner Losh wrote:
> On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote:
>
> > On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote:
> > > > [...]
> > >
> > > HO Eric!
> > >
> > > iflib was a recen
s dependency, and is there an UPDATING entry
> for this change?
>
> Thanks!
> -Enji
>
My question would be: why? If some drivers have a new dependency on
iflib, why isn't that expressed in sys/conf/files and handled
automatically?
-- Ian
__
o you can safely remove it from
your config.
Author: avos
Date: Fri Jan 25 13:48:40 2019
New Revision: 343427
URL: https://svnweb.freebsd.org/changeset/base/343427
Log:
Garbage collect AH_SUPPORT_AR5416 config option.
It does nothing since r318857.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ailed with error 2; retrying fpr
> 3 seconds
> Mounting from ufs:/dev/gpt/extroot failed with error 2; retrying fpr
> 2 seconds
> Mounting from ufs:/dev/gpt/extroot failed with error 2; retrying fpr
> 1 seconds
> ...
>
> I can provide a 'dmesg' output
on between iicbus and the controller lives right alongside
the DRIVER_MODULE() statement that establishes the connection between
the controller and the bus it sits on. See, for example:
sys/dev/glxiic/glxiic.c
sys/dev/iicbus/iicoc.c
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
_vte.o] Error code 1
> >
> > ...
> >
> > -- snip
> >
> > Is this known - did i miss something ?
> > Howto fix ?
> Does your "MODULAR" config file include "device miibus"?
>
It is possible to build miibus as
k" line 92:
> warning: using previous script for "_testsFILESINS_cleanup.ksh"
> defined here
>
>
> Is this something easily fixable? I'm unclear what is throwing a
> warning here?
>
> sean
>
Looks like some makefile has cleanup.ksh listed twi
lready attached
>
> I haven't fiddled with identify() yet, will look at that tonight.
>
If this is just another "bus" an ig4 instance can attach to, I'd think
the recipe would be to add another DRIVER_MODULE() to ig4_iic.c naming
ig4_lpss as the parent. Then add a n
f that will do better
> thanks,
> toomas
>
I don't think that will be an option. If it hasn't gotten to the point
of saying how much BIOS available memory there is, it's only halfway
through loader main() and has hung before getting to interact().
In fact, if that line ha
1 - 100 of 860 matches
Mail list logo
