On Sat, 26 May 2007 20:03:17 +0200 Michael Buesch <[EMAIL PROTECTED]> wrote:
> Ok, please take git and get my development tree and try with that:
>
> git clone http://bu3sch.de/git/wireless-dev.git
>
> It's based on 2.6.22-rc1 and it works fine for me.
Uwe has a slow connection, and getting
You wrote:
> Also sprach Rolf Eike Beer <[EMAIL PROTECTED]> (Sat, 26 May 2007
08:48:55 +0200):
> > After bootup (runlevel 5) I found this in dmesg:
> >
> > WARNING: at mm/slab.c:777 __find_general_cachep()
> > [] __kmalloc+0x40/0xc3
> > [] drm_rmdraw+0x126/0x24e [drm]
> > []
On May 26, 2007, at 10:44:46, Tetsuo Handa wrote:
Andreas Gruenbacher wrote:
Tetsuo Handa wrote:
Therefore, TOMOYO Linux checks the combination of filename and
argv[0] passed to execve().
So you are indeed trying to control the value of argv[0]? Well,
good luck with that, but it's totally
Robert P. J. Day wrote:
>
> It does not make sense for a noreturn function to have a return type
> other than void.
> ^
> ===
>
> so I'm just going to stick with the pattern that's been used so far.
> i realize it
On Saturday 26 May 2007 19:24:33 Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 19:18 schrieben Sie:
> > On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> > > Yes, sure! But the help text is very unlucky and humble, and it is not
> > > clear enough in the sense of being distinctive enough, just
Another macbook touchpad patch. Tries to follow the first detected finger.
any comments appreciated.
could somebody rapidly give me a link to create correct patches, so I could
send correct patches to the maintainer (I can't find any 'signoff' option
in 'git show' and I'm not able to select
Am Mittwoch 25 April 2007 schrieb Pavel Machek:
> Hi!
>
> > This is why there's a lot to be said for
> >
> > echo mem > /sys/power/state
> >
> > and being able to follow the path through _one_ object (the kernel)
> > over trying to figure out the interaction between many different
> > parts
It felt slightly lag while switching the firefox's tab compared to the 2.6.20.
-
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.kernel.org/majordomo-info.html
Please read the FAQ at
Am Samstag, 26. Mai 2007 19:18 schrieben Sie:
> On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> > Yes, sure! But the help text is very unlucky and humble, and it is not
> > clear enough in the sense of being distinctive enough, just clear and
> > comprehensive.
>
> Why don't you simply submit
On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> Yes, sure! But the help text is very unlucky and humble, and it is not clear
> enough in the sense of being distinctive enough, just clear and
> comprehensive.
Why don't you simply submit a patch to change the helptext then?
I'm not sure why
This represents the accumulated SCSI bug fixes so far. There's one
driver update: stex, but that's also mainly a bug fix.
The patch is available from:
master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
The short changelog is:
Alan Stern (1):
sd: fix refcounting
> > > > > > Seems to be hrtimers related - CC'ed Thomas.
> > > > > I doubt that. The tick interrupt just finds out, that the machine is
> > > > > stuck in rmmod.
> > > > > > > Also the rmmod hangs and would not exit even with kill -9. It also
> > > > > > > sucks up 100% cpu.
> > > > > Can you
Am Samstag, 26. Mai 2007 18:40 schrieben Sie:
> On Saturday 26 May 2007 18:26:06 Uwe Bugla wrote:
> > > I think we don't have IRQ assignment problems. Uwe simply disabled
> > > b44-PCI support in his first bugreport (I guess).
> >
> > Yes!
> >
> > > So there was
> > > no b44-PCI driver loaded.
> >
On Sat, 2007-05-26 at 18:49 +0200, Folkert van Heusden wrote:
> > > > > Seems to be hrtimers related - CC'ed Thomas.
> > > > I doubt that. The tick interrupt just finds out, that the machine is
> > > > stuck in rmmod.
> > > > > > Also the rmmod hangs and would not exit even with kill -9. It also
>
On Mon, 21 May 2007 22:06:36 -0700
Junio C Hamano <[EMAIL PROTECTED]> wrote:
> This introduces a shared header file that defines the entries
> for two dma blacklists in ide-dma.c and libata-core.c to make it
> easier to keep them in sync.
>
> Signed-off-by: Junio C Hamano <[EMAIL PROTECTED]>
On Saturday 26 May 2007 16:44, Tetsuo Handa wrote:
> Hello.
>
> Andreas Gruenbacher wrote:
> > > Therefore, TOMOYO Linux checks the combination of filename and argv[0]
> > > passed to execve().
> >
> > So you are indeed trying to control the value of argv[0]? Well, good luck
> > with that, but
> > > > Seems to be hrtimers related - CC'ed Thomas.
> > > I doubt that. The tick interrupt just finds out, that the machine is
> > > stuck in rmmod.
> > > > > Also the rmmod hangs and would not exit even with kill -9. It also
> > > > > sucks up 100% cpu.
> > > Can you please enable
On Sat, May 26, 2007 at 06:38:07PM +0200, Bodo Eggert wrote:
> Not exactly, if(foo) is the same as if( (int) foo), which is not
> guaranteed to result in non-null values for non-null pointers.
RTFStandard.
> ISO 9899/1999 says: "Any pointer may be converted to an integer type. [...]
>
Uwe Bugla <[EMAIL PROTECTED]> :
> Am Samstag, 26. Mai 2007 18:13 schrieben Sie:
[...]
> > Uwe, http://userweb.kernel.org/~akpm/git-wireless.patch.gz is the current
> > wireless tree. That's a patch against 2.6.22-rc3. Could you please test
> > that? If that works then we know that the bug
Also sprach Rolf Eike Beer <[EMAIL PROTECTED]> (Sat, 26 May 2007 08:48:55
+0200):
> After bootup (runlevel 5) I found this in dmesg:
>
> WARNING: at mm/slab.c:777 __find_general_cachep()
> [] __kmalloc+0x40/0xc3
> [] drm_rmdraw+0x126/0x24e [drm]
> [] skb_dequeue+0x39/0x3f
> []
On Saturday 26 May 2007 18:26:06 Uwe Bugla wrote:
> > I think we don't have IRQ assignment problems. Uwe simply disabled
> > b44-PCI support in his first bugreport (I guess).
>
> Yes!
>
> > So there was
> > no b44-PCI driver loaded.
>
> Well, not exactly: b44 plus ssb were in fact produced,
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> On May 25 2007 14:14, David Miller wrote:
>>"!!" is used in contexts where pointers might be being
>>tested as well as plain integers, the "!!" turns a pointer
>>into the equivalent integer boolean for testing.
>>
>>NULL pointers become 0
>>non-NULL
Junio C Hamano wrote:
This introduces a shared header file that defines the entries
for two dma blacklists in ide-dma.c and libata-core.c to make it
easier to keep them in sync.
Why wasn't this done this way in the first place? Out of tree
development for libata or something?
--
Bill
On Sat, 2007-05-26 at 18:17 +0200, Folkert van Heusden wrote:
> > > Seems to be hrtimers related - CC'ed Thomas.
> > I doubt that. The tick interrupt just finds out, that the machine is
> > stuck in rmmod.
> > > > Also the rmmod hangs and would not exit even with kill -9. It also
> > > > sucks up
Am Samstag, 26. Mai 2007 18:21 schrieben Sie:
> On Saturday 26 May 2007 18:13:09 Andrew Morton wrote:
> > > I already tried your -mm kernel, but it crashes on my machine
> > > for other reasons. (Yeah, I should look into them, too :P )
> >
> > err, please do. Just the oops trace would be a start.
Am Samstag, 26. Mai 2007 18:13 schrieben Sie:
> On Sat, 26 May 2007 17:50:48 +0200 Michael Buesch <[EMAIL PROTECTED]> wrote:
> > Andrew,
> >
> > I am going to ignore Uwe from now on. It's simply impossible
> > to debug the problem the way he is responding.
> > Well, I'm not the first person in the
Dear list members,
I am posting to this list just to get additional help for the bug I
reported here:
http://bugzilla.kernel.org/show_bug.cgi?id=8259
So the problem is the following:
I have a Asus P5W-DH Delux Mainboard with an onboard JMicron 20360/20363 AHCI
Controller.
As soon as I
Jonathan Woithe wrote:
A collegue of mine has an Intel mainboard with the i865 chipset onboard
(DQ965). All kernels up to and including 2.6.22-rc2 do not detect the IDE
CDROM/DVDROM when booting. The SATA hard drive is found without any
problems.
Let me belatedly ask if the device shows up in
Jonathan Woithe wrote:
On 21 May 2007 I wrote:
Attempting to compile a 2.6.21.1 kernel for use on a Fedora Core 6 box
results in a panic at boot because the root filesystem can't be found.
I have just compiled 2.6.22-rc2 with the configuration file given in my
previous post and the resulting
On Saturday 26 May 2007 18:13:09 Andrew Morton wrote:
> > I already tried your -mm kernel, but it crashes on my machine
> > for other reasons. (Yeah, I should look into them, too :P )
>
> err, please do. Just the oops trace would be a start.
Yes, I will look into it. I think it was related to
Hi,
> > Seems to be hrtimers related - CC'ed Thomas.
>
> I doubt that. The tick interrupt just finds out, that the machine is
> stuck in rmmod.
Can you please make netconsole unloadable via rmmod? My system seems to
hang every time I do rmmod on netconsole (rmmod using 100% cpu and not
Am Samstag, 26. Mai 2007 17:50 schrieben Sie:
> Andrew,
>
> I am going to ignore Uwe from now on. It's simply impossible
> to debug the problem the way he is responding.
> Well, I'm not the first person in the Linux community adding
> him to the killfile, ... .
> I ask to try wireless-dev, as the
> > Seems to be hrtimers related - CC'ed Thomas.
> I doubt that. The tick interrupt just finds out, that the machine is
> stuck in rmmod.
> > > Also the rmmod hangs and would not exit even with kill -9. It also
> > > sucks up 100% cpu.
> Can you please enable CONFIG_PROVE_LOCKING ?
Luckily I
On Sat, 26 May 2007 17:50:48 +0200 Michael Buesch <[EMAIL PROTECTED]> wrote:
> Andrew,
>
> I am going to ignore Uwe from now on. It's simply impossible
> to debug the problem the way he is responding.
> Well, I'm not the first person in the Linux community adding
> him to the killfile, ... .
On Sat, 2007-05-26 at 11:53 -0400, Parag Warudkar wrote:
> Seems to be hrtimers related - CC'ed Thomas.
I doubt that. The tick interrupt just finds out, that the machine is
stuck in rmmod.
> > Also the rmmod hangs and would not exit even with kill -9. It also
> > sucks up 100% cpu.
Can you
Greg KH wrote:
On Wed, May 23, 2007 at 09:27:12AM -0400, Mark Lord wrote:
Greg KH wrote:
And yes, it only starts to look for things when it recieves an event, it
does not "scan" sysfs at all.
Does it "look for" only that one event, or does it "scan" at that point?
udev will act on that
On Fri, 2007-05-25 at 21:58 +0100, Rui Nuno Capela wrote:
> Is there anything I can do better to help myself figuring out this
> issue? As this is a modern laptop such things like a serial console are
> unavailable, but it would be nice to track things up over netconsole
> perhaps?
>
> I just
On 5/26/07, Tommy Vercetti <[EMAIL PROTECTED]> wrote:
in terms of driver, what do you mean ?
The software driver that handles the specific chipset for that drive.
The thing that shows up when you do an lsmod, assuming you have the
driver compiled as a module.
/dev/hda:
Timing cached reads:
On Saturday 26 May 2007 14:07:24 Indan Zupancic wrote:
>
> Did the patches reach 2.6.22-rc3 yet?
No.
>
> If they did, then the following warnings might need fixing:
There is already one patch queued for it. But actually in my experience I cannot
remember a single real bug showed by these
On Sat, 26 May 2007 17:59:15 +0200 Tilman Schmidt <[EMAIL PROTECTED]> wrote:
> Am 23.05.2007 09:42 schrieb Andrew Morton:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc2/2.6.22-rc2-mm1/
>
> This breaks network initialization on my SuSE 10.0 box once
> again although
Am Samstag, 26. Mai 2007 17:36 schrieben Sie:
> On Saturday 26 May 2007 12:40:54 Uwe Bugla wrote:
> > Yes! This sort of mistakes is completely impossible, as I use to work
> > with aliases rather than IP adresses. The machine I tried to ping (i. e.
> > my router) is called Jerry (as a reminiscence
On Sat, 26 May 2007 16:07:49 +0200
Tommy Vercetti <[EMAIL PROTECTED]> wrote:
> > Anyway 97% is quite high... what CPU / Hard Disk do you have?
> Intel(R) Pentium(R) M processor 1400MHz
> TOSHIBA MK8025GAS
>
> > What kernel version?
> 2.6.21.1
> > I/O scheduler? (cat
Am 23.05.2007 09:42 schrieb Andrew Morton:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc2/2.6.22-rc2-mm1/
This breaks network initialization on my SuSE 10.0 box once
again although I compiled with CONFIG_SYSFS_DEPRECATED=y.
Acquisition of the IP address via DHCP times
Seems to be hrtimers related - CC'ed Thomas.
Parag
Folkert van Heusden wrote:
Hi,
When trying to remove the netconsole module, I got the following kernel
output after a while (couple of minutes iirc):
[525720.117293] BUG: soft lockup detected on CPU#1!
[525720.117353] []
Andrew,
I am going to ignore Uwe from now on. It's simply impossible
to debug the problem the way he is responding.
Well, I'm not the first person in the Linux community adding
him to the killfile, ... .
I ask to try wireless-dev, as the driver works perfectly fine
for me there, but he refuses to
in terms of driver, what do you mean ?
this is my lspci:
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller
(rev 21)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev
21)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM
Srivatsa Vaddagiri wrote:
>> Ingo/Peter, any thoughts here? CFS and smpnice probably is "broken"
>> with respect to such example as above albeit for nice-based tasks.
On Sat, May 26, 2007 at 10:17:42AM +1000, Peter Williams wrote:
> See above. I think that faced with cpu affinity use by the
Hi,
When trying to remove the netconsole module, I got the following kernel
output after a while (couple of minutes iirc):
[525720.117293] BUG: soft lockup detected on CPU#1!
[525720.117353] [] show_trace_log_lvl+0x1a/0x30
[525720.117439] [] show_trace+0x12/0x14
[525720.117526] []
On Saturday 26 May 2007 12:40:54 Uwe Bugla wrote:
> Yes! This sort of mistakes is completely impossible, as I use to work with
> aliases rather than IP adresses. The machine I tried to ping (i. e. my
> router) is called Jerry (as a reminiscence to Mr. "Captan Trips" from
> Grateful Dead), and
Hi,
wait time is 90+% , which means that machine is waiting, rather than doing
something meanwhile. (I guess).
Yes, the machine spends its time waiting for the disk to do its things
as it does not have anything else to do. Nothing to worry about. If
you want, launch some CPU bound process at
On 5/26/07, Tommy Vercetti <[EMAIL PROTECTED]> wrote:
I was trying to get answer to my question around, but no one knows.
I do have DMA turned on, etc, yet - on extensive harddrive operations wait
You may have DMA turned on, but it may be ineffectual if you don't
have the right IDE driver
26 May 2007 Cts tarihinde, S.Çağlar Onur şunları yazmıştı:
> 23 May 2007 Çar tarihinde, Ingo Molnar şunları yazmıştı:
> > As usual, any sort of feedback, bugreport, fix and suggestion is more
> > than welcome!
>
> I have another kaffeine [0.8.4]/xine-lib [1.1.6] problem with CFS for you
> :)
>
>
Roland Dreier wrote:
> > I am now wondering whether the usage of MSI would help in this case and
> > that i should be using enable_msi before request_irq ?
>
> MSI interrupts are never shared. So if pci_enable_msi() succeeds, you
> can be sure that the interrupts you get with that IRQ number
Ingo Oeser wrote:
> On Saturday 26 May 2007, Patrick McHardy wrote:
>
>>net/8021q ignores the VLAN header overhead, so we should probably do the
>>same here for consistency. Using IS_VLAN_IP (and IS_PPPOE_IP for current
>>-rc) looks fine, additionally we should probably also check for
>>skb->nfct
Hi Ingo;
23 May 2007 Çar tarihinde, Ingo Molnar şunları yazmıştı:
> As usual, any sort of feedback, bugreport, fix and suggestion is more
> than welcome!
I have another kaffeine [0.8.4]/xine-lib [1.1.6] problem with CFS for you :)
Under load (compiling any Qt app. or kernel with -j1 or -j2)
After bootup (runlevel 5) I found this in dmesg:
WARNING: at mm/slab.c:777 __find_general_cachep()
[] __kmalloc+0x40/0xc3
[] drm_rmdraw+0x126/0x24e [drm]
[] skb_dequeue+0x39/0x3f
[] drm_rmdraw+0x0/0x24e [drm]
[] drm_ioctl+0x14c/0x192 [drm]
[] do_ioctl+0x4c/0x62
[] vfs_ioctl+0x237/0x249
[]
Hello.
Andreas Gruenbacher wrote:
> > Therefore, TOMOYO Linux checks the combination of filename and argv[0]
> > passed to execve().
> So you are indeed trying to control the value of argv[0]? Well, good luck
> with
> that, but it's totally insane. You are guaranteed to break some applications.
On 26/05/2007, at 15:05, Tommy Vercetti wrote:
Hi folks,
I was trying to get answer to my question around, but no one knows.
I do have DMA turned on, etc, yet - on extensive harddrive
operations wait
time is 90+% , which means that machine is waiting, rather than doing
something meanwhile.
Em Sáb, 2007-05-26 às 12:51 +0200, Jan Engelhardt escreveu:
> On May 25 2007 23:33, Takashi Iwai wrote:
> >
> >Yeah, I'll check it again if reposted. Jan, could you split ALSA
> >portins at the next time?
>
> How much split? This time, I made four out of it.
>
> >This will make testing and
On Saturday 26 May 2007, Patrick McHardy wrote:
> Adam Osuchowski wrote:
> > if (((skb->protocol == htons(ETH_P_IP) && skb->len > skb->dev->mtu) ||
> > (IS_VLAN_IP(skb) && skb->len > skb->dev->mtu - VLAN_HLEN)) &&
> > !skb_is_gso(skb))
> > return ip_fragment ...
>
>
>
On Saturday 26 May 2007 15:52, Paolo Ornati wrote:
> On Sat, 26 May 2007 15:05:38 +0200
> It means that the disk is slow and the CPU is fast... so while the disk
> is busy seeking and reading data the CPU has nothing to do but wait for
> it.
>
> Idle == CPU has nothing to do
> Waiting == CPU has
On Saturday 26 May 2007 15:34, Alan Cox wrote:
> > As such, AA can detect whether you did exec("gzip") or exec("gunzip")
> > and apply the policy relevant to the program. It could apply different
>
> That's not actually useful for programs which link the same binary to
> multiple names because if
* Andi Kleen ([EMAIL PROTECTED]) wrote:
>
> > And, in this case we're in luck. It's not released in any -stable tree
> > yet (it's queued for the next release). So there's plenty of time to
> > fix it up before next -stable release.
> >
> > Something like below should fix it.
>
> I already
On Sat, 26 May 2007 15:05:38 +0200
Tommy Vercetti <[EMAIL PROTECTED]> wrote:
> I was trying to get answer to my question around, but no one knows.
> I do have DMA turned on, etc, yet - on extensive harddrive operations wait
> time is 90+% , which means that machine is waiting, rather than doing
On May 25 2007 14:14, David Miller wrote:
>
>WHat is with multiple people asking about "!!" all of a
>sudden today?
>
>> Are all these occurrences merely the debris of
>> s/something/!notsomething/g kind of patches or is there some
>> dark, unknown C / gcc wizardry I have absolutely no clue of?
>
On Saturday 26 May 2007 14:09, Tetsuo Handa wrote:
> Hello.
>
> Andreas Gruenbacher wrote:
> > > exec { "/usr/bin/gunzip" } "gzip", "-9", "some/file/to.gz";
> >
> > The above Perl code executes /usr/bin/gunzip and sets argv[0] to "gzip",
> > so this confirms that the value of argv[0] is arbitrary.
> As such, AA can detect whether you did exec("gzip") or exec("gunzip")
> and apply the policy relevant to the program. It could apply different
That's not actually useful for programs which link the same binary to
multiple names because if you don't consider argv[0] as well I can run
On Fri, 25 May 2007, H. Peter Anvin wrote:
> Robert P. J. Day wrote:
> >
> >
> > f() __attribute__((noreturn)) ;
> >
> > you get:
> >
> > warning: data definition has no type or storage class
> >
> > but gcc doesn't complain if you declare it thusly:
> >
> > __attribute__((noreturn)) f() ;
Hi folks,
I was trying to get answer to my question around, but no one knows.
I do have DMA turned on, etc, yet - on extensive harddrive operations wait
time is 90+% , which means that machine is waiting, rather than doing
something meanwhile. (I guess).
Can someone describe to me , in more
Chris Newport wrote:
>
> Sorry, I did not make myself clear.
>
> Linus Torvalds wrote:
>
>> On Fri, 25 May 2007, Chris Newport wrote:
>>
>>
>>> Maybe we should take a hint from Solaris.
>>>
>>
>> No. Solaris is shit. They make their decisions based on "we control
>> the hardware" kind of
Hi Arunachalam,
On Saturday 26 May 2007, Arunachalam wrote:
> I want to know in detail about , what the events (epoll or /dev/poll or
> select ) achieve in contrast to thread per client.
>
> i can have a thread per client and use send and recv system call directly
> right? Why do i go for these
Hello all,
I want to know in detail about , what the events (epoll or /dev/poll or
select ) achieve in contrast to thread per client.
i can have a thread per client and use send and recv system call directly
right? Why do i go for these event mechanisms?
Please help me to understand this.
On Saturday 26 May 2007, Nigel Cunningham wrote:
> Hi.
>
> On Sat, 2007-05-26 at 11:28 +0200, Maximilian Engelhardt wrote:
> > Hello,
> >
> > When I try software suspend on my laptop it always returns to my running
> > system after some time.
> > This is what's logged by the kernel:
> >
> >
Hello,
when using the prism54 driver including in the 2.6.22-rc3 kernel I get this
Oops when putting the card into monitor mode:
BUG: unable to handle kernel NULL pointer dereference at virtual address
01d8
printing eip:
c0500608
*pde =
Oops: 0002 [#1]
PREEMPT
Modules linked in:
On Friday 25 May 2007 21:06, Casey Schaufler wrote:
> --- Jeremy Maitin-Shepard <[EMAIL PROTECTED]> wrote:
> > ...
> > Well, my point was exactly that App Armor doesn't (as far as I know) do
> > anything to enforce the argv[0] convention,
>
> Sounds like an opportunity for improvement then.
Jeez,
Hello.
Andreas Gruenbacher wrote:
> > exec { "/usr/bin/gunzip" } "gzip", "-9", "some/file/to.gz";
> The above Perl code executes /usr/bin/gunzip and sets argv[0] to "gzip", so
> this confirms that the value of argv[0] is arbitrary. Well great, we already
> knew.
> AppArmor does not look at
On Mon, May 21, 2007 17:11, Sam Ravnborg wrote:
> On Mon, May 21, 2007 at 02:52:39PM +0100, Jeremy Fitzhardinge wrote:
>> Sam Ravnborg wrote:
>> > There was another patch that removed the __init marker to _fix_ section
>> > mismatch errors.
>> > I have lost the actual mail but I asked the
On Sat, May 26, 2007 at 09:14:00PM +1000, Nigel Cunningham wrote:
>
> You have the cryptd Kconfig option in (at least in rc3) - presumably
> Maximillian has been too keen and turned it on before you were ready :)
> It does make sense for it to be the problem. Without PF_NOFREEZE set,
> the
On Saturday 26 May 2007 07:20, Kyle Moffett wrote:
> On May 24, 2007, at 14:58:41, Casey Schaufler wrote:
> > On Fedora zcat, gzip and gunzip are all links to the same file. I
> > can imagine (although it is a bit of a stretch) allowing a set of
> > users access to gunzip but not gzip (or the
Hi Bret,
On 5/25/07, Bret Towe <[EMAIL PROTECTED]> wrote:
[ 237.556167] LZO compress successful: orig_size=17448, comp_size=8183
[ 253.320760] LZO decompress successful: decomp_size=17448
2221c586e3eb869af7f4333d4f56b441b9aa8414 test-input
2e6c96b687274b629308b29835cebd3af989e0c7 output
Hi Richard,
On 5/26/07, Richard Purdie <[EMAIL PROTECTED]> wrote:
I've been looking at my benchmark figures and I think I've found why the
figures for my version were different to yours. Its not your code which
is at fault, its the way it was hooked into the benchmarking program.
The compiler
Hi Pavel,
Just did some benchmarking; results below.
On 5/25/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
What is the performance difference between safe and unsafe version?
File size: 256K
- Following as tests for original test code - not any kernel port of this.
- Test with each block
Hi.
On Sat, 2007-05-26 at 21:08 +1000, Herbert Xu wrote:
> On Sat, May 26, 2007 at 07:53:53PM +1000, Nigel Cunningham wrote:
> >
> > Herbert, is this right? If cryptd is going to be used for block devs,
> > the task should probably be PF_NOFREEZE (or whatever it is today)
> > instead.
>
>
On Sat, May 26, 2007 at 07:53:53PM +1000, Nigel Cunningham wrote:
>
> Herbert, is this right? If cryptd is going to be used for block devs,
> the task should probably be PF_NOFREEZE (or whatever it is today)
> instead.
Probably. However, I don't think this is responsible for the reported
On May 25 2007 23:33, Takashi Iwai wrote:
>
>Yeah, I'll check it again if reposted. Jan, could you split ALSA
>portins at the next time?
How much split? This time, I made four out of it.
>This will make testing and merging much
>easier for me...
>
>But, above all, I'm not convinced much by
CONFIG_SOUND, CONFIG_SND, CONFIG_SOUND_PRIME, ...:
Change Kconfig objects from "menu, config" into "menuconfig" so
that the user can disable the whole feature without having to
enter the menu first.
CONFIG_SND_*_DRIVERS:
Make a "menuconfig" out of the Kconfig objects "menu, ..., endmenu",
so
Am Samstag, 26. Mai 2007 07:00 schrieben Sie:
> On Friday 25 May 2007 21:40, Uwe Bugla wrote:
> > Am Freitag, 25. Mai 2007 20:48 schrieben Sie:
> > > On Fri, 25 May 2007 17:59:29 +0200, Uwe Bugla wrote:
> > > > Perhaps someone reading this could try to reproduce that problem on
> > > > his
CONFIG_SOUND, CONFIG_SND, CONFIG_SOUND_PRIME, ...:
Change Kconfig objects from "menu, config" into "menuconfig" so
that the user can disable the whole feature without having to
enter the menu first.
CONFIG_SND_*_DRIVERS:
Make a "menuconfig" out of the Kconfig objects "menu, ..., endmenu",
so
CONFIG_SOUND, CONFIG_SND, CONFIG_SOUND_PRIME, ...:
Change Kconfig objects from "menu, config" into "menuconfig" so
that the user can disable the whole feature without having to
enter the menu first.
CONFIG_SND_*_DRIVERS:
Make a "menuconfig" out of the Kconfig objects "menu, ..., endmenu",
so
CONFIG_SOUND, CONFIG_SND, CONFIG_SOUND_PRIME, ...:
Change Kconfig objects from "menu, config" into "menuconfig" so
that the user can disable the whole feature without having to
enter the menu first.
CONFIG_SND_*_DRIVERS:
Make a "menuconfig" out of the Kconfig objects "menu, ..., endmenu",
so
On May 25 2007 10:28, Andrew Morton wrote:
>>
>> > snd: Unknown symbol unregister_sound_special
>> > snd: Unknown symbol register_sound_special_device
>> > snd: Unknown symbol sound_class
>>
>> Uwe, could you try to revert this patch?
>> use-menuconfig-objects-ii-sound.patch
>
>I think that
Hi Nitin,
On Fri, 2007-05-25 at 18:27 +0530, Nitin Gupta wrote:
> On 5/25/07, Richard Purdie <[EMAIL PROTECTED]> wrote:
> > On Fri, 2007-05-25 at 17:15 +0530, Nitin Gupta wrote:
> > > Richard, can you please provide perf. results for this patch also?
> > > Also, can you please mail back latest
Hello, Neil Brown.
Please cc me on blkdev barriers and, if you haven't yet, reading
Documentation/block/barrier.txt can be helpful too.
Neil Brown wrote:
[--snip--]
> 1/ SAFE. With a SAFE device, there is no write-behind cache, or if
> there is it is non-volatile. Once a write
On 25 May 2007, at 11:42, Pavel Machek wrote:
What is the performance difference between safe and unsafe version?
On 24 May 2007, at 23:26, Richard Purdie wrote:
For my minilzo kernel patch, the safe version showed a 7.2%
performance
hit.
The conclusion seemed to be that we should drop
On Fri, 2007-05-25 at 10:46 -0600, Eric W. Biederman wrote:
> Most of that though is just packaging. The meat of the issue
> is how do we upgrade the bootloader data. Do the changes
> below sound like everything we need?
>
> Field name: loadflags
> Type:modify (obligatory)
>
Swap prefetch is currently too lax in prefetching with extended idle periods
unused. Increase its aggressiveness and tunability.
Make it possible for swap_prefetch to be set to a high value ignoring load
and prefetching regardless.
Add tunables to modify the swap prefetch delay and sleep period
I will submit this for 2.6.22-rc and 2.6.21.y if nobody objects.
Date: Mon, 21 May 2007 01:05:41 +0200
From: Stefan Richter <[EMAIL PROTECTED]>
Subject: ieee1394: eth1394: bring back a parent device
This adds a real parent device to eth1394's ethX device like in Linux
2.6.20 and older. However,
Hi.
On Sat, 2007-05-26 at 11:28 +0200, Maximilian Engelhardt wrote:
> Hello,
>
> When I try software suspend on my laptop it always returns to my running
> system after some time.
> This is what's logged by the kernel:
>
> swsusp: Basic memory bitmaps created
> Stopping tasks ...
> Stopping
On Saturday 26 May 2007, Michael Buesch wrote:
> On Friday 25 May 2007 21:40, Uwe Bugla wrote:
> > Am Freitag, 25. Mai 2007 20:48 schrieben Sie:
> > > On Fri, 25 May 2007 17:59:29 +0200, Uwe Bugla wrote:
> > > > Perhaps someone reading this could try to reproduce that problem on
> > > > his
Hi!
> > > #1, This is why periodic checks are a good thing; it catches problems
> > > that could stay hidden and result in data loss sooner rather later.
> >
> > Actually, I see something funny with periodic checks here. It claims
> > 'filesystem check on next boot' for >10 boots now.
> >
> >
101 - 200 of 436 matches
Mail list logo
