Re: loading vmm.ko crashes main-n267684-e4b646ce1610

On Thu, Jan 25, 2024 at 03:34:54PM +0800, Zhenlei Huang wrote: You may want to configure the dump device before get the coredump. See https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-obtain

Re: loading vmm.ko crashes main-n267684-e4b646ce1610

> On Jan 24, 2024, at 8:47 AM, void wrote: > > Hello, > > Loading vmm either via vmm_load=YES in /boot/loader.conf or > manually via kldload vmm crashes the system to db> prompt > as shown in the link below: > > http://void.f-m.fm.user.fm/Screenshot_20240122_13

loading vmm.ko crashes main-n267684-e4b646ce1610

Hello, Loading vmm either via vmm_load=YES in /boot/loader.conf or manually via kldload vmm crashes the system to db> prompt as shown in the link below: http://void.f-m.fm.user.fm/Screenshot_20240122_135539.png Thing is, access is via a html5 console with no up/down scrolling or buffer. Noth

Re: vmm_load crashes to debugger early

Hi, On Mon, 22 Jan 2024, at 12:48, Ronald Klop wrote: > Hi, > > Can you mount /boot on another system? not sure how as the system cannot find the pool called 'zroot'. There are two zpools on the server - zroot for HD and 'ssd' for the ssds. I can boot to -current usb stick and zpool import -f ss

Re: vmm_load crashes to debugger early

w" to see what modules are already loaded and what variables are used while booting. I hope this helps. Regards, Ronald. Van: void Datum: maandag, 22 januari 2024 12:46 Aan: freebsd-current@freebsd.org CC: freebsd-virtualizat...@freebsd.org Onderwerp: vmm_load crashes to debugger early H

vmm_load crashes to debugger early

Hello, On a very recent -current, vmm_load="YES" in /boot/loader.conf crashes the system to debugger early on in the boot sequence. I can't even reach single user mode How can I prevent this one element of /boot/loader.conf from loading? thanks in advance for any advice --

Re: bootstrap loader crashes, BTX halted

On Sun, Aug 14, 2022, 2:12 PM Toomas Soome wrote: > > > > On 14. Aug 2022, at 23:08, Jens Schweikhardt > wrote: > > > > I just installed the latest current on a gpt zfs system and it crashes > early > > with (manually transferred from photo taken): >

Re: bootstrap loader crashes, BTX halted

> On 14. Aug 2022, at 23:08, Jens Schweikhardt > wrote: > > I just installed the latest current on a gpt zfs system and it crashes early > with (manually transferred from photo taken): > > Consoles: internal video/keyboard > BIOS drive C: is disk0 > BIOS 634kB

bootstrap loader crashes, BTX halted

I just installed the latest current on a gpt zfs system and it crashes early with (manually transferred from photo taken): Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 634kB/3090148kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 int=000d err=b844 efl

FW: pciconf -lbvV crashes kernel main-8d72c409c - 2022-02-07

Hi: Here are the kernel.full files some of you asked for. Let me know what else may be helpful to test. Thanks! Michael Jung Notes below * (UPDATED) * Started fresh Installed FreeBSD-14.0-CURRENT-amd64-20220113-0910a41ef3b-252413-disc1.iso with its accompany source tree. Built kernel

Re: pciconf -lbvV crashes kernel main-8d72c409c

Am 06.02.22 um 01:19 schrieb Michael Jung: > Dump header from device: /dev/ada0p2 > Architecture: amd64 > Architecture Version: 2 > Dump Length: 900231168 > Blocksize: 512 > Compression: none > Dumptime: 2022-02-04 15:48:08 -0500 > Hostname: draid.mikej.com > Magic: FreeBSD Kernel Dump > Version St

Re: pciconf -lbvV crashes kernel main-8d72c409c

On Sun, Feb 06, 2022 at 12:19:59AM +, Michael Jung wrote: > Dump header from device: /dev/ada0p2 > Architecture: amd64 > Architecture Version: 2 > As a reality check, I just tried the "pciconf -lbvV" command on my newer laptop, which was running: FreeBSD g1-48.catwhisker.org 14.0-CUR

pciconf -lbvV crashes kernel main-8d72c409c

Dump header from device: /dev/ada0p2 Architecture: amd64 Architecture Version: 2 Dump Length: 900231168 Blocksize: 512 Compression: none Dumptime: 2022-02-04 15:48:08 -0500 Hostname: draid.mikej.com Magic: FreeBSD Kernel Dump Version String: FreeBSD 14.0-CURRENT #1 main-8d72c409c:

Re: My -CURRENT crashes....

On Mon, Dec 27, 2021 at 09:15:53PM +0200, Konstantin Belousov wrote: > On Mon, Dec 27, 2021 at 10:58:02AM -0800, Gleb Smirnoff wrote: > > On Mon, Dec 27, 2021 at 01:43:01PM -0500, Alexander Motin wrote: > > A> > This allows us to deduct that the callout belongs to proc subsystem and > > A> > we can

Re: My -CURRENT crashes....

On Mon, Dec 27, 2021 at 10:58:02AM -0800, Gleb Smirnoff wrote: > On Mon, Dec 27, 2021 at 01:43:01PM -0500, Alexander Motin wrote: > A> > This allows us to deduct that the callout belongs to proc subsystem and > A> > we can retrieve the proc it points to: c_lock - 0x128 = > 0xf8030521e548 > A>

Re: My -CURRENT crashes....

On Mon, Dec 27, 2021 at 01:43:01PM -0500, Alexander Motin wrote: A> > This allows us to deduct that the callout belongs to proc subsystem and A> > we can retrieve the proc it points to: c_lock - 0x128 = 0xf8030521e548 A> > It is ccache in PRS_NORMAL state. And the "tmp" in our stack frame is it

Re: My -CURRENT crashes....

On 27.12.2021 12:31, Gleb Smirnoff wrote: > On Fri, Dec 17, 2021 at 01:27:11PM -0600, Larry Rosenman wrote: > L> Can someone look at the messages I posted to -CURRENT, most recent > L> today, with random > L> Callout(?) crashes after long (>6 hour) poudriere runs?

Re: My -CURRENT crashes....

On Fri, Dec 17, 2021 at 01:27:11PM -0600, Larry Rosenman wrote: L> Can someone look at the messages I posted to -CURRENT, most recent L> today, with random L> Callout(?) crashes after long (>6 hour) poudriere runs? L> L> I have core's available. I asked Larry to obtain

Re: main changed DIALOG_STATE, DIALOG_VARS, and DIALOG_COLORS but /usr/lib/libdialog.so.? naming was not adjusted? (crashes in releng/13 programs on main [so: 14] can result)

On Fri, Oct 22, 2021 at 04:11:56PM +, Baptiste Daroussin wrote: > > 22 oct. 2021 18:06:56 John Baldwin : > > > On 10/22/21 1:08 AM, Mark Millard via freebsd-current wrote: > >> main [soi: 14] commit a96ef450 (2021-02-26 09:16:49 +) > >> changed DIALOG_STATE, DIALOG_VARS, and DIALOG_COLORS

Re: main changed DIALOG_STATE, DIALOG_VARS, and DIALOG_COLORS but /usr/lib/libdialog.so.? naming was not adjusted? (crashes in releng/13 programs on main [so: 14] can result)

22 oct. 2021 18:06:56 John Baldwin : > On 10/22/21 1:08 AM, Mark Millard via freebsd-current wrote: >> main [soi: 14] commit a96ef450 (2021-02-26 09:16:49 +) >> changed DIALOG_STATE, DIALOG_VARS, and DIALOG_COLORS . >> These are publicly exposed in (ones that I noticed): >> /usr/include/dial

Re: main changed DIALOG_STATE, DIALOG_VARS, and DIALOG_COLORS but /usr/lib/libdialog.so.? naming was not adjusted? (crashes in releng/13 programs on main [so: 14] can result)

On 10/22/21 1:08 AM, Mark Millard via freebsd-current wrote: main [soi: 14] commit a96ef450 (2021-02-26 09:16:49 +) changed DIALOG_STATE, DIALOG_VARS, and DIALOG_COLORS . These are publicly exposed in (ones that I noticed): /usr/include/dialog.h:extern DIALOG_STATE dialog_state; /usr/include

main changed DIALOG_STATE, DIALOG_VARS, and DIALOG_COLORS but /usr/lib/libdialog.so.? naming was not adjusted? (crashes in releng/13 programs on main [so: 14] can result)

e the changes, there by not matching old programs built under releng/13.0 or stable/13 . Turns out that this explains the crashes I get when I attempt to use a releng/13 based dialog4ports under main [so: 14]. For a particular example, see: https://lists.freebsd.org/archives/freebsd-current/2021-Oc

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/15/21 10:31 PM, Adrian Chadd wrote: Hi! So, my Lenovo T540p also doesn't work right now; it just panics the kernel with a NULL pointer deref inside some deferred interrupt registration / callback thing. I move the taskqueue calls as you advice. Can you try the last version from GitHub (2

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

Hi! So, my Lenovo T540p also doesn't work right now; it just panics the kernel with a NULL pointer deref inside some deferred interrupt registration / callback thing. If I disable it at the boot console then it's fine. -adrian ___ freebsd-current@fr

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Fri, 14 May 2021 17:05:26 +0200 Marc Veldman wrote: > > On 14 May 2021, at 16:48, Gary Jennejohn wrote: > > > > On Fri, 14 May 2021 16:21:05 +0200 > > Marc Veldman wrote: > > > >>> On 14 May 2021, at 10:22, Henri Hennebert wrote: > >>> > >>> > >>> Please test the 2.0h version from Git

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Fri, May 14, 2021, 11:03 AM Marc Veldman wrote: > > > > On 14 May 2021, at 17:29, Henri Hennebert wrote: > > > > On 5/14/21 5:05 PM, Marc Veldman wrote: > >>> On 14 May 2021, at 16:48, Gary Jennejohn wrote: > >>> > >>> On Fri, 14 May 2021 16:21:05 +0200 > >>> Marc Veldman wrote: > >>> > >>>

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

> On 14 May 2021, at 17:29, Henri Hennebert wrote: > > On 5/14/21 5:05 PM, Marc Veldman wrote: >>> On 14 May 2021, at 16:48, Gary Jennejohn wrote: >>> >>> On Fri, 14 May 2021 16:21:05 +0200 >>> Marc Veldman wrote: >>> > On 14 May 2021, at 10:22, Henri Hennebert wrote: > > >>

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/14/21 5:05 PM, Marc Veldman wrote: On 14 May 2021, at 16:48, Gary Jennejohn wrote: On Fri, 14 May 2021 16:21:05 +0200 Marc Veldman wrote: On 14 May 2021, at 10:22, Henri Hennebert wrote: Please test the 2.0h version from GitHub. On my Lenovo P50s: Cold boot with card not insert

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 13/05/2021 16:09, Lev Serebryakov wrote:  It doesn't panic, boots and works more than 500 seconds :-) The Power To Serve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send a

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 14.05.2021 18:05, Marc Veldman wrote: I removed the flag, and it works now.Thanks! What is it in the trace that indicated that the inversion flag is not needed? THIS: Insert card after boot, no crash, but the message seems weird: May 14 16:01:27 supernovo kernel: rtsx0: Interrupt card i

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

> On 14 May 2021, at 16:48, Gary Jennejohn wrote: > > On Fri, 14 May 2021 16:21:05 +0200 > Marc Veldman wrote: > >>> On 14 May 2021, at 10:22, Henri Hennebert wrote: >>> >>> >>> Please test the 2.0h version from GitHub. >>> >> >> On my Lenovo P50s: >> >> Cold boot with card not inserted

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Fri, 14 May 2021 16:21:05 +0200 Marc Veldman wrote: > > On 14 May 2021, at 10:22, Henri Hennebert wrote: > > > > > > Please test the 2.0h version from GitHub. > > > > On my Lenovo P50s: > > Cold boot with card not inserted: OK > Insert card after boot, no crash, but the message > seems

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

> On 14 May 2021, at 10:22, Henri Hennebert wrote: > > > Please test the 2.0h version from GitHub. > On my Lenovo P50s: Cold boot with card not inserted: OK Insert card after boot, no crash, but the message seems weird: May 14 16:01:27 supernovo kernel: rtsx0: Interrupt card inserted/remo

Re: More rtsx issues (13.0-R system) was: Re: CURRENT crashes at early boot on Lenovo T540p...

> On 5/13/21 9:00 PM, Rodney W. Grimes wrote: > >> On 12.05.2021 21:01, Marc Veldman wrote: > >> > >>> I?m not sure if this is an interesting data point or not, > >>> but a warm boot without the card inserted succeeds after > >>> a cold boot with the card inserted. > >> > >>It could explain, wh

Re: More rtsx issues (13.0-R system) was: Re: CURRENT crashes at early boot on Lenovo T540p...

On 5/13/21 9:00 PM, Rodney W. Grimes wrote: On 12.05.2021 21:01, Marc Veldman wrote: I?m not sure if this is an interesting data point or not, but a warm boot without the card inserted succeeds after a cold boot with the card inserted. It could explain, why my tests with "same code path" g

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 14.05.2021 11:22, Henri Hennebert wrote: Please test the 2.0h version from GitHub. Cold Boot with card: OK Card removal after boot: OK Cold Boot without card:OK Card insertion after boot: OK It is with 14-CURRENT n246524-95a74ab4fb0 -- // Lev Serebryakov _

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 7:55 PM, Lev Serebryakov wrote: On 13.05.2021 18:56, Henri Hennebert wrote: So if I understand correctly, your problem is solved.  Stupid me. I didn't check card insertion/removal after boot. Card REMOVAL when boot was WITH CARD:  Instant panic: rtsx0: Interrupt card inserted/re

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 7:25 PM, Marc Veldman wrote: On 13 May 2021, at 17:56, Henri Hennebert wrote: On 5/13/21 5:51 PM, Lev Serebryakov wrote: On 13.05.2021 18:38, Henri Hennebert via freebsd-current wrote: This seems a good news. Can you replace sys/dev/rtsx.c by the latest version (2.0g) from http

More rtsx issues (13.0-R system) was: Re: CURRENT crashes at early boot on Lenovo T540p...

> On 12.05.2021 21:01, Marc Veldman wrote: > > > I?m not sure if this is an interesting data point or not, > > but a warm boot without the card inserted succeeds after > > a cold boot with the card inserted. > > It could explain, why my tests with "same code path" gave different results! I am

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Thu, 13 May 2021 20:55:20 +0300 Lev Serebryakov wrote: > On 13.05.2021 18:56, Henri Hennebert wrote: > > > So if I understand correctly, your problem is solved. > Stupid me. I didn't check card insertion/removal after boot. > > Card REMOVAL when boot was WITH CARD: > Instant panic: >

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 13.05.2021 18:56, Henri Hennebert wrote: So if I understand correctly, your problem is solved. Stupid me. I didn't check card insertion/removal after boot. Card REMOVAL when boot was WITH CARD: Instant panic: rtsx0: Interrupt card inserted/removed rtsx0: Card absent panic: mutex Giant no

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

> On 13 May 2021, at 17:56, Henri Hennebert wrote: > > On 5/13/21 5:51 PM, Lev Serebryakov wrote: >> On 13.05.2021 18:38, Henri Hennebert via freebsd-current wrote: >>> This seems a good news. >>> >>> Can you replace sys/dev/rtsx.c by the latest version (2.0g) from >>> https://github.com/hlh-r

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 5:51 PM, Lev Serebryakov wrote: On 13.05.2021 18:38, Henri Hennebert via freebsd-current wrote: This seems a good news. Can you replace sys/dev/rtsx.c by the latest version (2.0g) from https://github.com/hlh-restart/rtsx I reduce the DELAY to 25 and make some other updates wait

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 13.05.2021 18:38, Henri Hennebert via freebsd-current wrote: This seems a good news. Can you replace sys/dev/rtsx.c by the latest version (2.0g) from https://github.com/hlh-restart/rtsx I reduce the DELAY to 25 and make some other updates waiting in the pipeline. I've replaced two fil

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 5:09 PM, Lev Serebryakov wrote: On 13.05.2021 17:22, Henri Hennebert wrote: try to rebuild your kernel with the attached patch.   Nope, same panic after cold (power-cycle) boot. Can you try with "DELAY(50);" to see if this is a path to dig further.   It helps with panic!

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 2021-05-13 02:49, Henri Hennebert via freebsd-current wrote: On 5/13/21 6:00 AM, Marc Veldman wrote: On 12 May 2021, at 20:49, Henri Hennebert wrote: On 5/12/21 8:01 PM, Marc Veldman wrote: On 12 May 2021, at 18:06, Henri Hennebert wrote: On 5/12/21 5:04 PM, Marc Veldman wrote: Unfortu

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 13.05.2021 17:22, Henri Hennebert wrote: try to rebuild your kernel with the attached patch.   Nope, same panic after cold (power-cycle) boot. Can you try with "DELAY(50);" to see if this is a path to dig further.   It helps with panic! What do you mean? Does it display "card pres

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 4:18 PM, Lev Serebryakov wrote: On 13.05.2021 16:40, Henri Hennebert wrote: try to rebuild your kernel with the attached patch.   Nope, same panic after cold (power-cycle) boot. Can you try with "DELAY(50);" to see if this is a path to dig further.  It helps with panic!

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 13.05.2021 16:40, Henri Hennebert wrote: try to rebuild your kernel with the attached patch.   Nope, same panic after cold (power-cycle) boot. Can you try with "DELAY(50);" to see if this is a path to dig further. It helps with panic! -- // Lev Serebryakov

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 3:30 PM, Lev Serebryakov wrote: On 13.05.2021 15:48, Henri Hennebert via freebsd-current wrote: rtsx0: <2.0c .> rtsx0: Card present mmc0: on rtsx0 rtsx0: Interrupt card inserted/removed rtsx0: Card absent ... This must be the culprit this change from present/absent PANIC! (wi

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 13.05.2021 15:48, Henri Hennebert via freebsd-current wrote: rtsx0: <2.0c .> rtsx0: Card present mmc0: on rtsx0 rtsx0: Interrupt card inserted/removed rtsx0: Card absent ... This must be the culprit this change from present/absent PANIC! (without rtsx0 in stacktrace, again it is run

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 2:40 PM, Lev Serebryakov wrote: On 13.05.2021 15:13, Henri Hennebert via freebsd-current wrote: I’m not sure if this is an interesting data point or not, but a warm boot without the card inserted succeeds after a cold boot with the card inserted.   It could explain, why my tests

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 13.05.2021 15:13, Henri Hennebert via freebsd-current wrote: I’m not sure if this is an interesting data point or not, but a warm boot without the card inserted succeeds after a cold boot with the card inserted.   It could explain, why my tests with "same code path" gave different results!

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

It could explain, why in my case it crashes in different threads. And sometimes in strlen() in stacktrace which contains rtsx functions! -- // Lev Serebryakov ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freeb

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 2:01 PM, Lev Serebryakov wrote: On 13.05.2021 14:35, Henri Hennebert wrote: I’m not sure if this is an interesting data point or not, but a warm boot without the card inserted succeeds after a cold boot with the card inserted.   It could explain, why my tests with "same code path"

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 1:58 PM, Marc Veldman wrote: On 13 May 2021, at 11:49, Henri Hennebert wrote: ... ... Do you see an rtsx message before this mmc0 ? mmc0: detached ugen0.1: <0x8086 Yes. rtsx0: <2.0c Realtek RT5522A PCI MMC/SD Card reader mem 0xf410-0xf4100fff at device 0.0 on pci1> rtsx0

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 13.05.2021 14:35, Henri Hennebert wrote: I’m not sure if this is an interesting data point or not, but a warm boot without the card inserted succeeds after a cold boot with the card inserted.   It could explain, why my tests with "same code path" gave different results! With a "cold" boot

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

> On 13 May 2021, at 11:49, Henri Hennebert wrote: > ... ... >>> Do you see an rtsx message before this mmc0 ? >>> mmc0: detached ugen0.1: <0x8086 >> Yes. >> rtsx0: <2.0c Realtek RT5522A PCI MMC/SD Card reader mem >> 0xf410-0xf4100fff at device 0.0 on pci1> >> rtsx0: Card prese

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 1:31 PM, Lev Serebryakov wrote: On 12.05.2021 21:01, Marc Veldman wrote: I’m not sure if this is an interesting data point or not, but a warm boot without the card inserted succeeds after a cold boot with the card inserted.  It could explain, why my tests with "same code path" gav

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 12.05.2021 21:01, Marc Veldman wrote: I’m not sure if this is an interesting data point or not, but a warm boot without the card inserted succeeds after a cold boot with the card inserted. It could explain, why my tests with "same code path" gave different results! -- // Lev Serebryakov _

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/13/21 6:00 AM, Marc Veldman wrote: On 12 May 2021, at 20:49, Henri Hennebert wrote: On 5/12/21 8:01 PM, Marc Veldman wrote: On 12 May 2021, at 18:06, Henri Hennebert wrote: On 5/12/21 5:04 PM, Marc Veldman wrote: Unfortunately I can only say “me too”, but on a different Lenovo laptop

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

> On 12 May 2021, at 20:49, Henri Hennebert wrote: > > On 5/12/21 8:01 PM, Marc Veldman wrote: >>> On 12 May 2021, at 18:06, Henri Hennebert wrote: >>> >>> On 5/12/21 5:04 PM, Marc Veldman wrote: Unfortunately I can only say “me too”, but on a different Lenovo laptop. I’ve put my dia

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/12/21 8:01 PM, Marc Veldman wrote: On 12 May 2021, at 18:06, Henri Hennebert wrote: On 5/12/21 5:04 PM, Marc Veldman wrote: Unfortunately I can only say “me too”, but on a different Lenovo laptop. I’ve put my diagnostics in this thread, with the SVN revision in which it seems to have

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

> On 12 May 2021, at 18:06, Henri Hennebert wrote: > > On 5/12/21 5:04 PM, Marc Veldman wrote: >> Unfortunately I can only say “me too”, but on a different Lenovo laptop. >> I’ve put my diagnostics in this thread, with the SVN revision in which it >> seems to have broken. >> https://docs.freeb

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

> On 12 May 2021, at 17:46, Henri Hennebert wrote: > > On 5/12/21 5:04 PM, Marc Veldman wrote: >> Unfortunately I can only say “me too”, but on a different Lenovo laptop. >> I’ve put my diagnostics in this thread, with the SVN revision in which it >> seems to have broken. >> https://docs.freeb

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/12/21 5:04 PM, Marc Veldman wrote: Unfortunately I can only say “me too”, but on a different Lenovo laptop. I’ve put my diagnostics in this thread, with the SVN revision in which it seems to have broken. https://docs.freebsd.org/cgi/getmsg.cgi?fetch=327822+0+archive/2020/freebsd-current/2

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/12/21 5:04 PM, Marc Veldman wrote: Unfortunately I can only say “me too”, but on a different Lenovo laptop. I’ve put my diagnostics in this thread, with the SVN revision in which it seems to have broken. https://docs.freebsd.org/cgi/getmsg.cgi?fetch=327822+0+archive/2020/freebsd-current/2

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 12.05.2021 16:35, Henri Hennebert wrote: It would be fine if you can test the driver with dev.rtsx.0.inversion=1 in loader.conf and see it it solve the problem. the output of sysctl dev.rtsx  and kenv | grep smbios.system would be useful BTW is a dummy card inserted in the SD slot? Thank f

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

Unfortunately I can only say “me too”, but on a different Lenovo laptop. I’ve put my diagnostics in this thread, with the SVN revision in which it seems to have broken. https://docs.freebsd.org/cgi/getmsg.cgi?fetch=327822+0+archive/2020/freebsd-current/20201227.freebsd-current I’m willing to h

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Wed, 12 May 2021 16:44:59 +0300 Lev Serebryakov wrote: > On 12.05.2021 16:34, Gary Jennejohn wrote: > > > Is sysctl debug.debugger_on_panic set to 1? You should automatically > > land in ddb if that is set. I suppose it is, since you posted some > > back trace in an earlier mail. It also s

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 12.05.2021 16:34, Gary Jennejohn wrote: Is sysctl debug.debugger_on_panic set to 1? You should automatically land in ddb if that is set. I suppose it is, since you posted some back trace in an earlier mail. It also seems to be the default, at least in my FreeBSD-14 kernel. I see ddb rep

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/12/21 2:46 PM, Lev Serebryakov wrote: On 12.05.2021 13:01, Henri Hennebert via freebsd-current wrote: It would be fine if you can test the driver with dev.rtsx.0.inversion=1 in loader.conf and see it it solve the problem. the output of sysctl dev.rtsx  and kenv | grep smbios.system would

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Wed, 12 May 2021 15:46:24 +0300 Lev Serebryakov wrote: > On 12.05.2021 13:01, Henri Hennebert via freebsd-current wrote: > > > It would be fine if you can test the driver with dev.rtsx.0.inversion=1 in > > loader.conf and see it it solve the problem. > > the output of > > sysctl dev.rtsx and

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 12.05.2021 13:01, Henri Hennebert via freebsd-current wrote: It would be fine if you can test the driver with dev.rtsx.0.inversion=1 in loader.conf and see it it solve the problem. the output of sysctl dev.rtsx  and kenv | grep smbios.system would be useful BTW is a dummy card inserted in t

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/12/21 11:27 AM, Sergey V. Dyatko wrote: On Fri, 7 May 2021 18:53:03 +0300 Gleb Popov wrote: Just to add to this thread: I'm running CURRENT with rtsx device and driver and it works fine for me. I had to remove (nodevice rtsx) from GENERIC because of slw OS boot, it is trying to pro

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Fri, 7 May 2021 18:53:03 +0300 Gleb Popov wrote: > Just to add to this thread: > > I'm running CURRENT with rtsx device and driver and it works fine for me. I had to remove (nodevice rtsx) from GENERIC because of slw OS boot, it is trying to probe sd card long enough IMHO it wasn't good

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 5/7/21 2:01 PM, Lev Serebryakov wrote: On 07.05.2021 14:36, Lev Serebryakov wrote:    Looks like there is problem with rtsx driver!   Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem!   And console on these crashes is totally dead, and disks are not detected yet, so I

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 07.05.2021 19:34, Tomoaki AOKI wrote: Have you try dev.rtsx.0.inversion=1 in /boot/loader.conf with the device enabled on BIOS? Not yet :-) I'll try. If not yet, it would be worth trying. In rtsx(4) manpage, 〓 RTS522A on Lenovo P50s and Lenovo T470p, card detection and read-only

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame

On 07.05.2021 19:09, Jesper Schmitz Mouridsen wrote: On 07.05.2021 13.33, Lev Serebryakov wrote: Several versions of 14-CURRENT (including FreeBSD-14.0-CURRENT-amd64-20210506-49c894ddced-246502-memstick.img) can not boot on Lenovo T540p 19 times out of 20. It crashes on device detection

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame

On Fri, 7 May 2021 14:33:27 +0300 Lev Serebryakov wrote: > > Several versions of 14-CURRENT (including > FreeBSD-14.0-CURRENT-amd64-20210506-49c894ddced-246502-memstick.img) can not > boot on Lenovo T540p 19 times out of 20. > > It crashes on device detection, aft

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Fri, 7 May 2021 16:59:35 +0300 Lev Serebryakov wrote: > On 07.05.2021 16:22, Gary Jennejohn wrote: > > >>>> Looks like there is problem with rtsx driver! > >>> Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem! > >>> >

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame

On 07.05.2021 13.33, Lev Serebryakov wrote: Several versions of 14-CURRENT (including FreeBSD-14.0-CURRENT-amd64-20210506-49c894ddced-246502-memstick.img) can not boot on Lenovo T540p 19 times out of 20. It crashes on device detection, after detecting sound subsystem, with traps 9 and 12

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

Just to add to this thread: I'm running CURRENT with rtsx device and driver and it works fine for me. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-curren

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Fri, 7 May 2021 16:59:35 +0300 Lev Serebryakov wrote: > On 07.05.2021 16:22, Gary Jennejohn wrote: > > >>>> Looks like there is problem with rtsx driver! > >>> Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem! > >>> >

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 07.05.2021 16:22, Gary Jennejohn wrote: Looks like there is problem with rtsx driver! Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem! And console on these crashes is totally dead, and disks are not detected yet, so I can not look at structures in memory and/or dump

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 07.05.2021 16:07, Rodney W. Grimes wrote: ?? Looks like there is problem with rtsx driver! ?Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem! ?And console on these crashes is totally dead, and disks are not detected yet, so I can not look at structures in memory

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On Fri, 7 May 2021 15:01:13 +0300 Lev Serebryakov wrote: > On 07.05.2021 14:36, Lev Serebryakov wrote: > > >> Looks like there is problem with rtsx driver! > > Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem! > > > > And console on t

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

> On 07.05.2021 14:36, Lev Serebryakov wrote: > > >> ?? Looks like there is problem with rtsx driver! > > ?Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem! > > > > ?And console on these crashes is totally dead, and disks are not detect

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame - 13.0-RELEASE crashes same way!

On 07.05.2021 14:36, Lev Serebryakov wrote:    Looks like there is problem with rtsx driver!  Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem!  And console on these crashes is totally dead, and disks are not detected yet, so I can not look at structures in memory and

Re: CURRENT crashes at early boot on Lenovo T540p: rtsx to blame

On 07.05.2021 14:33, Lev Serebryakov wrote:   Looks like there is problem with rtsx driver! Oh, I forgot to add: disabling SD Card Reader in BIOS solves problem! And console on these crashes is totally dead, and disks are not detected yet, so I can not look at structures in memory and/or

CURRENT crashes at early boot on Lenovo T540p: rtsx to blame

Several versions of 14-CURRENT (including FreeBSD-14.0-CURRENT-amd64-20210506-49c894ddced-246502-memstick.img) can not boot on Lenovo T540p 19 times out of 20. It crashes on device detection, after detecting sound subsystem, with traps 9 and 12 (9 is more often) and mostly with this

make installworld crashes the system in g_slice_access geom_slice.c:127

> 0 && pp2->ace > 0) (kgdb) p pp2 $2 = (struct g_provider *) 0x0 pp2 is null, and pp2->ace crashes the system. Does the above crash pattern rings any bell? My system uses UFS SU+trim on GELI. On reboot, I had to manually run fsck. At the end I did reinstall successfully world f

Re: loading drm crashes system

Me: > Try September 26 as a reference date. s/September 26/September 6/ ; src = r365372 Respectfully, Robert "Gotcha, ya little bugger!" Huff ___ freebsd-current@freebsd.org mail

Re: loading drm crashes system

On Mon, 25 Jan 2021 22:21:16 -0500 Robert Huff wrote: > Niclas Zeising asks: > > > Which version of drm-current-kmod? > > 5.4.62.g20210118 > > > Can you try to remove it and build it directly from an updated ports > > tree, without using PORTS_MODULES=, and see if that helps? >

Re: loading drm crashes system

On Tue, 26 Jan 2021 13:42:45 +0100 Emmanuel Vadot wrote: > On Tue, 26 Jan 2021 07:02:11 + > Alexey Dokuchaev wrote: >> On Mon, Jan 25, 2021 at 10:21:16PM -0500, Robert Huff wrote: >>> Niclas Zeising asks: When did it stop working? >>> >>> September ... I _think_. >> >> Yeah, th

Re: loading drm crashes system

Hello: > > Niclas Zeising asks: > > > When did it stop working? > > > > September ... I _think_. > > Yeah, that sounds about right. > > There are known issues with Radeon cards, they were quite well > supported a year ago, then something got broken. I've promised to > bis

Re: loading drm crashes system

On Tue, 26 Jan 2021 07:02:11 + Alexey Dokuchaev wrote: > On Mon, Jan 25, 2021 at 10:21:16PM -0500, Robert Huff wrote: > > Niclas Zeising asks: > > > When did it stop working? > > > > September ... I _think_. > > Yeah, that sounds about right. > > There are known issues with Radeon cards, t

Re: loading drm crashes system

W dniu 26.01.2021 o 08:02, Alexey Dokuchaev pisze: On Mon, Jan 25, 2021 at 10:21:16PM -0500, Robert Huff wrote: Niclas Zeising asks: When did it stop working? September ... I _think_. Yeah, that sounds about right. There are known issues with Radeon cards, they were quite well supported a

Re: loading drm crashes system

On Mon, Jan 25, 2021 at 10:21:16PM -0500, Robert Huff wrote: > Niclas Zeising asks: > > When did it stop working? > > September ... I _think_. Yeah, that sounds about right. There are known issues with Radeon cards, they were quite well supported a year ago, then something got broken. I've prom

Re: loading drm crashes system

Niclas Zeising asks: > Which version of drm-current-kmod? 5.4.62.g20210118 > Can you try to remove it and build it directly from an updated ports > tree, without using PORTS_MODULES=, and see if that helps? It does not. > > The GPU is a Radeon HD 3300, and at one poi

  1   2   3   4   5   6   >