Re: Congratulations on the Silver Anniversery Edition of FreeBSD
On 12 Dec, Kevin Oberman wrote: > I worked with 4.2BSD and 4.3BSD back in the 70s and 80s. I moved to other > OSes (Digital RT, RSX and VMS an Varian Vortex) and returned in about 1999 > to FreeBSD 3.0. I've been using FreeBSD ever since. It's been wonderful and > I am so grateful to all of the people who have keeping it going over the > years. I try to contribute when I can, but I am not a coder, so it's in > other ways. Wow, I haven't heard Varian Vortex mentioned in a long time. The first real computer that I got to play with was a Varian, back in the mid-70's. I think I still have some of the manuals. After that it was Univac Chi/OS, Digital RT, Harris Vulcan / VOS, Masscomp RTU, Sun SunOS / Solaris, a bit of NetBSD, FreeBSD starting somewhere in the 2.2.x timeframe, and more recently CentOS, Fedora, and Debian. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: boot hang with certain Phenom II cpu models
Hello Marek, On Thu, 2018-12-13 14:24 +0100, Marek Zarychta wrote: > Try to boot FreeBSD with GRUB2 as a workaround. My hardware configuration > also suffered from similar issue[1] so I had never successfully booted > FreeBSD using standard loader, but GRUB2 allowed to install and use FreeBSD > on this PC. > > [1]https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=151122 thanks for the suggestion. Unfortunately, it did not help; kernel still hangs :| Cheers, -sascha ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfsboot@12.0: Shortening read at xxxx from 16 to -479991569
2018-12-13 16:59, Warner Losh wrote:
Do you have any encrypted disks?
Indeed I do, both pools are encrypted.
(although I haven't seen such messages with 11.2, as far as I can tell)
Mark
On Thu, Dec 13, 2018, 6:19 AM Mark Martinec
wrote:
On one of my hosts (now running 12.0-RELEASE) the zfsboot shows
this weird negative number, which sounds suspicious:
Verifying DMI pool Data .
Shortening read at 3907029152 from 16 to 15
Shortening read at 7435283708 from 16 to -479991569
BTX loader 1.0 BTX version is 1.02
Consoles: ...
BIOS drive C: is disk0
...
The machine boots up normally and is fine, zpool scrub is happy,
so, should I worry? Anything fishy there?
Searching through sources, the message seems to come from
stand/i386/zfsboot/zfsboot.c :
printf("Shortening read at %lld from %d to %lld\n",
alignlba, alignnb, (zdsk->dsk.size + zdsk->dsk.start) -
alignlba);
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfsboot@12.0: Shortening read at xxxx from 16 to -479991569
On Thu, 2018-12-13 at 08:59 -0700, Warner Losh wrote:
> On Thu, Dec 13, 2018, 6:19 AM Mark Martinec s.si
> wrote:
>
> >
> > On one of my hosts (now running 12.0-RELEASE) the zfsboot shows
> > this weird negative number, which sounds suspicious:
> >
> > Verifying DMI pool Data .
> > Shortening read at 3907029152 from 16 to 15
> > Shortening read at 7435283708 from 16 to -479991569
> >
> > BTX loader 1.0 BTX version is 1.02
> > Consoles: ...
> > BIOS drive C: is disk0
> > ...
> >
> > The machine boots up normally and is fine, zpool scrub is happy,
> > so, should I worry? Anything fishy there?
> >
> > Searching through sources, the message seems to come from
> > stand/i386/zfsboot/zfsboot.c :
> >
> > printf("Shortening read at %lld from %d to %lld\n",
> > alignlba, alignnb, (zdsk->dsk.size + zdsk->dsk.start) -
> > alignlba);
> >
>
> Do you have any encrypted disks?
>
> Warner
I ran into something like this once before, and tracked it down to
using the roundup2() and rounddown2() macros from sys/param.h. In
particular, a mix of 32 and 64 bit types of different signedness
resulted in zero-extension instead of sign-extension of one of the
values, and that masked off significant bits, then a later subtraction
turned a result into a negative number.
-- Ian
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zfsboot@12.0: Shortening read at xxxx from 16 to -479991569
On Thu, Dec 13, 2018, 6:19 AM Mark Martinec On one of my hosts (now running 12.0-RELEASE) the zfsboot shows
> this weird negative number, which sounds suspicious:
>
>Verifying DMI pool Data .
>Shortening read at 3907029152 from 16 to 15
>Shortening read at 7435283708 from 16 to -479991569
>
>BTX loader 1.0 BTX version is 1.02
>Consoles: ...
>BIOS drive C: is disk0
>...
>
> The machine boots up normally and is fine, zpool scrub is happy,
> so, should I worry? Anything fishy there?
>
> Searching through sources, the message seems to come from
> stand/i386/zfsboot/zfsboot.c :
>
>printf("Shortening read at %lld from %d to %lld\n",
> alignlba, alignnb, (zdsk->dsk.size + zdsk->dsk.start) - alignlba);
>
Do you have any encrypted disks?
Warner
Mark
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: boot hang with certain Phenom II cpu models
W dniu 13.12.2018 o 11:56, Sascha Klauder pisze: > Hi all, > > I've recently upgraded my Athlon II based home box (happily > running FreeBSD for several years) to a Phenom II X4 960T CPU. > Now, kernel (11.2) hangs in early hardware initialization. > > Mainboard is a nForce 720 based Gigabyte GA-M720-US3 rev 1.0, > BIOS is latest and the CPU is on Gigabyte's CPU support list > for this board. > > A parallel Windows 7 installation continues to work flawlessly > and the system is stable running prime95. Memtest86 reports no > errors. I've tried several other OS boot media (DragonFly 5.4, > OpenBSD 6.4, Linux 4.9) -- all boot fine with no problems (see > dmesg output linked below). > > I've found two very similiar problem reports on the FreeBSD > forums. Both involve Phenom II cpu's and nForce-based mainboards, > so I think we're missing some BIOS/ACPI quirk here. > https://forums.freebsd.org/threads/10-1-installer-wont-boot-past-acpi.50015/ > https://forums.freebsd.org/threads/boot-hangs-after-cpu-upgrade.64410/ > > So far, I tried (unsuccessfully) to disable obvious ACPI sub- > systems (cpu, mwait, quirks) and debug settings (acpi.cpu_unordered, > acpi.max_threads). Anyone got a hint where to look or debug this > further? > > kernel boot messages (obtained from 10.4 amd64): > https://lair.griffinsplace.de/~sascha/phenom/dmesg-freeze-FreeBSD10.txt > > boot messages with the previous Athlon II cpu in this system: > https://lair.griffinsplace.de/~sascha/phenom/dmesg-FreeBSD-AthlonII.txt > > boot messages from DFly, OpenBSD and Linux: > https://lair.griffinsplace.de/~sascha/phenom/ Try to boot FreeBSD with GRUB2 as a workaround. My hardware configuration also suffered from similar issue[1] so I had never successfully booted FreeBSD using standard loader, but GRUB2 allowed to install and use FreeBSD on this PC. [1]https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=151122 -- Marek Zarychta signature.asc Description: OpenPGP digital signature
zfsboot@12.0: Shortening read at xxxx from 16 to -479991569
On one of my hosts (now running 12.0-RELEASE) the zfsboot shows
this weird negative number, which sounds suspicious:
Verifying DMI pool Data .
Shortening read at 3907029152 from 16 to 15
Shortening read at 7435283708 from 16 to -479991569
BTX loader 1.0 BTX version is 1.02
Consoles: ...
BIOS drive C: is disk0
...
The machine boots up normally and is fine, zpool scrub is happy,
so, should I worry? Anything fishy there?
Searching through sources, the message seems to come from
stand/i386/zfsboot/zfsboot.c :
printf("Shortening read at %lld from %d to %lld\n",
alignlba, alignnb, (zdsk->dsk.size + zdsk->dsk.start) - alignlba);
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
boot hang with certain Phenom II cpu models
Hi all, I've recently upgraded my Athlon II based home box (happily running FreeBSD for several years) to a Phenom II X4 960T CPU. Now, kernel (11.2) hangs in early hardware initialization. Mainboard is a nForce 720 based Gigabyte GA-M720-US3 rev 1.0, BIOS is latest and the CPU is on Gigabyte's CPU support list for this board. A parallel Windows 7 installation continues to work flawlessly and the system is stable running prime95. Memtest86 reports no errors. I've tried several other OS boot media (DragonFly 5.4, OpenBSD 6.4, Linux 4.9) -- all boot fine with no problems (see dmesg output linked below). I've found two very similiar problem reports on the FreeBSD forums. Both involve Phenom II cpu's and nForce-based mainboards, so I think we're missing some BIOS/ACPI quirk here. https://forums.freebsd.org/threads/10-1-installer-wont-boot-past-acpi.50015/ https://forums.freebsd.org/threads/boot-hangs-after-cpu-upgrade.64410/ So far, I tried (unsuccessfully) to disable obvious ACPI sub- systems (cpu, mwait, quirks) and debug settings (acpi.cpu_unordered, acpi.max_threads). Anyone got a hint where to look or debug this further? kernel boot messages (obtained from 10.4 amd64): https://lair.griffinsplace.de/~sascha/phenom/dmesg-freeze-FreeBSD10.txt boot messages with the previous Athlon II cpu in this system: https://lair.griffinsplace.de/~sascha/phenom/dmesg-FreeBSD-AthlonII.txt boot messages from DFly, OpenBSD and Linux: https://lair.griffinsplace.de/~sascha/phenom/ Cheers, -sascha ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
