On 7/2/07, Ingo Molnar <[EMAIL PROTECTED]> wrote:
ok. Does the xterm slowdown get any better if you do:
echo 46 > /proc/sys/kernel/sched_features
? The default on v18 is:
echo 14 > /proc/sys/kernel/sched_features
No. The Ctrl-C still hangs between 1 and 3 seconds, again seemingly
dependi
On Tue, Jul 03, 2007 at 08:23:07AM +0200, Oliver Neukum wrote:
> Am Dienstag, 3. Juli 2007 schrieb Greg KH:
> > On Mon, Jul 02, 2007 at 10:33:12PM -0700, Yinghai Lu wrote:
> > > On 7/2/07, Greg KH <[EMAIL PROTECTED]> wrote:
> > > > On Mon, Jul 02, 2007 at 03:36:37PM -0700, Yinghai Lu wrote:
> > >
My $0.02 on thinkpad_acpi & HID's...
1. moving to DMI binding from PNP-id binding
sounds like a step in the wrong direction.
Are there thinkpads that you need to support that don't export IBM0068?
There is a long tradition of DMI information being copy/pasted
and being invalid. While the thinkp
On Mon, 2007-07-02 at 18:40 +0200, Vegard Nossum wrote:
> On 7/2/07, Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > thx. As an initial matter, could you double-check whether your v18
> > kernel source has the patch below applied already?
> >
> > Ingo
> >
> > Index: linux/kernel/sched_fair.c
> >
Am Dienstag, 3. Juli 2007 schrieb Greg KH:
> > > Ok, so two drivers might need this, but not the whole usb core, right?
> >
> > If those two drivers need the extended allocator, why not use it where
> > it is beneficial, even if the benefit is small?
>
> What is the benefit? Speed isn't an issue
* Pavel Machek <[EMAIL PROTECTED]> [2007-07-03 01:08]:
> On Mon 2007-07-02 14:39:27, Andi Kleen wrote:
> >
> > > > Perhaps one of you geniuses who all hate it can find a better way to
> > > > solve the "video output dead after kexec; but need visual feedback to
> > > > the user
> > > > while cras
* Vegard Nossum <[EMAIL PROTECTED]> wrote:
> I'd also like to point out that [EMAIL PROTECTED] seems to draw more CPU
> than it should. Or, at least, in top, it shows up as using 50% CPU
> even though other processes are demanding as much as they can get. The
> FAH program should be running wi
> BTW: I also saw a laptop (IIRC it was a sony) with asus and sony ACPI
> device.
> When both drivers got loaded things broke.
> A solution was to only let the asus driver get active if the device is
> known. Currently, not sure whether still (I sent a patch a while ago),
> the Asus driver falls b
On Tue, 2007-07-03 at 16:08 +1000, Nigel Cunningham wrote:
>
> > So I think Matthew is totally right. In fact, the presence of the
> > freezer is the main reason why Paulus so far NACKed Johannes attempts at
> > merging the PPC PM code with the generic code in kernel/power.c
> >
> > We've been do
* Mike Galbraith <[EMAIL PROTECTED]> wrote:
> This doesn't appear to be a CFS problem. I can reproduce the problem
> easily in virgin 2.6.22-rc7 by starting xterm-spam at nice -1 or
> better. As soon as xterm-spam can get enough CPU to keep the xterm
> fully busy, it's game over, the xterm fr
On Mon, 2007-07-02 at 18:29 -0700, Zachary Amsden wrote:
> > -static inline int
> > -ptep_test_and_clear_dirty (struct vm_area_struct *vma, unsigned long addr,
> > pte_t *ptep)
> > -{
> > -#ifdef CONFIG_SMP
> > - if (!pte_dirty(*ptep))
> > - return 0;
> > - return test_and_clear_bit(
William Thompson wrote:
> I'm not on either list, keep me in CC.
>
> I noticed the following error on a cdrom device:
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0
> res 40/00:03:00:00:00/00:00:00
Hi All,
I have an MMC driver for my kit (i.MX21 based cogent board
CSB535FS), which is supplied by Cogent (Kernel version 2.6.16).
The original driver (linux/drivers/mmc/mmc_block.c) uses
mmc_register_driver() method to register the driver but the one
supplied by Cogent uses platform_driver_r
> A) Cannot pass acpi_device_id through ops.add (probe equivalent func)
> -
>
> int acpi_match_device_ids(..)
> should be:
> const acpi_device_id *acpi_match_device_ids
> and the matching device id should get passed to the acpi dr
Am Dienstag, 3. Juli 2007 schrieb Benjamin Herrenschmidt:
> So to summarize, the plan that makes things work with fuse is:
>
> - For STR, don't do the freezer thing.
>
> - For STD, don't sys_sync() after you froze
>
> There might be -other- issues, but that should get you through some of
At t
On Sunday 17 June 2007 16:24, Thomas Renninger wrote:
> Define standardized HIDs ...
> Index: linux-2.6.22-rc4/include/acpi/acpi_drivers.h
> ===
> --- linux-2.6.22-rc4.orig/include/acpi/acpi_drivers.h
> +++ linux-2.6.22-rc4/include/ac
Hello World,
I re-stumbled on this installing Gentoo on VMware today;
http://lkml.org/lkml/2007/3/23/312
It doesn't seem to be fixed in 2.6.22-rc7, but I might be mistaken
somehow. Has anyone done any work on this or looked at the problem
in more detail? The trail seems to die at that thread.
I
On Tue, 2007-07-03 at 09:22 +0200, Ingo Molnar wrote:
> which allows xterm-spam (attached) to easily flood the xterm (without
> any scrolling that would act as a throttle) and the xterm to flood Xorg.
It's just an Xterm bug.
Xterm will look for X input if it ever manages to fill the input buff
On Tue, 2007-07-03 at 05:29 +0100, Matthew Garrett wrote:
> or alternatively we could do what we do for suspend to RAM on other
> platforms (PPC and APM) and just not use the freezer.
As a data point, I am running with this patch on top of 2.6.21.2 the
last 3+ weeks, with an average of 5/6 STR c
Am Dienstag, 3. Juli 2007 schrieb Romano Giannetti:
> On Tue, 2007-07-03 at 05:29 +0100, Matthew Garrett wrote:
> > or alternatively we could do what we do for suspend to RAM on other
> > platforms (PPC and APM) and just not use the freezer.
>
> As a data point, I am running with this patch on to
Michael Tokarev wrote:
> [Offtopic notice: For the first time I demonstrated some
> speed testing results on linux-ide mailinglist, as a
> demonstration how [NT]CQ can help. But later, someone
> becomes curious and posted that email to lkml, asking
> for more details. Since that, I become more cu
Michal Piotrowski wrote:
> Hi,
>
> [adding linux-ide to cc]
>
> On 27/06/07, Dan <[EMAIL PROTECTED]> wrote:
>> Something changed with the AHCI SATA driver in the latest git version.
>> With 2.6.21 I get ~49MB/sec according to hdparm. Using the latest git
>> version I only get ~8MB/sec. I've attac
* Keith Packard <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-07-03 at 09:22 +0200, Ingo Molnar wrote:
>
> > which allows xterm-spam (attached) to easily flood the xterm
> > (without any scrolling that would act as a throttle) and the xterm
> > to flood Xorg.
>
> It's just an Xterm bug.
>
> Xter
On Fri, 1 Jun 2007 05:38:48 -0700,
Greg KH <[EMAIL PROTECTED]> wrote:
[Sorry for taking so long to respond, I've been offline for a month]
> Can you resend me the new patch, I seem to have lost it in this thread
> :(
Andrew has the fixup patch in his -mm lineup as
driver-core-check-return-code-o
Andrew,
I was hoping to get your input on how to handle patches that cross
maintainers. I've got a patch that is pretty PPC specific, but
happens to touch some drivers as well.
Here's the diffstat to get a rough idea:
arch/powerpc/kernel/io.c| 12 ++--
arch/powerp
Hi All,
This is referring to my problem - not able to mount MMC card. I
have some output from dmesg when I remove and put the card back (I
have changes the kernel config to include i.MX SPI and disabled the
generic SPI). DOes this give any clue as to why the MMC card is not
appaering in /proc/p
On 7/3/07, Ingo Molnar <[EMAIL PROTECTED]> wrote:
does it still get more CPU time than you'd expect it to get? A reniced
or SCHED_IDLE task will 'fill in' any idle time that it senses, so in
itself it's not an anomaly if a task gets 50% and FEH fills in the
remaining 50%. Does it still get CPU ti
On Mon, 25 Jun 2007 01:16:24 -0700,
Greg KH <[EMAIL PROTECTED]> wrote:
[I'm a bit late to the party, but...]
> On Sun, Jun 24, 2007 at 11:04:13PM +0800, Huang, Ying wrote:
> > There does exist multithreaded device probing in current driver core
> > implementation, supposing two devices are hot-p
On Tue, 3 Jul 2007 04:01:20 -0500 Kumar Gala <[EMAIL PROTECTED]> wrote:
> Andrew,
>
> I was hoping to get your input on how to handle patches that cross
> maintainers. I've got a patch that is pretty PPC specific, but
> happens to touch some drivers as well.
>
> Here's the diffstat to get a
On Sun, Jul 01, 2007 at 01:03:11PM +0100, David Woodhouse wrote:
>
> Seems reasonable enough in principle -- but whatever you do, don't use
> "long" for it. That would definitely need different behaviour for 32-bit
> vs. 64-bit. Use explicitly sized types such as uint32_t or uint64_t.
Here the pa
On Tue, Jun 19, 2007 at 11:00:54AM +0100, Richard Purdie wrote:
> Its not a case of formatting the whole partition. The whole point of
> this code is the following use case:
>
> 1. Device crashes
> 2. Device reboots
> 3. mtdoops partition has a log of why it crashed
The oops logger uses oops_in_p
On Sat, Jun 30, 2007 at 12:52:46PM -0400, Andreas Dilger wrote:
> The @mode flags that are currently under consideration are (AFAIK):
>
> FA_FL_DEALLOC 0x01 /* deallocate unwritten extent (default allocate)
> */
> FA_FL_KEEP_SIZE 0x02 /* keep size for EOF {pre,de}alloc (default chan
On Tue, Jul 03, 2007 at 03:38:48PM +0530, Amit K. Arora wrote:
> > FA_FL_DEALLOC 0x01 /* deallocate unwritten extent (default
> > allocate) */
> > FA_FL_KEEP_SIZE 0x02 /* keep size for EOF {pre,de}alloc (default change
> > size) */
> > FA_FL_DEL_DATA 0x04 /* delete existing
On Mon, 2 Jul 2007, Tejun Heo wrote:
Hello, it's me again.
We have another bug which reportedly is related to pktcdvd. Please respond.
http://bugzilla.kernel.org/show_bug.cgi?id=7547
http://bugzilla.kernel.org/show_bug.cgi?id=7805
The problem is that when you run pktsetup, the driver will o
just built a new kernel and didn't notice that support for LVM
wasn't selected by default for x86. given what i thought was fairly
widespread use of LVM2, wouldn't it make sense to have this option as
part of the default config?
rday
--
On Sun, 2007-07-01 at 03:36 -0400, Mingming Cao wrote:
> +
> +#define EXT4_INODE_GET_XTIME(xtime, inode, raw_inode)
>\
> +do {\
> + (inode)->xtime.tv_sec = le32_to_cpu((raw_inode)->xtime);
> > So to summarize, the plan that makes things work with fuse is:
> >
> > - For STR, don't do the freezer thing.
> >
> > - For STD, don't sys_sync() after you froze
> >
> > There might be -other- issues, but that should get you through some of
>
> At the risk of repeating myself. Character d
On Sun, 2007-07-01 at 03:36 -0400, Mingming Cao wrote:
> +
> +#define EXT4_INODE_GET_XTIME(xtime, inode, raw_inode)
>\
> +do {\
> + (inode)->xtime.tv_sec = le32_to_cpu((raw_inode)->xtime);
Incase anyone is interested:
p34:/usr/src/linux-2.6.22-rc7# patch -p1 < ../mtrr-v3.patch
patching file Documentation/kernel-parameters.txt
Hunk #1 succeeded at 548 (offset -5 lines).
patching file arch/i386/kernel/cpu/mtrr/generic.c
Hunk #2 succeeded at 85 (offset 1 line).
patching file arch/i386
> > > > So to summarize, the plan that makes things work with fuse is:
> > > >
> > > > - For STR, don't do the freezer thing.
> > > >
> > > > - For STD, don't sys_sync() after you froze
> > > >
> > > > There might be -other- issues, but that should get you through some of
> > >
> > > At the r
Oliver Neukum writes:
> At the risk of repeating myself. Character device drivers are written
> with the assumption that normal io and suspend/resume do not race
> with each other due to the freezer.
> What do you intend to do about that?
Going back to the old powerbook sleep code, we had a two-p
Am Dienstag, 3. Juli 2007 schrieb Miklos Szeredi:
> > > > > So to summarize, the plan that makes things work with fuse is:
> > > > >
> > > > > - For STR, don't do the freezer thing.
> > > > >
> > > > > - For STD, don't sys_sync() after you froze
> > > > >
> > > > > There might be -other- issue
Am Dienstag, 3. Juli 2007 schrieb Miklos Szeredi:
> > > So to summarize, the plan that makes things work with fuse is:
> > >
> > > - For STR, don't do the freezer thing.
> > >
> > > - For STD, don't sys_sync() after you froze
> > >
> > > There might be -other- issues, but that should get you t
On Tue, Jul 03, 2007 at 04:26:31PM +0900, Tejun Heo wrote:
> William Thompson wrote:
> > I'm not on either list, keep me in CC.
> >
> > I noticed the following error on a cdrom device:
> > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> > ata2.00: cmd a0/00:00:00:00:20/00:00:00:
Hi,
I don't know really which subsystem this, so I'm sending this to the
linux-kernel list.
Please direct me to a more appropriate place if this is not correct.
I'm using a 3ware 9500 with Linux 2.6.18.1. I've grown the HW
raid5-array and here is where the problem begins. After the card had
Am Dienstag, 3. Juli 2007 schrieb Paul Mackerras:
> I'm actually having a hard time thinking of how to test your assertion
> since there are so few things on a typical computer that are plain
> character devices driving real hardware. A serial port would be about
> the only one; keyboards and mice
On Tue, 2007-07-03 at 09:44 +0200, Oliver Neukum wrote:
> Am Dienstag, 3. Juli 2007 schrieb Benjamin Herrenschmidt:
> > So to summarize, the plan that makes things work with fuse is:
> >
> > - For STR, don't do the freezer thing.
> >
> > - For STD, don't sys_sync() after you froze
> >
> > Ther
On Tue, 2007-07-03 at 13:27 +0200, Oliver Neukum wrote:
> > You are talking about hibernate, right? Suspending (to ram) is
> > instantaneous, in that _after_ suspend no CPU is active obviously.
>
> If that is so, why do you care? If it is really atomic, fuse has no
> chance
> to call out to its c
On Tue, Jul 03, 2007 at 11:31:07AM +0100, Christoph Hellwig wrote:
> On Tue, Jul 03, 2007 at 03:38:48PM +0530, Amit K. Arora wrote:
> > > FA_FL_DEALLOC 0x01 /* deallocate unwritten extent (default
> > > allocate) */
> > > FA_FL_KEEP_SIZE 0x02 /* keep size for EOF {pre,de}alloc (defau
Am Dienstag, 3. Juli 2007 schrieb Benjamin Herrenschmidt:
> On Tue, 2007-07-03 at 09:44 +0200, Oliver Neukum wrote:
> > Am Dienstag, 3. Juli 2007 schrieb Benjamin Herrenschmidt:
> > > So to summarize, the plan that makes things work with fuse is:
> > >
> > > - For STR, don't do the freezer thing.
> The problem is not with fuse. The problem is generic in nature.
>
> If you remove the freezer, user space remains active until the last CPU
> goes into suspend. It can do syscalls. Or do you know a clean way to exempt
> only the tasks fuse might use?
>
> Now device drivers have a guaranteed tem
Am Dienstag, 3. Juli 2007 schrieb Benjamin Herrenschmidt:
> On Tue, 2007-07-03 at 13:27 +0200, Oliver Neukum wrote:
> > > You are talking about hibernate, right? Suspending (to ram) is
> > > instantaneous, in that _after_ suspend no CPU is active obviously.
> >
> > If that is so, why do you care?
On Tue, 2007-07-03 at 03:40 -0400, Len Brown wrote:
> > A) Cannot pass acpi_device_id through ops.add (probe equivalent func)
> > -
> >
> > int acpi_match_device_ids(..)
> > should be:
> > const acpi_device_id *acpi_match_device_i
Am Dienstag, 3. Juli 2007 schrieb Benjamin Herrenschmidt:
> > Now device drivers have a guaranteed temporal sequence:
> >
> > last io -> suspend() -> resume() [or disconnect()] -> new io
>
> No, that's always been bullshit. You can have IOs emitted by kernel
> threads (think knfsd, and that's jus
William Thompson wrote:
>> Your cd rom failed to complete the TUR command your program issued in
>> the specified timeout. ODDs sometimes take quite long to finish TUR or
>> any other command when media is changed. Did you use sg command or
>> cdrom ioctl?
>
> I'm using SG_IO. I also tested sg3
Miklos Szeredi <[EMAIL PROTECTED]> wrote:
>> > So to summarize, the plan that makes things work with fuse is:
>> >
>> > - For STR, don't do the freezer thing.
>> >
>> > - For STD, don't sys_sync() after you froze
>> >
>> > There might be -other- issues, but that should get you through some of
>
I have updated my mm patch set. The diff:
- The tlb gather restart patch has been changed as discussed with Hugh.
- The ptep_establish patch now really removes all traces of the call.
- The mm_struct / vm_area_struct move to mm_types.h has been test
compiled on a number of architectures.
-
From: Martin Schwidefsky <[EMAIL PROTECTED]>
If need_resched() is false in the inner loop of unmap_vmas it is
unnecessary to do a full blown tlb_finish_mmu / tlb_gather_mmu for
each ZAP_BLOCK_SIZE ptes. Do a tlb_flush_mmu() instead. That gives
architectures with a non-generic tlb flush implementat
From: Martin Schwidefsky <[EMAIL PROTECTED]>
The last user of ptep_establish in mm/ is long gone. Remove the
architecture primitive as well.
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
---
include/asm-arm/pgtable.h |6 ++---
include/asm-generic/pgtable.h | 19 ---
From: Martin Schwidefsky <[EMAIL PROTECTED]>
Move the definitions of struct mm_struct and struct vma_area_struct
to include/mm_types.h. This allows to define more function in
asm/pgtable.h and friends with inline assemblies instead of macros.
Compile tested on i386, ia64, powerpc, powerpc64, s390-
From: Martin Schwidefsky <[EMAIL PROTECTED]>
Nobody is using ptep_test_and_clear_dirty and ptep_clear_flush_dirty.
Remove the functions from all architectures.
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
---
include/asm-frv/pgtable.h |8
include/asm-generic/pgta
From: Martin Schwidefsky <[EMAIL PROTECTED]>
The current tlb flushing code for page table entries violates the
s390 architecture in a small detail. The relevant section from the
principles of operation (SA22-7832-02 page 3-47):
"A valid table entry must not be changed while it is attached
t
On Tue, Jul 03, 2007 at 08:13:53AM +0200, Oliver Neukum wrote:
> Only if you want to audit all character devices' read() and write()
> methods for races against suspend().
> / on fuse is a bad idea.
Any driver that assumes that userspace will be frozen during suspend has
been broken forever. Tha
On Mon, 2007-07-02 at 17:06 -0500, Serge E. Hallyn wrote:
> Thanks Stephen, does the following version appear correct? It just
> checks for a different cap for security.capability, then if granted
> goes on to check FILE__GETATTR before granting setxattr or removexattr
> on any security.* xattr.
>
Hi Alex, hi all,
I have an Acer TM3012 with
0a:09.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card
Reader (SD/MMC/MS/MS PRO/xD)
but only when I plug in an SD card I get a device created, while
plugging in a Memory Stick I do not get any reaction of the kernel.
This is with ke
On Tue, 2007-07-03 at 03:58 -0400, Len Brown wrote:
> On Sunday 17 June 2007 16:24, Thomas Renninger wrote:
> > Define standardized HIDs ...
>
> > Index: linux-2.6.22-rc4/include/acpi/acpi_drivers.h
> > ===
> > --- linux-2.6.22-rc4.or
Hi all,
All my servers and workstations running a 2.6.21.5 kernel hanged exactly
when the date shift from june 30th to july 1st.
On my monitoring system every single station running a 2.6.21.5 kernel
stoped responding exactly after midnight on the date shift from June
30th to July 1st. Although,
On Tuesday, 3 July 2007 06:29, Matthew Garrett wrote:
> Suspend to RAM on a machine with / on a fuse filesystem turns out to be
> a screaming nightmare - either the suspend fails because syslog (for
> instance) can't be frozen, or the machine deadlocks for some other
> reason I haven't tracked d
On Tuesday, 3 July 2007 09:19, Benjamin Herrenschmidt wrote:
> On Tue, 2007-07-03 at 16:08 +1000, Nigel Cunningham wrote:
> >
> > > So I think Matthew is totally right. In fact, the presence of the
> > > freezer is the main reason why Paulus so far NACKed Johannes attempts at
> > > merging the PPC
On Tuesday, 3 July 2007 13:07, Oliver Neukum wrote:
> Am Dienstag, 3. Juli 2007 schrieb Miklos Szeredi:
> > > > So to summarize, the plan that makes things work with fuse is:
> > > >
> > > > - For STR, don't do the freezer thing.
> > > >
> > > > - For STD, don't sys_sync() after you froze
> > >
Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> just built a new kernel and didn't notice that support for LVM
> wasn't selected by default for x86. given what i thought was fairly
> widespread use of LVM2, wouldn't it make sense to have this option as
> part of the default config?
If you don't
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] De la part de
> Fortier,Vincent [Montreal]
> Envoyé : 3 juillet 2007 08:44
>
> Hi all,
>
> All my servers and workstations running a 2.6.21.5 kernel
> hanged exactly when the date shift from june 30th to july 1s
Hi Midhun,
I think mmc driver is layered modules, only top block driver
registers driver under "mmc_bus_type" bus, see
drivers/mmc/mmc_sysfs.c and mmc_block.c. I think they are creating a
tree of devices of same characteristics under that bus.
I think your driver is linux/drivers/mmc/imxmmc.c
Rolf Eike Beer wrote:
Renato S. Yamane wrote:
Rolf Eike Beer wrote:
Richard Hughes wrote:
Yes, although this is out of my area or expertise, sorry.
I've looked a bit but can't find any driver interaction of those
programs. Any further ideas welcome.
Do you try omnibook driver?
svn export
On Tuesday, 3 July 2007 13:46, Oliver Neukum wrote:
> Am Dienstag, 3. Juli 2007 schrieb Benjamin Herrenschmidt:
> > On Tue, 2007-07-03 at 09:44 +0200, Oliver Neukum wrote:
> > > Am Dienstag, 3. Juli 2007 schrieb Benjamin Herrenschmidt:
> > > > So to summarize, the plan that makes things work with f
On Tuesday, 3 July 2007 07:49, Benjamin Herrenschmidt wrote:
> On Tue, 2007-07-03 at 05:29 +0100, Matthew Garrett wrote:
> > Suspend to RAM on a machine with / on a fuse filesystem turns out to be
> > a screaming nightmare - either the suspend fails because syslog (for
> > instance) can't be froz
On Tuesday, 3 July 2007 07:51, Benjamin Herrenschmidt wrote:
> On Tue, 2007-07-03 at 05:29 +0100, Matthew Garrett wrote:
> > Suspend to RAM on a machine with / on a fuse filesystem turns out to be
> > a screaming nightmare - either the suspend fails because syslog (for
> > instance) can't be froz
On Tuesday, 3 July 2007 14:13, Matthew Garrett wrote:
> On Tue, Jul 03, 2007 at 08:13:53AM +0200, Oliver Neukum wrote:
>
> > Only if you want to audit all character devices' read() and write()
> > methods for races against suspend().
> > / on fuse is a bad idea.
>
> Any driver that assumes that u
On Tuesday, 3 July 2007 09:37, Romano Giannetti wrote:
> On Tue, 2007-07-03 at 05:29 +0100, Matthew Garrett wrote:
> > or alternatively we could do what we do for suspend to RAM on other
> > platforms (PPC and APM) and just not use the freezer.
>
> As a data point, I am running with this patch on
Hi, Vincent!
Fortier,Vincent [Montreal] schrieb:
Hi all,
All my servers and workstations running a 2.6.21.5 kernel hanged exactly
when the date shift from june 30th to july 1st.
On my monitoring system every single station running a 2.6.21.5 kernel
stoped responding exactly after midnight on t
On Tue, 2007-07-03 at 11:48 +0200, Rodolfo Giometti wrote:
> On Sun, Jul 01, 2007 at 01:03:11PM +0100, David Woodhouse wrote:
> >
> > Seems reasonable enough in principle -- but whatever you do, don't use
> > "long" for it. That would definitely need different behaviour for 32-bit
> > vs. 64-bit.
On Tue, 3 Jul 2007 01:28:57 -0400
"Xin Zhao" <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
> If a file is already opened when snapshot command is issued, the file
> itself could be in an inconsistent state already. Before the file is
> closed, maybe part of the file contains old data, the rest contains
On Tuesday, 3 July 2007 07:30, Benjamin Herrenschmidt wrote:
> On Tue, 2007-06-26 at 00:27 +0200, Rafael J. Wysocki wrote:
> > > > case PM_HIBERNATION_PREPARE:
> > > > case PM_SUSPEND_PREPARE:
> > > > usermodehelper_disabled = 1;
> > > > - return NOTIFY_OK;
> > > > +
On Mon, 2 July 2007 17:46:40 -0700, Jared Hulbert wrote:
>
> Right, the solution to swap problem is identical to the rw XIP
> filesystem problem.Jörn, that's why you're the self-appointed
> subject matter expert!
All right. I'll try to make an important face whenever the subject
comes up.
N
On Tue, 3 Jul 2007, Bodo Eggert wrote:
> Robert P. J. Day <[EMAIL PROTECTED]> wrote:
>
> > just built a new kernel and didn't notice that support for LVM
> > wasn't selected by default for x86. given what i thought was fairly
> > widespread use of LVM2, wouldn't it make sense to have this optio
On Tue, Jul 03, 2007 at 09:09:50AM -0400, David Woodhouse wrote:
> On Tue, 2007-07-03 at 11:48 +0200, Rodolfo Giometti wrote:
> > On Sun, Jul 01, 2007 at 01:03:11PM +0100, David Woodhouse wrote:
> > >
> > > Seems reasonable enough in principle -- but whatever you do, don't use
> > > "long" for it.
Hi,
On Tuesday, 3 July 2007 00:08, Nigel Cunningham wrote:
> Hi.
>
> On Tuesday 03 July 2007 05:18:39 Bill Davidsen wrote:
> > Nigel Cunningham wrote:
> > > Hi all.
> > >
> > > Suspend2's name is changing to "TuxOnIce".
> > >
> > > This is for a couple of reasons:
> > >
> > > In recent discuss
On Tuesday, 3 July 2007 15:19, Rafael J. Wysocki wrote:
> On Tuesday, 3 July 2007 07:30, Benjamin Herrenschmidt wrote:
> > On Tue, 2007-06-26 at 00:27 +0200, Rafael J. Wysocki wrote:
> > > > > case PM_HIBERNATION_PREPARE:
> > > > > case PM_SUSPEND_PREPARE:
> > > > > usermodehelp
Quoting Stephen Smalley ([EMAIL PROTECTED]):
> On Mon, 2007-07-02 at 17:06 -0500, Serge E. Hallyn wrote:
> > Thanks Stephen, does the following version appear correct? It just
> > checks for a different cap for security.capability, then if granted
> > goes on to check FILE__GETATTR before granting
On Thu, 2007-06-28 at 20:15 +0200, Andreas Gruenbacher wrote:
> On Thursday 28 June 2007 18:12, James Morris wrote:
> > Are you trying to cater for the case where you're holding an open fd for a
> > file which has been deleted, and thus has no pathname?
>
> Yes, see the AA_CHECK_FD flag in securi
Not really.
Current svn has read-only support for legacy MS (not mspro yet). I'm still
working on it. The
major difference: mmc/sd has an open spec, sony ms has none.
--- Norbert Preining <[EMAIL PROTECTED]> wrote:
> Hi Alex, hi all,
>
> I have an Acer TM3012 with
> 0a:09.2 Mass storage contro
On Tuesday, 3. July 2007, Fortier,Vincent [Montreal] wrote:
> Hi all,
>
> All my servers and workstations running a 2.6.21.5 kernel hanged exactly
> when the date shift from june 30th to july 1st.
>
Same thing here on two machines with plain vanilla 2.6.21.(3/4), on debian
testing & debian unstabl
On Tue, Jul 03, 2007 at 08:44:00AM -0400, Fortier,Vincent [Montreal] wrote:
> Hi all,
>
> All my servers and workstations running a 2.6.21.5 kernel hanged exactly
> when the date shift from june 30th to july 1st.
>
> On my monitoring system every single station running a 2.6.21.5 kernel
> stoped
X86 32bit with lots of debug turned on I get this:
Freeing unused kernel memory: 156k freed
Write protecting the kernel text: 1668k
Write protecting the kernel read-only data: 719k
Bad page state in process 'swapper'
page:c1c0 flags:0x0400 mapping: mapcount:0 count:0
Trying to fi
Mirrors change in IT821X
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
diff -u --new-file --exclude-from /usr/src/exclude --recursive
linux.vanilla-2.6.22-rc6-mm1/drivers/ata/ata_generic.c
linux-2.6.22-rc6-mm1/drivers/ata/ata_generic.c
--- linux.vanilla-2.6.22-rc6-mm1/drivers/ata/ata_generic.c
Florian Attenberger wrote:
Signed-off-by: Florian Attenberger <[EMAIL PROTECTED]>
--- 2.6.22-rc6/drivers/ata/sata_mv.c2007-06-30 16:21:47.462020256 +0200
+++ 2.6.22-rc6.mine/drivers/ata/sata_mv.c 2007-06-30 16:25:25.999165444
+0200
@@ -582,6 +582,9 @@ static const struct pci_device_
PCMCIA doesn't use DMA and as this driver is used on many platforms we
don't want it to fail on those that define the DMA alloc API as a NULL
return
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
diff -u --new-file --exclude-from /usr/src/exclude --recursive
linux.vanilla-2.6.22-rc6-mm1/drivers/ata
We got it backwards and now the other detects are fixed it shows up
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
diff -u --new-file --exclude-from /usr/src/exclude --recursive
linux.vanilla-2.6.22-rc6-mm1/drivers/ata/pata_pdc202xx_old.c
linux-2.6.22-rc6-mm1/drivers/ata/pata_pdc202xx_old.c
--- li
Alan Cox wrote:
Mirrors change in IT821X
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
diff -u --new-file --exclude-from /usr/src/exclude --recursive
linux.vanilla-2.6.22-rc6-mm1/drivers/ata/ata_generic.c
linux-2.6.22-rc6-mm1/drivers/ata/ata_generic.c
--- linux.vanilla-2.6.22-rc6-mm1/drivers/at
Lots of serial drivers check and optimise for setting the termios values
to the ones they were before. This is pointless and the check is wrong
anyway. Remove the checks on the serial drivers. If we ever do need such
a check put it back in the tty layer instead _once_!
Signed-off-by: Alan Cox <[EM
1 - 100 of 451 matches
Mail list logo
