From: Jiri Slaby <jslaby@suse.cz>
To: George Spelvin <linux@horizon.com>
Cc: ojab <ojab@ojab.ru>, stable <stable@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [stable-request] [Bisected] Kernel 3.8 hangs on boot
Date: Fri, 22 Feb 2013 12:01:17 +0100 [thread overview]
Message-ID: <51274FFD.4050509@suse.cz> (raw)
In-Reply-To: <5127402A.6040501@ojab.ru>
On 02/22/2013 10:53 AM, ojab wrote:
> On 22.02.2013 13:25, Jiri Slaby wrote:
>> On 02/22/2013 07:32 AM, ojab wrote:
>>
>> Ideally with description of tha hang. Are there any messages (if you
>> disable splash and enable debug)? Do keyboard LEDs blink?
>>
>>
>> Especially architecture. Then do you have serial ports, some GSM devices
>> or GPS?
>
> It's x86_64 machine and I have GPS w/ PPS (Garmin 18x LVC) connected via
> serial, without it kernel boots/works fine. Also no issues with GPS
> connected, but PPS disabled (by removing pps_core.ko module).
> If I'm connecting GPS w/ PPS to already booted machine — cursor on the
> display stops blinking and I cannot input anything, but I still can
> switch between VTs using Ctrl-Fx and keyboard LEDs are blinking when I'm
> pressing Num/Caps Lock keys.
Ok, you have a problem fixed by this commit:
commit 03a7ffe4e542310838bac70ef85acc17536b6d7c
Author: George Spelvin <linux@horizon.com>
Date: Sun Feb 10 04:41:56 2013 -0500
pps: Use pps_lookup_dev to reduce ldisc coupling
I think this should go to stable-3.8 with its prerequisity:
commit 513b032c98b4b9414aa4e9b4a315cb1bf0380101
Author: George Spelvin <linux@horizon.com>
Date: Sun Feb 10 04:08:32 2013 -0500
pps: Add pps_lookup_dev() function
George?
thanks,
--
js
suse labs
next parent reply other threads:[~2013-02-22 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <512710F3.9070602@ojab.ru>
[not found] ` <51273988.2070907@suse.cz>
[not found] ` <5127402A.6040501@ojab.ru>
2013-02-22 11:01 ` Jiri Slaby [this message]
2013-02-22 11:02 ` [stable-request] [Bisected] Kernel 3.8 hangs on boot Jiri Slaby
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=51274FFD.4050509@suse.cz \
--to=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=ojab@ojab.ru \
--cc=stable@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 NNTP newsgroup(s).