ou think you have a candidate you can do a more complete
clean-and-rebuild to be sure. Sometimes build glitches will require a
clean rebuild at some bisect points.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailma
we don't want to use a tool purposefully built for the problem
> you are facing? Doesn't seem like a "git debate" more like hammering in
> screws...
>
This in-your-face git evangelism is getting REALLY OLD, REALLY FAST.
Please stop it.
I have nothing
gt;
> No. At attach time, the RNG grabs some probe entropy. At detach time it does
> nothing.
>
> M
And yet... Steve has gathered evidence that the system bricks when a
device is detached with the new entropy-gathering code and doesn't do so
On Sun, 2014-11-16 at 18:23 +, Mark R V Murray wrote:
> > On 16 Nov 2014, at 18:21, Ian Lepore wrote:
> >
> > On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
> >>> On 16 Nov 2014, at 17:51, Steve Kargl
> >>> wrote:
> >>>
catch logic errors with
> > rebuilding code. Should this be in FreeBSD?
>
> Not sure what that is meant to achieve. If parts of the installation
> depend on the value of CC, why would you want to set it to false? Just
> so it can error out at those points?
>
&g
would be significant. I
don't understand why anything these days is still defaulting to 9600.
It's the 21st century, but we never got the George Jetson flying cars we
were promised, and apparently we're never going to break loose from the
standards set by accoustic-coupled
)
static inline void
locallog(int lvl, const char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);
logv(level, fmt, ap);
va_end(ap);
}
But unfortunately we don't have a logv() function. I think maybe we
should have one. :)
-- Ian
_
27;t decide if it's worth committing... it'll have a
lot of value to someone with slow serial and netbooting, is that common?
-- Ian
Index: lib/libstand/cd9660.c
===
--- lib/libstand/cd9660.c (revision 275941)
+++ lib/libs
On Mon, 2014-12-22 at 15:15 +, Poul-Henning Kamp wrote:
>
> In message <1419224743.1018.108.ca...@freebsd.org>, Ian Lepore writes:
>
> >On Sun, 2014-12-14 at 10:32 +, Poul-Henning Kamp wrote:
> >> The rotating swirlie ('-/|\') in the loade
r only ... I
> > performed the
> > iterative search of the foul commit by "svn update -r 276XXX" and then
> > build kernel only
> > via "make kernel" - this just for the record in case some
> > world-dependencies might have
> > effects.
>
> Hi!
>
> Thanks for that. Would you please file a PR with the details and what
> you've done?
>
> I hope you can narrow it down further. You've done a great job
> already, I just can't see any clear winner there for a commit to back
> out :(
r276064 looks like a candidate. At least, it has 'efi' in the name. :)
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Sun, 2014-12-28 at 20:57 +0100, O. Hartmann wrote:
> Am Fri, 26 Dec 2014 12:23:42 -0700
> Ian Lepore schrieb:
>
> > On Fri, 2014-12-26 at 08:48 -0800, Adrian Chadd wrote:
> > > On 26 December 2014 at 04:01, O. Hartmann
> > > wrote:
> > > > Am T
() routine and do all the real attach-time type stuff in a
bus_new_pass() routine after the pass number becomes high enough that
your co-dependent driver peers are available.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Tue, 2015-01-06 at 07:57 -0800, Adrian Chadd wrote:
> On 6 January 2015 at 07:55, Ian Lepore wrote:
> > On Tue, 2015-01-06 at 09:37 -0500, John Baldwin wrote:
> >> On 1/5/15 8:18 AM, Hans Petter Selasky wrote:
> >> > Hi,
> >> >
> >> > The
e best of my knowledge, and without retrying builds, the package
> builds fine on 8/9/10.
>
> Thanks,
> Matthias
It was removed in r276737. I don't know what replaces it.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
key.
Another small-board imx6 possibility is the Hummingboard from SolidRun.
I now have freebsd running on a SolidRun Cubox-i4, so I expect no large
drama in getting it working on other SolidRun imx6 products. Gonzo
ordered a Hummingboard recently, so we should know for sure some time
soon.
-- Ian
of uptime) we designed our
own motherboards with EDM sockets on them.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
looked into it).
Some audio support was recently committed, but I don't know much about
it yet.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> workaround as that is) will avoid it.
>
> Yes, this is being worked on.
FWIW, 24.8 days is the point at which an int32_t variable counting ticks
at 1khz rolls over from positive to negative numbers.
-- Ian
___
freebsd-current@freebsd
th 1 message
cap 01[d0] = powerspec 2 supports D0 D3 current D0
cap 13[a4] = PCI Advanced Features: FLR TP
void intel_modeset_init_hw(struct drm_device *dev)
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.or
s...
> >
>
> Adding xo_finish() to w.c line 268 just right before exit(0); fixes that
> issue (I don't know libxo well enough to say if this is the proper fix or
> just a workaround, but it seems logical to me).
>
I wonder if that implies that any non-
frastructure) but I would say this
> is
> very much a corner case
>
> Bapt
By far the biggest incompatibility I've run into is the change from :U
and :L to :tu and :tl, mostly because any existing makefiles that
contain :U or :L variable modifiers just silently do the wrong thing
On Tue, 2015-02-10 at 22:55 +, Brooks Davis wrote:
> On Tue, Feb 10, 2015 at 02:32:44PM -0700, Ian Lepore wrote:
> > On Tue, 2015-02-10 at 22:24 +0100, Michael Gmelin wrote:
> > >
> > >
> > > > On 10 Feb 2015, at 22:17, Michael Gmelin wrote:
> >
= VGA
cap 05[90] = MSI supports 1 message enabled with 1 message
cap 01[d0] = powerspec 2 supports D0 D3 current D0
cap 13[a4] = PCI Advanced Features: FLR TP
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.fr
ag removed by r278584 is BLM_PCH_OVERRIDE_ENABLE according
to the Linux driver. I think we're not correctly setting or selecting
the PWM channel for backlight control.
>
> -a
>
>
> On 11 February 2015 at 07:41, Ian FREISLICH wrote:
> > Hi
> >
> > With t
install to)?
How much time will this add to a build?
Yeah yeah, I can update a couple dozen src.conf files to eliminate them,
and that's not the biggest hassle in the world (but it's also not
nothing). It seems like this is a heavy enough load that it needs to
justify its ex
On Thu, 2015-02-12 at 04:11 +, Glen Barber wrote:
> On Wed, Feb 11, 2015 at 08:56:00PM -0700, Ian Lepore wrote:
> > On Wed, 2015-02-11 at 22:21 -0500, Ed Maste wrote:
> > > On 11 February 2015 at 21:39, Glen Barber wrote:
> > > >
> > > > Within t
old make without notice ?
> >
> Old make was already removed in 10.x what remains is only the sources and that
> is what I propose to remove from 11 (and only from 11)
>
> Best regards,
> Bapt
fmake exists as a port too, doesn't it? Tha
Ian FREISLICH wrote:
> Adrian Chadd wrote:
> > Hi,
> >
>
> > There's a "invert backlight" option in i915, try setting it to 1?
>
> This is pretty much all I could find (unless I was looking in the
> wrong place). It makes no difference. The bac
e can actually do better. :)
I sure hope "fix coloring" is shorthand for "don't you dare turn on any
of that color crap without the user's permission."
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
son
I never hit the triggering condition in testing, but it seems that just
about everyone else in the world did. :/
There are a couple locking-related fixes still needed which might
trigger a witness warning, they should be fixed soon as well.
-- Ian
___
the latest since some sbuf fixes have
> landed and see if I can finish a poudriere build run.
There is still a panic, one that I can't yet figure out why it wasn't
panicking before my changes, but I'm working on it.
-- Ian
___
On Tue, 2015-03-17 at 12:14 -0700, Craig Rodrigues wrote:
> On Tue, Mar 17, 2015 at 11:57 AM, Ian Lepore wrote:
>
> >
> > There is still a panic, one that I can't yet figure out why it wasn't
> > panicking before my changes, but I'm working on it.
>
On Tue, 2015-03-17 at 14:14 -0500, Mark Felder wrote:
>
> On Tue, Mar 17, 2015, at 13:57, Ian Lepore wrote:
> > On Tue, 2015-03-17 at 13:49 -0500, Mark Felder wrote:
> > >
> > > On Mon, Mar 16, 2015, at 13:03, Shawn Webb wrote:
> > > > O
use "make universe", sometimes with the -DMAKE_JUST_KERNELS option.
But the LINT kernels for x86 and sparc have been broken since January.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
e problems
with the xtoolchain ports, not the base build system, and probably
should have been reported to the port's maintainer, or on ports@. Or
perhaps it's some sort of usage error, I don't know anything about the
xtoolchain stuff. In any case, there doesn't seem to be anything wrong
with the base build using the supported build mechanisms.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
:27:22:6c:0b:8f timed out.
Apr 22 12:28:34 zen wpa_supplicant[2191]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=00:27:22:6c:0b:8f reason=3 locally_generated=1
Apr 22 12:28:34 zen kernel: wlan0: link state changed to DOWN
Ian
--
Ian Freislich
___
freebsd
to just eliminate the flag (and of course, USB's need for it, which I
fully admit I don't understand even a little bit).
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscrib
6:43 zen dhclient: New Subnet Mask (wlan0): 255.255.255.0
Apr 6 18:06:43 zen dhclient: New Broadcast Address (wlan0): 10.0.0.255
Apr 6 18:06:43 zen dhclient: New Routers (wlan0): 10.0.0.1
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing l
py" or "atrun"
> execution, only as often as I get these "save-entropy" complains.
It looks like the events that should have run at 02:55:00 and 03:00:00
were both run at 03:03:25. Does this same sort of pattern exist in
other instances of the error?
I don't have any
maintain the arm code on branches earlier than 10-stable
unless someone specifically asks for a change in 8.x. (afaik, virtually
nobody uses 9.x on arm).
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
> move forward in this area. But that's hard, as your response indicates.
>
> This is the last I'll say about this, because it appears the community
> isn't ready. Have fun with your ancient version control while Linux
> continues to grow in market share. :-(
So you're saying that it's not that you're missing the point, it's just
that you're trolling the list. That will be remembered.
(Of course, it's clear to those who've actually read the thread that you
are in fact completely missing the point.)
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
re...
There are 2125 occurrances of BUFSIZ in the base code (probably 95% of
them inappropriately used to size a local temp buffer or string). Do you
really want to perturb that much working tested software because it
makes md5 faster? How many of those occurrances are stack-allocated
variables and
e
they are allocated. As I've already pointed out, BUFSIZ appears in the
base code over 2000 times. Where is the analysis of the impact an 8x
change is going to have on all those uses?
-- Ian
___
freebsd-current@freebsd.org mailing list
ht
than grains of sand on the beach
won't care about things like 64k buffers used by /bin/sh to read a line
of text, and all the world is big servers now, right?
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
I would like to add a new feature to watchdogd(8): -x option
to specify the watchdog timeout to leave in effect when the program
exits (currently behavior is to disable the watchdog on exit). The
change is available for review...
https://reviews.freebsd.org/D2556
-- Ian
s it also MFCs it so that it isn't just a bunch of
lurking merge conflicts in the future.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
zeof(data)); // node is ‘pcd-reset'
> returns:
> data[0]: 0x0300
> data[1]: 0x0600
> data[2]: 0x0200
>
> which looks to me that it’s in the wrong endian?
>
> cheers,
> danny
FDT data is always big-endia
ouraged for -head.)
>
> That's the correct way, afaik.
>
> Cheers,
> Hiren
Is there a reason the sysctl tunable flag changes can't be MFC'd?
Leaving changes that widespread un-mfc'd just makes for lots of merge
conflicts as time goes on (and can also lead
akes sense. i don't observe deadlock, but, simple reboot.
>
> I believe I posted patches to serialize ddb entrance or panics due to nmi.
> I do not have references handy, you could search lists.
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
That was on freebsd-arch in July 2014.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ion, the refclocks were always selected as pps.peer
and sys.peer.
Now, even though the refclocks have settled down, the peer selection
seems a little strange. At least not what I'm used to seeing.
Ian
--
Ian Freislich
___
freebsd-cu
, "nebulous" that
> I didn't think it warranted a whine of its own here. But on the
> chance that it's related to ntpd giving up the ghost prematurely,
> it seemed but a reasonable exercise of "Full Disclosure" to mention
> it in th
That is, it's always
/any/path/here
obj/
src/
Given that we have (or at least had at one time) some of those magical
"..." paths that cause bmake to search up the hierarchy for its .mk
files, I wonder if an odd relationship between src and obj dir confuse
, all running CURRENT from within a day.
The upshot is that I have to be root in order to link code.
Any ideas greatly appreciated.
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
Glen Barber wrote:
> On Tue, Jul 28, 2015 at 07:31:56PM +, Glen Barber wrote:
> > On Tue, Jul 28, 2015 at 08:16:16PM +0200, Ian FREISLICH wrote:
> > > Hi
> > >=20
> > > I cannot for the life of me figure out why this is so:
> > >=20
> > >
se either the
permissions of the mount point or the permissions of the directory
mounted on that mount point. In the past, the permissions in the
mounted filesystem have always trumped the mount point, but I have
no idea what the spec says. Is this a bug?
Ian
--
Ian Freislich
_
Glen Barber wrote:
> On Tue, Jul 28, 2015 at 10:17:38PM +0200, Ian FREISLICH wrote:
> > I found the actual problem. The mount point for /usr was mode 700
> > even though the root of the mounted filesystem on /usr was mode 755.
> > Did I explain that clearly (quite difficult b
On Tue, 2015-07-28 at 22:17 +0200, Ian FREISLICH wrote:
> David Wolfskill wrote:
> > My experience with SU+J is limited (and negative -- in large part,
> > because I tend heavily on "dump | restore" pipelines to copy file
> > systems, some of which are "live&
inwake() type call to be sprinkled around to do
the matching SEV instruction.
-- 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 say
what platform you're working with. It appears that this has only ever
worked on i386 and a handful of old arm and mips platforms.
-- 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"
gt; mmap(0x0,5360,PROT_READ,MAP_PREFAULT_READ,4,0x0) ERR#22 'Invalid
> > argument'
> > close(4) = 0 (0x0)
> > SIGNAL 11 (SIGSEGV)
> > process killed, signal = 11 (core dumped)
> >
> > Any help debugging this futher would be much appreciated. I
like a serious problem. I do NO_CLEAN builds literally dozens
of times a day, across all arches. I can't remember the last time I
had a problem. When it does cause a problem, or when I've made big
changes that might require regenerating dependencies, I just rm -rf the
kernel dir(s) with
> 1 error generated.
> > *** Error code 1
>
> And when running:
>
> make -DNO_CLEAN -j6 universe MAKE_JUST_KERNELS=yes
> MODULES_OVERRIDE=linuxkpi
>
> With my "sys/conf/kern.post.mk" patch, it passes all the variants.
>
>
> Is
done with ntpdc on older releases can now be
done using ntpq with the new release. The ntpdc program itself is
still present so that you can still administer remote servers running
older code, since they won't be able to do everything via ntpq.
-- Ian
_
glanced over e.g. rw_rlock and it did not have the issue, now
> > > that I
> > > see _sx_xlock_hard it wuld indeed use fixing.
> > >
> > > Expect a patch in few h for all primitives I'll find. I'll stress
> > > test
> > > the kernel, bu
03 -> 0
> debug.total: 1013 -> 0
> debug.total: 1005 -> 0
> debug.total: 1006 -> 0
> debug.total: 1004 -> 0
> debug.total: 1005 -> 0
> debug.total: 1003 -> 0
> debug.total: 1004 -> 0
> debug.total: 1006 -> 0
> debug.total: 1004 -> 0
> deb
On Fri, 2015-11-06 at 17:51 +0100, Hans Petter Selasky wrote:
> On 11/06/15 17:43, Ian Lepore wrote:
> > On Fri, 2015-11-06 at 17:28 +0100, Hans Petter Selasky wrote:
> > > Hi,
>
> >
> > Do the test II results change with this setting?
> >
> >
On Fri, 2015-11-06 at 17:57 +0100, Hans Petter Selasky wrote:
> On 11/06/15 17:51, Hans Petter Selasky wrote:
> > On 11/06/15 17:43, Ian Lepore wrote:
> > > On Fri, 2015-11-06 at 17:28 +0100, Hans Petter Selasky wrote:
> > > > Hi,
> >
> > >
> >
u,
> or did you just omit that step?
>
In 19 years of using freebsd, I have never once needed to chflags on an
obj directory. Nothing in the build process sets any non-standard
flags in the obj dirs, and a simple rm -rf will remove everything just
fine (you would need to sudo the
ng or reviewing the changes, please see
https://reviews.freebsd.org/D4608
-- 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"
really urgent that anyone answers. More of an inquiry than a
> problem... at least at
> r288246... )
If I've understood your question correctly, I think the sequence you're
looking for is something like this:
init 1
mount -r /
fsck -y /
mount -w /
exit
When the NO_W
On Thu, 2015-12-24 at 12:48 +0100, Oliver Pinter wrote:
> On 12/24/15, Vijay Rajah wrote:
> >
> >
> > On 12/24/15 12:22 PM, Ian Smith wrote:
> > > ~2 minutes delay there. sendmail (mta and msp both) at least
> > > are unhappy about your hostname, and s
EVICE= in your kernel config. module_path is another one that
loader(8) normally provides, and it needs to be set for kldload and
things that auto-load modules (devd, mount) to work.
I think this should be safe to MFC, but I tend to be lazy and do MFCing
in long-delayed batches; let me know if
If someone with the same problem finds this thread on a search engine
next week, they're sure going to wish you had said what the fix was, or
linked to the forum post you found that fixed it.
-- Ian
On Tue, 2016-01-26 at 17:00 -0800, Chris H wrote:
> Never mind. I was able to find a quic
t; Thanks, Mokhi.
If you start working on locking in keyboard drivers you might discover
there are dragons there. For example...
https://lists.freebsd.org/pipermail/svn-src-head/2014-March/056833.html
-- Ian
___
freebsd-current@freebsd.org mail
l have one problem: I
> have to provide somehow the cleartext password in an automated environment.
>
> Maybe there is something missing ...
>
> oh
We use something like this at work (which I don't fully understand, but
it works on freebsd 6.x through 10.x at least)...
e
>
> Best regards
>
There's not a lot of information to go on here... at what point does it
halt? Why do you think it's related to the uart 1 hint? Does it help
to set hint.uart.1.disabled=1 in loader before booting?
-- Ian
__
swap In happening in top
during this unresponsiveness, and noticible amounts of Out activity
when nothing was happening except the rsync.
This is amd64, 12GB ram, 16GB swap, a tmpfs had about 400MB in it at
the time. Prior to the update around the 10.3 freeze, this machine
would never touch the
I915_WRITE(BLC_PWM_CPU_CTL2, PWM_ENABLE);
I915_WRITE(BLC_PWM_CPU_CTL, 0);
- I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE);
+ I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE | (1<<30));
}
void intel_modeset_init_hw(struct drm_device *dev)
--
Ian Freislich
--
Cape Augusta Digital Pro
On Tue, 2016-03-15 at 07:20 -0700, Jeffrey Bouquet wrote:
> rsync... see bottom posting
>
> On Tue, 15 Mar 2016 07:43:46 +0100, olli hauer wrote:
>
> > On 2016-03-14 15:19, Ian Lepore wrote:
> > > On Sun, 2016-03-13 at 19:08 -0700, Adrian Chadd wrote:
> > &g
ernational flight away from me for the 1.5
months so I can't test anything else until I'm back.
Ian
On 19 March 2016 01:10:54 Jean-Sébastien Pédron wrote:
On 14/03/2016 18:59, Ian FREISLICH wrote:
Hi
Hi!
With r296548 on the following hardware:
vgapci0@pci0:0:2:0: class=0x03
7;ve done it, but it seems to
still work... I just plugged in a usb drive while I was at the prompt
and it didn't show up until the second time I entered a '.'.
-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/
t; kldload: an error occurred while loading the module. Please check
> dmesg(8) for more details.
> root@tommy:~ [1]# exit
>
> Script done on Sun Mar 20 22:25:01 2016
>
> the full error in dmesg is the same as stated before:
>
> link_e
On Sun, 2016-03-20 at 23:40 +0100, Jilles Tjoelker wrote:
> On Sun, Mar 20, 2016 at 04:05:34PM -0600, Ian Lepore wrote:
> > On Sun, 2016-03-20 at 22:33 +0100, Guido Falsi wrote:
> > > On 03/20/16 22:21, Guido Falsi wrote:
> > > > On 03/20/16 22:18, Conrad Meyer wro
nks.
>
This is probably my fault, introduced with r292180 in December, and
fixed a few days ago with r297127; sorry about that. Updating should
get you running again.
Unfortunately you can't fix it just by pre-loading the right modules,
because part of the problem was a missing MODULE
h earlier.
> > > >
> > > > Thanks.
> > > >
> > >
> > > +1
> > > I would also like to clarify about this problem was drawn up a
> > > bug
> > > report.
> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=19
when it
attached.
The only change I can find that might have some effect is a switch to
MSI-based interrupts some time ago. That was MFC'd to 10-stable in
r271051, and that's very close to range cited in that PR.
It might be worth trying to set hw.sdhci.enable_msi=0 in loader.conf
and see
On Sat, 2016-03-26 at 02:42 +0300, Ruslan Makhmatkhanov wrote:
> Ian Lepore wrote on 03/26/16 02:11 AM:
> > On Fri, 2016-03-25 at 23:33 +0300, Ruslan Makhmatkhanov wrote:
> > > Hello,
> > >
> >
On Sat, 2016-03-26 at 12:23 +0300, Ruslan Makhmatkhanov wrote:
> Ian Lepore wrote on 03/26/16 04:09 AM:
> > On Sat, 2016-03-26 at 02:42 +0300, Ruslan Makhmatkhanov wrote:
> > > Ian Lepore wrote on 03/26/16 02:11 AM:
> > > > On Fri, 2016-03-25 at 23:33 +03
On Mon, 2016-03-28 at 12:33 +0300, Ruslan Makhmatkhanov wrote:
> Ian Lepore wrote on 03/28/16 05:29 AM:
>
> [...]
>
> > > I updated to r297281 with this quirk applied. Sadly, it doesn't
> > > change
> > > anything - controllers still not recognized. I
freebsd, design is decided by a
race to commit rather than by discussion.
-- 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"
Hi
Replying to myself...
The monitor works with in 1920x1080. Any higher resolution and the
monitor displays rapidly changing random colours filled over the entire
screen. I'm currently using r298115 with no improvement on the situation.
Ian
On 03/14/16 13:59, Ian FREISLICH wrote:
th both old and new versions of libarchive, and now the new version
will require a flag that the old version will reject as unknown.
Ick.
-- Ian
> On 5/14/2016 3:46 PM, Tim Kientzle wrote:
> > A little history about this issue:
> >
> > http://www.cve.mitre.org/cgi-bin/c
On Sun, 2016-05-15 at 01:29 +0200, Martin Matuska wrote:
> Ian, we are here talking about cpio, not libarchive. The flag in
> libarchive is not active by default.
>
Yes. We use cpio for filesystem images, for historical reasons (such
as cpio's ability to encode device major/mino
uff will break long-working
existing software, but at least it'll be easy to fix.
-- Ian
>
> On 15.05.2016 01:36, Ngie Cooper (yaneurabeya) wrote:
> > > On May 14, 2016, at 16:29, Martin Matuska wrote:
> > >
> > > Ian, we are here talking about cpio, not
OPTION: 6 ( 4) DNS server10.0.0.1
-------
--
Ian Freislich
--
Cape Augusta Digital Properties, LLC a Cape Augusta Company
*Breach of confidentiality & accidental breach of confidentiality *
On 05/18/16 19:49, Conrad Meyer wrote:
> Hey Ian,
>
> r299512 incorrectly encoded client identifiers because I misunderstood
> the intent of the sizeof()-scaled client_id. I reverted that change
> and replaced it with r300174, which I believe fixes the first overrun
> more corre
ient is discarding the
server's offer for whatever reason.
But, r300174 has it working again for me. I can't speak to the
correctness of the fix though.
Ian
--
Ian Freislich
--
Cape Augusta Digital Properties, LLC a Cape Augusta Company
*Breach of confidentiality & accidenta
driver, then you'll essentially be
embracing the entire FDT world (it's an alternative to ACPI and hints
and other types of metadata for describing hardware). You'll also be
breaking new ground in freebsd by being the first to try to use
freebsd's FDT support framework on an x
er-enable
pin that has to be asserted or something? I don't think we have an API
that lets an arbitrary driver which is not a child of the gpiobus
manipulate pins, outside of the FDT world.
-- Ian
___
freebsd-current@freebsd.org mailing list
ht
ultiple instructions requires 4-byte-aligned values (not a
typo: doubleword access requires word alignment). Everything smaller
than doubleword access in userland these days can be unaligned. The
optimizer can combine adjacent 32-bit accesses into doubleword
-instruction accesses, leading to alignment f
301 - 400 of 866 matches
Mail list logo
