Hi,
Jeff Garzik wrote:
diff -uprN linux-2.6.11-rc5-bk2/drivers/net/amd8111e.c
linux-2.6.11-rc5-bk2-pi/drivers/net/amd8111e.c
--- linux-2.6.11-rc5-bk2/drivers/net/amd8111e.c2005-02-28
13:44:46.0 +0100
+++ linux-2.6.11-rc5-bk2-pi/drivers/net/amd8111e.c2005-02-28
13:45:09.0
On Tue, Mar 01, 2005 at 11:52:44PM +, Alan Cox wrote:
> On Llu, 2005-02-28 at 19:20, Andries Brouwer wrote:
> > One such case is the mtrr code, where struct mtrr_ops has an
> > init field pointing at __init functions. Unless I overlook
> > something, this case may be easy to settle, since the
On Tue, 2005-03-01 at 10:06 -0800, Jay Lan wrote:
> Sorry I was not clear on my point.
>
> I was trying to point out that, an exit hook for BSD and CSA is
> essential to save accounting data before the data is gone. That
> can not be done with a netlink.
>
> So, my patch was to keep acct_process
On Tue, 2005-03-01 at 23:11 -0800, Greg KH wrote:
> You really don't want -2 for the file mode in sysfs. It creates:
> -rwsrwsrwT 1 root root 4096 Mar 1 22:59
> /sys/module/radeonfb/parameters/default_dynclk
>
> on my box. Here's a fix against a clean 2.6.11-rc5 kernel, please
> forward
You really don't want -2 for the file mode in sysfs. It creates:
-rwsrwsrwT 1 root root 4096 Mar 1 22:59
/sys/module/radeonfb/parameters/default_dynclk
on my box. Here's a fix against a clean 2.6.11-rc5 kernel, please
forward onward as you see fit.
Signed-off-by: Greg Kroah-Hartman
hello all the gurus out there,
i have written simple Target for SCSI device. its in very early stage.
I started to handle simple commands from the INITIATOR like INQUIRY,
READ CAPACITY , REPORT LUN.
Now i am upto READ and WRITE. I have responded READ properly. Problem
is in WRITE command. For
Adrian Bunk wrote:
+ select CRYPTO
select CRYPTO_AES
---help---
Include software based cipher suites in support of IEEE 802.11i
(aka TGi, WPA, WPA2, WPA-PSK, etc.) for use with CCMP enabled
networks.
@@ -54,10 +55,11 @@
"ieee80211_crypt_ccmp".
config IEEE80211_CRYPT_TKIP
On Mar 01, 2005 21:34 -0800, Junfeng Yang wrote:
> I tried to read from a regular ext3 file opened as O_DIRECT, but got the
> "Invalid argument" error. Running the same test program on a block device
> succeeded.
ext3 doesn't support the direct_IO method in 2.4 kernels, though there
was a patch
If I had to guess, I would try the attached patch. The via82cxxx.c
driver is a bit annoying in that, here we do not talk to the ISA bridge
but to the PCI device 0x4149 itself.
If this doesn't work, I could probably whip together a quick PATA driver
for libata that works on this hardware.
Panagiotis Issaris wrote:
Hi,
It seems to me that in the VIA Rhine device driver the requested irq might
not be freed in case the alloc_ring() function fails. alloc_ring()
can fail with a ENOMEM return value because of possible
pci_alloc_consistent() failures.
This patch applies to 2.6.11-rc5-bk2.
Panagiotis Issaris wrote:
Hi,
It seems to me that if in the amd8111e_open() fuction dev->irq isn't
zero and the irq request succeeds it might not get released anymore.
Specifically, on failure of the amd8111e_restart() call the function
returns -ENOMEM without releasing the irq. The
Hello,
1) I want to know how much can i write to
/proc entry file?? Is there any limitation on file
size???
2)Also how can i call /proc entry files
proc_read_myfile function on that file by another
kernel module call? What parameters i require to pass
and how? Say i have read
Linas Vepstas wrote:
>> I'd prefer to see it as ioerr_clear(), ioerr_read() ...
>
> I'd prefer pci_io_start() and pci_io_check_err()
>
> The names should have "pci" in them.
>
> I don't like "ioerr_clear" because it implies we are clearing the io error; we are not; we are clearing the checker
for
Bartlomiej Zolnierkiewicz wrote:
Yes but it seems that you've assumed that ioctl == flagged taskfile
and fs/internal == normal taskfile which is _not_ what I aim for.
I want fully-flagged taskfile handling like flagged_taskfile() and "hot path"
simpler taskfile handling like do_rw_taskfile() (at
Bartlomiej Zolnierkiewicz wrote:
If somebody implements SG_IO ioctl and SCSI command pass-through
from libata for IDE driver (and add possibility for discrete taskfiles), we can
just deprecate HDIO_DRIVE_TASKFILE, forget about it and some time later
remove this FPOS.
Can you explain what you mean
Hi everybody, I just joined the LKML!
Don't worry, this is not just a test message, I do actually have
something to say. I just compiled 2.6.11-rc5-mm1 and got undefined
symbols "match_int", "match_octal", "match_token", and "match_strdup" in
several modules. This is using binutils 2.15 and gcc
Hi,
I tried to read from a regular ext3 file opened as O_DIRECT, but got the
"Invalid argument" error. Running the same test program on a block device
succeeded.
uname -a shows
Linux *** 2.4.27-2-686-smp #1 SMP Thu Jan 20 11:02:39 JST 2005 i686
GNU/Linux
My test case is
#include
#include
aoeblk: mac_addr() returns u64, coerce to unsigned long long to printk it:
(sparc64 build warning)
drivers/block/aoe/aoeblk.c:245: warning: long long unsigned int format, u64 arg
(arg 2)
drivers/block/aoe/aoeblk.c:31: warning: long long unsigned int format, u64 arg
(arg 4)
cross-compile
I can't use sockfd_put(sock) directly.
I trace its code, the code is
extern __inline__ void sockfd_put(struct socket *sock)
{
fput(sock->file);
}
so I use fput(sock->file)
but it has problems too
1) execute "ls" in the ftp is also block
2) kernel prints "socki_lookup: socket file
On Fri, Feb 18, 2005 at 12:05:52PM -0800, Greg KH wrote:
> On Fri, Feb 18, 2005 at 07:46:28PM +, Christoph Hellwig wrote:
> > > /*
> > > + * sysfs stuff
> > > + * this should be moved to it's own file, maybe cciss_sysfs.h
> > > + */
> > > +
> > > +static ssize_t cciss_firmver_show(struct
This way we actually share dentries before inodes and thus mark more
inodes reclaimable once we shake them.
--- 1.240/mm/vmscan.c 2005-02-04 01:53:32 +01:00
+++ edited/mm/vmscan.c 2005-03-02 07:09:00 +01:00
@@ -137,7 +137,7 @@ struct shrinker *set_shrinker(int seeks,
On Wed, 2005-03-02 at 13:27 +1000, Jarne Cook wrote:
>On Tuesday 01 March 2005 12:35, you wrote:
>> On Monday 28 February 2005 21:02, [EMAIL PROTECTED] wrote:
>> > On Mon, 28 Feb 2005 14:59:31 +1000, Jarne Cook said:
>> > > They are both using dhcp to the same simple network. That's right.
>> >
Just a thought - perhaps you could see if Jay can test the performance
scaling of these changes on larger systems (8 to 64 CPUs, give or take,
small for SGI, but big for some vendors.)
Things like a global lock, for example, might be harmless on smaller
systems, but hurt big time on bigger
The page fault handler attempts to use the page_table_lock only for short
time periods. It repeatedly drops and reacquires the lock. When the lock
is reacquired, checks are made if the underlying pte has changed before
replacing the pte value. These locations are a good fit for the use of
Do not use the page_table_lock in do_anonymous_page. This will significantly
increase the parallelism in the page fault handler in SMP systems. The patch
also modifies the definitions of _mm_counter functions so that rss and anon_rss
become atomic.
Signed-off-by: Christoph Lameter <[EMAIL
This patch extracts all the operations on rss into definitions in
include/linux/sched.h. All rss operations are performed through
the following three macros:
get_mm_counter(mm, member) -> Obtain the value of a counter
set_mm_counter(mm, member, value) -> Set the value of a
The current way of updating ptes in the Linux vm includes first clearing
a pte before setting it to another value. The clearing is performed while
holding the page_table_lock to insure that the entry will not be modified
by the CPU directly (clearing the pte clears the present bit),
by an arch
Is there any chance that this patchset could go into mm now? This has been
discussed since last August
Changelog:
V17->V18 Rediff against 2.6.11-rc5-bk4
V16->V17 Do not increment page_count in do_wp_page. Performance data
posted.
V15->V16 of this patch: Redesign to allow full
On Mar 01, 2005, at 22:27, Jarne Cook wrote:
Damn
Having to configure the interfaces using bonding was not really the
answer I
was expecting.
I did not think linux would be that rigid. I figured if poodoze is
able to do
it (seamlessly mind you), surely linux (with some tinkering) would be
On Tuesday 01 March 2005 12:35, you wrote:
> On Monday 28 February 2005 21:02, [EMAIL PROTECTED] wrote:
> > On Mon, 28 Feb 2005 14:59:31 +1000, Jarne Cook said:
> > > They are both using dhcp to the same simple network. That's right.
> > > Same network. They both end up with
On Wed, 02 Mar 2005 01:02:50 +, Baruch Even wrote:
> > Might this be related to the broken BicTCP implementations in the 2.6.6+
> > kernels? A fix was added around 2.6.11-rc3 or 4.
>
> Unlikely, the problem with BIC would have shown itself only at high
> speeds over long latency links, not
On Tuesday 01 March 2005 12:35, you wrote:
> On Monday 28 February 2005 21:02, [EMAIL PROTECTED] wrote:
> > On Mon, 28 Feb 2005 14:59:31 +1000, Jarne Cook said:
> > > They are both using dhcp to the same simple network. That's right.
> > > Same network. They both end up with
Jesse Barnes wrote:
This was my thought too last time we had this discussion. A completely
asynchronous call is probably needed in addition to Hidetoshi's proposed API,
since as you point out, the driver may not be running when an error occurs
(e.g. in the case of a DMA error or more general
On Tue, 1 Mar 2005, Nathan Lynch wrote:
> On Sun, Feb 27, 2005 at 02:49:28PM -0800, Andrew Morton wrote:
> > Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> > >
> > > > - if (cpu_is_offline(smp_processor_id()) &&
> > > > + if (cpu_is_offline(_smp_processor_id()) &&
On Tue, 2005-03-01 at 18:03 -0800, Todd Poynor wrote:
> Advertise custom sets of system power states for non-ACPI systems.
> Currently, /sys/power/state shows and accepts a static set of choices
> that are not necessarily meaningful on all platforms (for example,
> suspend-to-disk is an option
An example of custom power states for the TI OMAP family.
/sys/power/states supports a state named "deepsleep", which corresponds
to the platform state actually entered by the present-day system suspend
handler. It no longer offers the option of "disk" suspend which would
not normally be
A minor update, mostly to update to the latest kernel.
BK users:
bk pull bk://gkernel.bkbits.net/libata-dev-2.6
Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
This will update the following files:
drivers/scsi/Kconfig |
Matthew Wilcox wrote:
I think what Jeff meant was "this new API handles none of this".
And that's true, it doesn't handle DMA errors. But I think that's just
something that hasn't been written/designed yet.
Yes, this API just supports drivers wanting to be more RAS-aware.
It would be happy if how
Advertise custom sets of system power states for non-ACPI systems.
Currently, /sys/power/state shows and accepts a static set of choices
that are not necessarily meaningful on all platforms (for example,
suspend-to-disk is an option even on diskless embedded systems, and the
meaning of standby vs.
On Sun, Feb 27, 2005 at 02:49:28PM -0800, Andrew Morton wrote:
> Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> >
> > > - if (cpu_is_offline(smp_processor_id()) &&
> > > +if (cpu_is_offline(_smp_processor_id()) &&
> > > system_state ==
This patch fixes a kernel crashing bug when using NAT. The crash occurs in
the case when we send out a UDP packet to a closed port on another host,
with the UDP packet being SNATed. The remote host replies with an ICMP
port unreachable (type 3, code 3). We need to adjust the ICMP packet,
Hi,
I wish to be personally CC'ed the answers/comments posted to the list in
response to this post
I have done some reading about system calls and memory management but some
issues are not yet that clear for me, so I hope some of you will assist
me...
PART1
--
Assume within a C user
I got this right after the initramfs script was finished and the root
filesystem was mounted:
Unable to handle kernel NULL pointer dereference at virtual address
printing eip:
c02f52fa
*pde =
Oops: 0002 [#1]
PREEMPT
Modules linked in:
CPU:0
EIP:0060:[]Not tainted
A while back someone complained about the CVS exporter because it
sometimes groups a pile of BK changesets into one commit. That's true,
it does.
I've been running tests over the BK tree and I think we can do better.
Here's the scoop: when we do an export we are going from a very bushy
graph
Paul Dickson wrote:
On Tue, 1 Mar 2005 14:29:24 -0500 (EST), linux-os wrote:
Intel NIC e100 device driver. Two identical machines.
Private network, no other devices. Connected using a Netgear switch.
Test data is the same thing sent from memory on one machine
to a discard server on another, using
On Tue, 1 Mar 2005 14:29:24 -0500 (EST), linux-os wrote:
> Intel NIC e100 device driver. Two identical machines.
> Private network, no other devices. Connected using a Netgear switch.
> Test data is the same thing sent from memory on one machine
> to a discard server on another, using TCP/IP
Corey Minyard wrote:
Nick Piggin wrote:
Is get_with_check actually going to be useful for anything? It
seems like it promotes complex and potentially unsafe schemes.
It is certainly more complex to use this, and I'm guessing that's why
Greg rejected it. Certainly a valid problem.
eg. In your
Nick Piggin wrote:
Corey Minyard wrote:
Arjan van de Ven wrote:
Just doing an atomic operation is not faster than doing a lock, an
atomic operation, then an unlock? Am I missing something?
if the lock and the atomic are on the same cacheline they're the same
cost on most modern cpus...
count is size_t, fill_write_buffer() may return a negative number
which would evade the 'count > 0' checks and do bad things.
found by the Coverity tool
Signed-off-by: Alexander Nyberg <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
--- 1.22/fs/sysfs/file.c
Corey Minyard wrote:
Arjan van de Ven wrote:
Just doing an atomic operation is not faster than doing a lock, an
atomic operation, then an unlock? Am I missing something?
if the lock and the atomic are on the same cacheline they're the same
cost on most modern cpus...
Ah, I see. Not
On Llu, 2005-02-28 at 19:20, Andries Brouwer wrote:
> One such case is the mtrr code, where struct mtrr_ops has an
> init field pointing at __init functions. Unless I overlook
> something, this case may be easy to settle, since the .init
> field is never used.
The failure to invoke the ->init
Bernd Schubert <[EMAIL PROTECTED]> writes:
> Hmm, after compiling with -D_FILE_OFFSET_BITS=64 it works fine. But why does
> it work without this option on a 32bit kernel, but not on a 64bit kernel?
See nfs_fileid_to_ino_t for why the inode number is different between
32bit and 64bit kernels.
The current reiser4 help texts have two disadvantages:
1. they are more marketing speech than technical speech with
some debatable statements
2. they are too long
Examples for what I call "debatable statements":
ReiserFS V3 is the stablest Linux filesystem, and V4 is the fastest.
Bernd Schubert <[EMAIL PROTECTED]> writes:
> Hmm, after compiling with -D_FILE_OFFSET_BITS=64 it works fine. But why does
> it work without this option on a 32bit kernel, but not on a 64bit kernel?
Most likely the inode number (which is the only non-filesize related item
that is different
Hi!
> > > Relocating pagedir |
> > > Reading image data (8157 pages): 100% 8157 done.
> > > Stopping tasks: |
> > > Freeing memory... done (0 pages freed)
> > > Freezing CPUs (at 1)...Sleeping in:
> > > [] dump_stack+0x19/0x20
> > > [] smp_pause+0x1f/0x54
>
On 03.01, Joerg Sommrey wrote:
> Hi all,
>
> a problem that was introduced between 2.6.10-ac9 and 2.6.10-ac11 made
> it's way into 2.6.11-rc5. While taking a backup onto a SCSI-streamer one
> of my RAID1-arrays gets corrupted. Afterwards the system hangs and
> isn't even bootable. Need to
On Wed, Mar 02, 2005 at 12:09:46AM +0100, Karol Kozimor wrote:
> I've finally got around to test latest kernels and managed to find a bug in
> the serial subsystem, which happens during suspend.
Yes, serial_cs is claiming that we don't have a device associated with
the port, so we're treating it
Arjan van de Ven wrote:
Just doing an atomic operation is not faster than doing a lock, an
atomic operation, then an unlock? Am I missing something?
if the lock and the atomic are on the same cacheline they're the same
cost on most modern cpus...
Ah, I see. Not likely to ever be the
Hi!
> Hmm, maybe I should change the vesafb test in the bootsplash code
> to test if fb_imageblit == cfb_imageblit. This would make Pavel
> very happy, I guess ;-)
Yes, I like that one. Also it is likely going to be cleaner than
vesafb_ops hack.
On Sad, 2005-02-26 at 21:50, [EMAIL PROTECTED] wrote:
> arch/i386/kernel/cpu/mtrr/cyrix.c has a routine cyrix_arr_init(), and
> arch/i386/kernel/cpu/mtrr/centaur.c has a routine centaur_mcr_init().
> At first sight it looks like these are unused.
> Do I overlook something?
>
> (They occur as the
Andi Kleen <[EMAIL PROTECTED]> writes:
> On Tue, Mar 01, 2005 at 11:10:38PM +0100, Andreas Schwab wrote:
>> That's because there are some values in the stat64 buffer delivered by the
>> kernel which cannot be packed into the stat buffer that you pass to stat.
>> Use stat64 or
On Tuesday 01 March 2005 23:10, Andreas Schwab wrote:
> Bernd Schubert <[EMAIL PROTECTED]> writes:
> >> It is most likely some kind of user space problem. I would change
> >> it to int err = stat(dir, );
> >> and then go through it with gdb and see what value err gets assigned.
> >>
> >> I cannot
Hi,
I've finally got around to test latest kernels and managed to find a bug in
the serial subsystem, which happens during suspend.
I use a 3Com PC Card Bluetooth adapter that needs serial_cs and hci_uart
modules. Whenever I try to suspend using 2.6.10 or a newer kernel, the
following bug
> stat64("/mnt/test/yp", {st_mode=S_IFDIR|0755, st_size=2704, ...}) = 0
It returns 0. No error. Someone else in user space must be adding the
EOVERFLOW.
glibc code does quite a lot of strange things with stat, perhaps
it comes from there.
> write(2, "err = -1\n", 9err = -1
> ) =
On Tue, 01 Mar 2005 16:26:05 -0300
Horst von Brand <[EMAIL PROTECTED]> wrote:
> Right. But where? I was thinking under arch/sparc64/drivers/floppy.S or
> such. And then there would need to be some make magic for it to get picked
> up and included only for sparc64. Sounds doable, if somewhat
> In fact, I'd argue that even a driver that _uses_ the interface should not
> necessarily shut itself down on error. Obviously, it should always log the
> error, but outside of that it might be good if the operator can decide and
> set a flag whether it should try to re-try (which may not always
> strace didn't say so, and normally it doesn't lie about things like this.
Well, I show you the updated source code and strace output and if you still
don't believe me, ask me for a login to our system ;)
#include
#include
#include
#include
#include
#include
#include
int main(int
On 03/01/05 17:17, Christoph Hellwig wrote:
Doing it in the core means less duplication and avoiding updating
all drivers.
I agree.
Luben
-
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 Tue, 2005-03-01 at 12:33 -0600, Linas Vepstas wrote:
> The current proposal (and prototype) has a "master recovery thread"
> to handle the coordinated reset of the pci controller. This master
> recovery thyread makes three calls in struct pci_driver:
>
>void (*frozen) (struct pci_dev *);
On Tue, 2005-03-01 at 18:19 +0100, Andi Kleen wrote:
> Hidetoshi Seto <[EMAIL PROTECTED]> writes:
>
> >
> > int sample_read_with_iochk(struct pci_dev *dev, u32 *buf, int words)
> > {
> > unsigned long ofs = pci_resource_start(dev, 0) + DATA_OFFSET;
> > int i;
> >
> > /* Create magical
On Tue, 2005-03-01 at 09:10 -0800, Jesse Barnes wrote:
> On Tuesday, March 1, 2005 8:59 am, Matthew Wilcox wrote:
> > The MCA handler has to go and figure out what the hell just happened
> > (was it a DIMM error, PCI bus error, etc). OK, fine, it finds that it
> > was an error on PCI bus 73. At
On Tue, 2005-03-01 at 08:49 -0800, Linus Torvalds wrote:
>
> On Tue, 1 Mar 2005, Jeff Garzik wrote:
> >
> > A new API handles none of this.
>
> Ehh?
>
> The new API is what _allows_ a driver to care. It doesn't handle DMA, but
> I think that's because nobody knows how to handle it (ie it's
On Tue, Mar 01, 2005 at 11:10:38PM +0100, Andreas Schwab wrote:
> That's because there are some values in the stat64 buffer delivered by the
> kernel which cannot be packed into the stat buffer that you pass to stat.
> Use stat64 or _FILE_OFFSET_BITS=64.
If that had been the case strace would
> I have been thinking about PCI system and parity errors, and how to
> handle them. I do not think this is the correct approach.
>
> A simple retry is... too simple. If you are having a massive problem on
> your PCI bus, more action should be taken than a retry.
It goes beyond that, see
On Tue, Mar 01, 2005 at 09:40:48AM -0500, Luben Tuikov wrote:
> On 03/01/05 03:14, Douglas Gilbert wrote:
> >> - scsi_error.c: scsi_normalize_sense
> >
> >
> >I introduced scsi_normalize_sense() recently, Christoph H.
> >proposed it should be static but Luben Tuikov (aic7xxx
> >maintainer) said
> Just doing an atomic operation is not faster than doing a lock, an
> atomic operation, then an unlock? Am I missing something?
if the lock and the atomic are on the same cacheline they're the same
cost on most modern cpus...
-
To unsubscribe from this list: send the line "unsubscribe
Bernd Schubert <[EMAIL PROTECTED]> writes:
>> It is most likely some kind of user space problem. I would change
>> it to int err = stat(dir, );
>> and then go through it with gdb and see what value err gets assigned.
>>
>> I cannot see any kernel problem.
>
> The err value will become -1 here.
On Tue, 2005-03-01 at 22:23 +0100, Pavel Machek wrote:
> Hi!
>
> > (This is for -mm, to be merged along with the aty128fb and radeonfb
> > related patches).
> >
> > This patch adds suspend/resume support to the Apple UniNorth AGP bridge
> > to make sure AGP is properly disabled when the machine
Chris Wright <[EMAIL PROTECTED]> wrote:
>
> * Andrew Morton ([EMAIL PROTECTED]) wrote:
> > - I seem to be getting a lot of patches which don't compile if you breathe
> > on the .config file, let alone if you try them on another architecture.
> > It
> > would be nice to receive less such
Andrew Morton wrote:
Vivek Goyal <[EMAIL PROTECTED]> wrote:
o Following patch exports kexec global variable "crash_notes" to user space
through sysfs as kernel attribute in /sys/kernel.
It breaks the x86_64 build. A fix for that is below.
Please test kexec/kdump patches on all three
On Tuesday 01 March 2005 22:38, Benjamin Herrenschmidt wrote:
> On Tue, 2005-03-01 at 12:36 +0100, Mws wrote:
> > hi benjamin
> >
> > now i had some spare time to do some investigation
> >
> > booting the 2.6.11-rc5 with radeonfb.default_dynclk=0 or with -1
> > brings up a framebuffer console.
Hi!
> So what it comes down to is
>
> sys_free_node_memory(long node_id, long pages_to_make_free, long what_to_free)
>
> where `what_to_free' consists of a bunch of bitflags (unmapped pagecache,
> mapped pagecache, anonymous memory, slab, ...).
Heh, swsusp needs shrink_all_memory() and I'd
Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> On Tue, Mar 01, 2005 at 01:27:41AM -0800, Andrew Morton wrote:
> >...
> > All 728 patches:
> >...
> > reiser4-rcu-barrier.patch
> > reiser4: add rcu_barrier() synchronization point
>
> Considering the patent situation at least in the USA, the
>
Arjan van de Ven wrote:
On Tue, 2005-03-01 at 12:15 -0800, Greg KH wrote:
On Sat, Feb 26, 2005 at 04:23:04PM -0600, Corey Minyard wrote:
Add a routine to kref that allows the kref_put() routine to be
unserialized even when the get routine attempts to kref_get()
an object without first
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> - I seem to be getting a lot of patches which don't compile if you breathe
> on the .config file, let alone if you try them on another architecture. It
> would be nice to receive less such patches, please.
The ia64 audit bit is likely my fault
On Tue, Mar 01, 2005 at 10:07:01PM +0100, Bernd Schubert wrote:
> Hello Andi,
>
> sorry, due to some mail sending/refusing problems, I had to resend to the
> nfs-list, which prevented the answers there to be posted to the other CCs.
>
> > It is most likely some kind of user space problem. I
Matt Mackall <[EMAIL PROTECTED]> wrote:
>
> I'll queue this
> up for after the sort and ACL stuff gets merged.
Whew!
I don't know how long the ACL changes will take to get merged up - is up to
Trond and he had quite a lot of rather robust comments on the first
iteration.
-
To unsubscribe from
On Tue, 2005-03-01 at 12:36 +0100, Mws wrote:
> hi benjamin
>
> now i had some spare time to do some investigation
>
> booting the 2.6.11-rc5 with radeonfb.default_dynclk=0 or with -1
> brings up a framebuffer console. everything is fine.
> starting xorg-x11 with Ati binary only drivers just
Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
>
> Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
Thanks. Many of these fixups are due to a 64-bit-resource patch in Greg's
bk-pci tree which he has now reverted. That being said:
- That patch will come back sometime
- Fixes like the below make
On Tue, Mar 01, 2005 at 10:02:43PM +0100, Arjan van de Ven wrote:
> On Tue, 2005-03-01 at 12:15 -0800, Greg KH wrote:
> > On Sat, Feb 26, 2005 at 04:23:04PM -0600, Corey Minyard wrote:
> > > Add a routine to kref that allows the kref_put() routine to be
> > > unserialized even when the get routine
Hi!
> (This is for -mm, to be merged along with the aty128fb and radeonfb
> related patches).
>
> This patch adds suspend/resume support to the Apple UniNorth AGP bridge
> to make sure AGP is properly disabled when the machine goes to sleep.
> Without this, the r300 based laptops will fail to
This patch adds the hotplug routine for generating hotplug events when
devices are seen on the macio bus. It uses the attributed created by the
sysfs nodes to generate the hotplug environment vars for userspace.
In order for hotplug to work with macio devices, patches to module-init-tools
and
This patch converts the usage of struct of_match to struct of_device_id,
similar to pci_device_id. This allows a device table to be generated, which
can be parsed by depmod(8) to generate a map file for module loading.
In order for hotplug to work with macio devices, patches to module-init-tools
This patch adds sysfs nodes that the hotplug userspace can use to load the
appropriate modules.
In order for hotplug to work with macio devices, patches to module-init-tools
and hotplug must be applied. Those patches are available at:
ftp://ftp.suse.com/pub/people/jeffm/linux/macio-hotplug/
Hello all -
I posted these patches a while ago, and let them fall by the wayside.
The following 3 patches, combined with the userspace patches referenced below,
implement hotplug events for open firmware/macio devices such as apple airport
wireless ethernet cards.
*
Dear Friend,
My names are Rose Okot Opoka. Im an 18 year old Ugandan girl living in the
northern part. Our village was raided in November 2002 by the rebel group the
lords resistance army . My father was a very wealthy International Coffee
merchant and on that day, he was brutally
A small change to the tests for "Bad page state", to avoid one class of
the page_remove_rmap BUG reports, giving more information while letting
the system continue: check page_mapcount (_mapcount != -1) rather than
page_mapped (_mapcount >= 0).
And how does _mapcount go bad? In the case under
Hello Andi,
sorry, due to some mail sending/refusing problems, I had to resend to the
nfs-list, which prevented the answers there to be posted to the other CCs.
> It is most likely some kind of user space problem. I would change
> it to int err = stat(dir, );
> and then go through it with gdb
On Tue, 2005-03-01 at 12:15 -0800, Greg KH wrote:
> On Sat, Feb 26, 2005 at 04:23:04PM -0600, Corey Minyard wrote:
> > Add a routine to kref that allows the kref_put() routine to be
> > unserialized even when the get routine attempts to kref_get()
> > an object without first holding a valid
On Mon, Feb 28, Antonino A. Daplas wrote:
> On Monday 28 February 2005 04:32, Olaf Hering wrote:
> > On Wed, Feb 23, Linus Torvalds wrote:
> > > This time it's really supposed to be a quickie, so people who can, please
> > > check it out, and we'll make the real 2.6.11 asap.
> >
> > Here is
1 - 100 of 528 matches
Mail list logo
