Quote:
Originally Posted by NiLuJe
@church mouse: I can see a cold boot, two (apparently sane) ejects (a minute apart each), a sane KU run, and the log dump.
Does that track?
Is the KU run actually a spurious one here? Did one actually happen? (Ideally, I'd need a log *after* a spurious KU run on eject  ).
(I mean, that one is sufficiently far apart from the eject that it *looks* user-triggered?). |
After the sane KU run there was a short delay before I carried a USB connect/eject, followed by the spurious message, then I generated the log dump.
Over the weekend I will try the process a few more times with longer delays between each step. Tonight, I feel I kind of rushed everything, which isn't fair to you, or a real world scenario.