From: ebiederm@xmission.com (Eric W. Biederman)
To: Dan Aloni <da-x@monatomic.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: kexec + USB storage in 2.6.19
Date: Fri, 12 Jan 2007 07:05:09 -0700 [thread overview]
Message-ID: <m1mz4oe3xm.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070112122444.GA28597@localdomain> (Dan Aloni's message of "Fri, 12 Jan 2007 14:24:44 +0200")
Dan Aloni <da-x@monatomic.org> writes:
> Hello,
>
> After upgrading from 2.6.18.3 to 2.6.19.2 on an x86_64 machine I noticed
> that the EHCI USB host is unable to work properly after a kexec invocation.
> This makes it impossible to mount the rootfs in the configuration I'm using.
>
> According to the prints, the irq changes from 23 to 10.
>
> NOTE: Since the device is already connected at boot, I've added a patch
> that disables the scanning delay for the first detected device, in order
> to shorten the time it takes for the boot process. It worked on 2.6.18.3,
> so I wonder what has changed...
At first glance it looks like acpi didn't come on in the kexec'd kernel.
Do you see anything like the line below.
> [ 78.139976] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ
Could your provide the full bootlogs instead of these partial ones?
There is enough context missing I don't think anyone can do more than
agree you are seeing a problem.
Eric
next prev parent reply other threads:[~2007-01-12 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 12:24 Dan Aloni
2007-01-12 14:05 ` Eric W. Biederman [this message]
2007-01-12 14:55 ` Dan Aloni
2007-01-12 14:57 ` Dan Aloni
2007-01-12 15:26 ` Eric W. Biederman
2007-01-12 16:02 ` kexec + ACPI in 2.6.19 (was: Re: kexec + USB storage in 2.6.19) Dan Aloni
2007-01-12 16:28 ` Dan Aloni
2007-01-12 16:43 ` Dan Aloni
2007-01-12 16:56 ` Dan Aloni
2007-01-12 17:33 ` Eric W. Biederman
2007-01-12 18:49 ` Dan Aloni
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=m1mz4oe3xm.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=da-x@monatomic.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®