Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

[Nick Wolff]

Sorry boot is broken from harddrive or iso(as cdrom) for some users(at
least 3) since somewhere in the revisions listed above and that still
stands as of the Head snapshot of 072519. Sorry for lack of clarity. There
was a thread under Problem with USB after r349133 but I decided to rename
it to try to catch more people's eyes/get more reports in if people run
into the issue. Don't think or at least know for sure USB is the problem as
when you bypass the waiting for USB you get a different hang farther into
system booting.

I will try to bisect the build in that magic revision range once I figure
out on what system as it's my primary builder that's having this issue. Not
that I have a lack of hardware I guess just time to setup something else.




On Mon, Jul 29, 2019, 21:45 Clay Daniels Jr. 
wrote:

> Rodney, you are right that the .iso "should work", and a lot of other
> projects, from Microsoft Windows 10 to Trident BSD only a furnish an iso,
> and no img file. FreeBSD is one of the few that give you both choices. The
> problem goes deeper than any one operating system. If you've ever used the
> Rufus tool to make a bootable usb, which is all Rufus does, you may have
> come across problems with "mount root". I found this article, answered by a
> Rufus developer very enlightening.
>
> https://superuser.com/questions/1170832/why-are-there-different-options-for-creating-bootable-usb-compared-to-a-cd
>
> I have a collection of usb thumbdrives here at my desk, and use them a
> lot, but I also bought me some blank dvd disks and use them too.
>
> But I think you are right, Nick Wolff's problem may be a a bug to be
> reported. All I know is I took the same file,
> FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso
> 
> , burned it to a dvd, and I'm now writing this email from the FreeBSD
> 13.0-CURRENT r350322 partition of my computer.
>
> Clay
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

[Clay Daniels Jr.]

Rodney, you are right that the .iso "should work", and a lot of other
projects, from Microsoft Windows 10 to Trident BSD only a furnish an iso,
and no img file. FreeBSD is one of the few that give you both choices. The
problem goes deeper than any one operating system. If you've ever used the
Rufus tool to make a bootable usb, which is all Rufus does, you may have
come across problems with "mount root". I found this article, answered by a
Rufus developer very enlightening.
https://superuser.com/questions/1170832/why-are-there-different-options-for-creating-bootable-usb-compared-to-a-cd

I have a collection of usb thumbdrives here at my desk, and use them a lot,
but I also bought me some blank dvd disks and use them too.

But I think you are right, Nick Wolff's problem may be a a bug to be
reported. All I know is I took the same file,
FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso

, burned it to a dvd, and I'm now writing this email from the FreeBSD
13.0-CURRENT r350322 partition of my computer.

Clay
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

[Rodney W. Grimes]

> The .iso files are for a dvd install. If you want to use a usb, download
> the .img files.
> 
> FreeBSD-13.0-CURRENT-amd64-20190725-r350322-memstick.img
> 

The FreeBSD projects amd64 .iso images are hybrid now,
they should work both as a memstick image and as a burned .iso.

IFF this is failing it is a bug and should be addressed.

file FreeBSD-13.0-CURRENT-amd64-20181213-r342020-disc1.iso
FreeBSD-13.0-CURRENT-amd64-20181213-r342020-disc1.iso: DOS/MBR boot sector; 
partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 
1, 1758779 sectors

file FreeBSD-12.0-CURRENT-amd64-20171206-r326622-disc1.iso
FreeBSD-12.0-CURRENT-amd64-20171206-r326622-disc1.iso: ISO 9660 CD-ROM 
filesystem data '12_0_CURRENT_AMD64_CD' (bootable)


> ( or get the .xz version and extract it on your machine - it's smaller)
> 
> This "mount root" problem got me too, so don't feel alone.
> 
> Clay
> clay@fbsd13:~ $ uname -a
> FreeBSD fbsd13 13.0-CURRENT FreeBSD 13.0-CURRENT r350322 GENERIC  amd64
> 
> 
> On Mon, Jul 29, 2019 at 4:03 PM Nick Wolff  wrote:
> 
> > I just tested the snapshot from 20190725 and still am getting the root
> > mount rating for "boot on boot. I think something deeper broke between
> > r349133 and r349160 because even when I turn off wait for Root Mount on usb
> > root via a loader variable boot just get's stuck later on in the process.
> >
> > This is all happening on an x11-dpi-nt board.
> >
> >
> > http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso
> >
> > On Mon, Jul 22, 2019 at 12:57 PM Nick Wolff 
> > wrote:
> >
> > > Hans,
> > >
> > > I'm building r350003  at the moment which is after the acpi change was
> > > moved into an unloaded module.
> > >
> > >
> > >
> > > On Mon, Jul 22, 2019 at 12:13 PM Hans Petter Selasky 
> > > wrote:
> > >
> > >> On 2019-07-22 17:23, Nick Wolff wrote:
> > >> > Sorry for email spam but I was wrong. Just gets stuck now during
> > >> reproping
> > >> > a pci device after init happens(this is actually a trueos build which
> > is
> > >> > why you see openrc). That device it's getting stuck on is "Sky Lake-E
> > >> CBDMA
> > >> > Registers" which shouldn't have a driver attached.
> > >> >
> > >>
> > https://drive.google.com/file/d/19NFI0Dcupu3ZcVxbcr2vYFZ-iDqiIzkx/view?usp=sharing
> > >> >
> > >> > Though it maybe something else getting stuck at this point and that
> > just
> > >> > happens to be the last thing on the screen.
> > >> >
> > >>
> > >> There was a recent change to add an ACPI wrapper for the USB HUB driver,
> > >> but that was a bit premature and introduced some bugs. For now the ACPI
> > >> USB HUB wrapper is not enabled by default. Do you experience issues with
> > >> the latest -current ?
> > >>
> > >> --HPS
> > >>
> > >>
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> >
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 

-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

[Clay Daniels Jr.]

The .iso files are for a dvd install. If you want to use a usb, download
the .img files.

FreeBSD-13.0-CURRENT-amd64-20190725-r350322-memstick.img


( or get the .xz version and extract it on your machine - it's smaller)

This "mount root" problem got me too, so don't feel alone.

Clay
clay@fbsd13:~ $ uname -a
FreeBSD fbsd13 13.0-CURRENT FreeBSD 13.0-CURRENT r350322 GENERIC  amd64


On Mon, Jul 29, 2019 at 4:03 PM Nick Wolff  wrote:

> I just tested the snapshot from 20190725 and still am getting the root
> mount rating for "boot on boot. I think something deeper broke between
> r349133 and r349160 because even when I turn off wait for Root Mount on usb
> root via a loader variable boot just get's stuck later on in the process.
>
> This is all happening on an x11-dpi-nt board.
>
>
> http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso
>
> On Mon, Jul 22, 2019 at 12:57 PM Nick Wolff 
> wrote:
>
> > Hans,
> >
> > I'm building r350003  at the moment which is after the acpi change was
> > moved into an unloaded module.
> >
> >
> >
> > On Mon, Jul 22, 2019 at 12:13 PM Hans Petter Selasky 
> > wrote:
> >
> >> On 2019-07-22 17:23, Nick Wolff wrote:
> >> > Sorry for email spam but I was wrong. Just gets stuck now during
> >> reproping
> >> > a pci device after init happens(this is actually a trueos build which
> is
> >> > why you see openrc). That device it's getting stuck on is "Sky Lake-E
> >> CBDMA
> >> > Registers" which shouldn't have a driver attached.
> >> >
> >>
> https://drive.google.com/file/d/19NFI0Dcupu3ZcVxbcr2vYFZ-iDqiIzkx/view?usp=sharing
> >> >
> >> > Though it maybe something else getting stuck at this point and that
> just
> >> > happens to be the last thing on the screen.
> >> >
> >>
> >> There was a recent change to add an ACPI wrapper for the USB HUB driver,
> >> but that was a bit premature and introduced some bugs. For now the ACPI
> >> USB HUB wrapper is not enabled by default. Do you experience issues with
> >> the latest -current ?
> >>
> >> --HPS
> >>
> >>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

[Nick Wolff]

I just tested the snapshot from 20190725 and still am getting the root
mount rating for "boot on boot. I think something deeper broke between
r349133 and r349160 because even when I turn off wait for Root Mount on usb
root via a loader variable boot just get's stuck later on in the process.

This is all happening on an x11-dpi-nt board.

http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso

On Mon, Jul 22, 2019 at 12:57 PM Nick Wolff  wrote:

> Hans,
>
> I'm building r350003  at the moment which is after the acpi change was
> moved into an unloaded module.
>
>
>
> On Mon, Jul 22, 2019 at 12:13 PM Hans Petter Selasky 
> wrote:
>
>> On 2019-07-22 17:23, Nick Wolff wrote:
>> > Sorry for email spam but I was wrong. Just gets stuck now during
>> reproping
>> > a pci device after init happens(this is actually a trueos build which is
>> > why you see openrc). That device it's getting stuck on is "Sky Lake-E
>> CBDMA
>> > Registers" which shouldn't have a driver attached.
>> >
>> https://drive.google.com/file/d/19NFI0Dcupu3ZcVxbcr2vYFZ-iDqiIzkx/view?usp=sharing
>> >
>> > Though it maybe something else getting stuck at this point and that just
>> > happens to be the last thing on the screen.
>> >
>>
>> There was a recent change to add an ACPI wrapper for the USB HUB driver,
>> but that was a bit premature and introduced some bugs. For now the ACPI
>> USB HUB wrapper is not enabled by default. Do you experience issues with
>> the latest -current ?
>>
>> --HPS
>>
>>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: kgdb assert while loading a kernel core

[Cy Schubert]

In message 
, Weike
.c...@dell.com writes:
>  Hi all,
>
>  I try to do some debugging for the FreeBSD kernel crash.
>  My system is FreeBSD 12. And I have a kernel core file, and while I load it 
> by kgdb. It reports the following error:
>
>  Inferior.c: 287: internal-error: struct inferior *find_inferior_pid(int): As
> sertion 'pid != 0' failed.
>
>  And I also try the gdb in ports/devel, and got the same error.
>
>  Any workaround for the error?

Which kgdb are you using? The /usr/libexec one or the port?


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

kgdb assert while loading a kernel core

[Weike.Chen]

 Hi all,

 I try to do some debugging for the FreeBSD kernel crash.
 My system is FreeBSD 12. And I have a kernel core file, and while I load it by 
kgdb. It reports the following error:

 Inferior.c: 287: internal-error: struct inferior *find_inferior_pid(int): 
Assertion 'pid != 0' failed.

 And I also try the gdb in ports/devel, and got the same error.

 Any workaround for the error?

 Thanks!

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485

[Rozhuk Ivan]

On Sat, 20 Jul 2019 00:54:47 +0200
Evilham  wrote:


> Minor glitches:
> - xbacklight doesn't work, neither does intel-backlight because 
>   it's AMD
> - Speakers don't appear to work, audio input/output on 3.5 jack 
>   does.
> - SD card reader doesn't work (Bounty for 125 USD: 
>   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521)

I have Asus 505 and backlight not work too (try via xfce4-power-manager).

I dig into it and found that problem somewhere in ACPI code.

1. It does not proper export some functions and FreeBSD
ACPI + xfce4-power-manager cant detect support this feature.
I hack kernel:
Index: /usr/src/sys/dev/acpica/acpi_video.c
===
--- /usr/src/sys/dev/acpica/acpi_video.c(revision 350398)
+++ /usr/src/sys/dev/acpica/acpi_video.c(working copy)
@@ -1053,8 +1053,12 @@
dcs = 0;
status = acpi_GetInteger(handle, "_DCS", );
if (ACPI_FAILURE(status))
-   printf("can't evaluate %s._DCS - %s\n",
-  acpi_name(handle), AcpiFormatException(status));
+   status = acpi_GetInteger(handle, "_STA", );
+   if (ACPI_FAILURE(status)) {
+   /* Assume that device OK by default. */
+   dcs = (DCS_EXISTS | DCS_ACTIVE | DCS_READY |
+   DCS_FUNCTIONAL | DCS_ATTACHED);
+   }
 
return (dcs);
 }
and now acpi/xfce4-power-manager show that feature supported but
it does not work.
(later I can move this hack into ACPI ASL code that load into bios, but it 
harder to maintain)

2. I dig more depper and decompile acpi code via isl.
There is a mess.
I found that function that set backlight level check some mem/register
value before write new backlight value.
I fail to found place where this value changed.
I try rewrite code to remove this check and recompile ACPI and load new
version witout this check on FreeBSD boot, it loaded but backlight still
not work.

Also I set in loader.conf:
hw.acpi.osname="Windows 2015"   # Some systems' ASL may have problems because 
they look for names of Microsoft operating systems.
because there is at least 4 different places in decompiled ACPI
where OS version and name checked - not help with blackligth, but as I see
this unblock some features/devices.


Also i2c touchpad dont work.
https://reviews.freebsd.org/D16698
not help.


For speakers probably wrong snddev set.
Try change hw.snd.default_unit.


> WARNING !drm_modeset_is_locked(>mutex) failed at 
> /wrkdirs/usr/ports/graphics/drm-fbsd12.0-kmod/work/kms-drm-6365030/drivers/gpu/drm/drm_atomic_helper.c:821
> [Multiple times...]
> kernel trap 22 with interrupts disabled
> kernel trap 22 with interrupts 
> disabled
> kernel trap 22 with interrupts disabled
> kernel trap 22 with interrupts disabled
> panic: spin lock held too long

I have another issue with amdgpu:
after lid closed and open again video freezes to few seconds every 10 seconds.
Switch to scfb xorg driver to fix it, but get small tearing on video playback.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"