ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
rvalue has quit [Ping timeout: 268 seconds]
rvalue has joined #armlinux
rfried1 has joined #armlinux
rfried has quit [Ping timeout: 256 seconds]
rfried1 is now known as rfried
Sledge has quit [Ping timeout: 264 seconds]
hanetzer has quit [Ping timeout: 240 seconds]
Sledge has joined #armlinux
apritzel has quit [Ping timeout: 246 seconds]
SystemError has quit [Remote host closed the connection]
SystemError has joined #armlinux
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #armlinux
SystemError has quit [Remote host closed the connection]
SystemError has joined #armlinux
heat has quit [Ping timeout: 240 seconds]
sakman has joined #armlinux
sakman has quit [Ping timeout: 260 seconds]
cbeznea has joined #armlinux
sakman has joined #armlinux
sakman has quit [Quit: sakman]
mvaittin_ has joined #armlinux
monstr has joined #armlinux
mvaittin_ has quit [Ping timeout: 256 seconds]
apritzel has joined #armlinux
vingu has quit [Ping timeout: 246 seconds]
apritzel has quit [Ping timeout: 264 seconds]
mvaittin has joined #armlinux
vingu has joined #armlinux
gclement has joined #armlinux
headless has joined #armlinux
iivanov_ has joined #armlinux
iivanov has quit [Ping timeout: 240 seconds]
gfernandez has joined #armlinux
iivanov_ has quit [Remote host closed the connection]
iivanov has joined #armlinux
qpla has joined #armlinux
luispm has joined #armlinux
frieder has joined #armlinux
SystemError has quit [Remote host closed the connection]
nsaenz has joined #armlinux
SystemError has joined #armlinux
sszy has joined #armlinux
qpla has quit [Read error: Connection reset by peer]
qpla has joined #armlinux
qpla has quit [Remote host closed the connection]
qpla has joined #armlinux
Lockesmith has quit [Ping timeout: 260 seconds]
Lockesmith has joined #armlinux
Lockesmith has quit [Remote host closed the connection]
Lockesmith has joined #armlinux
apritzel_ has joined #armlinux
headless has quit [Quit: Konversation terminated!]
iivanov_ has joined #armlinux
iivanov has quit [Ping timeout: 256 seconds]
luispm has quit [Ping timeout: 256 seconds]
dmart has joined #armlinux
SystemError has quit [Remote host closed the connection]
iivanov_ has quit [Remote host closed the connection]
iivanov has joined #armlinux
qpla has quit [Ping timeout: 256 seconds]
gfernandez has quit [Quit: Client closed]
luispm has joined #armlinux
tambarus has joined #armlinux
<ajb-linaro>
gah I'd love to know what the firmware is doing when it takes a minute before the efi framebuffer becomes visible
headless has joined #armlinux
<ardb>
ajb-linaro: which platform?
<ajb-linaro>
ardb Ampere AVA
<ardb>
ah
<ajb-linaro>
ardb I think there is a serial port but amusingly I don't think I have a 9 pin serial cable handy - there may be something on the PCB
<ardb>
why does it matter? on a system like that, it is typically talking to the BMC and all the other cores to get SMBIOS tables etc in order
<ajb-linaro>
ardb its just very enigmatically quiet when it does so I worry its hung. I'm debugging Xen stuff atm and that goes dark pretty quickly
<ardb>
most server boxes are like that unfortunately
<ardb>
can you hook up to the BMC?
<ardb>
this is rather symptomatic for server boards repurposed as workstations though
<ardb>
boot time just isn't important for the former
<manospitsid>
ajb-linaro: I use a rs232 to usb cable on mine
<manospitsid>
also it takes a while to load the graphical EFI stuff; it keeps printing firmware debugging stuff slowly on serial
<manospitsid>
I suspect that's what it is for you
<robmur01>
yeah, server boards like to do lots of stuff during POST, often complete memory tests and everything - my eMAG workstation takes about 2 minutes to reboot also
<ajb-linaro>
*sigh* unsurprisingly the amd rocm installer is very x86 focused
<milkylainen>
dram link training? :P
<milkylainen>
hasn't the latest in ddr standards become pretty awful with regard to link training times?
<ardb>
manospitsid: yeah just the amount of debug data vs the limited baud rate is likely to be a major factor here
<broonie>
If that's the platform I think it is it's not *super* chatty so probably not rate limiting.
<manospitsid>
it's not much in quantity, just slow
vingu has quit [Ping timeout: 256 seconds]
vingu has joined #armlinux
tambarus has quit [Ping timeout: 260 seconds]
tambarus has joined #armlinux
psydroid has joined #armlinux
heat has joined #armlinux
monstr has quit [Ping timeout: 252 seconds]
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #armlinux
monstr has joined #armlinux
mvaittin has quit [Ping timeout: 264 seconds]
apritzel__ has joined #armlinux
apritzel_ has quit [Ping timeout: 255 seconds]
headless has quit [Quit: Konversation terminated!]
apritzel_ has joined #armlinux
apritzel__ has quit [Ping timeout: 256 seconds]
<ajb-linaro>
manospitsid is that the 9 pin at the back?
frieder has quit [Ping timeout: 272 seconds]
frieder has joined #armlinux
<manospitsid>
ajb-linaro: yes
ungeskriptet9 has joined #armlinux
ungeskriptet has quit [Ping timeout: 246 seconds]
ungeskriptet9 is now known as ungeskriptet
iivanov has quit [Ping timeout: 256 seconds]
iivanov has joined #armlinux
gfernandez has joined #armlinux
gclement has quit [Read error: Connection reset by peer]
gclement has joined #armlinux
gclement1 has joined #armlinux
gclement has quit [Read error: Connection reset by peer]
monstr has quit [Remote host closed the connection]
heat has quit [Remote host closed the connection]
heat has joined #armlinux
tambarus has quit [Ping timeout: 264 seconds]
tambarus has joined #armlinux
gclement1 has quit [Ping timeout: 246 seconds]
vingu has quit [Quit: Leaving.]
vingu has joined #armlinux
dmart has quit [Quit: leaving]
gfernandez has quit [Quit: Client closed]
marc|gonzalez has joined #armlinux
<marc|gonzalez>
Is there a magic kernel bootcmd to force the kernel to probe devices sequentially, in order to get roughly deterministic kernel logs I can run diff on? (Even if it slows down boot by a factor of 10)
<marc|gonzalez>
(For example, I don't want the PCIe init to mingle with the SMMU init)
<marc|gonzalez>
I suppose one way to work around the issue is to compile everything as modules, and modprobe one device at a time, but hoping it doesn't come to this...
headless has joined #armlinux
<robmur01>
marc|gonzalez: "maxcpus=1", bring the rest up later ;)
<marc|gonzalez>
robmur01: that sounds good, although the sneaky little kernel could schedule a different probe once the first once starts waiting, right? :)
<robmur01>
"preempt=none" :D
<marc|gonzalez>
I will try that, and pray to the gods of the deadlock & livelock & merry forward progress!
<robmur01>
there do exist various async_probe options, but I'm not sure if it's actually possible to force everything including drivers' own PROBE_PREFER_ASYNCHRONOUS back to synchronous - the intent seems more focused on the other direction
<marc|gonzalez>
build system does not like me doing make -j20 qcom/apq8098-freebox-delta.dtb all
<marc|gonzalez>
looks like building the kernel in parallel with the DTB is not supported
<marc|gonzalez>
Unknown kernel command line parameters "preempt=none", will be passed to user space.
<marc|gonzalez>
I didn't even check, I thought that was a real option :p
<robmur01>
It is if you're cool and have CONFIG_PREEMPT_DYNAMIC
<marc|gonzalez>
Hey, I'm cool!
<marc|gonzalez>
"CONFIG_PREEMPT_DYNAMIC is not set" -- but not cool enough
<marc|gonzalez>
Thanks, will look closely-er at that