A little more
The -EEXIST matches http://marc.info/?l=linux-scsi=117699334422336=2
I had a bug fix at http://marc.info/?l=linux-scsi=117856436302690=2
Mathew's fix below superceeded my patch and supposedly also corrects it.
-- james s
PS: Emulex's testing has been with my fix. We haven't
fyi
I've seen these before (and they haven't been specific to the LLDD).
The "-EEXIST" error, was an issue of rescan-while-deleting, and where
refcounts held the old sdevs in place. They were ramant in 2.6.18/2.6.19.
Supposedly, we had patches from Hannes Reinecke. to resolve it, but that
On Tue, Aug 14, 2007 at 11:10:22AM +0200, Tore Anderson wrote:
> I gave it a spin, and got quite a few troubles that appears related to
> the lpfc driver. I don't know if these problems happened due to the
> recent update as the latest kernel I ran before was 2.6.20 (where I
> never saw
Hello Michal,
This morning I have booted laptop, for a while fan had been turned off.
But then after a light load (compiling stuff & co), fan was turned on
and now it is still on.
[EMAIL PROTECTED]:~$ acpi -bt
Battery 1: charged, 97%
Thermal 1: ok, 48.0 degrees C
Thermal 2: ok,
Hello,
I have also noticed that there are other messages printed twice, not a
big problem but still ;) . Perhaps it should be that way, don't know.
$ dmesg | grep sda
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode
Hello,
I have also noticed that there are other messages printed twice, not a
big problem but still ;) . Perhaps it should be that way, don't know.
$ dmesg | grep sda
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode
Hello Michal,
This morning I have booted laptop, for a while fan had been turned off.
But then after a light load (compiling stuff co), fan was turned on
and now it is still on.
[EMAIL PROTECTED]:~$ acpi -bt
Battery 1: charged, 97%
Thermal 1: ok, 48.0 degrees C
Thermal 2: ok,
On Tue, Aug 14, 2007 at 11:10:22AM +0200, Tore Anderson wrote:
I gave it a spin, and got quite a few troubles that appears related to
the lpfc driver. I don't know if these problems happened due to the
recent update as the latest kernel I ran before was 2.6.20 (where I
never saw problems
fyi
I've seen these before (and they haven't been specific to the LLDD).
The -EEXIST error, was an issue of rescan-while-deleting, and where
refcounts held the old sdevs in place. They were ramant in 2.6.18/2.6.19.
Supposedly, we had patches from Hannes Reinecke. to resolve it, but that
was
A little more
The -EEXIST matches http://marc.info/?l=linux-scsim=117699334422336w=2
I had a bug fix at http://marc.info/?l=linux-scsim=117856436302690w=2
Mathew's fix below superceeded my patch and supposedly also corrects it.
-- james s
PS: Emulex's testing has been with my fix. We
* James Smart
I've seen these before (and they haven't been specific to the LLDD).
You're probably right. I saw trouble happening when lpfc was in
action and thought it might have something to do with it, but then
again I'm not very intimate with the inner workings of the kernel.
If you
Hi Zilvinas,
On 13/08/07, Zilvinas Valinskas <[EMAIL PROTECTED]> wrote:
> Hello lkml,
>
> Linux kernel v2.6.23-rc3 booted ok and so far everything is fine. I have
> HP Compaq nx9420 laptop (Dual Core).
>
> Just a few things that I found interesting:
>
> 1.
Hello lkml,
Linux kernel v2.6.23-rc3 booted ok and so far everything is fine. I have
HP Compaq nx9420 laptop (Dual Core).
Just a few things that I found interesting:
1. /sys/devices/system/clocksource/clocksource0/*
$ sudo grep . *
available_clocksource:hpet hpet acpi_pm jiffies tsc
Hi,
On 13/08/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> Either people really are calming down, and figuring out that we're in the
> stabilization phase, or it's just that it's the middle of August, and
> most everybody at least in Europe are off on vacation.
Yeah right.
I will fill a bug
Hi,
On 13/08/07, Linus Torvalds [EMAIL PROTECTED] wrote:
Either people really are calming down, and figuring out that we're in the
stabilization phase, or it's just that it's the middle of August, and
most everybody at least in Europe are off on vacation.
Yeah right.
I will fill a bug
Hello lkml,
Linux kernel v2.6.23-rc3 booted ok and so far everything is fine. I have
HP Compaq nx9420 laptop (Dual Core).
Just a few things that I found interesting:
1. /sys/devices/system/clocksource/clocksource0/*
$ sudo grep . *
available_clocksource:hpet hpet acpi_pm jiffies tsc
Hi Zilvinas,
On 13/08/07, Zilvinas Valinskas [EMAIL PROTECTED] wrote:
Hello lkml,
Linux kernel v2.6.23-rc3 booted ok and so far everything is fine. I have
HP Compaq nx9420 laptop (Dual Core).
Just a few things that I found interesting:
1. /sys/devices/system/clocksource/clocksource0/*
$
s to handle AOpen's broken Award BIOS
Linus Torvalds (3):
Revert "genirq: temporary fix for level-triggered IRQ resend"
i386: Fix broken mmiocfg accesses
Linux 2.6.23-rc3
Mariusz Kozlowski (3):
drivers/net/ibmveth.c: memset fix
drivers/block/cciss.c: kmalloc + m
mmiocfg accesses
Linux 2.6.23-rc3
Mariusz Kozlowski (3):
drivers/net/ibmveth.c: memset fix
drivers/block/cciss.c: kmalloc + memset conversion to kzalloc
drivers/block/cpqarray.c: better error handling and kmalloc + memset
conversion to k[cz]alloc
Mark Fasheh (6
On 8/8/07, David Weinehall <[EMAIL PROTECTED]> wrote:
> Try adding acpi_sleep=s3_bios to your kernel boot options and see if it
> helps.
I tried, but that didn't help.
Thanks,
Jeff.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Sun, Aug 05, 2007 at 07:52:07PM +0800, Jeff Chua wrote:
> On 8/5/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>
> > Okay, since you're using VGA console this means suspend-to-ram isn't
> > restoring the mode.
> > Does it matter if you suspend from inside X or not?
>
> Just tested it. It
On Sun, Aug 05, 2007 at 07:52:07PM +0800, Jeff Chua wrote:
On 8/5/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Okay, since you're using VGA console this means suspend-to-ram isn't
restoring the mode.
Does it matter if you suspend from inside X or not?
Just tested it. It doesn't
On 8/8/07, David Weinehall [EMAIL PROTECTED] wrote:
Try adding acpi_sleep=s3_bios to your kernel boot options and see if it
helps.
I tried, but that didn't help.
Thanks,
Jeff.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
Here's my dmesg ...
Thanks,
Jeff
Linux version 2.6.23-rc2 ([EMAIL PROTECTED]) (gcc version 3.4.5) #5 SMP PREEMPT
Sat Aug 4 13:03:10 SGT 2007
BIOS-provided physical RAM map:
BIOS-e820: - 0009f000 (usable)
BIOS-e820: 0009f000 - 000a (reserved)
Jeff Chua wrote:
> On 8/7/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>
>> Does it show little penguins as the system boots?
>
> No I don't have that. I'm not using a "splash" screen in grub2. And
> funny thing is I don't get any problem up to 2.6.22.
>
I asked you about AS THE KERNEL IS
On 8/7/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> Does it show little penguins as the system boots?
No I don't have that. I'm not using a "splash" screen in grub2. And
funny thing is I don't get any problem up to 2.6.22.
Thanks,
Jeff.
-
To unsubscribe from this list: send the line
Jeff Chua wrote:
> On 8/7/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>> Indan Zupancic wrote:
>>> I thought he was using a VGA console, wouldn't that be in text mode?
>>>
>> That is, exactly, the problem. It should be, it's not.
>
> The text-console is the VGA console right? I hope we're
On 8/7/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> Indan Zupancic wrote:
> >
> > I thought he was using a VGA console, wouldn't that be in text mode?
> >
>
> That is, exactly, the problem. It should be, it's not.
The text-console is the VGA console right? I hope we're refering to
the same
On 8/7/07, Indan Zupancic <[EMAIL PROTECTED]> wrote:
> Does executing unicode_start, unicode_stop fixes it?
Doesn't seem to fix it. Now that I've to type blinding, I realised
that the text-console is about 1/20 of the whole screen size. If I
hold on to ENTER key, I could see the screen scroll.
On Monday, 6 August 2007 18:40, H. Peter Anvin wrote:
> Rafael J. Wysocki wrote:
> > On Monday, 6 August 2007 02:36, Jeff Chua wrote:
> >> On 8/6/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> >>
> >>> What does 's2ram -i' say about your machine?
> >> This machine can be identified by:
> >>
Indan Zupancic wrote:
>
> I thought he was using a VGA console, wouldn't that be in text mode?
>
That is, exactly, the problem. It should be, it's not.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Mon, August 6, 2007 19:16, H. Peter Anvin wrote:
> Indan Zupancic wrote:
>>
>> Does executing unicode_start, unicode_stop fixes it?
>>
>
> Does that seem likely, since his display isn't even in text mode?
No idea, just thought it would be worth a try. My console is garbled
too, doing that
Indan Zupancic wrote:
>
> Does executing unicode_start, unicode_stop fixes it?
>
Does that seem likely, since his display isn't even in text mode?
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
On Mon, August 6, 2007 18:06, Jeff Chua wrote:
> On 8/6/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
>> >���
>> That looks pretty much like all-one-bits (� = 255).
>> What about vcsa1 (use hexdump -C)?
>
> # hexdump -C /dev/vcsa1
> 19 50 00 18 ff ff
Rafael J. Wysocki wrote:
> On Monday, 6 August 2007 02:36, Jeff Chua wrote:
>> On 8/6/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>>
>>> What does 's2ram -i' say about your machine?
>> This machine can be identified by:
>> sys_vendor = "LENOVO"
>> sys_product = "1702E7A"
>>
On Aug 7 2007 00:06, Jeff Chua wrote:
>On 8/6/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
>> >ÿÿÿ
>> That looks pretty much like all-one-bits (ÿ = 255).
>> What about vcsa1 (use hexdump -C)?
>
># hexdump -C /dev/vcsa1
> 19 50 00 18 ff ff ff ff ff
On 8/6/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> >ÿÿÿ
> That looks pretty much like all-one-bits (ÿ = 255).
> What about vcsa1 (use hexdump -C)?
# hexdump -C /dev/vcsa1
19 50 00 18 ff ff ff ff ff ff ff ff ff ff ff ff |.P..|
On Aug 5 2007 21:26, Jeff Chua wrote:
>Here's what see when I "cat /dev/vcs1" ...
>
>ÿÿÿ
>
>The pattern repeats and fill the whole screen.
That looks pretty much like all-one-bits (ÿ = 255).
What about vcsa1 (use hexdump -C)?
Jan
--
On 8/6/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> This means it's not in the whitelist, AFAICS.
>
> Similar machines are known to work with "--acpi_sleep=3" or with
> "--acpi_sleep=1 --vbe_mode".
Good news.
"s2ram --force --acpi_sleep 1 --vbe_mode" works.
I also tried "--acpi_sleep=3",
On Monday, 6 August 2007 02:36, Jeff Chua wrote:
> On 8/6/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > What does 's2ram -i' say about your machine?
>
> This machine can be identified by:
> sys_vendor = "LENOVO"
> sys_product = "1702E7A"
> sys_version = "ThinkPad X60s"
>
On Monday, 6 August 2007 02:36, Jeff Chua wrote:
On 8/6/07, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
What does 's2ram -i' say about your machine?
This machine can be identified by:
sys_vendor = LENOVO
sys_product = 1702E7A
sys_version = ThinkPad X60s
bios_version
On 8/6/07, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
This means it's not in the whitelist, AFAICS.
Similar machines are known to work with --acpi_sleep=3 or with
--acpi_sleep=1 --vbe_mode.
Good news.
s2ram --force --acpi_sleep 1 --vbe_mode works.
I also tried --acpi_sleep=3, but that
On Aug 5 2007 21:26, Jeff Chua wrote:
Here's what see when I cat /dev/vcs1 ...
ÿÿÿ
The pattern repeats and fill the whole screen.
That looks pretty much like all-one-bits (ÿ = 255).
What about vcsa1 (use hexdump -C)?
Jan
--
On 8/6/07, Jan Engelhardt [EMAIL PROTECTED] wrote:
ÿÿÿ
That looks pretty much like all-one-bits (ÿ = 255).
What about vcsa1 (use hexdump -C)?
# hexdump -C /dev/vcsa1
19 50 00 18 ff ff ff ff ff ff ff ff ff ff ff ff |.P..|
0010 ff
On Aug 7 2007 00:06, Jeff Chua wrote:
On 8/6/07, Jan Engelhardt [EMAIL PROTECTED] wrote:
ÿÿÿ
That looks pretty much like all-one-bits (ÿ = 255).
What about vcsa1 (use hexdump -C)?
# hexdump -C /dev/vcsa1
19 50 00 18 ff ff ff ff ff ff ff ff ff ff
Rafael J. Wysocki wrote:
On Monday, 6 August 2007 02:36, Jeff Chua wrote:
On 8/6/07, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
What does 's2ram -i' say about your machine?
This machine can be identified by:
sys_vendor = LENOVO
sys_product = 1702E7A
sys_version = ThinkPad
On Mon, August 6, 2007 18:06, Jeff Chua wrote:
On 8/6/07, Jan Engelhardt [EMAIL PROTECTED] wrote:
���
That looks pretty much like all-one-bits (� = 255).
What about vcsa1 (use hexdump -C)?
# hexdump -C /dev/vcsa1
19 50 00 18 ff ff ff ff ff ff
Indan Zupancic wrote:
Does executing unicode_start, unicode_stop fixes it?
Does that seem likely, since his display isn't even in text mode?
-hpa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Mon, August 6, 2007 19:16, H. Peter Anvin wrote:
Indan Zupancic wrote:
Does executing unicode_start, unicode_stop fixes it?
Does that seem likely, since his display isn't even in text mode?
No idea, just thought it would be worth a try. My console is garbled
too, doing that unicode stuff
Indan Zupancic wrote:
I thought he was using a VGA console, wouldn't that be in text mode?
That is, exactly, the problem. It should be, it's not.
-hpa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
On Monday, 6 August 2007 18:40, H. Peter Anvin wrote:
Rafael J. Wysocki wrote:
On Monday, 6 August 2007 02:36, Jeff Chua wrote:
On 8/6/07, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
What does 's2ram -i' say about your machine?
This machine can be identified by:
sys_vendor =
On 8/7/07, Indan Zupancic [EMAIL PROTECTED] wrote:
Does executing unicode_start, unicode_stop fixes it?
Doesn't seem to fix it. Now that I've to type blinding, I realised
that the text-console is about 1/20 of the whole screen size. If I
hold on to ENTER key, I could see the screen scroll. But
On 8/7/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Indan Zupancic wrote:
I thought he was using a VGA console, wouldn't that be in text mode?
That is, exactly, the problem. It should be, it's not.
The text-console is the VGA console right? I hope we're refering to
the same thing. It's
Jeff Chua wrote:
On 8/7/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Indan Zupancic wrote:
I thought he was using a VGA console, wouldn't that be in text mode?
That is, exactly, the problem. It should be, it's not.
The text-console is the VGA console right? I hope we're refering to
the
On 8/7/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Does it show little penguins as the system boots?
No I don't have that. I'm not using a splash screen in grub2. And
funny thing is I don't get any problem up to 2.6.22.
Thanks,
Jeff.
-
To unsubscribe from this list: send the line unsubscribe
Jeff Chua wrote:
On 8/7/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Does it show little penguins as the system boots?
No I don't have that. I'm not using a splash screen in grub2. And
funny thing is I don't get any problem up to 2.6.22.
I asked you about AS THE KERNEL IS BOOTING, not
Here's my dmesg ...
Thanks,
Jeff
Linux version 2.6.23-rc2 ([EMAIL PROTECTED]) (gcc version 3.4.5) #5 SMP PREEMPT
Sat Aug 4 13:03:10 SGT 2007
BIOS-provided physical RAM map:
BIOS-e820: - 0009f000 (usable)
BIOS-e820: 0009f000 - 000a (reserved)
On 8/6/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> What does 's2ram -i' say about your machine?
This machine can be identified by:
sys_vendor = "LENOVO"
sys_product = "1702E7A"
sys_version = "ThinkPad X60s"
bios_version = "7BETD0WW (2.11 )"
Thanks,
Jeff.
-
To
On Sunday, 5 August 2007 15:26, Jeff Chua wrote:
> On 8/5/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
>
> > Can you try with the boot option acpi_sleep=s3_bios,s3_mode
> > OR
> > if using s2ram, use s2ram -f a3
>
> Tried both, text-console still not restored.
>
> In fact, with "s2ram -f
On 8/5/07, Antonino A. Daplas <[EMAIL PROTECTED]> wrote:
> Can you try with the boot option acpi_sleep=s3_bios,s3_mode
> OR
> if using s2ram, use s2ram -f a3
Tried both, text-console still not restored.
In fact, with "s2ram -f a3", backlight doesn't get restored. I've to
switch to F1 and back
On Sun, 2007-08-05 at 20:11 +0800, Jeff Chua wrote:
> On 8/5/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> > Also, please submit your .config and kernel command line.
>
> # cat /proc/cmdline
>
> BOOT_IMAGE=(hd0,14)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 reboot=bios
>
>
Can you try with
On 8/5/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
Also, please submit your .config and kernel command line.
# cat /proc/cmdline
BOOT_IMAGE=(hd0,14)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 reboot=bios
Below is my .config ...
#
# Automatically generated make config: don't edit
# Linux
On 8/5/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> I thought that the X server did all that on its own these days, but that may
> be just the newer "intel" driver, not the older "i810" driver that you
> probably use.
I've just checked. Upon boot-up into text-console (even without
starting
On 8/5/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> Okay, since you're using VGA console this means suspend-to-ram isn't
> restoring the mode.
> Does it matter if you suspend from inside X or not?
Just tested it. It doesn't matter... text console still messed up. X
is ok after resume.
On Sunday, 5 August 2007 15:26, Jeff Chua wrote:
On 8/5/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
Can you try with the boot option acpi_sleep=s3_bios,s3_mode
OR
if using s2ram, use s2ram -f a3
Tried both, text-console still not restored.
In fact, with s2ram -f a3, backlight
On 8/6/07, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
What does 's2ram -i' say about your machine?
This machine can be identified by:
sys_vendor = LENOVO
sys_product = 1702E7A
sys_version = ThinkPad X60s
bios_version = 7BETD0WW (2.11 )
Thanks,
Jeff.
-
To unsubscribe from
On 8/5/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Okay, since you're using VGA console this means suspend-to-ram isn't
restoring the mode.
Does it matter if you suspend from inside X or not?
Just tested it. It doesn't matter... text console still messed up. X
is ok after resume.
Thanks,
On 8/5/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Also, please submit your .config and kernel command line.
# cat /proc/cmdline
BOOT_IMAGE=(hd0,14)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 reboot=bios
Below is my .config ...
#
# Automatically generated make config: don't edit
# Linux
On 8/5/07, Linus Torvalds [EMAIL PROTECTED] wrote:
I thought that the X server did all that on its own these days, but that may
be just the newer intel driver, not the older i810 driver that you
probably use.
I've just checked. Upon boot-up into text-console (even without
starting X),
On Sun, 2007-08-05 at 20:11 +0800, Jeff Chua wrote:
On 8/5/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Also, please submit your .config and kernel command line.
# cat /proc/cmdline
BOOT_IMAGE=(hd0,14)/linux/bzc1 root=/dev/sda2 resume=/dev/sda3 reboot=bios
Can you try with the boot
On 8/5/07, Antonino A. Daplas [EMAIL PROTECTED] wrote:
Can you try with the boot option acpi_sleep=s3_bios,s3_mode
OR
if using s2ram, use s2ram -f a3
Tried both, text-console still not restored.
In fact, with s2ram -f a3, backlight doesn't get restored. I've to
switch to F1 and back to X to
Jeff Chua wrote:
> On 8/5/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>
>> Also, can you please describe "messed up" in more detail?
>
> The screen went into some graphic mode that can't be reset no matter
> what I tried (stty reset). I see all kinds of ramdom pattern/color
> everywhere. Then
On 8/5/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> Also, can you please describe "messed up" in more detail?
The screen went into some graphic mode that can't be reset no matter
what I tried (stty reset). I see all kinds of ramdom pattern/color
everywhere. Then typing "startx" would get in X
On 8/5/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Jeff - do I understand correctly that the "or" means that even *without* a
> suspend-to-ram sequence, and just by going into X and then going back to
> text-mode, the screen is corrupt?
I've done more tests. It seems that "suspend-to-ram"
On Saturday, 4 August 2007 12:30, Rafael J. Wysocki wrote:
> On Saturday, 4 August 2007 05:50, Linus Torvalds wrote:
> >
> > So I tried to hold people to the merge window, and said no to a few pull
> > requests, but this whole "-rc2 is the new -rc1" thing is a disease, and
> > not only is -rc2
On Sat, 2007-08-04 at 11:06 -0700, H. Peter Anvin wrote:
> Linus Torvalds wrote:
> >
> > On Sat, 4 Aug 2007, Jeff Chua wrote:
> >> On 8/4/07, Jeff Chua <[EMAIL PROTECTED]> wrote:
> After resume from s2ram or switching to console from X, my console is
> messed up on rc1 and rc2. Is there
Linus Torvalds wrote:
>
> On Sat, 4 Aug 2007, Jeff Chua wrote:
>> On 8/4/07, Jeff Chua <[EMAIL PROTECTED]> wrote:
After resume from s2ram or switching to console from X, my console is
messed up on rc1 and rc2. Is there a fix for this?
>>> This is on IBM X60. i915 chipset. No problem on
On Sat, 4 Aug 2007, Jeff Chua wrote:
>
> On 8/4/07, Jeff Chua <[EMAIL PROTECTED]> wrote:
> >
> > > After resume from s2ram or switching to console from X, my console is
> > > messed up on rc1 and rc2. Is there a fix for this?
> >
> > This is on IBM X60. i915 chipset. No problem on 2.6.22. If
On 8/4/07, Jeff Chua <[EMAIL PROTECTED]> wrote:
> > After resume from s2ram or switching to console from X, my console is
> > messed up on rc1 and rc2. Is there a fix for this?
>
> This is on IBM X60. i915 chipset. No problem on 2.6.22. If this is a
> known problem, than I don't need to bisect
On Saturday, 4 August 2007 05:50, Linus Torvalds wrote:
>
> So I tried to hold people to the merge window, and said no to a few pull
> requests, but this whole "-rc2 is the new -rc1" thing is a disease, and
> not only is -rc2 late, it's bigger than it should be. Oh, well.
Suspend and
On Saturday, 4 August 2007 05:50, Linus Torvalds wrote:
So I tried to hold people to the merge window, and said no to a few pull
requests, but this whole -rc2 is the new -rc1 thing is a disease, and
not only is -rc2 late, it's bigger than it should be. Oh, well.
Suspend and hibernation are
On 8/4/07, Jeff Chua [EMAIL PROTECTED] wrote:
After resume from s2ram or switching to console from X, my console is
messed up on rc1 and rc2. Is there a fix for this?
This is on IBM X60. i915 chipset. No problem on 2.6.22. If this is a
known problem, than I don't need to bisect all over
On Sat, 4 Aug 2007, Jeff Chua wrote:
On 8/4/07, Jeff Chua [EMAIL PROTECTED] wrote:
After resume from s2ram or switching to console from X, my console is
messed up on rc1 and rc2. Is there a fix for this?
This is on IBM X60. i915 chipset. No problem on 2.6.22. If this is a
known
Linus Torvalds wrote:
On Sat, 4 Aug 2007, Jeff Chua wrote:
On 8/4/07, Jeff Chua [EMAIL PROTECTED] wrote:
After resume from s2ram or switching to console from X, my console is
messed up on rc1 and rc2. Is there a fix for this?
This is on IBM X60. i915 chipset. No problem on 2.6.22. If this
On Sat, 2007-08-04 at 11:06 -0700, H. Peter Anvin wrote:
Linus Torvalds wrote:
On Sat, 4 Aug 2007, Jeff Chua wrote:
On 8/4/07, Jeff Chua [EMAIL PROTECTED] wrote:
After resume from s2ram or switching to console from X, my console is
messed up on rc1 and rc2. Is there a fix for this?
On Saturday, 4 August 2007 12:30, Rafael J. Wysocki wrote:
On Saturday, 4 August 2007 05:50, Linus Torvalds wrote:
So I tried to hold people to the merge window, and said no to a few pull
requests, but this whole -rc2 is the new -rc1 thing is a disease, and
not only is -rc2 late, it's
On 8/5/07, Linus Torvalds [EMAIL PROTECTED] wrote:
Jeff - do I understand correctly that the or means that even *without* a
suspend-to-ram sequence, and just by going into X and then going back to
text-mode, the screen is corrupt?
I've done more tests. It seems that suspend-to-ram sequence is
On 8/5/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Also, can you please describe messed up in more detail?
The screen went into some graphic mode that can't be reset no matter
what I tried (stty reset). I see all kinds of ramdom pattern/color
everywhere. Then typing startx would get in X just
Jeff Chua wrote:
On 8/5/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Also, can you please describe messed up in more detail?
The screen went into some graphic mode that can't be reset no matter
what I tried (stty reset). I see all kinds of ramdom pattern/color
everywhere. Then typing
On 8/4/07, Jeff Chua <[EMAIL PROTECTED]> wrote:
> On 8/4/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> After resume from s2ram or switching to console from X, my console is
> messed up on rc1 and rc2. Is there a fix for this?
This is on IBM X60. i915 chipset. No problem on 2.6.22. If this is a
On 8/4/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> A lot of the changes are small, and a lot of them really are fixes, but
> there's a MIPS merge in there too, and some absolutely _huge_ diffs due to
> some drivers undergoing Lindent cleanups (28 _thousand_ lines changes in
> advansys.c, and
On Fri, 3 Aug 2007, Linus Torvalds wrote:
So I tried to hold people to the merge window, and said no to a few pull
requests, but this whole "-rc2 is the new -rc1" thing is a disease, and
not only is -rc2 late, it's bigger than it should be. Oh, well.
I don't think this is new, -rc1 has always
So I tried to hold people to the merge window, and said no to a few pull
requests, but this whole "-rc2 is the new -rc1" thing is a disease, and
not only is -rc2 late, it's bigger than it should be. Oh, well.
A lot of the changes are small, and a lot of them really are fixes, but
there's a
So I tried to hold people to the merge window, and said no to a few pull
requests, but this whole -rc2 is the new -rc1 thing is a disease, and
not only is -rc2 late, it's bigger than it should be. Oh, well.
A lot of the changes are small, and a lot of them really are fixes, but
there's a MIPS
On Fri, 3 Aug 2007, Linus Torvalds wrote:
So I tried to hold people to the merge window, and said no to a few pull
requests, but this whole -rc2 is the new -rc1 thing is a disease, and
not only is -rc2 late, it's bigger than it should be. Oh, well.
I don't think this is new, -rc1 has always
On 8/4/07, Linus Torvalds [EMAIL PROTECTED] wrote:
A lot of the changes are small, and a lot of them really are fixes, but
there's a MIPS merge in there too, and some absolutely _huge_ diffs due to
some drivers undergoing Lindent cleanups (28 _thousand_ lines changes in
advansys.c, and the
On 8/4/07, Jeff Chua [EMAIL PROTECTED] wrote:
On 8/4/07, Linus Torvalds [EMAIL PROTECTED] wrote:
After resume from s2ram or switching to console from X, my console is
messed up on rc1 and rc2. Is there a fix for this?
This is on IBM X60. i915 chipset. No problem on 2.6.22. If this is a
known
501 - 597 of 597 matches
Mail list logo
