From: iwillallways forget1 <iwillalwaysforget1@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: /lib/udev/pcmcia-socket-startup makes 32-bit Linux crash hard
Date: Thu, 31 Mar 2016 05:30:33 +0000 [thread overview]
Message-ID: <CAD4SBxCnOAurZmWLJugvOH_8sSP3_DntmCt1GWiNDAfFndeDFA@mail.gmail.com> (raw)
Porteus 3.1 uses kernel 3.17.4.
64-bit Porteus 3.1 works fine on an NEC VF-6.
32-bit Porteus 3.1 hangs in udev during boot. It's not a 120-second
delay for udevadm settle, it's a hard crash which doesn't even display
an oops in text mode, doesn't even flash two keyboard lamps, and
doesn't even respond to the Caps Lock or Num Lock keys or
Ctrl+Alt+Delete. It needs a press of the power button.
32-bit Porteus 3.1, when booted with nohotplug, works until I try
running rc.udev start. Then the hang is the same as always.
Porteus is a live Linux distribution and has a rootcopy directory. I
copied file /lib/udev/rules.d/60-pcmcia.rules to the appropriate
directory in a Porteus USB stick, and edited it, so this would
override the built-in 60-pcmcia.rules file. I commented out these
lines:
SUBSYSTEM="pcmcia_socket", \
RUN+="/lib/udev/pcmcia-socket-startup"
So, /lib/udev/pcmcia-socket-startup works in 64-bit mode but makes
32-bit Linux die.
When those lines are commented out, the yenta drivers don't crash,
though I don't know if they'll work when a 32-bit Cardbus card or
16-bit PCMCIA card is actually inserted
I don't know yet if the problem is particular to this PC model, or
particular to the PCMCIA slot, or more widespread.
0a:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b6)
Subsystem: NEC Corporation Device [1033:88ec]
Kernel driver in use: yenta_cardbus
Kernel modules: yenta_socket
reply other threads:[~2016-03-31 5:30 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=CAD4SBxCnOAurZmWLJugvOH_8sSP3_DntmCt1GWiNDAfFndeDFA@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).