[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #48 from Dennis Clarke --- (In reply to Mark Millard from comment #46) oops. Bug 238730 - r349985 on ppc64 IBM 970MP PowerMac G5 sys/dev/bge/if_bge.c must move the device_get_devclass(bus) https://bu

[Bug 238730] r349985 on ppc64 IBM 970MP PowerMac G5 sys/dev/bge/if_bge.c must move the device_get_devclass(bus)

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238730 Dennis Clarke changed: What|Removed |Added Summary|r349985 on ppc64 IBM 970MP |r349985 on ppc64 IBM 970MP

[Bug 238730] r349985 on ppc64 IBM 970MP PowerMac G5 possible panic in bus_generic_new_pass

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238730 Dennis Clarke changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #30 from Dennis

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #47 from Mark Millard --- (In reply to Mark Millard from comment #45) My wording was poor: the "it" that crashes for ofwdump -ap is the system (FreeBSD), not the program. The issue is FreeBSD trying to handle an openfirnware e

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #46 from Mark Millard --- (In reply to Dennis Clarke from comment #44) Bugzilla 238730 is not a duplicate of this bug: It has its own fix with the change to if_bge.c that was noted in its comments: 239245 is a distinct problem

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #45 from Mark Millard --- (In reply to Dennis Clarke from comment #42) The output from: # ofwdump -Pmodel /rom/boot-rom includes textual lines like: 'Apple PowerMac11,2 5.2.7f1 BootROM built on 09/30/05 at 15:3' '1:0

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #44 from Dennis Clarke --- *** Bug 238730 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@f

[Bug 238730] r349985 on ppc64 IBM 970MP PowerMac G5 possible panic in bus_generic_new_pass

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238730 Dennis Clarke changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #43 from Dennis Clarke --- (In reply to Francis Little from comment #37) I think that the three of us have four machines on hand. I have two of these 64-bit PowerMac G5 types wherein I rarely powerup the smaller of the pair. Ho

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #42 from Dennis Clarke --- Regarding OpenFirmware the usual boot messages are none to helpful : see https://bz-attachments.freebsd.org/attachment.cgi?id=205912 I will shutdown the boxen and try to boot to the Openfirmware scr

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #41 from Dennis Clarke --- Created attachment 205912 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205912&action=edit OpenFirmware messages from PowerMac G5 quad during boot OpenFirmware messages from PowerMac G5 qu

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #40 from Dennis Clarke --- (In reply to Mark Millard from comment #34) Yes I think that myself and Francis Little need to get on the same page in every respect. If we can. I think we have nearly identical hardware and we certai

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #39 from Dennis Clarke --- (In reply to Francis Little from comment #31) Regarding the "usefdt=1" there isa blunt comment from Justin Hibbits on this at the bottom of : Bug 233863 - Various PowerMac G5 models may require

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #38 from Mark Millard --- (In reply to Francis Little from comment #37) Your list points out that I forgot to list the CD/DVD: cd0: Removable CD-ROM SCSI device In case you want to see matches to what you were explict about:

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #37 from Francis Little --- (In reply to Mark Millard from comment #36) So for mine its all fairly standard stuff and not a million miles from yours: Apple PowerMac11,2 5.2.7f1 BootROM Built on 09/30/05 at 15:31:03 cpu0: IBM

[Bug 239315] Forth loader misreads nextboot.conf files over 80 bytes

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239315 Bug ID: 239315 Summary: Forth loader misreads nextboot.conf files over 80 bytes Product: Base System Version: CURRENT Hardware: Any OS: Any

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #36 from Mark Millard --- (In reply to Francis Little from comment #35) For my context: Apple PowerMac11,2 5.2.7f1 BootROM built on 09/30/05 at 15:31:03 What is added to the quads could matter. I've got: 16 GiBYte of ECC RAM

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #35 from Francis Little --- (In reply to Mark Millard from comment #34) That is a good question, are the Quad's all the same? My OFW reports: Apple PowerMac11,2 5.2.7f1 BootROM Built on 09/30/05 at 15:31:03 Dennis, do you h

[Bug 236466] [sendfile]: panic when VOP_READ returns an error

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236466 --- Comment #5 from commit-h...@freebsd.org --- A commit references this bug: Author: asomers Date: Fri Jul 19 18:03:30 UTC 2019 New revision: 350144 URL: https://svnweb.freebsd.org/changeset/base/350144 Log: sendfile: don't panic when V

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #34 from Mark Millard --- (In reply to Francis Little from comment #31) If I read Dennis Clarke's material correctly, he is not using usefdt=1 . Also, as of r347463, the known issue for which usefdt=1 was being used was handled

[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #46 from Jeff Kletsky --- To add, this box is *not* using UEFI boot, but using BIOS ("legacy") boot, so the issue is not confined to UEFI boot. The release notes at https://www.freebsd.org/releases/12.0R/relnotes.html#errata do

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #33 from Francis Little --- So reinstalling with the FreeBSD-13.0-CURRENT-powerpc-powerpc64-20190718-r350103-disc1.iso and doing a buildworld / kernel etc from the r350114 svn sources had produced a workable G5 Quad! Booting us

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #32 from Francis Little --- Also, using the snapshot linked below, by interrupting the loader and setting usefdt=1, boots to the installer and will install a bootable system without panic: http://ftp.freebsd.org/pub/FreeBSD/sn

[Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239245 --- Comment #31 from Francis Little --- So using the method of extracting the kernel from ci.freebsd.org over my install (I use a 12-STABLE r349903 ISO to install), I am able to boot an r350114 kernel by setting set usefdt=1 at the boot