Thanks Adrian and Chris. That seems to work.
Ravi
-Original Message-
From: Adrian Bunk [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 24, 2005 5:08 PM
To: Ravinandan Arakali
Cc: linux-kernel@vger.kernel.org; Leonid. Grossman (E-mail)
Subject: Re: Problem applying latest 2.6 kernel
On Thu, 24 Mar 2005 14:49:55 -0800 (PST)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> Could you help me fix up this patch replacing the old clear_pages patch?
Ok, first you need to mark the order and gfp arguments as unsigned
for mm/page_alloc.c:prep_zero_page() so that it matches the
On Thu, 2005-03-24 at 20:15 -0600, Robert Hancock wrote:
> There is no need to use any binary drivers on the nForce4 - the only
> ones even available are for the network and audio. The network works
> fine with the forcedeth driver included in the kernel - I don't know
> about the audio, I'm
On Thu, 24 Mar 2005, David S. Miller wrote:
> Erm... were any of your test builds done with the new CONFIG_CLEAR_COLD
> option enabled? :-)
These were all fixed but I failed to do a "quilt refresh" sigh... The
email issues are also fixed now sigh. What a day.
> Next, replace your
Adrian Bunk wrote:
This patch fixes a check after use found by the Coverity checker.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
--- linux-2.6.12-rc1-mm1-full/drivers/net/tulip/dmfe.c.old 2005-03-23 05:05:36.0 +0100
+++ linux-2.6.12-rc1-mm1-full/drivers/net/tulip/dmfe.c 2005-03-23
Hello, James and Jens.
On Thu, Mar 24, 2005 at 06:45:58PM -0600, James Bottomley wrote:
> On Wed, 2005-03-23 at 16:25 +0100, Jens Axboe wrote:
> > Let me guess, it is hanging in wait_for_completion()?
>
> Yes, I have the trace now. Why is curious. This is the trace of the
> failure:
>
> Mar
Matthew Collins wrote:
Jeff Garzik wrote:
Bernard Blackham wrote:
Hi,
Playing with a recently acquired Promise SX8 card, we've found
similar performance results to Matt's post to lkml a few months back
at http://marc.theaimsgroup.com/?l=linux-kernel=110175890323356=2
It appears that the driver is
Vladimir Kondratiev wrote:
I did posted once; it was long time ago. I am sure I sent it to Dave. I can
resend if needed. Basically, I made Dave's stack work on 2.6 kernels; did
some changes toward QoS and provided simple utility to imitate low level
driver. I was concentrated on interfaces, it
[EMAIL PROTECTED]:/sys/class/i2c-adapter# ls * -l
[EMAIL PROTECTED]:/sys# cat */*/*/*
ksymoops 2.4.9 on i686 2.6.12-rc1-mm2. Options used
-o /lib/modules/2.6.12-rc1-mm2 (specified)
-m /boot/System.map-2.6.12-rc1-mm2 (specified)
Unable to handle kernel paging request at virtual address
Hi,
Was this change intentional or accidental? I have successfully built
ndiswrapper-1.0rc1 with the other recent kernel trees.
/usr/src/ndiswrapper-1.0rc1/driver/wrapper.c: In function `wrapper_init':
/usr/src/ndiswrapper-1.0rc1/driver/wrapper.c:1485: warning: passing
arg 4 of
On Thu, 2005-03-24 at 15:39 -0500, Jeff Garzik wrote:
> Evgeniy Polyakov wrote:
> > hw_random.c already does it using userspace daemons,
> > which is bad idea for very fast HW - like VIA xstore/xcrypt
> > instructions.
>
> This is incorrect, because it implies that a user would want to use the
Miles Lane <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED]:/sys/class/i2c-adapter# ls * -l
> [EMAIL PROTECTED]:/sys# cat */*/*/*
>
> ksymoops 2.4.9 on i686 2.6.12-rc1-mm2. Options used
> -o /lib/modules/2.6.12-rc1-mm2 (specified)
> -m /boot/System.map-2.6.12-rc1-mm2 (specified)
>
On Thu, 2005-03-24 at 15:56 -0500, Jeff Garzik wrote:
> > Idea to validate entropy data is good in general,
> > but it should be implemented in a way allowing external both in-kernel
> > and userspace
> > processes to contribute data.
> > So for in-kernel use we need such a mechanism, and
applied patches 1-3, thanks much.
Small administrivia request, though: after using my patch merging
script to merge your patches, I have to do the following things manually:
* delete diffstat output
* delete patch filename
* un-indent patch description text
It would be great if I didn't have to
On Mar 24, 2005, at 23:15, Miles Lane wrote:
Hi,
Was this change intentional or accidental? I have successfully built
ndiswrapper-1.0rc1 with the other recent kernel trees.
warning: passing arg 4 of `call_usermodehelper' makes pointer from
integer without a cast
error: too few arguments to
Evgeniy Polyakov wrote:
On Thu, 2005-03-24 at 15:39 -0500, Jeff Garzik wrote:
Evgeniy Polyakov wrote:
hw_random.c already does it using userspace daemons,
which is bad idea for very fast HW - like VIA xstore/xcrypt
instructions.
This is incorrect, because it implies that a user would want to use
On Thu, Mar 24, 2005 at 11:09:17PM -0500, Jeff Garzik wrote:
> >Indeed there does seem to be new firmware out as of 2/23/05. I ran my
> >tests with the 9/10/04 firmware but I did not adjust the CARM_MAX_Q
> >value. Do either of you happen to know what firmware revisions you
> >tested under?
Evgeniy Polyakov wrote:
On Thu, 2005-03-24 at 15:56 -0500, Jeff Garzik wrote:
See the earlier discussion, when data validation was -removed- from the
original Intel RNG driver, and moved to userspace.
I'm not arguing against userspace validation, but if data produced
_is_ cryptographically
On Fri, 2005-03-25 at 12:15 +0900, Tejun Heo wrote:
> I think I found the cause. Special requests submitted using
> scsi_do_req() never initializes ->end_io(). Normally, SCSI midlayer
> terminates special requests inside the SCSI midlayer without passing
> through the blkdev layer. However, if
On Thu, 2005-03-24 at 23:48 -0500, Jeff Garzik wrote:
> > And how HIFN driver can contribute entropy?
>
> Use the current chrdev->rngd method.
Why HIFN must be chardev?
> > You may say, that hardware can be broken and thus produces
> > wrong data, but if user want, it can turn it on or off.
>
Hugh Dickins wrote:
And the range to sparc64's flush_tlb_pgtables? It's less clear to me
now that we need to do more than is done here - every PMD_SIZE ever
occupied will be flushed, do we really have to flush every PGDIR_SIZE
ever partially occupied? A shame to complicate it unnecessarily.
It
Nick Piggin wrote:
Hugh Dickins wrote:
And the range to sparc64's flush_tlb_pgtables? It's less clear to me
now that we need to do more than is done here - every PMD_SIZE ever
occupied will be flushed, do we really have to flush every PGDIR_SIZE
ever partially occupied? A shame to complicate it
Hi,
On Thu, Mar 24, 2005 at 11:02:45PM -0600, James Bottomley wrote:
> On Fri, 2005-03-25 at 12:15 +0900, Tejun Heo wrote:
> > I think I found the cause. Special requests submitted using
> > scsi_do_req() never initializes ->end_io(). Normally, SCSI midlayer
> > terminates special requests
On Thu, 2005-03-24 at 14:59 +0300, Evgeniy Polyakov wrote:
> For example here is patch to enable acrypto support for hw_random.c
> It is very simple and support only upto 4 bytes request, of course it
> is not interested for anyone, but it is only 2-minutes example:
Full port.
---
On Thu, Mar 24, 2005 at 11:45:53PM -0500, Jeff Garzik wrote:
>
> I agree with this sentiment; this is mainly a policy decision that
> kernel programmers should not make.
Exactly. Policy decisions like this as well as entropy checking
should be done in user-space.
Cheers,
--
Visit Openswan at
[EMAIL PROTECTED], 2005-03-24 10:48:35-08:00, [EMAIL PROTECTED]
[driver core] Remove the unused device_find().
Signed-off-by: Patrick Mochel <[EMAIL PROTECTED]>
diff -Nru a/drivers/base/core.c b/drivers/base/core.c
--- a/drivers/base/core.c 2005-03-24 20:34:00 -08:00
+++
Here is the next round of driver model locking changes. These build off of
the previous set of changes, including the klist patch. They eradicate all
of the uses of the subsystems' rwsem in the driver core.
It does include the fix posted earlier that happened when removing the
driver.
A summary
[EMAIL PROTECTED], 2005-03-24 10:50:24-08:00, [EMAIL PROTECTED]
[driver core] Use bus_for_each_{dev,drv} for driver binding.
- Now possible, since the lists are locked using the klist lock and not the
global rwsem.
Signed-off-by: Patrick Mochel <[EMAIL PROTECTED]>
diff -Nru
[EMAIL PROTECTED], 2005-03-24 13:00:16-08:00, [EMAIL PROTECTED]
[usb] Fix up USB to use klist_node_attached() instead of list_empty() on
lists that will go away.
Signed-off-by: Patrick Mochel <[EMAIL PROTECTED]>
diff -Nru a/drivers/usb/core/usb.c b/drivers/usb/core/usb.c
---
[EMAIL PROTECTED], 2005-03-24 19:08:30-08:00, [EMAIL PROTECTED]
[driver core] Use a klist for device child lists.
- Use klist iterator in device_for_each_child(), making it safe to use for
removing devices.
- Remove unused list_to_dev() function.
- Kills all usage of
Evgeniy Polyakov wrote:
So I still insist on creating ability to contribute entropy directly,
without userspace validation.
It will be turned off by default.
If its disabled by default, then you and 2-3 other people will use this
feature. Not enough justification for a kernel API at that point.
[EMAIL PROTECTED], 2005-03-24 20:08:04-08:00, [EMAIL PROTECTED]
[driver core] Fix up bogus comment.
Signed-off-by: Patrick Mochel <[EMAIL PROTECTED]>
diff -Nru a/drivers/base/driver.c b/drivers/base/driver.c
--- a/drivers/base/driver.c 2005-03-24 20:32:39 -08:00
+++
[EMAIL PROTECTED], 2005-03-24 19:03:59-08:00, [EMAIL PROTECTED]
[scsi] Use device_for_each_child() to unregister devices in
scsi_remove_target().
Signed-off-by: Patrick Mochel <[EMAIL PROTECTED]>
diff -Nru a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
---
[EMAIL PROTECTED], 2005-03-24 18:59:59-08:00, [EMAIL PROTECTED]
[klist] Don't reference NULL klist pointer in klist_remove().
Signed-off-by: Patrick Mochel <[EMAIL PROTECTED]>
diff -Nru a/lib/klist.c b/lib/klist.c
--- a/lib/klist.c 2005-03-24 20:33:01 -08:00
+++ b/lib/klist.c
[EMAIL PROTECTED], 2005-03-24 12:58:57-08:00, [EMAIL PROTECTED]
[klist] add klist_node_attached() to determine if a node is on a list or not.
Signed-off-by: Patrick Mochel <[EMAIL PROTECTED]>
diff -Nru a/include/linux/klist.h b/include/linux/klist.h
--- a/include/linux/klist.h
[EMAIL PROTECTED], 2005-03-24 13:03:35-08:00, [EMAIL PROTECTED]
[driver core] Remove struct device::bus_list.
Signed-off-by: Patrick Mochel <[EMAIL PROTECTED]>
diff -Nru a/drivers/base/core.c b/drivers/base/core.c
--- a/drivers/base/core.c 2005-03-24 20:33:23 -08:00
+++
[EMAIL PROTECTED], 2005-03-24 13:08:05-08:00, [EMAIL PROTECTED]
[driver core] Remove struct device::driver_list.
Signed-off-by: Patrick Mochel <[EMAIL PROTECTED]>
diff -Nru a/drivers/base/core.c b/drivers/base/core.c
--- a/drivers/base/core.c 2005-03-24 20:33:16 -08:00
+++
On Fri, Mar 25, 2005 at 09:16:01AM +0300, Evgeniy Polyakov wrote:
> On Fri, 2005-03-25 at 00:58 -0500, Jeff Garzik wrote:
>
> > If its disabled by default, then you and 2-3 other people will use this
> > feature. Not enough justification for a kernel API at that point.
>
> It is only because
[EMAIL PROTECTED], 2005-03-24 13:02:28-08:00, [EMAIL PROTECTED]
[driver core] Fix up bus code and remove use of rwsem.
- Don't add devices to bus's embedded kset, since it's not used by anyone
anymore.
- Don't need to take the bus rwsem when calling {device,driver}_attach(),
since
* Esben Nielsen <[EMAIL PROTECTED]> wrote:
> I like the idea of having the scheduler take care of it - it is a very
> optimal coded queue-system after all. That will work on UP but not on
> SMP. Having the unlock operation to set the mutex in a "partially
> owned" state will work better. The
[EMAIL PROTECTED], 2005-03-24 18:58:45-08:00, [EMAIL PROTECTED]
[driver core] Call klist_del() instead of klist_remove().
- Can't wait on removing the current item in the list (the positive refcount
*because*
we are using it causes it to deadlock).
Signed-off-by: Patrick Mochel
On Fri, 2005-03-25 at 00:58 -0500, Jeff Garzik wrote:
> Evgeniy Polyakov wrote:
> > So I still insist on creating ability to contribute entropy directly,
> > without userspace validation.
> > It will be turned off by default.
>
> If its disabled by default, then you and 2-3 other people will use
On Fri, 2005-03-25 at 17:13 +1100, Herbert Xu wrote:
> On Fri, Mar 25, 2005 at 09:16:01AM +0300, Evgeniy Polyakov wrote:
> > On Fri, 2005-03-25 at 00:58 -0500, Jeff Garzik wrote:
> >
> > > If its disabled by default, then you and 2-3 other people will use this
> > > feature. Not enough
On Fri, Mar 25, 2005 at 09:34:19AM +0300, Evgeniy Polyakov wrote:
>
> Such hardware is used mostly in embedded world where SW crypto
> processing
> is too expensive, so users of such HW likely want to trust to
> theirs hardware and likely will turn in on.
That's fine. All you need for these
On Thu, Mar 24, 2005 at 05:00:18PM -0800, Patrick Mochel wrote:
>
> On Thu, 24 Mar 2005, Andrew Morton wrote:
>
> > Laurent Riffard <[EMAIL PROTECTED]> wrote:
> > >
> > > hello,
> > >
> > > Same kinds of problem here. It depends on the removed module. I mean:
> > > "rmmod loop" or "rmmod pcspkr"
On Fri, 2005-03-25 at 17:33 +1100, Herbert Xu wrote:
> On Fri, Mar 25, 2005 at 09:34:19AM +0300, Evgeniy Polyakov wrote:
> >
> > Such hardware is used mostly in embedded world where SW crypto
> > processing
> > is too expensive, so users of such HW likely want to trust to
> > theirs hardware and
On Wed, 23 Mar 2005, Pavel Machek wrote:
> This is WONTFIX for 2.6.11, but you can be pretty sure it is going to
> be fixed for SuSE 9.3, and patch is already in 2.6.12-rc1. Feel free
> to betatest SuSE 9.3 ;-).
Unfortunately the celebration was premature. I compiled 2.6.12-rc1,
noticing the
On Fri, Mar 25, 2005 at 09:59:18AM +0300, Evgeniy Polyakov wrote:
>
> It is not only about userspace/kernelspace system calls and data
> copying,
> but about whole revalidation process, which can and is quite expensive,
> due to system calls, copying and validating itself,
What I meant is if you
in the SATA kconfig menu, the help message from
Intel PIIX/ICH SATA support says:
CONFIG_SCSI_ATA_PIIX:
This option enables support for ICH5 Serial ATA.
If PATA support was enabled previously, this enables
support for select Intel PIIX/ICH PATA host controllers.
anyone care to clarify if
On Fri, 2005-03-25 at 17:56 +1100, Herbert Xu wrote:
> On Fri, Mar 25, 2005 at 09:59:18AM +0300, Evgeniy Polyakov wrote:
> >
> > It is not only about userspace/kernelspace system calls and data
> > copying,
> > but about whole revalidation process, which can and is quite expensive,
> > due to
Silicon Image contributed a patch which should help some of the
situations that users were seeing. If you are having problems with
sata_sil, please do try out this patch.
I'm concerned that the sata_sil blacklist has been growing beyond the
older Seagate drives which definitely had buggy
Søren Lott wrote:
in the SATA kconfig menu, the help message from
Intel PIIX/ICH SATA support says:
CONFIG_SCSI_ATA_PIIX:
This option enables support for ICH5 Serial ATA.
If PATA support was enabled previously, this enables
support for select Intel PIIX/ICH PATA host controllers.
anyone care
Evgeniy Polyakov wrote:
Noone will complain on Linux if NIC is broken and produces wrong
checksum
and HW checksum offloading is enabled using ethtools.
Actually, that is a problem and people have definitely complained about
it in the past.
Jeff
-
To unsubscribe from this list: send the
Hi.
I used to have this old laptop that went through hell, and time after time
I revived it (it got ran over by a car, stolen, etc), finally it started
locking up on me after about 5-10 minutes of use and this occured at the
same time my other desktop was dying, and I got angry and punched it a
On Fri, Mar 25, 2005 at 10:19:55AM +0300, Evgeniy Polyakov wrote:
>
> Noone will complain on Linux if NIC is broken and produces wrong
> checksum
> and HW checksum offloading is enabled using ethtools.
This is completely different. The worst that can happen with checksum
offloading is that the
On Fri, 2005-03-25 at 04:17 +1000, Triffid Hunter wrote:
> you can limit the max number of processes by putting the following into
> /etc/security/limits.conf (on my distro, and quite a number of others
> according to google too)
>
> * hardnproc
>
> you can also limit quite a number
On Fri, 2005-03-25 at 02:19 -0500, Jeff Garzik wrote:
> Evgeniy Polyakov wrote:
> > Noone will complain on Linux if NIC is broken and produces wrong
> > checksum
> > and HW checksum offloading is enabled using ethtools.
>
>
> Actually, that is a problem and people have definitely complained
On Thu, Mar 24, 2005 at 05:21:27PM -0800, Andrew Morton wrote:
> Coywolf Qi Hunt <[EMAIL PROTECTED]> wrote:
> >
> > >>--- 2.6.12-rc1-mm2/mm/oom_kill.c 2005-03-03 17:12:18.0 +0800
> > >>+++ 2.6.12-rc1-mm2-cy/mm/oom_kill.c 2005-03-25 08:07:19.0
> > >>+0800
> > >>@@ -20,6
On Thu, Mar 24, 2005 at 08:22:15PM -0800, Andrew Morton wrote:
> Miles Lane <[EMAIL PROTECTED]> wrote:
> > Unable to handle kernel paging request at virtual address 24fc1024
> > c0198448
> > *pde =
> > Oops: [#1]
> > CPU:0
> > EIP:0060:[]Not tainted VLI
>
> I
Can someone (Ingo?) recommend me CPU scheduler tests which are usually
used to test CPU scheduler perfomance, context switch performance,
SMP/migration/balancing performance etc.?
Thanks in advance,
Kirill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
Russell King <[EMAIL PROTECTED]> wrote:
>
> On Thu, Mar 24, 2005 at 08:22:15PM -0800, Andrew Morton wrote:
> > Miles Lane <[EMAIL PROTECTED]> wrote:
> > > Unable to handle kernel paging request at virtual address 24fc1024
> > > c0198448
> > > *pde =
> > > Oops: [#1]
> > > CPU:
On Thu, Mar 24, 2005 at 11:45:44PM -0800, Andrew Morton wrote:
> Russell King <[EMAIL PROTECTED]> wrote:
> > On Thu, Mar 24, 2005 at 08:22:15PM -0800, Andrew Morton wrote:
> > > Miles Lane <[EMAIL PROTECTED]> wrote:
> > > > Unable to handle kernel paging request at virtual address 24fc1024
> > >
On Fri, 2005-03-25 at 18:25 +1100, Herbert Xu wrote:
> On Fri, Mar 25, 2005 at 10:19:55AM +0300, Evgeniy Polyakov wrote:
> >
> > Noone will complain on Linux if NIC is broken and produces wrong
> > checksum
> > and HW checksum offloading is enabled using ethtools.
>
> This is completely
Silicon Image contributed a patch which should help some of the situations
that users were seeing. If you are having problems with sata_sil, please do
try out this patch.
I'm concerned that the sata_sil blacklist has been growing beyond the older
Seagate drives which definitely had buggy
601 - 664 of 664 matches
Mail list logo
