On Mon, Apr 22, 2019 at 08:20:30PM -0000, Ryan Harper wrote: > Hi Seth, > > notice only one of the stack tracks have the floppy, the mdadm one does > not. I've also recreated this on a qemu q35 machine type which does not > include the floppy device.
I looked at the madm stack trace, and I was assuming that it occurred during the same boot as the other one. I suppose I shouldn't have, but it would make sense. mdadm appears to be blocked on a block device's bd_mutex, so the cause is probably something else that has hung while holding that mutex. The mkfs stack trace would be just the kind of thing to create the mdadm stack trace, if it were trying to open the same device. So, were those traces from a single boot or from different boots? Can you provide stack trace(s) from the q35 machine type for comparison? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825413/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
