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: 246 seconds]
rvalue has joined #armlinux
heat has quit [Ping timeout: 240 seconds]
apritzel has quit [Ping timeout: 264 seconds]
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #armlinux
amitk has joined #armlinux
Lucanis has quit [Ping timeout: 260 seconds]
Lucanis has joined #armlinux
cbeznea_ has joined #armlinux
iivanov has joined #armlinux
sally has quit [Remote host closed the connection]
monstr has joined #armlinux
hanetzer has quit [Ping timeout: 260 seconds]
hanetzer has joined #armlinux
gfernandez has quit [Quit: Client closed]
gclement has joined #armlinux
<manospitsid>
How would you approach debugging this `Hardware error from APEI Generic Hardware` kernel panic? the error info is minimal. On a neoverse n1 (ampere altra) https://paste.debian.net/hidden/e0f267c7
frieder has joined #armlinux
iivanov has quit [Ping timeout: 255 seconds]
headless has joined #armlinux
iivanov has joined #armlinux
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #armlinux
nsaenz has joined #armlinux
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
Lockesmith has quit [*.net *.split]
SystemError has quit [*.net *.split]
sszy has joined #armlinux
biju has joined #armlinux
ezulian has joined #armlinux
ezulian has quit [Remote host closed the connection]
apritzel_ has joined #armlinux
headless_ has joined #armlinux
headless has quit [Ping timeout: 264 seconds]
headless_ has quit [Quit: Konversation terminated!]
ezulian has joined #armlinux
nsaenz has quit [Ping timeout: 264 seconds]
biju has quit [Ping timeout: 260 seconds]
robmur01_ is now known as robmur01
<robmur01>
manospitsid: as far as the kernel is concerned, we're panicking because firmware has told us a CPU is broken
<robmur01>
I'd guess a fatal "cache error" is maybe likely to be an ECC double-error detection, but to decode more specific details of that event record I'd imagine you might need to ask the firmware/hardware vendor
biju has joined #armlinux
<manospitsid>
robmur01: thank you! is it possible a pci device or bus cause this? cache error would mean any memory, including device/peripheral right?
<robmur01>
If it's coming from a specific CPU I'd be inclined to think it was a cache related to that CPU (L1/L2) rather than the system-level cache (which belongs to the CMN interconnect)
<robmur01>
but ultimately I suspect it depends on how the firmware has defined its error sources
<robher>
frieder: The graph will support that. Define a node for the DSI switch with 3 ports.
<robher>
frieder: To repeat yesterday's message: "If only there was a channel for devicetree topics..."
<robher>
frieder: I'm pretty sure the kernel won't be happy with the warning in your dts either.
<frieder>
robher: Ah, ok. I don't think I have tried that. Do I need to set a compatible for the node?
<frieder>
robher: The drivers are working fine even with the bindings warning.
<robher>
frieder: You'll need a driver for the node, so yes.
<robher>
Is the switch transparent?
<frieder>
robher: Ok, but there is no existing driver to represent a generic graph tree switch, right?
<robher>
frieder: I don't think so.
<marc|gonzalez>
frieder: robher is subtly :) alluding to #devicetree
<frieder>
marc|gonzalez: Ok, thanks. Got it now. I will switch over. Sorry for using the wrong channel.
<arnd>
geertu: I'm about ready to send a v2 of the CONFIG_PAGE_SIZE series, which way do you want the m68k Kconfig to go? Change it according to your initial reply or keep the version I have?
gfernandez has joined #armlinux
<ukleinek>
mmind00: I didn't buy the qnap device, qnap sent me one :-)
headless has joined #armlinux
<mmind00>
ukleinek: oh nice :-)
<ukleinek>
mmind00: and regarding the UART pinout: I asked for it, didn't hear back from them for a while (and worked it out myself in the meantime)
<ukleinek>
mmind00: when they finally responded they sent me an NDA that I would have had to sign before they tell me the pin assignment.
<mmind00>
ukleinek: for a pinout :-D
<ukleinek>
mmind00: high value trade secret!
<ukleinek>
mmind00: would you consider robher's reply to my ts433 patch a stopper?
<mmind00>
ukleinek: nope
* ukleinek
nods
SystemError has joined #armlinux
<mmind00>
ukleinek: though I'm looking into what's needed to fix those "unreleated" issues
amitk_ has joined #armlinux
apritzel has joined #armlinux
SystemError has quit [Remote host closed the connection]
SystemError has joined #armlinux
heat has joined #armlinux
mvaittin has quit [Ping timeout: 256 seconds]
<CounterPillow>
Imagine if the competition learned of their UART pinout! They could do heinous things like, hmm... uh...
SystemError has quit [Remote host closed the connection]
SystemError has joined #armlinux
<marc|gonzalez>
CounterPillow: like steal all their IP, and empty their bank accounts, and wipe their memory clean
<marc|gonzalez>
do not underestimate the power of 112 kbaud!
zkrx has quit [Ping timeout: 264 seconds]
apritzel has quit [Ping timeout: 264 seconds]
zkrx has joined #armlinux
SystemError has quit [Remote host closed the connection]
SystemError has joined #armlinux
gclement has quit [Ping timeout: 246 seconds]
heat_ has joined #armlinux
gfernandez has quit [Quit: Client closed]
heat has quit [Read error: Connection reset by peer]