From notting at redhat.com Fri Aug 1 19:51:05 2008 From: notting at redhat.com (Bill Nottingham) Date: Fri, 1 Aug 2008 15:51:05 -0400 Subject: [PATCH] be less annoying on boot Message-ID: <20080801195105.GA18828@nostromo.devel.redhat.com> As long as we're printing mostly useless messages on every boot regardless of debug level, make them 5% more amusing. Signed-off-by: Bill Nottingham -------------- next part -------------- --- linux-2.6.26.noarch/arch/x86/kernel/head64.c.foo 2008-08-01 15:44:28.000000000 -0400 +++ linux-2.6.26.noarch/arch/x86/kernel/head64.c 2008-08-01 15:46:53.000000000 -0400 @@ -109,11 +109,11 @@ early_printk("Kernel alive\n"); x86_64_init_pda(); - early_printk("Kernel really alive\n"); + early_printk("Kernel really alive! It's alive! IT'S ALIIIIIIIIIVE!\n"); x86_64_start_reservations(real_mode_data); } void __init x86_64_start_reservations(char *real_mode_data) From paul.moore at hp.com Fri Aug 1 22:01:48 2008 From: paul.moore at hp.com (Paul Moore) Date: Fri, 1 Aug 2008 18:01:48 -0400 Subject: [PATCH] be less annoying on boot In-Reply-To: <20080801195105.GA18828@nostromo.devel.redhat.com> References: <20080801195105.GA18828@nostromo.devel.redhat.com> Message-ID: <200808011801.48066.paul.moore@hp.com> On Friday 01 August 2008 3:51:05 pm Bill Nottingham wrote: > As long as we're printing mostly useless messages on every boot > regardless of debug level, make them 5% more amusing. > > Signed-off-by: Bill Nottingham You forgot the "MUWAHAHA!" :) -- paul moore linux @ hp From snecklifter at gmail.com Sat Aug 2 13:59:10 2008 From: snecklifter at gmail.com (Christopher Brown) Date: Sat, 2 Aug 2008 14:59:10 +0100 Subject: [PATCH] be less annoying on boot In-Reply-To: <200808011801.48066.paul.moore@hp.com> References: <20080801195105.GA18828@nostromo.devel.redhat.com> <200808011801.48066.paul.moore@hp.com> Message-ID: <364d303b0808020659v3900c56bkcf530b148d12d5de@mail.gmail.com> On Friday 01 August 2008 3:51:05 pm Bill Nottingham wrote: > As long as we're printing mostly useless messages on every boot > regardless of debug level, make them 5% more amusing. Sometimes I think a Frankenstein quote more appropriate: --- linux-2.6.26.noarch/arch/x86/kernel/head64.c.foo 2008-08-01 15:44:28.000000000 -0400 +++ linux-2.6.26.noarch/arch/x86/kernel/head64.c 2008-08-01 15:46:53.000000000 -0400 @@ -109,11 +109,11 @@ early_printk("Kernel alive\n"); x86_64_init_pda(); - early_printk("Kernel really alive\n"); + early_printk("And now, with the world before me, " "whither should I bend my steps?\n"); x86_64_start_reservations(real_mode_data); } void __init x86_64_start_reservations(char *real_mode_data) -- Christopher Brown http://www.chruz.com From eparis at redhat.com Sat Aug 2 14:16:30 2008 From: eparis at redhat.com (Eric Paris) Date: Sat, 02 Aug 2008 10:16:30 -0400 Subject: [PATCH] be less annoying on boot In-Reply-To: <364d303b0808020659v3900c56bkcf530b148d12d5de@mail.gmail.com> References: <20080801195105.GA18828@nostromo.devel.redhat.com> <200808011801.48066.paul.moore@hp.com> <364d303b0808020659v3900c56bkcf530b148d12d5de@mail.gmail.com> Message-ID: <1217686590.2906.8.camel@localhost.localdomain> On Sat, 2008-08-02 at 14:59 +0100, Christopher Brown wrote: > On Friday 01 August 2008 3:51:05 pm Bill Nottingham wrote: > > As long as we're printing mostly useless messages on every boot > > regardless of debug level, make them 5% more amusing. > > Sometimes I think a Frankenstein quote more appropriate: NAK, does not apply. > --- linux-2.6.26.noarch/arch/x86/kernel/head64.c.foo 2008-08-01 > 15:44:28.000000000 -0400 > +++ linux-2.6.26.noarch/arch/x86/kernel/head64.c 2008-08-01 > 15:46:53.000000000 -0400 > @@ -109,11 +109,11 @@ > > early_printk("Kernel alive\n"); > > x86_64_init_pda(); > > - early_printk("Kernel really alive\n"); > + early_printk("And now, with the world before me, " > "whither should I > bend my steps?\n"); > > x86_64_start_reservations(real_mode_data); > } > > void __init x86_64_start_reservations(char *real_mode_data) > > > From acme at redhat.com Sat Aug 2 15:09:24 2008 From: acme at redhat.com (Arnaldo Carvalho de Melo) Date: Sat, 2 Aug 2008 12:09:24 -0300 Subject: [PATCH] be less annoying on boot In-Reply-To: <1217686590.2906.8.camel@localhost.localdomain> References: <20080801195105.GA18828@nostromo.devel.redhat.com> <200808011801.48066.paul.moore@hp.com> <364d303b0808020659v3900c56bkcf530b148d12d5de@mail.gmail.com> <1217686590.2906.8.camel@localhost.localdomain> Message-ID: <20080802150924.GA15480@ghostprotocols.net> Em Sat, Aug 02, 2008 at 10:16:30AM -0400, Eric Paris escreveu: > On Sat, 2008-08-02 at 14:59 +0100, Christopher Brown wrote: > > On Friday 01 August 2008 3:51:05 pm Bill Nottingham wrote: > > > As long as we're printing mostly useless messages on every boot > > > regardless of debug level, make them 5% more amusing. > > > > Sometimes I think a Frankenstein quote more appropriate: > > NAK, does not apply. NAH, easily fixable by hand, worth the effort :-P > > > --- linux-2.6.26.noarch/arch/x86/kernel/head64.c.foo 2008-08-01 > > 15:44:28.000000000 -0400 > > +++ linux-2.6.26.noarch/arch/x86/kernel/head64.c 2008-08-01 > > 15:46:53.000000000 -0400 > > @@ -109,11 +109,11 @@ > > > > early_printk("Kernel alive\n"); > > > > x86_64_init_pda(); > > > > - early_printk("Kernel really alive\n"); > > + early_printk("And now, with the world before me, " > > "whither should I > > bend my steps?\n"); > > > > x86_64_start_reservations(real_mode_data); > > } > > > > void __init x86_64_start_reservations(char *real_mode_data) > > > > > > > > _______________________________________________ > Fedora-kernel-list mailing list > Fedora-kernel-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-kernel-list From snecklifter at gmail.com Sat Aug 2 17:12:56 2008 From: snecklifter at gmail.com (Christopher Brown) Date: Sat, 2 Aug 2008 18:12:56 +0100 Subject: [PATCH] be less annoying on boot In-Reply-To: <1217686590.2906.8.camel@localhost.localdomain> References: <20080801195105.GA18828@nostromo.devel.redhat.com> <200808011801.48066.paul.moore@hp.com> <364d303b0808020659v3900c56bkcf530b148d12d5de@mail.gmail.com> <1217686590.2906.8.camel@localhost.localdomain> Message-ID: <364d303b0808021012k8731eebuf94afc57e29f48f5@mail.gmail.com> 2008/8/2 Eric Paris : > On Sat, 2008-08-02 at 14:59 +0100, Christopher Brown wrote: >> On Friday 01 August 2008 3:51:05 pm Bill Nottingham wrote: >> > As long as we're printing mostly useless messages on every boot >> > regardless of debug level, make them 5% more amusing. >> >> Sometimes I think a Frankenstein quote more appropriate: > > NAK, does not apply. Yeah, gmail's interface does this fantastic "Watch while I f*** with your coding style" as soon as you hit send. I think its called a WYSIWLLAA editor - What You See Is What Looks Like Ascii Art. It's a sad day when I can't submit a single one-liner.... -- Christopher Brown http://www.chruz.com From tequilamex at hotmail.com Mon Aug 4 17:22:19 2008 From: tequilamex at hotmail.com (Kristopher Hensley) Date: Mon, 4 Aug 2008 18:22:19 +0100 Subject: 82221220 Rechnung Message-ID: <01c8f65f$079b3f80$b93b8b57@tequilamex> Morgen, Ihr Auftrag Nr. SP3269672 wurde erfullt. Ein Betrag von 6519.07 EURO wurde abgebucht und wird in Ihrem Bankauszug als ?Paypalabbuchung ? angezeigt. Sie finden die Details zu der Rechnung im Anhang PayPal (Europe) S.205; r.l. & Cie, S.C.A. 54-20 Boulevard Royal L-4039 Luxembourg Hochachtungsvoll, Vertretungsberechtigter: Kristopher Hensley Handelsregisternummer: R.C.S. B 131 166 From jwboyer at gmail.com Tue Aug 5 03:01:05 2008 From: jwboyer at gmail.com (Josh Boyer) Date: Mon, 04 Aug 2008 23:01:05 -0400 Subject: kernel-vanilla builds for 2.6.27-rc1 Message-ID: <1217905265.2328.52.camel@localhost.localdomain> http://jwboyer.fedorapeople.org/pub/ Let the kernel installs begin. Hopefully I didn't fsck something up horridly. If I did, then I'll fix it for -rc2. josh From SteveD at redhat.com Tue Aug 5 13:24:10 2008 From: SteveD at redhat.com (Steve Dickson) Date: Tue, 05 Aug 2008 09:24:10 -0400 Subject: [PATCH] kernel.spec: adding --with firmware & --without vdso_install build options In-Reply-To: <489220BE.8020906@redhat.com> References: <488F3EA1.8090102@RedHat.com> <489220BE.8020906@redhat.com> Message-ID: <4898547A.8050102@RedHat.com> Chuck Ebbert wrote: > Steve Dickson wrote: >> Now that devel kernels rpms require the kernel-firmware rpm, it makes >> sense to me that one should be able to build both of them at the same >> time. So this patch adds the "--with firmware" build option >> which will allow kernel-firmware rpms to built with kernel rpms. >> >> This patch also adds the "--without vdso_install" build option >> which stop the VDSO binaries from being installed. This cuts >> down the overall build time especially when you build over NFS >> like I do.. >> Signed-Off-By: Steve Dickson > > With one small change we can still support --without firmware. That way > the default behavior can be overridden in either case. See below... Sure.. that works... Is there an ETA for these two changes? steved. From kyle at mcmartin.ca Tue Aug 5 14:17:41 2008 From: kyle at mcmartin.ca (Kyle McMartin) Date: Tue, 5 Aug 2008 10:17:41 -0400 Subject: rpms/kernel/devel kernel.spec,1.847,1.848 In-Reply-To: <200808050548.m755m4Ga006642@cvs-int.fedora.redhat.com> References: <200808050548.m755m4Ga006642@cvs-int.fedora.redhat.com> Message-ID: <20080805141741.GB32404@phobos.i.cabal.ca> On Tue, Aug 05, 2008 at 05:48:04AM +0000, Dave Jones wrote: > + cp -a acpi config keys linux math-emu media mtd net pcmcia rdma rxrpc scsi sound video drm asm-generic $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/include > + if [ -f asm ]; then > + cp -a `readlink asm` $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/include > fi > This looks like it will DTRT thing in both cases. Cool. From jwilson at redhat.com Tue Aug 5 15:01:17 2008 From: jwilson at redhat.com (Jarod Wilson) Date: Tue, 5 Aug 2008 11:01:17 -0400 Subject: [PATCH] kernel.spec: adding --with firmware & --without vdso_install build options In-Reply-To: <4898547A.8050102@RedHat.com> References: <488F3EA1.8090102@RedHat.com> <489220BE.8020906@redhat.com> <4898547A.8050102@RedHat.com> Message-ID: <200808051101.17542.jwilson@redhat.com> On Tuesday 05 August 2008 09:24:10 Steve Dickson wrote: > Chuck Ebbert wrote: > > Steve Dickson wrote: > >> Now that devel kernels rpms require the kernel-firmware rpm, it makes > >> sense to me that one should be able to build both of them at the same > >> time. So this patch adds the "--with firmware" build option > >> which will allow kernel-firmware rpms to built with kernel rpms. > >> > >> This patch also adds the "--without vdso_install" build option > >> which stop the VDSO binaries from being installed. This cuts > >> down the overall build time especially when you build over NFS > >> like I do.. > >> Signed-Off-By: Steve Dickson > > > > With one small change we can still support --without firmware. That way > > the default behavior can be overridden in either case. See below... > > Sure.. that works... Is there an ETA for these two changes? I don't quite follow how the firmware change is supposed to work... The firmware is currently supposed to be a noarch package, and it gets built in the same pass as the kernel-docs sub-package, so it *shouldn't* be built in the same pass as the kernel. Is this flag to simply override that and build the firmware as an arch-specific package for simplified one-off builds? -- Jarod Wilson jwilson at redhat.com From kyle at mcmartin.ca Tue Aug 5 15:04:16 2008 From: kyle at mcmartin.ca (Kyle McMartin) Date: Tue, 5 Aug 2008 11:04:16 -0400 Subject: [PATCH] kernel.spec: adding --with firmware & --without vdso_install build options In-Reply-To: <200808051101.17542.jwilson@redhat.com> References: <488F3EA1.8090102@RedHat.com> <489220BE.8020906@redhat.com> <4898547A.8050102@RedHat.com> <200808051101.17542.jwilson@redhat.com> Message-ID: <20080805150416.GC32404@phobos.i.cabal.ca> On Tue, Aug 05, 2008 at 11:01:17AM -0400, Jarod Wilson wrote: > On Tuesday 05 August 2008 09:24:10 Steve Dickson wrote: > > Chuck Ebbert wrote: > > > Steve Dickson wrote: > > >> Now that devel kernels rpms require the kernel-firmware rpm, it makes > > >> sense to me that one should be able to build both of them at the same > > >> time. So this patch adds the "--with firmware" build option > > >> which will allow kernel-firmware rpms to built with kernel rpms. > > >> > > >> This patch also adds the "--without vdso_install" build option > > >> which stop the VDSO binaries from being installed. This cuts > > >> down the overall build time especially when you build over NFS > > >> like I do.. > > >> Signed-Off-By: Steve Dickson > > > > > > With one small change we can still support --without firmware. That way > > > the default behavior can be overridden in either case. See below... > > > > Sure.. that works... Is there an ETA for these two changes? > > I don't quite follow how the firmware change is supposed to work... The > firmware is currently supposed to be a noarch package, and it gets built in > the same pass as the kernel-docs sub-package, so it *shouldn't* be built in > the same pass as the kernel. Is this flag to simply override that and build > the firmware as an arch-specific package for simplified one-off builds? > You bring up a pretty good point here Jarod, what happens with firmware for arch-specific drivers? The Makefile rules will have to be written in such a way that it gets built into the package despite the CONFIG_* symbol being unset on the build arch. r, Kyle From roland at redhat.com Tue Aug 5 19:22:43 2008 From: roland at redhat.com (Roland McGrath) Date: Tue, 5 Aug 2008 12:22:43 -0700 (PDT) Subject: rpms/kernel/devel kernel.spec,1.847,1.848 In-Reply-To: Kyle McMartin's message of Tuesday, 5 August 2008 10:17:41 -0400 <20080805141741.GB32404@phobos.i.cabal.ca> References: <200808050548.m755m4Ga006642@cvs-int.fedora.redhat.com> <20080805141741.GB32404@phobos.i.cabal.ca> Message-ID: <20080805192243.986D0154217@magilla.localdomain> > On Tue, Aug 05, 2008 at 05:48:04AM +0000, Dave Jones wrote: > > + cp -a acpi config keys linux math-emu media mtd net pcmcia rdma rxrpc scsi sound video drm asm-generic $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/include > > + if [ -f asm ]; then > > + cp -a `readlink asm` $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/include > > fi > > > > This looks like it will DTRT thing in both cases. Cool. "cp -a asm/. targetdir" would work too. From kyle at mcmartin.ca Tue Aug 5 20:16:39 2008 From: kyle at mcmartin.ca (Kyle McMartin) Date: Tue, 5 Aug 2008 16:16:39 -0400 Subject: kernel-2.6.27-0.215.rc1.git4.fc10.i686 oops and no X :( In-Reply-To: <458750.64402.qm@web52607.mail.re2.yahoo.com> References: <458750.64402.qm@web52607.mail.re2.yahoo.com> Message-ID: <20080805201639.GD32404@phobos.i.cabal.ca> On Tue, Aug 05, 2008 at 12:37:32PM -0700, Antonio Olivares wrote: > Dear fellow testers, > > New kernel oops again and no X when starting it > > kernel-2.6.27-0.215.rc1.git4.fc10.i686 > > Here's oops > > http://www.kerneloops.org/submitresult.php?number=48331 > nasty... did this just start recently? Any thoughts, Dave? r, Kyle From cebbert at redhat.com Tue Aug 5 20:19:07 2008 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 05 Aug 2008 16:19:07 -0400 Subject: [PATCH] kernel.spec: adding --with firmware & --without vdso_install build options In-Reply-To: <20080805150416.GC32404@phobos.i.cabal.ca> References: <488F3EA1.8090102@RedHat.com> <489220BE.8020906@redhat.com> <4898547A.8050102@RedHat.com> <200808051101.17542.jwilson@redhat.com> <20080805150416.GC32404@phobos.i.cabal.ca> Message-ID: <4898B5BB.1080206@redhat.com> Kyle McMartin wrote: > On Tue, Aug 05, 2008 at 11:01:17AM -0400, Jarod Wilson wrote: >> On Tuesday 05 August 2008 09:24:10 Steve Dickson wrote: >>> Chuck Ebbert wrote: >>>> Steve Dickson wrote: >>>>> Now that devel kernels rpms require the kernel-firmware rpm, it makes >>>>> sense to me that one should be able to build both of them at the same >>>>> time. So this patch adds the "--with firmware" build option >>>>> which will allow kernel-firmware rpms to built with kernel rpms. >>>>> >>>>> This patch also adds the "--without vdso_install" build option >>>>> which stop the VDSO binaries from being installed. This cuts >>>>> down the overall build time especially when you build over NFS >>>>> like I do.. >>>>> Signed-Off-By: Steve Dickson >>>> With one small change we can still support --without firmware. That way >>>> the default behavior can be overridden in either case. See below... >>> Sure.. that works... Is there an ETA for these two changes? >> I don't quite follow how the firmware change is supposed to work... The >> firmware is currently supposed to be a noarch package, and it gets built in >> the same pass as the kernel-docs sub-package, so it *shouldn't* be built in >> the same pass as the kernel. Is this flag to simply override that and build >> the firmware as an arch-specific package for simplified one-off builds? >> > > You bring up a pretty good point here Jarod, what happens with firmware > for arch-specific drivers? The Makefile rules will have to be written in > such a way that it gets built into the package despite the CONFIG_* > symbol being unset on the build arch. > That's what it does. It includes all firmware, even for drivers that don't get built. Look in firmware/Makefile and you'll see it builds lists named fw-shipped-y, fw-shipped-m and fw-shipped- then just merges them to create fw-shipped-all which it uses to build/install the firmware. From kyle at mcmartin.ca Tue Aug 5 20:18:20 2008 From: kyle at mcmartin.ca (Kyle McMartin) Date: Tue, 5 Aug 2008 16:18:20 -0400 Subject: kernel-2.6.27-0.215.rc1.git4.fc10.i686 oops and no X :( In-Reply-To: <20080805201639.GD32404@phobos.i.cabal.ca> References: <458750.64402.qm@web52607.mail.re2.yahoo.com> <20080805201639.GD32404@phobos.i.cabal.ca> Message-ID: <20080805201820.GE32404@phobos.i.cabal.ca> On Tue, Aug 05, 2008 at 04:16:39PM -0400, Kyle McMartin wrote: > On Tue, Aug 05, 2008 at 12:37:32PM -0700, Antonio Olivares wrote: > > Dear fellow testers, > > > > New kernel oops again and no X when starting it > > > > kernel-2.6.27-0.215.rc1.git4.fc10.i686 > > > > Here's oops > > > > http://www.kerneloops.org/submitresult.php?number=48331 > > > > nasty... did this just start recently? > > Any thoughts, Dave? > fwiw this is hitting the BUG_ON in drm_open. mutex_lock(&dev->struct_mutex); BUG_ON((dev->dev_mapping != NULL) && (dev->dev_mapping != inode->i_mapping)); if (dev->dev_mapping == NULL) dev->dev_mapping = inode->i_mapping; mutex_unlock(&dev->struct_mutex); From cebbert at redhat.com Tue Aug 5 20:20:41 2008 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 05 Aug 2008 16:20:41 -0400 Subject: [PATCH] be less annoying on boot In-Reply-To: <20080801195105.GA18828@nostromo.devel.redhat.com> References: <20080801195105.GA18828@nostromo.devel.redhat.com> Message-ID: <4898B619.9040809@redhat.com> Bill Nottingham wrote: > As long as we're printing mostly useless messages on every boot regardless > of debug level, make them 5% more amusing. > > Signed-off-by: Bill Nottingham > > "Kernel not dead yet" Suggested by drago01 on IRC. From kyle at mcmartin.ca Tue Aug 5 20:21:31 2008 From: kyle at mcmartin.ca (Kyle McMartin) Date: Tue, 5 Aug 2008 16:21:31 -0400 Subject: [PATCH] kernel.spec: adding --with firmware & --without vdso_install build options In-Reply-To: <4898B5BB.1080206@redhat.com> References: <488F3EA1.8090102@RedHat.com> <489220BE.8020906@redhat.com> <4898547A.8050102@RedHat.com> <200808051101.17542.jwilson@redhat.com> <20080805150416.GC32404@phobos.i.cabal.ca> <4898B5BB.1080206@redhat.com> Message-ID: <20080805202131.GF32404@phobos.i.cabal.ca> On Tue, Aug 05, 2008 at 04:19:07PM -0400, Chuck Ebbert wrote: > That's what it does. It includes all firmware, even for drivers that don't get > built. Look in firmware/Makefile and you'll see it builds lists > named fw-shipped-y, fw-shipped-m and fw-shipped- then just merges them to > create fw-shipped-all which it uses to build/install the firmware. > Does this cover the case of firmware declared in Makefiles in subdirs that are obj-$(CONFIG_i) += subdir/? If so, cool, but I can't be arsed to check. cheers, kyle From cebbert at redhat.com Tue Aug 5 20:53:47 2008 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 05 Aug 2008 16:53:47 -0400 Subject: [PATCH] kernel.spec: adding --with firmware & --without vdso_install build options In-Reply-To: <20080805202131.GF32404@phobos.i.cabal.ca> References: <488F3EA1.8090102@RedHat.com> <489220BE.8020906@redhat.com> <4898547A.8050102@RedHat.com> <200808051101.17542.jwilson@redhat.com> <20080805150416.GC32404@phobos.i.cabal.ca> <4898B5BB.1080206@redhat.com> <20080805202131.GF32404@phobos.i.cabal.ca> Message-ID: <4898BDDB.9060405@redhat.com> Kyle McMartin wrote: > On Tue, Aug 05, 2008 at 04:19:07PM -0400, Chuck Ebbert wrote: >> That's what it does. It includes all firmware, even for drivers that don't get >> built. Look in firmware/Makefile and you'll see it builds lists >> named fw-shipped-y, fw-shipped-m and fw-shipped- then just merges them to >> create fw-shipped-all which it uses to build/install the firmware. >> > > Does this cover the case of firmware declared in Makefiles in subdirs > that are obj-$(CONFIG_i) += subdir/? > > If so, cool, but I can't be arsed to check. > It only does its thing for stuff in firmware/ Every firmware file needs to be moved there; some are not and they don't get into the package. From cebbert at redhat.com Tue Aug 5 20:59:57 2008 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 05 Aug 2008 16:59:57 -0400 Subject: [PATCH] kernel.spec: adding --with firmware & --without vdso_install build options In-Reply-To: <4898547A.8050102@RedHat.com> References: <488F3EA1.8090102@RedHat.com> <489220BE.8020906@redhat.com> <4898547A.8050102@RedHat.com> Message-ID: <4898BF4D.3010804@redhat.com> Steve Dickson wrote: > > Chuck Ebbert wrote: >> Steve Dickson wrote: >>> Now that devel kernels rpms require the kernel-firmware rpm, it makes >>> sense to me that one should be able to build both of them at the same >>> time. So this patch adds the "--with firmware" build option >>> which will allow kernel-firmware rpms to built with kernel rpms. >>> >>> This patch also adds the "--without vdso_install" build option >>> which stop the VDSO binaries from being installed. This cuts >>> down the overall build time especially when you build over NFS >>> like I do.. >>> Signed-Off-By: Steve Dickson >> With one small change we can still support --without firmware. That way >> the default behavior can be overridden in either case. See below... > Sure.. that works... Is there an ETA for these two changes? > Applied. From cebbert at redhat.com Tue Aug 5 21:05:33 2008 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 05 Aug 2008 17:05:33 -0400 Subject: When will we stop shipping WLAN improvements ahead of upstream in released Fedora version? In-Reply-To: <20080731213044.GB12820@redhat.com> References: <486F6F7E.8070809@leemhuis.info> <486F8FE0.6070401@leemhuis.info> <486F985C.3090803@leemhuis.info> <486F6F7E.8070809@leemhuis.info> <20080707153710.GD28109@redhat.com> <20080731213044.GB12820@redhat.com> Message-ID: <4898C09D.9000504@redhat.com> John W. Linville wrote: > > I still think that for continuity's sake f8 and f9 should continue > to get wireless fixes from 2.6.27. Those should only be specific > bug fixes (although I suppose there is still time for a new driver), > so hopefully the nattering nabobs won't be opposed to continuing with > that part of the original plan. > If you push wireless fixes to -stable Fedora would then get them for "free". I don't see many wireless patches in there generally, though the ath5k memory corruption fix just went in. And new drivers would be great. Lots of people seem to want ath9k, for example. From kyle at mcmartin.ca Tue Aug 5 21:55:00 2008 From: kyle at mcmartin.ca (Kyle McMartin) Date: Tue, 5 Aug 2008 17:55:00 -0400 Subject: When will we stop shipping WLAN improvements ahead of upstream in released Fedora version? In-Reply-To: <4898C09D.9000504@redhat.com> References: <486F6F7E.8070809@leemhuis.info> <486F8FE0.6070401@leemhuis.info> <486F985C.3090803@leemhuis.info> <486F6F7E.8070809@leemhuis.info> <20080707153710.GD28109@redhat.com> <20080731213044.GB12820@redhat.com> <4898C09D.9000504@redhat.com> Message-ID: <20080805215500.GA3521@phobos.i.cabal.ca> On Tue, Aug 05, 2008 at 05:05:33PM -0400, Chuck Ebbert wrote: > John W. Linville wrote: >> >> I still think that for continuity's sake f8 and f9 should continue >> to get wireless fixes from 2.6.27. Those should only be specific >> bug fixes (although I suppose there is still time for a new driver), >> so hopefully the nattering nabobs won't be opposed to continuing with >> that part of the original plan. >> > > If you push wireless fixes to -stable Fedora would then get them for "free". > I don't see many wireless patches in there generally, though the ath5k > memory corruption fix just went in. > > And new drivers would be great. Lots of people seem to want ath9k, for > example. > John has been forwarding me fixes, I just haven't gotten around to applying them yet. Will do so tonight. r, Kyle From airlied at redhat.com Wed Aug 6 00:57:52 2008 From: airlied at redhat.com (Dave Airlie) Date: Wed, 06 Aug 2008 10:57:52 +1000 Subject: kernel-2.6.27-0.215.rc1.git4.fc10.i686 oops and no X :( In-Reply-To: <20080805201820.GE32404@phobos.i.cabal.ca> References: <458750.64402.qm@web52607.mail.re2.yahoo.com> <20080805201639.GD32404@phobos.i.cabal.ca> <20080805201820.GE32404@phobos.i.cabal.ca> Message-ID: <1217984272.19781.0.camel@clockmaker.usersys.redhat.com> On Tue, 2008-08-05 at 16:18 -0400, Kyle McMartin wrote: > On Tue, Aug 05, 2008 at 04:16:39PM -0400, Kyle McMartin wrote: > > On Tue, Aug 05, 2008 at 12:37:32PM -0700, Antonio Olivares wrote: > > > Dear fellow testers, > > > > > > New kernel oops again and no X when starting it > > > > > > kernel-2.6.27-0.215.rc1.git4.fc10.i686 > > > > > > Here's oops > > > > > > http://www.kerneloops.org/submitresult.php?number=48331 > > > > > > > nasty... did this just start recently? > > > > Any thoughts, Dave? > > > > fwiw this is hitting the BUG_ON in drm_open. > > mutex_lock(&dev->struct_mutex); > BUG_ON((dev->dev_mapping != NULL) && > (dev->dev_mapping != inode->i_mapping)); > if (dev->dev_mapping == NULL) > dev->dev_mapping = inode->i_mapping; > mutex_unlock(&dev->struct_mutex); > should be fixed in 222 or somewhere around that, at least the bug that is open for it said that. Dave. From linville at redhat.com Wed Aug 6 14:27:42 2008 From: linville at redhat.com (John W. Linville) Date: Wed, 6 Aug 2008 10:27:42 -0400 Subject: When will we stop shipping WLAN improvements ahead of upstream in released Fedora version? In-Reply-To: <4898C09D.9000504@redhat.com> References: <486F6F7E.8070809@leemhuis.info> <486F8FE0.6070401@leemhuis.info> <486F985C.3090803@leemhuis.info> <486F6F7E.8070809@leemhuis.info> <20080707153710.GD28109@redhat.com> <20080731213044.GB12820@redhat.com> <4898C09D.9000504@redhat.com> Message-ID: <20080806142742.GA19352@redhat.com> On Tue, Aug 05, 2008 at 05:05:33PM -0400, Chuck Ebbert wrote: > John W. Linville wrote: > > > >I still think that for continuity's sake f8 and f9 should continue > >to get wireless fixes from 2.6.27. Those should only be specific > >bug fixes (although I suppose there is still time for a new driver), > >so hopefully the nattering nabobs won't be opposed to continuing with > >that part of the original plan. > > > > If you push wireless fixes to -stable Fedora would then get them for "free". > I don't see many wireless patches in there generally, though the ath5k > memory corruption fix just went in. Well I see where you had to revert a few in the F-9 changelogs as you rebased on later -stable kernels, so there must be a few getting through. :-) If you would like to nominate more wireless fixes for -stable, feel free to do so. As it is, I mostly rely on my driver/stack maintainers to identify appropriate patches for stable -- they are aware of the process, including the Cc: stable at kernel.org trick. Even so, that only works for those problems which date back to 2.6.26. Since Fedora kernels already have 2.6.27 code, then the 2.6.27 patches would seem appropriate for Fedora too. Of course you could elide the 2.6.27 code from the Fedora kernels as you have suggested elsewhere, but then you will reintroduce other problems. > And new drivers would be great. Lots of people seem to want ath9k, for > example. We'll see. Honestly I've been dropping other things in favor of keeping Fedora up-to-date for the last year or more. Rather than find ways to spend just as much time on Fedora while "getting less bang for my buck", I'll probably find something else to occupy more of my time. In particular, I think ath9k will make it into the 2.6.27 queue. John -- John W. Linville linville at redhat.com From nominalises at junbang.com.cn Thu Aug 7 08:35:47 2008 From: nominalises at junbang.com.cn (Aldredge Rodibaugh) Date: Thu, 07 Aug 2008 08:35:47 +0000 Subject: :o) Message-ID: <3219477698.20080807082406@junbang.com.cn> Salve, From jwboyer at gmail.com Thu Aug 7 18:02:56 2008 From: jwboyer at gmail.com (Josh Boyer) Date: Thu, 07 Aug 2008 14:02:56 -0400 Subject: kernel-vanilla builds for 2.6.27-rc1 In-Reply-To: <1217905265.2328.52.camel@localhost.localdomain> References: <1217905265.2328.52.camel@localhost.localdomain> Message-ID: <1218132176.2328.74.camel@localhost.localdomain> On Mon, 2008-08-04 at 23:01 -0400, Josh Boyer wrote: > http://jwboyer.fedorapeople.org/pub/ > > Let the kernel installs begin. > > Hopefully I didn't fsck something up horridly. If I did, then I'll fix > it for -rc2. Updated to -rc2 builds now. And the kernel-firmware Requires issue should be fixed up thanks to Jarod. josh From snecklifter at gmail.com Thu Aug 7 23:39:17 2008 From: snecklifter at gmail.com (Christopher Brown) Date: Fri, 8 Aug 2008 00:39:17 +0100 Subject: kernel-vanilla builds for 2.6.27-rc1 In-Reply-To: <1218132176.2328.74.camel@localhost.localdomain> References: <1217905265.2328.52.camel@localhost.localdomain> <1218132176.2328.74.camel@localhost.localdomain> Message-ID: <364d303b0808071639v63dd5641vd10e99ac1153251c@mail.gmail.com> 2008/8/7 Josh Boyer : > On Mon, 2008-08-04 at 23:01 -0400, Josh Boyer wrote: >> http://jwboyer.fedorapeople.org/pub/ >> >> Let the kernel installs begin. >> >> Hopefully I didn't fsck something up horridly. If I did, then I'll fix >> it for -rc2. > > Updated to -rc2 builds now. And the kernel-firmware Requires issue > should be fixed up thanks to Jarod. It looks all good from here. I'll be posting a diff of the vanilla and ummm ... blueberry ... dmesg in a moment. Any caveats, gotchas, test suites? -- Christopher Brown http://www.chruz.com From jwboyer at gmail.com Fri Aug 8 00:43:28 2008 From: jwboyer at gmail.com (Josh Boyer) Date: Thu, 07 Aug 2008 20:43:28 -0400 Subject: kernel-vanilla builds for 2.6.27-rc1 In-Reply-To: <364d303b0808071639v63dd5641vd10e99ac1153251c@mail.gmail.com> References: <1217905265.2328.52.camel@localhost.localdomain> <1218132176.2328.74.camel@localhost.localdomain> <364d303b0808071639v63dd5641vd10e99ac1153251c@mail.gmail.com> Message-ID: <1218156208.2328.84.camel@localhost.localdomain> On Fri, 2008-08-08 at 00:39 +0100, Christopher Brown wrote: > 2008/8/7 Josh Boyer : > > On Mon, 2008-08-04 at 23:01 -0400, Josh Boyer wrote: > >> http://jwboyer.fedorapeople.org/pub/ > >> > >> Let the kernel installs begin. > >> > >> Hopefully I didn't fsck something up horridly. If I did, then I'll fix > >> it for -rc2. > > > > Updated to -rc2 builds now. And the kernel-firmware Requires issue > > should be fixed up thanks to Jarod. > > It looks all good from here. I'll be posting a diff of the vanilla and > ummm ... blueberry ... dmesg in a moment. Any caveats, gotchas, test > suites? As for gotchas, well, it's a -rc2 kernel so be warned. But the same is true of rawhide in general. My current plan is to only do vanilla builds for -rc and final releases, unless a particular -rc is really badly broken and a git snapshot fixes quite a bit. A few caveats below. The intention isn't to provide an "alternative" kernel. It's more for those that want to test something and see if it works on vanilla as opposed to a patched Fedora kernel. That should be quite rare, as the Fedora kernels are fairly top notch and don't differ much from vanilla anyway. I'm sure some will use it as a "primary" kernel, but they should realize there is no support for these and the likely response will be "try rawhide" and/or "please report it to the Linux kernel mailing list". Also, due to quota limitations I can really only host one kernel version at a time. That means as soon as -rc3 comes out, the current builds are replaced. As for test suites, I'm not aware of any except those that are already available for any kernel such as LTP or the various benchmarks. josh From reacquaint at bt.ro Sat Aug 9 17:42:30 2008 From: reacquaint at bt.ro (Trafford Kibbey) Date: Sat, 09 Aug 2008 17:42:30 +0000 Subject: :o) Message-ID: <9625317837.20080809173252@bt.ro> Hoi, From snecklifter at gmail.com Sat Aug 9 22:20:18 2008 From: snecklifter at gmail.com (Christopher Brown) Date: Sat, 9 Aug 2008 23:20:18 +0100 Subject: kernel-vanilla builds for 2.6.27-rc1 In-Reply-To: <1218156208.2328.84.camel@localhost.localdomain> References: <1217905265.2328.52.camel@localhost.localdomain> <1218132176.2328.74.camel@localhost.localdomain> <364d303b0808071639v63dd5641vd10e99ac1153251c@mail.gmail.com> <1218156208.2328.84.camel@localhost.localdomain> Message-ID: <364d303b0808091520u1dd8fdd6kd56233162a1def1c@mail.gmail.com> 2008/8/8 Josh Boyer : > On Fri, 2008-08-08 at 00:39 +0100, Christopher Brown wrote: >> 2008/8/7 Josh Boyer : >> > On Mon, 2008-08-04 at 23:01 -0400, Josh Boyer wrote: >> >> http://jwboyer.fedorapeople.org/pub/ >> >> >> >> Let the kernel installs begin. >> >> >> >> Hopefully I didn't fsck something up horridly. If I did, then I'll fix >> >> it for -rc2. >> > >> > Updated to -rc2 builds now. And the kernel-firmware Requires issue >> > should be fixed up thanks to Jarod. >> >> It looks all good from here. I'll be posting a diff of the vanilla and >> ummm ... blueberry ... dmesg in a moment. Any caveats, gotchas, test >> suites? > > As for gotchas, well, it's a -rc2 kernel so be warned. But the same is > true of rawhide in general. > > My current plan is to only do vanilla builds for -rc and final releases, > unless a particular -rc is really badly broken and a git snapshot fixes > quite a bit. A few caveats below. > > The intention isn't to provide an "alternative" kernel. It's more for > those that want to test something and see if it works on vanilla as > opposed to a patched Fedora kernel. That should be quite rare, as the > Fedora kernels are fairly top notch and don't differ much from vanilla > anyway. Then I suppose this begs the question - why aren't we shipping a vanilla kernel to begin with? I'm sure there are excellent answers and I'm aware of some of them already. I do think it would be good to pimp this a bit more and that it could be offered as a viable alternative. Or do I have my head in clouds I don't understand? Probably. > I'm sure some will use it as a "primary" kernel, but they should realize > there is no support for these and the likely response will be "try > rawhide" and/or "please report it to the Linux kernel mailing list". On the contrary would this not bring greater support. At the moment mainline ask people with bugs to test with mainline which your average joe has difficulty with. > Also, due to quota limitations I can really only host one kernel version > at a time. That means as soon as -rc3 comes out, the current builds are > replaced. Understood, but if there was some way to get this added into the official repositories do the Fedora kernel bods see an opportunity? Cheers -- Christopher Brown http://www.chruz.com From jwboyer at gmail.com Sat Aug 9 23:46:44 2008 From: jwboyer at gmail.com (Josh Boyer) Date: Sat, 09 Aug 2008 19:46:44 -0400 Subject: kernel-vanilla builds for 2.6.27-rc1 In-Reply-To: <364d303b0808091520u1dd8fdd6kd56233162a1def1c@mail.gmail.com> References: <1217905265.2328.52.camel@localhost.localdomain> <1218132176.2328.74.camel@localhost.localdomain> <364d303b0808071639v63dd5641vd10e99ac1153251c@mail.gmail.com> <1218156208.2328.84.camel@localhost.localdomain> <364d303b0808091520u1dd8fdd6kd56233162a1def1c@mail.gmail.com> Message-ID: <1218325604.2328.116.camel@localhost.localdomain> On Sat, 2008-08-09 at 23:20 +0100, Christopher Brown wrote: > > The intention isn't to provide an "alternative" kernel. It's more for > > those that want to test something and see if it works on vanilla as > > opposed to a patched Fedora kernel. That should be quite rare, as the > > Fedora kernels are fairly top notch and don't differ much from vanilla > > anyway. > > Then I suppose this begs the question - why aren't we shipping a > vanilla kernel to begin with? Because there are patches that _are_ carried in Fedora that aren't upstream. Execshield, utrace, etc. And of course, the Fedora kernel developers put bug fix patches into Fedora while things are being worked upstream. Also, while rawhide tends to track vanilla very closely, the release version kernels do often care additional backports and fixes for things like wireless, etc. Just shipping the stock vanilla kernel there, while not being horrible, wouldn't have the same functionality that Fedora does. > I'm sure there are excellent answers and I'm aware of some of them > already. I do think it would be good to pimp this a bit more and that > it could be offered as a viable alternative. > > Or do I have my head in clouds I don't understand? Probably. In the clouds, no. It's just not feasible at the moment. > > Also, due to quota limitations I can really only host one kernel version > > at a time. That means as soon as -rc3 comes out, the current builds are > > replaced. > > Understood, but if there was some way to get this added into the > official repositories do the Fedora kernel bods see an opportunity? I personally don't. It's an additional kernel, which we've avoided to date in the official repositories for good reasons. It's also a lower valued download target, and having it sitting there on the official mirrors takes up roughly 2.4 GiB. josh From enamellists at castimis.com Mon Aug 11 08:56:34 2008 From: enamellists at castimis.com (Chrzan Kiepert) Date: Mon, 11 Aug 2008 08:56:34 +0000 Subject: Lawmaker Wants Schools To Phase Out Fluff Message-ID: <4573835565.20080811084340@castimis.com> Hej, From nayankumarp at hotmail.com Wed Aug 13 18:23:14 2008 From: nayankumarp at hotmail.com (nayan kumar) Date: Wed, 13 Aug 2008 23:53:14 +0530 Subject: warning :section mismatch while compiling fedora 2.6.21-1.3194.fc7 kernel Message-ID: Hi All while compiling linux kernel downloaded from kernel.org i am getting warning as given below WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc1001171) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc10013e6) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'probe_bigsmp' (at offset 0xc1002012) and 'init_apic_ldr' WARNING: vmlinux - Section mismatch: reference to .init.text:find_unisys_acpi_oem_table from .text between 'acpi_madt_oem_check' (at offset 0xc1002220) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:parse_unisys_oem from .text between 'acpi_madt_oem_check' (at offset 0xc100226d) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:setup_unisys from .text between 'acpi_madt_oem_check' (at offset 0xc1002274) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:parse_unisys_oem from .text between 'mps_oem_check' (at offset 0xc100220d) and 'acpi_madt_oem_check' WARNING: vmlinux - Section mismatch: reference to .init.text:es7000_sw_apic from .text between 'enable_apic_mode' (at offset 0xc1002284) and 'check_apicid_present' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc100a8a9) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc100a8bf) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc100ad9b) and 'detect_ht' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc100ada5) and 'detect_ht' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc11f990a) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc106d7e1) and 's_start' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'vgacon_startup' (at offset 0xc10f3987) and 'vgacon_scrolldelta' WARNING: vmlinux - Section mismatch: reference to .init.data:logo_linux_clut224 from .text between 'fb_find_logo' (at offset 0xc10fc5a8) and 'backlight_class_release' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc11f9f7e) and '_etext' The same warnings are also being reported when I compile my external module using the above built kernel. Is there any suggestions on how to solve this problem...? thanks in advance.. regards _________________________________________________________________ Searching for the best deals on travel? Visit MSN Travel. http://msn.coxandkings.co.in/cnk/cnk.do From roland at redhat.com Thu Aug 14 01:22:51 2008 From: roland at redhat.com (Roland McGrath) Date: Wed, 13 Aug 2008 18:22:51 -0700 (PDT) Subject: kernel-doc Message-ID: <20080814012251.B923C154495@magilla.localdomain> I reenabled kernel-doc and tweaked it up. * Make htmldocs too. Some pithy bits are only in the .tmpl stuff and it is nice to be able to point people at "install kernel-doc and point your browser at file:///...", etc. * make in %build, only install in %install. Pure rpm anality. * Use %{?_smp_mflags}. mandocs is slow enough already. * New macro switch %{doc_build_fail} to suppress barfing on 'make mandocs' failure. We should get real kernel-doc and can eyeball the logs for errors, but won't be breaking our builds on every rebase where upstream tweaked comments so they broke kerneldoc. The switch defaults from %{released_kernel}, so we should break again if kernel-doc would come out bogus in a non-rawhide build. No extra human intervention required. * Install in kernel-doc-%{rpmversion} (.27) subdir, not -%{kversion} (.26). It was obviously insane to have kernel-doc-2.6.27-0.xyz.fc10 that installs /usr/share/doc/kernel-doc-2.6.26/ files. Gabba gabba, Roland From amruth_pv at yahoo.com Thu Aug 14 15:31:00 2008 From: amruth_pv at yahoo.com (amruth) Date: Thu, 14 Aug 2008 08:31:00 -0700 (PDT) Subject: KGDB kernel panic no init found in linux 2.6.26 after booting KGDB enabled Message-ID: <60461.48422.qm@web45207.mail.sp1.yahoo.com> Hi > All > I am configuring linux 2.6.26 kernel in laptop and > transferring image to desktop. > My desktop is IDE drive. I am getting kernel panic try > init= option error after booting the kernel. > I am trying to setup KGDB on linux 2.6.26 kernel between > dev machine and test machine. I have issues and it is not > working. > I can get the kgdb to communicate but I cannot start init > images to start. I am using Redhat grub configuration. > Do we need apply any patch for 2.6.26 kernel. I am using > 2.4.15.5-kgdb patch. I can get communication to work after > applying patches. > The system gets into kernel panic after the connection is > made because of corrupted initram image. > Can anybody please give me sample grub entry so that I can > try. > Should we use init-2.6-kgdb.img or not. If yes how to > create it, what about modules in /lib/modules/2.6.../ > Can you please let me know how to fix this issue. > After KGDB is enabled the kernel gets into panic mode > otherwise it works fine.Can anybody please let me know why > KGDB crashes the system. > > Thanks > Amruth p.v > > > > > > > > -- > To unsubscribe from this list: send the line > "unsubscribe linux-usb" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at > http://vger.kernel.org/majordomo-info.html From jwilson at redhat.com Mon Aug 18 17:13:26 2008 From: jwilson at redhat.com (Jarod Wilson) Date: Mon, 18 Aug 2008 13:13:26 -0400 Subject: RFC: split changelog out of spec Message-ID: <48A9ADB6.6040703@redhat.com> Hey all, Been toying with the idea of splitting the changelog out of the kernel spec itself, to reduce the size of the spec file. Basically, instead of %changelog followed by all the entries, it'd be %include %{SOURCE1}, which is a file 'fedora-kernel-changelog', which carries all the usual changelog entries. Its reasonably trivial to implement, though my current hack-around for 'make clog' complains about me redefining the clog target. Is shaving 800+ lines out of the spec file (only to put them in another file) worth the hassle though? -- Jarod Wilson jarod at redhat.com From linville at redhat.com Mon Aug 18 17:16:37 2008 From: linville at redhat.com (John W. Linville) Date: Mon, 18 Aug 2008 13:16:37 -0400 Subject: RFC: split changelog out of spec In-Reply-To: <48A9ADB6.6040703@redhat.com> References: <48A9ADB6.6040703@redhat.com> Message-ID: <20080818171637.GA6361@redhat.com> On Mon, Aug 18, 2008 at 01:13:26PM -0400, Jarod Wilson wrote: > Is shaving > 800+ lines out of the spec file (only to put them in another file) worth > the hassle though? I don't see how. What is the motivation? -- John W. Linville linville at redhat.com From davej at redhat.com Mon Aug 18 17:20:05 2008 From: davej at redhat.com (Dave Jones) Date: Mon, 18 Aug 2008 13:20:05 -0400 Subject: RFC: split changelog out of spec In-Reply-To: <48A9ADB6.6040703@redhat.com> References: <48A9ADB6.6040703@redhat.com> Message-ID: <20080818172005.GB18771@redhat.com> On Mon, Aug 18, 2008 at 01:13:26PM -0400, Jarod Wilson wrote: > Hey all, > > Been toying with the idea of splitting the changelog out of the kernel spec > itself, to reduce the size of the spec file. Basically, instead of %changelog > followed by all the entries, it'd be %include %{SOURCE1}, which is a file > 'fedora-kernel-changelog', which carries all the usual changelog entries. Its > reasonably trivial to implement, though my current hack-around for 'make clog' > complains about me redefining the clog target. Is shaving 800+ lines out of > the spec file (only to put them in another file) worth the hassle though? Probably not until we move away from CVS to an SCM that doesn't suck. It'd be nice if 'make build' slurped the changelog out of the SCM. Dave -- http://www.codemonkey.org.uk From jwilson at redhat.com Mon Aug 18 17:41:14 2008 From: jwilson at redhat.com (Jarod Wilson) Date: Mon, 18 Aug 2008 13:41:14 -0400 Subject: RFC: split changelog out of spec In-Reply-To: <20080818172005.GB18771@redhat.com> References: <48A9ADB6.6040703@redhat.com> <20080818172005.GB18771@redhat.com> Message-ID: <48A9B43A.40509@redhat.com> Dave Jones wrote: > On Mon, Aug 18, 2008 at 01:13:26PM -0400, Jarod Wilson wrote: > > Hey all, > > > > Been toying with the idea of splitting the changelog out of the kernel spec > > itself, to reduce the size of the spec file. Basically, instead of %changelog > > followed by all the entries, it'd be %include %{SOURCE1}, which is a file > > 'fedora-kernel-changelog', which carries all the usual changelog entries. Its > > reasonably trivial to implement, though my current hack-around for 'make clog' > > complains about me redefining the clog target. Is shaving 800+ lines out of > > the spec file (only to put them in another file) worth the hassle though? > > Probably not until we move away from CVS to an SCM that doesn't suck. > It'd be nice if 'make build' slurped the changelog out of the SCM. I stupidly left out the part where I was supposed to mention that what I had in mind longer-term was that it'd be more straight-forward to manipulate a stand-alone changelog, esp. if we could just dump the changelog out of our SCM. (Some of what Don and Vivek are doing for RHEL w/git is what motivated me in the first place). We could also, if so desired, install the split-out changelog as a %doc file, the thought being that not everyone knows to look at 'rpm -q --changelog' output or look in the srpm/cvs/etc to see what's changed. John W. Linville wrote: > I don't see how. What is the motivation? Apologies, see above. :) -- Jarod Wilson jarod at redhat.com From nhorman at redhat.com Mon Aug 18 17:43:27 2008 From: nhorman at redhat.com (Neil Horman) Date: Mon, 18 Aug 2008 13:43:27 -0400 Subject: RFC: split changelog out of spec In-Reply-To: <20080818172005.GB18771@redhat.com> References: <48A9ADB6.6040703@redhat.com> <20080818172005.GB18771@redhat.com> Message-ID: <20080818174327.GG7052@hmsendeavour.rdu.redhat.com> On Mon, Aug 18, 2008 at 01:20:05PM -0400, Dave Jones wrote: > On Mon, Aug 18, 2008 at 01:13:26PM -0400, Jarod Wilson wrote: > > Hey all, > > > > Been toying with the idea of splitting the changelog out of the kernel spec > > itself, to reduce the size of the spec file. Basically, instead of %changelog > > followed by all the entries, it'd be %include %{SOURCE1}, which is a file > > 'fedora-kernel-changelog', which carries all the usual changelog entries. Its > > reasonably trivial to implement, though my current hack-around for 'make clog' > > complains about me redefining the clog target. Is shaving 800+ lines out of > > the spec file (only to put them in another file) worth the hassle though? > > Probably not until we move away from CVS to an SCM that doesn't suck. > It'd be nice if 'make build' slurped the changelog out of the SCM. > > Dave > I suppose that you could make the argument that including the changelog at all isn't really needed if you have it properly stored in scm. i.e if we used git the way the rhel trees are handled, and auto-generate patches based on commits, all we would really need to do is mark the base tree that we started from and the final tag that we're building, and you could extract the changelog at your leisure Neil > -- > http://www.codemonkey.org.uk > > _______________________________________________ > Fedora-kernel-list mailing list > Fedora-kernel-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-kernel-list -- /*************************************************** *Neil Horman *Senior Software Engineer *Red Hat, Inc. *nhorman at redhat.com *gpg keyid: 1024D / 0x92A74FA1 *http://pgp.mit.edu ***************************************************/ From drago01 at gmail.com Mon Aug 18 17:43:49 2008 From: drago01 at gmail.com (drago01) Date: Mon, 18 Aug 2008 19:43:49 +0200 Subject: RFC: split changelog out of spec In-Reply-To: <48A9B43A.40509@redhat.com> References: <48A9ADB6.6040703@redhat.com> <20080818172005.GB18771@redhat.com> <48A9B43A.40509@redhat.com> Message-ID: On Mon, Aug 18, 2008 at 7:41 PM, Jarod Wilson wrote: > We could also, if so desired, install the split-out changelog as a %doc > file, the thought being that not everyone knows to look at 'rpm -q > --changelog' output or look in the srpm/cvs/etc to see what's changed. This would just confuse user and is inconsistent with the rest of the distro... From linville at redhat.com Mon Aug 18 17:52:15 2008 From: linville at redhat.com (John W. Linville) Date: Mon, 18 Aug 2008 13:52:15 -0400 Subject: RFC: split changelog out of spec In-Reply-To: References: <48A9ADB6.6040703@redhat.com> <20080818172005.GB18771@redhat.com> <48A9B43A.40509@redhat.com> Message-ID: <20080818175215.GB6361@redhat.com> On Mon, Aug 18, 2008 at 07:43:49PM +0200, drago01 wrote: > On Mon, Aug 18, 2008 at 7:41 PM, Jarod Wilson wrote: > > We could also, if so desired, install the split-out changelog as a %doc > > file, the thought being that not everyone knows to look at 'rpm -q > > --changelog' output or look in the srpm/cvs/etc to see what's changed. > > This would just confuse user and is inconsistent with the rest of the distro... I presume the rpm command would still work, so I would see no harm in adding the changelog as a %doc (if/when it is broken-out from the spec file). John -- John W. Linville linville at redhat.com From jwilson at redhat.com Mon Aug 18 18:09:17 2008 From: jwilson at redhat.com (Jarod Wilson) Date: Mon, 18 Aug 2008 14:09:17 -0400 Subject: RFC: split changelog out of spec In-Reply-To: <20080818175215.GB6361@redhat.com> References: <48A9ADB6.6040703@redhat.com> <20080818172005.GB18771@redhat.com> <48A9B43A.40509@redhat.com> <20080818175215.GB6361@redhat.com> Message-ID: <48A9BACD.80109@redhat.com> John W. Linville wrote: > On Mon, Aug 18, 2008 at 07:43:49PM +0200, drago01 wrote: >> On Mon, Aug 18, 2008 at 7:41 PM, Jarod Wilson wrote: >>> We could also, if so desired, install the split-out changelog as a %doc >>> file, the thought being that not everyone knows to look at 'rpm -q >>> --changelog' output or look in the srpm/cvs/etc to see what's changed. >> This would just confuse user and is inconsistent with the rest of the distro... How so? > I presume the rpm command would still work Correct. > so I would see no harm > in adding the changelog as a %doc (if/when it is broken-out from the > spec file). Just to be clear... To make sure its 100% clear which kernel the changelog matches up with, it'd have to be %doc'd for each kernel and kernel-flavour, so it winds up in /usr/share/doc/kernel%{?flavour:-%{flavour}}-%{version}. If its part of kernel-doc, I think its not always obvious which actual kernel package it matches. With those clarifications, I don't see how it'd be confusing, or how it would cause any meaningful consistency problems with other distros. But please do enlighten me if I'm missing something. :) -- Jarod Wilson jarod at redhat.com From drago01 at gmail.com Mon Aug 18 18:33:57 2008 From: drago01 at gmail.com (drago01) Date: Mon, 18 Aug 2008 20:33:57 +0200 Subject: RFC: split changelog out of spec In-Reply-To: <48A9BACD.80109@redhat.com> References: <48A9ADB6.6040703@redhat.com> <20080818172005.GB18771@redhat.com> <48A9B43A.40509@redhat.com> <20080818175215.GB6361@redhat.com> <48A9BACD.80109@redhat.com> Message-ID: On Mon, Aug 18, 2008 at 8:09 PM, Jarod Wilson wrote: > John W. Linville wrote: >> >> On Mon, Aug 18, 2008 at 07:43:49PM +0200, drago01 wrote: >>> >>> On Mon, Aug 18, 2008 at 7:41 PM, Jarod Wilson wrote: >>>> >>>> We could also, if so desired, install the split-out changelog as a %doc >>>> file, the thought being that not everyone knows to look at 'rpm -q >>>> --changelog' output or look in the srpm/cvs/etc to see what's changed. >>> >>> This would just confuse user and is inconsistent with the rest of the >>> distro... > > How so? Ignore me .. read that as "move the changelog out of the rpm" From confirm+y=y06tf9 at facebookmail.com Fri Aug 22 15:04:20 2008 From: confirm+y=y06tf9 at facebookmail.com (Facebook) Date: Fri, 22 Aug 2008 08:04:20 -0700 Subject: Arafat Bouchafra added you as a friend on Facebook... Message-ID: Arafat added you as a friend on Facebook. We need to confirm that you know Arafat in order for you to be friends on Facebook. To confirm this friend request, follow the link below: http://www.facebook.com/n/?reqs.php ___________________ This e-mail may contain promotional materials. If you do not wish to receive future commercial mailings from Facebook, please click on the link below. Facebook's offices are located at 156 University Ave., Palo Alto, CA 94301. http://www.facebook.com/o.php?u=1435671220&k=484b8e Want to control which emails you receive from Facebook? Go to: http://www.facebook.com/editaccount.php?notifications&md=ZnJpZW5kO2Zyb209MTQzOTI0MTI5NTt0bz0xNDM1NjcxMjIw From invite+y=y06tf9 at facebookmail.com Fri Aug 22 15:04:21 2008 From: invite+y=y06tf9 at facebookmail.com (Arafat Bouchafra) Date: Fri, 22 Aug 2008 08:04:21 -0700 Subject: =?utf-8?q?D=C3=A9couvre_mon_profil_Facebook?= Message-ID: <2bda045dc4710383d269418cce0ca4fa@localhost.localdomain> J'ai cr?? mon profil Facebook sur lequel je peux publier mes photos, mes vid?os et des ?v?nements. Je souhaite t'ajouter ? mes amis pour que tu puisses y acc?der. Pour cela, tu dois d'abord t'inscrire ? Facebook?! Tu pourras ensuite cr?er ton propre profil. Merci, Arafat Clique sur ce lien : http://www.facebook.com/p.php?i=1439241295&k=65GUQ4RZQ43M5FGEWE55ST&r&v=2 ___________________ Ce courrier ?lectronique peut contenir des messages publicitaires. Si vous ne souhaitez plus recevoir de messages publicitaires de la part de Facebook, cliquez sur le lien ci-dessous. Les bureaux de Facebook sont situ?s au 156 University Ave., Palo Alto, CA 94301. http://www.facebook.com/o.php?u=1435671220&k=484b8e From notchlu50 at starportsys.com Mon Aug 25 04:20:07 2008 From: notchlu50 at starportsys.com (Merle Rosario) Date: Mon, 25 Aug 2008 12:20:07 +0800 Subject: You are nominated for a Ph.d Message-ID: <01c906ac$e8fff580$6e141f7d@notchlu50> WHAT A GREAT IDEA! We provide a concept that will allow anyone with sufficient work experience to obtain a fully verifiable University Degree. Bachelors, Masters or even a Doctorate. For US: 1.781.634.7970 Outside US: +1.781.634.7970 "Just leave your NAME & PHONE NO. (with CountryCode)" in the voicemail. Our staff will get back to you in next few days! From todd.e.rinaldo at jpmorgan.com Mon Aug 25 18:26:23 2008 From: todd.e.rinaldo at jpmorgan.com (todd.e.rinaldo at jpmorgan.com) Date: Mon, 25 Aug 2008 13:26:23 -0500 Subject: UNIX Process range 32769-65535 impossible? Message-ID: Hi, We have a need to increase the kernel pid_max. Right now it's at the default 32768. The maximum allowable we can increase to is 99,999 due to 3rd party vendor limitations. When we increased it to that value this weekend, we noticed that even though next pid increased sequentially, the range 32769-65535 was explicitly skipped. I note that the range 32769-65535 would be the negative numbers in a signed 2 byte int. This indicates to me that maybe there is some sort of design/legacy issue forcing this behaviour. Because we can only increase to 99,9999, not having access to the above range has limited our available pids by 1/3. Could anyone point me to some sort of documentation explaining this logic? Thanks for your help, Todd Rinaldo Generally, this communication is for informational purposes only and it is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. In the event you are receiving the offering materials attached below related to your interest in hedge funds or private equity, this communication may be intended as an offer or solicitation for the purchase or sale of such fund(s). All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities. From doug.chapman at hp.com Mon Aug 25 18:27:16 2008 From: doug.chapman at hp.com (Doug Chapman) Date: Mon, 25 Aug 2008 14:27:16 -0400 Subject: boot failures on very-large systems with CONFIG_SYSFS_DEPRECATED not set Message-ID: <1219688836.19785.13.camel@localhost.localdomain> Sometime leading up to the F9 kernel my very large ia64 system (64 cpu 1TB ram, bunch of PCI busses and I/O) fails to boot. It appears to be something in how nash/mkinitrd gets information from sysfs. Since this is an early boot-time issue and nash isn't very easy to debug I am having trouble getting to the root of the issue (but I am still investigating). I have however found what change triggered this. The default config file used to have CONFIG_SYSFS_DEPRECATED=y set. Upstream kernel commit d47846c5866b7d98a1173c86a39d810a06647329 renamed this to CONFIG_SYSFS_DEPRECATED_V2. It appears the default is still "y" however somehow with the transition the Fedora kernel now has this off. If possible I would like to see this get set to "y" for now. I will continue to debug this as it certainly _should_ boot just fine without this set. Even if we just turn it on for ia64 that works for me (but I imagine some new big x86_64 systems may run into it once they grow this large). thanks, - Doug From jwilson at redhat.com Tue Aug 26 14:22:12 2008 From: jwilson at redhat.com (Jarod Wilson) Date: Tue, 26 Aug 2008 10:22:12 -0400 Subject: boot failures on very-large systems with CONFIG_SYSFS_DEPRECATED not set In-Reply-To: <1219688836.19785.13.camel@localhost.localdomain> References: <1219688836.19785.13.camel@localhost.localdomain> Message-ID: <200808261022.12693.jwilson@redhat.com> On Monday 25 August 2008 14:27:16 Doug Chapman wrote: > Sometime leading up to the F9 kernel my very large ia64 system (64 cpu > 1TB ram, bunch of PCI busses and I/O) fails to boot. It appears to be > something in how nash/mkinitrd gets information from sysfs. Since this > is an early boot-time issue and nash isn't very easy to debug I am > having trouble getting to the root of the issue (but I am still > investigating). > > I have however found what change triggered this. The default config > file used to have CONFIG_SYSFS_DEPRECATED=y set. Upstream kernel commit > d47846c5866b7d98a1173c86a39d810a06647329 renamed this to > CONFIG_SYSFS_DEPRECATED_V2. It appears the default is still "y" however > somehow with the transition the Fedora kernel now has this off. > > If possible I would like to see this get set to "y" for now. I will > continue to debug this as it certainly _should_ boot just fine without > this set. Even if we just turn it on for ia64 that works for me (but I > imagine some new big x86_64 systems may run into it once they grow this > large). Just committed the change to flip those on for ia64-only. -- Jarod Wilson jarod at redhat.com From SteveD at redhat.com Wed Aug 27 16:48:41 2008 From: SteveD at redhat.com (Steve Dickson) Date: Wed, 27 Aug 2008 12:48:41 -0400 Subject: [PATCH] nfs: BUG_ON in nfs_follow_mountpoint Message-ID: <48B58569.3020200@RedHat.com> Here is a patch that was posted a while back on lkml that does indeed stop a OOPS.... I notice that is not in the latest rawhide kernel... We might want to think about taking this one early due to the obvious... steved. From: "Denis V. Lunev" Unfortunately, BUG_ON(IS_ROOT(dentry)) can happen inside nfs_follow_mountpoint with NFS running Fedora 8 using a specific setup. See https://bugzilla.redhat.com/show_bug.cgi?id=458622 So the situation should be handled on NFS client gracefully. Signed-off-by: Denis V. Lunev Cc: Trond Myklebust Cc: J. Bruce Fields Signed-off-by: Andrew Morton --- fs/nfs/namespace.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff -puN fs/nfs/namespace.c~nfs-bug_on-in-nfs_follow_mountpoint fs/nfs/namespace.c --- a/fs/nfs/namespace.c~nfs-bug_on-in-nfs_follow_mountpoint +++ a/fs/nfs/namespace.c @@ -105,7 +105,10 @@ static void * nfs_follow_mountpoint(stru dprintk("--> nfs_follow_mountpoint()\n"); - BUG_ON(IS_ROOT(dentry)); + err = -EIO; + if (IS_ROOT(dentry)) + goto out_err; + dprintk("%s: enter\n", __func__); dput(nd->path.dentry); nd->path.dentry = dget(dentry); _ From jwilson at redhat.com Thu Aug 28 04:59:16 2008 From: jwilson at redhat.com (Jarod Wilson) Date: Thu, 28 Aug 2008 00:59:16 -0400 Subject: [PATCH] nfs: BUG_ON in nfs_follow_mountpoint In-Reply-To: <48B58569.3020200@RedHat.com> References: <48B58569.3020200@RedHat.com> Message-ID: <200808280059.16812.jwilson@redhat.com> On Wednesday 27 August 2008 12:48:41 Steve Dickson wrote: > Here is a patch that was posted a while back on lkml that does > indeed stop a OOPS.... I notice that is not in the latest rawhide > kernel... We might want to think about taking this one early due > to the obvious... The patch comments mention Fedora 8... Do we need/want this for the F8 and F9 kernels as well? > From: "Denis V. Lunev" > > Unfortunately, BUG_ON(IS_ROOT(dentry)) can happen inside > nfs_follow_mountpoint with NFS running Fedora 8 using a specific setup. > > See https://bugzilla.redhat.com/show_bug.cgi?id=458622 -- Jarod Wilson jarod at redhat.com From dwrcnorgem at rcnorge.dk Thu Aug 28 12:02:42 2008 From: dwrcnorgem at rcnorge.dk (Mike Wiggett-Bassett) Date: Thu, 28 Aug 2008 15:02:42 +0300 Subject: Potenzprobleme? Mit uns nicht mehr Message-ID: <01c9091f$1eac1500$37c66a4e@dwrcnorgem> Online bestellen - original Qualitaet - 100% wirksam Unsere Kunden: - Sex ist befriedigender denn je. Stress und Leistungsdruck verschwinden. Sie ist nie wieder frustriert, ich habe keine Angst mehr zu versagen. Es ist ein wundervolles koerperliches Erlebnis, dem ein genauso tiefes Gefuehl folgt. - Das Beste an Vi. ist die Sicherheit, dass man "mit Autopilot fliegt", dass man entspannt und ohne Sorgen zur Sache kommen kann, dass der Staender auch haelt, auch wenn man unterbrochen wird (die Kinder klopfen an die Schlafzimmertuer, der Hund bellt, das Kondom sitzt schlecht). Wenn man Vi. bewusst anwendet, kann es auch der Partnerin gegenueber ein grosses Geschenk sein. Nur ein Rat: Sagen Sie ihr nicht, dass Sie es verwenden, das weibliche Selbstwertgefuehl ist genauso verletzlich wie das unsere. Angebote des Monats: NEU - Vi. Super Active 100 mg 30 Tab. 81,08 Euro Vi. 10 Tab. 100 mg + Ci. 10 Tab. x 20 mg 48,95 Euro Vi. 10 Tab. 22,60 Euro Vi. 30 Tab. 55,00 Euro - Sie sparen: 17,00 Euro Vi. 60 Tab. 82,70 Euro - Sie sparen: 53,00 Euro Vi. 90 Tab. 118,00 Euro - Sie sparen: 85,00 Euro Ci. 10 - 27,00 Euro Ci. 20 - 54,00 Euro - Sie sparen: 2,00 Euro Ci. 30 - 72,00 Euro - Sie sparen: 11,00 Euro - bequem und diskret online bestellen. - Visa verifizierter Onlineshop - keine versteckte Kosten - diskrete Verpackung - diskrete Zahlung - kein peinlicher Arztbesuch erforderlich - kostenlose, arztliche Telefon-Beratung - kein langes Warten - Auslieferung innerhalb von 2-3 Tagen Bestellen Sie noch heute und vergessen Sie Ihre Enttaeuschungen, anhaltende Versagensaengste und wiederholte peinliche Situationen http://img60.imageshack.us/img60/4697/jgzpewbigyg4.swf From SteveD at redhat.com Fri Aug 29 12:59:32 2008 From: SteveD at redhat.com (Steve Dickson) Date: Fri, 29 Aug 2008 08:59:32 -0400 Subject: [PATCH] nfs: BUG_ON in nfs_follow_mountpoint In-Reply-To: <200808280059.16812.jwilson@redhat.com> References: <48B58569.3020200@RedHat.com> <200808280059.16812.jwilson@redhat.com> Message-ID: <48B7F2B4.8090308@RedHat.com> Jarod Wilson wrote: > On Wednesday 27 August 2008 12:48:41 Steve Dickson wrote: >> Here is a patch that was posted a while back on lkml that does >> indeed stop a OOPS.... I notice that is not in the latest rawhide >> kernel... We might want to think about taking this one early due >> to the obvious... > > The patch comments mention Fedora 8... Do we need/want this for the F8 and F9 > kernels as well? I would not be a bad idea... if the patch posted does not apply to either kernel let me know and I'll make it happen... steved.