On Sunday 07 January 2007 00:36, Pavel Machek wrote:
[snip]
> > However, this patch is mostly useless if you have a separate stack for
> > IRQ's (since if that happens, any interrupt will be taken on a different
> > stack which we don't see any more), so you should NOT enable the 4KSTACKS
> > config option if you try this out.
>
> stupid idea... perhaps gcc-4.1 generates bigger stackframe somewhere,
> and stack overflows?
The primary reason it's not 4KSTACKS already is that I run multiple XFS
partitions on top of an md RAID 1. LVM isn't involved, however, and I'm not
using any other filesystem overlays like dm.
I'm fairly sceptical that it's a stack overflow, but I'll be sure to enable
the debugging option on the next try.
> that hw monitoring thingie... I'd turn it off. Its interactions with
> acpi are non-trivial and dangerous.
Well, GCC 3.4 kernels seem to run fine with it, but as I said to Linus I'll be
sure to turn this and the sound drivers off in the next build.
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]