From: Stefan Assmann <sassmann@suse.de>
To: Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>
Cc: kexec@lists.infradead.org, Masakazu Mokuno <mokuno@sm.sony.co.jp>,
Geoff Levand <geoffrey.levand@am.sony.com>
Subject: Re: ps3-kernel hang at kexec caused by usb
Date: Wed, 23 Jul 2008 16:43:32 +0200 [thread overview]
Message-ID: <48874394.6090602@suse.de> (raw)
In-Reply-To: <4886EC22.3040805@suse.de>
Stefan Assmann wrote:
> Hey all,
>
> I'm having troubles to kexec recent kernels on Playstation 3.
> After issuing
> kexec -l <vmlinux> --initrd=<initrd>
> kexec -e
> the screen stays black.
>
> I tracked this down in the suse kernel and it seems related to a patch
> with the Subject: USB: fix interrupt disabling for HCDs with shared
> interrupt handlers.
I forgot the git commit ID from mainline, sorry.
linux-2.6 bf9127c36341573dc47a9c2fc003dcf13bbbf246
>
> This patch went mainline with 2.6.26 and the most likely reason why
> it has not been discovered yet may be because USB is compiled
> as a module in most cases. However the suse config has it compiled
> into the kernel and this causes some mischief.
>
> It would be nice if somebody could try this on other distros as well.
> I'm attaching an altered ps3_defconfig (from geoffs git) that has
> USB compiled in. So all you need to do is compile a recent kernel
> (2.6.26) with that config and it should hang right after kexec.
Stefan
--
Stefan Assmann | SUSE LINUX Products GmbH
Software Engineer | Maxfeldstr. 5, D-90409 Nuernberg
Mail : sassmann@suse.de | GF: Markus Rex, HRB 16746 (AG Nuernberg)
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2008-07-23 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 8:30 ps3-kernel hang at kexec caused by usb Stefan Assmann
2008-07-23 14:43 ` Stefan Assmann [this message]
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=48874394.6090602@suse.de \
--to=sassmann@suse.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=geoffrey.levand@am.sony.com \
--cc=kexec@lists.infradead.org \
--cc=mokuno@sm.sony.co.jp \
/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