Dell Latitude D820, T7200 processor, x86_64 kernel. The MSI IRQs for
HDA-Intel evaporate fairly consistently some time after boot. On a few
occasions, the MSI IRQ for the ethernet interface also has dropped.
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
Audio
On 10/6/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
>
> commit a606d2a111cdf948da5d69eb1de5526c5c2dafef
> Author: Jeff Garzik <[EMAIL PROTECTED]>
> Date: Fri Oct 5 22:56:05 2007 -0400
>
> [netdrvr] forcedeth: interrupt handling cleanup
>
> * nv_nic_irq_optimized() and nv_nic_irq_other()
On Sat, 06 Oct 2007 15:53:37 +0200, Helge Deller said:
> diff --git a/drivers/char/random.c b/drivers/char/random.c
> index af274e5..c84a385 100644
> --- a/drivers/char/random.c
> +++ b/drivers/char/random.c
> @@ -239,6 +239,7 @@
> #include
> #include
> #include
> +#include
>
> #include
>
> ULPs:
>
> - Pradeep's IPoIB CM support for devices that don't have SRQs. Sean
>started reviewing but I didn't see any updated patches.
>
Roland, I submitted an updated patch incorporating some of Sean's comments
within
a day or two. Rest of comments pertained to restructuring the
If you can set up a serial console, it would be better. If not, can you
please take a photo of the crash and post it?
I am running short of elements, no digital camera o movil phone for the
case or serial link.
However, what it is on the screen when it crashes follows:
KERNEL 2.6.23-rc8
Hi,
I have just had an XFS error occur while deleting some directory
hierarchy. I hope this is the correct place to report it.
It essentially shutdown the file system, and a reboot seemed to return
everything to normal.
This is in syslog :
> Oct 6 23:40:33 jeeves kernel: xfs_da_do_buf: bno
Jan Engelhardt wrote:
On Oct 6 2007 15:53, Bill Davidsen wrote:
Jan Engelhardt wrote:
Colored kernel message output
Let's work more on Linux's cuteness! [http://lkml.org/lkml/2007/10/4/431]
The following patch makes it possible to give kernel messages a
selectable color which helps to
On Saturday 06 October 2007, Jeff Garzik wrote:
>
> This always bugged me: dev_ioctl() called dev_ifsioc() either inside
> read_lock(dev_base_lock) or rtnl_lock(), depending on the ioctl being
> executed.
>
> This change moves the ioctls executed inside dev_base_lock to a new
> function,
On Saturday 06 October 2007, Christoph Hellwig wrote:
> > +static int compat_put_u64(unsigned long arg, u64 val)
> > +{
> > + return put_user(val, (compat_u64 __user *)compat_ptr(arg));
> > +}
>
> These should probably be in compat.h
Hmm, I'm not sure. They are modeled after the
On Sat, 6 Oct 2007 22:09:52 +0200 (CEST)
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
> Colored kernel message output (1/2)
>
> This patch makes it possible to give kernel messages a selectable
> color. It can be chosen at compile time, overridden at boot time,
> and changed at run time.
As the
On Oct 7 2007 00:28, Oleg Verych wrote:
>
>I thought, i was talking about *write() functions, that got one
>additional unrelated, non config removable API change in face of
>`unsigned int loglevel'.
Documentation/stable_api_nonsense.txt ;-)
>Idea. Extend those macro defines before format string
On Sat, Oct 06, 2007 at 11:27:54PM +0200, Jan Engelhardt wrote:
[]
> _call_console_drivers() skips the substring and passes on the rest of the
> message:
>
> if (msg_level < 0 && ((end - cur_index) > 2) &&
> LOG_BUF(cur_index + 0) == '<' &&
>
On Sat, Oct 06, 2007 at 11:10:48PM +0200, Sam Ravnborg wrote:
> On Sat, Oct 06, 2007 at 10:47:21PM +0200, Oleg Verych wrote:
> > On Sat, Oct 06, 2007 at 08:59:20PM +0200, Sam Ravnborg wrote:
> > > > Maintenance and acceptance of the m4/make/perl/C/ncurses community of my
> > > > mainly `TERM=linux
Paul M wrote:
>
> What's wrong with:
>
> allocate a page of task_struct pointers
> again:
> need_repeat = false;
> cgroup_iter_start();
> while (cgroup_iter_next()) {
> if (p->cpus_allowed != new_cpumask) {
> store p;
> if (page is full) {
> need_repeat = true;
>
On Sat, Oct 06, 2007 at 11:03:38PM +0200, Jan Engelhardt wrote:
>
> On Oct 6 2007 23:03, Oleg Verych wrote:
> >>
> >> (btw., i corrected the subject line to remove the 'NAK'. Why do you
> >> think you can 'NAK' a patch in this field?)
> >
> >I added comment (like this), so anyone can skip
On 10/6/07, Paul Jackson <[EMAIL PROTECTED]> wrote:
> From: Paul Jackson <[EMAIL PROTECTED]>
>
> Decrustify the kernel/cpuset.c 'cpus' and 'mems' updating code.
>
> Other than subtle improvements in the consistency of identifying
> white space at the beginning and end of passed in masks, this
>
On Oct 6 2007 23:25, Oleg Verych wrote:
>> ---
>> arch/x86_64/kernel/early_printk.c | 11 +++
>> drivers/char/Kconfig |4 +++-
>> drivers/char/vt.c | 32
>> drivers/net/netconsole.c |3 ++-
>>
On 10/5/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
> Colored kernel message output
>
> Let's work more on Linux's cuteness! [http://lkml.org/lkml/2007/10/4/431]
> The following patch makes it possible to give kernel messages a
> selectable color which helps to distinguish it from other noise,
On Sat, 2007-10-06 at 12:48 -0600, Robert Hancock wrote:
> > On Oct 4, 2007, at 11:52 AM, Scott wrote:
> >
> >> I'm having what I think is a PCI bus problem.
> >>
> >> I have a ASUS P5B Intel 965 motherboard and a DVICO Fusion HDTV5 RT
> >> adapter on the PCI bus. When this adapter is recording
On Sat, Oct 06, 2007 at 10:14:06PM +0200, Ahmed S. Darwish wrote:
> Pressing sysRq+T always produce an Oops for every running system task (94
> Oopses, that's a record ;)).
uh-oh. For every sleeping task, I think.
> The bug is 100% reproducable. Should I begin bisecting/investigating the
>
On 10/6/07, David Rientjes <[EMAIL PROTECTED]> wrote:
> The getting and putting of the tasks will prevent them from exiting or
> being deallocated prematurely. But this is also a critical section that
> will need to be protected by some mutex so it doesn't race with other
> set_cpus_allowed().
Thanks for dealing with my acidness in the first patch :)
But what about this one?
On Sat, Oct 06, 2007 at 10:10:01PM +0200, Jan Engelhardt wrote:
>
> Colored kernel message output (2/2)
>
> By popular request, this patch adds per-loglevel coloring.
> The user may set values using
On 10/6/07, Paul Jackson <[EMAIL PROTECTED]> wrote:
> David wrote:
> > It would probably be better to just save references to the tasks.
> >
> > struct cgroup_iter it;
> > struct task_struct *p, **tasks;
> > int i = 0;
> >
> > cgroup_iter_start(cs->css.cgroup, );
> >
On Sat, Oct 06, 2007 at 10:47:21PM +0200, Oleg Verych wrote:
> On Sat, Oct 06, 2007 at 08:59:20PM +0200, Sam Ravnborg wrote:
> > > Maintenance and acceptance of the m4/make/perl/C/ncurses community of my
> > > mainly `TERM=linux ; sed && sh' approach is more important for me.
> >
> > There is
On Oct 6 2007 23:03, Oleg Verych wrote:
>>
>> (btw., i corrected the subject line to remove the 'NAK'. Why do you
>> think you can 'NAK' a patch in this field?)
>
>I added comment (like this), so anyone can skip reading body, if headers
>are "Oleg Verych && NAK". In case if `NAK' have a magic
On 10/6/07, Paul Jackson <[EMAIL PROTECTED]> wrote:
>
> This isn't working for me.
>
> The key kernel routine for updating a tasks cpus_allowed
> cannot be called while holding a spinlock.
>
> But the above loop holds a spinlock, css_set_lock, between
> the cgroup_iter_start and the
On Sat, Oct 06, 2007 at 10:14:05PM +0200, ahmed wrote:
> Hi all,
>
> Pressing sysRq+T always produce an Oops for every running system task (94
> Oopses, that's a record ;)).
> The bug is 100% reproducable. Should I begin bisecting/investigating the
> issue or it's a known problem ?
>
Shame,
On Sat, Oct 06, 2007 at 09:48:20PM +0200, Ingo Molnar wrote:
> >
> > This is a "kernel messages color-l10n".
> >
> > * text code size, that cannot be zero if config option is not set;
>
> not really an issue. Changing the inline function to non-inline will get
> rid of most of the text cost.
This always bugged me: dev_ioctl() called dev_ifsioc() either inside
read_lock(dev_base_lock) or rtnl_lock(), depending on the ioctl being
executed.
This change moves the ioctls executed inside dev_base_lock to a new
function, dev_ifsioc_locked(). Now the locking context is completely
clear to
On Sat, Oct 06, 2007 at 08:59:20PM +0200, Sam Ravnborg wrote:
> > Maintenance and acceptance of the m4/make/perl/C/ncurses community of my
> > mainly `TERM=linux ; sed && sh' approach is more important for me.
>
> There is noone having trouble with ncurses dependency today.
Who wants to meet a
On Oct 5 2007 21:49, Hugh Dickins wrote:
>> > > $ zcat /proc/config.gz | grep TMPFS
>> > > # CONFIG_TMPFS is not set
>> > > $ grep tmpfs /proc/filesystems
>> > > nodev tmpfs
>> >
>> > tmpfs (mm/shmem.c) is used by the kernel to support shared memory
>> > of various kinds even when CONFIG_TMPFS
Hi all,
Pressing sysRq+T always produce an Oops for every running system task (94
Oopses, that's a record ;)).
The bug is 100% reproducable. Should I begin bisecting/investigating the
issue or it's a known problem ?
$ ver_linux
Linux darwish-laptop 2.6.23-rc9 #23 Sat Oct 6 21:48:45 EET 2007
On Oct 3 2007 10:55, Bodo Eggert wrote:
>
>> [PATCH]: Fill the size of FIFOs
>>
>> Instead of reporting 0 in size when stating() a pipe
>
>FIFO
Yes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Colored kernel message output (2/2)
By popular request, this patch adds per-loglevel coloring.
The user may set values using vt.printk_color= or by modifying
the sysfs file in the running system.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/early_printk.c | 11
Colored kernel message output (1/2)
This patch makes it possible to give kernel messages a selectable
color. It can be chosen at compile time, overridden at boot time,
and changed at run time.
References: http://lkml.org/lkml/2007/4/1/162
http://lkml.org/lkml/2007/10/5/199
On Oct 6 2007 15:53, Bill Davidsen wrote:
> Jan Engelhardt wrote:
>> Colored kernel message output
>>
>> Let's work more on Linux's cuteness! [http://lkml.org/lkml/2007/10/4/431]
>> The following patch makes it possible to give kernel messages a
>> selectable color which helps to distinguish it
David wrote:
> It would probably be better to just save references to the tasks.
>
> struct cgroup_iter it;
> struct task_struct *p, **tasks;
> int i = 0;
>
> cgroup_iter_start(cs->css.cgroup, );
> while ((p = cgroup_iter_next(cs->css.cgroup, ))) {
>
Jan Engelhardt wrote:
Colored kernel message output
Let's work more on Linux's cuteness! [http://lkml.org/lkml/2007/10/4/431]
The following patch makes it possible to give kernel messages a
selectable color which helps to distinguish it from other noise,
such as boot messages. NetBSD has it,
On Sat, 2007-10-06 at 08:59 -0700, Linus Torvalds wrote:
> We do have a rule about "no regressions", so I think we'll have to do the
> revert, but it would be nice to hear what the consequences for the revert
> is for the affected hardware and new X.org..
No regressions is more important than
H. Peter Anvin wrote:
Alan Cox wrote:
On Fri, 05 Oct 2007 15:11:52 -0700
"H. Peter Anvin" <[EMAIL PROTECTED]> wrote:
Jan Engelhardt wrote:
15 partitions (at least for sd_mod devices) are too few.
Now when we have 20-bit minors, can't we simply recycle some of the
higher bits for additional
On Sat, Oct 06, 2007 at 07:58:52PM +0200, Oliver Pinter wrote:
> Hi All!
>
> this: http://www.milw0rm.com/exploits/4460http://www.milw0rm.com/exploits/4460
>
> exploit is fixed in kernel or not? this find I now..
Yes it's fixed by commit 176df2457 on 2007/09/21. It was CVE-2007-4573.
Regards,
Colored kernel message output (1/2)
This patch makes it possible to give kernel messages a selectable
color. It can be chosen at compile time, overridden at boot time,
and changed at run time.
There is no way to disable this option. It would only add ugly
ifdefs, and the default color is the
Colored kernel message output (2/2)
By popular request, this patch adds per-loglevel coloring.
The user may set values using vt.printk_color= or by modifying
the sysfs file in the running system.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/early_printk.c | 11
Kyle Moffett wrote:
On Oct 04, 2007, at 21:44:02, Eric W. Biederman wrote:
What we want from the LSM is the ability to say -EPERM when we can
clearly articulate that we want to disallow something.
This sort of depends on perspective; typically with security
infrastructure you actually want
> Maintenance and acceptance of the m4/make/perl/C/ncurses community of my
> mainly `TERM=linux ; sed && sh' approach is more important for me.
There is noone having trouble with ncurses dependency today.
And perl is not yet mandatory for a kernel build expect
for a few architectures.
m4 is not
On Sat, Oct 06, 2007 at 08:19:03PM +0200, Arnd Bergmann wrote:
> +static int compat_put_ushort(unsigned long arg, unsigned short val)
> +{
> + return put_user(val, (unsigned short __user *)compat_ptr(arg));
> +}
> +
> +static int compat_put_int(unsigned long arg, int val)
> +{
> + return
Trimmed the CC list a bit
On Oct 05, 2007, at 20:51:21, H. Peter Anvin wrote:
Ralf Baechle wrote:
To be consistent with the use of attributes in the rest of the
kernel replace all use of __attribute_pure__ with __pure and
delete the definition of __attribute_pure__.
Concern:
Scott wrote:
On Oct 4, 2007, at 11:52 AM, Scott wrote:
I'm having what I think is a PCI bus problem.
I have a ASUS P5B Intel 965 motherboard and a DVICO Fusion HDTV5 RT
adapter on the PCI bus. When this adapter is recording (anything) I see
pci_abort messages repeating in the
Rik van Riel wrote:
On Thu, 4 Oct 2007 12:20:50 -0700 (PDT)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
On Thu, 4 Oct 2007, Andi Kleen wrote:
We've known for ages that it is possible. But it has been always so
rare that it was ignored.
Well we can now address the rarity. That is the whole
As found by sparse, a user space pointer is assigned to a kernel
data structure while calling other code with set_fs(KERNEL_DS),
which could lead to leaking kernel data if that pointer is
ever accessed.
I could not find any place in the floppy drivers that actually
uses that pointer, but
blk_trace_setup is broken on x86_64 compat systems,
this makes the code work correctly on all 64 bit architectures
in compat mode.
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
Index: linux-2.6/block/blktrace.c
===
---
The floppy ioctls are used by multiple drivers, so they should be
handled in a shared location. Also, add minor cleanups.
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
Index: linux-2.6/block/compat_ioctl.c
===
---
Make compat_blkdev_ioctl and blkdev_ioctl reflect the respective
native versions. This is somewhat more efficient and makes it easier
to keep the two in sync.
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
Index: linux-2.6/block/Makefile
These are common to multiple block drivers, so they should
be handled by the block layer.
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
Index: linux-2.6/block/compat_ioctl.c
===
--- linux-2.6.orig/block/compat_ioctl.c
+++
These are shared by all cd-rom drivers and should have common
handlers. Do slight cosmetic cleanups in the process.
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
Index: linux-2.6/block/compat_ioctl.c
===
---
This is my block ioctl series split up into managable chunks. I'm not
really sure about the last two of these, I'd prefer to get a second
opinion on those.
Please apply once your tests have gone though.
Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Handle those blockdev ioctl calls that are compatible
directly from the compat_blkdev_ioctl() function, instead
of having to go through the compat_ioctl hash lookup.
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
Index: linux-2.6/block/compat_ioctl.c
BLKPG is common to all block devices, so it should be handled
by common code.
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
Index: linux-2.6/block/compat_ioctl.c
===
--- linux-2.6.orig/block/compat_ioctl.c
+++
Normally, all compat_ioctl operations are called without the BKL, the
block device operations are an exception to this rule.
Make this work the same as the other handlers.
Signed-off-by: Arnd Bergmann <[EMAIL PROTECTED]>
---
It would be good to find out whether it has been using the BKL
on
Yinghai Lu wrote:
On 9/28/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
Ayaz Abdulla wrote:
I am trying to track down a forcedeth driver issue described by bug 9047
in bugzilla (2.6.23-rc7-git1 forcedeth w/ MCP55 oops under heavy load).
I added a patch to synchronize the timer handlers so that
Hi All!
this: http://www.milw0rm.com/exploits/4460http://www.milw0rm.com/exploits/4460
exploit is fixed in kernel or not? this find I now..
--
Thanks,
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
On Sat, 6 Oct 2007, Paul Jackson wrote:
> This isn't working for me.
>
> The key kernel routine for updating a tasks cpus_allowed
> cannot be called while holding a spinlock.
>
> But the above loop holds a spinlock, css_set_lock, between
> the cgroup_iter_start and the cgroup_iter_end.
>
> I
* Sat, 6 Oct 2007 13:08:35 +0200
> * Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
>> Colored kernel message output
>>
>> Let's work more on Linux's cuteness!
>> [http://lkml.org/lkml/2007/10/4/431] The following patch makes it
>> possible to give kernel messages a selectable color
Only boot
On 9/28/07, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Ayaz Abdulla wrote:
> > I am trying to track down a forcedeth driver issue described by bug 9047
> > in bugzilla (2.6.23-rc7-git1 forcedeth w/ MCP55 oops under heavy load).
> > I added a patch to synchronize the timer handlers so that one
On Sat, Oct 06, 2007 at 09:03:00AM -0700, Linus Torvalds wrote:
>
>
> On Sat, 6 Oct 2007, Oleg Verych wrote:
> >
> > Thanks. I will be specific, after i will finish, what i already have,
> > to make air a bit less hot. Of course everything will be back
> > compatible, so nothing to worry about
Mathieu Chouquet-Stringer wrote:
Hey there,
I've seen the changes you made in commit b6a2fea39318 and I guess they
might be responsible for my xargs breakage...
In the kernel source tree, if I run a stupid find | xargs ls, I now get
this:
xargs: ls: Argument list too long
Which is
On Sat, Oct 06, 2007 at 01:08:35PM +0200, Ingo Molnar wrote:
> feature request: would be interesting to have a color table (defined in
> the .config) dependent on message loglevel. That way KERN_CRIT messages
> could be red, KERN_INFO ones white, etc.
If we do this, please let there be a
I can't get "hdparm -S" to work at all.
Using "hdparm -S 1" should set the timeout to
5 seconds, but the drives stay active/idle all the
time. When I set to standby manually, the drives
stay on standby for days, and start up fine when
they are used. I know this because I logged status
every 30
from: Gilles Gigan <[EMAIL PROTECTED]>
Adds watchdog driver for EPIC Nano 7240 boards from IEI
Signed-off-by: Gilles Gigan <[EMAIL PROTECTED]>
---
diff -uprN -X linux-2.6.23-rc9/Documentation/dontdiff
linux-2.6.23-rc9/drivers/char/watchdog/Kconfig
Hello,
When IOCB_FLAG_RESFD flag is set and iocb->aio_resfd is incorrect,
statement 'goto out_put_req' is executed. At label 'out_put_req',
aio_put_req(..) is called, which requires 'req->ki_filp' set.
Regards
Signed-off-by: Yan Zheng<[EMAIL PROTECTED]>
diff -ur linux-2.6.23-rc9/fs/aio.c
On Sat, 6 Oct 2007, Oleg Verych wrote:
>
> Thanks. I will be specific, after i will finish, what i already have,
> to make air a bit less hot. Of course everything will be back
> compatible, so nothing to worry about (the rewrite).
Qutie frankly, this kind of "I'll tell you more when I'm done"
On Sat, 6 Oct 2007, Jiri Slaby wrote:
>
> I guess, this will break my graphics, no?
http://lkml.org/lkml/2007/9/20/447
Can you try it?
We do have a rule about "no regressions", so I think we'll have to do the
revert, but it would be nice to hear what the consequences for the revert
is for
On Sat, 6 Oct 2007, Mike Frysinger wrote:
> On 10/6/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> > the result of running a quick and dirty shell script that
> > locates inclusions of header files under "include/linux" where
> > those header files don't appear to exist. (i didn't look any
Jeff Garzik wrote:
The goals of these changes are:
* move the driver towards a more sane, simple, easy to verify locking
setup -- irq handler would often acquire/release the lock twice
for each interrupt -- and hopefully
s/and hopefully// (it became the next bullet point)
-
To
On Sat, Oct 06, 2007 at 11:12:50AM -0400, Jeff Garzik wrote:
>
> The 'fe-lock' branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git fe-lock
It should also be pointed out that these patches were generated on top
of davem's net-2.6.24.git tree.
They -probably- apply
commit d7c766113ee2ec66ae8975e0acbad086d2c23594
Author: Jeff Garzik <[EMAIL PROTECTED]>
Date: Sat Oct 6 10:57:56 2007 -0400
[netdrvr] forcedeth: timer overhaul
* convert stats_poll timer to a delayed-work workqueue stats_task
* protect hw stats update with a lock
commit 39572457a4dfe9a9dc1efd6641e7a6467e5658a1
Author: Jeff Garzik <[EMAIL PROTECTED]>
Date: Sat Oct 6 01:21:01 2007 -0400
[netdrvr] forcedeth: internal simplification and cleanups
* remove changelog from source; its kept in git repository
* split guts of RX/TX DMA
commit 57cbfacc00d69be2ba02b65d1021442273b76263
Author: Jeff Garzik <[EMAIL PROTECTED]>
Date: Fri Oct 5 23:25:56 2007 -0400
[netdrvr] forcedeth: process TX completions using NAPI
Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
drivers/net/forcedeth.c | 143
commit a606d2a111cdf948da5d69eb1de5526c5c2dafef
Author: Jeff Garzik <[EMAIL PROTECTED]>
Date: Fri Oct 5 22:56:05 2007 -0400
[netdrvr] forcedeth: interrupt handling cleanup
* nv_nic_irq_optimized() and nv_nic_irq_other() were complete duplicates
of nv_nic_irq(), with the
commit 7bfc023b952e8e12c7333efccd2e78023c546a7c
Author: Jeff Garzik <[EMAIL PROTECTED]>
Date: Fri Oct 5 20:50:24 2007 -0400
[netdrvr] forcedeth: make NAPI unconditional
Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
drivers/net/Kconfig | 17 -
drivers/net/forcedeth.c |
The 'fe-lock' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git fe-lock
contains the following changes that I would like to get tested:
[netdrvr] forcedeth: make NAPI unconditional
[netdrvr] forcedeth: interrupt handling cleanup
[netdrvr]
On Fri, Oct 05, 2007 at 04:35:41AM +0200, Roman Zippel wrote:
> Hi,
>
> On Mon, 1 Oct 2007, Oleg Verych wrote:
>
> > Today's kconfig was proposed and accepted in a very unpleasant
> > circumstances, has very poor design, development and no working
> > alternative (for 5+ years now).
>
> If you
On Fri, 5 Oct 2007, Guennadi Liakhovetski wrote:
> On Sat, 6 Oct 2007, Michael Tokarev wrote:
>
> [snip]
> > That to say - it may be some miscompilations, but may be some probs with
> > hardware itself. If you can, try to reproduce the same on another board
> > (I just tried to boot 2.6.23-rc5
On Sat, 6 Oct 2007, [EMAIL PROTECTED] wrote:
> -hiroyasu ohyama
>
> I wonder what corrected attached source makes good performance of
> getting page slot cluster from page area discripter which is written
> "si" in the source codes.
> Because I think head of swap_list_t discripter doesn't
On 10/6/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> the result of running a quick and dirty shell script that locates
> inclusions of header files under "include/linux" where those header
> files don't appear to exist. (i didn't look any more closely at the
> results and, apparently,
The current Linux kernel currently contains the generate_random_uuid()
function, which creates - based on RFC 4122 - truly random UUIDs and provides
them to userspace through /proc/sys/kernel/random/boot_id and
/proc/sys/kernel/random/uuid.
The attached patch additionally adds the "Time-based
This patch fixes the DMA cascade by masking the correct bits.
Tested and working with Dreamcast PVR2 DMA. With this patch applied
the existing mainline code in arch/sh/drivers/dma/dma-sh.c works,
whereas before I was patching that to get round this problem.
Signed-off by: Adrian McMenamin
Pavel Machek wrote:
> It just would be nice to have example specifying one way...
I don't see a necessity.
--
Stefan Richter
-=-=-=== =-=- --==-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Jan Engelhardt <[EMAIL PROTECTED]> writes:
> What we see here might not be "ASCII", but "VGA-specific color values".
> It's just that I call it ASCII since it's the mirrored opposite of ANSI.
I see. Then perhaps "VGA color value" would be better.
--
Krzysztof Halasa
-
To unsubscribe from this
Am Samstag, 6. Oktober 2007 10:29 schrieb Hans-Peter Jansen:
> Am Donnerstag, 4. Oktober 2007 19:05 schrieb Mathieu Chouquet-Stringer:
> > Hey there,
> >
> > I've seen the changes you made in commit b6a2fea39318 and I guess they
> > might be responsible for my xargs breakage...
> >
> > In
* Paul Jackson <[EMAIL PROTECTED]> wrote:
> From: Paul Jackson <[EMAIL PROTECTED]>
>
> Add a new per-cpuset flag called 'sched_load_balance'.
[...]
> See further the Documentation and comments in the code itself.
>
> Signed-off-by: Paul Jackson <[EMAIL PROTECTED]>
Acked-by: Ingo Molnar
* Erez Zadok <[EMAIL PROTECTED]> wrote:
> So, I ran the above script and it found nearly 1.5 million reported
> warnings/errors, with drivers being the largest abuser, not
> surprisingly. [...]
have you tried that with the latest version too:
* Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> Colored kernel message output
>
> Let's work more on Linux's cuteness!
> [http://lkml.org/lkml/2007/10/4/431] The following patch makes it
> possible to give kernel messages a selectable color which helps to
> distinguish it from other noise,
On 10/06/2007 07:42 AM, Kyle McMartin wrote:
> This reverts commit f443675affe3f16dd428e46f0f7fd3f4d703eeab, which
> breaks horribly if you aren't running an unreleased xf86-video-intel
> driver out of git.
I guess, this will break my graphics, no?
http://lkml.org/lkml/2007/9/20/447
> Conflicts:
On Oct 5 2007 17:00, Andrew Morton wrote:
>>
>> It is already possible to deactivate the vc bell on a per-tty basis,
>> by using echo -en "\e[11;0]", but this is reset on reset(1).
>>
>> This adds a sysfs parameter to globally control the vc bell, as well
>> as sysfs parameters for default
> > + host->addr = pci_resource_start(pdev, 0);
> >
> > if (!request_region(host->addr, 256, "i91u")) {
> > printk(KERN_WARNING "initio: I/O port range 0x%x is busy.\n",
> > host->addr);
>
> I tried this fix on my SuSE 10.3 system (2.6.22.5-29 kernel) and it
> didn't work. The
On Oct 6 2007 10:55, Alan Cox wrote:
>> >
>> > It is already possible to deactivate the vc bell on a per-tty basis,
>> > by using echo -en "\e[11;0]", but this is reset on reset(1).
>> >
>> > This adds a sysfs parameter to globally control the vc bell, as well
>> > as sysfs parameters for
FYI, just found this V4L build failure in -rc9:
drivers/built-in.o: In function `saa7146_unregister_device':
: undefined reference to `video_unregister_device'
drivers/built-in.o: In function `saa7146_register_device':
: undefined reference to `video_device_alloc'
drivers/built-in.o: In
the result of running a quick and dirty shell script that locates
inclusions of header files under "include/linux" where those header
files don't appear to exist. (i didn't look any more closely at the
results and, apparently, these missing header files aren't fatal since
the builds still work
On Fri, 5 Oct 2007 17:00:11 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Fri, 5 Oct 2007 13:55:52 +0200 (CEST)
> Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
> >
> > It is already possible to deactivate the vc bell on a per-tty basis,
> > by using echo -en "\e[11;0]", but this is reset on
1 - 100 of 230 matches
Mail list logo
