On 1/29/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
On 1/29/07, Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Sun, Jan 28, 2007 at 12:47:18PM +0100, Patrick Ale wrote:
>
> Hi Patrick,
Morning!
The 2.6.19 was self-compiled, using the gentoo-sources-rc4 AND using
the vanilla 2.6.19 from
On Mon, 29 Jan 2007, Mike Galbraith wrote:
>
> Unfortunately, I'm git impaired. I am rummaging as we speak though.
Ok, I'm personally heading to bed, but it rally should be as simple as
- get the git tree in the first place
- do
git bisect good v2.6.19
git bisect bad
On Sun, Jan 28, 2007 at 10:43:12PM -0800, Andrew Morton wrote:
>
> > IIRC Ingo had made fixes for the networking stack in his rt tree since
> > the networking code assumes in lots of places that rcu_read_lock
> > disables preemption.
>
> oh. We'd better find those fixes then. I wonder what
On Sun, 2007-01-28 at 22:48 -0800, Andrew Morton wrote:
> On Mon, 29 Jan 2007 07:26:03 +0100
> Mike Galbraith <[EMAIL PROTECTED]> wrote:
>
> > FWIW, I just tried it with 2.6.20-rc6, and can confirm. Once nero is
> > run, the kernel never gives up retrying whatever command failed, so I
> > get...
On Sun, Jan 28, 2007 at 10:58:50PM -0600, Eric Sandeen wrote:
> >-#else
> > #define xfs_cap_vset(v,p,sz)(-EOPNOTSUPP)
> > #define xfs_cap_vget(v,p,sz)(-EOPNOTSUPP)
> > #define xfs_cap_vremove(v) (-EOPNOTSUPP)
> > #define _CAP_EXISTS (NULL)
> >-#endif
> >
> > #endif /*
On Mon, 29 Jan 2007 07:26:03 +0100
Mike Galbraith <[EMAIL PROTECTED]> wrote:
> FWIW, I just tried it with 2.6.20-rc6, and can confirm. Once nero is
> run, the kernel never gives up retrying whatever command failed, so I
> get...
>
> [ 4362.972995] hdd: status error: status=0x58 { DriveReady
On Mon, 29 Jan 2007 16:29:29 +1100
Herbert Xu <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 29, 2007 at 04:17:44PM +1100, Herbert Xu wrote:
> > Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> >
> > > Jan 28 22:58:29 euridica kernel: BUG: using smp_processor_id() in
> > > preemptible [0001] code:
On Mon, 29 Jan 2007 00:14:24 -0600
Olof Johansson <[EMAIL PROTECTED]> wrote:
> Add PA Semi's PCI vendor ID (0x1959).
>
>
> Signed-off-by: Olof Johansson <[EMAIL PROTECTED]>
>
> ---
>
> Submitting this separately -- several drivers that have recently been
> posted could make use of it. I
On Sun, 28 Jan 2007 23:08:17 MST, Eric W. Biederman said:
> [EMAIL PROTECTED] writes:
> Does it find sys? If so perhaps I should do something even more significant.
> I guess if I get many complaints about this I will figure out how to print
> out an appropriate error message.
It found sys, and
On Mon, Jan 29, 2007 at 12:59:27AM -0500, Rob Landley wrote:
> On Sunday 28 January 2007 8:52 pm, Oleg Verych wrote:
> > On Sun, Jan 28, 2007 at 03:17:06PM -0800, Andrew Morton wrote:
> > > On Sun, 28 Jan 2007 22:46:32 +
> > > Oleg Verych <[EMAIL PROTECTED]> wrote:
> > >
> > > > If
On Sun, 2007-01-28 at 14:33 +0100, Uwe Bugla wrote:
> Original-Nachricht
> Datum: Sat, 27 Jan 2007 18:42:30 +0100
> Von: Adrian Bunk <[EMAIL PROTECTED]>
> An: Linus Torvalds <[EMAIL PROTECTED]>, Andrew Morton <[EMAIL PROTECTED]>
> Betreff: 2.6.20-rc6: known unfixed regressions
[EMAIL PROTECTED] writes:
> On Sat, 27 Jan 2007 13:41:16 PST, Andrew Morton said:
>> > > >> The mm snapshot broken-out-2007-01-26-00-36.tar.gz has been uploaded
>> > > >> to
>> > > >>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-01-26-00-36.tar.gz
>>
>> > I have
On Sun, 2007-01-28 at 21:25 -0800, David Miller wrote:
> From: [EMAIL PROTECTED] (Eric W. Biederman)
> Date: Sun, 28 Jan 2007 22:18:59 -0700
>
> > Regardless of my opinion on the sanity of the hypervisor architects.
> > I have not seen anything that indicates it will be hard to support
> > the
Add PA Semi's PCI vendor ID (0x1959).
Signed-off-by: Olof Johansson <[EMAIL PROTECTED]>
---
Submitting this separately -- several drivers that have recently been
posted could make use of it. I didn't want to include it in each of them
and have patch conflicts when they're combined upstream.
Paul E. McKenney wrote:
> On Thu, Jan 25, 2007 at 11:06:35AM -0800, Josh Triplett wrote:
>> Paul E. McKenney wrote:
>>> On Thu, Jan 25, 2007 at 12:47:04AM -0800, Josh Triplett wrote:
One major item: this new test feature really needs a new module parameter
to
enable or disable it.
David Miller <[EMAIL PROTECTED]> writes:
> From: [EMAIL PROTECTED] (Eric W. Biederman)
> Date: Sun, 28 Jan 2007 22:18:59 -0700
>
>> Regardless of my opinion on the sanity of the hypervisor architects.
>> I have not seen anything that indicates it will be hard to support
>> the hypervisor doing
On Sunday 28 January 2007 8:52 pm, Oleg Verych wrote:
> On Sun, Jan 28, 2007 at 03:17:06PM -0800, Andrew Morton wrote:
> > On Sun, 28 Jan 2007 22:46:32 +
> > Oleg Verych <[EMAIL PROTECTED]> wrote:
> >
> > > If somebody will get lkml mbox archive, can you import it into gmane,
> > > please.
>
On Sun, 28 Jan 2007 21:58:26 EST, [EMAIL PROTECTED] said:
> --==_Exmh_1170039506_3335P
> Content-Type: text/plain; charset=us-ascii
>
> On 26/01/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > The mm snapshot broken-out-2007-01-26-00-36.tar.gz has been uploaded to
> >
> >
You have an interesting idea of "simplifies", given
16 files changed, 997 insertions(+), 25 deletions(-)
(omitting your Documentation), and over 7k more code.
You'll have to be much more persuasive (with good performance
results) to get us to welcome your added layer of complexity.
If the
On Mon, Jan 29, 2007 at 04:17:44PM +1100, Herbert Xu wrote:
> Michal Piotrowski <[EMAIL PROTECTED]> wrote:
>
> > Jan 28 22:58:29 euridica kernel: BUG: using smp_processor_id() in
> > preemptible [0001] code: yum-updatesd/2846
> > Jan 28 22:58:29 euridica kernel: caller is
On Sun, Jan 28, 2007 at 10:17:05PM +0100, Ingo Molnar wrote:
> btw., while my plan is to prototype your lock-stat patch in -rt
> initially, it should be doable to extend it to be usable with the
> upstream kernel as well.
>
> We can gather lock contention events when there is spinlock debugging
From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: Sun, 28 Jan 2007 22:18:59 -0700
> Regardless of my opinion on the sanity of the hypervisor architects.
> I have not seen anything that indicates it will be hard to support
> the hypervisor doing everything or most of everything for us, so
> I see
David Miller <[EMAIL PROTECTED]> writes:
> From: [EMAIL PROTECTED] (Eric W. Biederman)
> Date: Sun, 28 Jan 2007 16:26:44 -0700
>
>> Yes. In general the mainline linux kernel does not support certain
>> classes of stupidity. TCP offload engines, firmware drivers for
>> hardware we care about, a
On Sun, 28 Jan 2007 21:58:26 -0500 [EMAIL PROTECTED] wrote:
> On 26/01/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > The mm snapshot broken-out-2007-01-26-00-36.tar.gz has been uploaded to
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-01-26-00-36.tar.gz
>
Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> Jan 28 22:58:29 euridica kernel: BUG: using smp_processor_id() in preemptible
> [0001] code: yum-updatesd/2846
> Jan 28 22:58:29 euridica kernel: caller is nf_conntrack_in+0x363/0x47f
> [nf_conntrack]
> Jan 28 22:58:29 euridica kernel: []
On Monday August 21, [EMAIL PROTECTED] wrote:
>
> Could we instead replace it with a dprintk() that returns the value of
> "res"? That will keep it useful for debugging purposes.
(only 5 months later...)
Sure, how about this?
Thanks,
NeilBrown
Remove warning: VFS is out of sync with lock
On 26/01/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> The mm snapshot broken-out-2007-01-26-00-36.tar.gz has been uploaded to
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-01-26-00-36.tar.gz
Aliens ate my brain, part 2:
My IPv6 configuration evaporated,
On Sat, 27 Jan 2007 13:41:16 PST, Andrew Morton said:
> > > >> The mm snapshot broken-out-2007-01-26-00-36.tar.gz has been uploaded to
> > > >>
> > > >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-01-26-00-36.tar.gz
>
> > I have everything compiling now, mostly. The
Robert P. J. Day wrote:
Remove a couple kernel config variables (FS_POSIX_CAP and
FS_POSIX_MAC) that represent placeholders for unimplemented
functionality.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
...
diff --git a/fs/xfs/xfs_cap.h b/fs/xfs/xfs_cap.h
index 7a0e482..cfedfd1
On 2.6.20-rc6 (run #1097), the openposixtest[1] suite results were:
build errors: 13 files, 31 lines
PASS: 1687
FAILED: 68
UNTESTED: 95
UNRESOLVED: 9
UNSUPPORTED: 22
INTERRUPTED: 7
SCORE:89
[1] http://posixtest.sourceforge.net/ (using v1.5.2)
On 2.6.20-rc6-mm1
Andrew Morton wrote:
On Sun, 28 Jan 2007 15:11:34 +0100
Peter Zijlstra <[EMAIL PROTECTED]> wrote:
+static inline int set_page_address(struct page *page, void *address)
+{
+ if (address)
+ return cmpxchg(>virtual, NULL, address) == NULL;
+ else {
+ /*
+
Fix DocBook build.
Regression was introduced by
gregkh-usb-usb-linux-usb_ch9h-becomes-linux-usb-ch9h.patch
Tested by `make htmldocs`.
Signed-off-by: Don Mullis <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
---
Documentation/DocBook/gadget.tmpl |4 ++--
Documentation/DocBook/usb.tmpl|6
On Sun, Jan 28, 2007 at 03:30:05PM -0800, Andrew Morton wrote:
> On Sun, 28 Jan 2007 14:47:56 -0800
> "Paul E. McKenney" <[EMAIL PROTECTED]> wrote:
>
> > > If we use the process freezer, these bugs all get automatically fixed,
> > > and we get to remove the existing locking, and we don't need to
On Mon, Jan 29, 2007 at 03:00:35AM +0100, Richard Knutsson wrote:
> Oleg Verych wrote:
> >On Mon, Jan 29, 2007 at 02:26:04AM +0100, Richard Knutsson wrote:
> >[]
> >
> >>I also guess you saw that the script is _not_ for cleaning up
> >>source-files (can be intrusive and is better to be fixed
On Thu, Jan 25, 2007 at 11:06:35AM -0800, Josh Triplett wrote:
> Paul E. McKenney wrote:
> > On Thu, Jan 25, 2007 at 12:47:04AM -0800, Josh Triplett wrote:
> >> One major item: this new test feature really needs a new module parameter
> >> to
> >> enable or disable it.
> >
> >
On Sun, 28 Jan 2007 17:19:50 +0100 Adrian Bunk wrote:
> <-- snip -->
>
>
> This patch fixes a circular dependency by letting GFS2_FS_LOCKING_DLM
> and DLM depend on instead of select SYSFS.
>
> Since SYSFS depends on EMBEDDED this change shouldn't cause any problems
> for users.
>
>
Oleg Verych wrote:
On Mon, Jan 29, 2007 at 02:26:04AM +0100, Richard Knutsson wrote:
[]
I also guess you saw that the script is _not_ for cleaning up
source-files (can be intrusive and is better to be fixed when fixing
something else), but patches.
IMHO it's dealing with
Hi, all
Is there any good idea about this issue?
I really think this is a problem in the NFSv4, which should be resolved
in the latest kernel.
Thank you for any information on this issue.
Hi, all
I have been working on trying to evaluate the robustness of the NFS.
When I run the
Here's a patch for sd.c I've cooked up which issues a START STOP UNIT
command to stop the drive when the SCSI disk is removed or the machine
is powered down. The rationale behind this is that apparently on many
drives, simply cutting power to the spinning disk forces it to do an
emergency head
On Sun, Jan 28, 2007 at 03:17:06PM -0800, Andrew Morton wrote:
> On Sun, 28 Jan 2007 22:46:32 +
> Oleg Verych <[EMAIL PROTECTED]> wrote:
>
> > If somebody will get lkml mbox archive, can you import it into gmane,
> > please.
>
> http://userweb.kernel.org/~akpm/lkml-mbox-archives/
I think,
> To be clear I see this as 2 distinct layers of code. enable/disable
> that talks directly to the hardware, and the helpers of enable/disable
> that allocate the irq. I base this on the fact that I only need the
> alloc/free when I am exclusively working with real hardware.
We need the
On Mon, Jan 29, 2007 at 02:26:04AM +0100, Richard Knutsson wrote:
[]
> I also guess you saw that the script is _not_ for cleaning up
> source-files (can be intrusive and is better to be fixed when fixing
> something else), but patches.
IMHO it's dealing with consequences, not cause, and it's
Adrian Bunk wrote:
On Sun, Jan 28, 2007 at 04:04:42PM -0800, David Miller wrote:
From: Adrian Bunk <[EMAIL PROTECTED]>
Date: Mon, 29 Jan 2007 01:00:11 +0100
On Sun, Jan 28, 2007 at 03:53:48PM -0800, David Miller wrote:
Adrian is this the correct way to constrain the selection between
"n" and
Applies to 2.6.20-rc6.
---
libata's SCSI translation for the SCSI START STOP UNIT command with the
START bit clear (i.e. stopping the drive) appears to be incorrect. It
sends an ATA STANDBY command with the time period set to 0, which the
code comment says means "now", but the ATA standard
Oleg Verych wrote:
29-01-2007, Richard Knutsson:
Oleg Verych wrote:
Nack, big and fat. It's userspace problem.
If our "developers" can't use or update their every-day-tools, it's a
shame. And this is not trolling: i'm using Jed and GNU Emacs, both are
ok with whitespace "production".
> From: Rainer Weikusat
> Newsgroups: gmane.linux.kernel
> Subject: Re: unfixed regression in 2.6.20-rc6 (since 2.6.19)
> Date: Sun, 28 Jan 2007 14:34:56 +0100
Hallo.
> Greg KH <[EMAIL PROTECTED]> writes:
[]
>> Please work to see what is wrong with the existing patch. Is there
>> anything that
Patch is against 2.6.20-rc6-mm1, though will also apply to 2.6.20-rc6 if
sata_nv-cleanup-adma-error-handling-v2.patch and
sata_nv-cleanup-adma-error-handling-v2-cleanup.patch from -mm are
applied first. Testing from those who experienced the previous cache
flush timeout problem, in particular,
On Tue, 2007-01-23 at 23:28 +0300, Samium Gromoff wrote:
> Author: Samium Gromoff <[EMAIL PROTECTED]>
> Date: Tue Jan 23 22:31:13 2007 +0300
>
> Define the ELF binary header flag EF_AS_NO_RANDOM
>
> EF_AS_NO_RANDOM should mean that the binary requests to not apply
>
Arjan van de Ven wrote:
On Sun, 2007-01-28 at 17:04 +, Christoph Hellwig wrote:
On Sun, Jan 28, 2007 at 08:52:25AM -0800, Martin J. Bligh wrote:
Mmm. not wholly convinced that's true. Whilst i don't have lockmeter
stats to hand, the heavy time in __d_lookup seems to indicate we may
still
For the beginning, about another (but related) minor problem,
debug_smp_processor_id:
/*
* Kernel threads bound to a single CPU can safely use
* smp_processor_id():
*/
This is only true without CONFIG_HOTPLUG_CPU.
On Sun, 2007-01-28 at 17:04 +, Christoph Hellwig wrote:
> On Sun, Jan 28, 2007 at 08:52:25AM -0800, Martin J. Bligh wrote:
> > Mmm. not wholly convinced that's true. Whilst i don't have lockmeter
> > stats to hand, the heavy time in __d_lookup seems to indicate we may
> > still have a problem
Hi, all
Is there any good idea about this issue?
I really think this is a problem in the NFSv4, which should be resolved
in the latest kernel.
Thank you for any information on this issue.
Hi, all
I have been working on trying to evaluate the robustness of the NFS.
When I run the
> > Because most users won't even be aware of the module option: they'll just
> > know that their card doesn't work right.
>
> This isn't a card problem this is a monitor problem, the card just
> passes through the edid data from the monitor... or else the
> programming of the card registers from
On Sun, Jan 28, 2007 at 09:01:34PM -0200, Eriberto wrote:
> Ok. But, mkswap man is old (1999). However, from Linux Partition HOWTO:
>
> "footnote: "official" max swap size: With kernel 2.4, the limit is 64
> swap spaces at a maximum of 64Gb each, although this is not reflected in
> the man page
On Mon, 29 Jan 2007 11:12:57 +1100
"Dave Airlie" <[EMAIL PROTECTED]> wrote:
> > > Some nVidia video cards have broken EDID information. Using nvidiafb
> > > with CONFIG_FB_NVIDIA_I2C enabled on these systems causes the console
> > > framebuffer to use wrong timing information, causing the display
29-01-2007, Richard Knutsson:
> Oleg Verych wrote:
>> Nack, big and fat. It's userspace problem.
>>
>> If our "developers" can't use or update their every-day-tools, it's a
>> shame. And this is not trolling: i'm using Jed and GNU Emacs, both are
>> ok with whitespace "production".
> Oh, I hope I
On Mon, 29 Jan 2007 11:12:57 +1100
"Dave Airlie" <[EMAIL PROTECTED]> wrote:
> > > Some nVidia video cards have broken EDID information. Using nvidiafb
> > > with CONFIG_FB_NVIDIA_I2C enabled on these systems causes the console
> > > framebuffer to use wrong timing information, causing the display
On Sun, Jan 28, 2007 at 04:04:42PM -0800, David Miller wrote:
> From: Adrian Bunk <[EMAIL PROTECTED]>
> Date: Mon, 29 Jan 2007 01:00:11 +0100
>
> > On Sun, Jan 28, 2007 at 03:53:48PM -0800, David Miller wrote:
> > > Adrian is this the correct way to constrain the selection between
> > > "n" and
On Thu, 25 Jan 2007 16:18:35 -0500, Kristian Høgsberg <[EMAIL PROTECTED]> wrote:
> Indeed, I've just moved to an in-tree development model now. I still think
> the out-off-tree model is a good way to prototype, get started and reach
> "critical mass" with your driver. But as I'm starting to
> Some nVidia video cards have broken EDID information. Using nvidiafb
> with CONFIG_FB_NVIDIA_I2C enabled on these systems causes the console
> framebuffer to use wrong timing information, causing the display to be
> extremely 'snowy'. Since most distribution kernels are compiled with
>
On Sun, 28 Jan 2007 11:48:59 +0100
Giuseppe Bilotta <[EMAIL PROTECTED]> wrote:
> From: Giuseppe Bilotta <[EMAIL PROTECTED]>
>
> Some nVidia video cards have broken EDID information. Using nvidiafb
> with CONFIG_FB_NVIDIA_I2C enabled on these systems causes the console
> framebuffer to use wrong
Oleg Verych wrote:
From: Richard Knutsson
Newsgroups: gmane.linux.kernel
Subject: [SCRIPT] Remove "space damage" from patches
Date: Sun, 28 Jan 2007 22:37:01 +0100
Hello Andrew and all
Hallo.
I recently tried "git-apply" on the 2.6.20-rc6-mm1 patch and found it to
From: Adrian Bunk <[EMAIL PROTECTED]>
Date: Mon, 29 Jan 2007 01:00:11 +0100
> On Sun, Jan 28, 2007 at 03:53:48PM -0800, David Miller wrote:
> > Adrian is this the correct way to constrain the selection between
> > "n" and "m" in this kind of situation? I thought doing something
> > like "depends
Another nfsd patch suitable for 2.6.20, though it could wait for .21
if we feel it is time to be more cautious.
Thanks,
NeilBrown
### Comments for Changeset
Also remove {NFSD,RPC}_PARANOIA as having the defines doesn't
really add anything.
The printks covered by RPC_PARANOIA were tirggered by
On Sun, Jan 28, 2007 at 03:53:48PM -0800, David Miller wrote:
> From: Adrian Bunk <[EMAIL PROTECTED]>
> Date: Sun, 28 Jan 2007 23:21:37 +0100
>
> > On Sun, Jan 28, 2007 at 11:41:48AM -0800, Randy Dunlap wrote:
> > >...
> > > net/built-in.o: In function `q931_help':
> > >
From: Adrian Bunk <[EMAIL PROTECTED]>
Date: Sun, 28 Jan 2007 23:21:37 +0100
> On Sun, Jan 28, 2007 at 11:41:48AM -0800, Randy Dunlap wrote:
> >...
> > net/built-in.o: In function `q931_help':
> > nf_conntrack_h323_main.c:(.text.q931_help+0x6ad): undefined reference to
> > `ip6_route_output'
> >
the statfs header exports some structs to userspace ... the parisc statfs64
struct currently uses u64 so the trivial attached patch fixes it to use __u64
-mike
pgpooYiKlYGyj.pgp
Description: PGP signature
Use __u64 rather than u64 in the struct statfs64 exported to userspace.
Signed-off-by:
From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: Sun, 28 Jan 2007 14:20:12 -0700
> I see people pushing ridiculous interfaces like the RTAS hypervisor
> interface at me, and saying we must support running firmware drivers
> in the msi code.
This is not what's going on.
The hypervisor does the
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Sun, 28 Jan 2007 15:47:24 -0500
> I think the high-level ops approach makes more sense. It's more future
> proof, in addition to covering all existing implementations.
I totally agree with this.
-
To unsubscribe from this list: send the line
On Sun, 28 Jan 2007 15:23:43 -0800
"Martin J. Bligh" <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> > On Sun, 28 Jan 2007 08:56:08 -0800
> > "Martin J. Bligh" <[EMAIL PROTECTED]> wrote:
> >
> >>> - It seems that people have been busy creating the need for this. I had
> >>> to
> >>>
From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: Sun, 28 Jan 2007 16:26:44 -0700
> Yes. In general the mainline linux kernel does not support certain
> classes of stupidity. TCP offload engines, firmware drivers for
> hardware we care about, a fixed ABI to binary only modules, etc.
> It is the
On Sun, 28 Jan 2007 14:47:56 -0800
"Paul E. McKenney" <[EMAIL PROTECTED]> wrote:
> > If we use the process freezer, these bugs all get automatically fixed,
> > and we get to remove the existing locking, and we don't need to think
> > about it any more.
>
> The idea being to essentially suspend
Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
> .../... (enable/disable bits)
>
>> Which are either talking directly to the hardware, or are talking
>> to the hypervisor, which is using hardware isolation so it is safe to
>> talk directly to the hardware but isn't leting us? If we could
Andrew Morton wrote:
On Sun, 28 Jan 2007 08:56:08 -0800
"Martin J. Bligh" <[EMAIL PROTECTED]> wrote:
- It seems that people have been busy creating the need for this. I had to
apply over sixty patches to this tree to fix post-2.6.20-rc4-mm1 compilation
errors. And a number of patches
On Fri, Jan 26, 2007 at 01:29:49PM -0800, Andrew Morton wrote:
> On Sat, 27 Jan 2007 02:14:06 +0530
> Dipankar Sarma <[EMAIL PROTECTED]> wrote:
>
> > On Fri, Jan 26, 2007 at 12:17:39PM -0800, Andrew Morton wrote:
> > > On Sat, 27 Jan 2007 01:16:22 +0530
> > > Dipankar Sarma <[EMAIL PROTECTED]>
On Sun, Jan 28, 2007 at 12:47:18PM +0100, Patrick Ale wrote:
> Hi,
Hi Patrick,
> With kernel 2.6.19 I was able to boot using the pata_via driver
> I tried to compile 2.6.20-rc6 and now I get a "unknown device: sda3"
> error when I try to boot.
>
> I compiled 2.6.20-rc6 by copying over the
On Sun, 28 Jan 2007 23:31:00 +0100
Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> Jan 28 22:58:29 euridica kernel: BUG: using smp_processor_id() in preemptible
> [0001] code: yum-updatesd/2846
> Jan 28 22:58:29 euridica kernel: caller is nf_conntrack_in+0x363/0x47f
> [nf_conntrack]
I'll
One line summary of the problem:
Crash on device_shutdown
Full description of the problem/report:
When I shut down the system, I get a crash on the device_shutdown function
(called by kernel_shutdown_prepare).
Since the bug happens when the system is almost shutted down, I can't get the
log...
> We could have done it for interrupts too. A "struct irqnum" that has a bit
> that specifies "valid". That would work. But it tends to be painful, so it
> really has to give you something more than "zero is disabled".
>
> It's just not worth it.
>
> And it's why I decreed, that the ONLY SANE
Ok. But, mkswap man is old (1999). However, from Linux Partition HOWTO:
"footnote: "official" max swap size: With kernel 2.4, the limit is 64
swap spaces at a maximum of 64Gb each, although this is not reflected in
the man page for mkswap. With the 64 bit opteron on the 2.6 kernel, 128
swap areas
On Sun, 28 Jan 2007 08:56:08 -0800
"Martin J. Bligh" <[EMAIL PROTECTED]> wrote:
> > - It seems that people have been busy creating the need for this. I had to
> > apply over sixty patches to this tree to fix post-2.6.20-rc4-mm1
> > compilation
> > errors. And a number of patches were
> However, in all honesty, we have triggered bugs in that area too, simply
> because some driver code "knew" that PIO addresses could fit in 16 bits,
> and used u16 or "unsigned short" to remember the PIO address. Both ARM and
> Sparc was bitten by this, although usually the issue is trivial to
> On sparc64, for example, after I pointed this out to DaveM, he was able
> to implement the new iomap interface without the 'if (pio-mem-area)'
> branch present on x86.
Yup, we did that from day 1 on powerpc :-) However, I don't totally
agree with adding some other remapping layer here, I
> From: Richard Knutsson
> Newsgroups: gmane.linux.kernel
> Subject: [SCRIPT] Remove "space damage" from patches
> Date: Sun, 28 Jan 2007 22:37:01 +0100
> Hello Andrew and all
Hallo.
> I recently tried "git-apply" on the 2.6.20-rc6-mm1 patch and found it to
> complain about white-spaces.
> So
> Indeed. Zero means "not in use". It really is that simple.
I tried to avoid stepping into that specific flamewar as I don't have
strong opinions either way, but I've been asked to so ... and there are
a few things in your statement that I do like to argue about a bit :-)
> And I'm sorry,
Eriberto <[EMAIL PROTECTED]> wrote:
> I am trying understand the swap. I would like to know which is the
> maximum swap size on i386. Is 64 MB? If yes, how to know the origin of
> this "magic" number? I don't found it (Internet).
Look into the manpage of mkswap. It's 2 G x 32 swap partitions,
> From: "Parag Warudkar"
> Newsgroups: gmane.linux.kernel
> Subject: Re: git.kernel.org move (finally)... estimated week of Feb 5
> Date: Sun, 28 Jan 2007 11:51:34 -0500
[]
> Actually that's a good idea - why don't we put up a
> donation-for-hardware appeal on kernel.org and may be someplace more
On 1/28/07, Parag Warudkar <[EMAIL PROTECTED]> wrote:
>CONFIG_BINFMT_ELF=y
># CONFIG_BINFMT_MISC is not set
># CONFIG_IA32_EMULATION is not set
Hm Ok. That's explainable. You don't have CONFIG_IA32_EMULATION set
and arch_setup_additional pages is only defined/exported in
syscall32.c which won't
> Path: news.gmane.org!not-for-mail
> From: Andrey Borzenkov <[EMAIL PROTECTED]>
> Newsgroups: gmane.linux.kernel
> Date: Sun, 28 Jan 2007 20:24:43 +0300
Hallo.
> Benny Amorsen wrote:
>
>>> "DK" == Dave Kleikamp <[EMAIL PROTECTED]> writes:
>>
>> DK> On Sun, 2007-01-28 at 10:17 +0100, Benny
One line summary of the problem:
Crash on sysfs_follow_link
Full description of the problem/report:
When the hald deamon is started, it crashes on the sysfs_follow_link function.
Here's the log (from /var/log/kern.log) :
Jan 28 22:51:58 localhost kernel: BUG: unable to handle kernel NULL pointer
Wakko Warner wrote:
I have 2 machine that oops with these cards.
1) The bios has the option to enable/disable option roms on individual PCI
slots. I have an AHA-39160 and an AHA-2940U/UW (dual channel). If I
disable option roms, the driver oopses when accessing the 2nd card.
I can get the
Andrew Morton napisał(a):
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.20-rc6-mm1/
>
> will appear one day at
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm1/
>
>
Jan 28 22:58:29 euridica kernel: BUG: using
On Sun, 28 Jan 2007 15:11:34 +0100
Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> Eradicate global locks.
>
> - kmap_lock is removed by extensive use of atomic_t, a new flush
>scheme and modifying set_page_address to only allow NULL<->virt
>transitions.
>
> A count of 0 is an exclusive
On Sunday 28 January 2007 12:42, Randy Dunlap wrote:
> Have you now audited all ioctls (and sent patches) for this misbehavior?
my audit involved grepping the headers for '\<[us](8|16|32|64)\>' and sending
patches for the headers that came up
ive sent patches for all except for
On Sun, Jan 28, 2007 at 11:41:48AM -0800, Randy Dunlap wrote:
>...
> net/built-in.o: In function `q931_help':
> nf_conntrack_h323_main.c:(.text.q931_help+0x6ad): undefined reference to
> `ip6_route_output'
> nf_conntrack_h323_main.c:(.text.q931_help+0x6c3): undefined reference to
>
Paul Mackerras <[EMAIL PROTECTED]> writes:
> Eric W. Biederman writes:
>
>> @@ -693,15 +664,14 @@ int pci_enable_msi(struct pci_dev* dev)
>> if (!pos)
>> return -EINVAL;
>>
>> -WARN_ON(!msi_lookup_irq(dev, PCI_CAP_ID_MSI));
>> +WARN_ON(!!dev->msi_enabled);
>
> Minor
Dan Williams wrote:
> On Fri, 2007-01-26 at 21:48 -0600, Larry Finger wrote:
>> Is there a convention regarding the information that a wireless MAC layer
>> should provide when
>> reporting scan data from an AP with a hidden SSID?
>>
>> In ieee80211, the software inserts the string "" for such an
Jeff Garzik <[EMAIL PROTECTED]> writes:
> I think the high-level ops approach makes more sense. It's more future proof,
> in addition to covering all existing implementations.
To be precise in Michaels implementation one of the parameters passed is
a type parameter so that the architecture has
Eric W. Biederman writes:
> @@ -693,15 +664,14 @@ int pci_enable_msi(struct pci_dev* dev)
> if (!pos)
> return -EINVAL;
>
> - WARN_ON(!msi_lookup_irq(dev, PCI_CAP_ID_MSI));
> + WARN_ON(!!dev->msi_enabled);
Minor nit: what's wrong with just WARN_ON(dev->msi_enabled)
On Sat, 2007-01-27 at 23:44 +0100, Thomas Gleixner wrote:
> > If its a regression, what changeset caused the problem?
>
> Hey. I just discovered that crap. I'm going to bisect tomorrow. Bed time
> here in good old Europe. :)
It seems to be there in 2.6.18 already, although it takes more
1 - 100 of 498 matches
Mail list logo
