Hi.
On Thu, 2007-04-19 at 00:22 +0200, Christian Hesse wrote:
On Thursday 19 April 2007, Ingo Molnar wrote:
* Christian Hesse [EMAIL PROTECTED] wrote:
although probably your suspend2 problem is still not fixed, it's
worth a try nevertheless. Which suspend2 patch did you apply, and
Hi.
On Wed, 2007-04-18 at 18:56 -0400, Bob Picco wrote:
Ingo Molnar wrote:[Wed Apr 18 2007, 06:02:28PM EDT]
* Christian Hesse [EMAIL PROTECTED] wrote:
although probably your suspend2 problem is still not fixed, it's
worth a try nevertheless. Which suspend2 patch did you
Hi.
On Thu, 2007-04-19 at 00:02 +0200, Ingo Molnar wrote:
* Christian Hesse [EMAIL PROTECTED] wrote:
although probably your suspend2 problem is still not fixed, it's
worth a try nevertheless. Which suspend2 patch did you apply, and
was it against -rc6 or -rc7?
You are right
Hi Ingo.
On Thu, 2007-04-19 at 09:04 +0200, Ingo Molnar wrote:
* Nigel Cunningham [EMAIL PROTECTED] wrote:
From subsequent emails, I think you already got your answer, but just
in case...
Yes, if you enabled Replace swsusp by default and you already had it
set up for getting
Hi.
On Fri, 2007-04-20 at 14:45 +0300, Avi Kivity wrote:
Andi Kleen wrote:
Xavier Bestel [EMAIL PROTECTED] writes:
On Fri, 2007-04-20 at 00:46 +0200, roland wrote:
We just quietly added an exciting feature to Workstation 6.0. I believe
it
will make WS6 a great tool
Hi.
On Fri, 2007-04-20 at 04:21 -0700, Petr Vandrovec wrote:
Andi Kleen wrote:
Xavier Bestel [EMAIL PROTECTED] writes:
On Fri, 2007-04-20 at 00:46 +0200, roland wrote:
We just quietly added an exciting feature to Workstation 6.0. I believe
it
will make WS6 a great tool for Linux
Hi all.
I've been working on this email on and off for a while, but since Pavel
raised the issue again, I thought I should make a concerted effort to
finish it...
In this email, I'm going to outline the problems with the current design
(uswsusp and swsusp) and the ways in which Suspend2
Hi.
On Wed, 2007-04-25 at 07:29 +, Pavel Machek wrote:
Hi!
I absolutely detest all suspend-to-disk crap. Quite frankly, I hate
the whole thing. I think they've _all_ caused problems for the true
suspend (suspend-to-ram), and the last thing I want to see is three or
four
Hi.
On Wed, 2007-04-25 at 10:48 +0200, Xavier Bestel wrote:
On Wed, 2007-04-25 at 07:23 +, Pavel Machek wrote:
I absolutely detest all suspend-to-disk crap. Quite frankly, I hate the
whole thing. I think they've _all_ caused problems for the true suspend
(suspend-to-ram), and the
Hi.
On Wed, 2007-04-25 at 11:07 +0200, Xavier Bestel wrote:
On Wed, 2007-04-25 at 18:50 +1000, Nigel Cunningham wrote:
(And guess what, it uses APM and suspend is really faster and way more
reliable than each kernel implementation I could try).
If you tried Suspend2 and had problems
Hi.
On Fri, 2007-03-09 at 23:03 -0500, [EMAIL PROTECTED] wrote:
On Sat, 10 Mar 2007 09:57:32 +1100, Rusty Russell said:
+/* GCC is awesome. */
#define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0])
\
+ sizeof(typeof(int[1 -
Hi.
On Sat, 2007-02-10 at 23:20 +0100, Rafael J. Wysocki wrote:
Hi,
On Saturday, 10 February 2007 20:38, Pavel Machek wrote:
Hi!
I don't think this is already done (feel free to correct me if I'm
wrong)..
Can we start to NAK new drivers that don't have proper power
Hi.
On Sun, 2007-02-11 at 22:52 +0100, Willy Tarreau wrote:
On Sun, Feb 11, 2007 at 12:31:14PM -0600, Robert Hancock wrote:
Willy Tarreau wrote:
Nigel, don't take it as a personal offense, but I think it is a very
centric view of Linux usages. Where I work, Linux is used a lot on
servers
Hi.
On Sun, 2007-02-11 at 00:45 +0100, Tilman Schmidt wrote:
Am 10.02.2007 23:37 schrieb Nigel Cunningham:
If your device requires power management, and you know it requires power
management, why not just implement power management? Doing -ENOSYS
instead is like saying
Hi.
On Sun, 2007-02-11 at 01:44 +0100, Rafael J. Wysocki wrote:
Well, it's probably more acceptable than silently doing nothing and the
device failing or locking up the machine on resume, but I couldn't agree
more that it's not what we want to be encouraging. Perfect may be the
enemy
On Sun, 2007-02-11 at 01:27 +0100, Rafael J. Wysocki wrote:
On Sunday, 11 February 2007 00:45, Tilman Schmidt wrote:
Am 10.02.2007 23:37 schrieb Nigel Cunningham:
If your device requires power management, and you know it requires power
management, why not just implement power management
Hi.
On Sun, 2007-02-11 at 07:46 +0100, Willy Tarreau wrote:
Hi Nigel,
On Sun, Feb 11, 2007 at 09:37:06AM +1100, Nigel Cunningham wrote:
On Sat, 2007-02-10 at 23:20 +0100, Rafael J. Wysocki wrote:
(...)
What about this:
If the device requires that, implement .suspend and .resume
Hi.
On Sun, 2007-02-11 at 12:13 +, Matthew Garrett wrote:
On Sun, Feb 11, 2007 at 07:54:04AM +0100, Willy Tarreau wrote:
instead of modifying all drivers to explicitly state that they don't support
it, we should start with a test of the NULL pointer for .suspend which
should
mean
Hi.
On Sun, 2007-02-11 at 19:53 +0100, Rafael J. Wysocki wrote:
Having drivers explicitly marked as to whether they are safe is a good
kernel
feature; what to do if they're not is policy.
That's true, but I assume that the people who opt for doing that are also
willing to take part in
Hi.
On Sun, 2007-02-11 at 21:02 +, Alan wrote:
If the device requires that, implement .suspend and .resume or at least
define .suspend that will always return -ENOSYS (then people will know
they
have to unload the driver before the suspend). Similarly, if you aren't
sure
Hi.
On Sun, 2007-02-11 at 23:46 +0100, Willy Tarreau wrote:
On Sun, 2007-02-11 at 22:52 +0100, Willy Tarreau wrote:
On Sun, Feb 11, 2007 at 12:31:14PM -0600, Robert Hancock wrote:
Willy Tarreau wrote:
Nigel, don't take it as a personal offense, but I think it is a very
centric
Hi.
On Mon, 2007-02-12 at 02:57 +0400, Manu Abraham wrote:
On 2/12/07, Nigel Cunningham [EMAIL PROTECTED] wrote:
Neither am I. I'm just asking that new drivers have power management as
standard.
What if the hardware doesn't support power management ?
You would still want to do
Hi.
On Mon, 2007-02-12 at 00:16 +0100, Rafael J. Wysocki wrote:
On Monday, 12 February 2007 00:10, Nigel Cunningham wrote:
Hi.
On Sun, 2007-02-11 at 21:02 +, Alan wrote:
If the device requires that, implement .suspend and .resume or at
least
define .suspend
Hi.
On Mon, 2007-02-12 at 00:21 +0100, Pavel Machek wrote:
Hi!
define .suspend that will always return -ENOSYS (then people will
know they
have to unload the driver before the suspend). Similarly, if you
aren't sure
whether or not the device requires .suspend and
Hi.
On Mon, 2007-02-12 at 03:25 +0400, Manu Abraham wrote:
On 2/12/07, Nigel Cunningham [EMAIL PROTECTED] wrote:
Hi.
On Mon, 2007-02-12 at 02:57 +0400, Manu Abraham wrote:
On 2/12/07, Nigel Cunningham [EMAIL PROTECTED] wrote:
Neither am I. I'm just asking that new drivers have
Hi.
On Mon, 2007-02-12 at 00:29 +0100, Rafael J. Wysocki wrote:
On Sun, 2007-02-11 at 01:44 +0100, Rafael J. Wysocki wrote:
Well, it's probably more acceptable than silently doing nothing and the
device failing or locking up the machine on resume, but I couldn't
agree
more
Hi.
On Mon, 2007-02-12 at 00:38 +0100, Willy Tarreau wrote:
On Mon, Feb 12, 2007 at 10:18:42AM +1100, Nigel Cunningham wrote:
[snip]
Hmm sorry, but we don't have the same usages of notebooks. For no reason
would I keep documents open, for two reasons :
- when I shutdown my
Hi.
On Mon, 2007-02-12 at 00:41 +0100, Rafael J. Wysocki wrote:
I'm using M$ hibernation and Suspend2 to dual boot on our desktop (dtv
card that Linux doesn't support well yet), and I know other Suspend2
users doing the same. It's made earier by the fact that Suspend2 lets
you reboot
Hi.
On Mon, 2007-02-12 at 00:50 +0100, Rafael J. Wysocki wrote:
On Monday, 12 February 2007 00:47, Nigel Cunningham wrote:
Hi.
On Mon, 2007-02-12 at 00:41 +0100, Rafael J. Wysocki wrote:
I'm using M$ hibernation and Suspend2 to dual boot on our desktop (dtv
card that Linux doesn't
Hi.
On Mon, 2007-02-12 at 01:09 +0100, Rafael J. Wysocki wrote:
On Monday, 12 February 2007 00:55, Nigel Cunningham wrote:
Hi.
On Mon, 2007-02-12 at 00:50 +0100, Rafael J. Wysocki wrote:
On Monday, 12 February 2007 00:47, Nigel Cunningham wrote:
Hi.
On Mon, 2007-02-12
Howdy!
On Mon, 2007-02-12 at 01:10 +0100, Tilman Schmidt wrote:
Hi,
Am 11.02.2007 23:37 schrieb Nigel Cunningham:
On Sun, 2007-02-11 at 00:45 +0100, Tilman Schmidt wrote:
Am 10.02.2007 23:37 schrieb Nigel Cunningham:
If your device requires power management, and you know it requires
Hi Alan et al.
On Mon, 2007-02-12 at 19:08 +, Alan wrote:
I'm not sure you'll get 50MB/sec sustained to work although you might
with a good current drive used for nothing else, a linear stream of data
(no seeking and file system overhead), and a non PCI controller (PCI
Express, host
Hi.
On Mon, 2007-02-12 at 16:57 +0100, Geert Uytterhoeven wrote:
On Mon, 12 Feb 2007, Pavel Machek wrote:
Can't the upper layer just assume -ENOSYS if .resume/.suspend is NULL?
It's nicer if you don't have to implement dummy functions at all.
Unfortunately, drivers currently assume
Hi.
On Mon, 2007-02-12 at 22:01 +0100, Rafael J. Wysocki wrote:
On Monday, 12 February 2007 21:58, Pavel Machek wrote:
Hi!
If all you need to do is say 'I don't need to do anything' and we
have a
shared function that does that, all we're talking about doing is
adding
Hi.
On Mon, 2007-02-12 at 06:19 +0100, Willy Tarreau wrote:
One less myth as Nigel would say call it ;-)
You know me too well! :
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hi.
On Mon, 2007-02-12 at 21:06 +0100, Rafael J. Wysocki wrote:
On Monday, 12 February 2007 05:08, Nigel Cunningham wrote:
Nope. I'm assuming that the driver author knows what needs to be done to
get the driver out of whatever state the BIOS puts it in to start
Hi.
On Tue, 2007-02-13 at 00:23 +0100, Rafael J. Wysocki wrote:
Hi,
Here's my attempt to document the requirements with respect to the basic PM
support in drivers and the testing of that. Comments welcome.
Greetings,
Rafael
---
Documentation/SubmittingDrivers | 10 ++
Hi.
On Tue, 2007-03-20 at 19:23 -0600, Eric W. Biederman wrote:
Rafael J. Wysocki [EMAIL PROTECTED] writes:
On Tuesday, 20 March 2007 22:06, Rafael J. Wysocki wrote:
On Tuesday, 20 March 2007 21:58, Jiri Slaby wrote:
Rafael J. Wysocki napsal(a):
Actually, the problem is 100%
Hi.
On Wed, 2007-03-21 at 18:40 +0200, Maxim Levitsky wrote:
Hi,
Starting with 2.6.21-rc1 suspend to ram and disk doesn't work anymore on my
system.
I did a git-bisect and found that those commits break it:
e3c7db621bed4afb8e231cb005057f2feb5db557 - [PATCH] [PATCH] PM: Change code
Hi.
On Wed, 2007-03-21 at 22:38 +0100, Rafael J. Wysocki wrote:
Do you know exactly which mutex was being waited on and where it was
taken? If you can say that, it would be much more helpful.
Yeah, me too, but assuming too much sometimes bites me :)
I think this is the XFS problem with
Hi.
On Fri, 2007-04-06 at 16:34 +0200, Rafael J. Wysocki wrote:
On Monday, 2 April 2007 22:51, Pavel Machek wrote:
Hi!
+/* Per process freezer specific flags */
+#define PF_FE_SUSPEND0x8000 /* This thread should
not be frozen
+
Hi.
On Fri, 2007-04-06 at 12:47 -0500, Nathan Lynch wrote:
Ingo Molnar wrote:
* Nathan Lynch [EMAIL PROTECTED] wrote:
- raw_notifier_call_chain(cpu_chain, CPU_LOCK_ACQUIRE, hcpu);
+ if (freeze_processes(FE_HOTPLUG_CPU)) {
+
Hi.
On Mon, 2007-04-02 at 21:36 +0200, Pavel Machek wrote:
Hi!
But you're still likely to run into trouble if you unplug a storage
device, move it to another system and write on it, then plug it back into
the original system. The PLVM would somehow have to recognize that the
data
Hi.
On Sat, 2007-04-07 at 11:33 +0200, Rafael J. Wysocki wrote:
On Saturday, 7 April 2007 00:20, Nigel Cunningham wrote:
- current-flags |= PF_NOFREEZE;
+ freezer_exempt(FE_ALL);
pid = kernel_thread(do_linuxrc, /linuxrc, SIGCHLD);
if (pid 0
Hi again.
By the way, I'm stopping using [EMAIL PROTECTED]; could you
please change your address book to nigel at nigel dot suspend2 dot net?
Thanks!
Nigel
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Hi.
On Sat, 2007-04-07 at 18:14 +0200, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki [EMAIL PROTECTED]
Make handle_initrd() call try_to_freeze() in a suitable place instead of
setting
PF_NOFREEZE for the current task.
Signed-off-by: Rafael J. Wysocki [EMAIL PROTECTED]
---
Hi.
On Sat, 2007-04-07 at 15:06 -0700, Andrew Morton wrote:
On Sat, 7 Apr 2007 23:20:39 +0200 Rafael J. Wysocki [EMAIL PROTECTED]
wrote:
This should allow us to reduce the memory usage, practically always, and
improve performance.
And does it?
It will. I've been using extents for
Hi.
On Sun, 2007-04-08 at 01:13 +0200, Rafael J. Wysocki wrote:
On Sunday, 8 April 2007 00:31, Nigel Cunningham wrote:
Hi.
On Sat, 2007-04-07 at 15:06 -0700, Andrew Morton wrote:
On Sat, 7 Apr 2007 23:20:39 +0200 Rafael J. Wysocki [EMAIL PROTECTED]
wrote:
This should allow
Hi.
On Sun, 2007-04-08 at 18:47 +0200, Rafael J. Wysocki wrote:
On Sunday, 8 April 2007 01:42, Nigel Cunningham wrote:
Hi.
On Sun, 2007-04-08 at 01:13 +0200, Rafael J. Wysocki wrote:
On Sunday, 8 April 2007 00:31, Nigel Cunningham wrote:
Hi.
On Sat, 2007-04-07 at 15:06
Hi.
On Mon, 2007-04-09 at 15:03 +0200, Rafael J. Wysocki wrote:
On Sunday, 8 April 2007 23:07, Nigel Cunningham wrote:
[--snip--]
Normal usage in both cases is simply iterating through the list, so I
guess the cost would be approximately the same.
Deletion could would include
Hi.
On Sun, 2007-04-01 at 23:17 +0200, Sam Ravnborg wrote:
On Thu, Feb 01, 2007 at 02:05:49PM +1100, Nigel Cunningham wrote:
Hi.
The scripts/kconfig/mconf target isn't removed by the make mrproper
target. I can see a couple of possibilities, but wasn't sure which you'd
prefer, so
Hi.
On Fri, 2007-04-13 at 14:00 +0200, Rafael J. Wysocki wrote:
Shrinking memory... Pages needed: 128103 normal, 0 highmem
Pages needed: 125226 normal, 0 highmem
Pages needed: -5757 normal, 0 highmem
Pages needed: -5757 normal, 0 highmem
Pages needed: -5757 normal, 0 highmem
Pages
Hi.
On Fri, 2007-04-13 at 22:41 +0200, Rafael J. Wysocki wrote:
On Friday, 13 April 2007 14:21, Nigel Cunningham wrote:
Hi.
On Fri, 2007-04-13 at 14:00 +0200, Rafael J. Wysocki wrote:
Shrinking memory... Pages needed: 128103 normal, 0 highmem
Pages needed: 125226 normal, 0
Hi.
On Sat, 2007-04-14 at 00:10 +0200, Pavel Machek wrote:
Hi!
Well, it looks like someone allocated about 6000 pages after we had
freed
enough memory for suspending.
We have a tunable allowance in Suspend2 for this, because fglrx
allocates a lot of pages in its suspend
Hi.
On Sat, 2007-04-14 at 00:35 +0200, Rafael J. Wysocki wrote:
On Saturday, 14 April 2007 00:10, Pavel Machek wrote:
Hi!
Well, it looks like someone allocated about 6000 pages after we had
freed
enough memory for suspending.
We have a tunable allowance in Suspend2
Hi.
On Sat, 2007-04-14 at 00:38 +0200, Pavel Machek wrote:
Hi!
Well, it looks like someone allocated about 6000 pages after we had
freed
enough memory for suspending.
We have a tunable allowance in Suspend2 for this, because fglrx
allocates a lot of pages in
Hi.
On Sat, 2007-04-14 at 00:40 +0200, Pavel Machek wrote:
Hi!
Well, it looks like someone allocated about 6000 pages after we had
freed
enough memory for suspending.
We have a tunable allowance in Suspend2 for this, because fglrx
allocates a lot of pages in
Hi.
On Sat, 2007-04-14 at 00:57 +0200, Rafael J. Wysocki wrote:
Well, I'm not sure. First, we don't really know what the value of it
should be
and this alone is a good enough reason for making it tunable, IMHO.
Second, I
think different systems may need different
Hi.
On Wed, 2007-02-28 at 01:08 +0100, Rafael J. Wysocki wrote:
On Wednesday, 28 February 2007 01:01, Johannes Berg wrote:
On Wed, 2007-02-28 at 00:57 +0100, Rafael J. Wysocki wrote:
Okay, in that case I'd suggest removing create_freezeable_workqueue() and
make all workqueues
Hi.
On Fri, 2007-03-02 at 07:25 -0700, Tim Gardner wrote:
Pavel Machek wrote:
Hi!
I instrumented 2.6.21-rc1 base/power/resume.c device_resume() with
TRACE_RESUME(0) as the last statement in the function. Sure enough it
was the last hash value in the RTC after a hard reboot when resume
Hi.
On Fri, 2007-03-02 at 17:46 +0900, Tejun Heo wrote:
Add missing #ifdef CONFIG_PM conditionals around all PM related parts
in libata LLDs.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
drivers/ata/ahci.c | 14 ++
drivers/ata/ata_generic.c |4
Hi.
On Sat, 2007-03-03 at 12:20 +0900, Tejun Heo wrote:
Hello, Nigel.
Nigel Cunningham wrote:
Index: work1/drivers/ata/ahci.c
===
--- work1.orig/drivers/ata/ahci.c
+++ work1/drivers/ata/ahci.c
@@ -225,10 +225,12
Hi.
On Tue, 2007-03-06 at 21:31 +0100, Rafael J. Wysocki wrote:
Hi,
On Tuesday, 6 March 2007 01:30, Johannes Berg wrote:
On Tue, 2007-02-27 at 22:51 +0100, Rafael J. Wysocki wrote:
For 2.6.21-rc1 I've invented the appended workaround (works for me,
waiting for
Johannes to
Hi.
On Tue, 2007-03-06 at 01:16 +0100, Johan Henriksson wrote:
Hi!
I have gotten the radeon xpress 200m (the version without dedicated
vmem)
to work with radeonfb.
The attached patch (against linux-2.6.20.1) works for me.
Since I don't have any docs for the card I am unsure if the patch
Hi.
On Wed, 2007-03-07 at 07:07 -0800, Arjan van de Ven wrote:
On Wed, 2007-03-07 at 12:27 +0530, Vivek Goyal wrote:
Hi,
Here is another attempt on x86_64 relocatable bzImage patches(V4). This
patchset makes a bzImage relocatable and same kernel binary can be loaded
and run from
Hi.
On Thu, 2007-03-08 at 07:49 +1100, Nigel Cunningham wrote:
Hi.
On Wed, 2007-03-07 at 07:07 -0800, Arjan van de Ven wrote:
On Wed, 2007-03-07 at 12:27 +0530, Vivek Goyal wrote:
Hi,
Here is another attempt on x86_64 relocatable bzImage patches(V4). This
patchset makes
Hi.
On Wed, 2007-03-07 at 23:50 +0100, Pavel Machek wrote:
Hi!
o virt_to_page() call should be used on kernel linear addresses and not
on kernel text and data addresses. Swsusp code uses it on kernel data
(statically allocated swsusp_header).
o Allocate swsusp_header dynamically
Hi.
On Thu, 2007-03-08 at 10:10 +0530, Vivek Goyal wrote:
On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote:
Hi.
On Thu, 2007-03-08 at 07:49 +1100, Nigel Cunningham wrote:
Hi.
On Wed, 2007-03-07 at 07:07 -0800, Arjan van de Ven wrote:
On Wed, 2007-03-07 at 12
Hi.
Miklos Szeredi wrote:
On Tue 2008-01-08 12:35:09, Miklos Szeredi wrote:
From: Miklos Szeredi [EMAIL PROTECTED]
Use FS_SAFE for fuse fs type, but not for fuseblk.
FUSE was designed from the beginning to be safe for unprivileged users.
This
has also been verified in practice over many
Hi.
Miklos Szeredi wrote:
On Tue 2008-01-08 12:35:09, Miklos Szeredi wrote:
From: Miklos Szeredi [EMAIL PROTECTED]
Use FS_SAFE for fuse fs type, but not for fuseblk.
FUSE was designed from the beginning to be safe for unprivileged users.
This
has also been verified in practice over many
Hi.
Huang, Ying wrote:
This patchset provides an enhancement to kexec/kdump. It implements
the following features:
- Backup/restore memory used both by the original kernel and the
kexeced kernel.
Why the kexeced kernel as well?
[...]
The features of this patchset can be used as
Rene Herman wrote:
Good day.
Would some people on x86 (both 32 and 64) be kind enough to compile and
run the attached program? This is about testing how long I/O port access
to port 0x80 takes. It measures in CPU cycles so CPU speed is crucial in
reporting.
Posted a previous incarnation
Rene Herman wrote:
On 12-12-07 00:55, Nigel Cunningham wrote:
(AMD 1.8GHz Turion, running at 800MHz. ATI RS480 - Mitac 8350 mobo)
[EMAIL PROTECTED]:~/Downloads$ gcc port80.c -o port80
[EMAIL PROTECTED]:~/Downloads$ sudo ./port80
cycles: out 1235, in 1207
Looking good.
[EMAIL
Hi Berthold.
Berthold Cogel wrote:
Jan 1 17:34:39 wonderland kernel: usb 2-2: USB disconnect, address 3
Jan 1 17:34:39 wonderland kernel: usb 2-2.5: USB disconnect, address 4
Jan 1 17:34:39 wonderland kernel: drivers/input/tablet/wacom_sys.c:
wacom_sys_irq - usb_submit_urb failed with
Hi all.
With the start of a new year, I suppose it's a good time to think about
what I'd like to do with TuxOnIce this year and see what feedback I get.
First up, I'm thinking about closing the mailing lists and asking people
to use LKML instead for reporting issues and so on. I'm thinking about
Hi.
Rafael J. Wysocki wrote:
On Tuesday, 1 of January 2008, Nigel Cunningham wrote:
Hi all.
Hi Nigel,
Gidday :)
With the start of a new year, I suppose it's a good time to think about
what I'd like to do with TuxOnIce this year and see what feedback I get.
First up, I'm thinking about
Hi Christian.
Christian Hesse wrote:
On Tuesday 01 January 2008, Nigel Cunningham wrote:
Third, regarding the patch itself, I'm taking my time in working towards
the 3.0 release. We don't have any major bugs with 3.0-rc3 reported [...].
Well, I think I still have a bug, though
Hi Ted.
Theodore Tso wrote:
On Wed, Jan 02, 2008 at 10:54:18AM +1100, Nigel Cunningham wrote:
I would also like the TuxOnIce issues related to drivers, ACPI, etc. to go
to
one of the kernel-related lists, but I think linux-pm may be better for that
due to the much lower traffic.
I guess
Hi.
Rafael J. Wysocki wrote:
On Wednesday, 2 of January 2008, Theodore Tso wrote:
On Wed, Jan 02, 2008 at 10:54:18AM +1100, Nigel Cunningham wrote:
I would also like the TuxOnIce issues related to drivers, ACPI, etc. to go
to
one of the kernel-related lists, but I think linux-pm may
Hi.
Pavel Machek wrote:
Hi!
So how do you handle threads that are blocked on I/O or a lock
during the system freeze process, then?
We wait until they can continue.
So if I have a process blocked on an unavilable NFS mount, I can't
suspend?
That's correct, you can't.
[And I know what
Hi Martin.
Martin Steigerwald wrote:
Am Mittwoch 02 Januar 2008 schrieb Nigel Cunningham:
Hi.
Hi,
Rafael J. Wysocki wrote:
On Wednesday, 2 of January 2008, Theodore Tso wrote:
On Wed, Jan 02, 2008 at 10:54:18AM +1100, Nigel Cunningham
wrote:
I would also like the TuxOnIce issues
Hi.
Rafael J. Wysocki wrote:
On Wednesday, 2 of January 2008, Nigel Cunningham wrote:
Pavel Machek wrote:
So how do you handle threads that are blocked on I/O or a lock
during the system freeze process, then?
We wait until they can continue.
So if I have a process blocked on an unavilable
Hi.
Oliver Neukum wrote:
Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
On top of this, I made a (too simple at the moment) freeze_filesystems
function which iterates through super_blocks in reverse order, freezing
fuse filesystems or ordinary ones. I say 'too simple' because
Hi.
Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
Hi.
Oliver Neukum wrote:
Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
On top of this, I made a (too simple at the moment) freeze_filesystems
function which iterates through super_blocks
Hi.
Pavel Machek wrote:
On Fri 2008-01-04 21:54:06, Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 23:06:07 schrieb Nigel Cunningham:
Oliver Neukum wrote:
Am Donnerstag, 3. Januar 2008 10:52:53 schrieb Nigel Cunningham:
Oliver Neukum wrote:
Am Donnerstag 03 Januar 2008 schrieb Nigel
Hi.
Berthold Cogel wrote:
Al Viro schrieb:
On Tue, Jan 01, 2008 at 08:26:05PM +0100, Berthold Cogel wrote:
Jan 1 17:34:39 wonderland kernel: BUG: unable to handle kernel
paging request at virtual address 00100100
LIST_POISON1
Jan 1 17:34:39 wonderland kernel: EIP is at
. Wysocki [EMAIL PROTECTED]
Acked-by: Nigel Cunningham [EMAIL PROTECTED]
---
kernel/signal.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.23-mm1/kernel/signal.c
===
--- linux-2.6.23-mm1.orig/kernel
Hi Andrew.
On Thursday 20 September 2007 20:09:41 Pavel Machek wrote:
Seems like good enough for -mm to me.
Pavel
Andrew, if I recall correctly, you said a while ago that you didn't want
another hibernation implementation
Hi.
On Friday 21 September 2007 11:06:23 Andrew Morton wrote:
On Fri, 21 Sep 2007 10:24:34 +1000 Nigel Cunningham
[EMAIL PROTECTED] wrote:
Hi Andrew.
On Thursday 20 September 2007 20:09:41 Pavel Machek wrote:
Seems like good enough for -mm to me
Hi.
On Friday 21 September 2007 11:41:06 Andrew Morton wrote:
On Friday 21 September 2007 11:06:23 Andrew Morton wrote:
On Fri, 21 Sep 2007 10:24:34 +1000 Nigel Cunningham
[EMAIL PROTECTED] wrote:
Hi Andrew.
On Thursday 20 September 2007 20:09:41 Pavel Machek wrote
Hi.
On Friday 21 September 2007 12:18:57 Huang, Ying wrote:
That's not true. Kexec will itself be an implementation, otherwise you'd
end
up with people screaming about no hibernation support. And it won't result
in
the complete removal of the existing hibernation code from the kernel.
Hi.
On Friday 21 September 2007 12:45:57 Huang, Ying wrote:
On Fri, 2007-09-21 at 12:25 +1000, Nigel Cunningham wrote:
Hi.
On Friday 21 September 2007 12:18:57 Huang, Ying wrote:
That's not true. Kexec will itself be an implementation, otherwise
you'd
end
up with people
Hi.
On Friday 21 September 2007 21:56:29 Rafael J. Wysocki wrote:
[Besides, the current hibernation userland interface is used by default by
openSUSE and it's also used by quite some Debian users, so we can't drop
it overnight and it can't be implemented in a compatible way on top of the
Hi.
On Friday 21 September 2007 22:18:19 Rafael J. Wysocki wrote:
On Friday, 21 September 2007 13:58, Nigel Cunningham wrote:
Hi.
On Friday 21 September 2007 21:56:29 Rafael J. Wysocki wrote:
[Besides, the current hibernation userland interface is used by default
by
openSUSE
Hi.
On Saturday 22 September 2007 09:19:18 Kyle Moffett wrote:
I think that in order for this to work, there would need to be some
ABI whereby the resume-ing kernel can pass its entire ACPI state and
a bunch of other ACPI-related device details to the resume-ed kernel,
which I believe
Hi.
On Thursday 27 September 2007 06:30:36 Joseph Fannin wrote:
On Fri, Sep 21, 2007 at 11:45:12AM +0200, Pavel Machek wrote:
Hi!
Sounds doable, as long as you can cope with long command lines (which
shouldn't be a biggie). (If you've got a swapfile or parts of a swap
partition
Hi.
On Thursday 27 September 2007 16:33:54 Huang, Ying wrote:
On Wed, 2007-09-26 at 16:30 -0400, Joseph Fannin wrote:
But, in my ignorance, I'm not sure even fixing the ext3 bug will
guarantee you consistent metadata so that you can handle a
swap/hibernate file. You can do a sync(),
Hi Rafael et al.
This looks like it will be vanilla material, maybe 2.6.23 material?
Regards,
Nigel
-- Forwarded Message --
Subject: [Suspend2-devel] [patch] 2.2.10.3 build fixes
Date: Sunday 30 September 2007
From: Roman Dubtsov (dubtsov gmail com)
Hi,
I have recently run
Hi.
On Monday 01 October 2007 05:56:45 Rafael J. Wysocki wrote:
Hi,
On Sunday, 30 September 2007 13:44, Nigel Cunningham wrote:
Hi Rafael et al.
This looks like it will be vanilla material, maybe 2.6.23 material?
Well, I wouldn't like to export freezer.h . Why exactly would
Hi.
On Monday 01 October 2007 08:28:02 Rafael J. Wysocki wrote:
On Sunday, 30 September 2007 23:43, Nigel Cunningham wrote:
On Monday 01 October 2007 05:56:45 Rafael J. Wysocki wrote:
On Sunday, 30 September 2007 13:44, Nigel Cunningham wrote:
Hi Rafael et al.
This looks like
1 - 100 of 1220 matches
Mail list logo
