[Bug 239894] security.bsd.stack_guard_page default causes Java to crash

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239894

--- Comment #26 from commit-h...@freebsd.org ---
A commit references this bug:

Author: kib
Date: Tue Sep 10 07:29:23 UTC 2019
New revision: 352125
URL: https://svnweb.freebsd.org/changeset/base/352125

Log:
  MFC r351773:
  Add procctl(PROC_STACKGAP_CTL).

  PR:   239894

Changes:
_U  stable/11/
  stable/11/lib/libc/sys/procctl.2
  stable/11/sys/compat/freebsd32/freebsd32_misc.c
  stable/11/sys/kern/kern_exec.c
  stable/11/sys/kern/kern_fork.c
  stable/11/sys/kern/kern_procctl.c
  stable/11/sys/sys/proc.h
  stable/11/sys/sys/procctl.h
  stable/11/sys/vm/vm_map.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339

--- Comment #4 from Greg V  ---
(In reply to Vladimir Kondratyev from comment #3)
I mean it's no longer necessary to comment out the Skylake lpss reset (the line
that writes zero to 0x204)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339

--- Comment #5 from Vladimir Kondratyev  ---
Try to set SDA_RX_HOLD to 1. That is what Linux does.
reg_write(sc, IG4_REG_SDA_HOLD, 28); -> reg_write(sc, IG4_REG_SDA_HOLD, 0x1
+ 28);

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 239552] Quotas on NFS shares broken (return: none) on 11.3-RELEASE

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239552

--- Comment #6 from Dani  ---
(In reply to Sean Eric Fagan from comment #5)
Is there anything i can do for you to help speed this up? Is there a way to
force which version is going to be used?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 239894] security.bsd.stack_guard_page default causes Java to crash

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239894

--- Comment #27 from commit-h...@freebsd.org ---
A commit references this bug:

Author: kib
Date: Tue Sep 10 09:57:25 UTC 2019
New revision: 352133
URL: https://svnweb.freebsd.org/changeset/base/352133

Log:
  MFC r351774:
  Add stackgap control mode to proccontrol(1).

  PR:   239894

Changes:
_U  stable/11/
  stable/11/usr.bin/proccontrol/proccontrol.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240471] panic: rcv_start < rcv_end

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240471

Bug ID: 240471
   Summary: panic: rcv_start < rcv_end
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: l...@freebsd.org

I've seen this panic for a while randomly.  I have cores.

this latest one is on r352025

Unread portion of the kernel message buffer:
panic: rcv_start < rcv_end
cpuid = 0
time = 1568101636
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe01f7ccb380
vpanic() at vpanic+0x19d/frame 0xfe01f7ccb3d0
panic() at panic+0x43/frame 0xfe01f7ccb430
tcp_update_dsack_list() at tcp_update_dsack_list+0x489/frame 0xfe01f7ccb4b0
tcp_do_segment() at tcp_do_segment+0x1fbd/frame 0xfe01f7ccb590
tcp_input() at tcp_input+0xde8/frame 0xfe01f7ccb6e0
ip_input() at ip_input+0x11d/frame 0xfe01f7ccb780
netisr_dispatch_src() at netisr_dispatch_src+0x89/frame 0xfe01f7ccb7f0
ether_demux() at ether_demux+0x13b/frame 0xfe01f7ccb820
ng_ether_rcv_upper() at ng_ether_rcv_upper+0x95/frame 0xfe01f7ccb840
ng_apply_item() at ng_apply_item+0x100/frame 0xfe01f7ccb8c0
ng_snd_item() at ng_snd_item+0x2ad/frame 0xfe01f7ccb900
ng_apply_item() at ng_apply_item+0x100/frame 0xfe01f7ccb980
ng_snd_item() at ng_snd_item+0x2ad/frame 0xfe01f7ccb9c0
ng_ether_input() at ng_ether_input+0x4c/frame 0xfe01f7ccb9f0
ether_nh_input() at ether_nh_input+0x2cd/frame 0xfe01f7ccba40
netisr_dispatch_src() at netisr_dispatch_src+0x89/frame 0xfe01f7ccbab0
ether_input() at ether_input+0x48/frame 0xfe01f7ccbad0
bce_intr() at bce_intr+0x697/frame 0xfe01f7ccbb50
ithread_loop() at ithread_loop+0x187/frame 0xfe01f7ccbbb0
fork_exit() at fork_exit+0x84/frame 0xfe01f7ccbbf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe01f7ccbbf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
Uptime: 2d7h30m34s
Dumping 26161 out of 131027
MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%

__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55  __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct
pcpu,
(kgdb) #0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1  doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:392
#2  0x804bd160 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:479
#3  0x804bd5d9 in vpanic (fmt=, ap=)
at /usr/src/sys/kern/kern_shutdown.c:908
#4  0x804bd313 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:835
#5  0x80676049 in tcp_update_dsack_list (tp=0xf81092c91760,
rcv_start=1781970437, rcv_end=1781970437)
at /usr/src/sys/netinet/tcp_sack.c:166
#6  0x8066b01d in tcp_do_segment (m=0xf806144cfa00,
th=, so=0xf8018caf2a98, tp=0xf81092c91760,
drop_hdrlen=40, tlen=, iptos=0 '\000')
at /usr/src/sys/netinet/tcp_input.c:3076
#7  0x80668378 in tcp_input (mp=,
offp=, proto=)
at /usr/src/sys/netinet/tcp_input.c:1373
#8  0x805f2c6d in ip_input (m=0x0)
at /usr/src/sys/netinet/ip_input.c:829
#9  0x805ce9c9 in netisr_dispatch_src (proto=1,
source=, m=) at /usr/src/sys/net/netisr.c:1123
#10 0x805c3bfb in ether_demux (ifp=0xf80129859000,
m=) at /usr/src/sys/net/if_ethersubr.c:913
#11 0x827f4045 in ng_ether_rcv_upper (hook=,
item=) at /usr/src/sys/netgraph/ng_ether.c:741
#12 0x827e1750 in ng_apply_item (node=0xf8012ee3e500,
item=0xf805ab929b00, rw=0) at /usr/src/sys/netgraph/ng_base.c:2403
#13 0x827e144d in ng_snd_item (item=0xf805ab929b00, flags=0)
at /usr/src/sys/netgraph/ng_base.c:2320
#14 0x827e1750 in ng_apply_item (node=0xf8012ee3e000,
item=0xf805ab929b00, rw=0) at /usr/src/sys/netgraph/ng_base.c:2403
#15 0x827e144d in ng_snd_item (item=0xf805ab929b00, flags=0)
at /usr/src/sys/netgraph/ng_base.c:2320
#16 0x827f3cbc in ng_ether_input (ifp=,
mp=0xfe01f7ccba18) at /usr/src/sys/netgraph/ng_ether.c:255
#17 0x805c4e4d in ether_input_internal (ifp=0xf80129859000,
m=0xf806144cfa00) at /usr/src/sys/net/if_ethersubr.c:654
#18 ether_nh_input (m=) at /usr/src/sys/net/if_ethersubr.c:735
#19 0x805ce9c9 in netisr_dispatch_src (proto=5,
source=, m=) at /usr/src/sys/net/netisr.c:1123
#20 0x805c4038 in ether_input (ifp=0xf80129859000, m=0x0)
at /usr/src/sys/net/if_ethersubr.c:823
#21 0x8262f877 in bce_rx_intr (sc=)
at /usr/src/sys/dev/bce/if_bce.c:6848
#22 bce_intr (xsc=0xfe020082) at /usr/src/sys/dev/bce/if_bce.c:8017
#23 0x80485ba7 in intr_event_execute_handlers (p=,
ie=) at /usr/src/sys/kern/kern_intr.c:1148
#24 ithread_execute_handlers (p=, ie=)
at /usr/src/sys/kern/kern_intr.c:1161
#2

[Bug 240472] r352025: when getting a core.txt file, missing the ps.

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240472

Bug ID: 240472
   Summary: r352025: when getting a core.txt file, missing the ps.
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: l...@freebsd.org

when getting a core.txt file, we now get:


ps -axlww

ps: _zombproc: no such symbol



-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240475] [PATCH]: Add support for CPUID 0x16 in tsc_freq_cpuid() (TSC clock)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240475

Bug ID: 240475
   Summary: [PATCH]: Add support for CPUID 0x16 in
tsc_freq_cpuid() (TSC clock)
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: n...@neelc.org

Created attachment 207346
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207346&action=edit
Patch (Revision 1)

Keep in mind that I am new to the kernel.

Description:

If frequency for CPUID 0x15 is zero, fall back to CPUID 0x16 for the TSC clock
if available. This is needed on some Intel SOCs like Skylake and Kaby Lake
whcih report 0 for the crystal clock..

Inspired by Linux commit 604dc9170f2435d27da5039a3efd757dceadc684.

Tested on the HP Spectre x360 13-ap0043dx running 13-CURRENT with an accurate
clock using this patch (without the patch, the ticks are slower).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240475] [PATCH]: Add support for CPUID 0x16 in tsc_freq_cpuid() (TSC clock)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240475

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240471] panic: rcv_start < rcv_end

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240471

Mark Linimon  changed:

   What|Removed |Added

   Keywords||panic

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240464] pcm: chn_write(): pcm2:virtual:dsp2.vp*: play interrupt timeout, channel dead

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240464

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|multime...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240463] netwait is required for systems with SSD's as boot device

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240463

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|r...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339

--- Comment #6 from Greg V  ---
(In reply to Vladimir Kondratyev from comment #5)
That did not help..

I looked at the Linux code, it sets (1 << 16) actually. (Also did not help.)
Zircon (Fuchsia) does not do this. The datasheet for Skylake does not list any
such field in that register, 15:0 are the hold time and 31:16 are reserved.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240475] [PATCH]: Add support for CPUID 0x16 in tsc_freq_cpuid() (TSC clock)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240475

--- Comment #1 from Neel Chauhan  ---
Fixed description:

If frequency for CPUID 0x15 is zero, fall back to CPUID 0x16 for the TSC clock
if available. This is needed on some Intel SOCs like Skylake and Kaby Lake
which report 0 for the crystal clock.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 239803] Problem with concurrent transfer of file descriptors

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239803

Jason A. Harmening  changed:

   What|Removed |Added

 CC||j...@freebsd.org

--- Comment #1 from Jason A. Harmening  ---
Possibly the same root cause as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227285 ?   Does the patch for
cycle-aware gc posted there fix this issue?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339

--- Comment #7 from Vladimir Kondratyev  ---
Created attachment 207356
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207356&action=edit
ig4.patch

You can try my ig4 driver version. It borrows timings from LPSS driver and have
some other improvements like polling mode, suspend/resume, some error handling
and so on.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339

--- Comment #8 from Vladimir Kondratyev  ---
(In reply to Greg V from comment #6)
> The datasheet for Skylake does not list any such field in that register, 15:0 
> are the hold time and 31:16 are reserved.
This field, like some other slave-mode related parameters, is not exposed in
desktop-class chipset specs, but exposed in SOCs specs e.g. Arria SOCs and
still has an effect as these devices shares common design.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240471] panic: rcv_start < rcv_end

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240471

Michael Tuexen  changed:

   What|Removed |Added

 CC||tue...@freebsd.org

--- Comment #1 from Michael Tuexen  ---
This panic should be fixed in https://svnweb.freebsd.org/changeset/base/352072.
Can you update and see if the problem persists?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240471] panic: rcv_start < rcv_end

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240471

Michael Tuexen  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|tue...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339

--- Comment #9 from Greg V  ---
(In reply to Vladimir Kondratyev from comment #7)

oh cool, you already wrote the ACPI lookup of parameters, I was thinking about
doing that haha. Though the values that it ends up applying seem really high
(564, 480 on i2c2 for SCL). I commented that out again

Unfortunately the problem is still there.

Some more testing:

- after the lockup in FreeBSD, Linux cannot recover that i2c bus either —
rebooting (not shutting down and powering up) into Chrome OS results in
'i2c_designware.2: controller timed out' and the touchpad not working;

- the EC interface on the same bus allows reading the console of the touchpad's
firmware, but that's impossible when the controller is locked up.. I'm waiting
for a debug cable to ship, but the documentation doesn't say that it's possible
to access the touchpad console through that;

- I added some logging to the error handling, on i2c0 (working touchscreen)
after reading the touchscreen's descriptor for setup there's an RX underflow,
but here (touchpad) that did not happen, none of these errors happened;

- with HAVE_IG4_POLLING in iichid, there's no RX underflow there (obviously),
but it does not fix the lockup.

I wonder if it might actually be iichid/imt doing something that causes the
touchpad to do something wrong with the bus…

log: https://gist.github.com/myfreeweb/67b3ca690c22b31f502079b11263f0f4

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339

--- Comment #10 from Greg V  ---
(In reply to Greg V from comment #9)

* the parameters are fine, I was expecting fast mode numbers and printing slow
mode ones

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339

--- Comment #11 from Vladimir Kondratyev  ---
(In reply to Greg V from comment #9)
> there's an RX underflow, but here (touchpad) that did not happen, none of 
> these errors happened;
RX underflow has happened on attempt to read THQA certificate which is
discarded right after it has been read. So failure to read it is not fatal.
By my experience "RX underflow" is caused by ig4 bugs usually, but I am not
100% sure that it is a law.

> - with HAVE_IG4_POLLING in iichid, there's no RX underflow there (obviously), 
> but it does not fix the lockup.
> I wonder if it might actually be iichid/imt doing something that causes the 
> touchpad to do something wrong with the bus…
Really, I have never tested imt with touchpads. It still does not support
button state reporting and clickpad detection. So any bugs are possible.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240485] [PATCH] ig4: Add Cannon Lake LP and H I2C Controller IDs

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240485

Bug ID: 240485
   Summary: [PATCH] ig4: Add Cannon Lake LP and H I2C Controller
IDs
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: n...@neelc.org

Created attachment 207365
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207365&action=edit
Patch (Revision 1)

Add PCI IDs for I2C controller for Intel Cannon Lake PCH models. Cannon Lake is
used on systems based on platforms like Intel Coffee Lake and Whiskey Lake.

Inspired by Linux commit b418bbff36dd25dc49ed6abbb1e1deedd0d7cff5

Tested on the HP Spectre x360 13-ap0043dx running 13-CURRENT.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240485] [PATCH] ig4: Add Cannon Lake LP and H I2C Controller IDs

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240485

Neel Chauhan  changed:

   What|Removed |Added

 CC||n...@neelc.org
   Keywords||patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 228826] [devmatch] Crossbuilding ARM64 from AMD64 requires manual run of kldxref -R /boot

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228826

Ed Maste  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2404
   ||78

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240485] ig4: Add Cannon Lake LP and H I2C Controller IDs

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240485

Kubilay Kocak  changed:

   What|Removed |Added

 Status|New |Open
   Keywords|patch   |feature, needs-qa
Summary|[PATCH] ig4: Add Cannon |ig4: Add Cannon Lake LP and
   |Lake LP and H I2C   |H I2C Controller IDs
   |Controller IDs  |
  Flags||mfc-stable11?,
   ||mfc-stable12?
 CC||c...@freebsd.org,
   ||gre...@freebsd.org

--- Comment #1 from Kubilay Kocak  ---
Thank you for the report and patch Neel

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487

Bug ID: 240487
   Summary: Boot hangs at "Trying to mount root from
ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
   Product: Base System
   Version: 12.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: terry-free...@glaver.org

After upgrading from 12-STABLE r352025 to r352200, the system no longer
successfully boots, hanging at "Trying to mount root from ufs:/dev/da0p3
[rw]..." with no further messages. Reverting to r352025 boots normally.

After posting on -stable
https://lists.freebsd.org/pipermail/freebsd-stable/2019-September/091500.html
another user reports the same issue with a smaller range of commits - r352139
works, r352194 hangs.

I can provide access to the problem system if needed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487

Alan Somers  changed:

   What|Removed |Added

 CC||asom...@freebsd.org

--- Comment #1 from Alan Somers  ---
I'm seeing this behavior on stable/12 at r352201 on a super-common system: a
BHyve VM using virtio-blk and virtio-net, booting from UFS.  I would think it
should be easy for anybody to reproduce.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240061] MADV_FREE rewinds time to before fork()

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240061

--- Comment #9 from commit-h...@freebsd.org ---
A commit references this bug:

Author: kib
Date: Wed Sep 11 04:55:10 UTC 2019
New revision: 352202
URL: https://svnweb.freebsd.org/changeset/base/352202

Log:
  MFC r351830:
  madvise(MADV_FREE): Quick fix to time rewind.

  PR:   240061

Changes:
_U  stable/12/
  stable/12/sys/vm/vm_map.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240061] MADV_FREE rewinds time to before fork()

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240061

--- Comment #10 from commit-h...@freebsd.org ---
A commit references this bug:

Author: kib
Date: Wed Sep 11 04:59:27 UTC 2019
New revision: 352203
URL: https://svnweb.freebsd.org/changeset/base/352203

Log:
  MFC r351830:
  madvise(MADV_FREE): Quick fix to time rewind.

  PR:   240061

Changes:
_U  stable/11/
  stable/11/sys/vm/vm_map.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE

2019-09-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487

wolfg...@lyxys.ka.sub.org changed:

   What|Removed |Added

 CC||wolfg...@lyxys.ka.sub.org

--- Comment #2 from wolfg...@lyxys.ka.sub.org ---
I'm seeing the hang after successfully finding USB devices on 12-STABLE r352194
amd64 booting from zfs. r352139 worked ok.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"