ropriate.
This is our _standard_ practice for dealing with this stuff. This is how all
the OpenSolaris bits for Dtrace and ZFS are handled (except that they end up
in a cddl directory instead of contrib). GENERIC / LINT builds can include
things from sys/contrib just fine, so ipfilter won't be
}
> Else
> {
So this is the \_SB_.PCI0.GFX0 device. However, you should kldload acpi_video
and see if it already attaches to this device (devinfo -v can be helpful here
as it will show the ACPI handle of the parent of the acpi_video de
All
your checkouts and merges should be done using svn.FreeBSD.org, not a local
mirror. That might explain your merge problem.
Also, if you are just updating the existing vendor branch and not updating it
to a newer version I'm not sure you really need the @NN part for the
bootstrap
On Monday, September 24, 2012 12:37:30 pm John Nielsen wrote:
> I have a machine running "FreeBSD 10.0-CURRENT #0 r240887" amd64 with two
ConnectX (InfiniBand) cards. Relevant bits of dmesg and pciconf -lv below. The
cards are connected directly to a 10GB Ethernet switch so I nee
m doesn't deadlock it's perfectly useable so long
> as you don't touch the file that's wedged. A lot of the time the
> userland process is unkillable, but often it is killable. How do
> I get from from the PID to where the FS is stuck in
On Wed, Jul 03, 2013 at 01:16:19AM +, Mike C. wrote:
>
> Hi,
>
> According to the windows drivers info on Acer's page, my laptop internal
> SD card reader vendor is "Realtek".
>
> I'm not being able to use the card reader but I'm not sure how to debug
> this...
>
> I see nothing in dmesg re
On Jun 12, 2013, at 11:49 AM, Hiroki Sato wrote:
> I would like your comments on release notes for each release.
> Although I have been working on editing them for years, the workflow
> is still not optimal and sometimes delay of the preparation became an
> obstacle for release process. I would
ot it better to submit via PR (GNATS) rather than a mailing list?
That's what PRs are for...
John
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "
On Friday, June 14, 2013 12:38:12 pm Luigi Rizzo wrote:
> On Fri, Jun 14, 2013 at 12:07:29PM -0400, John Baldwin wrote:
> > On Wednesday, June 12, 2013 2:36:52 pm Alfred Perlstein wrote:
> > > On 6/12/13 11:01 AM, Luigi Rizzo wrote:
> > > > hi,
> > > >
can hold anything you want since it's basically a
memcpy at that point. Various sysctl handlers that need to hold locks while
writing things out use sysctl_wire_old_buffer() for exactly this reason.
--
John Baldwin
___
freebsd-current@freebsd.o
On Thursday, March 07, 2013 9:13:38 pm matt wrote:
> On 02/28/13 09:09, John Baldwin wrote:
> > On Thursday, February 28, 2013 8:15:46 am matt wrote:
> >> On 02/27/13 12:27, John Baldwin wrote:
> >>> On Wednesday, February 27, 2013 1:35:43 pm matt wrote:
> >
is the approach of FreeBSD and devs about that.
You don't know what the module might have corrupted by the time you crash.
It is also quite hard to isolate a crash to a specific module. Many modules
operate on data that is shared with the rest of the system, so just be
n 'unwind' the locking dependencies from there.
>
> Sorry, now I get it, let's see if I can find the locked vnodes and the
> thread that owns them...
You can use 'show lock v_interlock>' to find an owning
thread and then use 'show sleepchain '. If you ar
ch makes it impossible to install the packages on it (xorg, ... etc.
> all compiled on my "master site";
>
> what can I do? The only diff between the computers real difference
> between the computers is that this 4th one has 2 CPU...
Is there a chance you have a hardware issue (
y one block, which contains zeros starting from
> 0x200.
>
> Note that I don't do anything else on that machine during that time.
To be clear, you are still seeing zero'd data in your printfs? Also, it seems
like it is passing the wrong size now? Can yo
then.
This looks fine to me. It would be nice to fix i386 as well to be consistent.
I would commit the new DDB commands as a separate patch from the watchpoint
fixes.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/
Alexander Yerenkow wrote this message on Sat, May 11, 2013 at 18:13 +0300:
> zpools or increase/decrease UFS partitions.
growfs(8)
NAME
growfs -- grow size of an existing ufs file system
HISTORY
The growfs utility first appeared in FreeBSD 4.4.
--
John-Mark Gur
On Thursday, May 09, 2013 4:34:16 am Kamil Czekirda wrote:
> Do you have any ideas to resolve the problem?
I have no idea what part of e1000 common code deals with AMT/IPMI and what you
might need to do to make this work. I was hoping Jack would be be able to
respond here.
> 2013/4/2
On Sun, May 5, 2013 at 2:26 PM, Ulrich Spörlein wrote:
>
> Committed to svn://svn.freebsd.org/base/user/uqs/scan-world as of
> r250268.
>
Thanks.
>
> I'm not sure they are a good basis for said project, however,
>
Ill take a lo
hanks.
Regards,
John Smith.
___
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 Friday, May 03, 2013 1:53:35 pm Alex Keda wrote:
> 03.05.2013 20:41, John Baldwin пишет:
> > On Thursday, May 02, 2013 4:18:45 pm Alex Keda wrote:
> >> see begin in:
> >> http://lists.freebsd.org/pipermail/freebsd-current/2012-
November/038000.html
> >
>
ion(dev), reg);
} else {
start = rman_get_start(res);
pci_write_bar(dev, pm, start);
--
John Baldwin
___
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 Thursday, May 02, 2013 1:53:47 pm Ian FREISLICH wrote:
> John Baldwin wrote:
> > On Thursday, May 02, 2013 7:25:08 am Robert N. M. Watson wrote:
> > >
> > > On 2 May 2013, at 11:42, Glen Barber wrote:
> > >
> > > > Hmm. Perhaps it w
7fffccc8, rbp = 0x7fffcce0 ---
The are both old and known. The bufwait one is documented in ufs_dirhash.c
and is a false positive.
--
John Baldwin
___
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"
ight be seeing a software memory
corruption bug of some sort.
Other users have reported this (Ian Lepore), and Peter Wemm can now reproduce
these at will as well, so I think this is a software bug. What might be
easiest if we can't figure this out from the crashdump is just to bisect the
of
to
work in an environment where I had to largely do post-mortem analysis, I had
to get a gdb environment that was close to as functional. Also, using kgdb
on a live system to obtain info is less invasive than ddb (doesn't halt the
system), and you can easily add new scripts to generate use
ce gdb6'. You can then run 'ps' to get a good
ps listing that includes threads. You can also use 'thread apply all bt' to
get stacktraces of all threads in kgdb. I believe there is an 'allpcpu'
command that is similar to 'show allpcpu' in D
On Tuesday, April 30, 2013 5:19:08 pm Glen Barber wrote:
> On Tue, Apr 30, 2013 at 04:53:13PM -0400, John Baldwin wrote:
> > Try 'p phd' to start. INP_PCBPORTHASH is a macro, so you will
> > have to do it by hand:
> >
> > 'p pcbinfo->ipi_p
On Monday, April 29, 2013 8:35:52 pm Glen Barber wrote:
> On Mon, Apr 29, 2013 at 12:24:06PM -0400, John Baldwin wrote:
> > On Sunday, April 28, 2013 12:02:56 am Glen Barber wrote:
> > > On Sat, Apr 27, 2013 at 10:17:32AM +0200, Ian FREISLICH wrote:
> > > > Hi
>
*/
> 1436 porthash =
> &pcbinfo->ipi_porthashbase[INP_PCBPORTHASH(lport,
> 1437 pcbinfo->ipi_porthashmask)];
> 1438 LIST_FOREACH(phd, porthash, phd_hash) {
> 1439 if (phd->phd_port == lport)
spect driver, but it's similar like on Linux.
> Can you show us the way to resolve this problem?
While the e1000 drivers share the same common code, there are some differences
in the OS-dependent bits (e.g. if_igb.c, etc.). I've cc'd Jack Vogel who
maintains the e1000 dr
d to shuffle the IRQs assigned to the PCI links around. That should
all be moot since you are using the APIC anyway.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
> Ok, the relevant / interesting bit:s. John, any ideas?
Only that this means absolutely nothing? These are the values the BIOS wrote
into the registers which we use as hints about whether or not ACPI lies about
which interrupts
On Fri, Apr 12, 2013 at 11:31:09PM -0600, Scott Long wrote:
>
> On Apr 12, 2013, at 7:43 PM, Rui Paulo wrote:
>
> > On 2013/04/11, at 13:18, Gleb Smirnoff wrote:
> >
> >> Lack of maintainer in a near future would lead to bitrot due to changes
> >> in other areas of network stack, kernel APIs,
On Thursday, April 11, 2013 5:37:48 pm Poul-Henning Kamp wrote:
> In message <201304111050.37055@freebsd.org>, John Baldwin writes:
>
> >> Though if these ports don't have the logic that the AST cards did to
> >> share the IRQ, that'd make it hard...
On Thursday, April 11, 2013 3:01:40 am John-Mark Gurney wrote:
> John Baldwin wrote this message on Wed, Apr 10, 2013 at 10:16 -0400:
> > On Wednesday, April 10, 2013 3:04:15 am Poul-Henning Kamp wrote:
> > > In message <1424327083.20130410103...@serebryakov.spb.ru>, Le
John Baldwin wrote this message on Wed, Apr 10, 2013 at 10:16 -0400:
> On Wednesday, April 10, 2013 3:04:15 am Poul-Henning Kamp wrote:
> > In message <1424327083.20130410103...@serebryakov.spb.ru>, Lev Serebryakov
> writ
> > es:
> > >Hello, Poul-Henning.
> >
On Wednesday, April 10, 2013 2:28:38 am Lev Serebryakov wrote:
> Hello, John.
> You wrote 10 апреля 2013 г., 0:58:22:
>
> >> Problem is, that every uart device now is independent from each
> >> other in good "OOP" style, and it looks like interrupt sharing
port" device, bot not
> >>> exactly.
> >PHK> That is what the puc(4) driver does...
> > Yes, for PCI devices only :(
>
> Yes, it needs to learn to do it from hints for ISA.
No, that is that not the right hammer for this. This isn't a single ISA
dev
On Tuesday, April 09, 2013 4:44:51 pm Lev Serebryakov wrote:
> Hello, John.
> You wrote 10 апреля 2013 г., 0:08:09:
>
> JB> When did it ever work?
> Problem is, that every uart device now is independent from each
> other in good "OOP" style, and it looks like in
When did it ever work?
> God, you made me remember ISA interrupt sharing. I thought the main
> source of evilness is edge shared interrupts?
Right, and ISA are edge and active-hi, so generally not shareable.
Lev,
Can you assign different interrupts via the BIOS somehow?
--
John Baldw
On Thursday, April 04, 2013 12:16:32 pm Andriy Gapon wrote:
> on 19/03/2013 18:20 John Baldwin said the following:
> > Yes, we likely could start using that, we would just need to ensure it has
some
> > sort of minimum size. However, maybe it would always have that minimum
size
On Monday, April 01, 2013 3:56:01 pm Jilles Tjoelker wrote:
> On Mon, Apr 01, 2013 at 02:06:50PM -0400, John Baldwin wrote:
> > Why not use 'local -' instead of the $- magic? That is:
>
> > devfs_rulesets_from_file()
> > {
> >local file
{ while read line
> do
> @@ -1360,6 +1365,7 @@ devfs_rulesets_from_file()
> break
> fi
> done } < $file
> + case $_opts in *f*) ;; *) set +f ;; esac
> return $_err
> }
Why not use 'local -' instead of t
gt; disabled and can be moved to AcpiLeaveSleepState. This is after the _BFS and
> _GTS support was removed.
>
> What do you think?
> Thank you.
Hmm, I think intr_table_lock used to be a spin lock at some point. I don't
remember
why we changed it to a regular mutex. It may be that
se, you
might choose to not include USB, but use ATA, or not use umass, but
the rest of USB...
Someone on a list was talking about trying to get FreeBSD down on a
really small system, 16MB ram...
/me thinks of the old wd driver.
--
John-Mark Gurney Voice: +1 415 22
deeptech71 wrote this message on Fri, Mar 22, 2013 at 15:55 +0100:
> The obvious fix: widen the scope of ``#ifdef DES'':
Thanks, committed in r248656.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All th
quot;real" root. I think your
change is fine.
--
John Baldwin
___
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"
at 1MB is too small. A minimum size of 16MB
might
handle that case correctly while using the first extended region in the common
case.
> Additionally, in the case of zfsboot I think that we do not use memory above
> 1MB
> for anything else besides the heap.
You load either /boot/zfsloader or the kernel there.
--
John Baldwin
___
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 Friday, March 15, 2013 11:24:32 am Andre Oppermann wrote:
> On 15.03.2013 14:46, John Baldwin wrote:
> > On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote:
> >> Hi Rick, all,
> >>
> >> is there a plan to decide for one NFS implementation for FreeB
y and being in a position of still using 8.x with oldNFS in production,
I would prefer to not remove it quite yet.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
failed
You can ignore those. acpi is trying to reserve the addresses used for RAM
as system resources, but the ram0 driver has already done so.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
On Thursday, March 14, 2013 4:21:02 pm Pawel Jakub Dawidek wrote:
> On Thu, Mar 14, 2013 at 10:11:07AM -0700, Chuck Swiger wrote:
> > Hi--
> >
> > On Mar 14, 2013, at 9:50 AM, John Baldwin wrote:
> > > On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrot
On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrote:
> On Thu, Mar 14, 2013 at 09:42:40AM -0400, John Baldwin wrote:
> > On Thursday, March 14, 2013 4:44:20 am Pawel Jakub Dawidek wrote:
> > > On Thu, Mar 14, 2013 at 08:28:25AM +0100, Dirk Engling wrote:
> > &
ar *path, mode_t mode, pid_t
*pidptr = -1;
if (errno == 0 || errno == EAGAIN)
errno = EEXIST;
- }
+ } else if (errno == EWOULDBLOCK)
+
if (errno == EWOULDBLOCK) {
+ if (pidptr == NULL)
+ pidptr = &dummy;
count = 20;
rqtp.tv_sec = 0;
rqtp.tv_nsec = 500;
--
John Baldwin
___
.d/netif start" if you don't want to
reboot, but I've never done that.. I've just rebooted, since this
is my router and I want to make sure it comes up...
Good luck...
> On Tue, Mar 12, 2013 at 11:39 PM, John-Mark Gurney wrote:
>
> > Yasir hussan wrote this message o
er enabling it in HEAD only just as we do with INVARIANTS, etc.
However, when it was added it was never intended to be used for
production.
--
John Baldwin
___
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"
oadcast 10.0.1.255
> > media: Ethernet autoselect (1000baseT )
> > status: active
> >
> > These are both the same thing. Is there any particular reason that
> > you want multiple interfaces? I can't see a use for it beyond "it's
> > what
cum commits? It broke some other stuff initially related to fd passing,
so I don't think it is beyond imagination that it broke something with UNIX
domain sockets in general.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.
On Thursday, February 28, 2013 8:15:46 am matt wrote:
> On 02/27/13 12:27, John Baldwin wrote:
> > On Wednesday, February 27, 2013 1:35:43 pm matt wrote:
> >> On 02/27/13 09:00, John Baldwin wrote:
> >>> If that is true, it's because your BIOS is lying. Do you
On Wednesday, February 27, 2013 1:17:40 pm matt wrote:
> On 02/27/13 09:08, John Baldwin wrote:
> > On Sunday, February 24, 2013 2:57:32 pm matt wrote:
> >> What does this mean exactly?
> >>
> >> Whenever I call/evaluate certain ACPI paths, this gets printed o
On Wednesday, February 27, 2013 1:35:43 pm matt wrote:
> On 02/27/13 09:00, John Baldwin wrote:
> > If that is true, it's because your BIOS is lying. Do you have a URL to
> > your ASL lying around already?
> Too big for pastebin :( +500k
>
> h
IC_ESR_ILLEGAL_REGISTER 0x0080
It means something wrote to an invalid lapic register. It is probably a bug
in your BIOS, yes.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curre
On Tuesday, February 26, 2013 9:32:33 pm matt wrote:
> On 02/26/13 10:46, John Baldwin wrote:
> > On Monday, February 25, 2013 11:20:29 pm matt wrote:
> >> On 02/25/13 18:33, Adrian Chadd wrote:
> >>> [101232] acpi_video0: on vgapci0
> >>> found Internal
evice in the ACPI namespace. Thus, the specific handle assigned by ACPI
is for the exact PCI location of the requisite vgapci device. If your
BIOS lies it is hard for us to do anything useful, at least automatically.
Do the other devices in your system that have _DOD
On Monday, February 25, 2013 7:47:47 am Olivier Houchard wrote:
> On Mon, Feb 25, 2013 at 07:09:20PM +1300, Andrew Turner wrote:
> > On Thu, 21 Feb 2013 10:43:49 -0500
> > John Baldwin wrote:
> >
> > > On Thursday, February 21, 2013 7:53:52 am Svatopluk Kraus wrote
el like that is definitely the wrong way.
> A tunable for an acpi_video override might be useful, but it still
> leaves potentially the wrong path in vgapci's IVARs.
>
> Is there a better place to "correct" the ACPI_PATH that gets stored in
> vgapci's ivar? Is
-current broken on pre-PPro machines (w/ work around)
http://www.freebsd.org/cgi/mid.cgi?20130201170737.gp1...@funkthat.com
The work around is to use gcc which will not emit the cmov instructions...
--
John-Mark Gurney Voice: +1 415 225 5579
"Al
sr/obj/usr/src/sys/GENERIC amd64
And I haven't installworld yet... so somehow supporting the AES
instructions in gcc causes the kernel to miscompile...
I'm now going to diff the two kernels to find out what's different...
--
John-Mark Gurney
, not userland) and figure
out which part of the system.. But clearly, we are still using gcc
somehow in our kernel builds...
If I don't figure out what it is in a few hours, I'll back out the
change...
--
John-Mark Gurney Voice: +1 415 225 5579
On Thursday, February 21, 2013 7:53:52 am Svatopluk Kraus wrote:
> On Wed, Feb 20, 2013 at 4:22 PM, John Baldwin wrote:
> > On Wednesday, February 20, 2013 7:31:08 am Svatopluk Kraus wrote:
> >> On Tue, Feb 19, 2013 at 7:51 PM, Konstantin Belousov
> >> wrote:
> >
still trying to find out which revision have broke the stuff.
>
> I ran into this earlier today. Selecting "safe mode" in the boot loader
> menu seems to work around the problem on my system. Now I will not
> reboot until I see a fix for this in head :-)
"safe
On Wednesday, February 20, 2013 2:27:39 pm Konstantin Belousov wrote:
> On Wed, Feb 20, 2013 at 10:22:29AM -0500, John Baldwin wrote:
> > On Wednesday, February 20, 2013 7:31:08 am Svatopluk Kraus wrote:
> > > On Tue, Feb 19, 2013 at 7:51 PM, Konstantin Belousov
> > >
rthread has to be
atomic. If your read of curthread looks like:
mov , r0
add , r0
ld r0, r1
Then that will indeed break. Alpha used a fixed register for 'pcpu_reg'
(as does ia64 IIRC). OTOH, you might also be
a
-lm
> ./.libs/libsox.so: undefined reference to `open_memstream'
I'm guessing it thinks that we have open_memstream() because someone added
fmemopen() recently. I have an implementation of open_memstream() that I will
commit soon.
--
John Baldwin
_
/usr/share/mk is for use by projects
outside /usr/src...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
___
freebsd-current@freebsd.org mailing
t(&object, 0, sizeof object);
>
> or
>
> memset(&pointer, 0, sizeof *pointer);
>
> but apparently it is difficult to choose the right one. :)
I assume you mean:
memset(pointer, 0, sizeof *pointer);
:)
--
John-Mark Gurney
On Friday, February 15, 2013 10:10:12 am Jilles Tjoelker wrote:
> On Wed, Feb 13, 2013 at 11:44:19AM -0500, John Baldwin wrote:
> > On Thursday, February 07, 2013 4:12:22 pm Jilles Tjoelker wrote:
> > > On Tue, Feb 05, 2013 at 03:46:43PM -0500, John Baldwin wrote:
>
On Thursday, February 14, 2013 9:45:22 pm Adrian Chadd wrote:
> On 14 February 2013 13:35, John Baldwin wrote:
>
> > ISA bounces anything above 16GB. They are bouncing. I know it works for
> > some
> > people as I fixed a bug in the ISA bounce buffer code somewhat
works for some
people as I fixed a bug in the ISA bounce buffer code somewhat recentish:
http://svnweb.freebsd.org/base?view=revision&revision=233675
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
. The
> modules seems to build fine without having to
> fiddle about with kernel config jiggerypokey.
COMPAT_LINUX will work on amd64 eventually and will be used for 64-bit Linux
binaries (COMPAT_LINUX32 is to run Linux/i386 binaries on FreeBSD/amd64).
--
John Baldwin
___
On Thursday, February 07, 2013 4:12:22 pm Jilles Tjoelker wrote:
> On Tue, Feb 05, 2013 at 03:46:43PM -0500, John Baldwin wrote:
> > I've written an implementation of open_memstream() and
> > open_wmemstream() along with a set of regression tests. I'm pretty
> > s
ints at the
directory holding the custom libc.
--
John Baldwin
___
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"
partially parsed character we
aren't going to get the rest of it.
http://www.FreeBSD.org/~jhb/patches/open_memstream.patch
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To un
ee on screen is
>
> p4tcc3: on cpu3
>
> then the system run dark and reboots without any notice (kernel doesn't
> have debugging switched on so far, will do this after Monday).
I don't think there are any known issues. Can you narrow it down to
ou
use gcc instead of clang...
A bug has been filed:
http://llvm.org/bugs/show_bug.cgi?id=15115
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
___
freebsd
e_bar);
> >> - else
> >> - printf("in maps 0x%x and 0x%x", table_bar, pba_bar);
> >> + if (table_bar == pba_bar) {
> >> + printf("in map 0x%x[0x%x][0x%x]",
instead of one of the
headers on HEAD. (and this is my fault)
Alexey, can you patch the port for that?
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mai
rio)
> td->td_priority = prio;
> if (prio < tdq->tdq_lowpri)
> tdq->tdq_lowpri = prio;
> - else if (tdq->tdq_lowpri == oldpri)
> + else if (tdq->tdq_lowpri == oldpri) {
> t
On Saturday, January 26, 2013 9:18:57 am Andriy Gapon wrote:
> on 25/01/2013 18:08 Andriy Gapon said the following:
> > on 25/01/2013 15:51 John Baldwin said the following:
> >> On Friday, January 25, 2013 3:43:33 am Andriy Gapon wrote:
> >>>
> >>> If y
oth in the kernel and in the preloaded file and
> the module has a module event handler (modeventhand_t), then the handler will
> registered and called twice.
Yes, I think it is too hard at present to safely allow a linker file to
override the same module in a kernel, so the duplic
d. It should also be registered before any of the I/O APICs are by
the design of the local_apic.c code.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to &quo
nothing else, the length should be a
size_t instead of an int.
--
John Baldwin
___
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;t test it. Look at "buildworld is broken ?" thread
Looks like this broken when jkim imported the latest ACPICA code base:
https://svnweb.freebsd.org/base?view=revision&revision=245582
I've forward the tinderbox failure to him, so hopefully he'll fix
rgv(char **, char *, size_t);
+const char *fmt_argv(char **, char *, char *, size_t);
double getpcpu(const KINFO *);
char*kvar(KINFO *, VARENT *);
char*label(KINFO *, VARENT *);
--
John Baldwin
___
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"
ial port.)
I think adding -b is fine.
--
John Baldwin
___
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"
John-Mark Gurney wrote this message on Tue, Jan 15, 2013 at 15:10 -0800:
> hiren panchasara wrote this message on Tue, Jan 15, 2013 at 07:52 -0800:
> > http://www.strugglingcoder.info/patches/clang_warnings_dev_bktr.txt
>
> This patch does not look correct at all... It is simpl
on?
What is the warning that we are fixing here?
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
___
freebsd-current@freebsd.org mailing list
http://list
On Monday, January 14, 2013 5:44:42 pm Konstantin Belousov wrote:
> On Mon, Jan 14, 2013 at 04:39:17PM -0500, John Baldwin wrote:
> > This patch adds a new -r flag to dump the resource usage information (what
you
> > would get from getrusage() or wait()) for a given process.
1101 - 1200 of 4747 matches
Mail list logo
