ERIC-NODBG-CA72
arm64 aarch64 1300139 1300139
Cannot reproduce here (but with much simpler names and on stable/13):
zfs create testz/test
zfs snapshot testz/test@snap1
zfs rename testz/test testz/test2
All worked.
--
Andriy Gapon
___
freebsd-stable@f
On 14/04/2021 16:32, Mark Johnston wrote:
On Wed, Apr 14, 2021 at 02:21:44PM +0300, Andriy Gapon wrote:
On 14/04/2021 00:18, Mark Johnston wrote:
fbt::vm_page_unwire:entry
/args[0]->oflags & 0x4/
{
@unwire[stack()] = count();
}
Unrelated report, dtrace complains about thi
oflags type=3 off=760
psind type=2167 off=768
segind type=2167 off=776
valid type=3574 off=784
dirty type=3574 off=792
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/free
ate it with any activity.
P.S.
I have not been running any virtual machines.
I do use nvidia graphics driver.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe
On 07/04/2021 22:54, Mark Johnston wrote:
> On Wed, Apr 07, 2021 at 10:42:57PM +0300, Andriy Gapon wrote:
>>
>> I regularly see that the top's memory line does not add up (and by a lot).
>> That can be seen with vm.stats as well.
>>
>> For example:
&
er of pages either.
Approximately 2 million pages, 8 gigabytes or 25% of the whole memory on this
system.
This is 47c00a9835926e96, 13.0-STABLE amd64.
I do not think that I saw anything like that when I used (much) older FreeBSD.
--
Andriy Gapon
___
freebsd-
On 20/03/2021 05:01, Yoshihiro Ota wrote:
> On Tue, 9 Mar 2021 11:24:53 +0200
> Andriy Gapon wrote:
>
>> On 08/03/2021 05:24, Yoshihiro Ota wrote:
>>> On Sun, 7 Mar 2021 00:09:33 +0200
>>> Andriy Gapon wrote:
>>>
>>>> On 06/03/2021 20:
On 08/03/2021 05:24, Yoshihiro Ota wrote:
> On Sun, 7 Mar 2021 00:09:33 +0200
> Andriy Gapon wrote:
>
>> On 06/03/2021 20:09, Yoshihiro Ota wrote:
>>> Hi all,
>>>
>>> I'm upgrading fron 12.2-RELEASE to 13-BETA/RC one by one.
>>>
>>> Af
install world/kernel and mergemaster.
Please use procstat -kk to capture a kernel stack trace of the hung process.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any ma
gt;
> Thank you in advance and best regards,
I think that this is worth a PR.
I think that even when mounting read-only the underlying GEOM object should be
marked for exclusive use.
I vaguely recall that UFS has some quirk in this respect to allow for
modifications by fsck. That is supposed to be limited to the root filesystem.
Maybe it should further be limited to certain boot stages to prevent
foot-shooting after a system is fully booted.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 28/02/2021 20:12, David Wolfskill wrote:
> Various devices under src/sys/dev/hid are available in base under
> stable/13 and head; are they available in some way under stable/12?
Yes, they are part of iichid package.
--
Andriy Gapon
___
f
"clear stall" (clearing halt on endpoints)
# CH340 USB<->RS232 requires this
# and it seems that Linux and Windows do this by default
hw.usb.no_cs_fail=1
I recall that without that tuning I had a similar problem.
> вт, 5 июн. 2018 г. в 15:05, Ian FREISLICH :
>
>> On 0
ually exist
(or has a different ID).
This is a logical inconsistency, not a data integrity issue.
So, a scrub, being a data integrity check, would not detect such an issue.
Hypothetical zfs_fsck is needed to find and repair such logical problems.
Does that pool and filesystem have any special history?
I
On 22/02/2021 16:20, Chris Anderson wrote:
> On Mon, Feb 22, 2021 at 1:36 AM Andriy Gapon <mailto:a...@freebsd.org>> wrote:
>
> On 22/02/2021 09:31, Chris Anderson wrote:
> > None of these files are especially important to me, however I was
> wondering
&g
On 22/02/2021 09:31, Chris Anderson wrote:
> None of these files are especially important to me, however I was wondering
> if there would be any benefit to the community from trying to debug this
> issue further to understand what might be going wrong.
Yes.
--
And
Does anyone use ZFS with a 32-bit kernel, that is also not i386 ?
If you do, could you please let me know? Along with uname -rmp output.
Thank you!
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman
Has anyone ever tested a kernel with option RSS and an ixv interface?
Just looking for some data points.
Thanks!
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe
nd (meaning neither the on-board
cache is flushed nor the command is propagated to a disk). So, if you use some
advanced controller it would make sense to use its own management tool to
offline a disk before pulling it.
I do not preclude a possibility of an issue in ZFS. But it
omething called DTL, a dirty-time log, for a missing / offlined /
removed device. When the device re-appears and gets resilvered, ZFS walks only
those blocks that were born within the TXG range(s) when the device was missing.
In any case, I do not have an explanation for what you are seeing
after
it was recycled.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ceed. I
cannot understand how the vnode lock could be held by another thread.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
each(@F)) { 1 while
s/^(-?\d+)(\d{3})/$1,$2/; print $_, " "} print "\n"' | column -t
This would be much nicer as a small python script.
Or, even, we could add a sort option for vmstat -z / -m.
--
Andriy Gapon
___
freebsd-stable@freebs
w.ocpea.com/dump/core.txt>
This is useless because you do not have debug symbols for the kernel.
> Does anyone have any idea how we can go about discovering the cause for
> this? We would appreciate any suggestion ...
--
Andriy Gapon
___
f
On 14/12/2018 21:37, Sascha Klauder wrote:
> On Fri, 2018-12-14 11:56 +0200, Andriy Gapon wrote:
>> On 13/12/2018 12:56, Sascha Klauder wrote:
>>> So far, I tried (unsuccessfully) to disable obvious ACPI sub-
>>> systems (cpu, mwait, quirks) and debug s
finsplace.de/~sascha/phenom/dmesg-FreeBSD-AthlonII.txt
>
> boot messages from DFly, OpenBSD and Linux:
> https://lair.griffinsplace.de/~sascha/phenom/
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd
On 22/10/2018 17:32, Eugene Grosbein wrote:
> 22.10.2018 21:21, Andriy Gapon wrote:
>> This is just a typical foot-shooting (and a shortcoming of the kernel build
>> system that allows such foot-shooting to happen).
>> I think that there can be other ways in which you can
just a typical foot-shooting (and a shortcoming of the kernel build
system that allows such foot-shooting to happen).
I think that there can be other ways in which you can specify inconsistent
kernel options and/or an incorrect subset of modules in MODULES_OVERRIDE to
create missing dependencies
On 19/10/2018 12:24, Eugene Grosbein wrote:
> On 19.10.2018 13:28, Andriy Gapon wrote:
>
>>> It was brought to my attention that 10.x did not require availability
>>> of krpc for ZFS-on-root system to be bootable but 11.x does.
>>>
>>> That is, major
root-on-zfs requires krpc.
> We could have mentioned that requrement in Release Notes but we had not.
>
> Should we issue an Errata Note?
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/free
ntly (e.g., every time pools are listed).
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 11/06/2018 13:26, Willem Jan Withagen wrote:
> On 11/06/2018 12:13, Andriy Gapon wrote:
>> On 08/06/2018 13:02, Willem Jan Withagen wrote:
>>> My file server is crashing about every 15 minutes at the moment.
>>> The panic looks like:
>>>
>>> Jun
ne+0xe
> Jun 8 11:48:43 zfs kernel: Uptime: 9m7s
>
> Maybe a known bug?
> Is there anything I can do about this?
> Any debugging needed?
Sorry to inform you but your on-disk data got corrupted.
The most straightforward thing you can do is try to save data from the pool in
readonly
chance it
might start working now. Could you please test that as well?
Thanks!
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stab
On 26/04/2018 18:14, Alan Somers wrote:
> On Thu, Apr 26, 2018 at 8:37 AM, Eugene Grosbein <eu...@grosbein.net
> <mailto:eu...@grosbein.net>> wrote:
>
> 26.04.2018 14:50, Andriy Gapon wrote:
>
> > You can try to use zdb -l to find the stale labels.
On 26/04/2018 17:37, Eugene Grosbein wrote:
> 26.04.2018 14:50, Andriy Gapon wrote:
>
>> You can try to use zdb -l to find the stale labels.
>> And then zpool labelclear to clear them.
>
> Our "zpool labelclear" implementation destroys everything (literally).
stumbles upon this and refuses to boot the system
> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227772). The workaround is
> to
> use the 11.1 loader, but I'm afraid this behavior will now be the intended
> one.
You can try to use zdb -l to find the stale labels.
And then
roblem and that
anyone could run?
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 13/03/2018 13:52, Eugene Grosbein wrote:
> On 13.03.2018 17:39, Andriy Gapon wrote:
>> On 13/03/2018 11:37, Eugene Grosbein wrote:
>>> Hi!
>>>
>>> Let's create a stripe and GPT over it using test files as backing store:
>>>
>>> trunc
ced on st0 it's opened for writing and, thus, md0 and md1 are
open for writing too. Afterwards, the write access count is cleared from three
of them and that triggers re-tasting. I guess that g_part code tries to taste
md0 and md1 and sees the GPT label at the start of md0 and the label is
correct
at all (or maybe it is).
> load: 1.98 cmd: python2.7 53438 [usem] 54.70r 14.98u 6.04s 0% 230992k
> make: Working in: /usr/ports/net/samba47
> load: 0.34 cmd: python2.7 53438 [usem] 168.48r 14.98u 6.04s 0% 230992k
> make: Working in: /usr/ports/net/samba47
> load: 0.31 cmd: pyth
ip2 -9
0 28989 86816 0 106 5 183489680 -RN 17 1:27.86
bzip2 -9
0 28990 86816 0 108 5 183489680 -RN 17 1:35.50
bzip2 -9
0 28991 86816 0 106 5 183489680 -RN 17 1:27.00
bzip2 -9
0 28992 86816 0 106 5 1834
as a missing device condition.
-F/-X/-T is not guaranteed to work as the old (freed, overwritten) data is not
kept indefinitely.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscri
e first two try to figure out txg
automatically. But I could be wrong.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ang support yet (like powerpc) one after another in a fraction of time
required to build just amd64.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
o experiment with an "unwind" / "extreme
unwind" import using -F -n / -X -n. Or manually specifying a txg number for
import (in read-only mode).
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listin
be unresponding.
>
> Is it possible to get that simple MFC happen so 11.1-RELEASE be unaffected?
Yes, sure. You can do it.
https://wiki.freebsd.org/Releng/ChangeRequestGuidelines
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://list
to ask
to test a patch.
Looks like you won't be able to help with that. At least, until that some day
:-).
>> On Mar 25, 2017, at 11:02 AM, Andriy Gapon <a...@freebsd.org> wrote:
>>
>>
>> Does anyone [still] use Opteron 6100-series / "Magny-Cours"
Does anyone [still] use Opteron 6100-series / "Magny-Cours" processors with
FreeBSD?
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail t
u told the kernel that you want to mount your root from a ZFS
pool which is on a USB driver which you have already thrown out. Should the
kernel just keep waiting for that pool to appear?
Microsoft provides support for FreeBSD Hyper-V drivers.
Please try to discuss this prob
<===
Root mount waiting for: storvsc <===
...
So, the kernel attempted to mount the root even before vmbus was attached and,
thus, before storvsc appeared and informed the kernel that it might be holding
the root.
How ZFS was supposed to know that vmbus is ever going to appear?
To me this soun
If you currently use aacraid(4) driver and can afford to run a test,
could you please test if you get any regressions after applying the following
patch?
https://reviews.freebsd.org/D9900.diff
Thank you!
--
Andriy Gapon
___
freebsd-stable
On 25/02/2017 16:46, Andriy Gapon wrote:
> On 25/02/2017 15:10, Wolfgang Zenker wrote:
>> Hi,
>>
>> I'm using FreeBSD 11 on a chromebook Acer C720. Because I normally
>> use a mouse I didn't catch the exact time when cyapa and isl stopped
>> wor
: get mode from tunables:
> info: [drm] - kern.vt.fb.modes.DP-1
> info: [drm] - kern.vt.fb.default_mode
> fbd0 on drmn0
> VT: Replacing driver "vga" with new "fb".
> info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0
> wlan0: Ethernet addres
cc and then use CROSS_TOOLCHAIN=amd64-gcc
command line argument for buildkernel
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "fre
On 23/08/2016 11:43, Andriy Gapon wrote:
>
> Please review and test a change to .zfs code that is intended to make the code
> aligned with FreeBSD VFS and, as such, more stable:
> https://reviews.freebsd.org/D7421
>
> The change removes two features.
> .zfs/shares is gone
don't know how to make gzguts.h. Stop
>
> make[5]: stopped in /usr/src/sys/boot/libstand32
gzguts.h in libstand32?
That does not seem to be related to any of the commits listed at the beginning.
--
Andriy Gapon
___
freebsd-stable@freebs
../../dev/firewire/fwohci.c:1878:9:
> error: use of undeclared identifier 'prequpper'
> (prequpper & 0x)) {
Sorry about this, should be fixed by r310081.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from bhyve...Reading symbols from
/usr/lib/debug//usr/sbin/bhyve.debug...done.
Something is wrong in your environment.
--
Andriy Gapon
On 14/11/2016 14:00, Henri Hennebert wrote:
> On 11/14/2016 12:45, Andriy Gapon wrote:
>> Okay. Luckily for us, it seems that 'm' is available in frame 5. It also
>> happens to be the first field of 'struct faultstate'. So, could you please
>> go
>> to frame a
On 14/11/2016 11:35, Henri Hennebert wrote:
>
>
> On 11/14/2016 10:07, Andriy Gapon wrote:
>> Hmm, I've just noticed another interesting thread:
>> Thread 668 (Thread 101245):
>> #0 sched_switch (td=0xf800b642aa00, newtd=0xf8000285f000,
>> flags=>
On 13/11/2016 15:28, Henri Hennebert wrote:
> On 11/13/2016 11:06, Andriy Gapon wrote:
>> On 12/11/2016 14:40, Henri Hennebert wrote:
>>> I attatch it
>>
>> Thank you!
>> So, these two threads are trying to get the lock in the exclusive mode:
>> Thread 68
d be nice to get a file
path and a directory vnode where the lookup is called.
Thank you.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to &
On 11/11/2016 16:50, Henri Hennebert wrote:
>
>
> On 11/11/2016 12:24, Andriy Gapon wrote:
>>
>> At this stage I would try to get a system crash dump for post-mortem
>> analysis.
>> There are a few way to do that. You can enter ddb and then run 'dump' and
>
On 10/11/2016 21:41, Henri Hennebert wrote:
> On 11/10/2016 19:40, Andriy Gapon wrote:
>> On 10/11/2016 19:55, Henri Hennebert wrote:
>>>
>>>
>>> On 11/10/2016 18:33, Andriy Gapon wrote:
>>>> On 10/11/2016 18:12, Henri Hennebert wrote:
>>>&g
On 10/11/2016 19:55, Henri Hennebert wrote:
>
>
> On 11/10/2016 18:33, Andriy Gapon wrote:
>> On 10/11/2016 18:12, Henri Hennebert wrote:
>>> On 11/10/2016 16:54, Andriy Gapon wrote:
>>>> On 10/11/2016 17:20, Henri Hennebert wrote:
>>&
On 10/11/2016 18:12, Henri Hennebert wrote:
> On 11/10/2016 16:54, Andriy Gapon wrote:
>> On 10/11/2016 17:20, Henri Hennebert wrote:
>>> On 11/10/2016 15:00, Andriy Gapon wrote:
>>>> Interesting. I can not spot any suspicious thread that would hold the
>>&
On 10/11/2016 17:20, Henri Hennebert wrote:
> On 11/10/2016 15:00, Andriy Gapon wrote:
>> Interesting. I can not spot any suspicious thread that would hold the vnode
>> lock. Could you please run kgdb (just like that, no arguments), then execute
>> 'bt' command and the
On 10/11/2016 12:30, Henri Hennebert wrote:
> On 11/10/2016 11:21, Andriy Gapon wrote:
>> On 09/11/2016 15:58, Eric van Gyzen wrote:
>>> On 11/09/2016 07:48, Henri Hennebert wrote:
>>>> I encounter a strange deadlock on
>>>>
>>>> FreeBSD avori
lock, but someone who _can_ help will probably ask
> for
> the output of "procstat -kk PID" with the PID of the "find" process.
In fact, it's procstat -kk -a. With just one thread we would see that a thread
is blocked on something, but we won't see why that something can not be
acquired.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ho 'abcdABCD' | sed 's/[A-Z]/X/g’
> abcd
>
> FreeBSD 10-stable
> $ echo 'abcdABCD' | sed 's/[A-Z]/X/g'
> abcd
Latest Gentoo:
$ echo 'abcdABCD' | sed 's/[A-Z]/X/g'
aXXX
Recent OpenIndiana (an illumos based OS):
$ echo 'abcdABCD' | se
Instead of the guesswork and black magic, you could try to use tools to analyze
the problem. E.g., determine if the delay is because a CPU does a lot of work
or it is because of waiting. Find the bottleneck, etc.
pmcstat, dtrace are your friends :-)
--
Andriy Gapon
On 18/10/2016 00:43, Steven Hartland wrote:
> On 17/10/2016 20:52, Andriy Gapon wrote:
>> On 17/10/2016 21:54, Steven Hartland wrote:
>>> You're hitting stack exhaustion, have you tried increasing the kernel stack
>>> pages?
>>> It can be changed from /boot/
opensolaris/uts/common/fs/zfs/zio.c:3112
>> #173 0x822bbefd in zio_execute (zio=)
>> at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1651
>> #174 0x822a216d in vdev_queue_io_done (zio=)
>> at
>> /usr/src/sys/cddl/contrib/opensolaris/uts/c
On 14/10/2016 21:49, Torfinn Ingolfsen wrote:
> On Tue, 11 Oct 2016 14:29:34 +0300
> Andriy Gapon <a...@freebsd.org> wrote:
>
>> On 06/10/2016 00:37, Andriy Gapon wrote:
>>> On 05/10/2016 23:28, Torfinn Ingolfsen wrote:
>>>> #6 0x80cd0081 in
848), MFC-ed even later.
Apparently no one else who uses 32-bit systems and has L2ARC configured had a
chance to run into the bug.
Thank you very much for discovering and analyzing the bug and providing a fix
for it!
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 13/10/2016 07:04, Aryeh Friedman wrote:
> Please check dmesg(8)
> for more details.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to &q
On 06/10/2016 00:37, Andriy Gapon wrote:
> On 05/10/2016 23:28, Torfinn Ingolfsen wrote:
>> #6 0x80cd0081 in calltrap ()
>> at /usr/src/sys/amd64/amd64/exception.S:238
>> #7 0x81bcb078 in aibs_add_sensor () from /boot/kernel/aibs.ko
>
h, I've just spotted a very silly typo.
Could you please replace '0' with 'o' in
err = aibs_add_sensor(sc, 0, [i], );
?
I wish compilers were more noisy about passing a scalar as a pointer argument.
Thanks!
--
Andriy Gapon
___
freebsd-stable
On 05/10/2016 23:28, Torfinn Ingolfsen wrote:
> On Wed, 5 Oct 2016 16:09:40 +0300
> Andriy Gapon <a...@freebsd.org> wrote:
>
>>
>> Seems like this is a clang vs gcc issue as I didn't get warnings here.
>> Could you please simply add initialization to those
On 05/10/2016 23:28, Torfinn Ingolfsen wrote:
> Unfortunately, my machines panics as soon as this module is loaded:
Not good...
> (kgdb) #0 doadump (textdump=) at pcpu.h:235
> #1 0x80900b06 in kern_reboot (howto=260)
> at /usr/src/sys/kern/kern_shutdown.c:454
> #2
Does anyone use iicsmb driver for any practical purposes?
Or more broadly, does anyone have a system with an I2C controller behind which
SMBus-compatible slaves are known to exist?
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https
On 05/10/2016 15:37, Torfinn Ingolfsen wrote:
> On Mon, 3 Oct 2016 23:05:48 +0300
> Andriy Gapon <a...@freebsd.org> wrote:
>
>> Yes, it does. Thank you!
>> It seems like a couple of minor changes are not in the source tree that you
>> are
>> using. O
46
Thanks!
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
the other is a different
rounding of 0C in Kelvins.
I've generated a patch that should apply to your tree:
https://people.freebsd.org/~avg/aibs-ggrp-gitm.93.diff
Please try.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.or
-C option? :-)
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
duce any result, then there is no chance of the driver working.
Otherwise I would be interested in a full acpidump -dt output.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any m
On 30/09/2016 15:57, Torfinn Ingolfsen wrote:
> On Fri, 30 Sep 2016 14:30:02 +0300
> Andriy Gapon <a...@freebsd.org> wrote:
>
>> Testing the patch should be as easy as building, installing and loading aibs
>> module (found in sys/modules/acpi/aibs). Well,
es/acpi/aibs). Well, also don't forget to apply the
patch with patch -p1 :-)
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
u for your persistence and testing.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 14/09/2016 15:49, Slawa Olhovchenkov wrote:
> MSR_APICBASE = 0xfee00d00
> x2APIC is prohibited but turned on by BIOS
Kostik, ^
P.S. the format string for the value should have been 0x%016jx.
--
Andriy Gapon
___
freebsd-
On 14/09/2016 15:33, Slawa Olhovchenkov wrote:
> On Wed, Sep 14, 2016 at 03:22:17PM +0300, Andriy Gapon wrote:
>
>> On 14/09/2016 14:36, Konstantin Belousov wrote:
>>> On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote:
>>>> On 13/09/2016 18:22, Kon
On 13/09/2016 17:59, Slawa Olhovchenkov wrote:
> Goggling on X2APIC_OPT_OUT take same result: other OS in this case
> downgrade to xAPIC mode.
It still does not make any sense for BIOS to turn on x2APIC and then instruct
the OS that x2APIC must not be used.
--
Andriy
On 14/09/2016 14:36, Konstantin Belousov wrote:
> On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote:
>> On 13/09/2016 18:22, Konstantin Belousov wrote:
>>> Any access
>>> to the LAPIC registers page in x2APIC mode faults.
>>
>>
memory. That can be different for Intel processors, of course.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
y is that in both cases, hw.x2apic_enable=0 and X2APIC_OPT_OUT is on,
the BIOS turns on x2APIC mode and transitions to OS in that mode.
In the case when X2APIC_OPT_OUT is on it's clearly a BIOS bug.
But maybe we could do a little bit better in both cases. At the very least we
could detect the s
On 13/09/2016 15:42, Slawa Olhovchenkov wrote:
> On Tue, Sep 13, 2016 at 03:38:17PM +0300, Andriy Gapon wrote:
>
>> On 13/09/2016 15:11, Slawa Olhovchenkov wrote:
>>> On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote:
>>>
>>>> On
On 13/09/2016 15:11, Slawa Olhovchenkov wrote:
> On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote:
>
>> On 12/09/2016 20:53, Slawa Olhovchenkov wrote:
>>> boot_cpu_id = 255
>>
>> I think that this points towards the BIOS not configuring the BSP L
you disable X2APIC_OPT_OUT and set
hw.x2apic_enable=0 in loader.conf or at the loader prompt.
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebs
cpu_id == -1) {
boot_cpu_id = PCPU_GET(apic_id);
cpu_info[boot_cpu_id].cpu_bsp = 1;
} else
right after boot_cpu_id = PCPU_GET(apic_id) line please insert
printf("boot_cpu_id = %d\n", boot_cpu_id);
On 12/09/2016 12:39, Slawa Olhovchenkov wrote:
> On Sun, Sep 04, 2016 at 08:14:07PM +0300, Andriy Gapon wrote:
>
>> On 04/09/2016 19:29, Konstantin Belousov wrote:
>>> This is possible, of course. But it would not affect "SMP: Added CPU ..."
>>> lines.
1 - 100 of 947 matches
Mail list logo
