On 17/03/2018 18:51, Mark Millard wrote:
> I'll note that top was a -w that reports:
>
>-w Display approximate swap usage for each process.
As far as I can tell, this option is quite broken.
The "approximate swap usage" it reports is nowhere like it
(54, FreeBSD ELF64, sys_ioctl), rip = 0x80049afda, rsp =
>> 0x7fffbd18, rbp = 0x7fffbd90 ---
>> KDB: enter: panic
>> [ thread pid 56 tid 100606 ]
>> Stopped at kdb_enter+0x3b: movq$0,kdb_why
>> db>
>
> It seems like a race as I can get it to boo
something I should be doing to help debug these?
IMO, no. Please ignore LORs involving "bufwait", "filedesc structure", "syncer"
unless you experience any real problem (like a lock up).
--
Andriy Gapon
___
freebsd-current
On 18/02/2018 22:33, Gleb Smirnoff wrote:
> On Sun, Feb 18, 2018 at 10:15:24PM +0200, Andriy Gapon wrote:
> A> On 18/02/2018 15:26, Gleb Smirnoff wrote:
> A> > My only point is that it is a performance improvement. IMHO that's
> enough :)
> A>
> A> I don't think
ementations confirm to it.
--
Andriy Gapon
___
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"
On 18/02/2018 04:35, Gleb Smirnoff wrote:
> Andriy,
>
> On Sun, Feb 18, 2018 at 12:54:21AM +0200, Andriy Gapon wrote:
> A> > Today's rebuild has given me uptimes of below an hour, usually. The box
> will stay up in single user mode long enough to rebuild world/kern
made aware of bogus_page. Or, at least, that
they should not verify that the requested pages are busied.
--
Andriy Gapon
___
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"
essage and the backtrace would be a good start, but a crash dump is
probably what's really needed to analyze the issue.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, sen
On 04/02/2018 11:50, Maurizio Vairani wrote:
> I have added a socket in the ifioctl() call as in the
> /usr/src/sys/nfs/bootp_subr.c source.
> Please let me know if you prefer a patch.
A patch here https://reviews.freebsd.org/ would be the best.
--
And
[cc-ing current@ to raise more awareness]
On 05/12/2017 16:03, Alexey Dokuchaev wrote:
> On Fri, Nov 24, 2017 at 11:31:51AM +0200, Andriy Gapon wrote:
>>
>> I have reported a couple of nvidia-driver issues in the FreeBSD section
>> of the nVidia developer forum, but no repli
are produced if there is a problem while writing a core file.
So, they can appear only if (after) a process crashed.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, s
On 21/11/2017 14:48, Thomas Laus wrote:
> I had boot success when copying gptzfsboot file from my laptop that is
> running r325474. The problem CURRENT version running on my desktop is
> r326012.
Thomas,
could you please compare sizes of the files before going further?
--
And
On 13/11/2017 17:02, Ed Maste wrote:
> On 7 November 2017 at 13:12, Andriy Gapon <a...@freebsd.org> wrote:
>>
>> I hope that lld is not that widely used now.
>> But I admit that I put the cart before the horse.
>> I didn't expect that posix_fallocate is used in th
On 06/11/2017 19:26, Ian Lepore wrote:
> On Mon, 2017-11-06 at 17:40 +0200, Andriy Gapon wrote:
>> From UPDATING:
>> The naive and non-compliant support of posix_fallocate(2) in ZFS
>> has been removed as of r325320. The system call now returns EINVAL
>> when used on a
volved, of course).
One example is the arm64 build (typically a cross build from amd64).
The lld issue is fixed in head as of r325420. But other branches are still
affected (if you are building them on a head kernel).
Other posix_fallocate consumers could be affected too.
--
Andriy
On 04/11/2017 13:58, Ed Maste wrote:
> I have no idea how they decided EINVAL was a reasonable errno for this case.
I completely agree. That's a weird choice that I have not seen for any other
API.
--
Andriy Gapon
___
freebsd-current@freebsd.
On 04/11/2017 13:41, Andriy Gapon wrote:
> On 04/11/2017 12:32, Mark Millard wrote:
>> if (int Err = ::posix_fallocate(FD, 0, Size)) {
>> if (Err != EOPNOTSUPP)
>> return std::error_code(Err, std::generic_category());
>> }
>
> The commit message
six_fallocate.html
--
Andriy Gapon
___
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"
On 01/11/2017 10:12, Andriy Gapon wrote:
> On 01/11/2017 09:33, O. Hartmann wrote:
>> I have the same (or similar) probleme here on two boxes now, maybe more to
>> come
>> as I start updating CURRENT cyclic.
>>
>> Reverting r325227 solves to problem for now.
&
ing soon.
Sorry for the trouble and thanks for the report.
--
Andriy Gapon
___
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"
On 31/10/2017 14:32, David Wolfskill wrote:
> Andriy, I "cloned" the slice before doing the above, so I can poke
> at this a bit more (e.g., try to get a crash dump), if that would
> still be useful.
Yes, it would be, as I currently do not see what the problem with r325227 is
On 31/10/2017 13:37, David Wolfskill wrote:
> Any suggestions for diagnosing or fixing it?
Try setting a dump device via loader.conf (e.g. dumpdev="ada0p99") and obtaining
a crash dump.
--
Andriy Gapon
___
freebsd-current@freebsd.org
https://reviews.freebsd.org/D12420
Who would be the best people to review this change?
Where are they lurking?
Please point me towards them or add yourself as a reviewer if you are one of
them :)
Thanks!
--
Andriy Gapon
___
freebsd-current@freebsd.org
odule load
handler.
He also offered an idea for a possible solution: holding the modules lock in the
shared mode (MOD_SLOCK) around calls to sysctl-s registered from modules.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.
of how the code works correct?
Can the order of linker_file_sysinit and linker_file_register_sysctls be changed
without a great risk?
Thank you!
P.S.
The same applies to:
linker_file_sysuninit(file);
linker_file_unregister_sysctls(file);
--
Andriy Gapon
On 02/08/2017 04:00, Ngie Cooper (yaneurabeya) wrote:
>
>> On Aug 1, 2017, at 09:21, John Baldwin <j...@freebsd.org> wrote:
>>
>> On Tuesday, August 01, 2017 09:47:41 AM Andriy Gapon wrote:
>>> On 01/08/2017 02:31, Ngie Cooper wrote:
>>>> Hi,
&g
On 01/08/2017 19:21, John Baldwin wrote:
> On Tuesday, August 01, 2017 09:47:41 AM Andriy Gapon wrote:
>> On 01/08/2017 02:31, Ngie Cooper wrote:
>>> Hi,
>>> I tried upgrading my host from 11.1-STABLE to 12.0-CURRENT, and it
>>> didn’t work because
ource files via
.include "${SUNW}/uts/common/Makefile.files"
Perhaps something to do with "inline"...
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
gt; around). This is always advisable when running HEAD anyway, particularly so
> now. For us, a kernel.old from June 18th worked fine.
>
My apologies for the bug.
Everyone affected, could you please test the patch from the bug report?
https://bugs.freebs
On 27/06/2017 17:16, Shawn Webb wrote:
> On Tue, Jun 27, 2017 at 05:12:01PM +0300, Andriy Gapon wrote:
>> On 26/06/2017 03:31, Shawn Webb wrote:
>>> This is on the latest HardenedBSD 12-CURRENT on one of my servers:
>>>
>>> [141] panic: sleepq_add: td
fork_exit+0x84/frame 0xfe2fcbf0
> [141] fork_trampoline() at fork_trampoline+0xe/frame 0xfe2fcbf0
Seems like another architectural incompatibility between illumos and FreeBSD.
Are you able to reproduce the crash more or less reliably?
--
Andriy Gapon
e_run_locked+0x127/frame 0xfe01b0231b80
>>> taskqueue_thread_loop() at 0x806d4ee8 =
>>> taskqueue_thread_loop+0xc8/frame 0xfe01b0231bb0
>>> fork_exit() at 0x80640df5 = fork_exit+0x85/frame 0xfe01b0231bf0
>>> fork_tr
On 15/06/2017 11:16, Ngie Cooper wrote:
> On Thu, Jun 15, 2017 at 12:44 AM, Andriy Gapon <a...@freebsd.org> wrote:
>>
>> It seems that hwpmc does not support newer Xeon processors:
>> pmc: Unknown Intel CPU.
>
> What FreeBSD version is this?
Head as of
ould appreciate any help, patches, suggestions, documentation links, etc.
Thank you.
--
Andriy Gapon
___
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"
kernel?
Ideally, I would like to see the trace with KTR_SCHED | KTR_RUNQ compiled into
the kernel via KTR_COMPILE and then enabled at the run time via
debug.ktr.mask=0x2040.
Thank you.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https:/
chance?
--
Andriy Gapon
___
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"
On 16/05/2017 16:49, Kristof Provost wrote:
> On 16 May 2017, at 15:41, Andriy Gapon wrote:
>> On 10/05/2017 12:37, Kristof Provost wrote:
>>> I have a reproducible panic on CURRENT (r318136) doing
>>> (jupiter) # zfs send -R -v zroot/var@before-kernel-2017-04-26 | nc d
4 in fork_exit (callout=0x822bf150
> , arg=0xfe0120a1d168, frame=0xfe0120cadbc0) at
> /usr/src/sys/kern/kern_fork.c:1038
> #16 0x80eb682e in fork_trampoline () at
> /usr/src/sys/amd64/amd64/exception.S:611
> #17 0x in ?? ()
>
> Let me kn
hat the gang blocks
are typically created when a pool is very fragmented.
> I will hammer the box with and report back first of the week whether the panic
> re-occurs or not.
Please also try removing those old files again too.
Running zpool
0xf80009350f00, frame=0xfe086140ec00)
> at /usr/src/sys/kern/kern_fork.c:1038
> #20 0x80eb5a1e in fork_trampoline ()
> at /usr/src/sys/amd64/amd64/exception.S:611
> #21 0x in ?? ()
> Current language: auto; currently minimal
> (kgdb)
> ___
> 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"
>
--
Andriy Gapon
___
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"
On 30/03/2017 14:23, Andriy Gapon wrote:
> On 30/03/2017 12:34, Andrey Chernov wrote:
>> On 30.03.2017 12:23, Andrey Chernov wrote:
>>> Yes, only for reboot/shutdown. The system does not do anythings wrong
>>> even under high load. On reboot or hang those lines are ne
ut previously the system rebooted because of a printf that
caused a LOR (between spinlocks, AFAIR), witness tried to report it... using
printf, and that recursed and there was a triple fault in the end.
Let me try to dig some details, maybe the current issue is related in some ways.
By chan
On 27/03/2017 15:06, Piotr Kubaj wrote:
> Does it have to be specifically 61xx series? I have a server running 2
> 6262HE's.
>
Yes. I have the info that I need for 62xx Opterons.
Thanks.
--
Andriy Gapon
___
freebsd-current@freebsd.org mai
On 03/27/2017 14:35, Rainer Hurling wrote:
> Am 27.03.2017 um 10:31 schrieb Andriy Gapon:
>> On 03/26/2017 00:21, Manfred Antar wrote:
>>> Recent change to genassym.c breaks building a current kernel:
>>>
>>> -
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"
..
> text data bssdechex filename
> 8657083 805570 3350664 12813317 0xc38405 kernel.full
> --- kernel.debug ---
> objcopy --only-keep-debug kernel.full kernel.debug
> --- kernel ---
> objcopy --strip-debug --add-gnu-debuglink=kernel.debug k
Does anyone [still] use Opteron 6100-series / "Magny-Cours" processors with
FreeBSD?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail t
Any thoughts?
Were messages replaced by the second '[..]' really so useless?
--
Andriy Gapon
___
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"
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-current
as ACPI ID 2
>> APIC: CPU 3 has ACPI ID 3
>> APIC: CPU 4 has ACPI ID 4
>> APIC: CPU 5 has ACPI ID 5
>> APIC: CPU 6 has ACPI ID 6
>> APIC: CPU 7 has ACPI ID 7
>> lapic0: MCE Thresholding ELVT unmasked
>> kernel trap 12 with interrupts disabled
>>
>>
>> Fatal trap 12: page fault while in kernel mode
>> cpuid = 0; apic id = 00
>> fault virtual address = 0x0
>> fault code = supervisor write data, page not present
>> instruction pointer = 0x20:0x809b36ed
>> stack pointer = 0x28:0x8130baa0
>> frame pointer = 0x28:0x8130bad0
>> code segment= base 0x0, limit 0xf, type 0x1b
>> = DPL 0, pres 1, long 1, def32 0, gran 1
>> processor eflags= resume, IOPL = 0
>> current process = 0 ()
>> [ thread pid 0 tid 0 ]
>> Stopped at _mca_init+0x55d:movl$0x1,(%rax,%rcx,1)
>> db> bt
>> Tracing pid 0 tid 0 td 0x810a9dc0
>> _mca_init() at _mca_init+0x55d/frame 0x8130bad0
>> mi_startup() at mi_startup+0x9c/frame 0x8130baf0
>> btext() at btext+0x2c
>> db>
--
Andriy Gapon
___
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"
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
quot; which could be contested. In that case the thread spins
waiting for the lock to be released. This is reported as "spinning" and then
"running" states.
I would like to fix that, but not sure how to do that best.
One idea is to move the mi_switch() t
(atkbdc + ums).
I have also installed xf86-input-evdev.
Do I need any additional kernel evedev configuration via sysctl?
What should I add to xorg configuration to enable evdev for X?
Thank you!
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing
yscallenter (td=0xf80055de6000,
> sa=)
> at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:135
> #13 amd64_syscall (td=0xf80055de6000, traced=0)
> at /usr/src/sys/amd64/amd64/trap.c:902
> #14
> Can't read data for section '.eh_frame' in file '/'
>
On 14/11/2016 11:58, Gary Jennejohn wrote:
> On Sun, 13 Nov 2016 23:56:09 +0200
> Andriy Gapon <a...@freebsd.org> wrote:
>
>> On 11/11/2016 14:25, Andriy Gapon wrote:
>>> panic: mutex sbp not owned at /usr/src/sys/dev/firewire/sbp.c:967
>>> cpuid = 2
>
On 11/11/2016 14:25, Andriy Gapon wrote:
> panic: mutex sbp not owned at /usr/src/sys/dev/firewire/sbp.c:967
> cpuid = 2
> curthread: 0xf8000ada5000
> stack: 0xfe0504ded000 - 0xfe0504df1000
> stack pointer: 0xfe0504df0a00
> KDB: stack backtrace:
>
bus manager 0
> Nov 12 10:25:00 ernst kernel: da0 at sbp0 bus 0 scbus6 target 0 lun 0
> Nov 12 10:25:00 ernst kernel: da0: detached
> Nov 12 10:25:00 ernst kernel: (da0:sbp0:0:0:0): Periph destroyed
Is this with INVARIANTS ?
--
Andriy Gapon
__
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
--
Andriy Gapon
___
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"
e appropriate time.
Anyone interested in the issue, could you please take a look at this review?
https://reviews.freebsd.org/D8430
Thank you.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/fre
("[pmc,%d] pm %p != pp_pmcs[%d] %p", __LINE__,
pm, ri, pp->pp_pmcs[ri].pp_pmc));
--
Andriy Gapon
___
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"
On 28/10/2016 16:01, Andriy Gapon wrote:
> I suspect that under the right conditions it's possible for wrmsr to cause a
> counter overflow, such that an interrupt (if enabled) is generated after wrmsr
> is executed, even if wrmsr disables the counter.
>
> In amd_intr() we
On 27/10/2016 16:20, Andriy Gapon wrote:
>
> I observe a problem on a relatively recent, but not the latest, head.
> r306752 amd64 on AMD hardware.
> If I run
> pmcstat -T -P instructions -t $pid
> with a pid of a busy userland process, then I shortly get a (stray) NMI.
, me-toos?
Thank you!
--
Andriy Gapon
___
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"
ignored the
development and for that I can only blame myself.
> [1]https://lists.freebsd.org/pipermail/freebsd-arch/2015-March/016972.html
> [2]https://lists.freebsd.org/pipermail/freebsd-arch/2015-May/017157.html
I also agree that having a thin library on top of the ioctl would be a
select are:
- revert SMB_MAXBLOCKSIZE to 32
- remove SMB_TRANS as it does not map to anything defined by the SMBus
specification and it can not be implemented for most, if not all,
SMBus controllers
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing lis
JFYI. I bumped __FreeBSD_version to 1200013 to mark this change.
Forwarded Message
Subject: svn commit: r307131 - head/include
Date: Wed, 12 Oct 2016 07:08:32 + (UTC)
From: Andriy Gapon <a...@freebsd.org>
To: src-committ...@freebsd.org, svn-src-...@freebsd.org,
svn
On 12/10/2016 09:21, Andriy Gapon wrote:
> On 12/10/2016 07:03, Warner Losh wrote:
>> I think I can do the device table mechanism if Andriy isn't up for it.
>
> That would be great, thank you!
>
Meanwhile, I've added a "stop-gap" version of 'chromebook_
On 12/10/2016 07:03, Warner Losh wrote:
> I think I can do the device table mechanism if Andriy isn't up for it.
That would be great, thank you!
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listi
rce
of confusion) for Matt when he added smbus_trans().
Right now I do not have any good suggestion on how to expose that 90% SMBus, 10%
I2C functionality in the FreeBSD model.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lis
t; wrote:
>> On Mon, 10 Oct 2016 14:35:22 +0300
>> Andriy Gapon <a...@freebsd.org> wrote:
>>
>>> On 09/10/2016 23:22, Warner Losh wrote:
>>>> There seems to be enough information present in the smbios data to
>>>> know what devices are at
es and adds isl
and cyapa devices to a bus if some criteria are met.
--
Andriy Gapon
___
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"
JFYI,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213334
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-uns
On 09/10/2016 09:36, Matthias Apitz wrote:
> El día Saturday, October 08, 2016 a las 10:17:07PM +0300, Andriy Gapon
> escribió:
>
>> On 08/10/2016 21:07, Matthias Apitz wrote:
>>> I have now produced a memstick with (unpatched) r306769 of October 6. It
>>&g
ything newer? And will test/report.
v4 is the latest. Thanks!
--
Andriy Gapon
___
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"
On 06/10/2016 11:10, Michael Gmelin wrote:
>
>
>> On 06 Oct 2016, at 09:48, Andriy Gapon <a...@freebsd.org> wrote:
>>
>>> On 06/10/2016 08:37, Andriy Gapon wrote:
>>> The more testing the better!
>>
>> Based on Michael's results I've uploaded
On 06/10/2016 08:37, Andriy Gapon wrote:
> The more testing the better!
Based on Michael's results I've uploaded a new version:
https://people.freebsd.org/~avg/ig4-i2c.v4.diff
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
ht
On 06/10/2016 10:25, Andriy Gapon wrote:
> On 06/10/2016 10:08, Michael Gmelin wrote:
>>
>>
>>> On 05 Oct 2016, at 15:01, Andriy Gapon <a...@freebsd.org> wrote:
>>>
>>>> On 05/10/2016 14:19, Michael Gmelin wrote:
>>>>
>>>&g
On 06/10/2016 10:08, Michael Gmelin wrote:
>
>
>> On 05 Oct 2016, at 15:01, Andriy Gapon <a...@freebsd.org> wrote:
>>
>>> On 05/10/2016 14:19, Michael Gmelin wrote:
>>>
>>> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_p
On 06/10/2016 07:47, Matthias Apitz wrote:
> El día Wednesday, October 05, 2016 a las 04:01:25PM +0300, Andriy Gapon
> escribió:
>
>> On 05/10/2016 14:19, Michael Gmelin wrote:
>>>
>>> ig4iic_start is called, but iicbus_hinted_child, isl_probe, i
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-current@freebsd.org mailing list
https
/~avg/ig4-i2c.v3.diff
It contains a fix and some cosmetic changes on top of the previous patch.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
if gets called.
Thank you!
--
Andriy Gapon
___
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"
se double-check that device.hints contains the necessary hints?
Could you also set debug.bootverbose=1 before kldload ig4 and kldload isl and
show me any new log messages that appear after doing kldload?
--
Andriy Gapon
___
freebsd-current@freebsd.org mai
46
Thanks!
--
Andriy Gapon
___
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"
On 03/10/2016 23:25, Michael Gmelin wrote:
> On Mon, 3 Oct 2016 19:41:17 +0300
> Andriy Gapon <a...@freebsd.org> wrote:
>
>> On 03/10/2016 19:07, Michael Gmelin wrote:
>>> I upgraded the latter the r306641, applied your patches (cleanly)
>>> and ra
sily fixed by removing "#include " from
> isl.c (line 56).
Thank you for reporting this!
Looks like I overlooked this because I didn't do make clean after removing
vnode_if.h from the Makefile.
Will fix this too.
--
Andriy Gapon
___
fre
hat ig4 driver is changed, so it too has to be rebuilt if you
are going to build individual modules rather than do a kernel + modules build.
I will appreciate your testing and feedback.
Thank you!
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
ht
es/acpi/aibs). Well, also don't forget to apply the
patch with patch -p1 :-)
--
Andriy Gapon
___
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"
On 28/09/2016 21:08, Andrey V. Elsukov wrote:
> This is very strange problem, how did you created MBR if you have not
> destroyed GPT? :)
Using a tool that's not aware of GPT at all?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
arm-cortexa5-processor-for-trustzone-capabilities
Linux has a driver for it:
http://www.phoronix.com/scan.php?px=MTU4MTM=news_item
http://cateee.net/lkddb/web-lkddb/CRYPTO_DEV_CCP.html
--
Andriy Gapon
___
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"
_MODULE_ORDERED(xl, pci, xl_driver, xl_devclass, NULL, NULL,
> SI_ORDER_ANY);
> DRIVER_MODULE(miibus, xl, miibus_driver, miibus_devclass, NULL, NULL);
>
> DRIVER_MODULE() uses SI_ORDER_MIDDLE by default.
>
> This probably needs to be fixed in all of the smbus controller
ake
it more robust.
--
Andriy Gapon
___
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"
nlinked from a directory
specified by the attribute.
So, at the moment I do not have any good ideas on how to make this work.
Maybe trying to use the parent attribute and failing when it's inconsistent
would be good enough...
--
Andriy Gapon
___
fre
On 04/09/2016 11:24, Andriy Gapon wrote:
> On 27/08/2016 22:09, Frederic Chardon wrote:
>>> Anybody is able to reproduce this behavior or is it a local problem?
>> Reverting 303970 solves this issue. gcore and adb works again, and I
>> can start the vboxnet service.
>
to be sure.
I can not reproduce this issue here.
Unfortunately, I have no clue how kern.proc.pathname works, so I would
appreciate any hints at what filesystem operations I should look for potential
problems.
--
Andriy Gapon
___
freebsd-current@freebsd.o
were already missing on FreeBSD, and properly implementing
the feature required some more work.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On 19/08/2016 14:06, Alexander Motin wrote:
> On 19.08.16 11:30, Andriy Gapon wrote:
>> So, what's suspicious here is that we discover two AHCI channels on the
>> JMicron
>> device and we seem to discover some sort of a device on one of them. But the
>> communication
ked at some nearby device entries,
and - is it as simple as adding AHCI_Q_1CH quick for this device?
--
Andriy Gapon
___
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"
that does switching should be prepared to work in the rather
restrictive context. Which the kms code is not.
P.S. It seems that the latest version of drm_fb_helper.c in Linux is quite
different from what we have.
--
Andriy Gapon
___
freebsd-current
On 28/07/2016 13:34, Andriy Gapon wrote:
> Locally I have the following rc script to handle subordinate datasets of
> a boot environment: http://dpaste.com/0Q0JPGN.txt
> It is designed for exactly the scenario described above.
> The script is automatically enabled when zfs_enabl
201 - 300 of 1235 matches
Mail list logo
