> appeared in the errata yet. The bug report says that until this is
> fixed, the workaround is to also disable HLT in cpu_idle. I am not
> sure what is the correct value for the sysctl on FreeBSD, perhaps
>
> sysctl machdep.idle=0
>
> or some other value?
>
It is in
On Mon, 27 Aug 2018 20:18:46 +0800
Meowthink wrote:
> Hi Gary,
>
> On 8/27/18, Gary Jennejohn wrote:
> > On Mon, 27 Aug 2018 10:13:10 +0200
> > Phil Norman wrote:
> >
> >> Hi.
> >>
> >> I have a similar setup: Ryzen 3 and Fatal1ty X
art of the kernel in
FreeBSD 12.
After taking these steps about two months ago I have had no more
lockups and the machine runs very stabily.
[big snip]
--
Gary Jennejohn
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mai
On Mon, 12 Dec 2011 08:04:37 -0800
m...@freebsd.org wrote:
> On Mon, Dec 12, 2011 at 7:32 AM, Gary Jennejohn
> wrote:
> > On Mon, 12 Dec 2011 15:13:00 +
> > Vincent Hoffman wrote:
> >
> >>
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Ha
On Mon, 12 Dec 2011 17:10:46 +0100
Lars Engels wrote:
> Did you use -jX to build the world?
>
I'm top posting since Lars did.
It was buildkernel, not buildworld.
Yes, -j6.
> _____
> Von: Gary Jennejohn
> Versendet am: Mon Dec
d this heavily. Usually
2 or more cores were at or below 90%. Not really that significant, but
still a noticeable difference in apparent scheduling behavior. Whether
the observed difference is due to some change in data from the kernel to
gkrellm is beyond me.
--
Gary Jennejohn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
the kernel source it appears that only sched_4bsd.c makes use
of hlt_cpus_mask.
--
Gary Jennejohn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
nyone actually care about vgrind in base? Will people be angry if
> I unroll the 2 cases where it is used under share/doc?
>
I personally have never used vgrind, but since it's available as part of
/usr/ports/textproc/heirloom-doctools IMO it would be safe to remove it
from base, maybe wit
Ls]
There's no code in the kernel to switch back out of graphics mode (i.e.
what X uses) when a panic happens.
You probably can switch to v0, but you won't be able to see it.
The only sure-fire way is to hook up a screen (terminal, laptop or
another computer) to a serial port.
-
4G in
loader.conf and see whether that affects thunderbird/firefox. Who
knows, there may some weird problem caused by all that memory? That
would a fairly quick and cheap way to test this.
--
Gary Jennejohn
___
freebsd-stable@freebsd.org mailin
led?
I do.
You could try adding these options to MOZ_OPTIONS in the Makefile
--enable-debug[=DBG]Enable building with developer debug info
--enable-debug-modules Enable/disable debug info for specific modules
--enable-debugger-info-modules
Enable/disable debug
d haven't seen any problems. But of course, I've
been running various incarnations of 3.6 for a while and may have gotten
all the dependencies already correctly installed.
---
Gary Jennejohn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Sun, 24 Jan 2010 18:48:15 +0200
Alexander Motin wrote:
> Gary Jennejohn wrote:
> > I started seeing a problem a few days ago with one of my DVD drives (a
> > burner at cd0) under 9-current, which makes it impossible to use it even
> > to simply read a DVD.
> >
&
us 0 scbus6 target 1 lun 0
cd1: Removable CD-ROM SCSI-0 device
cd1: 33.300MB/s transfers (UDMA2, PIO size 65534bytes)
cd1: Attempt to query device size failed: NOT READY, Medium not present -
tray closed
I haven't the foggiest why cd0 behaves diffrently from cd1, which is a
vanill
;
> > I'm not sure but I suspect you are using custom kernel built without
> > INET6 option. If so, thunderbird3 is depending upon IPv6.
>
> Can it be made to not require IPv6? (especially when there is no actual IPv6
> connectivity).
>
Seems to be hardcoded all ov
On Tue, 17 Feb 2009 13:46:20 -0700
Scott Long wrote:
> Bruce Evans wrote:
> > On Tue, 17 Feb 2009, Gary Jennejohn wrote:
> >
> >> I tested this with an Adaptec 29160. I saw no real improvement in
> >> performance, but also no regressions.
> >>
>
k I had attached just didn't have enough
performance reserves to show an improvement.
My test scenario was buildworld. Since /usr/src and /usr/obj were both
on the one disk it got a pretty good workout.
AMD64 X2 (2.5 GHz) with 4GB of RAM.
BTW under a very fresh 8.0-cu
L 3154 (PCIE)"
>
> > new xorg will hit ports soon, but a preliminary patch is available at
> > http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch
>
> Ok, I'll test it.
>
I have an RV6xx based system here - graphics in the chipset. Can
rq256.
I'm running amd64 with
re0: port 0xde00-0xdeff mem 0xfdaff000-0xfdaf,
0xfdae0000-0xfdae irq 18 at device 0.0 on pci2
---
Gary Jennejohn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
s motherboard/BIOS related and not a
general problem with ahc or any other SCSI driver. I can say that
at least with my Gigabyte GA-M61P-S3 I observed data corruption with
4GB of memory installed and with the BIOS mapping a part of memory
above 4GB.
Forcing
corruption surely ?
>
Maybe it's BIOS related? I have a new mobo from a different vendor
where I could give it a try and see if the corruption goes away.
---
Gary Jennejohn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nown
> ahc(4) - affected
> ahd(4) - unknown; no one answered the OP's question in the thread
I asked Scott whether he thought ahd would be affected, but he never
responded. I was thinking about getting a PCIe controller but then
I dropped the idea due to lack of fun
y problems, but I was running it with disks only.
Maybe Scott, or someone, has fixed it in the meantime? I haven't
tried to use the full 4 GB in my box since January since I can't
afford data corruption.
---
Gary Jennejohn
___
freebsd-stabl
On Sat, 11 Oct 2008 12:08:00 +0200 (CEST)
Jean-Marc Zucconi <[EMAIL PROTECTED]> wrote:
> >>>>> Gary Jennejohn writes:
>
> > On Fri, 10 Oct 2008 14:29:37 -0300
> > JoaoBR <[EMAIL PROTECTED]> wrote:
>
> >> I tried MBs as Asus, Abit and
On Sat, 11 Oct 2008 03:13:16 -0700
Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote:
> > On Fri, 10 Oct 2008 14:29:37 -0300
> > JoaoBR <[EMAIL PROTECTED]> wrote:
> >
> > > I tried MBs
problem. If you want to use SCSI then you'll have to limit
memory to 3.5 GB.
---
Gary Jennejohn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"Vinod Kashyap" writes:
>
> And now, moving to the important thing... in kern.pre.mk, I changed
> COPTFLAGS from -O2 to -O for amd64 (just like i386), and the problem
> is gone!!
>
Better to do it in /etc/make.conf.
---
Gary Jennejohn / garyjATjennejoh
Soeren Schmidt writes:
> If I dont get any significant showstopper reports this is what will get
> committed to -current soon (plus what I might get done until then of new
> features).
>
What's with ATAPICAM?
---
Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org
28 matches
Mail list logo
