I have an NForce4 board with an Athlon 64 and use the 2.6.8 kernel from
the inofficial debian AMD64 port, and everything works, except that the
proprietary nvidia driver for my geforce card complains about "Your
Linux kernel has problems in its implementation of the change_page_attr
kernel
On Sun, 14 Aug 2005, James Cleverdon wrote:
> > > +static int next_irq = 16;
> >
> > Won't this need a lock for hotplug later?
>
> That's what I thought originally, but maybe not. We initialize all RTEs
> and assign IRQs+vectors fairly early in boot, plus store the results in
> arrays.
On Mon, Aug 15, 2005 at 01:25:56PM +1000, Dmytro Bablinyuk wrote:
> I hope this is the right place to ask. My apologise if it's wrong.
> I have found 2.4.25-low-latency.patch.gz for the 2.4.25 kernel but I
> couldn't find preemptible patch for this version of kernel.
> I found
diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 12
-EXTRAVERSION = .4
+EXTRAVERSION = .5
NAME=Woozy Numbat
# *DOCUMENTATION*
diff --git a/arch/ppc64/boot/zlib.c b/arch/ppc64/boot/zlib.c
--- a/arch/ppc64/boot/zlib.c
+++
We (the -stable team) are announcing the release of the 2.6.12.5 kernel.
The diffstat and short summary of the fixes are below.
I'll also be replying to this message with a copy of the patch between
2.6.12.4 and 2.6.12.5, as it is small enough to do so.
The updated 2.6.12.y git tree can be
Thanks Sumit, I did it in the same way as ur first solution.
it worked.
On Sun, 14 Aug 2005, sumit kalra wrote:
Hi Manohar,
Yes, you need to put a scripts in /etc/rc.d/init.d
which would invoke your daemon. You should provide
options in this script to start/stop this daemon and
fetch it's
On 8/15/05, Mike Waychison <[EMAIL PROTECTED]> wrote:
> Coywolf Qi Hunt wrote:
> > Hello,
> >
> > Unexport __mntput() was talked about two months ago.
> > http://lkml.org/lkml/2005/6/9/69
> > Modules should not call __mntput() directly. If autofs or nfsd does that,
> > it's
> > being wrong.
>
This version contains minor bug fixes and improvements to the zaphod
scheduler including changes to the default configuration parameters that
take into account the results of tests using Con Kolivas's new (and very
useful) interbench benchmark tool.
A patch from Plugsched-5.2.3 to
> On Thursday 04 August 2005 02:22 am, Andi Kleen wrote:
> > On Thu, Aug 04, 2005 at 12:05:50AM -0700, James Cleverdon wrote:
> > > diff -pruN 2.6.12.3/arch/i386/kernel/acpi/boot.c
> > > n12.3/arch/i386/kernel/acpi/boot.c ---
> > > 2.6.12.3/arch/i386/kernel/acpi/boot.c 2005-07-15
>
Hi Andrew,
The overwrite arg has been removed from the relay_subbufs_consumed()
(since it has been removed from relayfs altogether) so the comment
preceding the function must go.
Thanks,
Hareesh
diff -ruN linux-akpm/fs/relayfs/relay.c linux/fs/relayfs/relay.c
---
> On Thursday 04 August 2005 02:22 am, Andi Kleen wrote:
> > On Thu, Aug 04, 2005 at 12:05:50AM -0700, James Cleverdon wrote:
> > > diff -pruN 2.6.12.3/arch/i386/kernel/acpi/boot.c
> > > n12.3/arch/i386/kernel/acpi/boot.c ---
> > > 2.6.12.3/arch/i386/kernel/acpi/boot.c 2005-07-15
>
Back out Axboe-style quasi-S/G and replace it with one command and
repeated URBs. This is similar to what usb-storage does, only instead
of a few URBs allocated together, one URB is reused.
Jens's idea was very nice, but it collapsed when I had to support
packet commads for CD burning. I cannot
Coywolf Qi Hunt wrote:
Hello,
Unexport __mntput() was talked about two months ago.
http://lkml.org/lkml/2005/6/9/69
Modules should not call __mntput() directly. If autofs or nfsd does that, it's
being wrong.
I think you missed the point in the last discussion. __mntput is called
from
On Mon, 2005-08-15 at 13:25 +1000, Dmytro Bablinyuk wrote:
> I hope this is the right place to ask. My apologise if it's wrong.
> I have found 2.4.25-low-latency.patch.gz for the 2.4.25 kernel but I
> couldn't find preemptible patch for this version of kernel.
> I found
On Sun, 14 Aug 2005, Robert Love wrote:
> On Sun, 2005-08-14 at 20:40 -0600, Zwane Mwaikambo wrote:
>
> > I'm new here, if the inode isn't being watched, what's to stop d_delete
> > from removing the inode before fsnotify_unlink proceeds to use it?
>
> Nothing. But check out
>
>
On Sun, 2005-08-14 at 20:40 -0600, Zwane Mwaikambo wrote:
> I'm new here, if the inode isn't being watched, what's to stop d_delete
> from removing the inode before fsnotify_unlink proceeds to use it?
Nothing. But check out
Quick and dirty patch to use the 16 vectors that appear to have
fallen through the cracks. This also is useful for older CPUs that
have serial APICS: P54C, P6, P2, P3, K5, K6, etc. They can benefit
from the extra vector space to hash the IRQs.
I suppose I could have started at 0x20 instead of
On Thursday 04 August 2005 02:22 am, Andi Kleen wrote:
> On Thu, Aug 04, 2005 at 12:05:50AM -0700, James Cleverdon wrote:
> > diff -pruN 2.6.12.3/arch/i386/kernel/acpi/boot.c
> > n12.3/arch/i386/kernel/acpi/boot.c ---
> > 2.6.12.3/arch/i386/kernel/acpi/boot.c 2005-07-15 14:18:57.0
>
On Sun, 14 Aug 2005, Phil Dier wrote:
> I just got this:
>
> Unable to handle kernel paging request at virtual address eeafefc0
> printing eip:
> c0188487
> *pde = 00681067
> *pte = 2eafe000
> Oops: [#1]
> SMP DEBUG_PAGEALLOC
> Modules linked in:
> CPU:1
> EIP:0060:[]Not
On Sun, 14 Aug 2005, Rafael J. Wysocki wrote:
> I've got the following BUG on Asus L5D (x86-64) with the 2.6.13-rc5-mm1
> kernel:
>
> BUG: rwlock recursion on CPU#0, nscd/3668, 8817d4a0
>
> Call Trace:{add_preempt_count+105}
> {rwlock_bug+114}
>{_raw_write_lock+62}
>
I just got this:
Unable to handle kernel paging request at virtual address eeafefc0
printing eip:
c0188487
*pde = 00681067
*pte = 2eafe000
Oops: [#1]
SMP DEBUG_PAGEALLOC
Modules linked in:
CPU:1
EIP:0060:[]Not tainted VLI
EFLAGS: 00010296 (2.6.13-rc6)
EIP is at
Hello,
Unexport __mntput() was talked about two months ago.
http://lkml.org/lkml/2005/6/9/69
Modules should not call __mntput() directly. If autofs or nfsd does that, it's
being wrong.
Coywolf
Signed-off-by: Coywolf Qi Hunt <[EMAIL PROTECTED]>
---
On Sun, 14 Aug 2005, Pavel Machek wrote:
> > Ok perhaps on the resume side instead. When trying to resume can you try
> > booting with 'dyntick=disable'. Note this isn't meant to be a long term fix
> > but once we figure out where the problem is we should be able to code
> > around
> > it.
>
On Sun, 14 Aug 2005, Lukas Sandström wrote:
>
> The commits 71db63acff69618b3d9d3114bd061938150e146b ([PATCH] increase
> PCIBIOS_MIN_IO on x86) and 0b2bfb4e7ff61f286676867c3508569bea6fbf7a
> (ACPI: increase PCIBIOS_MIN_IO on x86) shortly after -rc5 caused my
> on-board audio to stop working.
On Sun, 14 Aug 2005, Chuck Ebbert wrote:
>
> GCC warns about using llseek and suggests lseek64 instead. That works
> for me, but up till 2.6.11 plain lseek worked too. I guess it really
> shouldn't have?
Well, we have had various special-cases for /dev/[k]mem to try to make it
work even
On Mon, 15 Aug 2005 01:37:08 +0100 Alan Cox wrote:
>
> We certainly could interpret 0x51, 0x04 specifically. Its not an "error"
> in the usual spew at the user case generally speaking but a "do this"
> "no" sequence. Its useful to log because sending unknown commands to an
> IDE device is
On Sun, Aug 14, 2005 at 11:25:25PM +0100, Russell King wrote:
> On Sun, Aug 14, 2005 at 04:02:31PM +0100, Matthew Wilcox wrote:
> > Last time I tried to do something like this, it fell over with
> > multi-function serial ports. Look at this example:
> >
> > # ls -l /sys/class/tty/ttyS*/device |
On Mon, 15 Aug 2005 09:29:20 +1000, Con Kolivas <[EMAIL PROTECTED]> wrote:
> > Remember that dmesg diff you sent? That's the one. If you strace
> > the digikamcameracl, it probably keels over after EBUSY.
>
> Nice shot! Got it in one. bugzilla updated with confirmation.
>
> So how do we proceed
On Llu, 2005-08-15 at 00:51 +0200, Voluspa wrote:
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> ide: failed opcode was: 0xec
> ide: Did you just run "hdparm -I" or do you use a nosy desktop?
We certainly could interpret 0x51,
On Sun, Aug 14, 2005 at 02:33:05PM +0100, Alan Cox wrote:
> What does a full identify data set for the drive look like ?
Here it is for the two drives. Please note that multisect was turned on
manually as well as the security freeze.
/dev/hda:
ATA device, with non-removable media
Model
On Mon, 15 Aug 2005 04:56, Pete Zaitcev wrote:
> On Sun, 14 Aug 2005 18:42:12 +1000, Con Kolivas <[EMAIL PROTECTED]> wrote:
> > On Sun, 14 Aug 2005 18:00, Pete Zaitcev wrote:
> > > On Sun, 14 Aug 2005 17:12:06 +1000, Con Kolivas <[EMAIL PROTECTED]>
> > > wrote:
> >
> > Yes all those dmesgs etc
On Sul, 2005-08-14 at 15:59 -0400, Lee Revell wrote:
> I know the alternatives are available. That doesn't make it any less
> idiotic to use non ASCII characters as operators. I think it's a very
> slippery slope. We write code in ASCII, dammit.
Its a trivial patch and there is a lot to be
Quoting Serge E. Hallyn ([EMAIL PROTECTED])
>Quoting Joshua Hudson ([EMAIL PROTECTED]):
> Why would you want a virtual network device implementation? The whole
>
>So that a jailed process can use the net but can't use your network
>address (intercept ssh, imap/stunnel, etc).
[snip]
>But in the
ALERT!
This e-mail, in its original form, contained one or more attached files that
were infected with a virus, worm, or other type of security threat. This e-mail
was sent from a Road Runner IP address. As part of our continuing initiative to
stop the spread of malicious viruses, Road Runner
On 2005-08-14 20:10:49 Nick Warne wrote:
>Note the last sentence:
>
>' This variation is designed for use with "libraries" of drive
>identification information, and can also be used on ATAPI drives which may
>give media errors with the standard mechanism.
My jaw just clonked on the
On Sun, Aug 14, 2005 at 04:02:31PM +0100, Matthew Wilcox wrote:
> On Sat, Aug 13, 2005 at 02:39:56PM -0700, Greg KH wrote:
> > Heh, I already have a patch like this pending for 2.6.14 at:
> >
> >
On Sun, 14 Aug 2005, James Bottomley wrote:
> On Sun, 2005-08-14 at 21:33 +0200, Guennadi Liakhovetski wrote:
> > Just to make sure everyone agrees on this - there's currently a know bug
> > in dc395x with highmem reported by Pierre Ossman in thread "Kernel panic
> > with dc395x in 2.6.12.2" on
On Sun, 14 Aug 2005 17:52:36 EDT, Kyle Moffett said:
> > Note that ?^ is functionally identical to !.?| differs from || in
> Since when is the string "!.?|" an operator???
I think that was supposed to read:
Note that ?^ is functionally identical to !.
?| differs from ?? in that ?| returns
Lee Revell wrote:
> For strings, of course. But there's no need for UTF-8 operators.
Indeed - this is the main rationale for the patch, of course. People
want to write non-ASCII in script primarily in string literals,
and (perhaps even more often) in comments. Now, for comments, it
wouldn't
On Aug 12, 2005, at 17:53:53, Steven Rostedt wrote:
Two more systems that are different from Linux.
So far, Linux is the odd ball out.
Make that three more systems (Mac OS X has the same behavior as the
BSDs):
zeus:~ kyle$ uname -a
Darwin zeus.moffetthome.net 8.2.0 Darwin Kernel Version
Based on testing at the cifs plugfest last week these were the two most
important patches from among those pending in my tree. The rest can
wait until after 2.6.12
[PATCH] [CIFS] Fix missing entries in search results when very long file names and
more than 50 (or so) of such long search
On Aug 14, 2005, at 02:18:13, Jason L Tibbitts III wrote:
"LR" == Lee Revell <[EMAIL PROTECTED]> writes:
LR> Is Larry smoking crack?
From the Perl6-Bible: http://search.cpan.org/dist/Perl6-Bible/lib/
Perl6/Bible/S03.pod:
I think this confirms that the answer is yes. See the following at
Hi Willy :)
* Willy Tarreau <[EMAIL PROTECTED]> dixit:
> > That's not possible. sd_mod will assign different devices for
> > different USB gadgets, and that's my problem in the first case!. If I
> > plug my USB-whatever, it gets assigned /dev/sda1 (for the first
> > partition, I mean).
All right, I'll see what I can come up with. This is quite a tall order.
1. A mechanism for creating virtual network interfaces
2. A mechanism for restricting binding to certain network interfaces
3. A mechanism for binding certain network interfaces.
4. The jail code itself
Much of the work is
Hi, all
I might be missunderstanding things but...
First of all, machines with long pipelines will suffer from cache misses
(p4 in this case).
Depending on the size copied, (i don't know how large they are so..)
can't one run out of cachelines and/or evict more useful cache data?
Ie, if it's
On 8/14/05, Alan Cox <[EMAIL PROTECTED]> wrote:
> On Sul, 2005-08-14 at 17:56 +0200, Bartlomiej Zolnierkiewicz wrote:
> > * your stuff was accepted after all (and some stuff like ide-cd
> > fixes was never splitted from the -ac patchset and submitted)
>
> They were.
I remember discussion about
Daniel Drake wrote:
CaT wrote:
1. Alan Cox's IDE driver that was included in his ac patchset, which
seems to have died at 2.6.11ac7.
2. A brief visit from a SCSI IDE driver in Andrew Mortons mm patchset.
It lived a brief but noted life before being taken out without any
reason (that I
On Fri, Aug 12, 2005 at 09:31:09PM +0200, Olaf Hering wrote:
> On Fri, Aug 12, Matt Mackall wrote:
>
> > Does the task dump work without patch 5/8 (add retry timeout)? I'll
> > try testing it here.
>
> I spoke to soon, worked once, after reboot not anymore. Will try to play
> with individual
On Sul, 2005-08-14 at 17:56 +0200, Bartlomiej Zolnierkiewicz wrote:
> * your stuff was accepted after all (and some stuff like ide-cd
> fixes was never splitted from the -ac patchset and submitted)
They were.
> * you've never provided any technical details on "the stuff I broke"
I did,
On 11-Aug-05, Chuck Ebbert wrote:
> Both -rc4 and -rc6 just silently reboot after two or three days.
It was a failed UPS battery.
__
Chuck
-
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 Sun, 14 Aug 2005 09:24:02 -0700 (PDT), Linus Torvalds wrote:
> Yes, the thing needs to be opened with O_LARGEFILE and you need to use
> "llseek()" to seek into it, but once you do that, everything should be
> fine.
GCC warns about using llseek and suggests lseek64 instead. That works
for
Hi.
The commits 71db63acff69618b3d9d3114bd061938150e146b ([PATCH] increase
PCIBIOS_MIN_IO on x86) and 0b2bfb4e7ff61f286676867c3508569bea6fbf7a
(ACPI: increase PCIBIOS_MIN_IO on x86) shortly after -rc5 caused my
on-board audio to stop working. See attached output from dmesg and lspci.
On a
On Sun, 2005-08-14 at 13:13 -0700, Stephen Pollei wrote:
> Seems like lots of Europeans might want a bigger
> charset, not to mention Asians, Hindus, and whomever else.
For strings, of course. But there's no need for UTF-8 operators.
Lee
-
To unsubscribe from this list: send the line
Hi!
> This patch adds the return value check for sysdev suspend and does
> restore in failure case. Send the patch to pm-list, but seems lost, so I
> resend it.
It seems to duplicate code a bit. Can that be fixed?
Pavel
--
64 bytes from 195.113.31.123:
Hi!
> > > What happens when you disable it at runtime before suspending?
> > >
> > > echo 0 > /sys/devices/system/dyn_tick/dyn_tick0/enable
> >
> > This has no effect. The system stalls at exactly the same point. The
> > last lines on my screen are:
>
> Ok perhaps on the resume side instead.
On 8/14/05, Lee Revell <[EMAIL PROTECTED]> wrote:
> I know the alternatives are available. That doesn't make it any less
> idiotic to use non ASCII characters as operators. I think it's a very
> slippery slope. We write code in ASCII, dammit.
Yes you and I might write 99.9% of our code in
On Sun, 14 Aug 2005 22:12:55 +1000, Roger Luethi <[EMAIL PROTECTED]> wrote:
@@ -31,7 +31,7 @@
#define APC_BPORT_REG 0x30
#define APC_REGMASK0x01
-define APC_BPMASK 0x03
+#define APC_BPMASK 0x03
Color me skeptical. I've seen some weird bit flips and
I just remember a path I took when resolving the issue further to my post
below.
Here is what man hdparm says on -i and -I:
-i Display the identification info that was obtained from the
drive at boot time,
if available. This is a feature of modern IDE drives, and
Hi,
I continue studying the VFS interface. As I said in previous e-mails,
my goal is to integrate an existing parallel filesystem into the Linux
kernel.
Now, I am looking for a reduced subset of operations to focus on. I
have selected the following:
struct file_system_type
get_sb()
Voluspa wrote:
>
> The "hdparm -I /dev/hdc"
>
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> de: failed opcode was: 0xec
>
> Is present on all kernels that I have locally (oldest 2.6.11.11)
> so it is not related to the
On Sun, 2005-08-14 at 21:33 +0200, Guennadi Liakhovetski wrote:
> Just to make sure everyone agrees on this - there's currently a know bug
> in dc395x with highmem reported by Pierre Ossman in thread "Kernel panic
> with dc395x in 2.6.12.2" on linux-scsi. It is also trivial to reproduce on
>
Hi
On Thu, 4 Aug 2005, James Bottomley wrote:
> This is my (hopefully final) collection of safe driver updates and bug
> fixes for 2.6.13.
Just to make sure everyone agrees on this - there's currently a know bug
in dc395x with highmem reported by Pierre Ossman in thread "Kernel panic
with
The "hdparm -I /dev/hdc"
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
de: failed opcode was: 0xec
Is present on all kernels that I have locally (oldest 2.6.11.11)
so it is not related to the threadstarters problems, it seems.
Hi Michael,
> > Individual patches will be posted in reply to this post, with
> > explanations and diffstat. Please consider applying them.
>
> How come these patches never showed up on LKML?
They did, just with some delay. I'm only a human.
--
Jean Delvare
-
To unsubscribe from this list:
On Sun, 14 Aug 2005 18:42:12 +1000, Con Kolivas <[EMAIL PROTECTED]> wrote:
> On Sun, 14 Aug 2005 18:00, Pete Zaitcev wrote:
> > On Sun, 14 Aug 2005 17:12:06 +1000, Con Kolivas <[EMAIL PROTECTED]> wrote:
> Yes all those dmesgs etc were redone after it failed in rc6 as I needed it
> working. Oh
Doing a "hdparm -I /dev/hdc" (without a disk/with a ISO disk/[u]mounted/music
CD):
Aug 14 19:14:33 sleipner kernel: hdc: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Aug 14 19:14:33 sleipner kernel: hdc: drive_cmd: error=0x04 { AbortedCommand }
Aug 14 19:14:33 sleipner kernel: ide:
Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
>> Is the machine running X? We need some output from it so we can debug
>> what's going on, the info should be printed to the console. It would
>> be great if you could run the latest kernel and see if you get any
>> output. Also add nmi_watchdog=2 to
On Sun, 14 Aug 2005, Chuck Ebbert wrote:
>
> It's ugly but so is the existing code. And it won't fix 64-bit
> archs AFAICT. Tested on 2.6.11, patch offsets fixed up for 2.6.13-rc6.
Btw, if you really want to allow negative ("huge positive") loff_t, then
you should do it the way we did
On Sun, 14 Aug 2005, Chuck Ebbert wrote:
>
> The first thing drivers/char/mem.c:read_kmem does is convert the
> loff_t it gets as the offset for reading into an unsigned int. This
> patch makes the kmem driver's llseek operator do that up-front, so
> that fs/read_write.c:rw_verify_area
On Sun, Aug 14, 2005 at 12:12:52PM -0400, Chuck Ebbert wrote:
> The first thing drivers/char/mem.c:read_kmem does is convert the
> loff_t it gets as the offset for reading into an unsigned int. This
> patch makes the kmem driver's llseek operator do that up-front, so
> that
The first thing drivers/char/mem.c:read_kmem does is convert the
loff_t it gets as the offset for reading into an unsigned int. This
patch makes the kmem driver's llseek operator do that up-front, so
that fs/read_write.c:rw_verify_area doesn't return -EINVAL when
we try to read from higher
On Sun, Aug 14, 2005 at 08:48:48AM -0700, Richard Henderson wrote:
> On Sun, Aug 14, 2005 at 11:35:43AM +0200, Christoph Hellwig wrote:
> > This version has the arch_ptrace return value changes to long as
> > recommended by Richard Henderson.
> ...
> > +extern int arch_ptrace(struct task_struct
On 8/14/05, Alan Cox <[EMAIL PROTECTED]> wrote:
> On Sul, 2005-08-14 at 17:01 +0200, Bartlomiej Zolnierkiewicz wrote:
> > > Thats probably the fact other patches from -ac are missing in base. It
> > > should be harmless.
> >
> > Therefore please submit them.
>
> Cut the crap, you know I've
On Sun, Aug 14, 2005 at 11:35:43AM +0200, Christoph Hellwig wrote:
> This version has the arch_ptrace return value changes to long as
> recommended by Richard Henderson.
...
> +extern int arch_ptrace(struct task_struct *child, long request, long addr,
> long data);
No it doesn't.
r~
On Sul, 2005-08-14 at 17:01 +0200, Bartlomiej Zolnierkiewicz wrote:
> > Thats probably the fact other patches from -ac are missing in base. It
> > should be harmless.
>
> Therefore please submit them.
Cut the crap, you know I've submitted the stuff again and again and
again along with other
Am Sonntag, den 14.08.2005, 09:29 -0400 schrieb Willem Riede:
> On Wed, 10 Aug 2005 20:54:35 +, Allen Martin wrote:
>
> > Likely the only way nForce4 NCQ support could be added under Linux would
> > be with a closed source binary driver, and no one really wants that,
> > especially for
Five log messages lack their trailing new line in i2c-core.
Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
drivers/i2c/i2c-core.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
--- linux-2.4.31.orig/drivers/i2c/i2c-core.c2005-04-09 12:35:59.0
+0200
+++
Fix two typos in the i2c documentation.
Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
Documentation/i2c/functionality |2 +-
Documentation/i2c/writing-clients |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- linux-2.4.31.orig/Documentation/i2c/functionality 2000-12-29
Fix documentation to match code in include/linux/i2c-dev.h
Signed-off-by: Jan Veldeman <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
Documentation/i2c/dev-interface |4 ++--
1 files changed, 2 insertions(+), 2
The lm_sensors project changed mailing lists.
Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
MAINTAINERS |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
--- linux-2.4.30.orig/MAINTAINERS 2005-06-03 19:21:41.0 +0200
+++ linux-2.4.30/MAINTAINERS2005-06-03
Jean Delvare wrote:
I have a total of 5 patches with minor fixes to the Linux 2.4 i2c
subsystem and documentation. These fixes I gathered for the past few
months as they were applied to the Linux 2.6 tree and to the i2c CVS
repository.
Individual patches will be posted in reply to this post,
Backport of a spelling fix Tobias Klauser sent to me for Linux
2.6.12-rc4. Already fixed in i2c CVS.
Signed-off-by: Tobias Klauser <[EMAIL PROTECTED]>
Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
drivers/i2c/i2c-dev.c |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
---
On 8/14/05, Alan Cox <[EMAIL PROTECTED]> wrote:
> On Sul, 2005-08-14 at 13:44 +0100, Daniel Drake wrote:
> > > [227523.229557] hda: 390721968 sectors (200049 MB) w/8192KiB Cache,
> > > CHS=24321/255/63, BUG
>
> Thats probably the fact other patches from -ac are missing in base. It
> should be
On Sat, Aug 13, 2005 at 02:39:56PM -0700, Greg KH wrote:
> Heh, I already have a patch like this pending for 2.6.14 at:
>
> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/driver-link-device-and-class.patch
Last time I tried to do something like this, it
On Sul, 2005-08-14 at 13:35 +0200, Bartlomiej Zolnierkiewicz wrote:
> > The symptoms vary. On some of my machines just inserting
> > an audio CD makes the box instantly lock up.
You've got all the gnome cruft running. Start by turning that off. Then
try inserting/removing audio discs, playing
On Sul, 2005-08-14 at 13:44 +0100, Daniel Drake wrote:
> > [227523.229557] hda: 390721968 sectors (200049 MB) w/8192KiB Cache,
> > CHS=24321/255/63, BUG
Thats probably the fact other patches from -ac are missing in base. It
should be harmless.
> > [227523.229631] hda: cache flushes not
On Sul, 2005-08-14 at 10:30 +1000, Con Kolivas wrote:
> > presumably related, on 2.6.13-rc6. Putting in a cd and trying to read it
> > will cause huge delays and then error out with:
> >
> > ide-cd: cmd 0x28 timed out
(Thats READ_10)
> > hdc: DMA timeout retry
> > hdc: timeout waiting for DMA
>
On Wed, 10 Aug 2005 20:54:35 +, Allen Martin wrote:
> Likely the only way nForce4 NCQ support could be added under Linux would
> be with a closed source binary driver, and no one really wants that,
> especially for storage / boot volume. We decided it wasn't worth the
> headache of a binary
Rafael J. Wysocki wrote:
> I've got the following BUG on Asus L5D (x86-64) with the 2.6.13-rc5-mm1
> kernel:
>
> BUG: rwlock recursion on CPU#0, nscd/3668, 8817d4a0
>
> Call Trace:{add_preempt_count+105}
> {rwlock_bug+114}
>{_raw_write_lock+62}
> {_write_lock_bh+40}
>
Hi Marcelo,
I have a total of 5 patches with minor fixes to the Linux 2.4 i2c
subsystem and documentation. These fixes I gathered for the past few
months as they were applied to the Linux 2.6 tree and to the i2c CVS
repository.
Individual patches will be posted in reply to this post, with
On Sun, Aug 14, 2005 at 03:41:49PM +0300, Samer Sarhan wrote:
> Hi,
> I had a design problem of a Linux module (Linux 2.6.11) that lead me to do
> this:
>
> int work_fn(void* data);
> task_t my_task;
> task_t* kthread = kthread_create(work_fn, NULL, "Task 1");
> // assume kthread create was
On Sun, 2005-08-14 at 15:41 +0300, Samer Sarhan wrote:
> Hi,
> I had a design problem of a Linux module (Linux 2.6.11) that lead me to do
> this:
>
> int work_fn(void* data);
> task_t my_task;
> task_t* kthread = kthread_create(work_fn, NULL, "Task 1");
> // assume kthread create was
Adds support for writing multiple sectors at once. This allows
back-to-back transfers of sectors giving roughly double write throughput.
To be able to detect which sector is causing problems the system falls
back to single sector writes if a failure is detected.
Tested by several people with no
Hi,
I've got the following BUG on Asus L5D (x86-64) with the 2.6.13-rc5-mm1 kernel:
BUG: rwlock recursion on CPU#0, nscd/3668, 8817d4a0
Call Trace:{add_preempt_count+105}
{rwlock_bug+114}
{_raw_write_lock+62}
{_write_lock_bh+40}
{:ip_conntrack:destroy_conntrack+196}
Hi,
I had a design problem of a Linux module (Linux 2.6.11) that lead me to do this:
int work_fn(void* data);
task_t my_task;
task_t* kthread = kthread_create(work_fn, NULL, "Task 1");
// assume kthread create was successfully...
my_task = *kthread;
// change what current maceo points to...
On Sun, Aug 14, 2005 at 01:43:18PM +0200, Alexander Nyberg wrote:
> On Sun, Aug 14, 2005 at 10:10:18AM + Danny ter Haar wrote:
> > I've posted a couple of times than my newsserver is not stable
> > with any 2.6.13-rcX kernels.
> > Last kernel that survived is 2.6.12-mm1 (18+days)
> Is the
On 8/13/05, Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 13, 2005 at 10:00:14AM -0400, Steven Rostedt wrote:
> > On Sat, 2005-08-13 at 14:39 +0200, Andi Kleen wrote:
> > > On Fri, Aug 12, 2005 at 10:40:02PM -0400, Steven Rostedt wroqte:
> > > > Here's a patch that converts all architectures
> @@ -31,7 +31,7 @@
> #define APC_BPORT_REG 0x30
>
> #define APC_REGMASK0x01
> -define APC_BPMASK 0x03
> +#define APC_BPMASK 0x03
Color me skeptical. I've seen some weird bit flips and data corruption;
"paramters" to "paramEters" I could buy. But data
Quoting Joshua Hudson ([EMAIL PROTECTED]):
> Why would you want a virtual network device implementation? The whole
So that a jailed process can use the net but can't use your network
address (intercept ssh, imap/stunnel, etc).
> I do like the idea of patching in through LSM, however not
CaT wrote:
1. Alan Cox's IDE driver that was included in his ac patchset, which
seems to have died at 2.6.11ac7.
Alan's driver has been merged into 2.6.13. You can get the up-to-date
Wooo!
patches here:
1 - 100 of 265 matches
Mail list logo
