From mboxrd@z Thu Jan  1 00:00:00 1970
From: Greg KH <gregkh@linuxfoundation.org>
Date: Tue, 15 Mar 2016 03:16:47 +0000
Subject: Re: Fwd: How to determine which device crashes udev in boot?
Message-Id: <20160315031647.GA30956@kroah.com>
List-Id: <linux-hotplug.vger.kernel.org>
References: <CAD4SBxBhtLmMqiUmCFZ7i8q1aQ2d6Hrse=k_BBz_2VGcJQSmcg@mail.gmail.com>
In-Reply-To: <CAD4SBxBhtLmMqiUmCFZ7i8q1aQ2d6Hrse=k_BBz_2VGcJQSmcg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

On Tue, Mar 15, 2016 at 10:39:39AM +0900, iwillallways forget1 wrote:
> 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.

good luck!

greg k-h