linux-kernel - RE: 3.1-rc3 fails to boot on my pandaboard

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 26 Aug 2011 19:05:39 +0000
From:	"Maupin, Chase" <chase.maupin@...com>
To:	Govindraj <govindraj.ti@...il.com>,
	"Coelho, Luciano" <coelho@...com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: RE: 3.1-rc3 fails to boot on my pandaboard


> -----Original Message-----
> From: linux-omap-owner@...r.kernel.org [mailto:linux-omap-
> owner@...r.kernel.org] On Behalf Of Govindraj
> Sent: Thursday, August 25, 2011 6:46 AM
> To: Coelho, Luciano
> Cc: linux-kernel@...r.kernel.org; linux-omap@...r.kernel.org; Thomas
> Gleixner; Sebastian Andrzej Siewior
> Subject: Re: 3.1-rc3 fails to boot on my pandaboard
> 
> On Thu, Aug 25, 2011 at 5:09 PM, Luciano Coelho <coelho@...com> wrote:
> > On Thu, 2011-08-25 at 17:05 +0530, Govindraj wrote:
> >> On Thu, Aug 25, 2011 at 4:09 PM, Luciano Coelho <coelho@...com>
> wrote:
> >> > Hi,
> >> >
> >> > There seems to be a problem with 3.1-rc3, which prevents it from
> booting
> >> > on my PandaBoard (ARM OMAP4).
> >> >
> >> > 3.1-rc2 works fine, so I have bisected the problem and it turns
> out to
> >> > be caused by this:
> >> >
> >> > commit f3637a5f2e2eb391ff5757bc83fb5de8f9726464
> >> > Author: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> >> > Date:   Thu Jul 7 22:32:17 2011 +0200
> >> >
> >> >    irq: Always set IRQF_ONESHOT if no primary handler is specified
> >> >
> >> > After reverting this commit, -rc3 boots fine.  I'm not sure where
> >> > exactly the problem is.  Maybe it's something in the omap code
> which is
> >> > broken and this patch causes the bug to show up?
> >> >
> >> > What happens is that the booting process hangs after printing out
> this:
> >> >
> >>
> >> fyi,
> >>
> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-
> 2.6.git;a=commitdiff;h=69dd3d8e29e294caaf63eb5e8a72d250279f9e5f;hp=fcb8
> ce5cfe30ca9ca5c9a79cdfe26d1993e65e0c
> >
> > Ah, thanks.  Now I see where the irq == 74 comes from. :) Still, I
> don't
> > see that on my system.
> >

FYI, I also saw this same issue on an AM37x-evm and beagleboard.  Reverting the above commit works for me to be able to see the boot messages from the file system after the kernel boots.

> 
> 69dd3d8 Revert "irq: Always set IRQF_ONESHOT if no primary handler is
> specified"
> f2b6071 drm/radeon: Extended DDC Probing for Toshiba L300D Radeon
> Mobility X1100 HDMI-A Connector
> c87019e HID: wiimote: Add status and return request handlers
> 2cb5e4b HID: wiimote: Add drm request
> 23a5a4a HID: wiimote: Register led class devices
> 26af174 HID: wiimote: Correctly call HID open/close callbacks
> 3989ef6 HID: wiimote: Simplify synchronization
> 8d3bb23 drm/ttm: ensure ttm for new node is bound before calling
> move_notify()
> eac2095 drm/ttm: unbind ttm before destroying node in accel move
> cleanup
> 7c4c396 drm/ttm: fix ttm_bo_add_ttm(user) failure path
> f5e4282 HID: usbhid: Add support for SiGma Micro chip
> 11f3a6b bridge: fix a possible net_device leak
> b6bede3 xfs: fix tracing builds inside the source tree
> 832d80a Merge branch 'for-davem' of
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless
> fcb8ce5 Linux 3.1-rc3
> 
> 
> --
> Thanks,
> Govindraj.R
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap"
> in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/