Fwd: Fwd: How to determine which device crashes udev in boot?

Greg K-H replied to me:
>> Some device has a working driver for Porteus's 64-bit kernel but a
>> crashing driver for Porteus's 32-bit kernel, and the crash is so hard
>> that it doesn't even start flashing two keyboard lights.  Also this
>> being text mode (when I type udevadm not startx), the crash is so hard
>> that it doesn't print an oops.
>
> Use a serial console, that way you can see the oops happen there.

Perhaps I should mention that I had
tail -f /var/log/messages >/mnt/sdb1/what 2>&1 &
running in the background before running udevd and udevadm trigger.
The log included udev stuff until the crash, but did not include the oops.

I think I own two USB-to-serial adapters and a serial reverse cable.
I'll have to hunt for them and bring them to my employer.
Do you think the oops will get out over a USB-to-serial adapter
before the kernel crashes hard?

(Several years ago I saved virtual serial output to a real file under
VMware and diagnosed an oops, but the NEC VF-6 is a real notebook with
some device that a VMware virtual PC doesn't have.)