On Tue, 2007-03-20 at 07:11 +0100, Willy Tarreau wrote:
> Also, while I don't agree with starting to renice X to get something usable,
> it seems real that there's something funny on Mike's system which makes it
> behave particularly strangely when combined with RSDL, because other people
> in com
On Tue, 2007-03-20 at 18:47 +1100, David Chinner wrote:
> On Mon, Mar 19, 2007 at 04:57:37PM +0100, Peter Zijlstra wrote:
> > This patch-set implements per device dirty page throttling. Which should
> > solve
> > the problem we currently have with one device hogging the dirty limit.
> >
> > Preli
Hi Eric!
On 03/19/2007 06:44 PM, Eric W. Biederman wrote:
Oliver Falk <[EMAIL PROTECTED]> writes:
[ ... ]
The kernel uname function at least does not have fields that
report processor or hardware platform.
But on i386 it reports:
[EMAIL PROTECTED] ~]$ uname -mpi
i686 i686 i386
And I remembe
2007/3/20, Thomas Gleixner <[EMAIL PROTECTED]>:
On Mon, 2007-03-19 at 22:51 +0100, Stefan Prechtel wrote:
> 2007/3/19, Thomas Gleixner <[EMAIL PROTECTED]>:
> > On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
> > >CPU0 CPU1
> > > 0: 28289 0 local-APIC-ed
On Mon, 19 Mar 2007 18:42:22 +0100, Jesper Juhl wrote:
> --- a/drivers/block/floppy.c
> +++ b/drivers/block/floppy.c
> @@ -4302,7 +4302,12 @@ static int __init floppy_init(void)
> if (err)
> goto out_flush_work;
>
> - device_create_file(&floppy_devi
On Tue, Mar 20, 2007 at 05:46:46PM +1100, Keith Owens wrote:
> Should pnpacpi probe and setup the serial devices even when thay have
> already been setup? Or this is something strange about the UART in
> this particular box?
Yes, so it can be associated with the correct device.
No idea why it's
On Tue, 2007-03-20 at 07:11 +0100, Willy Tarreau wrote:
> I don't agree with starting to renice X to get something usable
X looks very special to me: it's a big userspace driver, the primary
task handling user interaction on the desktop, and on some OS the part
responsible for moving the mouse poi
On 20/03/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
Andrew Morton wrote:
> On Tue, 20 Mar 2007 13:47:53 +1100 Nick Piggin <[EMAIL PROTECTED]> wrote:
>
>
>>Andrew Morton wrote:
>>
>>Hang on a sec... I'll try fixing the thing before you next make a
>>release.
>>
>
>
> Too late. hot-fixes/ awaits
On Mon, 2007-03-19 at 21:27 -0700, Greg KH wrote:
> On Sat, Mar 17, 2007 at 02:26:57PM +0100, Andi Kleen wrote:
> > Arjan van de Ven <[EMAIL PROTECTED]> writes:
> > >
> > > well we can do the handshake to take ownership like we do much later in
> > > boot, but that requires PCI to be there and ful
On Tue, 2007-03-20 at 01:36 -0400, Eric St-Laurent wrote:
> On Tue, 2007-20-03 at 01:04 -0400, Lee Revell wrote:
>
> > I think CONFIG_TRY_TO_DISABLE_SMI would be excellent for debugging,
> > not to mention people trying to spec out hardware for RT
> > applications...
>
> There is a SMI disabling
On 20/03/07, Mikael Pettersson <[EMAIL PROTECTED]> wrote:
On Mon, 19 Mar 2007 18:42:22 +0100, Jesper Juhl wrote:
> --- a/drivers/block/floppy.c
> +++ b/drivers/block/floppy.c
> @@ -4302,7 +4302,12 @@ static int __init floppy_init(void)
> if (err)
> goto out_flu
Hello,
on my notebook, the built in wlan card uses the ipw2100 driver. On boot
time, the ipw2100 module is loaded and fires a hotplug "add" event.
The hotplug event configures the interface and starts wpa_supplicant and
wpa_cli.
The ipw2100 chip can be enabled/disabled by a hardware switch, so i
On 19-03-2007 07:24, Neil Brown wrote:
> On Friday March 16, [EMAIL PROTECTED] wrote:
>> OK. That's not necessarily a bug: one could envisage a (weird) piece of
>> code which takes a lock then releases it on a later workqueue invokation.
>> But I'm not sure that nfs4_laundromat() is actually supp
Thomas Gleixner wrote:
> I finally found a dual core box, which survives suspend/resume without
> crashing in the middle of nowhere. Sigh, I never figured out from the
> code and the bug reports what's going on.
>
> The observed hangs are caused by a stale state transition of the clock
> event de
Hello,
>> How can I put delay between subsequent msg sends to achieve desired
>> packet rate without loses, e.g., 3.5Gbps without bursts? Even nanosleep()
>> with the lowest possible delay seems to be too much delay. Busy loop with
>> clock_gettime(3) works OK on SMP boxes, but on UP it causes pro
On Tue, Mar 20, 2007 at 09:08:24AM +0100, Peter Zijlstra wrote:
> On Tue, 2007-03-20 at 18:47 +1100, David Chinner wrote:
> > So overall we've lost about 15-20% of the theoretical aggregate
> > perfomrance, but we haven't starved any of the devices over a
> > long period of time.
> >
> > However,
On 2007/03/19 13:09, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> I may have missed the answer to this before, but: does the problem
> go away if you disable preempt?
On my system (same problem, original bug report), preemption is
disabled.
Max
-
To unsubscribe from this list: send the line "unsubsc
On Tue, 2007-03-20 at 20:38 +1100, David Chinner wrote:
> On Tue, Mar 20, 2007 at 09:08:24AM +0100, Peter Zijlstra wrote:
> > On Tue, 2007-03-20 at 18:47 +1100, David Chinner wrote:
> > > So overall we've lost about 15-20% of the theoretical aggregate
> > > perfomrance, but we haven't starved any o
Andrew Morton wrote:
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>
> Will appear later at
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
>
>
>
[All of the below is from the pre hot-fix runs. The very few results
w
Hi!
> In 2.6.21-rc1,2,3, my laptop will fully suspend to ram, but then
> *immediately* resumes back from suspension. (It resumes just fine, as well.)
>
> Nothing out of the ordinary is logged, and this happens even when
> booting into init=/bin/sh with minimal modules loaded and executing
> s2ram
On Mon, Mar 19, 2007 at 01:41:25PM -0700, Greg KH wrote:
> On Mon, Mar 19, 2007 at 06:30:13PM +0300, Alexey Dobriyan wrote:
> > Steps to reproduce:
> >
> > # modprobe p4-clockmod
> > $ cd /sys/devices/system/cpu/cpu0/cpufreq/
> > # rmmod p4-clockmod
> > $ cat stats/time_in_state
> >
On Mon, 19 Mar 2007 17:43:38 -0400, Bob Copeland wrote:
> I tried out an earlier version of this patch several months ago just to play
> around with the joystick part of the accelerometer driver on my MacBook, and
> found that it was backwards in the y-direction compared to what Neverball
> seemed
struct clocksource is a critical data structure.
Most of its fields are read only, some of them are heavily modified at each
timer interrupt.
It makes sense to separate those fields and make sure they all share one cache
line, or at least the minimum for machines with small cache lines.
Signed
Op Tuesday 20 March 2007, schreef Bill Davidsen:
> Kasper Sandberg wrote:
> > On Sun, 2007-03-18 at 08:38 +0100, Mike Galbraith wrote:
> >> On Sun, 2007-03-18 at 08:22 +0100, Radoslaw Szkodzinski wrote:
> >>> I'd recon KDE regresses because of kioslaves waiting on a pipe
> >>> (communication with t
Op Tuesday 20 March 2007, schreef Linus Torvalds:
> On Mon, 19 Mar 2007, Xavier Bestel wrote:
> > > >> Stock scheduler wins easily, no contest.
> > > >
> > > > What happens when you renice X ?
> > >
> > > Dunno -- not necessary with the stock scheduler.
> >
> > Could you try something like renice -
Adrian Bunk wrote:
> This email lists some known regressions in Linus' tree compared to 2.6.20.
Since I didn't see any mention of this:
I'm seeing an Oops when removing the ohci1394 module:
[ 16.047275] ieee1394: Node removed: ID:BUS[158717321-38:0860]
GUID[c033ced6]
[ 16.047287] B
Hello!
Here are more informations... the problem seems to be a little bit more
special.
1.) I've bootet these systems through NFS and would like to access
/dev/sda or /dev/sdb then. For example via fdisk and this does not work.
2.) I've now tested the following kernels -
2.6.18.8 - works
2.
Hello LKML,
Second repost of "BUG: Killing and reviving files with USB disks", this time
also destined to linux-fsdevel.
This is a reproducible demonstration of the problem initially reported in my
first e-mail, titled "PROBLEM: 'bio too big device' after moving to a USB
disk" (http://lkml.org/l
David Woodhouse <[EMAIL PROTECTED]> wrote:
> > hm, did you try running this on x86_64?
>
> I don't have any. I only tested it on PowerPC and i386. Others then
> provided more exclusions for SPARC and maybe ARM, although I'm not sure
> you have the latter yet. It's not hard to add extra exclusions
When testing how JFFS2 handles write errors, the following message appears:
BUG: sleeping function called from invalid context at
include/linux/writeback.h:76
Here is the terminal output:
# uname -a
Linux ahunter-desktop 2.6.20ded11 #13 SMP PREEMPT Mon Mar 19 16:20:42 EET 2007
i686 GNU/Linu
On Tue, Mar 20, 2007 at 07:43:08AM +, David Woodhouse wrote:
> On Mon, 2007-03-19 at 16:42 -0700, Andrew Morton wrote:
> > hm, did you try running this on x86_64?
>
> I don't have any. I only tested it on PowerPC and i386. Others then
> provided more exclusions for SPARC and maybe ARM, althoug
On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote:
>
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
[..]
> +complain-about-missing-system-calls.patch
> +complain-about-missing-system-calls-update.patch
Hi,
I needed the following patch to fix this compile e
Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> As I understand your description for non-shared mappings the VMAs are
> per process.
Are you talking about the current state of play? If so, not precisely. In
the current scheme of things, *all* VMAs are kept in a global tree and are
globally avail
Hi Pavel,
I'm sorry for my late reply.
Pavel Machek wrote:
> Hi!
>
>>+If you don't want to dump all shared memory segments attached to pid 1234,
>>+write 0 to the process's proc file.
>>+
>>+ $ echo 1 > /proc/1234/coredump_omit_anonymous_shared
>
> Write 0?
Thank you for pointing out.
It see
On 15-03-2007 20:17, Folkert van Heusden wrote:
>>> On Tue, 13 Mar 2007 17:50:14 +0100 Folkert van Heusden <[EMAIL PROTECTED]>
>>> wrote:
...
> Haha ok :-)
>
> Good, since I run 2.6.20 with these debugging switches switched on, I
> get occasionally errors like these. I get ALWAYS the following er
On Tue, Mar 20, 2007 at 11:24:41AM +0100, Tobias Diedrich wrote:
> Adrian Bunk wrote:
> > This email lists some known regressions in Linus' tree compared to 2.6.20.
>
> Since I didn't see any mention of this:
>
> I'm seeing an Oops when removing the ohci1394 module:
>
> [ 16.047275] ieee1394:
Hi!
> Thanks, that Kconfig change seems like the simplest solution for this.
Simplest, maybe, but is it right? Ptrace should work without /proc, no?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsub
On Tue, Mar 20, 2007 at 12:17:01PM +0100, Jarek Poplawski wrote:
...
> IMHO lockdep found that two locks are taken in different order:
>
> -> #1: 1) tty_mutex in con_console() 2) dqptr_sem (somewhere later)
> -> #0: 1) dqptr_sem 2) tty_console in dquot_alloc_space() with print_warning()
Should be
On Tue, Mar 20, 2007 at 12:22:53PM +0100, Jarek Poplawski wrote:
> On Tue, Mar 20, 2007 at 12:17:01PM +0100, Jarek Poplawski wrote:
> ...
> > IMHO lockdep found that two locks are taken in different order:
> >
> > -> #1: 1) tty_mutex in con_console() 2) dqptr_sem (somewhere later)
> > -> #0: 1) dq
> The floppy driver's sysfs file just provides some auxiliary
> information to user-space, none of which matters for most of
> its users. It is IMO totally inappropriate to fail floppy
> driver init in this case.
I thought it was for udev to create the device nodes? But
I might be wrong on that.
On Mon, Mar 19, 2007 at 09:27:34PM -0700, Greg KH wrote:
> On Sat, Mar 17, 2007 at 02:26:57PM +0100, Andi Kleen wrote:
> > Arjan van de Ven <[EMAIL PROTECTED]> writes:
> > >
> > > well we can do the handshake to take ownership like we do much later in
> > > boot, but that requires PCI to be there
Am Dienstag, 20. März 2007 12:36 schrieb Andi Kleen:
> It's long after timer calibration, which is what it interfered with here.
>
> To handle that it would need to be moved to the x86 early quirks and
> use boot_ioremap etc. It would be probably somewhat messy, but doable.
USB is not specific to
On Mon, Mar 19, 2007 at 04:25:29PM -0700, Andrew Morton wrote:
> On Sun, 18 Mar 2007 19:35:48 +0100
> Michal Piotrowski <[EMAIL PROTECTED]> wrote:
>
> > WARNING: could not find versions for .tmp_versions/built-in.mod
> > WARNING: could not find versions for .tmp_versions/built-in.mod
> > WARNING:
On Tue, 20 Mar 2007 12:29:49 +0100 (CET), Andreas Kleen <[EMAIL PROTECTED]>
wrote:
> > The floppy driver's sysfs file just provides some auxiliary
> > information to user-space, none of which matters for most of
> > its users. It is IMO totally inappropriate to fail floppy
> > driver init in this
Hi!
Run this script. The s2ram at the end of it will wakeup immediately
after going to sleep, bad. I tried reproducing it with smaller
version, but was not too successful.
Pavel
#!/bin/bash
killall klogd
echo -n "testing refrigerato
Hi!
> Run this script. The s2ram at the end of it will wakeup immediately
> after going to sleep, bad. I tried reproducing it with smaller
> version, but was not too successful.
Actually
> sleep 2
> echo -n "testing swsusp (platform)..."
> echo platform > /sys/power/disk
> echo disk > /sys/power
On Tue 20-03-07 12:31:51, Jarek Poplawski wrote:
> On Tue, Mar 20, 2007 at 12:22:53PM +0100, Jarek Poplawski wrote:
> > On Tue, Mar 20, 2007 at 12:17:01PM +0100, Jarek Poplawski wrote:
> > ...
> > > IMHO lockdep found that two locks are taken in different order:
> > >
> > > -> #1: 1) tty_mutex in
On Thu, Mar 08, 2007 at 04:14:07PM -0800, David Miller wrote:
> From: David Woodhouse <[EMAIL PROTECTED]>
> Date: Thu, 08 Mar 2007 23:01:13 +
>
> > Most system calls seem to get added to i386 first. This patch
> > automatically generates a warning for any new system call which is
> > implement
On Mon, 2007-03-19 at 14:54 -0500, Matt Mackall wrote:
>
> False starts that get mainlined delay or prevent things getting done
> right. The question is and remains "is UBI the right way to do
> things?" Not "is UBI the easiest way to do things?" or "is UBI
> something people have already adopted?
On Mon, Mar 19, 2007 at 05:27:11PM -0700, Randy Dunlap wrote:
> On Wed, 7 Mar 2007 20:19:15 -0800 Andrew Morton wrote:
>
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc3/2.6.21-rc3-mm2/
> >
> > - This is the same as 2.6.21-rc3-mm1, except Con's CPU scheduler chang
>
> iSCSI/nbd(6)
> |
> filesystem {swap | ext3ext3 jffs2
> \ | || /
>/ \ | dm-crypt->snapshot(5) /
> device mapper -|\ \ | /
>
Nick Piggin wrote:
Rik van Riel wrote:
We apply pressure to each of sets of the pageout queues based on:
- the size of each queue
- the fraction of recently referenced pages in each queue,
not counting used-once file pages
- swappiness (file IO is more efficient than swap IO)
This ignore
Hi!
...and cause is really simple.
During resume, we do not know that "reboot" method was used, so we
assume plaform and make the led blink...
Unfortunately I see no easy solution, and this may/will cause other
problems -- in case of broken bios and user telling us not to call
that bios, we'll c
Hi!
..and machine is pretty unhappy about that. I triggered it by
paralel-building kernel while suspending/resuming.
[EMAIL PROTECTED]:/home/pavel/sf/suspend# date
Thu Feb 12 05:22:32 CET 1914
[EMAIL PROTECTED]:/home/pavel/sf/suspend#
...and no, it is not easily reproducible :-(.
Hi!
I got this nastinness in my syslog... perhaps HDA intel takes too long
to play with its hardware? Or should we just kill the softlockup
watchdog since Linux is not realtime system, yet?
Pavel
HDA Intel :00:1b.0: freeze
BUG:
At Tue, 20 Mar 2007 13:32:53 +0100,
Pavel Machek wrote:
>
> Hi!
>
> I got this nastinness in my syslog... perhaps HDA intel takes too long
> to play with its hardware? Or should we just kill the softlockup
> watchdog since Linux is not realtime system, yet?
X60/T60 is known to be often broken re
Xavier Bestel wrote:
> On Tue, 2007-03-20 at 07:11 +0100, Willy Tarreau wrote:
>> I don't agree with starting to renice X to get something usable
>
> X looks very special to me: it's a big userspace driver, the primary
> task handling user interaction on the desktop, and on some OS the part
> resp
Stephane Jourdois wrote:
On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
[..]
+complain-about-missing-system-calls.patch
+complain-about-missing-system-calls-update.patch
Hi,
I needed the following patch to
Hi!
> > The patch is designed to minimize the amount of changes and there are some
> > nice
> > simplifications and optimizations possible on top of it. I am going to
> > implement them separately in the future.
>
> Blows up with ia64 allmodconfig due to CONFIG_PM=y, CONFIG_SOFTWARE_SUSPEND=n:
Linus Torvalds wrote:
Quite frankly, I was *planning* on merging RSDL very early after 2.6.21,
but there is one thing that has turned me completely off the whole thing:
- the people involved seem to be totally unwilling to even admit there
might be a problem.
Not to mention that it see
Hi!
> > I got this nastinness in my syslog... perhaps HDA intel takes too long
> > to play with its hardware? Or should we just kill the softlockup
> > watchdog since Linux is not realtime system, yet?
>
> X60/T60 is known to be often broken regarding the communication
> between the controller an
> Yes, I was looking at it. Hmm, we can possibly get rid of tty_mutex being
> acquired under dqptr_sem in quota code. But looking at the path from
> con_close() there's another inversion with i_mutex which is also acquired
> along the path for sysfs. And we can hardly get rid of it in the quota
At Tue, 20 Mar 2007 14:22:03 +0100,
Pavel Machek wrote:
>
> Hi!
>
> > > I got this nastinness in my syslog... perhaps HDA intel takes too long
> > > to play with its hardware? Or should we just kill the softlockup
> > > watchdog since Linux is not realtime system, yet?
> >
> > X60/T60 is known t
On Tue, Mar 20, 2007 at 01:19:09PM +0100, Jan Kara wrote:
> On Tue 20-03-07 12:31:51, Jarek Poplawski wrote:
> > On Tue, Mar 20, 2007 at 12:22:53PM +0100, Jarek Poplawski wrote:
> > > On Tue, Mar 20, 2007 at 12:17:01PM +0100, Jarek Poplawski wrote:
> > > ...
> > > > IMHO lockdep found that two lock
Hello,
I don't see any announcement for 2.6.21-rc4-mm1 on LKML, but I went
ahead and tried it out. I hit the following, even after running
mrproper.
init/.missing_syscalls.h.cmd:2: *** missing separator. Stop.
make: *** [.tmp_vmlinux1] Error 2
-
To unsubscribe from this list: send the line "un
On Tue, Mar 20, 2007 at 02:25:49PM +0200, Artem Bityutskiy wrote:
> You failed to clearly define what is block until now, then you blame me
> that I do not understand you. So I see block = eraseblock, lets assume
> for further conversation.
>
> OK. Suppose we have done what you say, although I _do
On Tue 20-03-07 14:44:46, Jarek Poplawski wrote:
> On Tue, Mar 20, 2007 at 01:19:09PM +0100, Jan Kara wrote:
> > On Tue 20-03-07 12:31:51, Jarek Poplawski wrote:
> > > On Tue, Mar 20, 2007 at 12:22:53PM +0100, Jarek Poplawski wrote:
> > > > On Tue, Mar 20, 2007 at 12:17:01PM +0100, Jarek Poplawski
adds device ids of two Fujitsu Siemens Tablet PCs to pnp_dev_table
Signed-off-by: Danny Kukawka <[EMAIL PROTECTED]>
--- linux-2.6.21-rc4/drivers/serial/8250_pnp.c 2007-03-19 21:42:43.0
+0100
+++ linux-2.6.21-rc5/drivers/serial/8250_pnp.c 2007-03-19 21:55:53.0
+0100
@@ -340,6 +
On Tue 20-03-07 14:35:10, Arjan van de Ven wrote:
>
>
> > Yes, I was looking at it. Hmm, we can possibly get rid of tty_mutex being
> > acquired under dqptr_sem in quota code. But looking at the path from
> > con_close() there's another inversion with i_mutex which is also acquired
> > along th
On Tuesday 20 March 2007 11:33, Stefan Priebe wrote:
> 1.) I've bootet these systems through NFS and would like to access
> /dev/sda or /dev/sdb then. For example via fdisk and this does not work.
What do you mean by "booted through NFS"? Do you mean the machine
runs with the root file system moun
Hello!
It runs with nfsroot
# mount
192.168.0.100:/PXE/debian on / type nfs (rw)
Kernel command line: nfs root=/dev/nfs nfsroot=192.168.0.100:/PXE/debian
ip=dhcp
Stefan
Olaf Kirch schrieb:
On Tuesday 20 March 2007 11:33, Stefan Priebe wrote:
1.) I've bootet these systems through NFS and w
At Mon, 19 Mar 2007 21:39:43 +0100,
Adrian Bunk wrote:
>
> Subject: snd-intel8x0: no 3d surround sound
> References : http://lkml.org/lkml/2007/3/5/164
> Submitter : Michal Piotrowski <[EMAIL PROTECTED]>
> Caused-By : Randy Cushman <[EMAIL PROTECTED]>
> commit 831466f4ad2b5fe23d
Hello!
Here a some more information:
- sometimes the whole systems crash - sometimes they are still alive
- if they are alive fdisk consumes 99% CPU
- fdisk cannot be killed also not with kill -9
- the same happens with a cat on /dev/sdX
- no problem when trying to access /dev/hdX
Stefan
Olaf K
> - on a 2.6.20 system, try "dd if=/dev/sdb of=/dev/null bs=4k count=1" or
>something like this (with NFS root) - does this crash, too?
no it does not crash it is also no problem to set the count= to 1 or
so or change the bs to 16k ...
> - do you have ACLs on files in /dev?
no
> - e
This adds an optional wrapper around ata_ac_issue_prot that triggers the LED
layer.
This is used for the PMU LED on G5 towers (IDE trigger). My test platform is a
PowerMac 7,3 (Dual G5 2.0GHz, June 2004) with a K2 (sata_svw) controller.
Now respun as a single patch, and the function name shortene
Tony Vroon wrote:
> This adds an optional wrapper around ata_ac_issue_prot that triggers the LED
> layer.
> This is used for the PMU LED on G5 towers (IDE trigger). My test platform is
> a
> PowerMac 7,3 (Dual G5 2.0GHz, June 2004) with a K2 (sata_svw) controller.
> Now respun as a single patch,
Hello!
With the sysrq i've found the function with is the problem:
inode.c => nfs_getattr => nfs_sync_mapping_range
I've also found the attached patch - which is not included in any stable
release nor in 2.6.21.X but is public since 20.02.07
I think this is very important.
Stefan Priebe
comm
Miles Lane a écrit :
> Hello,
>
> I don't see any announcement for 2.6.21-rc4-mm1 on LKML, but I went
> ahead and tried it out. I hit the following, even after running
> mrproper.
>
> init/.missing_syscalls.h.cmd:2: *** missing separator. Stop.
> make: *** [.tmp_vmlinux1] Error 2
Would you ple
On Tue, 2007-03-20 at 15:21 +0100, Jan Kara wrote:
> On Tue 20-03-07 14:35:10, Arjan van de Ven wrote:
> >
> >
> > > Yes, I was looking at it. Hmm, we can possibly get rid of tty_mutex
> > > being
> > > acquired under dqptr_sem in quota code. But looking at the path from
> > > con_close() ther
This patch does several things to allow the underlying hardware to be
shared amount many devices. The most important thing is the use of
the created device via device_create instead of the hardware device. No
longer should fbdev drivers use the xxx_set_drvdata with the parent
bus device. The sec
On 3/20/07, Stéphane Jourdois <[EMAIL PROTECTED]> wrote:
Miles Lane a écrit :
> Hello,
>
> I don't see any announcement for 2.6.21-rc4-mm1 on LKML, but I went
> ahead and tried it out. I hit the following, even after running
> mrproper.
>
> init/.missing_syscalls.h.cmd:2: *** missing separator.
> Or new, user defined, ones?
there's always the "CHANGED" event.. it's very very generic and just
means "check my state for new stuff"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger
Andrew Morton napsal(a):
> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
I'm getting this while trying to swsusp:
Stopping tasks ...
Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze):
swapper
Restarting tasks ... done.
What to test? Enable PM_DEBUG?
regards,
-
On Tuesday 20 March 2007 00:46, Keith Owens wrote:
> Booting with 'console=tty console=ttyS0,9600'. The serial console on
> ttyS0 (0x3f8, irq 4) is probed twice, once from serial8250_init() and
> again from serial_pnp_probe().
I played with this last summer, but was too timid to finish it
and pos
It looks like the number of section mismatches is much reduced, which
is great. But, I don't remember seeing "WARNING: could not find
versions for ..." warnings before. Is this an artifact of the
init/.missing_syscalls.h problem I encountered earlier?
MODPOST vmlinux
WARNING: could not find ve
Miles Lane a écrit :
> On 3/20/07, Stéphane Jourdois <[EMAIL PROTECTED]> wrote:
>> Miles Lane a écrit :
>> > Hello,
>> >
>> > I don't see any announcement for 2.6.21-rc4-mm1 on LKML, but I went
>> > ahead and tried it out. I hit the following, even after running
>> > mrproper.
>> >
>> > init/.miss
Francois Romieu wrote:
RSA is slow. syscalls are fast.
Which part of the kernel is supposed to benefit from this code ?
The main purpose behind the development of this module was to create an in-kernel
system of signed modules. The scenario applies most in embedded systems that are running l
Thanks for your comments
On Mon, Mar 19, 2007 at 06:22:15PM +0200, Tasos Parisinos wrote:
+static inline _i32 rsa_max(_i32 x, _i32 y)
+{
+return (x > y)? x: y;
+}
We've got a max() already. Use tabs.
This is right, will be fixed, just hate discipline
+
+/*
+ * Module loading callback
The Makefile fragment in Documentation/kbuild/modules.txt looks to be
missing some braces.
Signed-off-by: Anton Blanchard <[EMAIL PROTECTED]>
---
diff --git a/Documentation/kbuild/modules.txt b/Documentation/kbuild/modules.txt
index 769ee05..1d247d5 100644
--- a/Documentation/kbuild/modules.txt
Pavel Machek wrote:
> Hi!
>
>> In 2.6.21-rc1,2,3, my laptop will fully suspend to ram, but then
>> *immediately* resumes back from suspension. (It resumes just fine, as well.)
>>
>> Nothing out of the ordinary is logged, and this happens even when
>> booting into init=/bin/sh with minimal modules
On Tue, 20 Mar 2007, Tasos Parisinos wrote:
> The main purpose behind the development of this module was to create an
> in-kernel system of signed modules.
I suggest you read this thread:
http://lkml.org/lkml/2007/2/14/164
--
James Morris
<[EMAIL PROTECTED]>
-
To unsubscribe from this list: se
On Tue, Mar 20, 2007 at 08:32:24AM -0600, Bjorn Helgaas wrote:
> Index: work-mm2/include/linux/serial_8250.h
> ===
> --- work-mm2.orig/include/linux/serial_8250.h 2006-08-22 12:26:25.0
> -0600
> +++ work-mm2/include/linux/seri
On Tue, 2007-03-20 at 09:52 -0400, Theodore Tso wrote:
> It would also help people understand why there are so many "units" in
> UBI, since hopefully the high-level documentation would explain why
> they fit together, and perhaps why some of the units weren't folded
> together. What value do they
On 3/20/07, Mark Lord <[EMAIL PROTECTED]> wrote:
I've droppped it from my machine -- interactive response is much
more important for my primary machine right now.
Help out with a data point? Are you running KDE as well? If you are,
then it looks like the common denominator that RSDL is handling
Ray Lee wrote:
On 3/20/07, Mark Lord <[EMAIL PROTECTED]> wrote:
I've droppped it from my machine -- interactive response is much
more important for my primary machine right now.
Help out with a data point? Are you running KDE as well?
Yes, KDE.
-
To unsubscribe from this list: send the line
On Tuesday 20 March 2007 08:06, Pavel Machek wrote:
> Hi!
>
> > Run this script. The s2ram at the end of it will wakeup immediately
> > after going to sleep, bad. I tried reproducing it with smaller
> > version, but was not too successful.
>
> Actually
>
> > sleep 2
> > echo -n "testing swsusp (
On Tue, Mar 20, 2007 at 04:44:01PM +0200, Tasos Parisinos wrote:
> >>+/* Pre-allocate some auxilliary mpis */
> >>+rsa_echo("Preallocating %lu bytes for auxilliary operands\n",
> >>+ RSA_AUX_SIZE * RSA_AUX_COUNT * sizeof(_u32));
> >
> >And printk.
>
> i made such a printk wrapper n
On Tue, 20 Mar 2007, Willy Tarreau wrote:
>
> Linus, you're unfair with Con. He initially was on this position, and lately
> worked with Mike by proposing changes to try to improve his X responsiveness.
I was not actually so much speaking about Con, as about a lot of the
tone in general here.
Peter Zijlstra a écrit :
+static void *get_futex_address(union futex_key *key)
+{
+ void *uaddr;
+
+ if (key->both.offset & 1) {
+ /* shared mapping */
+ uaddr = (void*)((key->shared.pgoff << PAGE_SHIFT)
+ + key->shared.offset
Hi!
I was testing suspend in 2.6.21-rc4 a lot, and now... machine feels
like someone added 50..100msec delay somewhere in keyboard
handling. Mouse does not seem affected. /proc/interrupts seem to
increase as they should, for both keyboard and mouse. Can someone
reproduce it? Any ideas how to debug
1 - 100 of 421 matches
Mail list logo
