On Tue, Apr 29, 2025 at 02:19:30AM +0000, Damien Zammit wrote: > Hi, this is very interesting and probably indicating that we need to fix race > between previous servers starting up and next ones, as you mentioned. > What happens if you put a sleep(5) before rump_init() in rumpdisk, does ahci > boot?
Just tried it. Log: https://paste.debian.net/1372174/ It seems to me that it's not the issue with ACPI. The log of ACPI (the log before `PASS!`) is tidy. Assume ACPI has got enough time from sleep(5) to finish initialization. It seems there is something else having data race with rumpdisk. In: ``` rumpdisk r[a n 1.000000d0] Copyrighot (c) 1996m, 19i97n, i19t98, 1999, 2000, 20o01, 2002,p 2e00n3, [ f a1.00i000l00e] 2d00 ``` We can see 'random init open faile`. No idea where does it come from. Zhaoming > > -------- Original Message -------- > On 29/4/25 12:11 pm, Zhaoming Luo <zhming...@163.com> wrote: > > > Hi, > > > > I got the Thinkpad T60 dock and the serial-to-usb cable. The issue is > > that we found booting Thinkpad T60 with rumpdisk failed, so I collected > > the log for navigation. I followed this link[0] to set up the > > environment for rumpdisk. If I miss any neccessary information, please > > remind me. > > > > I set up three environments. (1) uses hd0 (i.e. old linux driver to > > bootup). (2) and (3) use wd0 (i.e. rumpdisk). (2) uses SATA BIOS setup > > AHCI. (3) uses SATA BIOS setup Compactibility. > > > > In all three environments: > > gnumach version: 20250304 > > hurd version: 20250420-1 > > --- > > Boot without rumpdisk: > > > > - Setup: > > BIOS Config: > > SATA: Compactibility > > > > In /boot/grub/grub.cfg: > > multiboot /boot/gnumach-1.8-486.gz root=part:2:device:hd0 console=com0 > > > > In /etc/fstab: > > /dev/hd0s2 / ext2 defaults 0 1 > > /dev/hd0s1 none swap sw 0 0 > > /dev/hd2 /media/cdrom0 iso9660 noauto 0 0 > > > > Result: Success > > > > Log: https://paste.debian.net/1372168/ > > --- > > Boot with rumpdisk: > > > > - Setup: > > BIOS Config: > > SATA: AHCI > > > > In /boot/grub/grub.cfg: > > multiboot /boot/gnumach-1.8-486.gz root=part:2:device:wd0 console=com0 > > noide > > > > In /etc/fstab: > > /dev/wd0s2 / ext2 defaults 0 1 > > /dev/wd0s1 none swap sw 0 0 > > /dev/wd2 /media/cdrom0 iso9660 noauto 0 0 > > > > Result: Fail > > > > Log: https://paste.debian.net/1372169/ > > --- > > Boot with rumpdisk: > > > > - Setup: > > BIOS Config: > > SATA: Compactibility > > > > In /boot/grub/grub.cfg: > > multiboot /boot/gnumach-1.8-486.gz root=part:2:device:wd0 console=com0 > > noide > > > > In /etc/fstab: > > /dev/wd0s2 / ext2 defaults 0 1 > > /dev/wd0s1 none swap sw 0 0 > > /dev/wd2 /media/cdrom0 iso9660 noauto 0 0 > > > > Result: Fail > > > > Log: https://paste.debian.net/1372170/ > > > > --- > > My guess: > > I guess is that there are some data races between acpi and rumpdisk. We > > can see that the output started being messy after boundry of acpi and > > rumpdisk. > > > > Zhaoming > > > > [0]: https://darnassus.sceen.net/~hurd-web/hurd/rump/rumpdisk/ > > > > > >
