Re: Boot failure, amd64 (HP EliteBook 650 G10)

Hi Graham, On 3/9/24 10:52, Graham Perrin wrote: amd64. AFAICT the EliteBook 650 G10 was introduced around May 2023. Does anything in the three photographs tally with a report in Bugzilla? Any overlap with

Re: Boot failure, amd64 (HP EliteBook 650 G10)

I'd love to borrow one of these machines fir a week or so. Warner On Sat, Mar 9, 2024, 2:52 AM Graham Perrin wrote: > > > amd64. > > AFAICT the EliteBook 650 G10 was introduced around May 2023. > > Does anything in the three photographs t

Re: Boot failure on refreshed Dell Precision 7550

> On 10. Jul 2020, at 16:43, Shawn Webb wrote: > > On Fri, Jul 10, 2020 at 04:36:41PM +0300, Toomas Soome wrote: >> >> >>> On 10. Jul 2020, at 16:25, Shawn Webb wrote: >>> >>> Hey all, >>> >>> I just got in a new Dell Precision 7550 laptop. Tried booting FreeBSD >>> on it and UEFI boot fai

Re: Boot failure on refreshed Dell Precision 7550

> On 10. Jul 2020, at 16:25, Shawn Webb wrote: > > Hey all, > > I just got in a new Dell Precision 7550 laptop. Tried booting FreeBSD > on it and UEFI boot failed. The screen goes black immedately when > selecting the memstick and around ten to twenty seconds later, the > system reboots. > >

Re: Boot failure on refreshed Dell Precision 7550

On Fri, Jul 10, 2020 at 09:43:59AM -0400, Shawn Webb wrote: > On Fri, Jul 10, 2020 at 04:36:41PM +0300, Toomas Soome wrote: > > > > > > > On 10. Jul 2020, at 16:25, Shawn Webb wrote: > > > > > > Hey all, > > > > > > I just got in a new Dell Precision 7550 laptop. Tried booting FreeBSD > > > on

Re: Boot failure on refreshed Dell Precision 7550

On Fri, Jul 10, 2020 at 04:36:41PM +0300, Toomas Soome wrote: > > > > On 10. Jul 2020, at 16:25, Shawn Webb wrote: > > > > Hey all, > > > > I just got in a new Dell Precision 7550 laptop. Tried booting FreeBSD > > on it and UEFI boot failed. The screen goes black immedately when > > selecting

Re: Boot failure: panic: No heap setup

> On 30 Mar 2018, at 18:03, Stefan Esser wrote: > > Am 29.03.18 um 07:15 schrieb Toomas Soome: >> >> >>> On 29 Mar 2018, at 01:06, Stefan Esser wrote: >>> >>> Am 28.03.18 um 22:28 schrieb Warner Losh: > Hmmm, the code references point into the boot loader code - I had > expected tha

Re: Boot failure: panic: No heap setup

Am 29.03.18 um 07:15 schrieb Toomas Soome: > > >> On 29 Mar 2018, at 01:06, Stefan Esser wrote: >> >> Am 28.03.18 um 22:28 schrieb Warner Losh: Hmmm, the code references point into the boot loader code - I had expected that there is a problem in the kernel, not the boot loader. >>

Re: Boot failure: panic: No heap setup

> On 29 Mar 2018, at 01:06, Stefan Esser wrote: > > Am 28.03.18 um 22:28 schrieb Warner Losh: >>> Hmmm, the code references point into the boot loader code - I had >>> expected that there is a problem in the kernel, not the boot loader. >>> [1] https://svnweb.freebsd.org/base/head/st

Re: Boot failure: panic: No heap setup

Am 28.03.18 um 22:28 schrieb Warner Losh: > > Hmmm, the code references point into the boot loader code - I had > > expected that there is a problem in the kernel, not the boot loader. > > > >> [1] > >> https://svnweb.freebsd.org/base/head/stand/libsa/sbrk.c?view=markup#l56 >

Re: Boot failure: panic: No heap setup

On Wed, Mar 28, 2018 at 1:10 PM, Kyle Evans wrote: > On Tue, Mar 27, 2018 at 6:39 PM, Stefan Esser wrote: > > Am 27.03.18 um 21:31 schrieb Kyle Evans: > >> > >> On Tue, Mar 27, 2018 at 11:06 AM, Stefan Esser wrote: > >>> > >>> A few weeks ago I tried the LUA boot and found, that my kernel did n

Re: Boot failure: panic: No heap setup

On Tue, Mar 27, 2018 at 6:39 PM, Stefan Esser wrote: > Am 27.03.18 um 21:31 schrieb Kyle Evans: >> >> On Tue, Mar 27, 2018 at 11:06 AM, Stefan Esser wrote: >>> >>> A few weeks ago I tried the LUA boot and found, that my kernel did not >>> start >>> (i.e. did not print the initial FreeBSD version

Re: Boot failure: panic: No heap setup

Am 27.03.18 um 21:31 schrieb Kyle Evans: On Tue, Mar 27, 2018 at 11:06 AM, Stefan Esser wrote: A few weeks ago I tried the LUA boot and found, that my kernel did not start (i.e. did not print the initial FreeBSD version line), but instead stopped with: Oy =/ panic: No heap setup I recovere

Re: Boot failure: panic: No heap setup

On Tue, Mar 27, 2018 at 11:06 AM, Stefan Esser wrote: > A few weeks ago I tried the LUA boot and found, that my kernel did not start > (i.e. did not print the initial FreeBSD version line), but instead stopped > with: Oy =/ > panic: No heap setup > > I recovered by booting from an alternate boot

Re: Boot failure - svn up from this morning

Hi, I had the same problems, however, there is one more regression after these changes. It stably reproduces if you use EFI_STAGING_SIZE. I have custom FreeBSD distributive which has a sufficiently large mfsroot which is loaded through UEFI mode. To solve the problem, it was suggested to increase

Re: Boot failure - svn up from this morning

On 7 Mar 2017, at 16:50, Chris H wrote: On Tue, 07 Mar 2017 16:27:59 -0330 "Jonathan Anderson" wrote Hi, On 5 Mar 2017, at 20:31, Chris H wrote: OK copying the boot.efi from the install DVD will only hose the system (EFI). Before I attempt to do the same thing... what do you mean by "ho

RE: Boot failure - svn up from this morning

> From: Alex Deiter [mailto:alex.dei...@gmail.com] > Hello Dexuan, > This issue reproduced at least for 4 different HW platform > How can I help you resolve this issue ? > > The same result for r314862: Hi guys, Sorry, I had to commit a new patch (r314891) just now to really fix the off-by-one bu

RE: Boot failure - svn up from this morning

ima > ; Sepherosa Ziehau > Subject: Re: Boot failure - svn up from this morning > > Hello Dexuan, > > This issue reproduced at least for 4 different HW platform: > > Supermicro 6037R-TXRF > Supermicro A1SRM-2758F > Supermicro X9SCM-F > Gigabyte GA-C1037UN-EU &g

Re: Boot failure - svn up from this morning

yaneurabeya) ; Michael Tuexen >> ; Roberto Rodriguez Jr ; Guido >> Falsi ; Warner Losh ; Ultima >> ; Sepherosa Ziehau >> Subject: RE: Boot failure - svn up from this morning >> >>> From: Alex Deiter [mailto:alex.dei...@gmail.com] >>> Sent: Tuesday, Mar

Re: Boot failure - svn up from this morning

On Tue, 07 Mar 2017 16:27:59 -0330 "Jonathan Anderson" wrote > Hi, > > On 5 Mar 2017, at 20:31, Chris H wrote: > > > OK copying the boot.efi from the install DVD will only > > hose the system (EFI). > > Before I attempt to do the same thing... what do you mean by "hose the > system"? Is the c

Re: Boot failure - svn up from this morning

Hi, On 5 Mar 2017, at 20:31, Chris H wrote: OK copying the boot.efi from the install DVD will only hose the system (EFI). Before I attempt to do the same thing... what do you mean by "hose the system"? Is the correct recovery path to build a new USB image with "make release" post-r314828?

Re: Boot failure - svn up from this morning

On Mon, 6 Mar 2017 04:01:04 + Dexuan Cui wrote > > From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd- > > curr...@freebsd.org] On Behalf Of Dexuan Cui > > Hi Chris, > > Thank you very much for the screenshots!!! > > > > On the host there is a 1MB LoaderData memory range, which sp

RE: Boot failure - svn up from this morning

> From: Dexuan Cui > I committed r314770 just now to minimize the impact: > https://svnweb.freebsd.org/base?view=revision&revision=314770 > > Please let me know in case this can't solve the issue. Sorry, r314770 has a bug, so I had to commit r314828 for this: https://svnweb.freebsd.org/base?vie

RE: Boot failure - svn up from this morning

> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd- > curr...@freebsd.org] On Behalf Of Dexuan Cui > Hi Chris, > Thank you very much for the screenshots!!! > > On the host there is a 1MB LoaderData memory range, which splits > the big Conventional Memory range into a small one (15MB)

RE: Boot failure - svn up from this morning

> From: Dexuan Cui > Sent: Monday, March 6, 2017 13:10 > Can you please try the below patch? > https://reviews.freebsd.org/D9904 > You can find the URL of the "Download Raw Diff" in the page and > 'wget' the patch and then apply it. > > It should be able to fix the recent UEFI-boot issue introduce

Re: Boot failure - svn up from this morning

On Mon, 6 Mar 2017 04:01:04 + Dexuan Cui wrote > > From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd- > > curr...@freebsd.org] On Behalf Of Dexuan Cui > > Hi Chris, > > Thank you very much for the screenshots!!! > > > > On the host there is a 1MB LoaderData memory range, which sp

Re: Boot failure - svn up from this morning

On Mon, 6 Mar 2017 03:00:20 + Dexuan Cui wrote > > From: Chris H [mailto:bsd-li...@bsdforge.com] > > Sent: Monday, March 6, 2017 09:57 > > > Thanks! I'm eager to see your screenshots. > > > The line whose "Physical" address contains 2MB is the most interesting to > > > me. And please at least

RE: Boot failure - svn up from this morning

> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd- > curr...@freebsd.org] On Behalf Of Dexuan Cui > Hi Chris, > Thank you very much for the screenshots!!! > > On the host there is a 1MB LoaderData memory range, which splits > the big Conventional Memory range into a small one (15MB)

RE: Boot failure - svn up from this morning

> From: Chris H [mailto:bsd-li...@bsdforge.com] > Sent: Monday, March 6, 2017 09:57 > > Thanks! I'm eager to see your screenshots. > > The line whose "Physical" address contains 2MB is the most interesting to > > me. > > And please at least post the other lines around the line. > OK. Her you go. I

Re: Boot failure - svn up from this morning

Thank you verymuch for the reply, Dexuan! On Mon, 6 Mar 2017 00:34:19 + Dexuan Cui wrote > > From: Chris H [mailto:bsd-li...@bsdforge.com] > > > Hi Alex, > > > Thanks for the info! > > > Unluckily it looks the delay() in my patch didn't work here somehow, so > > > the screen scrolled up so q

RE: Boot failure - svn up from this morning

> From: Chris H [mailto:bsd-li...@bsdforge.com] > OK copying the boot.efi from the install DVD will only > hose the system (EFI). Do you mean copying the boot.efi from the install DVD doesn't work? If so we need to build a good boot.efi with the CURRENT code + reverting the offending commit. > So

RE: Boot failure - svn up from this morning

> From: Chris H [mailto:bsd-li...@bsdforge.com] > > Hi Alex, > > Thanks for the info! > > Unluckily it looks the delay() in my patch didn't work here somehow, so the > > screen scrolled up so quickly that we're unable to see the output clearly... > > :-( > > > > Luckily we can use this new method:

Re: Boot failure - svn up from this morning

On Sun, 05 Mar 2017 15:14:52 -0800 "Chris H" wrote > On Sun, 5 Mar 2017 10:48:32 + Dexuan Cui wrote > > > > From: Alex Deiter > > > Sent: Sunday, March 5, 2017 03:32 > > > > > > Hello, > > > > > > Screenshot: boot with patched loader: > > > Video: boot with patched loader: > > > > Hi Ale

Re: Boot failure - svn up from this morning

On Sun, 5 Mar 2017 10:48:32 + Dexuan Cui wrote > > From: Alex Deiter > > Sent: Sunday, March 5, 2017 03:32 > > > > Hello, > > > > Screenshot: boot with patched loader: > > Video: boot with patched loader: > > Hi Alex, > Thanks for the info! > Unluckily it looks the delay() in my patch did

RE: Boot failure - svn up from this morning

> From: Alex Deiter > Sent: Sunday, March 5, 2017 03:32 > > Hello, > > Screenshot: boot with patched loader: > Video: boot with patched loader: Hi Alex, Thanks for the info! Unluckily it looks the delay() in my patch didn't work here somehow, so the screen scrolled up so quickly that we're una

Re: Boot failure - svn up from this morning

On Fri, Mar 03, 2017 at 02:30:08PM +0100, Michael Tuexen wrote: > > On 3 Mar 2017, at 12:59, Dexuan Cui wrote: > > > >> From: Dexuan Cui > >> Sent: Friday, March 3, 2017 19:50 > >>> From: Alex Deiter > >>> Sent: Friday, March 3, 2017 17:22 > >>> Hello, > >>> The same issue with FreeBSD 12.0-CURRE

Re: Boot failure - svn up from this morning

Hello, Screenshot: boot with patched loader: http://picpaste.com/IMG_1768-PnmZAtBZ.JPG Video: boot with patched loader: https://youtu.be/thzyRk0D36w Thank you! Alex Deiter alex.dei...@gmail.com > On 3 Mar 2017, at 16:37, Dexuan Cui wrote: > >> From: Michael Tuexen >> Sent: Friday, March 3,

Re: Boot failure - svn up from this morning

Hello Dexuan, Thank you for the patch! I’ll test it and let you know the result. Thank you! Alex Deiter alex.dei...@gmail.com > On 3 Mar 2017, at 14:49, Dexuan Cui wrote: > >> From: Alex Deiter >> Sent: Friday, March 3, 2017 17:22 >> >> Hello, >> The same issue with FreeBSD 12.0-CURRENT-r3

Re: Boot failure - svn up from this morning

> On 3 Mar 2017, at 12:59, Dexuan Cui wrote: > >> From: Dexuan Cui >> Sent: Friday, March 3, 2017 19:50 >>> From: Alex Deiter >>> Sent: Friday, March 3, 2017 17:22 >>> Hello, >>> The same issue with FreeBSD 12.0-CURRENT-r314563: >>> elf64_loadimage: could not read symbols - skipped! >>> >>> I su

RE: Boot failure - svn up from this morning

> From: Michael Tuexen > Sent: Friday, March 3, 2017 21:30 > > BTW, I understand it's really annoying to boot the host first... > > I'm really sorry for this. > > > > I suppose you're able to build or find a good 'loader.efi' binary on > > another host, > > and then manage to replace the bad 'loa

RE: Boot failure - svn up from this morning

> From: Dexuan Cui > Sent: Friday, March 3, 2017 19:50 > > From: Alex Deiter > > Sent: Friday, March 3, 2017 17:22 > > Hello, > > The same issue with FreeBSD 12.0-CURRENT-r314563: > > elf64_loadimage: could not read symbols - skipped! > > > > I suspect regression after: > > > > Revision 314547 - Di

RE: Boot failure - svn up from this morning

> From: Alex Deiter > Sent: Friday, March 3, 2017 17:22 > > Hello, > The same issue with FreeBSD 12.0-CURRENT-r314563: > elf64_loadimage: could not read symbols - skipped! > > I suspect regression after: > > Revision 314547 - Directory Listing > Modified Thu Mar 2 07:25:50 2017 UTC (25 hours, 54 mi

Re: Boot failure - svn up from this morning

Hello, The same issue with FreeBSD 12.0-CURRENT-r314563: elf64_loadimage: could not read symbols - skipped! http://picpaste.com/IMG_1764-vfZl1l5o.JPG I suspect regression after: Revision 314547 - Directory Listing Modified Thu Mar 2 07:25:50 2017 UTC (25 hours, 54 minutes ago) by dexuan load

Re: Boot failure - svn up from this morning

On Thu, 2 Mar 2017 21:32:39 -0800 "Ngie Cooper (yaneurabeya)" wrote > > On Mar 2, 2017, at 21:16, Chris H wrote: > > > > On Thu, 2 Mar 2017 21:56:38 -0500 (EST) AN wrote > > > >> Hi: > >> > >> I'm having a major problem after updating a 12-current machine today. > >> After buildworld/kernel/

Re: Boot failure - svn up from this morning

> On Mar 2, 2017, at 21:16, Chris H wrote: > > On Thu, 2 Mar 2017 21:56:38 -0500 (EST) AN wrote > >> Hi: >> >> I'm having a major problem after updating a 12-current machine today. >> After buildworld/kernel/install cycle on reboot I'm getting the following >> failure: >> >> "/boot/kernel/ke

Re: Boot failure - svn up from this morning

On Thu, 2 Mar 2017 21:56:38 -0500 (EST) AN wrote > Hi: > > I'm having a major problem after updating a 12-current machine today. > After buildworld/kernel/install cycle on reboot I'm getting the following > failure: > > "/boot/kernel/kernel text=0xb7716f data=0x100548+0x398358 > elf64_loadima

Re: Boot failure with r272146

On Fri, 2014-09-26 at 07:40 -0700, Justin Hibbits wrote: > That fixed it, thanks! > > -Justin Fix committed as r272181, sorry for the glitch. -- Ian > On Sep 26, 2014 6:59 AM, "Ian Lepore" wrote: > > > On Thu, 2014-09-25 at 20:40 -0700, Justin Hibbits wrote: > > > With r272146 my SATA control

Re: Boot failure with r272146

That fixed it, thanks! -Justin On Sep 26, 2014 6:59 AM, "Ian Lepore" wrote: > On Thu, 2014-09-25 at 20:40 -0700, Justin Hibbits wrote: > > With r272146 my SATA controller fails to attach, preventing the kernel > > from mounting root. I've attached a log of as much as dconschat would > > allow.

Re: Boot failure with r272146

On Thu, 2014-09-25 at 20:40 -0700, Justin Hibbits wrote: > With r272146 my SATA controller fails to attach, preventing the kernel > from mounting root. I've attached a log of as much as dconschat would > allow. The relevant portion is pcib10: > > atapci0: mem 0xfa402000-0xfa403fff > at device 1

Re: boot failure at ZFS: unsupported feature: com.delphix:hole_birth

On 1/2/14, 7:18 AM, 乔楚 wrote: update bootcod: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i ada0 Now, it can boot ok. thanks for letting us know.. I know I'll be hitting this soon :-) 2014/1/1 乔楚 Today ,I upgrade to http://svnweb.freebsd.org/base?view=revision&revision=260157 Aft

Re: boot failure at ZFS: unsupported feature: com.delphix:hole_birth

update bootcod: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i ada0 Now, it can boot ok. 2014/1/1 乔楚 > Today ,I upgrade to > http://svnweb.freebsd.org/base?view=revision&revision=260157 > > After svn up, make clean, make buildworld, make buildkernel, make > installkernel, reboot, mergemas

Re: boot failure after upgrade to HEAD from svn: zfs i/o error - all block copies unavailable invalid format

Now , I'm recovery my OS. I installed freebsd11 on a new disk ,and copy every thing to it. 2013/12/12 乔楚 > >Have you updated bootcode then? > After make installkernel && make installworld && reboot, boot error. > > > Yes ,I can import in -currentr258961( > http://ftp.freebsd.org/pub/FreeBSD/sna

Re: boot failure after upgrade to HEAD from svn: zfs i/o error - all block copies unavailable invalid format

>Have you updated bootcode then? After make installkernel && make installworld && reboot, boot error. Yes ,I can import in -currentr258961( http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/FreeBSD-11.0-CURRENT-amd64-20131205-r258961-memstick.img ). Now, I install -currentr258961 on a

Re: boot failure after upgrade to HEAD from svn: zfs i/o error - all block copies unavailable invalid format

10.12.2013 18:59, 乔楚 wrote: *Today, after **upgrade to HEAD from svn, My FreeBSD can't boot.* *Error message:* *ZFS: i/o error all block copies unavailable **Invalid format* I see you are using GPT. Have you updated bootcode then? Can you import your pool from any HEAD snapshot? -- Sphinx

Re: boot failure after upgrade to HEAD from svn: zfs i/o error - all block copies unavailable invalid format

Plugin the disk as usb disk to other freebsd11(vm) , dmesg info: ugen1.2: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x4100 umass0:3:0: Attached to scbus3 da1 at umass-sim0 bus 0 scbus3 target 0 lun 0 da1: Fixed Direct Access SCSI-0 device da1: Serial Number 0033

Re: Boot failure with latest -CURRENT

Andre Guibert de Bruet schrieb: On Fri, 31 Jan 2003, Pascal Giannakakis wrote: today i updated sources with CVS, compiled world and kernel, then rebooted. During boot it hangs at the boot message (the place where in FreeBSD 4.7 a lot of boot info would appear, like ata, cpu, usb0 blah blah). -

Re: Boot failure with latest -CURRENT

On Fri, 31 Jan 2003, Pascal Giannakakis wrote: > today i updated sources with CVS, compiled world and kernel, then > rebooted. During boot it hangs at the boot message (the place where in > FreeBSD 4.7 a lot of boot info would appear, like ata, cpu, usb0 blah blah). > > - The keyboard num-lock do

RE: boot failure

On 09-Apr-2002 Jan Stocker wrote: > After a buildworld / buildkernel /installkernel / installworld on my current > system from yesterday sources (about 19:00 CET) my system doesnt boot: The > kernel and the acpi module will be loaded and then nothing happens for a > second, something is accessing