From: iwillallways forget1 <iwillalwaysforget1@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Fwd: Fwd: How to determine which device crashes udev in boot?
Date: Thu, 17 Mar 2016 08:54:10 +0000 [thread overview]
Message-ID: <CAD4SBxAoUczieAGCkjzMfYrPru4P+KJiVwA-TDkrdDS+osk_Lw@mail.gmail.com> (raw)
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.)
next reply other threads:[~2016-03-17 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 8:54 iwillallways forget1 [this message]
2016-03-17 16:56 ` Fwd: Fwd: How to determine which device crashes udev in boot? Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD4SBxAoUczieAGCkjzMfYrPru4P+KJiVwA-TDkrdDS+osk_Lw@mail.gmail.com \
--to=iwillalwaysforget1@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).