On Mon, 15 Aug 2005, Harald Welte wrote:
> On Sun, Aug 14, 2005 at 08:15:53PM -0600, Zwane Mwaikambo wrote:
>
> > Is the following patch correct? ip_conntrack_event_cache should never be
> > called with ip_conntrack_lock held and ct_add_counters does not need to be
> > called with ip_conntrack_
On Sun, Aug 14, 2005 at 08:15:53PM -0600, Zwane Mwaikambo wrote:
> Is the following patch correct? ip_conntrack_event_cache should never be
> called with ip_conntrack_lock held and ct_add_counters does not need to be
> called with ip_conntrack_lock held.
No, it's not correct. ct_add_countes ha
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}
> {_write_l
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}
>{:
On Mon, Aug 08, 2005 at 07:06:50PM -0500, James Bottomley wrote:
> On Mon, 2005-08-08 at 10:42 -0700, Andrew Morton wrote:
> > -mm has extra list_head debugging goodies. I'd be suspecting a list_head
> > corruption detected somewhere under spi_release_transport().
>
> Aha, looking in wrong driver
On Mon, 2005-08-08 at 10:42 -0700, Andrew Morton wrote:
> -mm has extra list_head debugging goodies. I'd be suspecting a list_head
> corruption detected somewhere under spi_release_transport().
Aha, looking in wrong driver ... the problem actually appears to be a
double release of the transport t
James Bottomley <[EMAIL PROTECTED]> wrote:
>
> On Mon, 2005-08-08 at 19:11 +0200, Andi Kleen wrote:
> > Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?
>
> The traceback looks pretty meaningless.
>
> What was happening on the machine before this. i.e. was it booting up
On Mon, Aug 08, 2005 at 12:33:29PM -0500, James Bottomley wrote:
> On Mon, 2005-08-08 at 19:11 +0200, Andi Kleen wrote:
> > Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?
>
> The traceback looks pretty meaningless.
>
> What was happening on the machine before this. i.
On Mon, 2005-08-08 at 19:11 +0200, Andi Kleen wrote:
> Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?
The traceback looks pretty meaningless.
What was happening on the machine before this. i.e. was it booting up,
in which case can we have the prior dmesg file; or was
On Mon, Aug 08, 2005 at 07:11:26PM +0200, Andi Kleen wrote:
> On Mon, Aug 08, 2005 at 09:48:19AM -0700, Ashok Raj wrote:
> > Folks,
> >
> > Iam getting this on the recent 2.6.12-rc5-mm1 kernel built with defconfig.
> >
> > Cheers,
> > Ashok Raj
> >
> > --- [cut here ] - [please
On Mon, Aug 08, 2005 at 09:48:19AM -0700, Ashok Raj wrote:
> Folks,
>
> Iam getting this on the recent 2.6.12-rc5-mm1 kernel built with defconfig.
>
> Cheers,
> Ashok Raj
>
> --- [cut here ] - [please bite here ] -
> Kernel BUG at "include/linux/list.h":165
> invalid ope
> > > I don't think it was supposed to do that.
> > >
> > > Quite possibly it's something to do with the new debugging code - could
> > you
> > > please take a copy of the offending config, send it over and then try
> > > removing debug options, see if the crash goes away? CONFIG_DEBUG_PREEM
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> - This kernel is broken on ia64: the spinlock consolidation patch
> needs fixing.
ia64 had a couple of other compilation problems as well. The patch below
fixes the spinlock-type issues and 3 other types of build errors. The
patched kernel builds
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > I don't think it was supposed to do that.
> >
> > Quite possibly it's something to do with the new debugging code - could you
> > please take a copy of the offending config, send it over and then try
> > removing debug options, see if the cr
Rogério Brito <[EMAIL PROTECTED]> wrote:
>
> Thanks Andrew, for including the vfat speedup patch.
>
> It has really improved a lot the performance of access to directories
> having many subdirectories in an external Firewire HD that I have.
>
> I'd say that if others don't have problems with it,
Thanks Andrew, for including the vfat speedup patch.
It has really improved a lot the performance of access to directories
having many subdirectories in an external Firewire HD that I have.
I'd say that if others don't have problems with it, then it should be
in 2.6.13, as far as I am concerned.
On Sunday, 7 of August 2005 19:23, Andrew Morton wrote:
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> >
> > I get the following Oops after trying to start nscd from YaST on an
> > Athlon64-based box
> > (compiled with CONFIG_DEBUG_SPINLOCK=y):
> >
> > Unable to handle kernel NULL pointer d
On 8/7/05, Andrew Morton <[EMAIL PROTECTED]> wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc5/2.6.13-rc5-mm1/
I probably don't need/want phy stuff anyhow, but when I tried it:
Problem:
drivers/built-in.o: In function `phy_start_machine':
: undefined reference to `
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> I get the following Oops after trying to start nscd from YaST on an
> Athlon64-based box
> (compiled with CONFIG_DEBUG_SPINLOCK=y):
>
> Unable to handle kernel NULL pointer dereference at 0008 RIP:
> {kmem_cache_alloc+232}
> PGD 1
19 matches
Mail list logo
