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).
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
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 /
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
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
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
over 8-10 will complete also with the laptop undocked; it
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
over 8-10 will complete also with the laptop undocked; it
Added Cc: list
Il 04/03/2013 13:29, Roberto Oppedisano ha scritto:
Il 03/03/2013 01:22, Ville Syrjala ha scritto:
Roberto Oppedisano gmail.com> writes:
Hello,
with recent kernels after a suspend/resume cycle on my laptop (HP
6730b) the fans stays at full speed.
I too have been
Il 03/03/2013 01:22, Ville Syrjala ha scritto:
Roberto Oppedisano gmail.com> writes:
Hello,
with recent kernels after a suspend/resume cycle on my laptop (HP
6730b) the fans stays at full speed.
I too have been hit by this regression w/ a HP Compaq NC6000 laptop.
>From what I ca
Il 03/03/2013 01:22, Ville Syrjala ha scritto:
Roberto Oppedisano roberto.oppedisano at gmail.com writes:
Hello,
with recent kernels after a suspend/resume cycle on my laptop (HP
6730b) the fans stays at full speed.
I too have been hit by this regression w/ a HP Compaq NC6000 laptop
Added Cc: list
Il 04/03/2013 13:29, Roberto Oppedisano ha scritto:
Il 03/03/2013 01:22, Ville Syrjala ha scritto:
Roberto Oppedisano roberto.oppedisano at gmail.com writes:
Hello,
with recent kernels after a suspend/resume cycle on my laptop (HP
6730b) the fans stays at full speed.
I
next branch and the problem seems to be
gone (I tried a couple of suspend resume cycles).
Kind regards
R
--
Roberto Oppedisano
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
next branch and the problem seems to be
gone (I tried a couple of suspend resume cycles).
Kind regards
R
--
Roberto Oppedisano
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Hi,
any news about this issue ? I'm still seeing the problem with the
released 3.7 (and also with 3.7.1).
Let me know if you need more info or testing.
Kind regards
R
Il 05/12/2012 08:30, Roberto Oppedisano ha scritto:
Hello Rui
Il 04/12/2012 15:11, Zhang Rui ha scritto:
Hi, Roberto
Hi,
any news about this issue ? I'm still seeing the problem with the
released 3.7 (and also with 3.7.1).
Let me know if you need more info or testing.
Kind regards
R
Il 05/12/2012 08:30, Roberto Oppedisano ha scritto:
Hello Rui
Il 04/12/2012 15:11, Zhang Rui ha scritto:
Hi, Roberto
Jeff Garzik wrote, On 11/08/2007 07:02 PM:
> Set module option "noacpi" to 1, to disable ACPI and see if that fixes
> the problem.
>
Booting with libata.noacpi=1 fixes the problem too.
R
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
I can confirm that this patch solves the problem with s2ram on my laptop.
R
Matthew Garrett wrote:
Experience suggests that the _GTF method may be bad. We currently fail
device revalidation in that case, which seems excessive.
Signed-off-by: Matthew Garrett <[EMAIL PROTECTED]>
---
diff
I can confirm that this patch solves the problem with s2ram on my laptop.
R
Matthew Garrett wrote:
Experience suggests that the _GTF method may be bad. We currently fail
device revalidation in that case, which seems excessive.
Signed-off-by: Matthew Garrett [EMAIL PROTECTED]
---
diff --git
Jeff Garzik wrote, On 11/08/2007 07:02 PM:
Set module option noacpi to 1, to disable ACPI and see if that fixes
the problem.
Booting with libata.noacpi=1 fixes the problem too.
R
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Andrew Morton wrote, On 11/07/2007 09:13 PM:
>> On Wed, 07 Nov 2007 15:15:07 +0100 Roberto Oppedisano <[EMAIL PROTECTED]>
>> wrote:
>> Hello.
>> I noticed that after suspending to ram the DVD-ROM/CDRW
>> drive in no more recognized on my laptop. Looki
Andrew Morton wrote, On 11/07/2007 09:13 PM:
On Wed, 07 Nov 2007 15:15:07 +0100 Roberto Oppedisano [EMAIL PROTECTED]
wrote:
Hello.
I noticed that after suspending to ram the DVD-ROM/CDRW
drive in no more recognized on my laptop. Looking at dmesg
after suspend i found:
[5.313446
:00:00.0 into 4x mode
[4.837263] agpgart: Putting AGP V2 device at :01:00.0 into 4x mode
[4.837290] [drm] Loading R200 Microcode
[5.313446] ata2.00: _GTF unexpected object type 0x1
[5.313453] ata2.00: ACPI on devcfg failed the second time, disabling
(errno=-22)
[5.31
: disabled
--
Roberto Oppedisano [RO2480-RIPE]
Infracom Italia S.p.A. OSS and LIR Services
Tel. +39 045 8271518 Fax +39 045 8271499 Cell. +39 348 7419534
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
32 matches
Mail list logo
