#asahi · 2024-05-08 11:41
PaulFertserbawj_: right. So probably the DT you're using doesn't define a video device?#asahi · 2024-05-08 11:40
bawj_but the uboot i built with qemu_arm64 config already sets that flag#asahi · 2024-05-08 11:40
bawj_PaulFertser: looking at the source it seems CONFIG_VIDEO is the flag to set https://github.com/AsahiLinux/u-boot/blob/582f851413c3fd1fcd60d701ed54fff2e840b9cf/lib/efi_loader/Makefile#L84#asahi · 2024-05-08 11:37
PaulFertserI think there should be an easy way to do that but I can't tell what exactly to choose in the options. Would be really surprising if Qemu didn't support at least one board which is also supported by U-boot video drivers.#asahi · 2024-05-08 11:31
PaulFertserSo you need to build with CONFIG_LCD and run on supported emulated board.#asahi · 2024-05-08 11:30
PaulFertserbawj_: it was added long time ago https://patchwork.ozlabs.org/project/uboot/patch/1458063501-211379-1-git-send-email-agraf@suse.de/#asahi · 2024-05-08 11:28
PaulFertserbawj_: probably your u-boot was built without it?#asahi · 2024-05-08 11:23
bawj_may have reached a dead end #asahi · 2024-05-08 11:23
bawj_PaulFertser: i tried what u mentioned, built uboot for qemu_arm64 and ran my uefi application through it, seems like it couldnt find the GraphicsOutputProtocol from calling locateProtocol. #asahi · 2024-05-08 09:49
bluetailI do think apple eventually fixed aforementioned issue with the 8GB models with a firmware update ...#asahi · 2024-05-08 09:49
bluetailThanks Paul#asahi · 2024-05-08 09:46
bluetailessentially, the issue with the 8gb model was a kernel panic on use#asahi · 2024-05-08 09:46
PaulFertserIn this case it's "Apple Mac mini (M1, 2020)" running 6.6.3 Fedora#asahi · 2024-05-08 09:45
bluetailthere was a badge of bad units, I think apple messed up big time, but who knows#asahi · 2024-05-08 09:45
bluetailmy first m1 mac mini was faulty, 8GB model - firmware issue potentially#asahi · 2024-05-08 09:45
bluetailthis is a m1 mac mini with 16gb RAM#asahi · 2024-05-08 09:42
chadmed_i also use an m2 pro mini as a server and same no dart faults here #asahi · 2024-05-08 09:38
jannaumarcan afaik also uses m1 and m2 pro as storage servers and doesn't see that there. my m1 storage server is fixe as well#asahi · 2024-05-08 09:37
jannauyes, "apple-dart 502f80000.iommu: translation fault: status:0x81000404 stream:1 code:0x404 (unknown) at 0xffda4080" is bad on probably explains the errors. marcan was/is seeing this on a m2 mac mini used as ceph storage box. and there was another report (I think an issue on gh)#asahi · 2024-05-08 09:10
PaulFertserAnd now it's default either way#asahi · 2024-05-08 09:09
PaulFertserbluetail: 4k should be good#asahi · 2024-05-08 09:06
bluetailSince the m1 mac operates at 16k pages, it wouldn't be unthinkable that it tries to use 16k pages, even if specified at 4k#asahi · 2024-05-08 09:06
bluetailI did force 4k pages for the disks since I also use it on a normal x86/x64 machine#asahi · 2024-05-08 09:05
bluetailI do wonder though#asahi · 2024-05-08 08:29
bluetailNot just leaving like those silly guests#asahi · 2024-05-08 08:29
bluetailI am here, anyways#asahi · 2024-05-08 08:29
bluetailBefore submitting a report, I'd like to know what else is needed#asahi · 2024-05-08 08:29
PaulFertserThe devs here should be able to give a better advice, yes.#asahi · 2024-05-08 08:29
bluetailthe real devs are here#asahi · 2024-05-08 08:28
PaulFertserI guess you should report instances of those as a github ticket. It's strange they only affect the xhci controller in your testing but it's up to the real devs to judge what other data or tests might be useful.#asahi · 2024-05-08 08:26
bluetailcan you elaborate? I could google this, if not.#asahi · 2024-05-08 08:26
PaulFertsertranslation faults are bad mkay?#asahi · 2024-05-08 08:25
bluetailI prob gonna make multiple runs ...#asahi · 2024-05-08 08:24
bluetailmemtester didnt found a issue#asahi · 2024-05-08 08:22
bluetailgoogle spit out https://lore.kernel.org/linux-arm-kernel/20230113105029.26654-8-marcan@marcan.st/T/ but I am not sure if thats the right result#asahi · 2024-05-08 08:21
PaulFertserThose apple-dart errors look scary and probably that's what you need to discuss with the devs.#asahi · 2024-05-08 08:20
PaulFertserAnd then 30 seconds later exactly the hell broke loose.#asahi · 2024-05-08 08:19
PaulFertserIt might have started with that.#asahi · 2024-05-08 08:19
PaulFertserApr 16 00:39:17 archm1 kernel: apple-dart 502f80000.iommu: translation fault: status:0x81000404 stream:1 code:0x404 (unknown) at 0xffda4080#asahi · 2024-05-08 08:19
PaulFertserHuh that's another day and another problem.#asahi · 2024-05-08 08:18
bluetailthe thing is, this is a raid1c3 (three disks)#asahi · 2024-05-08 08:18
bluetailand before that ... "Apr 16 00:39:53 archm1 kernel: usb 4-1.4: USB disconnect, device number 10"#asahi · 2024-05-08 08:17
PaulFertserThat's assuming your logs have full information. From what you show it looks like there's no issue detected at all anyhow on any level until suddenly access beyond the end is made.#asahi · 2024-05-08 08:17
bluetaildid you see: Apr 16 00:39:53 archm1 kernel: BTRFS info (device dm-4: state E): forced readonly#asahi · 2024-05-08 08:17
bluetailwait#asahi · 2024-05-08 08:16
bluetailIn that case I am going to assume a btrfs issue and after the btrfs filesystem repair, I try again.#asahi · 2024-05-08 08:13
PaulFertserUSB packets have CRC so silent data corruptions on USB level shouldn't be practically possible.#asahi · 2024-05-08 08:11
bluetailthere are no corruption errors, either#asahi · 2024-05-08 08:11
bluetailsmartctl doesnt report anything useful, either#asahi · 2024-05-08 08:08
PaulFertserReading past end of device isn't supposed to not generate an error.