/sys/GRAN-TOURISMO
amd64
My KERNCONFs, make.conf, and src.conf are provided for reference.
Thanks,
-Garrett
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
.
misordered hunks! is a lie, because the whole patch consisted of exactly
one hunk.
This was quite confusing.
$ patch --version
Patch version 2.1
gpatch worked as expected:
patching file
Hunk #1 FAILED at 55.
1 out of 1 hunk FAILED -- saving rejects to file .rej
--
Andriy Gapon
@ FBSD_1.0;
^
I would appreciate any help with getting this straightened.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
of these for the lifetime of the 10.x branch.
I have an alternative proposal (to re@ and core@) to set WITHOUT_CLANG_IS_CC
in stable/10 or at least releng/10.0.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
that is used for
toolchain target.
Dependency between NO_WARNS and CSTD was removed in r198335 + r198365, but those
were never MFC-ed.
What do you think?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
a compiler from ports or switch to clang as their default
compiler.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr
on 23/08/2013 15:34 Nathan Whitehorn said the following:
On 08/23/13 07:26, Andriy Gapon wrote:
on 23/08/2013 14:06 David Chisnall said the following:
Our gcc is from 2007. It has no C11, no C++11 support. It has bugs in its
atomic generation so you can't use it sensibly without lots
of ugly code to make it work with old compilers. I will be very
happy to remove a load of hacks once C++11 support is available in the base
system (not for 10.0, as dtc is used on a lot of tier 2 archs where gcc is
still default).
--
Andriy Gapon
systems.
However I observe the following:
$ echo cd0 cd1 xx | sed 's/cd[0-9][^ ]* *//g'
xx
$ echo cd0 cd1 xx | sed 's/[[::]]cd[0-9][^ ]* *//g'
cd1 xx
In my opinion '[[::]]' should not affect how the pattern is matched in this
case.
Any thoughts, suggestions?
Thank you!
--
Andriy Gapon
on 02/09/2013 17:54 Andriy Gapon said the following:
re_format(7) says:
There are two special cases‡ of bracket expressions: the bracket expres‐
sions ‘[[::]]’ and ‘[[::]]’ match the null string at the beginning and
end of a word respectively. A word is defined as a sequence
on 30/09/2013 02:11 kwh...@site.uottawa.ca said the following:
Sorry, debugging this is *way* beyond me. Any hints, patches to try?
Please share the stack trace.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
on 02/10/2013 20:59 Keith White said the following:
On Wed, 2 Oct 2013, Andriy Gapon wrote:
on 30/09/2013 02:11 kwh...@site.uottawa.ca said the following:
Sorry, debugging this is *way* beyond me. Any hints, patches to try?
Please share the stack trace.
--
Andriy Gapon
There's now
--
Andriy Gapon
___
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
=0xf8000524f000, traced=0) at
subr_syscall.c:134
#15 0x80c979fb in Xfast_syscall () at
/usr/src/sys/amd64/amd64/exception.S:391
#16 0x0008019f49ca in ?? ()
Previous frame inner to this frame (corrupt stack?)
Current language: auto; currently minimal
(kgdb)
...keith
--
Andriy
,3DNow!+,3DNow!
AMD
Features2=0x837ffLAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,NodeId
TSC: P-state invariant
FreeBSD/SMP: Multiprocessor System Detected: 48 CPUs
FreeBSD/SMP: 4 package(s) x 12 core(s)
--
Andriy Gapon
still in BETA. It
would be nice if powerd worked out of the box on those chips.
I am *not* looking into this.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
++ and libc++.
--
Andriy Gapon
___
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
should be automatically imported.
--
Andriy Gapon
___
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
same behavior.
What does zdb -C report?
--
Andriy Gapon
___
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
These are just trivial wrappers based on the fact that int and long on i386 have
the same bit layout and likewise for long and long long on amd64.
For your reviewing pleasure :-)
Thanks!
commit fdc1228b113f8b4c9dbda2b0323cb087c6b6df9d
Author: Andriy Gapon a...@icyb.net.ua
Date: Thu Nov 7 19:13
;
-CORE_ADDR amd64fbsd_sigtramp_end_addr = 0x7fe0;
+CORE_ADDR amd64fbsd_sigtramp_start_addr = 0x7000;
+CORE_ADDR amd64fbsd_sigtramp_end_addr = 0x7020;
/* From machine/signal.h. */
int amd64fbsd_sc_reg_offset[] =
--
Andriy Gapon
No such line 52 in input file, ignoring
No such line 45 in input file, ignoring
Is this a cause for concern?
Do those messages mean that potentially important patches are not actually
applied?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
on 26/11/2013 11:57 Andriy Gapon said the following:
Author: avg
Date: Tue Nov 26 09:57:14 2013
New Revision: 258632
URL: http://svnweb.freebsd.org/changeset/base/258632
Log:
MFV r255255: 4045 zfs write throttle i/o scheduler performance work
illumos/illumos-gate
on 27/11/2013 18:17 Andriy Gapon said the following:
on 26/11/2013 11:57 Andriy Gapon said the following:
Author: avg
Date: Tue Nov 26 09:57:14 2013
New Revision: 258632
URL: http://svnweb.freebsd.org/changeset/base/258632
Log:
MFV r255255: 4045 zfs write throttle i/o scheduler
macros.
ASSERT is compiled out when DEBUG is not set while VERIFY is always kept.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current
:-)
BTW, for a while now we have some support for interacting with the watchdog(9)
from within the kernel. I have the following local patch / hack that makes use
of that support:
commit b64c5e855420f2d905a04f69fad5de116e8ffae5
Author: Andriy Gapon a...@icyb.net.ua
Date: Fri Nov 25 10:00:59 2011
|MAP_STACK_GROWS_UP);
3342 cow = ~orient;
--
Andriy Gapon
___
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
));
if (addrbos vm_map_min(map) ||
I can confirm that the patch fixes the problem for me.
Thanks!
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
on 04/06/2011 11:22 Andriy Gapon said the following:
commit 458ebd9aca7e91fc6e0825c727c7220ab9f61016
generic_stop_cpus: move timeout detection code from under DIAGNOSTIC
... and also increase it a bit.
IMO it's better to detect and report the (rather serious) condition
on 03/06/2011 18:13 Andriy Gapon said the following:
I wonder if anybody uses kdb_stop_cpus with non-default value.
I would like to go ahead and remove kdb_stop_cpus tunable/sysctl if nobody
objects.
If, yes, I am very interested to learn about your usecase for it.
I think
similar:
http://lists.freebsd.org/pipermail/freebsd-current/2010-October/020336.html
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current
manually. 'MFC after' only states original intent. Sometimes
developers forget to do MFC; sometimes they discover new circumstances which
prevent MFC; etc.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
will be able to sneak it
into the 9 release (unless there are objections to this).
Thank you!
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd
3. using su+j, gjournal or a different filesystem altogether
4. using fsck after reboot
It seems to me that syncing filesystems in panic context is an adventure. And
it
may become even more of an adventure if we introduce code that completely stops
scheduler in and after panic.
--
Andriy Gapon
: 40.000MB/s transfers
Jun 25 13:15:47 blue kernel: da0: 983MB (2015231 512 byte sectors: 64H 32S/T
983C)
Jun 25 13:15:47 blue kernel: (sg0:umass-sim0:0:0:0):
cam_periph_release_locked:
release 0xc47bfc00 when refcount is zero
Hm, I have to ask, have you tried this without sg driver?
--
Andriy
on 26/06/2011 08:51 Warner Losh said the following:
On Jun 25, 2011, at 8:49 AM, Andriy Gapon wrote:
Does anybody actually use kern.sync_on_panic tunable/sysctl? If yes, then
in what circumstances do you need it? That is, why any other alternative
doesn't work for you? Like: 1. remounting
is
unclean an needs to be fsck'ed.
Will proceed with a verbose kernel.
I think that procstat -kk output for at least one stuck process could also turn
out to be useful.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
(it
was also driven via Super I/O), but that was totally, well, just for fun.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr
not 224 and if you haven't tried 224 yet, then could you please try
it and see if there is any improvement?
This assumes that you use SCHED_ULE (kern.sched.name is ULE).
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
on 06/07/2011 15:35 arrowdodger said the following:
On Wed, Jul 6, 2011 at 3:37 PM, Andriy Gapon a...@freebsd.org
mailto:a...@freebsd.org wrote:
Just curious what your current value of sysctl kern.sched.preempt_thresh
is.
And if it's not 224 and if you haven't tried 224 yet
I think that if you use non-base gcc for ports on CURRENT, then you need to
follow
this procedure after upgrading world to a revision after the cpumask_t/cpuset_t
change:
1. upgrade/re-install gccXX using base gcc as a bootstrap compiler (make CC=gcc)
2. everything else... :)
--
Andriy Gapon
on 06/07/2011 16:33 Alexander Best said the following:
you might also want to try enabling options IPI_PREEMPTION. no idea, if this
improves your situation, though.
Just in case, this option has effect for 4BSD scheduler only.
--
Andriy Gapon
, then could you please
try
it and see if there is any improvement?
This assumes that you use SCHED_ULE (kern.sched.name is ULE).
--
Andriy Gapon
Whoa, it's definitely better! Thanks a lot. But still, when IO causes system
to use swap, X11 became completely unusable.
I had
that it's not the same problem as sub-optimal performance of heavy CPU-bound
load, which is what you reported if I am not mistaken.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
to a past discussion, if any, would suffice.
--
Andriy Gapon
___
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
they bind their threads to CPUs
to avoid the situation that you describe. Apparently they didn't know how to do
CPU-binding on FreeBSD, so this is not implemented. You may have a motivation
to help them out with this.
--
Andriy Gapon
___
freebsd-current
on 07/07/2011 18:14 Steve Kargl said the following:
On Thu, Jul 07, 2011 at 10:27:53AM +0300, Andriy Gapon wrote:
on 06/07/2011 21:11 Nathan Whitehorn said the following:
On 07/06/11 13:00, Steve Kargl wrote:
AFAICT, it is a cpu affinity issue. If I launch n+1 MPI images
on a system with n
of that software on that platform as indication that there is something wrong
with
the platform, not the software.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
to
commit? And are you prepared to take responsibility for quality of your
reviews?
I am sure that other developers will gladly accept your offer too.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
on 12/07/2011 00:48 Arnaud Lacombe said the following:
Hi,
On Mon, Jul 11, 2011 at 5:14 PM, Andriy Gapon a...@freebsd.org wrote:
on 11/07/2011 23:33 Arnaud Lacombe said the following:
For the record, I would like to see enforced public review for _every_
patch *before* it is checked
on 11/07/2011 19:16 Steve Kargl said the following:
On Mon, Jul 11, 2011 at 06:07:04PM +0300, Andriy Gapon wrote:
But it's not clear which of the processes are slaves and which is master.
It's also not clear why the master takes so much CPU (on par with the
slaves) -
from my reading of its
before reporting a regression...
FWIW, smp(4) still documents machdep.hlt_cpus and machdep.hlt_logical_cpus.
It should probably be updated with hint.lapic.X.disabled from UPDATING.
Yes.
Thank you for the reports.
--
Andriy Gapon
___
freebsd-current
on 15/05/2011 19:24 Andriy Gapon said the following:
on 15/05/2011 19:09 Max Laier said the following:
I don't think we ever intended to synchronize the local teardown part, and I
believe that is the correct behavior for this API.
This version is sufficiently close to what I have, so I am
on 17/05/2011 18:51 John Baldwin said the following:
On Tuesday, May 17, 2011 10:34:41 am Andriy Gapon wrote:
on 17/05/2011 16:58 John Baldwin said the following:
No, it doesn't quite work that way. It wouldn't work on Alpha for example.
All load_acq is a load with a memory barrier to order
This is a reminder that if you would like to see the code for sane panic(9)
context in 9.0, then I still need at least one independent reviewer and tester
for
the code. Thank you.
on 25/06/2011 17:37 Andriy Gapon said the following:
I would like to ask for testing of the following patch
.
No warning, either.
Are you sure about this one?
I have never expected that any installer would be able to create or delete
hardware (a hard disk) in my computer.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
on 12/07/2011 11:05 Andriy Gapon said the following:
I think that the best thing you can further provide (as objective evidence for
the problem at hand) is ktr(4) traces for at least KTR_SCHED mask. Perhaps
you
even already have them from your previous sessions with Jeff.
P.S
nothing (exit 1)
So looks like a potential bug in some optimization.
-w works correctly without -r. With -r it works correctly for some substrings,
but not for others.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
This is to account for the recent changes in x86 SMP code:
http://people.freebsd.org/~avg/hlt_cpus-doc.diff
Please review. Thank you!
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
. Not sure if there are any
alternative approaches.
--
Andriy Gapon
___
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
: movq$0,0x6b4e62(%rip)
db ps
--
Andriy Gapon
___
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 taskqueue_thread_loop+0x4e
fork_exit() at fork_exit+0x11f
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xff8000160d00, rbp = 0 ---
KDB: enter: panic
[thread pid 0 tid 100033 ]
Stopped at kdb_enter+0x3b: movq $0,0x6b4e62(%rip)
db ps
--
Andriy Gapon
...
--
Andriy Gapon
___
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
to know what
that is?
I think I've already referred to the thread on stable@.
This is currently being investigated.
P.S.
Just a pure illustration you can grep for thread_lock to see where else outside
schedulers the sched locks are taken.
--
Andriy Gapon
exactly the same sets
of
CPUs.
--
Andriy Gapon
___
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
with static storage should be initialized with all zeros.
--
Andriy Gapon
___
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
the kernel and the one from the .ko) which causes
the panic.
Tangentially related: kib has/had a patch for proper hiding of static symbols
from
kernel runtime linker symbol resolution. It would be nice to get that into the
tree some day.
--
Andriy Gapon
on 01/08/2011 15:47 John Baldwin said the following:
On Sunday, July 31, 2011 11:22:18 am Andriy Gapon wrote:
Just an observation:
- print_INTEL_info and print_INTEL_TLB are missing from amd64 identcpu.c
- print_INTEL_TLB doesn't cover all the codes defined by Intel specs
- not sure; perhaps
) ?
Thanks for 9.0, looks nice.
--
Andriy Gapon
___
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
-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current
= 0xbfbfeca8 ---
Uptime: 1m10s
Rebooting...
--
Andriy Gapon
___
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
the by the end-users).
--
Andriy Gapon
___
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
it before it
actually proves itself on practical tasks. Or has it already? I might have
missed that.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
on 05/08/2011 18:40 Vlad Galu said the following:
On Fri, Aug 5, 2011 at 5:34 PM, Andriy Gapon a...@freebsd.org wrote:
on 05/08/2011 18:23 Vlad Galu said the following:
Netmap's scope may be narrow, but it's a great alternative to
proprietary implementations that are provided by only a handful
TEL +39-050-2211611 . via Diotisalvi 2
Mobile +39-338-6809875 . 56122 PISA (Italy)
-+---
--
Andriy Gapon
___
freebsd-current@freebsd.org
to be in your make.conf.
--
Andriy Gapon
___
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 28/07/2011 17:09 Andriy Gapon said the following:
$ fgrep -w -r CS drm
...
drm/include/drm/drm_mode.h:#define DRM_MODE_FLAG_NCSYNC (18)
$ fgrep -w -r CSY drm
...
drm/include/drm/drm_mode.h:#define DRM_MODE_FLAG_NCSYNC (18)
$ fgrep -w -r CSYN drm
nothing (exit 1)
$ fgrep -w -r NCS drm
TOLOG is set.
Maybe try to add !kdb_active condition for cnputs() call in vprintf().
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current
+0x996 0x805AB6C4 at kern_kldload+0xB4
0x805AB894 at kldload+0x84 0x80600DD5 at
syscallenter+0x1E5 0x808ACA5B at syscall+0x4B 0x80895292
at Xfast_syscall+0xE2
--
Andriy Gapon
___
freebsd
.JPG).
You should investigate and fix that.
Meanwhile you may want to set the kern.geom.part.check_integrity loader tunable
to
zero (either in loader prompt or in loader.conf).
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http
-allocate a BAR).
This makes only if the BAR has sane values. Not sure what happens if the BAR
has
some junk that duplicates other PCI device, or something like that.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
on 16/08/2011 22:09 John Baldwin said the following:
On Tuesday, August 16, 2011 12:26:11 pm Andriy Gapon wrote:
The following are pure speculations, I'd rather let David speak, but just in
case;
on 16/08/2011 18:45 John Baldwin said the following:
Well, that would seem odd, still
first.
--
Andriy Gapon
___
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 21/08/2011 20:47 Derrick Edwards said the following:
On Fri, 2011-08-19 at 17:21 +0300, Andriy Gapon wrote:
on 19/08/2011 01:07 Derrick Edwards said the following:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xbe00a45b6798
want to try to reproduce this panic with the following patch:
http://article.gmane.org/gmane.os.freebsd.stable/76534
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
would include not invoking those lock-related operations or other
inappropriate operations).
Thank you very much in advance for your insights and help!
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
vfs_mountroot_conf0(struct sbuf *sb)
{
char *s, *tok, *mnt, *opt;
int error;
sbuf_printf(sb, .onfail panic\n);
...
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
on 29/08/2011 10:10 Roger Genre said the following:
Perhaps I miss some important new feature introduced in 9.0 to work around
that
problem ?
Most likely you just overlook a CAM feature that you have not needed before.
Please see cam(4), search for 'wired'.
--
Andriy Gapon
on 27/08/2011 18:16 Marcel Moolenaar said the following:
On Aug 26, 2011, at 2:07 PM, Andriy Gapon wrote:
It seems that after the introduction of the mountroot scripting language a
user
now has exactly one chance to try to specify a correct root device at the
mountroot prompt. I am
on 29/08/2011 19:45 Marcel Moolenaar said the following:
On Aug 29, 2011, at 1:21 AM, Andriy Gapon wrote:
on 27/08/2011 18:16 Marcel Moolenaar said the following:
On Aug 26, 2011, at 2:07 PM, Andriy Gapon wrote:
It seems that after the introduction of the mountroot scripting language
So, just to re-iterate, I think that this is indeed a regression and the one
that could be particularly unhelpful for a new release - the time when people
are much more likely to end up at the mountroot prompt during an installation of
a new system or an upgrade.
on 29/08/2011 23:19 Andriy Gapon
about
when to fix it.
4. There is a missing developer/maintainer for DTrace on FreeBSD.
Nevertheless the kernel DTrace is quite usable and useful for kernel debugging.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
on 30/08/2011 18:39 Andriy Gapon said the following:
4. There is a missing developer/maintainer for DTrace on FreeBSD.
I probably should clarify this point: it doesn't have to be *the* maintainer, a
collective maintainer is also perfect. Thus, contributions are very welcome.
Nevertheless
!
--
Andriy Gapon
___
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
-a option was given or mounting of
${vfs.mountroot.from} failed
- there is no way of the prompt (as you noted above) - previously an empty input
was the way out
So, even if .onfail retry is an improvement comparing to .onfail panic, it's
still
a regression comparing to the previous behavior.
--
Andriy
/dev/acd0 /cdrom cd9660 ro,noauto 00
proc /proc procfs rw 00
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
a small patch that adds FFS volume label/name support to makefs:
http://people.freebsd.org/~avg/makefs.ffs-label.diff
Documentation is not updated.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
in post-panic environment:
http://people.freebsd.org/~avg/stop_scheduler_on_panic.usb.diff
The patch is the same for both head and stable/8.
It shouldn't hurt if you don't use USB devices or use other USB devices.
--
Andriy Gapon
___
freebsd-current
on 03/08/2011 01:06 John Baldwin said the following:
On Saturday, July 30, 2011 2:49:52 am Andriy Gapon wrote:
on 19/07/2011 18:16 John Baldwin said the following:
Hmm, can you get devinfo -r output from a working kernel with ichwd loaded?
You might be able to just build the kernel
it with gmake
- the only porting change needed is s/elf_i386/elf_i386_fbsd/ in the makefile
- installed out/bio.bin to ${LOCALBASE}/share/qemu/seabios.bin for convenience
- used it with -bios seabios.bin option to qemu
--
Andriy Gapon
___
freebsd-current@freebsd.org
1 - 100 of 1235 matches
Mail list logo
