In message <20180622052755.ga49...@x2.osted.lan>, Peter Holm writes:
> On Thu, Jun 21, 2018 at 06:42:41PM -0700, Matthew Macy wrote:
> > I made changes this morning / early afternoon.
> > -M
> >
>
> With r335501 I no longer see any of the issues I reported. Thank
> you for the fix!
>
> - Peter
I
On Thu, Jun 21, 2018 at 06:42:41PM -0700, Matthew Macy wrote:
> I made changes this morning / early afternoon.
> -M
>
With r335501 I no longer see any of the issues I reported. Thank
you for the fix!
- Peter
> On Thu, Jun 21, 2018 at 6:41 PM, Cy Schubert
> wrote:
> > Like as of now?
> >
> >
Hi,
check if you have 'options IXL_IW' in your kernel conf. It's removed from
GENERIC. I had the same problem here with my customized conf.
On Thu, Jun 21, 2018 at 11:43 PM, Pete Wright wrote:
> howdy - just ran into an issue with building a kernel that has EVDEV
> enabled causing this error:
howdy - just ran into an issue with building a kernel that has EVDEV
enabled causing this error:
--- kernel.full ---
linking kernel.full
ld: error: undefined symbol: ixl_iw_pf_init
>>> referenced by if_ixl.c:900
(/usr/home/pete/git/freebsd/sys/dev/ixl/if_ixl.c:900)
>>>
I saw them go by on my phone, thinking they might fix it.
Building now.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
In message
, Matthew Macy writes:
> I made changes this morning / early afternoon.
>
I made changes this morning / early afternoon.
-M
On Thu, Jun 21, 2018 at 6:41 PM, Cy Schubert wrote:
> Like as of now?
>
> The last panic occurred this morning after a build last night.
>
>
> --
> Cheers,
> Cy Schubert
> FreeBSD UNIX: Web: http://www.FreeBSD.org
>
> The need of
Like as of now?
The last panic occurred this morning after a build last night.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
In message
, Matthew Macy writes:
> Try updating. It should be fixed.
>
> On
Try updating. It should be fixed.
On Thu, Jun 21, 2018 at 6:14 PM, Cy Schubert wrote:
> In message <20180620090957.ga...@x2.osted.lan>, Peter Holm writes:
>> 20180620 10:32:47 all (1/1): udp.sh
>> Kernel page fault with the following non-sleepable locks held:
>> shared rw udpinp (udpinp) r = 0
In message <20180620090957.ga...@x2.osted.lan>, Peter Holm writes:
> 20180620 10:32:47 all (1/1): udp.sh
> Kernel page fault with the following non-sleepable locks held:
> shared rw udpinp (udpinp) r = 0 (0xf80bbc808d78) locked @ netinet/in_pcb.
> c:2398
> stack backtrace:
> #0
On 2018-Jun-19, at 9:14 PM, Li-Wen Hsu wrote:
> On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote:
>>
>> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
>>
>>> On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
Li-Wen reported that the build is done in a 11.1-rel jail though, so
the
On 21 June 2018 at 09:09, Ed Maste wrote:
>
> We'll also need a man page.
I took a quick look at this, and in doing so found that the output
from "llvm-objdump --help" appears to be missing a large number of
single-letter options, so one more thing to sort out.
As it happens there are LLVM bugs
On 20 June 2018 at 17:26, Alexander Richardson wrote:
>
> When I made the change to use llvm-objdump in CheriBSD I had to change the
> objdump flags from -xrsSd to -r -s -p -S -d -h -l -t.
Ah yes, I recall discussing this now. Per GNU objdump's man page, -x
is equivalent to -a -f -h -p -r -t.
> On 21 Jun 2018, at 09:00, KIRIYAMA Kazuhiko wrote:
>
> At Wed, 20 Jun 2018 23:34:48 -0400,
> Allan Jude wrote:
>>
>> On 2018-06-20 21:36, KIRIYAMA Kazuhiko wrote:
>>> Hi all,
>>>
>>> I've been reported ZFS boot disable problem [1], and found
>>> that this issue occers form RAID
At Wed, 20 Jun 2018 23:34:48 -0400,
Allan Jude wrote:
>
> On 2018-06-20 21:36, KIRIYAMA Kazuhiko wrote:
> > Hi all,
> >
> > I've been reported ZFS boot disable problem [1], and found
> > that this issue occers form RAID configuration [2]. So I
> > rebuit with RAID5 and re-installed 12.0-CURRENT
> On 21 Jun 2018, at 06:34, Allan Jude wrote:
>
> On 2018-06-20 21:36, KIRIYAMA Kazuhiko wrote:
>> Hi all,
>>
>> I've been reported ZFS boot disable problem [1], and found
>> that this issue occers form RAID configuration [2]. So I
>> rebuit with RAID5 and re-installed 12.0-CURRENT
>>
15 matches
Mail list logo