Il 18/03/2013 00:27, Rafael J. Wysocki ha scritto:
Please try to boot with initcall_debug in the kernel command line and see
if that works around the problem and if not, whether or not it provides a
clue about the point where boot is stuck (and if that point is always the
same).
Il 18/03/2013 00:27, Rafael J. Wysocki ha scritto:
Please try to boot with initcall_debug in the kernel command line and see
if that works around the problem and if not, whether or not it provides a
clue about the point where boot is stuck (and if that point is always the
same).
On Sunday, March 17, 2013 09:32:31 AM Roberto Oppedisano wrote:
> Il 17/03/2013 01:59, Rafael J. Wysocki ha scritto:
> > On Saturday, March 16, 2013 08:10:11 AM Roberto Oppedisano wrote:
> >> Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
> Here's the new suspect:
>
>
Il 17/03/2013 01:59, Rafael J. Wysocki ha scritto:
On Saturday, March 16, 2013 08:10:11 AM Roberto Oppedisano wrote:
Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
Here's the new suspect:
f95988de06ea62ef5bd861f06e9ef56cea405ed1 is the first bad commit
commit
Il 17/03/2013 01:59, Rafael J. Wysocki ha scritto:
On Saturday, March 16, 2013 08:10:11 AM Roberto Oppedisano wrote:
Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
Here's the new suspect:
f95988de06ea62ef5bd861f06e9ef56cea405ed1 is the first bad commit
commit
On Sunday, March 17, 2013 09:32:31 AM Roberto Oppedisano wrote:
Il 17/03/2013 01:59, Rafael J. Wysocki ha scritto:
On Saturday, March 16, 2013 08:10:11 AM Roberto Oppedisano wrote:
Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
Here's the new suspect:
On Saturday, March 16, 2013 08:10:11 AM Roberto Oppedisano wrote:
> Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
> >> Here's the new suspect:
> >>
> >> f95988de06ea62ef5bd861f06e9ef56cea405ed1 is the first bad commit
> >> commit f95988de06ea62ef5bd861f06e9ef56cea405ed1
> >> Author: Rafael J.
Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
Here's the new suspect:
f95988de06ea62ef5bd861f06e9ef56cea405ed1 is the first bad commit
commit f95988de06ea62ef5bd861f06e9ef56cea405ed1
Author: Rafael J. Wysocki
Date: Mon Jan 7 21:17:02 2013 +0100
ACPI / scan: Treat power resources
Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
Here's the new suspect:
f95988de06ea62ef5bd861f06e9ef56cea405ed1 is the first bad commit
commit f95988de06ea62ef5bd861f06e9ef56cea405ed1
Author: Rafael J. Wysocki rafael.j.wyso...@intel.com
Date: Mon Jan 7 21:17:02 2013 +0100
ACPI /
On Saturday, March 16, 2013 08:10:11 AM Roberto Oppedisano wrote:
Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
Here's the new suspect:
f95988de06ea62ef5bd861f06e9ef56cea405ed1 is the first bad commit
commit f95988de06ea62ef5bd861f06e9ef56cea405ed1
Author: Rafael J. Wysocki
On Friday, March 15, 2013 02:10:24 PM Roberto Oppedisano wrote:
> Hi!
>
> Il 15/03/2013 10:42, Roberto Oppedisano ha scritto:
> > Il 14/03/2013 18:27, Rafael J. Wysocki ha scritto:
> >> On Thursday, March 14, 2013 09:20:51 AM Roberto Oppedisano wrote:
> >> As Toshi said, this particular commit
Hi!
Il 15/03/2013 10:42, Roberto Oppedisano ha scritto:
Il 14/03/2013 18:27, Rafael J. Wysocki ha scritto:
On Thursday, March 14, 2013 09:20:51 AM Roberto Oppedisano wrote:
As Toshi said, this particular commit doesn't make any functional
changes. Can you please verify if the immediately
Il 14/03/2013 15:37, Toshi Kani ha scritto:
By the boot failure, are you referring the one that is partially
captured in screeshot3.png?
yes
If so, we need full error messages (i.e.
the top of the stack trace) to see what happened.
I'll try to get it, but it could take some time (I hope
to
Il 14/03/2013 18:27, Rafael J. Wysocki ha scritto:
On Thursday, March 14, 2013 09:20:51 AM Roberto Oppedisano wrote:
As Toshi said, this particular commit doesn't make any functional
changes. Can you please verify if the immediately preceding commit
6af9a803f4d2e4137d9f74a8fc9af4857fbda001
Il 14/03/2013 18:27, Rafael J. Wysocki ha scritto:
On Thursday, March 14, 2013 09:20:51 AM Roberto Oppedisano wrote:
As Toshi said, this particular commit doesn't make any functional
changes. Can you please verify if the immediately preceding commit
6af9a803f4d2e4137d9f74a8fc9af4857fbda001
Il 14/03/2013 15:37, Toshi Kani ha scritto:
By the boot failure, are you referring the one that is partially
captured in screeshot3.png?
yes
If so, we need full error messages (i.e.
the top of the stack trace) to see what happened.
I'll try to get it, but it could take some time (I hope
to
Hi!
Il 15/03/2013 10:42, Roberto Oppedisano ha scritto:
Il 14/03/2013 18:27, Rafael J. Wysocki ha scritto:
On Thursday, March 14, 2013 09:20:51 AM Roberto Oppedisano wrote:
As Toshi said, this particular commit doesn't make any functional
changes. Can you please verify if the immediately
On Friday, March 15, 2013 02:10:24 PM Roberto Oppedisano wrote:
Hi!
Il 15/03/2013 10:42, Roberto Oppedisano ha scritto:
Il 14/03/2013 18:27, Rafael J. Wysocki ha scritto:
On Thursday, March 14, 2013 09:20:51 AM Roberto Oppedisano wrote:
As Toshi said, this particular commit doesn't make
On Thursday, March 14, 2013 09:20:51 AM Roberto Oppedisano wrote:
> Hi
>
> Il 11/03/2013 09:00, Roberto Oppedisano ha scritto:
> > Hello
> > I'm observing this kind of boot failure when my laptop
> > is not docked; I didn't notice before because I seldom reboot
> > it when it's not connected
On Thu, 2013-03-14 at 09:20 +0100, Roberto Oppedisano wrote:
> Hi
>
> Il 11/03/2013 09:00, Roberto Oppedisano ha scritto:
> > Hello
> > I'm observing this kind of boot failure when my laptop
> > is not docked; I didn't notice before because I seldom reboot
> > it when it's not connected to a
Hi
Il 11/03/2013 09:00, Roberto Oppedisano ha scritto:
Hello
I'm observing this kind of boot failure when my laptop
is not docked; I didn't notice before because I seldom reboot
it when it's not connected to a docking station.
The failure is reproducible at 80-90%, meaning that one boot
Hi
Il 11/03/2013 09:00, Roberto Oppedisano ha scritto:
Hello
I'm observing this kind of boot failure when my laptop
is not docked; I didn't notice before because I seldom reboot
it when it's not connected to a docking station.
The failure is reproducible at 80-90%, meaning that one boot
On Thu, 2013-03-14 at 09:20 +0100, Roberto Oppedisano wrote:
Hi
Il 11/03/2013 09:00, Roberto Oppedisano ha scritto:
Hello
I'm observing this kind of boot failure when my laptop
is not docked; I didn't notice before because I seldom reboot
it when it's not connected to a docking
On Thursday, March 14, 2013 09:20:51 AM Roberto Oppedisano wrote:
Hi
Il 11/03/2013 09:00, Roberto Oppedisano ha scritto:
Hello
I'm observing this kind of boot failure when my laptop
is not docked; I didn't notice before because I seldom reboot
it when it's not connected to a
24 matches
Mail list logo
