From: iwillallways forget1 <iwillalwaysforget1@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Fwd: /lib/udev/pcmcia-socket-startup makes 32-bit Linux crash hard
Date: Mon, 04 Apr 2016 03:21:29 +0000 [thread overview]
Message-ID: <CAD4SBxC=JfSRPpHTezqWr9kQ383R3GyomZC8Q-4_PY6ZB-Hvwg@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.
It appears that the particular device is highly relevant:
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
I tested two other PCs with pcmcia slots made by different manufacturers.
One was cardbus only, and had no problem.
One was cardbus + 16-bit pcmcia, and had no problem, not made by Ricoh.
So the particular Ricoh controller looks relevant.
In /lib/udev/rules.d/60-pcmcia.rules I commented out these two lines:
SUBSYSTEM="pcmcia_socket", \
RUN+="/lib/udev/pcmcia-socket-startup"
After commenting them out, Linux boots with no problem.
Sorry to repeat for the nth time, but 64-bit Linux doesn't have this probem
but 32-bit Linux's version of pcmcia-socket-startup kills the kernel hard
on this very same PC.
In a separate message I'll discuss two intermittent problems when a 16-bit
pcmcia card is actually used. But these won't affect many people because
no one, not even me, uses a 16-bit pcmcia card for anything other than testing.
reply other threads:[~2016-04-04 3:21 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='CAD4SBxC=JfSRPpHTezqWr9kQ383R3GyomZC8Q-4_PY6ZB-Hvwg@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).