linux-kernel - Re: kexec + USB storage in 2.6.19

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <m1mz4oe3xm.fsf@ebiederm.dsl.xmission.com>
Date:	Fri, 12 Jan 2007 07:05:09 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Dan Aloni <da-x@...atomic.org>
Cc:	Linux Kernel List <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...e.de>, linux-usb-devel@...ts.sourceforge.net
Subject: Re: kexec + USB storage in 2.6.19

Dan Aloni <da-x@...atomic.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
-
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/