[Bug 238730] r349241 on ppc64 IBM 970 instant panic in vm_mem_init(0)

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238730 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com ---

[Bug 238730] r349241 on ppc64 IBM 970 instant panic in vm_mem_init(0)

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238730 --- Comment #9 from Dennis Clarke --- Created attachment 205784 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205784=edit r349985 ppc64 panic at boot on PowerMac G5 quad r349985 panic at boot. -- You are receiving this mail

[Bug 238730] r349241 on ppc64 IBM 970 instant panic in vm_mem_init(0)

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238730 --- Comment #8 from Dennis Clarke --- (In reply to Justin Hibbits from comment #7) Excellent idea however I was going to attempt a more blunt force approach. My idea after seeing another instant panic would be to wipe the machine clean

[Bug 238730] r349241 on ppc64 IBM 970 instant panic in vm_mem_init(0)

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238730 --- Comment #7 from Justin Hibbits --- Can you try bisecting the kernel? I don't have an applicable G5 to test with. You have a known-good and a known-bad. Bisecting between them should only be ~13 builds (and you might be able to

[Bug 238730] r349241 on ppc64 IBM 970 instant panic in vm_mem_init(0)

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238730 --- Comment #6 from Dennis Clarke --- Last known kernel to boot and allow me to compile head/current was r345425 and I used that today to buildworld and kernel for r349985 which instantly panics. So has anyone seen anything recent build

Problem reports for b...@freebsd.org that need special attention

2019-07-14 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 239207] boot0 error if floppy disk is not present

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239207 Bug ID: 239207 Summary: boot0 error if floppy disk is not present Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New

[Bug 238558] Correctly use BASEDIR when checking for src component in freebsd-update

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238558 --- Comment #4 from Christoph Kliemann --- Sorry, I'm not a FreeBSD developer. Here is a list of current FreeBSD developers: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html It may take some time.

[Bug 238558] Correctly use BASEDIR when checking for src component in freebsd-update

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238558 --- Comment #3 from Waqar Ahmed --- Hello Christoph, can you please confirm if you still require something from my end ? Also when can i expect this to be reviewed ? Thank you! -- You are receiving this mail because: You are the assignee

[Bug 238558] Correctly use BASEDIR when checking for src component in freebsd-update

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238558 --- Comment #2 from Christoph Kliemann --- Found the function call, please disregard. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org

[Bug 238558] Correctly use BASEDIR when checking for src component in freebsd-update

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238558 Christoph Kliemann changed: What|Removed |Added CC||freebsd-b...@cklie.de ---

[Bug 234793] Failed unknown for $USER in sshd logs even if I got authenticated

2019-07-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793 --- Comment #17 from Egbert Pot --- Issue still present on 12.0-RELEASE-p7 Is there a possibility to upgrade the OpenSSH package to version 7.9 or 8.0? -- You are receiving this mail because: You are the assignee for the bug.