Hi,
I am resending this to the orinoco devel mailing list.
Today I have tried using a Linksys WPC11 WLAN card and another Senao
NL2511 Plus and I am seeing the same errors in the kernel log and
again, the network interface does not show up with iwconfig.
These two cards are known to be working
Alex Dubov wrote:
>
> You'll agree, I think, that add_disk in mmc_block_probe issues a lot of
> requests (reads partition
> table, fs superblocks and such - plenty of room for critical errors). Then,
> driver's remove method
> will not be called before driver's probe method had finished. So
Signed-off-by: <[EMAIL PROTECTED]>
---
Documentation/memctlr.txt | 70 ++
1 file changed, 70 insertions(+)
diff -puN /dev/null Documentation/memctlr.txt
--- /dev/null 2007-02-02 22:51:23.0 +0530
+++
This patch reclaims pages from a container when the container limit is hit.
The executable is oom'ed only when the container it is running in, is overlimit
and we could not reclaim any pages belonging to the container
A parameter called pushback, controls how much memory is reclaimed when the
This patch adds the basic accounting hooks to account for pages allocated
into the RSS of a process. Accounting is maintained at two levels, in
the mm_struct of each task and in the memory controller data structure
associated with each node in the container.
When the limit specified for the
This patch sets up the basic controller infrastructure on top of the
containers infrastructure. Two files are provided for monitoring
and control memctlr_usage and memctlr_limit.
memctlr_usage shows the current usage (in pages, of RSS) and the limit
set by the user.
memctlr_limit can be used
This patch applies on top of Paul Menage's container patches (V7) posted at
http://lkml.org/lkml/2007/2/12/88
It implements a controller within the containers framework for limiting
memory usage (RSS usage).
The memory controller was discussed at length in the RFC posted to lkml
On Sun, 2007-02-18 at 10:27 +0100, Mike Galbraith wrote:
> On Sun, 2007-02-18 at 09:02 +0100, Mike Galbraith wrote:
>
> > The reason it's hanging is that nobody releases the driver, so we wait
> > forever in driver_unregister(). With the below, box boots fine...
> >
> > ---
On Sun, Feb 18, 2007 at 09:14:21PM -0800, Phy Prabab wrote:
> Willy,
>
> Thanks for the heads up and patch location. It looks like the guys at
> RH seemed to have applied a patch to allow one to set affinity,
> however, it might be that it is broken. Guess I will have to contact
> the RH people
Hi,
>From SUSv3, I expected SIGCHLD from dead processes (already reaped by wait(2))
should be cleared. But it seems that such situation is not handled in Linux.
Here is a test program. set sigchld handler and call waitpid() in main().
==
#include
#include
#include
#include
int
Hi Jean,
On Sunday 18 February 2007 15:30, Jean Delvare wrote:
> In platform_device_del(), we currently delete the device resources
> first, then we delete the device itself. This causes a (minor) bug to
> occur when one unregisters a platform device before unregistering its
> platform driver,
On Sunday 18 February 2007 9:28 pm, Randy Dunlap wrote:
> On Sun, 18 Feb 2007 21:08:07 -0800 David Brownell wrote:
>
> > Currently a parport_driver can't get a handle on the device node for the
> > underlying parport (PNPACPI, PCI, etc). That prevents correct placement
> > of sysfs child nodes,
On Sun, 18 Feb 2007 21:08:07 -0800 David Brownell wrote:
> Currently a parport_driver can't get a handle on the device node for the
> underlying parport (PNPACPI, PCI, etc). That prevents correct placement
> of sysfs child nodes, which can affect things like power management.
>
> This patch
On Sunday 18 February 2007 4:28 pm, Andrew Morton wrote:
> On Mon, 19 Feb 2007 00:32:08 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> wrote:
>
> > One more thing:
> >
> > rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
> > Unable to handle kernel NULL pointer dereference at
Currently a parport_driver can't get a handle on the device node for the
underlying parport (PNPACPI, PCI, etc). That prevents correct placement
of sysfs child nodes, which can affect things like power management.
This patch resolves that issue for non-legacy configurations:
* "struct
Dear Kernel Developers,
Since the most recent successful for me kernel 2.6.19-rc6-mm1, I've
tried few times to build more recent snapshots and now finally
2.6.20-mm2. In all those cases I have a sad outcome -- kernel boots but
at some point during boot (few moments after Penguin icon in the top
Willy,
Thanks for the heads up and patch location. It looks like the guys at
RH seemed to have applied a patch to allow one to set affinity,
however, it might be that it is broken. Guess I will have to contact
the RH people to get an update as to what they did/did not do.
Thanks!
Phy
On
On Wed, 7 Feb 2007, Andy wrote:
> If the scroll lock is on and there is a bunch of console output, the machine
> will eventually stop responding to the network, until scroll lock is turned
> off (at sometimes that doesn't even help).
>
> Easy test:
>
> hit scroll lock
> do a few echo t >
From: Erez Zadok <[EMAIL PROTECTED]>
A user-specified get_nlinks may depend on other inode attributes.
Cc: Michael Halcrow <[EMAIL PROTECTED]>
Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>
Signed-off-by: Josef 'Jeff' Sipek <[EMAIL PROTECTED]>
---
fs/stack.c | 14 +-
1 files
Hi Phy !
On Sun, Feb 18, 2007 at 06:02:17PM -0800, Phy Prabab wrote:
> Hello everyone,
>
> I am trying to set affinity on a program to make sure I can get the
> best use of the cache as possible and to eliminate as much noise as
> possible with running my program. I have tried unsuccessfully to
Lennart Sorensen wrote:
> On Sun, Feb 18, 2007 at 05:15:30PM +0100, Udo van den Heuvel wrote:
>> FYI: My situation is a VIA Epia EN12000 with a TranquilPC dual PCI riser
>> where only the Device Number can be changed.
>> The kernel sees the two DVB cards in there as:
>>
>> saa7146: register
On 2/19/07, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
Ian, you have an PATA controller so there is no need to use ata_piix.
Just disabling ata_piix should workaround the issue.
OK. I have done this and the message goes away in boot logs. As you
say I don't need the old drivers
The latest maintenance release GIT 1.5.0.1 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.0.1.tar.{gz,bz2} (tarball)
git-htmldocs-1.5.0.1.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.0.1.tar.{gz,bz2}
Hello everyone,
I am trying to set affinity on a program to make sure I can get the
best use of the cache as possible and to eliminate as much noise as
possible with running my program. I have tried unsuccessfully to set
affinity using sched_set/getaffinity and the CPU_SET macros. In
On Sun, 2007-02-18 at 19:40 -0600, Eric Sandeen wrote:
> Andrew Morton wrote:
> > I thought Eric fixed that. Maybe he broke it instead ;)
>
> Eeek... I'll reserve judgment on who broke what until I see that
> corrupted image... ;) is it available? How huge?
2G, but bzip'ed e2image -r is 54M:
On Sunday 18 February 2007 19:39, Lennart Sorensen wrote:
[snip]
> > > On a PC, the BIOS is supposed to assign interrupts to devices based on
> > > those rules, since that is how the hardware must be done according to
> > > the PCI specifications.
> >
> > I set the BIOS for 'PnP OS installed'.
Andrew Morton wrote:
On Mon, 19 Feb 2007 10:52:42 +1100 Rusty Russell <[EMAIL PROTECTED]> wrote:
Hi all,
This happened on 2.6.20-rc6-mm3, so I upgraded to 2.6.20-git14, and
same thing happened. Doing a forced fsck on the (corrupted by
double-mounting I think) filesystem fixed it, but
> > > In general, writepage is supposed to do work without blocking on
> > > expensive locks that will get pdflush and dirty reclaim stuck in this
> > > fashion. You'll probably have to take the same approach reiserfs does
> > > in data=journal mode, which is leaving the page dirty if
On Mon, Feb 19, 2007 at 01:54:31AM +0100, Miklos Szeredi wrote:
> > > > > > If so, writes to B will decrease the dirty memory threshold.
> > > > >
> > > > > Yes, but not by enough. Say A dirties a 1100 pages, limit is 1000.
> > > > > Some pages queued for writeback (doesn't matter how much). B
On 18/02/07, Alex Riesen <[EMAIL PROTECTED]> wrote:
Thomas Gleixner, Sun, Feb 18, 2007 13:36:56 +0100:
> On Sun, 2007-02-18 at 10:50 +0100, Alex Riesen wrote:
> > > The arch/i386/kernel/process.c part of the patch should apply to 2.6.20
> > > as well. Can you check if the problem is there too ?
> > > > > If so, writes to B will decrease the dirty memory threshold.
> > > >
> > > > Yes, but not by enough. Say A dirties a 1100 pages, limit is 1000.
> > > > Some pages queued for writeback (doesn't matter how much). B writes
> > > > back 1, 1099 dirty remain in A, zero in B.
On Mon, Feb 19, 2007 at 01:25:21AM +0100, Miklos Szeredi wrote:
> > > > If so, writes to B will decrease the dirty memory threshold.
> > >
> > > Yes, but not by enough. Say A dirties a 1100 pages, limit is 1000.
> > > Some pages queued for writeback (doesn't matter how much). B writes
> > >
> > > > If so, writes to B will decrease the dirty memory threshold.
> > >
> > > Yes, but not by enough. Say A dirties a 1100 pages, limit is 1000.
> > > Some pages queued for writeback (doesn't matter how much). B writes
> > > back 1, 1099 dirty remain in A, zero in B. balance_dirty_pages()
On Sun, 18 Feb 2007, Andi Kleen wrote:
> On Saturday 17 February 2007 09:35, Zwane Mwaikambo wrote:
> > On Fri, 16 Feb 2007, Andrew Morton wrote:
> >
> > > On Fri, 16 Feb 2007 06:39:45 -0800 (PST) Zwane Mwaikambo <[EMAIL
> > > PROTECTED]> wrote:
> > >
> > > > On Thu, 15 Feb 2007, Andrew Morton
There is a newly updated ext4 patchset available at:
http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches
and
http://www2.kernel.org/git/?p=linux/kernel/git/tytso/ext4.git
Compared to 2.6.20-ext4-1, I've removed the the i_version patch, since
they had numerous
On Mon, 19 Feb 2007 10:52:42 +1100 Rusty Russell <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> This happened on 2.6.20-rc6-mm3, so I upgraded to 2.6.20-git14, and
> same thing happened. Doing a forced fsck on the (corrupted by
> double-mounting I think) filesystem fixed it, but I took a copy
> --- a/fs/fs-writeback.c~a
> +++ a/fs/fs-writeback.c
> @@ -356,7 +356,7 @@ int generic_sync_sb_inodes(struct super_
> continue; /* Skip a congested blockdev */
> }
>
> - if (wbc->bdi && bdi != wbc->bdi) {
> + if (wbc->bdi
Francis Moreau wrote:
Hi,
I must miss something...
Looking at these prototypes
unsigned long simple_strtoul(const char *cp, char **endp,unsigned int base)
unsigned long long memparse (char *ptr, char **retptr)
I'm really wondering why not all parameters are not all 'const'. None
of these
On Mon, 19 Feb 2007 00:32:08 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
wrote:
> On Sunday, 18 February 2007 06:51, Andrew Morton wrote:
> >
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.20-mm2/
> >
> > Will appear later at
> >
> >
> >
On Mon, 19 Feb 2007 00:33:26 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
wrote:
> On Sunday, 18 February 2007 06:51, Andrew Morton wrote:
> >
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.20-mm2/
> >
> > Will appear later at
> >
> >
> >
On Sun, 2007-02-18 at 22:24 +0100, Arjan van de Ven wrote:
> On Fri, 2007-02-16 at 13:41 +0100, Ingo Molnar wrote:
> > * Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> >
> > > So I propose we remove all assumptions from the code that we actually
> > > have an array of irqs. That will allow for
Randy Dunlap wrote:
On Sun, 18 Feb 2007 09:32:15 -0800 H. Peter Anvin wrote:
Jean Delvare wrote:
On Thu, 15 Feb 2007 06:34:35 -0800, H. Peter Anvin wrote:
Jean Delvare wrote:
On x86, the BIOS led state can be read from byte 0x97 the BIOS RAM. The
BIOS RAM is mapped at 0x400 so all we need
> > > If so, writes to B will decrease the dirty memory threshold.
> >
> > Yes, but not by enough. Say A dirties a 1100 pages, limit is 1000.
> > Some pages queued for writeback (doesn't matter how much). B writes
> > back 1, 1099 dirty remain in A, zero in B. balance_dirty_pages() for
> > B
Hi Jiri,
> > I m using a Logitech MX 5000 keyboard with an included MX 1000 mouse,
> > both bluetooth using the same USB reciever.
> > When the USB reciever is already plugged-in at boot-time and the
> > Bluetooth service fires-up I get this message:
> > ===
> > BUG: warning:
Ingo Molnar writes:
> add include/linux/syslet.h which contains the user-space API/ABI
> declarations. Add the new header to include/linux/Kbuild as well.
> +struct syslet_uatom {
> + unsigned long flags;
> + unsigned long nr;
> +
On Mon, 19 Feb 2007 00:25:48 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
wrote:
> > netconsole is good.
>
> I know. :-)
>
> In the meantime, I've got something worse on another x86_64 box:
>
> Asus Laptop ACPI Extras version 0.30
> L5D model detected, supported
> audit(1171831698.918:2):
On Sun, Feb 18, 2007 at 06:31:23AM -0500, Jaya Kumar wrote:
> On 2/17/07, Paul Mundt <[EMAIL PROTECTED]> wrote:
> >This would also provide an interesting hook for setting up chained DMA
> >for the real framebuffer updates when there's more than a couple of pages
> >that have been touched, which
On Mon, 19 Feb 2007 00:22:11 +0100 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> > If so, writes to B will decrease the dirty memory threshold.
>
> Yes, but not by enough. Say A dirties a 1100 pages, limit is 1000.
> Some pages queued for writeback (doesn't matter how much). B writes
> back 1,
Hi all,
This happened on 2.6.20-rc6-mm3, so I upgraded to 2.6.20-git14, and
same thing happened. Doing a forced fsck on the (corrupted by
double-mounting I think) filesystem fixed it, but I took a copy before
doing that.
Do we care about ext3 barfing on corrupted filesystems?
[
> > This is hard to trigger problem, so I'll spare you the rather lengthy log.
> > It happens if card timeouts and mmc_remove_host is called while
> > mmc_register_card is still in
> > progress (the hint was in crash dump). If I sleep before remove, it gives
> > the
> mmc_register_card
> >
Eensy weensy follow-up. No screed. Well, maybe just a _little_ screed.
On 2/18/07, Oleg Verych <[EMAIL PROTECTED]> wrote:
Ulrich Drepper is known to be against current FSF's position on glibc
licence changing.
Will that stop the FSF? Will it stop Red Hat, MontaVista, or
CodeSourcery? Even
On 19/02/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
On Sunday, 18 February 2007 20:43, Andrew Morton wrote:
> On Sun, 18 Feb 2007 13:44:54 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
wrote:
>
> > On Sunday, 18 February 2007 06:51, Andrew Morton wrote:
> > >
> > > Temporarily at
> > >
>
On Sunday, 18 February 2007 06:51, Andrew Morton wrote:
>
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.20-mm2/
>
> Will appear later at
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/
I think something like this is generally necessary:
On Sunday, 18 February 2007 06:51, Andrew Morton wrote:
>
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.20-mm2/
>
> Will appear later at
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/
One more thing:
rtc_cmos 00:02: rtc core: registered
On Sunday, 18 February 2007 23:17, Oleg Nesterov wrote:
> refrigerator() can miss a wakeup, "wait event" loop needs a proper memory
> ordering.
>
> Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
ACK
> --- WQ/kernel/power/process.c~WAKE2007-02-18 22:56:49.0 +0300
> +++
On Sunday, 18 February 2007 20:43, Andrew Morton wrote:
> On Sun, 18 Feb 2007 13:44:54 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> wrote:
>
> > On Sunday, 18 February 2007 06:51, Andrew Morton wrote:
> > >
> > > Temporarily at
> > >
> > > http://userweb.kernel.org/~akpm/2.6.20-mm2/
> > >
Fedora is getting a bunch of bug reports about the I2O block
driver not working in 2.6.19 kernels.
Everything looks like it loads OK, but no block IO can be
done, not even reading the partition table:
I2O subsystem v1.325
i2o: max drivers = 8
i2o: Checking for PCI I2O controllers...
ACPI: PCI
On Sunday, 18 February 2007 23:01, Oleg Nesterov wrote:
> On 02/18, Rafael J. Wysocki wrote:
> >
> > Appended is a patch that does something along these lines. The necessary
> > thread_info flags are defined for i386 and x86_64, for now.
>
> I'll try to look at this patch when I am not so
> > > > I was testing the new fuse shared writable mmap support, and finding
> > > > that bash-shared-mapping deadlocks (which isn't so strange ;). What
> > > > is more strange is that this is not an OOM situation at all, with
> > > > plenty of free and cached pages.
> > > >
> > > > A little
> You could blacklist the ACPI "thermal" module instead. If you're
> interested in monitoring your CPU temperature, k8temp is IMHO more
> convenient to use than ACPI, as it interfaces properly with libsensors
> and all hardware monitoring user interfaces.
That would be somewhat dangerous because
Maynard Johnson wrote:
Arnd Bergmann wrote:
On Friday 16 February 2007 01:32, Maynard Johnson wrote:
config OPROFILE_CELL
bool "OProfile for Cell Broadband Engine"
depends on OPROFILE && SPU_FS
default y if ((SPU_FS = y && OPROFILE = y) || (SPU_FS = m &&
OPROFILE
On Sun, 2007-02-18 at 23:40 +0200, Timur Aydin wrote:
> reg is indeed 0x and the function returns -ENODEV.
>
> I need help to further troubleshoot the problem, any directions or
> hints welcome...
The card is likely dead, but please check it with hostap_cs and on
different hardware just in
I have a small hope this patch is correct (compile tested). At least, the code
was not correct before this patch. "Cancel and flush" should do "Cancel", and
then "flush".
Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
--- WQ/drivers/ata/libata-core.c~4_ata 2007-02-18 22:56:47.0 +0300
On Sun, 18 Feb 2007 23:50:14 +0100 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> > > I was testing the new fuse shared writable mmap support, and finding
> > > that bash-shared-mapping deadlocks (which isn't so strange ;). What
> > > is more strange is that this is not an OOM situation at all,
> Andrew Morton wrote:
> > On Sun, 18 Feb 2007 19:28:18 +0100 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> >
> >> I was testing the new fuse shared writable mmap support, and finding
> >> that bash-shared-mapping deadlocks (which isn't so strange ;). What
> >> is more strange is that this is not
> > I was testing the new fuse shared writable mmap support, and finding
> > that bash-shared-mapping deadlocks (which isn't so strange ;). What
> > is more strange is that this is not an OOM situation at all, with
> > plenty of free and cached pages.
> >
> > A little more investigation shows
On Sun, 18 Feb 2007 14:35:17 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
> I guess I need to do a git-blockless -mm3
OK, this is looking like a pain - I'd have to drop or significantly redo
thirty or more patches. Jens, please fix it asap.
-
To unsubscribe from this list: send the line
Hello all,
I got the DSDT from chuck and it seems there is nothing interesting - no
declaration of PCI_config for the registers. If someone wants to check it I can
send him the DSDT.
_TMP looks like this:
Store (\_SB.PCI0.LPC0.EC0.RTMP, Local0)
Store ("Current temp is: ",
On Sunday 18 February 2007 04:02:17 Josh Boyer wrote:
> On Sun, Feb 18, 2007 at 03:15:23AM +0100, Arnd Bergmann wrote:
> > On Sunday 18 February 2007 03:04, Josh Boyer wrote:
> > > No, the MTD interface isn't flawed. gluebi is present to make things
> > > like JFFS2 work on top of UBI volumes
On Sun, 18 Feb 2007 13:47:44 -0800 "Miles Lane" <[EMAIL PROTECTED]> wrote:
> It looks like there are some slight differences between the stack traces I
> have and the ones that have already been posted.
> I hope this helps,
> Miles
>
> psmouse.c: TouchPad at isa0060/serio1/input0 lost
change occurrence of hlist_for_each/hlist_entry to hlist_for_each_entry as it
combines the previous two macros
Signed-off-by: Thomas Hisch <[EMAIL PROTECTED]>
---
net/core/dev.c | 17 ++---
1 files changed, 6 insertions(+), 11 deletions(-)
diff --git a/net/core/dev.c
refrigerator() can miss a wakeup, "wait event" loop needs a proper memory
ordering.
Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
--- WQ/kernel/power/process.c~WAKE 2007-02-18 22:56:49.0 +0300
+++ WQ/kernel/power/process.c 2007-02-19 01:04:26.0 +0300
@@ -46,8 +46,10 @@
Turned on lock testing/proving/deadlock detection. Not chasing any
particular
problem, but looking for things "oddities".
Turned on options (under kernel hacking):
Locking API boot-time self-tests
RT Mutex debugging, deadlock detection
Lock debugging: prove locking correctness
Multiple
On 02/18, Rafael J. Wysocki wrote:
>
> Appended is a patch that does something along these lines. The necessary
> thread_info flags are defined for i386 and x86_64, for now.
I'll try to look at this patch when I am not so sleepy ...
just one small nit right now,
> ---
On Saturday 17 February 2007 09:35, Zwane Mwaikambo wrote:
> On Fri, 16 Feb 2007, Andrew Morton wrote:
>
> > On Fri, 16 Feb 2007 06:39:45 -0800 (PST) Zwane Mwaikambo <[EMAIL
> > PROTECTED]> wrote:
> >
> > > On Thu, 15 Feb 2007, Andrew Morton wrote:
> > >
> > > > It's not an X problem - the
pp_cam_entry->cb_task need not to be _NOAUTOREL ... because in fact it is
never used ???
Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
--- WQ/drivers/media/video/cpia_pp.c~3_cpia_pp 2006-12-17 19:06:40.0
+0300
+++ WQ/drivers/media/video/cpia_pp.c2007-02-19 00:27:41.0
Looks like dbs_timer() is very careful wrt per_cpu(cpu_dbs_info),
and it doesn't need the help of WORK_STRUCT_NOAUTOREL.
Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
--- WQ/drivers/cpufreq/cpufreq_ondemand.c~2_cpufreq 2007-02-18
22:56:47.0 +0300
+++
Afaics, noautorel work_struct buys nothing for "struct net_bridge_port".
If del_nbp()->cancel_delayed_work(>carrier_check) fails, port_carrier_check
may be called later anyway. So the reading of *work in port_carrier_check() is
equally unsafe with or without this patch.
Signed-off-by: Oleg
These patches change the code which I absolutely don't understand.
Compile tested. Please review.
Oleg.
-
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
Jan Beulich wrote:
> Whether a region is below 1Mb is determined by its start rather than
> its end.
>
> This hunk got erroneously dropped from a previous patch.
>
> Signed-off-by: Jan Beulich <[EMAIL PROTECTED]>
>
> --- linux-2.6.20/arch/i386/kernel/cpu/mtrr/generic.c 2007-02-04
>
Andrew Morton wrote:
On Sun, 18 Feb 2007 19:28:18 +0100 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
I was testing the new fuse shared writable mmap support, and finding
that bash-shared-mapping deadlocks (which isn't so strange ;). What
is more strange is that this is not an OOM situation at
On Fri, 2007-02-16 at 13:41 +0100, Ingo Molnar wrote:
> * Eric W. Biederman <[EMAIL PROTECTED]> wrote:
>
> > So I propose we remove all assumptions from the code that we actually
> > have an array of irqs. That will allow for irq_desc to be dynamically
> > allocated instead of statically
On Fri, 16 Feb 2007, Fortier,Vincent [Montreal] wrote:
> I m using a Logitech MX 5000 keyboard with an included MX 1000 mouse,
> both bluetooth using the same USB reciever.
> When the USB reciever is already plugged-in at boot-time and the
> Bluetooth service fires-up I get this message:
>
On 2/18/07, Theodore Tso <[EMAIL PROTECTED]> wrote:
Actually, the FSF and many of its representatives, has claimed, on
many occassions, that the GPL infects across dynamic linking. That
is, if you write your own code that calls readline which links via a
dynamically linked shared library, and
On 2/18/07, Davide Libenzi wrote:
Clets would execute in userspace, like signal handlers,
or like "event handlers" in cooperative multitasking environments
without the Unix baggage
but under the special schedule() handler.
or, better yet, as the next tasklet in the chain after the softirq
On Sun, 18 Feb 2007 19:28:18 +0100 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> I was testing the new fuse shared writable mmap support, and finding
> that bash-shared-mapping deadlocks (which isn't so strange ;). What
> is more strange is that this is not an OOM situation at all, with
> plenty
On Sunday 18 February 2007 20:53, Ian McDonald wrote:
> I'm getting this in my logs when starting up after going from a
> 2.6.20rc5 kernel (which didn't do this) to Linus' latest tree as of 36
> hours ago:
>
> Feb 18 14:52:32 localhost kernel: [ 16.392136] Uniform
> Multi-Platform E-IDE driver
Udo van den Heuvel <[EMAIL PROTECTED]> writes:
> FYI: My situation is a VIA Epia EN12000 with a TranquilPC dual PCI riser
> where only the Device Number can be changed.
With jumpers?
> So IRQ 16 and 20. But when using the stock 2.6.20 kernel there is no
> communication with the DVB-T card (the
[EMAIL PROTECTED] (Lennart Sorensen) writes:
> My understanding (which is better of verified against the specs) is:
>
> PCI interrupts (PCI INTA to INTD) are rotated for every slot by one. So
> slot 0, 4, 8, etc see INTA->realINTA, INTB->realINTB. INTC->realINTC,
> INTD->realINTD
> slot 1, 5, 9,
On Sun, 18 Feb 2007, Pavel Machek wrote:
> > > The upcall will setup a frame, execute the clet (where jump/conditions
> > > and
> > > userspace variable changes happen in machine code - gcc is pretty good in
> > > taking care of that for us) on its return, come back through a
> > >
Avi Kivity wrote:
Bill Davidsen wrote:
There doesn't seem to be a great place for KVM user questions, this
is it, and kvm-devel seems a poor place for user questions, while the
chat room is real time and depends on the question and the answer
being in the same place at the same time.
In platform_device_del(), we currently delete the device resources
first, then we delete the device itself. This causes a (minor) bug to
occur when one unregisters a platform device before unregistering its
platform driver, and the driver is requesting (in .probe()) and
releasing (in .remove()) a
On Fri, Feb 16, 2007 at 05:24:42PM -0800, Andrew Morton wrote:
> req_lock is initialsied in fs/nfs/inode.c:init_once().
Oh, it is indeed. Grmbl.
> What kernel version were you using?
I've reproduced this on a base 2.6.20 g5_defconfig + NFS root and serial
console options on a G5 here.
The
Hi!
> > The upcall will setup a frame, execute the clet (where jump/conditions and
> > userspace variable changes happen in machine code - gcc is pretty good in
> > taking care of that for us) on its return, come back through a
> > sys_async_return, and go back to userspace.
>
> So, for
Hi!
> Advanced Mathematics, lesson 1:
> 101 != 105
>
> ;-)
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
>
> ---
> --- linux-2.6.20-mm1/drivers/isdn/gigaset/Makefile.old2007-02-15
> 17:38:23.0 +0100
> +++ linux-2.6.20-mm1/drivers/isdn/gigaset/Makefile2007-02-15
>
Hi!
> >Contrawise, if Embedded developers do contribute their
> >device driver
> >changes back to the kernel, they will be fine. ...
> ---
>
> In fairness, though, some of the developers WILL bitch
> about your not
> using a recent kernel and not providing patches until
> products ship,
>
Hi!
> >> (See, among other cases, Lexmark. v. Static
> >> Controls.) A copyright is not a patent, you can only
> >own something if there
> >> are multiple equally good ways to do it and you claim
> >*one* of them.
> >
> >Only in a world where "write a Linux module" is a
> >"functional idea." I
On Sun, Feb 18, 2007 at 07:49:34PM +0200, Dan Aloni wrote:
| On Sun, Feb 18, 2007 at 06:13:38PM +0100, Andi Kleen wrote:
| > [adding mtd maintainer]
| >
| > On Sunday 18 February 2007 11:42, Cyrill Gorcunov wrote:
| > > On Sat, Feb 17, 2007 at 11:29:19PM +0200, Dan Aloni wrote:
| > > | Hello,
| >
On 18/02/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Sun, 18 Feb 2007 18:58:05 +0100 Mattia Dongili <[EMAIL PROTECTED]> wrote:
> On Sun, Feb 18, 2007 at 02:06:59PM +0100, Laurent Riffard wrote:
> > Le 18.02.2007 06:51, Andrew Morton a écrit :
> > >Temporarily at
> > >
> > >
> Except for the what appears to be instability of the irq numbers on
> simpler configurations I don't have a problem with it.
I agree that's a bit annoying and I beleive it can be fixed. In
additionm I'd like to look into exposing the domain/HW number -> virq
mapping somewhere in sysfs maybe.
1 - 100 of 398 matches
Mail list logo
