From cebbert at redhat.com Wed Apr 1 22:23:52 2009 From: cebbert at redhat.com (Chuck Ebbert) Date: Wed, 1 Apr 2009 18:23:52 -0400 Subject: Patch incomplete write error not returned to NFS client In-Reply-To: References: Message-ID: <20090401182352.033bebc8@dhcp-100-2-144.bos.redhat.com> On Tue, 24 Mar 2009 16:17:24 -0400 Victor wrote: > Request for integrating this patch into the next kernel update for > Fedora 10. The patch fixes a bug in NFS where an error will not be > returned to the NFS client when an incomplete write happens at the > filesystem level on the server. > > http://git.linux-nfs.org/?p=bfields/linux.git;a=commitdiff;h=192a3cb6bc1f12a0af55bcf2fbb6e923d48a5b58;hp=82f69c6c0efae204dbf428f5c93fcc8d088696c2 > Please file a bug against Fedora 10 in bugzilla so we can track this. From aksdb at gmx.de Thu Apr 2 08:32:40 2009 From: aksdb at gmx.de (Andreas Schneider) Date: Thu, 2 Apr 2009 10:32:40 +0200 Subject: TuxOnIce in the official Fedora Kernel? Message-ID: <20090402103240.721b157f@netmaster> Hello, I'm using Fedora on two laptops for quite some time now (since F8). Having used suspend-to-disk very often I can conclude, that I'm not happy with the performance it shows. Suspending a laptop with just 1GB of memory takes about 30 to 60 seconds here and nearly the same for resuming. The same laptop on Windows (sorry ;-)) got it done in about 10 seconds each. What I did some time ago, was to switch to the TuxOnIce[1] patched kernels from atrpms. Not only does TuxOnIce show a progressbar (even with splash if wanted) during suspend and resume, it also handles the process in the expected 10 to 15 seconds. Since Fedora patches the Kernel anyway, I propose adding TuxOnIce (also known as Suspend2) into the official Fedora Kernel. It doesn't hurt those who don't use suspend-to-disk anyway but benefits those who do. Also it could probably rather easy be integrated with Plymouth to show a nice animation during suspend and resume. (Though that would be optional :-P) I hope you take at least the time to consider it for a few moments. Thanks in Advance, Andreas Schneider. [1] http://www.tuxonice.net/ From jwboyer at gmail.com Thu Apr 2 11:31:53 2009 From: jwboyer at gmail.com (Josh Boyer) Date: Thu, 2 Apr 2009 07:31:53 -0400 Subject: TuxOnIce in the official Fedora Kernel? In-Reply-To: <20090402103240.721b157f@netmaster> References: <20090402103240.721b157f@netmaster> Message-ID: <20090402113153.GA9667@yoda.jdub.homelinux.org> On Thu, Apr 02, 2009 at 10:32:40AM +0200, Andreas Schneider wrote: >Hello, > >I'm using Fedora on two laptops for quite some time now (since F8). >Having used suspend-to-disk very often I can conclude, that I'm not >happy with the performance it shows. Suspending a laptop with just >1GB of memory takes about 30 to 60 seconds here and nearly the same >for resuming. The same laptop on Windows (sorry ;-)) got it done in >about 10 seconds each. >What I did some time ago, was to switch to the TuxOnIce[1] patched >kernels from atrpms. Not only does TuxOnIce show a progressbar (even >with splash if wanted) during suspend and resume, it also handles >the process in the expected 10 to 15 seconds. > >Since Fedora patches the Kernel anyway, I propose adding TuxOnIce It's patched very minimally. The two largest items are execshield and utrace. Aside from that, patches actually tend to be fixes, not features. >(also known as Suspend2) into the official Fedora Kernel. It doesn't >hurt those who don't use suspend-to-disk anyway but benefits those >who do. >Also it could probably rather easy be integrated with Plymouth to >show a nice animation during suspend and resume. (Though that would >be optional :-P) I think the best option is for either TuxOnIce to get into the kernel.org kernel, or to fix the problems with the existing suspend framework. >I hope you take at least the time to consider it for a few moments. I won't speak for the Fedora kernel team, but I can't see them really wanting to add this. josh From mjg at redhat.com Thu Apr 2 11:32:13 2009 From: mjg at redhat.com (Matthew Garrett) Date: Thu, 2 Apr 2009 12:32:13 +0100 Subject: TuxOnIce in the official Fedora Kernel? In-Reply-To: <20090402103240.721b157f@netmaster> References: <20090402103240.721b157f@netmaster> Message-ID: <20090402113212.GA28314@srcf.ucam.org> On Thu, Apr 02, 2009 at 10:32:40AM +0200, Andreas Schneider wrote: > Since Fedora patches the Kernel anyway, I propose adding TuxOnIce > (also known as Suspend2) into the official Fedora Kernel. It doesn't > hurt those who don't use suspend-to-disk anyway but benefits those > who do. We patch the kernel, but generally not with code that's proven controversial upstream. There's still no sign of the suspend2 code going into the mainline kernel which means that we're unlikely to include it. -- Matthew Garrett | mjg59 at srcf.ucam.org From jeremy at jeremysanders.net Tue Apr 7 20:44:19 2009 From: jeremy at jeremysanders.net (Jeremy Sanders) Date: Tue, 07 Apr 2009 21:44:19 +0100 Subject: EDAC on AMD with Fedora 10 Message-ID: Is there any reason the amd76x_edac module doesn't appear in the Fedora 10 kernel RPM? As far as I can see it should be being built from the configuration. We've got an AMD 790X based motherboard which doesn't seem to have any Fedora 10 support for ECC RAM. Jeremy From mtosatti at redhat.com Wed Apr 8 22:00:15 2009 From: mtosatti at redhat.com (Marcelo Tosatti) Date: Wed, 8 Apr 2009 19:00:15 -0300 Subject: [PATCH] FC11: fix rh#491625 (Unable to run RHEL-5 Xen within KVM guest) Message-ID: <20090408220015.GA17778@amt.cnet> Following adds a fix for $subject. Please review. Don't have commit access yet so unable to commit myself. TODO | 7 + kernel.spec | 15 +++ linux-2.6-kvm-kconfig-irqchip.patch | 69 ++++++++++++++++ linux-2.6-kvm-mask-notifiers.patch | 117 ++++++++++++++++++++++++++++ linux-2.6-kvm-reset-pit-irq-on-unmask.patch | 67 ++++++++++++++++ 5 files changed, 275 insertions(+) -------------- next part -------------- Index: F-11/TODO =================================================================== --- F-11.orig/TODO +++ F-11/TODO @@ -102,3 +102,10 @@ * linux-2.6.29-pat-fixes.patch: http://bugs.freedesktop.org/show_bug.cgi?id=20803 ajax to follow up with jbarnes + +* linux-2.6-kvm-kconfig-irqchip.patch +* linux-2.6-kvm-mask-notifiers.patch +* linux-2.6-kvm-reset-pit-irq-on-unmask.patch: + https://bugzilla.redhat.com/show_bug.cgi?id=491625 + Queued by Avi, needs to get into linux-2.6-stable. + Index: F-11/kernel.spec =================================================================== --- F-11.orig/kernel.spec +++ F-11/kernel.spec @@ -720,6 +720,11 @@ Patch9101: linux-2.6-net-fix-another-gro # http://bugs.freedesktop.org/show_bug.cgi?id=20803 Patch9210: linux-2.6.29-pat-fixes.patch +# kvm fixes +Patch9300: linux-2.6-kvm-kconfig-irqchip.patch +Patch9301: linux-2.6-kvm-mask-notifiers.patch +Patch9302: linux-2.6-kvm-reset-pit-irq-on-unmask.patch + %endif BuildRoot: %{_tmppath}/kernel-%{KVERREL}-root @@ -1320,6 +1325,10 @@ ApplyPatch linux-2.6-net-fix-another-gro ApplyPatch linux-2.6.29-pat-fixes.patch +ApplyPatch linux-2.6-kvm-kconfig-irqchip.patch +ApplyPatch linux-2.6-kvm-mask-notifiers.patch +ApplyPatch linux-2.6-kvm-reset-pit-irq-on-unmask.patch + # END OF PATCH APPLICATIONS %endif @@ -1905,6 +1914,12 @@ fi # and build. %changelog +* Wed Apr 08 2009 Marcelo Tosatti +- linux-2.6-kvm-kconfig-irqchip.patch + linux-2.6-kvm-mask-notifiers.patch + linux-2.6-kvm-reset-pit-irq-on-unmask.patch: + Fixes PIT bug with Xen on KVM (rh#491625). + * Wed Apr 08 2009 Dave Jones 2.6.29.1-58 - disable MMIOTRACE in non-debug builds (#494584) Index: F-11/linux-2.6-kvm-mask-notifiers.patch =================================================================== --- /dev/null +++ F-11/linux-2.6-kvm-mask-notifiers.patch @@ -0,0 +1,117 @@ +b018d32632d3c59d3618e23128e4312fe8e48d64 +diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h +index 3cf0ede..99963f3 100644 +--- a/include/linux/kvm_host.h ++++ b/include/linux/kvm_host.h +@@ -127,6 +127,10 @@ struct kvm { + struct kvm_coalesced_mmio_ring *coalesced_mmio_ring; + #endif + ++#ifdef CONFIG_HAVE_KVM_IRQCHIP ++ struct hlist_head mask_notifier_list; ++#endif ++ + #ifdef KVM_ARCH_WANT_MMU_NOTIFIER + struct mmu_notifier mmu_notifier; + unsigned long mmu_notifier_seq; +@@ -320,6 +324,19 @@ struct kvm_assigned_dev_kernel { + struct pci_dev *dev; + struct kvm *kvm; + }; ++ ++struct kvm_irq_mask_notifier { ++ void (*func)(struct kvm_irq_mask_notifier *kimn, bool masked); ++ int irq; ++ struct hlist_node link; ++}; ++ ++void kvm_register_irq_mask_notifier(struct kvm *kvm, int irq, ++ struct kvm_irq_mask_notifier *kimn); ++void kvm_unregister_irq_mask_notifier(struct kvm *kvm, int irq, ++ struct kvm_irq_mask_notifier *kimn); ++void kvm_fire_mask_notifiers(struct kvm *kvm, int irq, bool mask); ++ + void kvm_set_irq(struct kvm *kvm, int irq_source_id, int irq, int level); + void kvm_notify_acked_irq(struct kvm *kvm, unsigned gsi); + void kvm_register_irq_ack_notifier(struct kvm *kvm, +diff --git a/virt/kvm/ioapic.c b/virt/kvm/ioapic.c +index 23b81cf..e85a2bc 100644 +--- a/virt/kvm/ioapic.c ++++ b/virt/kvm/ioapic.c +@@ -101,6 +101,7 @@ static void ioapic_service(struct kvm_ioapic *ioapic, unsigned int idx) + static void ioapic_write_indirect(struct kvm_ioapic *ioapic, u32 val) + { + unsigned index; ++ bool mask_before, mask_after; + + switch (ioapic->ioregsel) { + case IOAPIC_REG_VERSION: +@@ -120,6 +121,7 @@ static void ioapic_write_indirect(struct kvm_ioapic *ioapic, u32 val) + ioapic_debug("change redir index %x val %x\n", index, val); + if (index >= IOAPIC_NUM_PINS) + return; ++ mask_before = ioapic->redirtbl[index].fields.mask; + if (ioapic->ioregsel & 1) { + ioapic->redirtbl[index].bits &= 0xffffffff; + ioapic->redirtbl[index].bits |= (u64) val << 32; +@@ -128,6 +130,9 @@ static void ioapic_write_indirect(struct kvm_ioapic *ioapic, u32 val) + ioapic->redirtbl[index].bits |= (u32) val; + ioapic->redirtbl[index].fields.remote_irr = 0; + } ++ mask_after = ioapic->redirtbl[index].fields.mask; ++ if (mask_before != mask_after) ++ kvm_fire_mask_notifiers(ioapic->kvm, index, mask_after); + if (ioapic->irr & (1 << index)) + ioapic_service(ioapic, index); + break; +@@ -426,3 +431,4 @@ int kvm_ioapic_init(struct kvm *kvm) + kvm_io_bus_register_dev(&kvm->mmio_bus, &ioapic->dev); + return 0; + } ++ +diff --git a/virt/kvm/irq_comm.c b/virt/kvm/irq_comm.c +index aa5d1e5..5162a41 100644 +--- a/virt/kvm/irq_comm.c ++++ b/virt/kvm/irq_comm.c +@@ -99,3 +99,27 @@ void kvm_free_irq_source_id(struct kvm *kvm, int irq_source_id) + clear_bit(irq_source_id, &kvm->arch.irq_states[i]); + clear_bit(irq_source_id, &kvm->arch.irq_sources_bitmap); + } ++ ++void kvm_register_irq_mask_notifier(struct kvm *kvm, int irq, ++ struct kvm_irq_mask_notifier *kimn) ++{ ++ kimn->irq = irq; ++ hlist_add_head(&kimn->link, &kvm->mask_notifier_list); ++} ++ ++void kvm_unregister_irq_mask_notifier(struct kvm *kvm, int irq, ++ struct kvm_irq_mask_notifier *kimn) ++{ ++ hlist_del(&kimn->link); ++} ++ ++void kvm_fire_mask_notifiers(struct kvm *kvm, int irq, bool mask) ++{ ++ struct kvm_irq_mask_notifier *kimn; ++ struct hlist_node *n; ++ ++ hlist_for_each_entry(kimn, n, &kvm->mask_notifier_list, link) ++ if (kimn->irq == irq) ++ kimn->func(kimn, mask); ++} ++ +diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c +index dcbfc68..785c1e3 100644 +--- a/virt/kvm/kvm_main.c ++++ b/virt/kvm/kvm_main.c +@@ -831,6 +831,9 @@ static struct kvm *kvm_create_vm(void) + + if (IS_ERR(kvm)) + goto out; ++#ifdef CONFIG_HAVE_KVM_IRQCHIP ++ INIT_HLIST_HEAD(&kvm->mask_notifier_list); ++#endif + + #ifdef KVM_COALESCED_MMIO_PAGE_OFFSET + page = alloc_page(GFP_KERNEL | __GFP_ZERO); Index: F-11/linux-2.6-kvm-reset-pit-irq-on-unmask.patch =================================================================== --- /dev/null +++ F-11/linux-2.6-kvm-reset-pit-irq-on-unmask.patch @@ -0,0 +1,67 @@ +commit 4780c65904f0fc4e312ee2da9383eacbe04e61ea +Author: Avi Kivity +Date: Sun Jan 4 18:06:06 2009 +0200 + + KVM: Reset PIT irq injection logic when the PIT IRQ is unmasked + + While the PIT is masked the guest cannot ack the irq, so the reinject logic + will never allow the interrupt to be injected. + + Fix by resetting the reinjection counters on unmask. + + Unbreaks Xen. + + Signed-off-by: Avi Kivity + +diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c +index 69d1bbf..c13bb92 100644 +--- a/arch/x86/kvm/i8254.c ++++ b/arch/x86/kvm/i8254.c +@@ -539,6 +539,16 @@ void kvm_pit_reset(struct kvm_pit *pit) + pit->pit_state.irq_ack = 1; + } + ++static void pit_mask_notifer(struct kvm_irq_mask_notifier *kimn, bool mask) ++{ ++ struct kvm_pit *pit = container_of(kimn, struct kvm_pit, mask_notifier); ++ ++ if (!mask) { ++ atomic_set(&pit->pit_state.pit_timer.pending, 0); ++ pit->pit_state.irq_ack = 1; ++ } ++} ++ + struct kvm_pit *kvm_create_pit(struct kvm *kvm) + { + struct kvm_pit *pit; +@@ -586,6 +596,9 @@ struct kvm_pit *kvm_create_pit(struct kvm *kvm) + + kvm_pit_reset(pit); + ++ pit->mask_notifier.func = pit_mask_notifer; ++ kvm_register_irq_mask_notifier(kvm, 0, &pit->mask_notifier); ++ + return pit; + } + +@@ -594,6 +607,8 @@ void kvm_free_pit(struct kvm *kvm) + struct hrtimer *timer; + + if (kvm->arch.vpit) { ++ kvm_unregister_irq_mask_notifier(kvm, 0, ++ &kvm->arch.vpit->mask_notifier); + mutex_lock(&kvm->arch.vpit->pit_state.lock); + timer = &kvm->arch.vpit->pit_state.pit_timer.timer; + hrtimer_cancel(timer); +diff --git a/arch/x86/kvm/i8254.h b/arch/x86/kvm/i8254.h +index 76959c4..6acbe4b 100644 +--- a/arch/x86/kvm/i8254.h ++++ b/arch/x86/kvm/i8254.h +@@ -46,6 +46,7 @@ struct kvm_pit { + struct kvm *kvm; + struct kvm_kpit_state pit_state; + int irq_source_id; ++ struct kvm_irq_mask_notifier mask_notifier; + }; + + #define KVM_PIT_BASE_ADDRESS 0x40 Index: F-11/linux-2.6-kvm-kconfig-irqchip.patch =================================================================== --- /dev/null +++ F-11/linux-2.6-kvm-kconfig-irqchip.patch @@ -0,0 +1,69 @@ +commit 1dae8e15bb85de0116ed43cd3d798a035044954c +Author: Avi Kivity +Date: Sun Jan 4 18:04:18 2009 +0200 + + KVM: Add CONFIG_HAVE_KVM_IRQCHIP + + Two KVM archs support irqchips and two don't. Add a Kconfig item to + make selecting between the two models easier. + + Signed-off-by: Avi Kivity + +diff --git a/arch/ia64/kvm/Kconfig b/arch/ia64/kvm/Kconfig +index f833a0b..0a2d6b8 100644 +--- a/arch/ia64/kvm/Kconfig ++++ b/arch/ia64/kvm/Kconfig +@@ -4,6 +4,10 @@ + config HAVE_KVM + bool + ++config HAVE_KVM_IRQCHIP ++ bool ++ default y ++ + menuconfig VIRTUALIZATION + bool "Virtualization" + depends on HAVE_KVM || IA64 +diff --git a/arch/powerpc/kvm/Kconfig b/arch/powerpc/kvm/Kconfig +index 1465705..5a152a5 100644 +--- a/arch/powerpc/kvm/Kconfig ++++ b/arch/powerpc/kvm/Kconfig +@@ -2,6 +2,9 @@ + # KVM configuration + # + ++config HAVE_KVM_IRQCHIP ++ bool ++ + menuconfig VIRTUALIZATION + bool "Virtualization" + ---help--- +diff --git a/arch/s390/kvm/Kconfig b/arch/s390/kvm/Kconfig +index e051cad..3e260b7 100644 +--- a/arch/s390/kvm/Kconfig ++++ b/arch/s390/kvm/Kconfig +@@ -4,6 +4,9 @@ + config HAVE_KVM + bool + ++config HAVE_KVM_IRQCHIP ++ bool ++ + menuconfig VIRTUALIZATION + bool "Virtualization" + default y +diff --git a/arch/x86/kvm/Kconfig b/arch/x86/kvm/Kconfig +index b81125f..0a303c3 100644 +--- a/arch/x86/kvm/Kconfig ++++ b/arch/x86/kvm/Kconfig +@@ -4,6 +4,10 @@ + config HAVE_KVM + bool + ++config HAVE_KVM_IRQCHIP ++ bool ++ default y ++ + menuconfig VIRTUALIZATION + bool "Virtualization" + depends on HAVE_KVM || X86 From davej at redhat.com Wed Apr 8 22:08:43 2009 From: davej at redhat.com (Dave Jones) Date: Wed, 8 Apr 2009 18:08:43 -0400 Subject: [PATCH] FC11: fix rh#491625 (Unable to run RHEL-5 Xen within KVM guest) In-Reply-To: <20090408220015.GA17778@amt.cnet> References: <20090408220015.GA17778@amt.cnet> Message-ID: <20090408220843.GC9888@redhat.com> On Wed, Apr 08, 2009 at 07:00:15PM -0300, Marcelo Tosatti wrote: > > Following adds a fix for $subject. Please review. Looks fine to me, as long as it's been tested. > Don't have commit access yet so unable to commit myself. https://fedoraproject.org/wiki/Kernel#Contributing_to_the_Fedora_kernel has all the details. We can hook you up. Dave From doug.chapman at hp.com Tue Apr 14 12:18:40 2009 From: doug.chapman at hp.com (Doug Chapman) Date: Tue, 14 Apr 2009 08:18:40 -0400 Subject: [PATCH] squashfs broken when pageszie > blocksize Message-ID: <1239711520.1127.32.camel@oberon> Not sure if we are too late for F11 on this or not but this patch is needed to be able to mount squashfs (as used by anaconda) on ia64. Our goal is to be able to build Fedora on ia64 with no custom SRPMs so it would be appreciated if this could be pulled in. -------------------- Squashfs is broken on any system where the pageszie is larger than either the block size of the squashfs image or larger than the metadata size (8192). This is easily fixed by ensuring cache->pages is always > 0. Signed-off-by: Doug Chapman Cc: Phillip Lougher --- diff --git a/fs/squashfs/cache.c b/fs/squashfs/cache.c index 1c4739e..40c98fa 100644 --- a/fs/squashfs/cache.c +++ b/fs/squashfs/cache.c @@ -252,6 +252,7 @@ struct squashfs_cache *squashfs_cache_init(char *name, int entries, cache->entries = entries; cache->block_size = block_size; cache->pages = block_size >> PAGE_CACHE_SHIFT; + cache->pages = cache->pages ? cache->pages : 1; cache->name = name; cache->num_waiters = 0; spin_lock_init(&cache->lock); From jwboyer at gmail.com Tue Apr 14 12:57:07 2009 From: jwboyer at gmail.com (Josh Boyer) Date: Tue, 14 Apr 2009 08:57:07 -0400 Subject: [PATCH] squashfs broken when pageszie > blocksize In-Reply-To: <1239711520.1127.32.camel@oberon> References: <1239711520.1127.32.camel@oberon> Message-ID: <20090414125707.GB2427@yoda.jdub.homelinux.org> On Tue, Apr 14, 2009 at 08:18:40AM -0400, Doug Chapman wrote: >Not sure if we are too late for F11 on this or not but this patch >is needed to be able to mount squashfs (as used by anaconda) on >ia64. Our goal is to be able to build Fedora on ia64 with no >custom SRPMs so it would be appreciated if this could be pulled >in. It would be needed for ppc64 kernels using a 64KiB pagesize as well from what I can see. Sounds like a good idea to me. josh From jarod at redhat.com Tue Apr 14 14:14:05 2009 From: jarod at redhat.com (Jarod Wilson) Date: Tue, 14 Apr 2009 10:14:05 -0400 Subject: [PATCH] squashfs broken when pageszie > blocksize In-Reply-To: <20090414125707.GB2427@yoda.jdub.homelinux.org> References: <1239711520.1127.32.camel@oberon> <20090414125707.GB2427@yoda.jdub.homelinux.org> Message-ID: <200904141014.06353.jarod@redhat.com> On Tuesday 14 April 2009 08:57:07 Josh Boyer wrote: > On Tue, Apr 14, 2009 at 08:18:40AM -0400, Doug Chapman wrote: > >Not sure if we are too late for F11 on this or not but this patch > >is needed to be able to mount squashfs (as used by anaconda) on > >ia64. Our goal is to be able to build Fedora on ia64 with no > >custom SRPMs so it would be appreciated if this could be pulled > >in. > > It would be needed for ppc64 kernels using a 64KiB pagesize as well > from what I can see. Sounds like a good idea to me. Committed to the F11 branch. Not needed for F10 and earlier, since they're still using squashfs v3, even for the 2.6.29.x builds. Will just let it trickle in via upstream for the devel branch. -- Jarod Wilson jarod at redhat.com From cebbert at redhat.com Tue Apr 14 21:27:32 2009 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 14 Apr 2009 17:27:32 -0400 Subject: EDAC on AMD with Fedora 10 In-Reply-To: References: Message-ID: <20090414172732.70319b27@dhcp-100-2-144.bos.redhat.com> On Tue, 07 Apr 2009 21:44:19 +0100 Jeremy Sanders wrote: > Is there any reason the amd76x_edac module doesn't appear in the Fedora 10 > kernel RPM? As far as I can see it should be being built from the > configuration. > > We've got an AMD 790X based motherboard which doesn't seem to have any > Fedora 10 support for ECC RAM. > According to the kernel Kconfig file it's only available for old 32-bit Athlons, and it is in the i686 kernel(s). config EDAC_AMD76X tristate "AMD 76x (760, 762, 768)" depends on EDAC_MM_EDAC && PCI && X86_32 help Support for error detection and correction on the AMD 76x series of chipsets used with the Athlon processor. From jeremy at jeremysanders.net Wed Apr 15 09:13:36 2009 From: jeremy at jeremysanders.net (Jeremy Sanders) Date: Wed, 15 Apr 2009 10:13:36 +0100 Subject: EDAC on AMD with Fedora 10 References: <20090414172732.70319b27@dhcp-100-2-144.bos.redhat.com> Message-ID: Chuck Ebbert wrote: > According to the kernel Kconfig file it's only available for old 32-bit > Athlons, and it is in the i686 kernel(s). > > > config EDAC_AMD76X > tristate "AMD 76x (760, 762, 768)" > depends on EDAC_MM_EDAC && PCI && X86_32 > help > Support for error detection and correction on the AMD 76x > series of chipsets used with the Athlon processor. Thanks. I didn't realise it was only 32 bit athlons only. Any idea what EDAC modules 64 bit Athlon 64s should use? Under RHEL the k8_edac module provides ECC checking, but this module no longer exists as far as I can tell in Fedora 10. I seems strange that Fedora doesn't support ECC on AMD systems, but RHEL does! Jeremy From jarod at redhat.com Wed Apr 15 13:47:05 2009 From: jarod at redhat.com (Jarod Wilson) Date: Wed, 15 Apr 2009 09:47:05 -0400 Subject: EDAC on AMD with Fedora 10 In-Reply-To: References: <20090414172732.70319b27@dhcp-100-2-144.bos.redhat.com> Message-ID: <200904150947.05951.jarod@redhat.com> On Wednesday 15 April 2009 05:13:36 Jeremy Sanders wrote: > Chuck Ebbert wrote: > > > According to the kernel Kconfig file it's only available for old 32-bit > > Athlons, and it is in the i686 kernel(s). > > > > > > config EDAC_AMD76X > > tristate "AMD 76x (760, 762, 768)" > > depends on EDAC_MM_EDAC && PCI && X86_32 > > help > > Support for error detection and correction on the AMD 76x > > series of chipsets used with the Athlon processor. > > Thanks. I didn't realise it was only 32 bit athlons only. > > Any idea what EDAC modules 64 bit Athlon 64s should use? Under RHEL the > k8_edac module provides ECC checking, but this module no longer exists as > far as I can tell in Fedora 10. > > I seems strange that Fedora doesn't support ECC on AMD systems, but RHEL > does! The k8_edac module in RHEL5 is there via an out-of-tree patch. I can't recall why, but upstream had issues with the code, so it has yet to be merged into Linus' kernel, thus the reason its not in the Fedora kernel. CC'ing Aris, who might have a better idea on upstream progress of that code... -- Jarod Wilson jarod at redhat.com From aris at redhat.com Wed Apr 15 12:36:10 2009 From: aris at redhat.com (Aristeu Rozanski) Date: Wed, 15 Apr 2009 08:36:10 -0400 Subject: EDAC on AMD with Fedora 10 In-Reply-To: References: <20090414172732.70319b27@dhcp-100-2-144.bos.redhat.com> Message-ID: <20090415123609.GH16974@redhat.com> > > According to the kernel Kconfig file it's only available for old 32-bit > > Athlons, and it is in the i686 kernel(s). > > > > > > config EDAC_AMD76X > > tristate "AMD 76x (760, 762, 768)" > > depends on EDAC_MM_EDAC && PCI && X86_32 > > help > > Support for error detection and correction on the AMD 76x > > series of chipsets used with the Athlon processor. > > Thanks. I didn't realise it was only 32 bit athlons only. > > Any idea what EDAC modules 64 bit Athlon 64s should use? Under RHEL the > k8_edac module provides ECC checking, but this module no longer exists as > far as I can tell in Fedora 10. > > I seems strange that Fedora doesn't support ECC on AMD systems, but RHEL > does! the reason for that is that k8_edac is not upstream. k8_edac and amd64_edac are available at http://bluesmoke.sf.net/. To explain why: on 64 bit athlons the ECC error reporting is done by MCE events and because of that, k8_edac and amd64_edac need to have access to MCE registers but the developers never managed to convince the mcelog maintainer to share those registers. it's a long (ongoing) story. -- Aristeu From doug.chapman at hp.com Wed Apr 22 20:33:22 2009 From: doug.chapman at hp.com (Doug Chapman) Date: Wed, 22 Apr 2009 16:33:22 -0400 Subject: ia64 no longer should set CONFIG_SYSFS_DEPRECATED=y Message-ID: <1240432402.8644.20.camel@oberon> Back in the F9 timeframe we had recommended that CONFIG_SYSFS_DEPRECATED=y be set for the ia64 config. It appears that recent anaconda changes no longer work at all with that set. Can we get this removed? It was set only for ia64 so it will have no affect on other arches. thanks, - Doug From davej at redhat.com Wed Apr 22 20:40:23 2009 From: davej at redhat.com (Dave Jones) Date: Wed, 22 Apr 2009 16:40:23 -0400 Subject: ia64 no longer should set CONFIG_SYSFS_DEPRECATED=y In-Reply-To: <1240432402.8644.20.camel@oberon> References: <1240432402.8644.20.camel@oberon> Message-ID: <20090422204023.GA10836@redhat.com> On Wed, Apr 22, 2009 at 04:33:22PM -0400, Doug Chapman wrote: > Back in the F9 timeframe we had recommended that > CONFIG_SYSFS_DEPRECATED=y be set for the ia64 config. It appears that > recent anaconda changes no longer work at all with that set. > > Can we get this removed? It was set only for ia64 so it will have no > affect on other arches. Done. Dave From cra at WPI.EDU Wed Apr 22 22:18:07 2009 From: cra at WPI.EDU (Chuck Anderson) Date: Wed, 22 Apr 2009 18:18:07 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken Message-ID: <20090422221807.GE13050@angus.ind.WPI.EDU> Trying to build a vanilla kernel with: rpmbuild -ba --with vanilla kernel.spec fails like so: + ApplyPatch linux-2.6-build-nonintconfig.patch + local patch=linux-2.6-build-nonintconfig.patch + shift + '[' '!' -f /home/cra/rpmbuild/SOURCES/linux-2.6-build-nonintconfig.patch ']' ERROR: Patch linux-2.6-build-nonintconfig.patch not listed as a source patch in specfile error: Bad exit status from /var/tmp/rpm-tmp.8pegaB (%prep) this is due to the following code in ApplyPatch(): if ! egrep "^Patch[0-9]+: $patch\$" %{_specdir}/%{name}.spec ; then if [ "${patch:0:10}" != "patch-2.6." ] ; then echo "ERROR: Patch $patch not listed as a source patch in specfile" exit 1 fi fi 2>/dev/null Why is it checking for "patch-2.6.*" in the patch file name? I removed that entire block of code and --with vanilla now works. What is the expected behavior of that block of code? From kyle at mcmartin.ca Thu Apr 23 04:29:01 2009 From: kyle at mcmartin.ca (Kyle McMartin) Date: Thu, 23 Apr 2009 00:29:01 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: <20090422221807.GE13050@angus.ind.WPI.EDU> References: <20090422221807.GE13050@angus.ind.WPI.EDU> Message-ID: <20090423042901.GC28423@bombadil.infradead.org> On Wed, Apr 22, 2009 at 06:18:07PM -0400, Chuck Anderson wrote: > if ! egrep "^Patch[0-9]+: $patch\$" %{_specdir}/%{name}.spec ; then > if [ "${patch:0:10}" != "patch-2.6." ] ; then > echo "ERROR: Patch $patch not listed as a source patch in specfile" > exit 1 > fi > fi 2>/dev/null > > Why is it checking for "patch-2.6.*" in the patch file name? I > removed that entire block of code and --with vanilla now works. What > is the expected behavior of that block of code? > Urgh. Yeah, this was added to check that ApplyPatch patches are also listed in the srpm (if they aren't, then obviously we'll ftbfs... this lets 'make prep' catch it.) This rule should probably be updated to use an $specdir/exclude file or something. regards, Kyle From cebbert at redhat.com Tue Apr 28 15:08:05 2009 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 28 Apr 2009 11:08:05 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: <20090422221807.GE13050@angus.ind.WPI.EDU> References: <20090422221807.GE13050@angus.ind.WPI.EDU> Message-ID: <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> On Wed, 22 Apr 2009 18:18:07 -0400 Chuck Anderson wrote: > ERROR: Patch linux-2.6-build-nonintconfig.patch not listed as a > source patch in specfile > error: Bad exit status from /var/tmp/rpm-tmp.8pegaB (%prep) > > this is due to the following code in ApplyPatch(): > > if ! egrep "^Patch[0-9]+: $patch\$" %{_specdir}/%{name}.spec ; then > if [ "${patch:0:10}" != "patch-2.6." ] ; then > echo "ERROR: Patch $patch not listed as a source patch in specfile" > exit 1 > fi > fi 2>/dev/null > It's trying to grep in {_specdir}/kernel-vanilla.spec because of the ugly name-munging that's used to build the vanilla kernel. Fixed in 2.6.29.1-114: if ! egrep "^Patch[0-9]+: $patch\$" %{_specdir}/${RPM_PACKAGE_NAME%%%%%{?variant}}.spec ; then From cra at WPI.EDU Tue Apr 28 15:17:04 2009 From: cra at WPI.EDU (Chuck Anderson) Date: Tue, 28 Apr 2009 11:17:04 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> References: <20090422221807.GE13050@angus.ind.WPI.EDU> <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> Message-ID: <20090428151704.GB25564@angus.ind.WPI.EDU> On Tue, Apr 28, 2009 at 11:08:05AM -0400, Chuck Ebbert wrote: > On Wed, 22 Apr 2009 18:18:07 -0400 > Chuck Anderson wrote: > > > ERROR: Patch linux-2.6-build-nonintconfig.patch not listed as a > > source patch in specfile > > error: Bad exit status from /var/tmp/rpm-tmp.8pegaB (%prep) > > > > this is due to the following code in ApplyPatch(): > > > > if ! egrep "^Patch[0-9]+: $patch\$" %{_specdir}/%{name}.spec ; then > > if [ "${patch:0:10}" != "patch-2.6." ] ; then > > echo "ERROR: Patch $patch not listed as a source patch in specfile" > > exit 1 > > fi > > fi 2>/dev/null > > > > It's trying to grep in {_specdir}/kernel-vanilla.spec because of the ugly name-munging > that's used to build the vanilla kernel. > > Fixed in 2.6.29.1-114: > > if ! egrep "^Patch[0-9]+: $patch\$" %{_specdir}/${RPM_PACKAGE_NAME%%%%%{?variant}}.spec ; then Great. I ended up having lots of other issues with vanilla build. At some point during the build, the "make oldconfig" becomes interactive during the %install phase. I answer all the questions with default values (hitting enter on each one) and then the build fails. I also see some interesting thigs with ia64. Why is it messing with ia64 configs? Excerpts: Building for target noarch ... + Arch=ia64 + make ARCH=ia64 loose_nonint_oldconfig /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-segrel.S: Assembler messages: /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-segrel.S:1: Error: unknown pseudo-op: `.rodata' /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-segrel.S:2: Error: no such instruction: `data4 @segrel(start)' objdump: '/tmp/out12892': No such file /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/toolchain-flags: line 19: [: !=: unary operator expected /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-text-align.S: Assembler messages: /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-text-align.S:1: Error: unknown pseudo-op: `.proc' /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-text-align.S:2: Error: unknown pseudo-op: `.prologue' /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-text-align.S:3: Error: unknown pseudo-op: `.save' /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-text-align.S:6: Error: unknown pseudo-op: `.endp' readelf: Error: '/tmp/out12892': No such file /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-gas-asm.S: Assembler messages: /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-gas-asm.S:1: Error: junk at end of line, first unrecognized character is `[' /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-gas-asm.S:2: Error: unknown pseudo-op: `.xdata4' objdump: '/tmp/out12918.o': No such file /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/arch/ia64/scripts/check-gas: line 10: [: !=: unary operator expected + echo '# ia64' ... Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.RmV63c + umask 022 + cd /home/cra/rpmbuild/BUILD + cd kernel-2.6.29 + LANG=C + export LANG + unset DISPLAY + cd linux-2.6.29.noarch + make INSTALL_FW_PATH=/home/cra/rpmbuild/BUILDROOT/kernel-vanilla-2.6.29.1-102.fc10.noarch/lib/firmware firmware_install scripts/kconfig/conf -s arch/x86/Kconfig * * Restart config... * * * Enable the block layer * Enable the block layer (BLOCK) [Y/?] y Support for large block devices and files (LBD) [N/y/?] (NEW) aborted! Console input/output is redirected. Run 'make oldconfig' to update configuration. make[2]: *** [silentoldconfig] Error 1 make[1]: *** [silentoldconfig] Error 2 ... /bin/sh: /home/cra/rpmbuild/BUILD/kernel-2.6.29/linux-2.6.29.noarch/scripts/ihex2fw: No such file or directory make[1]: *** [firmware/dabusb/firmware.fw] Error 127 make: *** [firmware_install] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.RmV63c (%install) ... File listed twice: /usr/src/kernels/2.6.29.1-102.fc10.i686.PAE/usr File listed twice: /usr/src/kernels/2.6.29.1-102.fc10.i686.PAE/usr/Kconfig File listed twice: /usr/src/kernels/2.6.29.1-102.fc10.i686.PAE/usr/Makefile Bad exit status from /var/tmp/rpm-tmp.RmV63c (%install) From cebbert at redhat.com Tue Apr 28 17:01:17 2009 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 28 Apr 2009 13:01:17 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: <20090428151704.GB25564@angus.ind.WPI.EDU> References: <20090422221807.GE13050@angus.ind.WPI.EDU> <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> <20090428151704.GB25564@angus.ind.WPI.EDU> Message-ID: <20090428130117.6f26a76b@dhcp-100-2-144.bos.redhat.com> On Tue, 28 Apr 2009 11:17:04 -0400 Chuck Anderson wrote: > > Great. I ended up having lots of other issues with vanilla build. At > some point during the build, the "make oldconfig" becomes interactive > during the %install phase. I answer all the questions with default > values (hitting enter on each one) and then the build fails. I also > see some interesting thigs with ia64. Why is it messing with ia64 > configs? > > Excerpts: > > Building for target noarch > ... You should always specify an arch. I normally use: rpmbuild -bb --target x86_64 --with baseonly --without debuginfo --with firmware kernel.spec (--with firmware has some problems when building 32-bit kernels on x86_64 though.) From cra at WPI.EDU Tue Apr 28 17:14:08 2009 From: cra at WPI.EDU (Chuck Anderson) Date: Tue, 28 Apr 2009 13:14:08 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: <20090428130117.6f26a76b@dhcp-100-2-144.bos.redhat.com> References: <20090422221807.GE13050@angus.ind.WPI.EDU> <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> <20090428151704.GB25564@angus.ind.WPI.EDU> <20090428130117.6f26a76b@dhcp-100-2-144.bos.redhat.com> Message-ID: <20090428171408.GD25564@angus.ind.WPI.EDU> On Tue, Apr 28, 2009 at 01:01:17PM -0400, Chuck Ebbert wrote: > On Tue, 28 Apr 2009 11:17:04 -0400 > Chuck Anderson wrote: > > > > > Great. I ended up having lots of other issues with vanilla build. At > > some point during the build, the "make oldconfig" becomes interactive > > during the %install phase. I answer all the questions with default > > values (hitting enter on each one) and then the build fails. I also > > see some interesting thigs with ia64. Why is it messing with ia64 > > configs? > > > > Excerpts: > > > > Building for target noarch > > ... > > You should always specify an arch. > > I normally use: > > rpmbuild -bb --target x86_64 --with baseonly --without debuginfo --with firmware kernel.spec > > (--with firmware has some problems when building 32-bit kernels on x86_64 though.) Sorry, I should have specified the command I had used. It was similar to this: rpmbuild -ba --target=i386,i686,noarch --with vanilla --without debuginfo --without debug --with firmware kernel.spec I was building on an F10 i386 host. From roland at redhat.com Tue Apr 28 17:16:22 2009 From: roland at redhat.com (Roland McGrath) Date: Tue, 28 Apr 2009 10:16:22 -0700 (PDT) Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: Chuck Anderson's message of Tuesday, 28 April 2009 11:17:04 -0400 <20090428151704.GB25564@angus.ind.WPI.EDU> References: <20090422221807.GE13050@angus.ind.WPI.EDU> <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> <20090428151704.GB25564@angus.ind.WPI.EDU> Message-ID: <20090428171622.22EF8FC3C6@magilla.sf.frob.com> > Great. I ended up having lots of other issues with vanilla build. At > some point during the build, the "make oldconfig" becomes interactive > during the %install phase. %install?? Weird. That should not be happening. Maybe a V=1 on the make command would make kbuild explain why it decided to do that. > I also see some interesting thigs with ia64. Why is it messing with ia64 > configs? That stuff is "normal". Ignore it if it doesn't break the build. From roland at redhat.com Tue Apr 28 17:27:38 2009 From: roland at redhat.com (Roland McGrath) Date: Tue, 28 Apr 2009 10:27:38 -0700 (PDT) Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: Chuck Ebbert's message of Tuesday, 28 April 2009 13:01:17 -0400 <20090428130117.6f26a76b@dhcp-100-2-144.bos.redhat.com> References: <20090422221807.GE13050@angus.ind.WPI.EDU> <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> <20090428151704.GB25564@angus.ind.WPI.EDU> <20090428130117.6f26a76b@dhcp-100-2-144.bos.redhat.com> Message-ID: <20090428172738.59CFDFC3C6@magilla.sf.frob.com> > You should always specify an arch. make prep uses noarch and generally works fine. You can just ignore the strange assembler messages in the 'make configs' phase and the .config files come out fine, in my experience. From kyle at mcmartin.ca Tue Apr 28 17:30:58 2009 From: kyle at mcmartin.ca (Kyle McMartin) Date: Tue, 28 Apr 2009 13:30:58 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: <20090428172738.59CFDFC3C6@magilla.sf.frob.com> References: <20090422221807.GE13050@angus.ind.WPI.EDU> <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> <20090428151704.GB25564@angus.ind.WPI.EDU> <20090428130117.6f26a76b@dhcp-100-2-144.bos.redhat.com> <20090428172738.59CFDFC3C6@magilla.sf.frob.com> Message-ID: <20090428173058.GC5264@bombadil.infradead.org> On Tue, Apr 28, 2009 at 10:27:38AM -0700, Roland McGrath wrote: > > You should always specify an arch. > > make prep uses noarch and generally works fine. You can just ignore the > strange assembler messages in the 'make configs' phase and the .config > files come out fine, in my experience. > The strange messages are just annoying Makefile detritus because of running ARCH=ia64, they're nothing to be concerned with, and not relevant to anything but actually building the kernel on ia64. (See also arch/ia64/Makefile $GAS_STATUS and $KBUILD_CPPFLAGS) cheers, Kyle From cebbert at redhat.com Tue Apr 28 17:43:20 2009 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 28 Apr 2009 13:43:20 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: <20090428172738.59CFDFC3C6@magilla.sf.frob.com> References: <20090422221807.GE13050@angus.ind.WPI.EDU> <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> <20090428151704.GB25564@angus.ind.WPI.EDU> <20090428130117.6f26a76b@dhcp-100-2-144.bos.redhat.com> <20090428172738.59CFDFC3C6@magilla.sf.frob.com> Message-ID: <20090428134320.680d1b47@dhcp-100-2-144.bos.redhat.com> On Tue, 28 Apr 2009 10:27:38 -0700 (PDT) Roland McGrath wrote: > > You should always specify an arch. > > make prep uses noarch and generally works fine. You can just ignore the > strange assembler messages in the 'make configs' phase and the .config > files come out fine, in my experience. Well yeah, but if you're running rpmbuild -ba you probably want to build a kernel. From cebbert at redhat.com Tue Apr 28 17:51:08 2009 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 28 Apr 2009 13:51:08 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: <20090428171408.GD25564@angus.ind.WPI.EDU> References: <20090422221807.GE13050@angus.ind.WPI.EDU> <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> <20090428151704.GB25564@angus.ind.WPI.EDU> <20090428130117.6f26a76b@dhcp-100-2-144.bos.redhat.com> <20090428171408.GD25564@angus.ind.WPI.EDU> Message-ID: <20090428135108.5342f410@dhcp-100-2-144.bos.redhat.com> On Tue, 28 Apr 2009 13:14:08 -0400 Chuck Anderson wrote: > Sorry, I should have specified the command I had used. It was similar > to this: > > rpmbuild -ba --target=i386,i686,noarch --with vanilla --without debuginfo --without debug --with firmware kernel.spec > > I was building on an F10 i386 host. > I don't think the target can be a list. And if you say '--with firmware' you don't need to build the noarch target unless you want docs (if you do want the whole noarch build then you don't need '--with firmware'.) From cra at WPI.EDU Tue Apr 28 17:57:31 2009 From: cra at WPI.EDU (Chuck Anderson) Date: Tue, 28 Apr 2009 13:57:31 -0400 Subject: 2.6.29.1-102.fc11 --with vanilla broken In-Reply-To: <20090428135108.5342f410@dhcp-100-2-144.bos.redhat.com> References: <20090422221807.GE13050@angus.ind.WPI.EDU> <20090428110805.714b4649@dhcp-100-2-144.bos.redhat.com> <20090428151704.GB25564@angus.ind.WPI.EDU> <20090428130117.6f26a76b@dhcp-100-2-144.bos.redhat.com> <20090428171408.GD25564@angus.ind.WPI.EDU> <20090428135108.5342f410@dhcp-100-2-144.bos.redhat.com> Message-ID: <20090428175731.GF25564@angus.ind.WPI.EDU> On Tue, Apr 28, 2009 at 01:51:08PM -0400, Chuck Ebbert wrote: > On Tue, 28 Apr 2009 13:14:08 -0400 > Chuck Anderson wrote: > > > Sorry, I should have specified the command I had used. It was similar > > to this: > > > > rpmbuild -ba --target=i386,i686,noarch --with vanilla --without debuginfo --without debug --with firmware kernel.spec > > > > I was building on an F10 i386 host. > > > > I don't think the target can be a list. And if you say '--with firmware' you don't need > to build the noarch target unless you want docs (if you do want the whole noarch build > then you don't need '--with firmware'.) The target has been able to be list for as long as I can remember building Fedora kernels. If it can't be a list now, then that is news to me. From doug.chapman at hp.com Tue Apr 28 19:02:46 2009 From: doug.chapman at hp.com (Doug Chapman) Date: Tue, 28 Apr 2009 15:02:46 -0400 Subject: ia64 no longer should set CONFIG_SYSFS_DEPRECATED=y In-Reply-To: <20090422204023.GA10836@redhat.com> References: <1240432402.8644.20.camel@oberon> <20090422204023.GA10836@redhat.com> Message-ID: <1240945366.18654.8.camel@oberon> On Wed, 2009-04-22 at 16:40 -0400, Dave Jones wrote: > On Wed, Apr 22, 2009 at 04:33:22PM -0400, Doug Chapman wrote: > > Back in the F9 timeframe we had recommended that > > CONFIG_SYSFS_DEPRECATED=y be set for the ia64 config. It appears that > > recent anaconda changes no longer work at all with that set. > > > > Can we get this removed? It was set only for ia64 so it will have no > > affect on other arches. > > Done. > > Dave > I see this change has been made to the fc12 tree but not fc11. Can we get this change in the current F-11 branch also? thanks, - Doug From rheneus.paul at gmail.com Thu Apr 30 07:07:09 2009 From: rheneus.paul at gmail.com (rheneus.paul at gmail.com) Date: Thu, 30 Apr 2009 07:07:09 +0000 Subject: 2.6.18.1 linux hangs Message-ID: <00163646ccde3804b40468c05862@google.com> In FC6, some times the linux hangs at bootup after the "Uncompressing linux ..." and before the "Red Hat nash version ..". It's not happening always, I've enabled kernel debug and loglevel to print more detailed information. If it hangs again, I would attach the detailed log information. Throw some light on what could be the issue, so that I can debug more on this. CPU info: # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Intel(R) Core(TM) Duo CPU U2500 @ 1.20GHz stepping : 12 cpu MHz : 1200.000 cache size : 2048 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr bogomips : 2403.04 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Intel(R) Core(TM) Duo CPU U2500 @ 1.20GHz stepping : 12 cpu MHz : 1200.000 cache size : 2048 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr bogomips : 2400.22 thanks in advance, Antony Rheneus From jwboyer at gmail.com Thu Apr 30 11:35:45 2009 From: jwboyer at gmail.com (Josh Boyer) Date: Thu, 30 Apr 2009 07:35:45 -0400 Subject: 2.6.18.1 linux hangs In-Reply-To: <00163646ccde3804b40468c05862@google.com> References: <00163646ccde3804b40468c05862@google.com> Message-ID: <20090430113545.GA2424@yoda.jdub.homelinux.org> On Thu, Apr 30, 2009 at 07:07:09AM +0000, rheneus.paul at gmail.com wrote: > In FC6, some times the linux hangs at bootup after the "Uncompressing > linux ..." and before the "Red Hat nash version ..". FC6 has been end-of-life for quite some time now. I suggest you upgrade to something newer. josh From bmaly at redhat.com Thu Apr 30 19:44:12 2009 From: bmaly at redhat.com (Brian Maly) Date: Thu, 30 Apr 2009 15:44:12 -0400 Subject: 2.6.18.1 linux hangs In-Reply-To: <00163646ccde3804b40468c05862@google.com> References: <00163646ccde3804b40468c05862@google.com> Message-ID: <49F9FF8C.7050801@redhat.com> rheneus.paul at gmail.com wrote: > In FC6, some times the linux hangs at bootup after the "Uncompressing > linux ..." and before the "Red Hat nash version ..". > > It's not happening always, I've enabled kernel debug and loglevel to > print more detailed information. If it hangs again, I would attach the > detailed log information. > > Throw some light on what could be the issue, so that I can debug more > on this. > > CPU info: > # cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 14 > model name : Intel(R) Core(TM) Duo CPU U2500 @ 1.20GHz > stepping : 12 > cpu MHz : 1200.000 > cache size : 2048 KB > physical id : 0 > siblings : 2 > core id : 0 > cpu cores : 2 > fdiv_bug : no > hlt_bug : no > f00f_bug : no > coma_bug : no > fpu : yes > fpu_exception : yes > cpuid level : 10 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat > clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni > monitor vmx est tm2 xtpr > bogomips : 2403.04 > > processor : 1 > vendor_id : GenuineIntel > cpu family : 6 > model : 14 > model name : Intel(R) Core(TM) Duo CPU U2500 @ 1.20GHz > stepping : 12 > cpu MHz : 1200.000 > cache size : 2048 KB > physical id : 0 > siblings : 2 > core id : 1 > cpu cores : 2 > fdiv_bug : no > hlt_bug : no > f00f_bug : no > coma_bug : no > fpu : yes > fpu_exception : yes > cpuid level : 10 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat > clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni > monitor vmx est tm2 xtpr > bogomips : 2400.22 > > thanks in advance, > Antony Rheneus > _______________________________________________ > Fedora-kernel-list mailing list > Fedora-kernel-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-kernel-list There are some known issues with older (i.e. 2.6.18) kernels on Core 2 Duo based systems. Just update your kernel to a newer version (i.e. >= F9 kernel, etc). Brian From cebbert at redhat.com Thu Apr 30 20:02:52 2009 From: cebbert at redhat.com (Chuck Ebbert) Date: Thu, 30 Apr 2009 16:02:52 -0400 Subject: ia64 no longer should set CONFIG_SYSFS_DEPRECATED=y In-Reply-To: <1240945366.18654.8.camel@oberon> References: <1240432402.8644.20.camel@oberon> <20090422204023.GA10836@redhat.com> <1240945366.18654.8.camel@oberon> Message-ID: <20090430160252.7fc2f7ac@dhcp-100-2-144.bos.redhat.com> On Tue, 28 Apr 2009 15:02:46 -0400 Doug Chapman wrote: > > On Wed, 2009-04-22 at 16:40 -0400, Dave Jones wrote: > > On Wed, Apr 22, 2009 at 04:33:22PM -0400, Doug Chapman wrote: > > > Back in the F9 timeframe we had recommended that > > > CONFIG_SYSFS_DEPRECATED=y be set for the ia64 config. It appears that > > > recent anaconda changes no longer work at all with that set. > > > > > > Can we get this removed? It was set only for ia64 so it will have no > > > affect on other arches. > > > > Done. > > > > Dave > > > > I see this change has been made to the fc12 tree but not fc11. Can we > get this change in the current F-11 branch also? > Done.