On Thu, 3 Mar 2005, Andrew Morton wrote:
Christoph Lameter [EMAIL PROTECTED] wrote:
On Wed, 2 Mar 2005, Andrew Morton wrote:
This is not relevant since it only deals with file pages.
OK. And CONFIG_DEBUG_PAGEALLOC?
Its a debug feature that can be fixed if its broken.
On Mer, 2005-03-02 at 22:21, Linus Torvalds wrote:
- 2.6.odd: still a stable kernel, but accept bigger changes leading up
to it (timeframe: a month or two).
- 2.odd.x: aim for big changes that may destabilize the kernel for
several releases (timeframe: a year or two)
- odd.x.x:
I'm not sure the change is any better. AMD now use Geode for two totally
unrelated CPU families and they need different configuration.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, 2005-03-03 at 11:27, Marcelo Tosatti wrote:
Hi Thomas,
I'm forwarding your message to Mikael and Len, who have knowledge
on the IOAPIC infrastructure.
- Forwarded message from [EMAIL PROTECTED] -
From: [EMAIL PROTECTED]
Date: Wed, 2 Mar 2005 13:37:03 +0800
To: [EMAIL
Hi.
Here are the stats:
1GB P4, 2.6.11+Suspend2 2.1.8.
Soft image size limit set to 2MB to emulate Pavel's implementation (eat
as much memory as we can).
Without patch:
Freed 16545 pages in 4000 jiffies = 16.16 MB/s
Freed 83281 pages in 14060 jiffies = 23.14 MB/s
Freed 237754 pages in 41482
On Iau, 2005-03-03 at 01:27, Dave Jones wrote:
In an ideal world, we'd see a single 'y' release of 2.6.x.y, but if x+1 takes
too long to be released, bits of x+1 should also appear in x.y+1
The only question in my mind is 'how critical does a bug have to be to
justify a .y release. Once a new
to den 03.03.2005 Klokka 22:46 (+0100) skreiv Andi Kleen:
As far as the kernel is concerned, asm/posix_types defines
__kernel_ino_t as unsigned long on most platforms (except a few which
define is as unsigned int). We don't care what size type glibc itself
uses.
That could easily be
On Thu, Mar 03, 2005 at 10:15:46PM +, Alan Cox wrote:
We still need 2.6.x.y updates on a more official footing and with more
than one person as the 2.6.x.y maintainer. I think that is actually
more important.
That appears to be the consensus conclusion we've arrived at.
Jeff
-
Jeff Garzik writes:
Rene Rebe wrote:
Hi,
--- linux-2.6.11/drivers/md/raid6altivec.uc.vanilla2005-03-02
16:44:56.407107752 +0100
+++ linux-2.6.11/drivers/md/raid6altivec.uc2005-03-02
16:45:22.424152560 +0100
@@ -108,7 +108,7 @@
int raid6_have_altivec(void)
{
I agree.
But what if the file systems can handle certain errors better than
what the drivers can do now ? Take for e.g., data corruption. If the
driver finds a corrupted sector that it cannot recover, it is going to
convert this specific error in to a more generic error code (-EIO) and
report it
On Thu, 3 Mar 2005 22:01:19 +0100, Adrian Bunk [EMAIL PROTECTED] wrote:
This patch contains cleanups including the following:
Are you cleaning up all of that annoying trailing whitespace too? It
is always giving me problems on diffs.
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from this
As I read the code the driver task (A) should _not_ be removed from the
runqueue. It has to be waken up to call schedule_timeout() such it gets
back on the runqueue after 10 ms. If it is taken out of the runqueue at
line 76 it will stay off the runqueue forever in the TASK_UNINTERRUBTIBLE
state!
Hi,
Jody McIntyre wrote:
I'll apply this to the 1394 tree and send it to Linus after testing if
you add a Signed-off-by: line per Documentation/SubmittingPatches .
Also, please cc [EMAIL PROTECTED] with ieee1394
changes.
Sure! Thanks!
Adds the missing failure handling for a __copy_to_user call.
On Thu, Mar 03, 2005 at 04:28:52PM -0500, Jeff Garzik wrote:
Bill Rugolsky Jr. wrote:
I've watched you periodically announce hey, I'm doing an update for
FC3/FC2, please test on the mail list, and a handful of people go test.
If we could convince many of the the less risk-averse but lazy users
Because Xen is compiled with -Wall -Werror, has inherited
processor.h from Linux and Fedora is now built with gcc4,
I discovered this bug.
The few callers I verified all call cpuid with unsigned
ints, but the function is defined with signed ints. This
trivial patch fixes that.
Signed-off-by: Rik
On Fri, Mar 04, 2005 at 09:30:22AM +1100, Paul Mackerras wrote:
Jeff Garzik writes:
Rene Rebe wrote:
Hi,
--- linux-2.6.11/drivers/md/raid6altivec.uc.vanilla2005-03-02
16:44:56.407107752 +0100
+++ linux-2.6.11/drivers/md/raid6altivec.uc2005-03-02
This patch contains the following cleanups:
- make a needlessly global function static
- remove the unused global function do_posix_clock_notimer_create
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
include/linux/posix-timers.h |3 +--
kernel/posix-timers.c|9 ++---
2
On Thu, Mar 03, 2005 at 01:37:26PM -0800, Trond Myklebust wrote:
to den 03.03.2005 Klokka 10:19 (+0100) skreiv Andi Kleen:
The problem here is that glibc uses stat64() which supports
64bit inode numbers. But glibc does the overflow checking itself
and generates the EOVERFLOW in user space.
On Thu, 3 Mar 2005, Hua Zhong wrote:
Indeed. What I have in mind (and suggested in the past) is that we have a
real 2.6 stable release maintainer. The only difference is that he starts
from a random 2.6.x release he picks, and releases 2.6.x.y until he thinks
stable enough, and he moves on
On Fri, Mar 04, 2005 at 09:30:22AM +1100, Paul Mackerras wrote:
I nominate this as a candidate for linux-2.6.11 release branch. :)
No. Unfortunately if you fix ppc64 here you will break ppc, and vice
versa. Yes, we are going to reconcile the cur_cpu_spec definitions
between ppc and
Hi!
I had accidently chosen CONFIG_PNP and noticed that my keyboard didn't
work with bk-dtor-input.patch in the tree (backing out makes keyboard
work).
diff -up working_dmesg nokeyboard_dmesg
--- working_dmesg 2005-03-03 22:15:52.0 +0100
+++ nokeyboard_dmesg2005-03-03
On Thu, 2005-03-03 at 13:53 -0800, David Lang wrote:
Actually, the 5 was pretty pointless anyway. What I got
from talking to people is that they wanted a release that only got fixes
that would crash the machine, or cause a root exploit. That's what I
thought Linus was trying to say.
On Friday 04 March 2005 00:53, Alan Jenkins wrote:
Having a GeForce FX 5200 which I expected to work under rivafb (kernel
version 2.6.11), I found the attached message on google groups.
I know it is a little later now, but would you think about getting the
work you've done committed?
I
On Friday 04 March 2005 01:03, Oded Shimon wrote:
- ods15
Oops.
diff -U 3 -r -N -X /usr/src/diffignore -- linux-2.6.6/drivers/video/riva/fbdev.c linux/drivers/video/riva/fbdev.c
--- linux-2.6.6/drivers/video/riva/fbdev.c 2004-05-10 05:32:54.0 +0300
+++ linux/drivers/video/riva/fbdev.c
On Thu, Mar 03, 2005 at 02:45:15PM -0800, Greg KH wrote:
On Fri, Mar 04, 2005 at 09:30:22AM +1100, Paul Mackerras wrote:
Jeff Garzik writes:
Rene Rebe wrote:
Hi,
--- linux-2.6.11/drivers/md/raid6altivec.uc.vanilla2005-03-02
16:44:56.407107752 +0100
+++
* Remove duplicate include.
* Avoid mode set to '' message when error updating /sys/power/disk.
Signed-off-by: Todd Poynor [EMAIL PROTECTED]
--- linux-2.6.11-rc4-orig/kernel/power/disk.c 2005-02-23 09:47:03.0
-0800
+++ linux-2.6.11-rc4-pm/kernel/power/disk.c 2005-03-03
This patch links all selected files under drivers/video/savagefb/ into
one module.
This required a renaming of savagefb.c to savagefb_driver.c .
As a side effect, the EXPORT_SYMBOL's in this directory are no longer
required.
---
Other names than savagefb_driver.c (e.g. savagefb_main.c) are
Hi Jody,
My previous e-mail seemed to be messed up by Thunderbird... so now I'm using
good
old Mutt again.
On Thu, Mar 03, 2005 at 04:48:43PM -0500 or thereabouts, Jody McIntyre wrote:
Thanks. Here's my third try :-)
With friendly regards,
Takis
I'll apply this to the 1394 tree and
Greg KH [EMAIL PROTECTED] wrote:
It's perfectly workable from a BK standpoint to do
- linux-2.6 commit
- cpcset into linux-2.6.X.Y [see Documentation/BK-usage/cpcset]
- pull from linux-2.6.X.Y into linux-2.6 [dups cset, but no
real code change]
That's fine with
From: Michael S. Tsirkin [EMAIL PROTECTED]
Set device_cap_flags field in mthca's query_device method.
Signed-off-by: Michael S. Tsirkin [EMAIL PROTECTED]
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
--- linux-export.orig/drivers/infiniband/hw/mthca/mthca_cmd.h 2005-01-25
Tie up one last loose end by mapping enough context memory to cover
the whole multicast table during initialization, and then enable
mem-free mode. mthca now supports enough of mem-free mode so that
IPoIB works with a mem-free HCA.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
---
From: Sean Hefty [EMAIL PROTECTED]
Modify ib_cancel_mad() to invoke a user's send completion callback from
a different thread context than that used by the caller. This allows a
caller to hold a lock while calling cancel that is also acquired from
their send handler.
Signed-off-by: Sean Hefty
Implement posting send and receive work requests for mem-free mode.
Also tidy up a few things in send/receive posting for Tavor mode (fix
smp_wmb()s that should really be just wmb()s, annotate tests in the
fast path with likely()/unlikely()).
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
---
From: Michael S. Tsirkin [EMAIL PROTECTED]
1. Split the QP spinlock into separate send and receive locks.
The only place where we have to lock both is upon modify_qp, and
that is not on data path.
2. Avoid taking any QP locks when polling CQ.
This last part is achieved by getting rid
Update QP initialization and cleanup to handle mem-free mode. In
mem-free mode, work queue sizes have to be rounded up to a power of 2,
we need to allocate doorbells, there must be memory mapped for the
entries in the QP and extended QP context table that we use, and the
entries of the receive
Update CQ initialization and cleanup to handle mem-free mode: we need
to make sure the HCA has memory mapped for the entry in the CQ context
table we will use and also allocate doorbell records.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
---
Add support for CQ data path operations (request notification, update
consumer index) in mem-free mode.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
--- linux-export.orig/drivers/infiniband/hw/mthca/mthca_cq.c2005-03-03
14:13:00.312829664 -0800
+++
Slightly improve debugging output for UNMAP_ICM and MODIFY_QP firmware commands.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
--- linux-export.orig/drivers/infiniband/hw/mthca/mthca_cmd.c 2005-01-25
20:48:02.0 -0800
+++ linux-export/drivers/infiniband/hw/mthca/mthca_cmd.c
Add a mthca_write_db_rec() to wrap writing doorbell records. On
64-bit archs, this is just a 64-bit write, while on 32-bit archs it
splits the write into two 32-bit writes with a memory barrier to make
sure the two halves of the record are written in the correct order.
Signed-off-by: Roland
Add support for mem-free mode to memory region code. This mostly
amounts to properly munging between keys and indices.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
--- linux-export.orig/drivers/infiniband/hw/mthca/mthca_mr.c2005-01-15
15:16:11.0 -0800
+++
Update interrupt handling code to handle mem-free mode. While we're
at it, improve the Tavor interrupt handling to avoid an extra MMIO
read of the event cause register.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
--- linux-export.orig/drivers/infiniband/hw/mthca/mthca_dev.h 2005-03-03
Add support for mapping more memory into HCA's context to cover
context tables when new objects are allocated. Pass the object
size into mthca_alloc_icm_table(), reference count the ICM chunks,
and add new mthca_table_get() and mthca_table_put() functions to
handle mapping memory when allocating
Add support for allocating user access regions (UARs). Use this to
allocate a region for kernel at driver init instead using hard-coded
MTHCA_KAR_PAGE index.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
--- linux-export.orig/drivers/infiniband/hw/mthca/Makefile 2005-01-15
From: Michael S. Tsirkin [EMAIL PROTECTED]
Avoid taking the CQ table lock in the fast path path by using
synchronize_irq() after removing a CQ from the table to make sure that
no completion events are still in progress. This gets a nice speedup
(about 4%) in IP over IB on my hardware.
From: Michael S. Tsirkin [EMAIL PROTECTED]
Locking during the poll cq operation can be reduced by locking the cq
while qp is being removed from the qp array. This also avoids an
extra atomic operation for reference counting.
Signed-off-by: Michael S. Tsirkin [EMAIL PROTECTED]
Signed-off-by:
On Thu, Mar 03, 2005 at 03:17:52PM -0800, Andrew Morton wrote:
That's the only way it _can_ work. The maintainer of 2.6.x.y shouldn't be
Andrew, what about my suggestion of shifting left x.y of 8 bits? ;) Do
we risk the magic 2.7 number to get us stuck in unstable mode for 2
years instead of 2
On Iau, 2005-03-03 at 16:59, Greg KH wrote:
On Thu, Mar 03, 2005 at 10:55:13AM -0600, Chris Friesen wrote:
Linus Torvalds wrote:
I'll tell you what the problem is: I don't think you'll find anybody to do
the parallell only trivial patches tree.
Isn't this what -ac and -as
Andrew Morton [EMAIL PROTECTED] wrote:
Peter Chubb [EMAIL PROTECTED] wrote:
Hi,
As part of the Gelato scalability focus group, we've been running
OSDL's Re-AIM7 benchmark with an I/O intensive load with varying
numbers of processors. The current kernel shows severe contention
Brice Figureau [EMAIL PROTECTED] wrote:
I'm reporting an oops on a bi-Xeon database server under 2.6.10-ac10
quite similar to:
http://marc.theaimsgroup.com/?l=ext3-usersm=110848085314238w=2
I also got another server crashing (a mail server this time), but I
couldn't get the oops/panic.
Roland Dreier wrote:
+void cancel_sends(void *data)
+{
+ struct ib_mad_agent_private *mad_agent_priv;
+ struct ib_mad_send_wr_private *mad_send_wr;
+ struct ib_mad_send_wc mad_send_wc;
+ unsigned long flags;
+
+ mad_agent_priv = (struct ib_mad_agent_private *)data;
Revised patch is attached.
Jean Delvare wrote:
Hi James,
A revised ds1337 patch addressing all of Jean's comments is attached.
Fine with me except for:
+ if (!i2c_check_functionality(adapter, I2C_FUNC_SMBUS_BYTE_DATA |
+I2C_FUNC_SMBUS_I2C_BLOCK))
I
On Fri, 4 Mar 2005, Benjamin Herrenschmidt wrote:
On Thu, 2005-03-03 at 12:38 -0300, Frédéric L. W. Meunier wrote:
Maybe we are having conflicting bus names between radeonfb
and matroxfb, or 2 instances of radeonfb ? Can you send the
entire log please ?
I don't have matroxfb and there aren't 2
Hi...
I have a problem with nfs. It always worked, so I don't know what is
failing now.
I have a server running 2.6.11-rc3-mm2. I try to export a dir via nfs:
/etc/exports:
/raid belly.cps.unizar.es(ro,insecure,no_root_squash,no_subtree_check)
nada:/proc/fs/nfs# exportfs -v
/raid
On Thu, Mar 03, 2005 at 11:51:42PM +, Alan Cox wrote:
-ac is essentially base security fixes + working IDE locking + pwc +
fixes for the bugs everyone hit that needed fixing urgently. I consider
working locking on my storage essential because I like my data to still
be there.
Working IDE
Dave Jones ([EMAIL PROTECTED]) said:
[*] I don't know any details of the /proc incompatibility which davej
mentions, and I'd like to. That sounds like a screw-up.
We changed the format of /proc/slabinfo. Running slabtop threw up
an error message complaining that the format had
On Wed, Mar 02, 2005 at 10:57:10AM +0100, Domen Puncer wrote:
A new release from kernel janitors (http://janitor.kernelnewbies.org/).
Apologies to janitors that this took so long.
This time we have a new record: 354 patches!
I'll start sending/resending what's not already in -mm soon.
In article [EMAIL PROTECTED],
Miquel van Smoorenburg [EMAIL PROTECTED] wrote:
In article [EMAIL PROTECTED],
Miquel van Smoorenburg [EMAIL PROTECTED] wrote:
I just upgrades one of our newsservers from 2.6.9 to 2.6.11. I
use iostat -k -x 2 to see live how busy the disks are. But
I don't believe that
Here's another series of patches that applies on top of the fixes I
posted yesterday. This series syncs the kernel with everything ready
for merging from the OpenIB subversion tree.
Most of these patches add more support for mem-free mode to mthca.
This allows PCI Express HCAs to operate by
On Thursday 03 March 2005 16:58, Alexander Nyberg wrote:
Hi!
I had accidently chosen CONFIG_PNP and noticed that my keyboard didn't
work with bk-dtor-input.patch in the tree (backing out makes keyboard
work).
Hi,
It looks like some old stuff in my tree overwrites good stuff from
Jeff Are you concerned about ordering, or write-combining?
ordering... write combining would be fine.
Jeff I am unaware of a situation where writes are re-ordered into
Jeff a reversed, descending order for no apparent reason.
Hmm... I've seen ppc64 do some pretty freaky reordering
Jeff don't add casts to a void pointer, that's silly.
Fair enough...
Jeff dumb question... why is the lock dropped? is it just for
Jeff the send_handler(), or also for wr_id assigned, kfree, and
Jeff wake_up() ?
Not sure... Sean?
- R.
-
To unsubscribe from this list: send the
Nish Aravamudan wrote:
On Thu, 03 Mar 2005 13:51:40 +0100, Pierre Ossman [EMAIL PROTECTED] wrote:
I just upgraded to Linux 2.6.11 and the soundcard on my machine went
silent. All volume controls are correct and there are no errors
reported. But no sound coming from the speakers. And here's the
Roland Dreier wrote:
+void cancel_sends(void *data)
+{
+struct ib_mad_agent_private *mad_agent_priv;
+struct ib_mad_send_wr_private *mad_send_wr;
+struct ib_mad_send_wc mad_send_wc;
+unsigned long flags;
+
+mad_agent_priv = (struct ib_mad_agent_private *)data;
don't
Roland Dreier wrote:
@@ -783,6 +777,11 @@
cq-cqn (dev-limits.num_cqs - 1));
spin_unlock_irq(dev-cq_table.lock);
+ if (dev-mthca_flags MTHCA_FLAG_MSI_X)
+ synchronize_irq(dev-eq_table.eq[MTHCA_EQ_COMP].msi_x_vector);
+ else
+ synchronize_irq(dev-pdev-irq);
+
Tangent: I think we need
Andrew Morton wrote:
Mark Canter [EMAIL PROTECTED] wrote:
To close this issue out of the LKML and alsa-devel, a bug report has been
written.
It appears to be an issue with the 'headphone jack sense' (as kde labels
it). The issue is in the way the 8x0 addresses the docking station/port
don't add casts to a void pointer, that's silly.
How should we handle this nit? Should I post a new version of this
patch or an incremental diff that fixes it up?
- R.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
Roland Dreier wrote:
Jeff Are you concerned about ordering, or write-combining?
ordering... write combining would be fine.
Jeff I am unaware of a situation where writes are re-ordered into
Jeff a reversed, descending order for no apparent reason.
Hmm... I've seen ppc64 do some pretty
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
--- linux-2.6.11-rc5-mm1-full/kernel/panic.c.old2005-03-04
00:54:46.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/panic.c2005-03-04 00:54:54.0
+0100
@@ -24,8 +24,6 @@
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
--- linux-2.6.11-rc5-mm1-full/kernel/resource.c.old 2005-03-04
01:01:30.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/resource.c 2005-03-04 01:01:42.0
+0100
@@ -371,8 +371,6
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
--- linux-2.6.11-rc5-mm1-full/kernel/sched.c.old2005-03-04
01:06:21.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/sched.c2005-03-04 01:06:36.0
+0100
@@ -3387,8
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
--- linux-2.6.11-rc5-mm1-full/kernel/printk.c.old 2005-03-04
00:58:16.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/printk.c 2005-03-04 00:58:22.0
+0100
@@ -675,7 +675,6
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
--- linux-2.6.11-rc5-mm1-full/kernel/sched.c.old2005-03-04
01:04:28.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/sched.c2005-03-04 01:04:34.0
+0100
@@ -3053,7
On Thu, Mar 03, 2005 at 07:35:00PM -0500, Jeff Garzik wrote:
Roland Dreier wrote:
@@ -783,6 +777,11 @@
cq-cqn (dev-limits.num_cqs - 1));
spin_unlock_irq(dev-cq_table.lock);
+if (dev-mthca_flags MTHCA_FLAG_MSI_X)
+
Greg Sure, I have no problem accepting that into the pci core.
What would pci_irq_sync() do exactly?
- R.
-
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
Roland Dreier [EMAIL PROTECTED] wrote:
don't add casts to a void pointer, that's silly.
How should we handle this nit? Should I post a new version of this
patch or an incremental diff that fixes it up?
I'll fix it up.
-
To unsubscribe from this list: send the line unsubscribe
Andrew Morton [EMAIL PROTECTED] wrote:
Roland Dreier [EMAIL PROTECTED] wrote:
don't add casts to a void pointer, that's silly.
How should we handle this nit? Should I post a new version of this
patch or an incremental diff that fixes it up?
I'll fix it up.
Actually,
Willy Tarreau [EMAIL PROTECTED] writes:
On Wed, Mar 02, 2005 at 02:00:30PM -0800, Philippe Troin wrote:
+ /* Asus K8V Se Deluxe bugfix. Correct VPD content */
+ /* MBo April 2004 */
+ if( ((unsigned char)pAC-vpd.vpd_buf[0x3f] == 0x38)
+ ((unsigned
Lee Revell [EMAIL PROTECTED] wrote:
AFAICT this code is equivalent and cleans up the (efi_)set_rtc_mmss code
referred to as horrible... FIXME in the comments. Completely
untested.
Signed-Off-By: Lee Revell [EMAIL PROTECTED]
--- linux-2.6.11-rc4/arch/i386/kernel/time.c.orig
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
--- linux-2.6.11-rc5-mm1-full/kernel/kallsyms.c.old 2005-03-04
00:49:34.0 +0100
+++ linux-2.6.11-rc5-mm1-full/kernel/kallsyms.c 2005-03-04 00:49:49.0
+0100
@@ -408,4 +408,3
I didn't find any possible modular usage in the kernel.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
--- linux-2.6.11-rc5-mm1-full/kernel/sys.c.old 2005-03-04 01:19:18.0
+0100
+++ linux-2.6.11-rc5-mm1-full/kernel/sys.c 2005-03-04 01:19:29.0
+0100
@@ -1382,8 +1382,6 @@
Hi,
after my external USB hdd disconnected itself reiser4 paniced. I dont think a
journalingfs should panic if its device fails..
Log:
scsi2 (0:0): rejecting I/O to dead device
reiser4[ktxnmgrd:dm-0:t(25324)]: reiser4_handle_error
(fs/reiser4/vfs_ops.c:1315)[foobar-42]:
reiser4 panicked
Hi,
I have a reiser4 partition on a local IDE disk. I opened a 130MB textfile with
kwrite, and killed it while ot opened the file (took to long...) diskio was
finished at this point.
a [ent:hda6.] Process was eating 100% CPU time for several (54) seconds.
Is this a normal, expected behaviour?
On Thu, 2005-03-03 at 16:45 -0800, Andrew Morton wrote:
If efi_enabled is true and efi_set_rtc_mmss(xtime.tv_sec) returns zero, the
new code will run set_rtc_mmss(xtime.tv_sec) whereas the old code won't.
Argh, I should know better then to send patches before having coffee.
Here's a new patch.
Andrew Morton [EMAIL PROTECTED] wrote:
Andrew Morton [EMAIL PROTECTED] wrote:
Roland Dreier [EMAIL PROTECTED] wrote:
don't add casts to a void pointer, that's silly.
How should we handle this nit? Should I post a new version of this
patch or an incremental diff that
On Gwe, 2005-03-04 at 00:19, CaT wrote:
Working IDE locking? Does this mean if I have 2 promise cards, a HD
on each card and I copy from one to the other it wont all blow up in my
face?
Depends on your PCI bus and also if the are on the same IRQ. In the same
IRQ case you may find 2.6.11 is a
@@ -783,6 +777,11 @@
cq-cqn (dev-limits.num_cqs - 1));
spin_unlock_irq(dev-cq_table.lock);
+if (dev-mthca_flags MTHCA_FLAG_MSI_X)
+ synchronize_irq(dev-eq_table.eq[MTHCA_EQ_COMP].msi_x_vector);
+ else
+
Jeff Well, we don't just add code to hope and pray for an event
Jeff that nobody is sure can even occur...
The hardware requires that if the record is written in two 32-bit
chunks, then they must be written in order. Of course the hardware
probably won't be reading just as we're writing,
On Mar 03, 2005, at 14:35, Sean wrote:
Wait a second though, this tree will be branched from the development
mainline. So it will contain many patches that entered with less
testing. What will be the policy for dealing with regressions
relative
to the previous $sucker release caused by huge
Linus Torvalds [EMAIL PROTECTED] wrote:
Now, I haven't actually gotten any complaints about 2.6.11 (apart from
gcc4 still has problems with fairly trivial solutions)
There have been quite a few. Mainly driver stuff again:
Subject: Re: [BUG] 2.4.27 - 2.4.29 tar: /dev/nst0: Warning: Cannot
Mem-free mode requires the driver to allocate additional doorbell pages
for each user access region. Add support for this in mthca_memfree.c,
and have the driver allocate a table in db_tab for kernel use.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
---
Add code to initialize EQ context properly in both Tavor and mem-free mode.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
--- linux-export.orig/drivers/infiniband/hw/mthca/mthca_eq.c2005-03-03
14:12:56.154732247 -0800
+++ linux-export/drivers/infiniband/hw/mthca/mthca_eq.c 2005-03-03
Simplify some of the code for CQ handling slightly.
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
--- linux-export.orig/drivers/infiniband/hw/mthca/mthca_cq.c2005-03-03
14:12:52.923433653 -0800
+++ linux-export/drivers/infiniband/hw/mthca/mthca_cq.c 2005-03-03
14:12:53.538300187 -0800
@@
Roland Dreier wrote:
Add a mthca_write_db_rec() to wrap writing doorbell records. On
64-bit archs, this is just a 64-bit write, while on 32-bit archs it
splits the write into two 32-bit writes with a memory barrier to make
sure the two halves of the record are written in the correct order.
thanks Ganesh Brice! Now it works!
i use the driver specified by ganesh at sourceforge.
thanks.
On Wed, 2 Mar 2005 05:19:02 -0800, Ganesh Venkatesan
[EMAIL PROTECTED] wrote:
Did you try e100? What kernel are you using? You could download the
latest e100 from
On Fri, Mar 04, 2005 at 12:44:04AM +, Alan Cox wrote:
On Gwe, 2005-03-04 at 00:19, CaT wrote:
Working IDE locking? Does this mean if I have 2 promise cards, a HD
on each card and I copy from one to the other it wont all blow up in my
face?
Depends on your PCI bus and also if the are
On Iau, 2005-03-03 at 23:17, Andrew Morton wrote:
Ideally, the 2.6.x.y maintainer wouldn't need any particular kernel
development skills - it's just patchmonkeying the things which maintainers
send him.
I would disagree, and I suspect anyone else who has maintained a distro
stable kernel would
On Thu, 2005-03-03 at 15:28 -0800, Andrew Morton wrote:
Subject: [Bugme-new] [Bug 4282] New: ALSA driver in Linux 2.6.11 causes a
kernel panic when loading the EMU10K1 driver
Um... this one is highly suspect. Myself and others have been doing a
lot of work on this driver lately, and have
. ya, 110,5 2, 5 oa, 1 ocoa, c/ye, oyoa oo oa,
cocoe xopoee.
oo cooa o pooco+oc+ca. cyapey oao a
e cpo.
Beea epe, 2 e., ee.
200 ye/m2 o.
T 7787823 Aecap
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
From: Michael S. Tsirkin [EMAIL PROTECTED]
Clean up CQ code so that we only calculate the address of a CQ entry
once when using it.
Signed-off-by: Michael S. Tsirkin [EMAIL PROTECTED]
Signed-off-by: Roland Dreier [EMAIL PROTECTED]
--- linux-export.orig/drivers/infiniband/hw/mthca/mthca_cq.c
[EMAIL PROTECTED] (Olof Johansson) wrote:
Here's a patch that will work for both PPC and PPC64. The proper way to
fix this in mainline is to merge -mm's cpu_has_feature patch, but for
the stable 2.6.11-series, this much less intrusive (i.e. just the pure
bugfix, not the cleanup part).
901 - 1000 of 1028 matches
Mail list logo
