[Bug 276985] crash in LinuxKPI/drm

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985

--- Comment #30 from Tomasz "CeDeROM" CEDRO <tomek@cedro.info> ---
(In reply to Olivier Certner from comment #26)

Thanks Olivier. This is my last message in this thread. I will add another disk
and create a dedicated install on this machine and report a separate bug as
requested. As I explained before this is my main production workstation that
keeps data and generates cash it cannot break for a second. I have other more
powerful machines (i.e. recent MacStudio) but I prefer to stick to FreeBSD.
After switching from 13 to 14 it crashed like crazy on exactly the same
hardware setup, call it regression or whatever you like, for me it's not
production ready because it does not allow me to work. I saw other people with
AMGDPU problems so I added my info on my problem (not necessarily exactly the
same problem I know). I am happy that your setup forks fine, and for your
friends, but I would not ship a product like this knowing it does not work for
me nor for some people. I just got used to comfort of a release being always
rock solid.

Thanks for pointing out its a different issue. Also thank you for pointing out
I can work with 5.10, 5.15, and 6.10 on 14 release what is not possible on 13
(some documentation on this would be nice). If I knew what the problem is and
how to fix it I would send patches not crash logs.

Btw there is no need to use offensive aggressive and arrogant language (i.e.
"you are not willing to test", "you're alone", "spreading FUD by
over-generalizing your own case", etc). This is not a constructive and
motivating language that I am used for to see here. I am not here to argue,
especially with new kernel developer that may solve the problem, just to note
"I also have serious problems with my AMDGPU drivers on 14 like the others
reported and I do not know what the problem is". But I get the point. You see
far more details and point the direction. And with no testing on the
problematic hardware there will be no solution. I will create a dedicated
install on a separate disk and try to help testing. I am just a bit scared to
do this on a production machine you can imagine that - data loss here would
cost me time, trust, and probably abandoning FreeBSD (on desktop).

My last question - if you are the drm module maintainer / developer - would it
be possible to mark following ports with incremental numbers like 510, 515,
610, not 61 for a newest release please (61 < 515)?

Thank you for your time and have a good day Olivier.. its 12:00 here and I just
finished writing a driver for external chip on RTOS after some ~36h non stop
work.. all done on several FreeBSD machines.. tome to get some sleep :-) :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.