Avi Kivity wrote:
The following patchset makes kvm more robust wrt cpu hotunplug, and
makes suspend-to-ram actually work. Suspend-to-disk benefits from
the cpu hotunplug improvements as well.
Here's the patchset diffstat in case anyone's interested:
Hello.
I think bind mounts were discussed when shared subtree
( http://lwn.net/Articles/159092/ ) was introduced.
For systems that allow users mount their CD/DVDs freely,
bind mounts are used and labeling files is a convenient way
to deny accessing somebody else's files.
But systems that don't
On Thu, May 24 2007, FUJITA Tomonori wrote:
> (cc's added)
>
> From: Jens Axboe <[EMAIL PROTECTED]>
> Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
> Date: Thu, 24 May 2007 14:05:54 +0200
>
> > On Thu, May 24 2007, Jens Axboe wrote:
> > > >
(cc's added)
From: Jens Axboe <[EMAIL PROTECTED]>
Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
Date: Thu, 24 May 2007 14:05:54 +0200
> On Thu, May 24 2007, Jens Axboe wrote:
> > >
Dear Auke
I'm sorry for being so late. Let me answer your questions.
> 82545's:
> 82545EM_COPPER
> 82545EM_FIBER
> Here you skip 3 other 82545 device ID's, was that intentional?
Maybe my understanding on the e1000 driver was wrong. I looked up the
following code, and thought the device
On Wed, 23 May 2007, Roland Dreier wrote:
> > - every static function in a header file must be __always_inline
>
> Why? Why does it matter whether a function is defined in a .h file or
> a .c file? Can't the compiler decide better than we can whether
> something should be inlined or not?
>
>
Ben Collins wrote:
This work around has been in use by almost any distribution trying to
support sparc64 since at least 2002. Without it, sunhme hangs fairly
quickly on UltraSPARC 1's.
Dave, I know it's not in the kernel because it isn't a "fix", but given
that we haven't seen a fix in more
n_hdlc, allow RESTARTSYS retval of tty write
Cc: Paul Fulghum <[EMAIL PROTECTED]>
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit 119ce83eb190c70d50ed7558c7b67b400ea00ec7
tree d334650d032ded74085a6951c0a1d3e3268fb7db
parent 221eebee5eedfa7c2463dcbfb545b92595512310
author Jiri Slaby
riscom8, eliminate busy loop
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit 221eebee5eedfa7c2463dcbfb545b92595512310
tree ea667b3ef038cff3a0e86266d37d364766a17303
parent a677db846e7951118d0409956f4197cc01194f99
author Jiri Slaby <[EMAIL PROTECTED]> Wed, 23 May 2007 17:30:19 +0200
init: wait for asynchronously scanned block devices
Some buses (e.g. USB and MMC) do their scanning of devices in the
background, causing a race between them and prepare_namespace().
In order to be able to use these buses without an initrd, we now
wait for the device specified in root= to
specialix, remove busy waiting
use msleep instead, because not in atomic
Cc: Roger Wolff <[EMAIL PROTECTED]>
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit a677db846e7951118d0409956f4197cc01194f99
tree f0b69d293f8c779111a1a7f0cf9cc37cf164a0c6
parent
moxa, eliminate busy waiting
blah, moxa delays 250+ ms in busy waiting, use msleep instead.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit 3f4308a387d98370556455e729787cc47f200757
tree 26ae5bab0e6f56a06c71c8f15533f643d070da4f
parent 4ea1257b890befc706f6d43562ba68671db39195
author Jiri
On Thu, 2007-05-24 at 10:01 +0200, Antonino Ingargiola wrote:
> Hi,
>
> 2007/5/23, Romano Giannetti <[EMAIL PROTECTED]>:
> [cut]
> > Uf, I will try to find the time. I am on my way to try to compile
> > 2.6.21.2 now. Problem is that a kernel compile "the ubuntu way" last
> > hours here. If there
The hotplug IPIs can be called from the cpu on which we are currently
running on, so use on_one_cpu(). Similarly, drop on_each_cpu() for the
suspend/resume callbacks, as we're in atomic context here and only one
cpu is up anyway.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
Only at the CPU_DYING stage can we be sure that no user process will
be scheduled onto the cpu and oops when trying to use virtualization
extensions.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
This defines on_one_cpu() which is similar to smp_call_function_single()
except that it works if cpu happens to be the current cpu. Can also be
seen as a complement to on_each_cpu() (which also doesn't treat the
current cpu specially).
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
CPU_DYING is notified in atomic context, so no taking mutexes here.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
arch/i386/kernel/cpu/mcheck/therm_throt.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/i386/kernel/cpu/mcheck/therm_throt.c
By keeping track of which cpus have virtualization enabled, we
prevent double-enable or double-disable during hotplug, which is a
very fatal oops.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c | 47 +++
1 files changed, 35
KVM wants a notification when a cpu is about to die, so it can disable
hardware extensions, but at a time when user processes cannot be scheduled
on the cpu, so it doesn't try to use virtualization extensions after they
have been disabled.
This adds a CPU_DYING notification. The notification is
CPU_DYING is called in atomic context, so don't try to take any locks.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
kernel/cpuset.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/kernel/cpuset.c b/kernel/cpuset.c
index f57854b..d4ab1c6 100644
---
The following patchset makes kvm more robust wrt cpu hotunplug, and
makes suspend-to-ram actually work. Suspend-to-disk benefits from
the cpu hotunplug improvements as well.
The major issue is that KVM wants to disable the virtualization
extensions at a point in time when no user processes are
On Thu, May 24 2007, Jens Axboe wrote:
> > http://git.kernel.org/?p=linux/kernel/git/tomo/linux-2.6-bidi.git;a=commitdiff;h=fb2747a9f2465ac4a1ea9e3533b92510fbcaae0c
>
> Neat, will take a look! I should be able to just reuse that.
BTW, when do you plan on pushing the SCSI sg update? I'd love for
On Tue, 2007-05-22 at 15:07 -0700, Linus Torvalds wrote:
>
> On Tue, 22 May 2007, Romano Giannetti wrote:
> >
> It's not known, no, and yeah, that's scary (and 60 seconds is long enough
> that most people would have grown bored and pushed the power button for
> five seconds, having considered
On Thu, May 24 2007, Jens Axboe wrote:
> > Oops: Kernel access of bad area, sig: 11 [#1]
> > SMP NR_CPUS=32 NUMA pSeries
> > Modules linked in: qla2xxx scsi_transport_fc
> > NIP: c00414a0 LR: c004162c CTR: 0001
> > REGS: c47bb130 TRAP: 0300 Not tainted
On some strange workload involving strace and fuse I get ocasional
long periods (10-100s) of total unresponsiveness, not even SysRq-*
working. Then the machine continues as normal. Nothing in dmesg,
absolutely no indication about what is happening.
Tried nmi_watchdog=1, but then the machine
Any chance the patches below that fix two mem leaks in XFS will make
it in in time for 2.6.22? I believe they should...
On 18/05/07, Jesper Juhl <[EMAIL PROTECTED]> wrote:
On Thursday 17 May 2007 04:40:24 David Chinner wrote:
> On Wed, May 16, 2007 at 11:31:16PM +0200, Jesper Juhl wrote:
> >
El Thu, 24 May 2007 17:45:04 +0800, "Qi Yong" <[EMAIL PROTECTED]> escribió:
> Hello,
>
> This duplicated paragraph problem was introduced by the following two
> commits. They are one patch actually.
D'oh, it seems the patch was picked from the mailing list and merged twice,
and I didn't notice
From: Jens Axboe <[EMAIL PROTECTED]>
Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
Date: Thu, 24 May 2007 11:34:41 +0200
> On Tue, May 22 2007, Badari Pulavarty wrote:
> > > If iommu=off works, can you try a normal boot but with this applied on
> > > top of the sglist patches?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan Engelhardt schrieb:
On May 24 2007 12:45, Lars K.W. Gohlke wrote:
Date: Thu, 24 May 2007 12:45:06 +0200
From: Lars K.W. Gohlke <[EMAIL PROTECTED]>
To: Jan Engelhardt <[EMAIL PROTECTED]>
Cc: Tilman Schmidt <[EMAIL PROTECTED]>,
Hi Richard,
On 5/24/07, Richard Purdie <[EMAIL PROTECTED]> wrote:
On Thu, 2007-05-24 at 01:04 +0530, Satyam Sharma wrote:
> On 5/23/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
> > [...]
> > +/* Macros for 'safe' decompression */
> > +#ifdef LZO1X_DECOMPRESS_SAFE
> > +
> > +#define
On Thu, May 24, 2007 at 08:47:13PM +1000, Herbert Xu wrote:
> On Thu, May 24, 2007 at 11:36:22AM +0100, Jeremy Fitzhardinge wrote:
> >
> > I got a hang while rmmodding e1000. sysrq-t shows:
> >
> > rmmod D 003FFAFC 6616 15923 15911 (NOTLB)
> >e9341e44 0092 82318c15
> > hd.c:(.init.text+0x44a7d): undefined reference to `drive_info'
> > hd.c:(.init.text+0x44a89): undefined reference to `drive_info'
> > hd.c:(.init.text+0x44a95): undefined reference to `drive_info'
> > hd.c:(.init.text+0x44aa1): undefined reference to `drive_info'
> > hd.c:(.init.text+0x44aad):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tilman Schmidt schrieb:
Am 14.05.2007 15:00 schrieb Lars K.W. Gohlke:
after searching the mailing list and searching the web, I still don't
know how to access correctly the serial port (in user space known as
/dev/ttyS01)
I can only tell you how
On May 24 2007 12:45, Lars K.W. Gohlke wrote:
>Date: Thu, 24 May 2007 12:45:06 +0200
>From: Lars K.W. Gohlke <[EMAIL PROTECTED]>
>To: Jan Engelhardt <[EMAIL PROTECTED]>
>Cc: Tilman Schmidt <[EMAIL PROTECTED]>, linux-kernel@vger.kernel.org
>Subject: Re: How to access correctly serial port inside
On 5/24/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
On 5/24/07, Satyam Sharma <[EMAIL PROTECTED]> wrote:
> [...]
> Just defining and exporting LZO1X_WORKMEM_SIZE may not be enough
> to guarantee that users _will_ pass in workmem of size exactly that much.
>
> If this workmem is really merely a
On Thu, May 24, 2007 at 11:36:22AM +0100, Jeremy Fitzhardinge wrote:
>
> I got a hang while rmmodding e1000. sysrq-t shows:
>
> rmmod D 003FFAFC 6616 15923 15911 (NOTLB)
>e9341e44 0092 82318c15 003ffafc e9341e2c e9341e14
> 823187a1
>003ffafc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan Engelhardt schrieb:
On May 24 2007 12:22, Lars K.W. Gohlke wrote:
ok, I have read everything and also have read the chapters about
tty_drivers. However I'm not really understand, how to ... .
I will summarize the concrete scenario, which will
Andrew Paprocki wrote:
...
> BUG: at /usr/src/linux-2.6.22-rc2/mm/slab.c:777 __find_general_cachep()
>
> Call Trace:
> [] __kmalloc+0x3e/0xbe
> [] cache_k8_northbridges+0x7f/0xf0
> [] gart_iommu_init+0x13/0x4f8
> [] kobject_shadow_add+0xef/0x1a2
> [] kobject_get+0x12/0x17
> []
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc2/2.6.22-rc2-mm1/
>
I got a hang while rmmodding e1000. sysrq-t shows:
rmmod D 003FFAFC 6616 15923 15911 (NOTLB)
e9341e44 0092 82318c15 003ffafc e9341e2c e9341e14
On May 24 2007 12:22, Lars K.W. Gohlke wrote:
>
> ok, I have read everything and also have read the chapters about
> tty_drivers. However I'm not really understand, how to ... .
>
> I will summarize the concrete scenario, which will lead to the
> understanding and further solution of deadling
smpboot: cachesize comparison fix in smp_tune_scheduling()
boot_cpu_data.x86_cache_size is signed int and can be < 0 too.
PS: this function is removed from current -mm.
Signed-off-by: Jarek Poplawski <[EMAIL PROTECTED]>
---
diff -Nurp 2.6.22-rc2-git5-/arch/i386/kernel/smpboot.c
The problem that an MTA on the route to me wrongly refused packages with
a 554 error is fixed, and I've resubscribed to linux-kernel.
If you sent me an email that bounced, please resend it.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tilman Schmidt schrieb:
Am 15.05.2007 10:43 schrieb Jan Engelhardt:
On May 15 2007 01:00, Tilman Schmidt wrote:
Am 14.05.2007 22:00 schrieb Jan Engelhardt:
On May 14 2007 19:40, Lars K.W. Gohlke wrote:
after searching the mailing list and
Hello,
After trying 2.6.22-rc2, I noticed the warning message from libata about
upgrading shutdown(8). First, I have two SATA disks, and get the warning for
only one of them. Second, I double-checked the source of shutdown for my
distro (Debian unstable), and do not see anything related to
On Wed, May 23, 2007 at 08:10:54PM -0700, Jesse Barnes wrote:
> > +/* Give unknown D-Link network adapters a proper class */
> > +static void __devinit quirk_dlink_unknown(struct pci_dev *dev)
> > +{
> > + if (dev->class = PCI_CLASS_UNKNOWN)
>
> Err, == of course. Obviously I didn't test this.
Pavel Machek wrote:
Well, in 2.6.73.1 we add 'trivial' one line to add new pci id, and in
2.6.73.2 we have data corruption, because that driver needed some
quirk we did not know about...?
False argument. -stable should only be merging patches that are already
upstream, and known.
Hi!
> >So, because of that, I don't really see a need to be
> >adding new device
> >ids to the -stable tree.
>
> Maybe you are just not seeing all the developers that
> keep bringing this up??
>
> Really, it is just silly to think that one-line PCI IDs
> patches will cause any harm at all,
> > That didn't used to work right on the AMD boards when I tried it last as
> > we ended up with a buffer that was mapped by the IOMMU for some reason
> > and that was not below 2GB.
>
> The physical address you mean? If that is still happening then it needs
> to get fixed. The allocation
On Thu, May 24 2007, FUJITA Tomonori wrote:
> From: Jens Axboe <[EMAIL PROTECTED]>
> Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
> Date: Thu, 24 May 2007 11:34:41 +0200
>
> > On Tue, May 22 2007, Badari Pulavarty wrote:
> > > > If iommu=off works, can you try a normal boot but
* Andrea Righi <[EMAIL PROTECTED]> wrote:
> Actually it seems that SIGKILLs are not printed. In
> get_signal_to_deliver() we have:
>
> [snip]
> @@ -1843,6 +1879,8 @@ relock:
>* Anything else is fatal, maybe with a core dump.
>*/
> current->flags |=
> Also there is the problem that some drivers use ZONE_DMA allocations
> because their device can only generate addresses below some limit, but
> on a platform with an IOMMU there is in fact no restriction on what
> memory the device can access.
Bzt - have to call your bluff on that one
The
> is this completely bad mojo ? is there some other mechanism that
> provides what i want and i just dont know about it ? or do i just
> make people change the driver to fit their application, thus throwing
> out the idea of keeping all board-specific details in just the boards
> file ...
There
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> [...] The only add-on change should be to not print SIGKILL events.
ah, that's already included in the version in -mm.
admittedly, the #ifdef __i386__ is quite lame, but there's no generic
safely-try-to-show-code-at-addr function available at the
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Thu, 24 May 2007 09:58:35 +0200 Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> >
> > * Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > > Well OK. But vdso-print-fatal-signals.patch is designated
> > > not-for-mainline anyway.
> >
> > btw., why?
On 19/05/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On Fri, 18 May 2007 12:01:41 EDT, "Robert P. J. Day" said:
> On Fri, 18 May 2007, debian developer wrote:
> > -your skills, and other developers will be aware of your presence. Fixing
> > bugs is one of the best ways to get merits among
On Tue, May 22 2007, Badari Pulavarty wrote:
> > If iommu=off works, can you try a normal boot but with this applied on
> > top of the sglist patches? That should fix gart mapping.
> >
> > diff --git a/arch/x86_64/kernel/pci-gart.c b/arch/x86_64/kernel/pci-gart.c
> > index 2e22a3a..b16384f 100644
Hi,
On Friday 18 May 2007, Thomas Kuther wrote:
> On Mi, 16.05.07 11:46 Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
> wrote:
>
> > > Shall I test it without "noraid=1" too?
> >
> > Please do, the main goal of the patch was to fix "RAID mode"
> > ("noraid=1" should work fine also without the
On Thu, May 24, 2007 at 03:47:45AM -0500, Daniel Newby wrote:
> On 5/24/07, Paul Mundt <[EMAIL PROTECTED]> wrote:
> > It sounds like your constraining your driver based on terminology.
> >Watchdogs on most embedded platforms support either a 'reset' mode or
> >otherwise act as periodic timers,
On Thu, May 24 2007, René Peters wrote:
> Hello!
>
> Inserting of audio CDs causes my system to hang with high I/O-load while
> kded's mediamanagement is running.
> Long time later (round about 10-20 minutes) the system comes back again and
> i'm able to play the audio CD. The issue is
Hello,
Below is a very preliminary patch that adds kexec/kdump invocation
functionality in kdb. It is currently based on 2.6.20.11 and
supported only for x86_64.
The main use case is for a user who would like to make use of the
interactive debugger but wants to conserve the option whether to
Ingo Molnar wrote:
> btw., i think some more consolidation could be done in this area. We've
> now got the traditional /proc/PID/stat metrics, schedstats, taskstats
> and delay accounting and with CFS we've got /proc/sched_debug and
> /proc/PID/sched. There's a fair amount of overlap.
>
Yes.
On Thursday 24 May 2007 03:28, James Morris wrote:
> On Wed, 23 May 2007, Andreas Gruenbacher wrote:
> > This is backwards from what AppArmor does. The policy defines which paths
> > may be accessed; all paths not explicitly listed are denied. If files are
> > mounted at multiple locations, then
On Wed, 2007-05-23 at 11:57 -0700, Ravikiran G Thirumalai wrote:
> > >OK, but could we please have a concise description of the impact
> > >of these changes on kernel memory footprint? Increase or decrease?
> > >And by approximately how much?
> >
> > Depending on how linker places percpu data,
Ingo Molnar wrote:
> * Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>> Well OK. But vdso-print-fatal-signals.patch is designated
>> not-for-mainline anyway.
>
> btw., why? It's very, very useful to distro, early-boot-userspace and
> glibc development. The only add-on change should be to not
On 5/24/07, Paul Mundt <[EMAIL PROTECTED]> wrote:
It sounds like your constraining your driver based on terminology.
Watchdogs on most embedded platforms support either a 'reset' mode or
otherwise act as periodic timers, trying to push both of these
functionalities in to a watchdog driver is
On Thu, 2007-05-24 at 01:04 +0530, Satyam Sharma wrote:
> On 5/23/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
> > diff --git a/include/linux/lzo1x.h b/include/linux/lzo1x.h
> > [...]
> > +/* Size of temp buffer (workmem) required by lzo1x_compress */
> > +#define LZO1X_WORKMEM_SIZE ((size_t)
In article <[EMAIL PROTECTED]>, you wrote:
>From: Randy Dunlap <[EMAIL PROTECTED]>
>
>If a parameter description begins with a '.', this indicates a
>"request" for "man" mode output (*roff), so it needs special
>handling.
>
>Problem case is in include/asm-i386/atomic.h for function
On Thu, 24 May 2007 10:01:21 +0200
"Antonino Ingargiola" <[EMAIL PROTECTED]> wrote:
> Is not the ubuntu or debian way to take hours to compile. Is that you
> have to trim the config and enable the only modules you need for your
> hardware, then a rebuild cycle could last 10-15 min.
Even 3-5 min
On Thu, 24 May 2007 09:58:35 +0200 Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > Well OK. But vdso-print-fatal-signals.patch is designated
> > not-for-mainline anyway.
>
> btw., why?
err, because that's what I decided a year ago. I wonder why
Hi,
When I exec aumix from console, the kernel oops seems in modprobe
process, and after a while , system hanged.
BUG: unable to handle kernel paging request at virtual address 646c6f68
printing eip:
c016531e
*pde =
Oops: [#1]
PREEMPT
Modules linked in: cifs snd_hda_intel snd_pcm
* Balbir Singh <[EMAIL PROTECTED]> wrote:
> Hi, Ingo,
>
> I've implemented a patch on top of v14 for better accounting of
> sched_info statistics. Earlier, sched_info relied on jiffies for
> accounting and I've seen applications that show "0" cpu usage
> statistics (in delay accounting and
Hi,
2007/5/23, Romano Giannetti <[EMAIL PROTECTED]>:
[cut]
Uf, I will try to find the time. I am on my way to try to compile
2.6.21.2 now. Problem is that a kernel compile "the ubuntu way" last
hours here. If there is an expert on make-kpkg here, I could use some
advise. I'd prefer to test
Pavel Emelianov wrote:
>> Index: linux-2.6.20/mm/rss_container.c
>> ===
>> --- linux-2.6.20.orig/mm/rss_container.c 2007-05-15 05:13:46.0
>> -0700
>> +++ linux-2.6.20/mm/rss_container.c 2007-05-16 20:45:45.0
Paul Menage wrote:
> On 5/24/07, Balbir Singh <[EMAIL PROTECTED]> wrote:
>> Kirill Korotaev wrote:
>> >> Where do we stand on all of this now anyway? I was thinking of
>> getting Paul's
>> >> changes into -mm soon, see what sort of calamities that brings about.
>> > I think we can merge Paul's
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> Well OK. But vdso-print-fatal-signals.patch is designated
> not-for-mainline anyway.
btw., why? It's very, very useful to distro, early-boot-userspace and
glibc development. The only add-on change should be to not print SIGKILL
events. Otherwise
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> > When a cpu is disabled, move_task_off_dead_cpu() is called for tasks
> > that have been running on that cpu.
>
> So I still have these three patches in the pending queue but I was
> rather hoping that the scheduler, sched-domains and cpuset
Hi,
Since 2.6.21 I can't mount my usb key (vfat).
I don't know if it's related to the vfat patch in 2.6.21.2
Here is the dmesg error parts:
FAT: invalid media value (0xb9)
VFS: Can't find a valid FAT filesystem on dev sdc.
Tell me if you need more infos.
Amaury
-
To unsubscribe from
On Wed, May 23, 2007 at 04:07:12PM -0700, Christoph Lameter wrote:
> On Wed, 23 May 2007, Russell King wrote:
> > At the end of the day, it is _far_ simpler from an architectural point
> > of view for memory to live in the DMA zone and disable the normal and
> > highmem zones than it is to
* Chuck Ebbert <[EMAIL PROTECTED]> wrote:
> > if (need_resched() && system_state == SYSTEM_RUNNING) {
> > - raw_local_irq_disable();
> > - _local_bh_enable();
> > - raw_local_irq_enable();
> > + local_bh_enable();
> > __cond_resched();
> >
Peter Williams wrote:
Peter Williams wrote:
Peter Williams wrote:
Dmitry Adamushko wrote:
On 18/05/07, Peter Williams <[EMAIL PROTECTED]> wrote:
[...]
One thing that might work is to jitter the load balancing interval a
bit. The reason I say this is that one of the characteristics of top
On 5/24/07, Balbir Singh <[EMAIL PROTECTED]> wrote:
Kirill Korotaev wrote:
>> Where do we stand on all of this now anyway? I was thinking of getting
Paul's
>> changes into -mm soon, see what sort of calamities that brings about.
> I think we can merge Paul's patches with *interfaces* and then
Kirill Korotaev wrote:
>> Where do we stand on all of this now anyway? I was thinking of getting
>> Paul's
>> changes into -mm soon, see what sort of calamities that brings about.
> I think we can merge Paul's patches with *interfaces* and then switch to
> developing/reviewing/commiting resource
* Christoph Lameter <[EMAIL PROTECTED]> wrote:
> +SLUB Debug output
> +-
> +
> +Here is a sample of slub debug output:
> +
> +*** SLUB kmalloc-8: Redzone [EMAIL PROTECTED] slab 0xc528c530 offset=3360
> flags=0x40c3 inuse=61 freelist=0xc90f6d58
> + Bytes b4 0xc90f6d10: 00
On Wed, 23 May 2007, Dmitry Torokhov wrote:
> It looks like you are now in the same position I was some time ago WRT
> to debug information for i8042 - constantly asking people to enable
> debug, recompile and send the results. May I recommend changing
> CONFIG_HID_DEBUG to "default y if
On Wed, May 23 2007, Christoph Lameter wrote:
> On Wed, 23 May 2007, Jens Axboe wrote:
>
> > That works for me with the patch, .config attached.
>
> H... That means the .config sent initially here was bogus.
?
Considering we're trying to help you fix bugs in your code, you could be
On Thursday 24 May 2007 03:00:56 David Miller wrote:
> From: Ingo Molnar <[EMAIL PROTECTED]>
> Date: Wed, 23 May 2007 13:40:21 +0200
>
> > * Herbert Xu <[EMAIL PROTECTED]> wrote:
> > > [NET_SCHED]: Fix qdisc_restart return value when dequeue is empty
> > >
> > > My previous patch that changed the
Jared Hulbert wrote:
To me, it looks like this
work can be modified to use filemap_xip.
How?
First, get a struct page behind the subject file system image. A good
idea to get there is to use vmem_map, which allows have a
discontiguous mem_map array in virtual storage. Then add the memory
On Wed, 23 May 2007 11:08:42 -0700,
Greg KH <[EMAIL PROTECTED]> wrote:
> Ok, yeah, that is wierd.
>
> Kay found the problem (he's traveling right now) and here's his updated
> version of the patch which should work for everyone involved.
>
> Please let me know if this causes any problems or
Richard Griffiths (wrs) wrote:
One question I have is the difference in the two models. If I understand
correctly the filemap_xip expects the ext2 to mount as XIP while the
Linear Cramfs only enables XIP for apps that have the sticky bit set.
Hence the Application XIP moniker.
Does the
On Wed, May 23, 2007 at 02:06:16PM +0200, Ingo Molnar wrote:
>
> i'm pleased to announce release -v14 of the CFS scheduler patchset.
>
> The CFS patch against v2.6.22-rc2, v2.6.21.1 or v2.6.20.10 can be
> downloaded from the usual place:
>
>
From: Patrick McHardy <[EMAIL PROTECTED]>
Date: Thu, 24 May 2007 07:41:00 +0200
> David Miller wrote:
> >>* Herbert Xu <[EMAIL PROTECTED]> wrote:
> >>
> >>>[NET_SCHED]: Fix qdisc_restart return value when dequeue is empty
> >
> > Applied, thanks everyone.
>
>
> Even though it didn't fix this
Hi Mike.
Forwarding this to Roman Zippel which is the kconfig maintainer.
The intent with this is clear but the solution you suggest albeit simple
does not really match where we could end up with kconfig.
Recently Roman added support for options in the kconfig language
and I would assume we
On 05/24/2007 07:11 AM, Rene Herman wrote:
Okay. I would by the way not be against turning the timestamping off
by default and turning it _on_ with a "timestamps" or "logtime" or
whatever option.
Yes I only now looked. Sorry, didn't realise that was how it already worked.
CONFIG_PRINTK_TIME
Linus Torvalds wrote:
Things like: A20 gate, 15-16MB holes, i387 FP exception on irq 13 are
totally pointless in this day and age. Things like the DMA controller are
getting there, along with PS/2 keyboard support.
The latest Intel chipset I have (ICH9) is legacy free: no serial port
and
Linus Torvalds wrote:
Things like: A20 gate, 15-16MB holes, i387 FP exception on irq 13 are
totally pointless in this day and age. Things like the DMA controller are
getting there, along with PS/2 keyboard support.
The latest Intel chipset I have (ICH9) is legacy free: no serial port
and
On 05/24/2007 07:11 AM, Rene Herman wrote:
Okay. I would by the way not be against turning the timestamping off
by default and turning it _on_ with a timestamps or logtime or
whatever option.
Yes I only now looked. Sorry, didn't realise that was how it already worked.
CONFIG_PRINTK_TIME
Hi Mike.
Forwarding this to Roman Zippel which is the kconfig maintainer.
The intent with this is clear but the solution you suggest albeit simple
does not really match where we could end up with kconfig.
Recently Roman added support for options in the kconfig language
and I would assume we
From: Patrick McHardy [EMAIL PROTECTED]
Date: Thu, 24 May 2007 07:41:00 +0200
David Miller wrote:
* Herbert Xu [EMAIL PROTECTED] wrote:
[NET_SCHED]: Fix qdisc_restart return value when dequeue is empty
Applied, thanks everyone.
Even though it didn't fix this problem, this patch I
On Wed, May 23, 2007 at 02:06:16PM +0200, Ingo Molnar wrote:
i'm pleased to announce release -v14 of the CFS scheduler patchset.
The CFS patch against v2.6.22-rc2, v2.6.21.1 or v2.6.20.10 can be
downloaded from the usual place:
http://people.redhat.com/mingo/cfs-scheduler/
Richard Griffiths (wrs) wrote:
One question I have is the difference in the two models. If I understand
correctly the filemap_xip expects the ext2 to mount as XIP while the
Linear Cramfs only enables XIP for apps that have the sticky bit set.
Hence the Application XIP moniker.
Does the
401 - 500 of 988 matches
Mail list logo
