From: iwillallways forget1 <iwillalwaysforget1@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Fwd: Fwd: Fwd: How to determine which device crashes udev in boot?
Date: Thu, 31 Mar 2016 05:13:22 +0000 [thread overview]
Message-ID: <CAD4SBxC8tPB8W+Stjmi5=GkN_2XGyZ-E0F5Ly9uQ8uTFmtSs4Q@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.
[...]
> No, usb serial usually does not work for capturing oops messages because
> the kernel crashes and USB needs interrupts to be running properly to
> deliver data.
It's a notebook PC and doesn't have a real serial port.
It does have a real PCMCIA slot, which will be the subject of a new thread.
> As you know what kernel drivers are needed for this hardware (it works
> in 64bit mode), just load them by hand, one by one, in 32bit mode and
> see what one dies.
All modprobes succeeded. A new thread will discuss the problem.
I still never figured out how to make udev ignore a device. Of course
I see debugging options (which didn't help) and options to ignore
devices that have certain attributes or properties, but never got the
syntax right to ignore the PCMCIA slot or bridge. For the moment I no
longer need to know, but if there's a tutorial somewhere please say.
reply other threads:[~2016-03-31 5:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAD4SBxC8tPB8W+Stjmi5=GkN_2XGyZ-E0F5Ly9uQ8uTFmtSs4Q@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).