From feng.xian at gmail.com Sun Nov 11 05:48:33 2007 From: feng.xian at gmail.com (Feng Xian) Date: Sat, 10 Nov 2007 23:48:33 -0600 Subject: How to build smp kernel Message-ID: <610b3d450711102148vaebd87al40b93ecc3df2e45e@mail.gmail.com> Hi, I had a 16-core machine and tried to build a smp version of linux-2.6.23 kernel. I did the following steps: 1. make menuconfig ( actually I didt change the configuration since it builds SMP support by default) 2. make; make modules; make modules_install; make install But the final image file is vmlinuz-2.6.23, not vmlinuz-2.6.23smp. Is this final image a real smp kernel? If not, do i need to apply patches. Thanks! Feng -- Addr: 1025N, 23rd str, APT 33, Lincoln, NE, 68503 Phone: (402)310-9826 WWW: cse.unl.edu/~fxian From jwilson at redhat.com Sun Nov 11 23:30:37 2007 From: jwilson at redhat.com (Jarod Wilson) Date: Sun, 11 Nov 2007 18:30:37 -0500 Subject: How to build smp kernel In-Reply-To: <610b3d450711102148vaebd87al40b93ecc3df2e45e@mail.gmail.com> References: <610b3d450711102148vaebd87al40b93ecc3df2e45e@mail.gmail.com> Message-ID: <4737909D.7020101@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Feng Xian wrote: > Hi, > > I had a 16-core machine and tried to build a smp version of > linux-2.6.23 kernel. I did the following steps: > > 1. make menuconfig ( actually I didt change the configuration since it > builds SMP support by default) All of our x86 and x86_64 kernels are smp-aware, there is no separate smp kernel, the same kernel is used for single-processor and multi-processor systems. > 2. make; make modules; make modules_install; make install > > But the final image file is vmlinuz-2.6.23, not vmlinuz-2.6.23smp. Is > this final image a real smp kernel? If not, do i need to apply > patches. Thanks! In the past when we did have a separate kernel-smp package (actually, we still do for ppc32), the 'smp' was inserted by part of the rpm build process, it doesn't happen automagically, just because you enabled smp in the kernel config. - -- Jarod Wilson jwilson at redhat.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHN5CdtO+bni+75QMRAsORAJsHxl06Z/pqEttj085JP5qPXOanIACgxO4m 4t55vz3JJAOfcWpo1Gcnf5c= =BzxM -----END PGP SIGNATURE----- From feng.xian at gmail.com Mon Nov 12 02:14:29 2007 From: feng.xian at gmail.com (Feng Xian) Date: Sun, 11 Nov 2007 20:14:29 -0600 Subject: How to build smp kernel In-Reply-To: <4737909D.7020101@redhat.com> References: <610b3d450711102148vaebd87al40b93ecc3df2e45e@mail.gmail.com> <4737909D.7020101@redhat.com> Message-ID: <610b3d450711111814i3f69a419x15de1e3dceaaa4bc@mail.gmail.com> Thanks! On 11/11/07, Jarod Wilson wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Feng Xian wrote: > > Hi, > > > > I had a 16-core machine and tried to build a smp version of > > linux-2.6.23 kernel. I did the following steps: > > > > 1. make menuconfig ( actually I didt change the configuration since it > > builds SMP support by default) > > All of our x86 and x86_64 kernels are smp-aware, there is no separate > smp kernel, the same kernel is used for single-processor and > multi-processor systems. > > > 2. make; make modules; make modules_install; make install > > > > But the final image file is vmlinuz-2.6.23, not vmlinuz-2.6.23smp. Is > > this final image a real smp kernel? If not, do i need to apply > > patches. Thanks! > > In the past when we did have a separate kernel-smp package (actually, we > still do for ppc32), the 'smp' was inserted by part of the rpm build > process, it doesn't happen automagically, just because you enabled smp > in the kernel config. > > - -- > Jarod Wilson > jwilson at redhat.com > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHN5CdtO+bni+75QMRAsORAJsHxl06Z/pqEttj085JP5qPXOanIACgxO4m > 4t55vz3JJAOfcWpo1Gcnf5c= > =BzxM > -----END PGP SIGNATURE----- > -- Addr: 1025N, 23rd str, APT 33, Lincoln, NE, 68503 Phone: (402)310-9826 WWW: cse.unl.edu/~fxian -------------- next part -------------- An HTML attachment was scrubbed... URL: From feng.xian at gmail.com Sun Nov 11 05:28:23 2007 From: feng.xian at gmail.com (Feng Xian) Date: Sat, 10 Nov 2007 23:28:23 -0600 Subject: hello! In-Reply-To: <207049.6045.qm@web36504.mail.mud.yahoo.com> References: <207049.6045.qm@web36504.mail.mud.yahoo.com> Message-ID: <610b3d450711102128qff68b22rb4c04ede6c58568e@mail.gmail.com> Hi, I had a 16-core machine and tried to build a smp version of linux-2.6.23 kernel. I did the following steps: 1. make menuconfig ( actually I didt change the configuration since it builds SMP support by default) 2. make; make modules; make modules_install; make install But the final image file is vmlinuz-2.6.23, not vmlinuz-2.6.23smp. Is this final image a real smp kernel? If not, do i need to apply patches. Thanks! Feng From tiagomatos at gmail.com Sun Nov 11 10:53:50 2007 From: tiagomatos at gmail.com (Rui Tiago Matos) Date: Sun, 11 Nov 2007 10:53:50 +0000 Subject: How to build smp kernel In-Reply-To: <610b3d450711102148vaebd87al40b93ecc3df2e45e@mail.gmail.com> References: <610b3d450711102148vaebd87al40b93ecc3df2e45e@mail.gmail.com> Message-ID: On 11/11/2007, Feng Xian wrote: > But the final image file is vmlinuz-2.6.23, not vmlinuz-2.6.23smp. Is > this final image a real smp kernel? If not, do i need to apply > patches. Thanks! Actually, these days, the kernel can autodetect at boot if it is running on an SMP system and activate support for it automatically. For instance here's a snippet from the fedora 8 kernel 2.6.23.1-42.fc8: CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU 0/0 -> Node 0 using mwait in idle threads. CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 CPU0: Thermal monitoring enabled (TM2) SMP alternatives: switching to UP code ACPI: Core revision 20070126 Using local APIC timer interrupts. APIC timer calibration result 12465172 Detected 12.465 MHz APIC timer. SMP alternatives: switching to SMP code Booting processor 1/2 APIC 0x1 Initializing CPU#1 Calibrating delay using timer specific routine.. 3988.84 BogoMIPS (lpj=1994422) CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU 1/1 -> Node 0 CPU: Physical Processor ID: 0 CPU: Processor Core ID: 1 CPU1: Thermal monitoring enabled (TM2) Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz stepping 0a Brought up 2 CPUs So, there, as you can see ther kernle is pretty smart nowadays. Also check the release notes: http://docs.fedoraproject.org/release-notes/f8/en_US/sn-Kernel.html#sn-Kernel-Flavors Good luck, Rui From snecklifter at gmail.com Sun Nov 11 11:58:51 2007 From: snecklifter at gmail.com (Christopher Brown) Date: Sun, 11 Nov 2007 11:58:51 +0000 Subject: How to build smp kernel In-Reply-To: <610b3d450711102148vaebd87al40b93ecc3df2e45e@mail.gmail.com> References: <610b3d450711102148vaebd87al40b93ecc3df2e45e@mail.gmail.com> Message-ID: <364d303b0711110358p5d3dfd1fj5f3c0f9e4797ac1a@mail.gmail.com> On 11/11/2007, Feng Xian wrote: > Hi, > > I had a 16-core machine and tried to build a smp version of > linux-2.6.23 kernel. I did the following steps: > > 1. make menuconfig ( actually I didt change the configuration since it > builds SMP support by default) > > 2. make; make modules; make modules_install; make install > > But the final image file is vmlinuz-2.6.23, not vmlinuz-2.6.23smp. Is > this final image a real smp kernel? If not, do i need to apply > patches. Thanks! Multiprocessor support is provided by default - there is no separate smp kernel (from Fedora 7 onwards I think). You should not need to apply additional patches. O/T : I'm back from vacation though extremely jet-lagged. Cheers Chris -- http://www.chruz.com From feng.xian at gmail.com Mon Nov 12 07:30:18 2007 From: feng.xian at gmail.com (Feng Xian) Date: Mon, 12 Nov 2007 01:30:18 -0600 Subject: How to change the number of processors in a 16-core machine Message-ID: <610b3d450711112330n16013119wce42fbb46ab67e28@mail.gmail.com> Hi, I am doing a scalable test on a 16-core machine (8 dual-core amd processors). So I need to vary the processors from 1 to 16. But I couldnt remove the cores from motherboard. Is there any way to achieve this by changing the max number of processors in the kernel? Thanks! From tiagomatos at gmail.com Mon Nov 12 09:48:41 2007 From: tiagomatos at gmail.com (Rui Tiago Matos) Date: Mon, 12 Nov 2007 09:48:41 +0000 Subject: How to change the number of processors in a 16-core machine In-Reply-To: <610b3d450711112330n16013119wce42fbb46ab67e28@mail.gmail.com> References: <610b3d450711112330n16013119wce42fbb46ab67e28@mail.gmail.com> Message-ID: On 12/11/2007, Feng Xian wrote: > Hi, > > I am doing a scalable test on a 16-core machine (8 dual-core amd > processors). So I need to vary the processors from 1 to 16. But I > couldnt remove the cores from motherboard. Is there any way to achieve > this by changing the max number of processors in the kernel? Thanks! >From Documentation/kernel-parameters.txt in a linux source tree: maxcpus= [SMP] Maximum number of processors that an SMP kernel should make use of. maxcpus=n : n >= 0 limits the kernel to using 'n' processors. n=0 is a special case, it is equivalent to "nosmp", which also disables the IO APIC. Just add that parameter on your grub config or directly on the grub shell. Rui From brugolsky at telemetry-investments.com Mon Nov 12 14:52:49 2007 From: brugolsky at telemetry-investments.com (Bill Rugolsky Jr.) Date: Mon, 12 Nov 2007 09:52:49 -0500 Subject: How to change the number of processors in a 16-core machine In-Reply-To: References: <610b3d450711112330n16013119wce42fbb46ab67e28@mail.gmail.com> Message-ID: <20071112145249.GA21189@ti88.telemetry-investments.com> On Mon, Nov 12, 2007 at 09:48:41AM +0000, Rui Tiago Matos wrote: > On 12/11/2007, Feng Xian wrote: > > Hi, > > > > I am doing a scalable test on a 16-core machine (8 dual-core amd > > processors). So I need to vary the processors from 1 to 16. But I > > couldnt remove the cores from motherboard. Is there any way to achieve > > this by changing the max number of processors in the kernel? Thanks! > > >From Documentation/kernel-parameters.txt in a linux source tree: > > maxcpus= [SMP] Maximum number of processors that an SMP kernel > should make use of. maxcpus=n : n >= 0 limits the > kernel to using 'n' processors. n=0 is a special case, > it is equivalent to "nosmp", which also disables > the IO APIC. > > Just add that parameter on your grub config or directly on the grub shell. With CPU hotplug, you don't even have to reboot. See Documentation/cpu-hotplug.txt: ... Command Line Switches --------------------- maxcpus=n Restrict boot time cpus to n. Say if you have 4 cpus, using maxcpus=2 will only boot 2. You can choose to bring the other cpus later online, read FAQ's for more info. additional_cpus=n (*) Use this to limit hotpluggable cpus. This option sets cpu_possible_map = cpu_present_map + additional_cpus ... Q: How do i logically offline a CPU? A: Do the following. #echo 0 > /sys/devices/system/cpu/cpuX/online [echo 1 into the same file to bring it back online.] Regards, Bill Rugolsky From brugolsky at telemetry-investments.com Mon Nov 12 15:00:04 2007 From: brugolsky at telemetry-investments.com (Bill Rugolsky Jr.) Date: Mon, 12 Nov 2007 10:00:04 -0500 Subject: How to change the number of processors in a 16-core machine In-Reply-To: <20071112145249.GA21189@ti88.telemetry-investments.com> References: <610b3d450711112330n16013119wce42fbb46ab67e28@mail.gmail.com> <20071112145249.GA21189@ti88.telemetry-investments.com> Message-ID: <20071112150004.GD16995@ti88.telemetry-investments.com> On Mon, Nov 12, 2007 at 09:52:49AM -0500, Bill Rugolsky Jr. wrote: > With CPU hotplug, you don't even have to reboot. One additional note: Since the Opteron boxes are NUMA, the memory topology (and any differences from the online CPU topology) may also affect your performance benchmark results. -Bill From feng.xian at gmail.com Mon Nov 12 21:13:15 2007 From: feng.xian at gmail.com (Feng Xian) Date: Mon, 12 Nov 2007 15:13:15 -0600 Subject: help! My re-compiled kernel always got crashed in a machine with scsi/sata disk Message-ID: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> Thanks for all your help. I ran into another problem. My 16-core machine has a scsi/sata disk. I have enabled all important features related with scsi and sata. I built 2.6.23 kernel on this machine. But the kernel always got crashed randomly. Sometimes it couldnot even boot, reporting some random errors, like "segment violation, sleep for 40 seconds", or "Group volume VolGroup00 uses lvm2 metadata: read-only", then jump to a strange login window that I cannot log in using my root password. Another thing is that Linux works perfect if I installed Fecore Core 7 on this multi-core machine with scsi/sata disk. Why it didnt work if I used re-compiled kernel. I guess it is because I didnt config kernel right (although I enabled all important features related with scsi/sata) in "make menuconfig". If you happen to know how to enable scsi/sata features correctly, please let me know. Thanks! Below is my grub.conf related to 2.6.23 kernel. # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/sda default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.20) root (hd0,0) kernel /vmlinuz-2.6.20 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.20.img -------------- next part -------------- An HTML attachment was scrubbed... URL: From feng.xian at gmail.com Mon Nov 12 21:16:59 2007 From: feng.xian at gmail.com (Feng Xian) Date: Mon, 12 Nov 2007 15:16:59 -0600 Subject: help! My re-compiled kernel always got crashed in a machine with scsi/sata disk In-Reply-To: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> References: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> Message-ID: <610b3d450711121316w5d3c10f8l5ed4f3fb0b2541c0@mail.gmail.com> Sorry, I posted 2.6.20 parameters in grub.conf. Parameters if 2.6.23 are shown below: title Fedora (2.6.23) root (hd0,0) kernel /vmlinuz-2.6.23 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.23.img Feng On 11/12/07, Feng Xian wrote: > > Thanks for all your help. I ran into another problem. > > My 16-core machine has a scsi/sata disk. I have enabled all important > features related with scsi and sata. I built 2.6.23 kernel on this > machine. But the kernel always got crashed randomly. Sometimes it couldnot > even boot, reporting some random errors, like "segment violation, sleep for > 40 seconds", or "Group volume VolGroup00 uses lvm2 metadata: read-only", > then jump to a strange login window that I cannot log in using my root > password. > > Another thing is that Linux works perfect if I installed Fecore Core 7 on > this multi-core machine with scsi/sata disk. Why it didnt work if I used > re-compiled kernel. I guess it is because I didnt config kernel right > (although I enabled all important features related with scsi/sata) in "make > menuconfig". If you happen to know how to enable scsi/sata features > correctly, please let me know. Thanks! > > Below is my grub.conf related to 2.6.23 kernel. > > > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to this > file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 > # initrd /initrd-version.img > #boot=/dev/sda > default=1 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title Fedora (2.6.20) > root (hd0,0) > kernel /vmlinuz-2.6.20 ro root=/dev/VolGroup00/LogVol00 rhgb quiet > initrd /initrd-2.6.20.img > > -- Addr: 1025N, 23rd str, APT 33, Lincoln, NE, 68503 Phone: (402)310-9826 WWW: cse.unl.edu/~fxian -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwilson at redhat.com Mon Nov 12 21:23:01 2007 From: jwilson at redhat.com (Jarod Wilson) Date: Mon, 12 Nov 2007 16:23:01 -0500 Subject: help! My re-compiled kernel always got crashed in a machine with scsi/sata disk In-Reply-To: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> References: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> Message-ID: <4738C435.6000605@redhat.com> Feng Xian wrote: > Thanks for all your help. I ran into another problem. > > My 16-core machine has a scsi/sata disk. I have enabled all important > features related with scsi and sata. I built 2.6.23 kernel on this > machine. But the kernel always got crashed randomly. Sometimes it > couldnot even boot, reporting some random errors, like "segment > violation, sleep for 40 seconds", or "Group volume VolGroup00 uses lvm2 > metadata: read-only", then jump to a strange login window that I cannot > log in using my root password. > > Another thing is that Linux works perfect if I installed Fecore Core 7 > on this multi-core machine with scsi/sata disk. Why it didnt work if I > used re-compiled kernel. I guess it is because I didnt config kernel > right (although I enabled all important features related with scsi/sata) > in "make menuconfig". If you happen to know how to enable scsi/sata > features correctly, please let me know. Thanks! I don't think this is the correct forum for this question. This list is targeted at issues surrounding the Fedora kernel, and you're building your own kernel. Once you start building your own, with a config that obviously differs significantly from the Fedora config, we can't realistically provide support here. Furthermore, I'm not quite sure I understand why you think you need to build your own kernel either. To be bluntly honest, if you can't figure out what's going wrong there on your own, you probably shouldn't be building your own. -- Jarod Wilson jwilson at redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From feng.xian at gmail.com Mon Nov 12 21:30:45 2007 From: feng.xian at gmail.com (Feng Xian) Date: Mon, 12 Nov 2007 15:30:45 -0600 Subject: help! My re-compiled kernel always got crashed in a machine with scsi/sata disk In-Reply-To: <4738C435.6000605@redhat.com> References: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> <4738C435.6000605@redhat.com> Message-ID: <610b3d450711121330k5c9b5479he3e3e95f7555a5a6@mail.gmail.com> I downloaded a clean version of 2.6.23 and didnt do any modification on it (athough I am about to modify it in the future). By default, the clean version doesnt enable sata features, so I enabled these features and compiled this clean version. But I couldn't boot linux with the compiled kernel like I mentioned in my previous posts. On 11/12/07, Jarod Wilson wrote: > > Feng Xian wrote: > > Thanks for all your help. I ran into another problem. > > > > My 16-core machine has a scsi/sata disk. I have enabled all important > > features related with scsi and sata. I built 2.6.23 kernel on this > > machine. But the kernel always got crashed randomly. Sometimes it > > couldnot even boot, reporting some random errors, like "segment > > violation, sleep for 40 seconds", or "Group volume VolGroup00 uses lvm2 > > metadata: read-only", then jump to a strange login window that I cannot > > log in using my root password. > > > > Another thing is that Linux works perfect if I installed Fecore Core 7 > > on this multi-core machine with scsi/sata disk. Why it didnt work if I > > used re-compiled kernel. I guess it is because I didnt config kernel > > right (although I enabled all important features related with scsi/sata) > > in "make menuconfig". If you happen to know how to enable scsi/sata > > features correctly, please let me know. Thanks! > > I don't think this is the correct forum for this question. This list is > targeted at issues surrounding the Fedora kernel, and you're building > your own kernel. Once you start building your own, with a config that > obviously differs significantly from the Fedora config, we can't > realistically provide support here. > > Furthermore, I'm not quite sure I understand why you think you need to > build your own kernel either. To be bluntly honest, if you can't figure > out what's going wrong there on your own, you probably shouldn't be > building your own. > > -- > Jarod Wilson > jwilson at redhat.com > > > > -- Addr: 1025N, 23rd str, APT 33, Lincoln, NE, 68503 Phone: (402)310-9826 WWW: cse.unl.edu/~fxian -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwilson at redhat.com Mon Nov 12 21:53:05 2007 From: jwilson at redhat.com (Jarod Wilson) Date: Mon, 12 Nov 2007 16:53:05 -0500 Subject: help! My re-compiled kernel always got crashed in a machine with scsi/sata disk In-Reply-To: <610b3d450711121330k5c9b5479he3e3e95f7555a5a6@mail.gmail.com> References: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> <4738C435.6000605@redhat.com> <610b3d450711121330k5c9b5479he3e3e95f7555a5a6@mail.gmail.com> Message-ID: <4738CB41.9070103@redhat.com> Feng Xian wrote: > I downloaded a clean version of 2.6.23 and didnt do any modification on > it (athough I am about to modify it in the future). By default, the > clean version doesnt enable sata features, so I enabled these features > and compiled this clean version. But I couldn't boot linux with the > compiled kernel like I mentioned in my previous posts. Like I said, its not a Fedora kernel, and thus not something we can reasonably support here. The only possible list-relevant bit of info here would be knowing *why* you're building your own, such that we can make the Fedora kernel provide what you need so you don't have to, if possible and/or relevant. That said, seeing as how a Fedora kernel does boot your system, you'll probably get a lot closer to a bootable system with your own kernel if you start with the Fedora kernel config file instead of the upstream kernel config file, and go from there. > On 11/12/07, *Jarod Wilson* > wrote: > > Feng Xian wrote: > > Thanks for all your help. I ran into another problem. > > > > My 16-core machine has a scsi/sata disk. I have enabled all important > > features related with scsi and sata. I built 2.6.23 kernel on this > > machine. But the kernel always got crashed randomly. Sometimes it > > couldnot even boot, reporting some random errors, like "segment > > violation, sleep for 40 seconds", or "Group volume VolGroup00 uses > lvm2 > > metadata: read-only", then jump to a strange login window that I > cannot > > log in using my root password. > > > > Another thing is that Linux works perfect if I installed Fecore > Core 7 > > on this multi-core machine with scsi/sata disk. Why it didnt work if I > > used re-compiled kernel. I guess it is because I didnt config kernel > > right (although I enabled all important features related with > scsi/sata) > > in "make menuconfig". If you happen to know how to enable scsi/sata > > features correctly, please let me know. Thanks! > > I don't think this is the correct forum for this question. This list is > targeted at issues surrounding the Fedora kernel, and you're building > your own kernel. Once you start building your own, with a config that > obviously differs significantly from the Fedora config, we can't > realistically provide support here. > > Furthermore, I'm not quite sure I understand why you think you need to > build your own kernel either. To be bluntly honest, if you can't figure > out what's going wrong there on your own, you probably shouldn't be > building your own. -- Jarod Wilson jwilson at redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From Lam at Lam.pl Tue Nov 13 06:38:01 2007 From: Lam at Lam.pl (Leszek Matok) Date: Tue, 13 Nov 2007 07:38:01 +0100 Subject: help! My re-compiled kernel always got crashed in a machine with scsi/sata disk In-Reply-To: <610b3d450711121330k5c9b5479he3e3e95f7555a5a6@mail.gmail.com> References: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> <4738C435.6000605@redhat.com> <610b3d450711121330k5c9b5479he3e3e95f7555a5a6@mail.gmail.com> Message-ID: <20071113073801.5501ba17@pensja.lam.pl> Dnia 2007-11-12, o godz. 15:30:45 "Feng Xian" napisa?(a): > By default, the clean > version doesnt enable sata features, so I enabled these features and > compiled this clean version. By default, Fedora's kernel works without the need to recompile. And you've already admitted that. Use Fedora when it works and you can come back and report problems when it doesn't. If you plan on patching the kernel, Fedora provides SRPM-s with patches and known-working configs in there. This is the thing you can seek help on on this list, not the "vanilla" kernel with your own broken config. Lam -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From feng.xian at gmail.com Tue Nov 13 16:30:36 2007 From: feng.xian at gmail.com (Feng Xian) Date: Tue, 13 Nov 2007 10:30:36 -0600 Subject: help! My re-compiled kernel always got crashed in a machine with scsi/sata disk In-Reply-To: <20071113073801.5501ba17@pensja.lam.pl> References: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> <4738C435.6000605@redhat.com> <610b3d450711121330k5c9b5479he3e3e95f7555a5a6@mail.gmail.com> <20071113073801.5501ba17@pensja.lam.pl> Message-ID: <610b3d450711130830n6261c5a8mde846ec81c51993@mail.gmail.com> Thanks! Now I know what confused me. What I downloaded was linux kernel from "Linux Archive" website instead of fedora source from redhat. I used to believe that these two sources are the same. From your message, they are apparently different. I compiled fedora source again this time and it is working now! Thanks a lot! :-) On Nov 13, 2007 12:38 AM, Leszek Matok wrote: > Dnia 2007-11-12, o godz. 15:30:45 "Feng Xian" napisa?(a): > > > By default, the clean > > version doesnt enable sata features, so I enabled these features and > > compiled this clean version. > By default, Fedora's kernel works without the need to recompile. And you've > already admitted that. Use Fedora when it works and you can come back and > report problems when it doesn't. > > If you plan on patching the kernel, Fedora provides SRPM-s with patches and > known-working configs in there. This is the thing you can seek help on on this > list, not the "vanilla" kernel with your own broken config. > > Lam > > _______________________________________________ > Fedora-kernel-list mailing list > Fedora-kernel-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-kernel-list > > -- Addr: 1025N, 23rd str, APT 33, Lincoln, NE, 68503 Phone: (402)310-9826 WWW: cse.unl.edu/~fxian From jwilson at redhat.com Tue Nov 13 16:49:30 2007 From: jwilson at redhat.com (Jarod Wilson) Date: Tue, 13 Nov 2007 11:49:30 -0500 Subject: help! My re-compiled kernel always got crashed in a machine with scsi/sata disk In-Reply-To: <610b3d450711130830n6261c5a8mde846ec81c51993@mail.gmail.com> References: <610b3d450711121313q955d888peeda1cb63d570255@mail.gmail.com> <4738C435.6000605@redhat.com> <610b3d450711121330k5c9b5479he3e3e95f7555a5a6@mail.gmail.com> <20071113073801.5501ba17@pensja.lam.pl> <610b3d450711130830n6261c5a8mde846ec81c51993@mail.gmail.com> Message-ID: <4739D59A.5020503@redhat.com> Feng Xian wrote: > Thanks! Now I know what confused me. What I downloaded was linux > kernel from "Linux Archive" website instead of fedora source from > redhat. I used to believe that these two sources are the same. From > your message, they are apparently different. As far as the code itself goes, we try to stay as close to upstream as possible. We start with the upstream kernel tarball and apply some patches and our own kernel config from there. Generally, if you take an upstream tarball and just use the Fedora kernel config, you'll get a booting system (usually works for me, anyhow). -- Jarod Wilson jwilson at redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From cebbert at redhat.com Tue Nov 13 17:08:01 2007 From: cebbert at redhat.com (Chuck Ebbert) Date: Tue, 13 Nov 2007 12:08:01 -0500 Subject: Adding a pointrelease option to the spec Message-ID: <4739D9F1.80109@redhat.com> This might be useful for people building their own kernels: --- kernel.spec 12 Nov 2007 22:05:50 -0000 1.237 +++ kernel.spec 13 Nov 2007 17:05:39 -0000 @@ -12,7 +12,16 @@ # that the kernel isn't the stock distribution kernel, for example, # by setting the define to ".local" or ".bz123456" # +# You may also add a "pointrelease" with or without the "buildid" +# so that your locally built kernel gets a version number that +# is higher than the kernel it is based on and lower than the +# next offical Fedora release. +# #% define buildid .local +#% define pointrelease .1 +%if 0{?pointrelease} +%define buildid {pointrelease}{?buildid} +%endif # fedora_build defines which build revision of this kernel version we're # building. Rather than incrementing forever, as with the prior versioning From jwilson at redhat.com Tue Nov 13 17:14:47 2007 From: jwilson at redhat.com (Jarod Wilson) Date: Tue, 13 Nov 2007 12:14:47 -0500 Subject: Adding a pointrelease option to the spec In-Reply-To: <4739D9F1.80109@redhat.com> References: <4739D9F1.80109@redhat.com> Message-ID: <4739DB87.9010801@redhat.com> Chuck Ebbert wrote: > This might be useful for people building their own kernels: > > --- kernel.spec 12 Nov 2007 22:05:50 -0000 1.237 > +++ kernel.spec 13 Nov 2007 17:05:39 -0000 > @@ -12,7 +12,16 @@ > # that the kernel isn't the stock distribution kernel, for example, > # by setting the define to ".local" or ".bz123456" > # > +# You may also add a "pointrelease" with or without the "buildid" > +# so that your locally built kernel gets a version number that > +# is higher than the kernel it is based on and lower than the > +# next offical Fedora release. > +# > #% define buildid .local > +#% define pointrelease .1 > +%if 0{?pointrelease} > +%define buildid {pointrelease}{?buildid} > +%endif > > # fedora_build defines which build revision of this kernel version we're > # building. Rather than incrementing forever, as with the prior versioning I generally just use buildid for the same, i.e., I set buildid to .xyz1, .xyz2, .xyz3, etc as I rebuild a newer versions. I think its probably not worth the extra lines added to the spec file (which, by the way, in the example above, are missing a bunch of % symbols before the {. :) -- Jarod Wilson jwilson at redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From uksusansmithuk at yahoo.com Wed Nov 14 18:47:12 2007 From: uksusansmithuk at yahoo.com (Susan Smith) Date: Wed, 14 Nov 2007 21:47:12 +0300 (MSK) Subject: I WANT TO INVEST IN YOUR COUNTRY, CAN YOU ASSIST ME? Message-ID: <200711141847.lAEIlCMk019644@beta.tagtech.ru> Hello I want to invest this money in your country and i need your assistance in the investment. I want to drop you a quick note because I did not hear Back from you concerning the information I sent you The other day. Incase you did not receive the letter introducing my Intent. I am Mrs. Susan Smith from London .wife to late Mr. Clement Smith who was the former Branch chairman Of the petroleum oil company in Kuwait for nine years, Who perished in fatal accident on 18TH JULY 2004 on His way to a meeting with his secretary (MR. MARTIN GREENBERG) OF FLORIDA UNITED STATES OF AMERICA, I gotYour mail through my private search and out of Desperation I decided to reach you through this medium. My late husband deposit USD$25 million in a bank here in London and I want to invest the money in your country, Before the death of my late husband he told me that I Have to invest this money out of London that he don't Want any body from his office or our country to know About this money, that is why I contacted you so that You will help me to transfer this money out from The bank to your country for investment as I told you. I want you to receive this fund on my behalf in your Country so that we can invest it for a good business And invest on a profitable business venture on agreed If you are interested, please reply via my email address. Upon your Response, I shall then provide you with more details, and further Explanations that will help you understand the transaction. No doubt This proposal will make you apprehensive, please I implore you to Observe utmost confidentiality and rest assured that this transaction Would be most profitable for both of us because I will require your Assistance to invest my share in your country. I await your swift response and hope that you will accept my Proposal, as time is of equal essence in this project as well as is Confidentiality Regards Mrs. Susan Smith From roland at redhat.com Wed Nov 14 21:20:13 2007 From: roland at redhat.com (Roland McGrath) Date: Wed, 14 Nov 2007 13:20:13 -0800 (PST) Subject: sparse 0.4.1 Message-ID: <20071114212013.D874326F8B6@magilla.localdomain> Dave asked me to ping when sparse got updated. 0.4.1 is built, [78] updates should get pushed RSN. This presumably works with the kernel source again. From davej at redhat.com Wed Nov 14 21:44:34 2007 From: davej at redhat.com (Dave Jones) Date: Wed, 14 Nov 2007 16:44:34 -0500 Subject: sparse 0.4.1 In-Reply-To: <20071114212013.D874326F8B6@magilla.localdomain> References: <20071114212013.D874326F8B6@magilla.localdomain> Message-ID: <20071114214434.GE5718@redhat.com> On Wed, Nov 14, 2007 at 01:20:13PM -0800, Roland McGrath wrote: > Dave asked me to ping when sparse got updated. 0.4.1 is built, [78] updates > should get pushed RSN. This presumably works with the kernel source again. Cool, I'll reeanble it. I can't do rawhide builds right now due to breakage in curl preventing 'make upload' from working. Dave -- http://www.codemonkey.org.uk From xjfu at comcast.net Wed Nov 14 23:19:18 2007 From: xjfu at comcast.net (Cary Fu) Date: Wed, 14 Nov 2007 15:19:18 -0800 Subject: How can I develop loadable module for Fedora 7 and later? Message-ID: <001c01c82714$c9d27020$677ba8c0@SuperVisual> When I tried to build a loadable module for Fedora 7, there are lots of error warning came up regarding the line of #include . Is there anyone knows where can I find the information about making a loadable module for Fedora 7. Thanks in advance for any input. Cary Fu -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwilson at redhat.com Wed Nov 14 23:22:02 2007 From: jwilson at redhat.com (Jarod Wilson) Date: Wed, 14 Nov 2007 18:22:02 -0500 Subject: How can I develop loadable module for Fedora 7 and later? In-Reply-To: <001c01c82714$c9d27020$677ba8c0@SuperVisual> References: <001c01c82714$c9d27020$677ba8c0@SuperVisual> Message-ID: <473B831A.3060707@redhat.com> Cary Fu wrote: > When I tried to build a loadable module for Fedora 7, there are lots of > error warning came up regarding the line of #include . > Is there anyone knows where can I find the information about making a > loadable module for Fedora 7. Thanks in advance for any input. Just take a look at the source to any of the umpteen modules in the kernel... May also want to visit http://kernelnewbies.org/. -- Jarod Wilson jwilson at redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From davej at redhat.com Thu Nov 15 19:53:45 2007 From: davej at redhat.com (Dave Jones) Date: Thu, 15 Nov 2007 14:53:45 -0500 Subject: vanilla/ changes in devel. Message-ID: <20071115195345.GA18707@redhat.com> I just checked something into devel/ that changes how we 'make prep'. Before, under kernel-2.6.23/ we had a vanilla dir and a fedora-patched dir called linux-2.6.23.noarch The vanilla dir used to be just the unpacked tarball. With the change I just checked in, that dir is now patched up to the latest upstream (ie, 2.6.24rc2-git5 right now). This speeds up subsequent make preps quite a bit as the -rc's increase in size. The downside (and reason for this heads up) is that anyone with an existing checkout will find that make prep will now fail to apply patches as the specfile expects vanilla in the new form. rm -rf kernel-2.6.23 and make prep again, and it'll all just work out. Dave -- http://www.codemonkey.org.uk From gilboad at gmail.com Fri Nov 16 02:17:32 2007 From: gilboad at gmail.com (Gilboa Davara) Date: Fri, 16 Nov 2007 04:17:32 +0200 Subject: How to change the number of processors in a 16-core machine In-Reply-To: <20071112150004.GD16995@ti88.telemetry-investments.com> References: <610b3d450711112330n16013119wce42fbb46ab67e28@mail.gmail.com> <20071112145249.GA21189@ti88.telemetry-investments.com> <20071112150004.GD16995@ti88.telemetry-investments.com> Message-ID: <1195179452.11129.1.camel@gilboa-home-dev.localdomain> On Mon, 2007-11-12 at 10:00 -0500, Bill Rugolsky Jr. wrote: > On Mon, Nov 12, 2007 at 09:52:49AM -0500, Bill Rugolsky Jr. wrote: > > With CPU hotplug, you don't even have to reboot. > > One additional note: Since the Opteron boxes are NUMA, the memory topology > (and any differences from the online CPU topology) may also affect your > performance benchmark results. > > -Bill OT question: If he off-lines a certain CPU - doesn't he also disables all the HT links that belong to this CPU? (Along with their DRAM banks and I/O links?) - Gilboa From SteveD at redhat.com Fri Nov 16 14:00:19 2007 From: SteveD at redhat.com (Steve Dickson) Date: Fri, 16 Nov 2007 09:00:19 -0500 Subject: Install hang on a Dell PowerEdge SC1430 Message-ID: <473DA273.7010309@RedHat.com> Are there known issues with F8 (and F7) being installed on PowerEdges? Booting from DVD (and CDs) I get the following three lines than nothing... Loading Vmlinuz........ Loading initrd.img..... Read. This happens with both x86 and x86_64 installs from DVD of either F8 or F7. I also tried burning the boot.iso from the DVD to a CD and boot from that with the same results. Being this is pretty broken, I'm hoping this is a known problem and there is some type of workaround. tia, steved. From mauricio at projetofedora.org Fri Nov 16 17:31:24 2007 From: mauricio at projetofedora.org (Mauricio Pretto) Date: Fri, 16 Nov 2007 15:31:24 -0200 Subject: Install hang on a Dell PowerEdge SC1430 In-Reply-To: <473DA273.7010309@RedHat.com> References: <473DA273.7010309@RedHat.com> Message-ID: <473DD3EC.2070008@projetofedora.org> Try acpi=off Regards Pretto http://fedoraproject.org/wiki/MauricioPretto Steve Dickson wrote: > Are there known issues with F8 (and F7) being > installed on PowerEdges? Booting from DVD (and CDs) > I get the following three lines than nothing... > > Loading Vmlinuz........ > Loading initrd.img..... > Read. > > This happens with both x86 and x86_64 installs > from DVD of either F8 or F7. I also tried burning > the boot.iso from the DVD to a CD and boot from > that with the same results. > > Being this is pretty broken, I'm hoping this is a known > problem and there is some type of workaround. > > tia, > > steved. > > > _______________________________________________ > Fedora-kernel-list mailing list > Fedora-kernel-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-kernel-list From mauricio at projetofedora.org Fri Nov 16 17:34:06 2007 From: mauricio at projetofedora.org (Mauricio Pretto) Date: Fri, 16 Nov 2007 15:34:06 -0200 Subject: Install hang on a Dell PowerEdge SC1430 In-Reply-To: <473DD3EC.2070008@projetofedora.org> References: <473DA273.7010309@RedHat.com> <473DD3EC.2070008@projetofedora.org> Message-ID: <473DD48E.7020007@projetofedora.org> https://fedoraproject.org/wiki/KernelCommonProblems Pretto http://fedoraproject.org/wiki/MauricioPretto Mauricio Pretto wrote: > Try acpi=off > Regards > Pretto > http://fedoraproject.org/wiki/MauricioPretto > > > > Steve Dickson wrote: >> Are there known issues with F8 (and F7) being >> installed on PowerEdges? Booting from DVD (and CDs) >> I get the following three lines than nothing... >> >> Loading Vmlinuz........ >> Loading initrd.img..... >> Read. >> >> This happens with both x86 and x86_64 installs >> from DVD of either F8 or F7. I also tried burning >> the boot.iso from the DVD to a CD and boot from >> that with the same results. >> >> Being this is pretty broken, I'm hoping this is a known >> problem and there is some type of workaround. >> >> tia, >> >> steved. >> >> >> _______________________________________________ >> Fedora-kernel-list mailing list >> Fedora-kernel-list at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-kernel-list > > _______________________________________________ > Fedora-kernel-list mailing list > Fedora-kernel-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-kernel-list From davej at redhat.com Fri Nov 16 19:02:16 2007 From: davej at redhat.com (Dave Jones) Date: Fri, 16 Nov 2007 14:02:16 -0500 Subject: vanilla/ changes in devel. In-Reply-To: <20071115195345.GA18707@redhat.com> References: <20071115195345.GA18707@redhat.com> Message-ID: <20071116190216.GD32293@redhat.com> On Thu, Nov 15, 2007 at 02:53:45PM -0500, Dave Jones wrote: > I just checked something into devel/ that changes how we 'make prep'. > Before, under kernel-2.6.23/ we had a vanilla dir and a fedora-patched > dir called linux-2.6.23.noarch > The vanilla dir used to be just the unpacked tarball. > With the change I just checked in, that dir is now patched up > to the latest upstream (ie, 2.6.24rc2-git5 right now). > > This speeds up subsequent make preps quite a bit as the -rc's increase > in size. The downside (and reason for this heads up) is that anyone > with an existing checkout will find that make prep will now fail > to apply patches as the specfile expects vanilla in the new form. > > rm -rf kernel-2.6.23 and make prep again, and it'll all just work out. I tweaked this some more. I found that I'd have had to have done that rm -rf every day when I rebased, which is less than fun. So now the 'vanilla' dir has the version postfixed to it. The downside is that this means that the kernel-2.6.23/ dir will get a bit cluttered over time with lots of symlink'd trees in your local checkouts, but it will dtrt. There's room for a further optimisation which I'm too lazy to do right now, and that's to have a separate vanilla-$ver dir for both the -rc and the -git if present. This way rebasing to a new -git will use the previous vanilla-rc tree if present instead of regenerating it from scratch. the %prep is also getting a bit messy with all of this hackery, so I'll probably end up cleaning it all up when I get around to doing that optimisation. Seems to work right now though. Dave -- http://www.codemonkey.org.uk From cebbert at redhat.com Fri Nov 16 20:50:45 2007 From: cebbert at redhat.com (Chuck Ebbert) Date: Fri, 16 Nov 2007 15:50:45 -0500 Subject: Install hang on a Dell PowerEdge SC1430 In-Reply-To: <473DA273.7010309@RedHat.com> References: <473DA273.7010309@RedHat.com> Message-ID: <473E02A5.6030905@redhat.com> On 11/16/2007 09:00 AM, Steve Dickson wrote: > Are there known issues with F8 (and F7) being > installed on PowerEdges? Booting from DVD (and CDs) > I get the following three lines than nothing... > > Loading Vmlinuz........ > Loading initrd.img..... > Read. > > This happens with both x86 and x86_64 installs > from DVD of either F8 or F7. I also tried burning > the boot.iso from the DVD to a CD and boot from > that with the same results. > > Being this is pretty broken, I'm hoping this is a known > problem and there is some type of workaround. > edd=skipmbr ?? If that fixes it, visit https://bugzilla.redhat.com/show_bug.cgi?id=379411 and add your report. (This bug was supposedly fixed before release but still seems to be present, just a lot less common than before.) From samfw at redhat.com Sun Nov 18 11:33:21 2007 From: samfw at redhat.com (Sam Folk-Williams) Date: Sun, 18 Nov 2007 06:33:21 -0500 Subject: Review requested: Custom Kernel Doc updated Message-ID: <47402301.4040608@redhat.com> Hi, I have updated http://fedoraproject.org/wiki/Docs/CustomKernel for F8. Would appreciate a technical review. The section on building only modules has not been updated - if anyone has any comments on that, much appreciated. Any suggestions welcome. Thanks, Sam From cebbert at redhat.com Mon Nov 19 17:58:55 2007 From: cebbert at redhat.com (Chuck Ebbert) Date: Mon, 19 Nov 2007 12:58:55 -0500 Subject: ALSA versions in the Fedora kernel Message-ID: <4741CEDF.2070809@redhat.com> Here's a proposal for what version of ALSA we deliver with our kernel: Fedora 7 will stay with the version it has, 1.0.14, which is being maintained with stable patches by the ALSA team. Fedora 8 will stay with 1.0.15 and only merge carefully selected bug fixes from upstream ALSA. Fedora 9 / devel will track upstream ALSA development so we can shake out bugs as soon as possible. This can be done by carrying the git-alsa-mm patch from the -mm kernel. From davej at redhat.com Mon Nov 19 18:36:15 2007 From: davej at redhat.com (Dave Jones) Date: Mon, 19 Nov 2007 13:36:15 -0500 Subject: ALSA versions in the Fedora kernel In-Reply-To: <4741CEDF.2070809@redhat.com> References: <4741CEDF.2070809@redhat.com> Message-ID: <20071119183615.GA6670@redhat.com> On Mon, Nov 19, 2007 at 12:58:55PM -0500, Chuck Ebbert wrote: > Here's a proposal for what version of ALSA we deliver with our kernel: > > Fedora 7 will stay with the version it has, 1.0.14, which is being > maintained with stable patches by the ALSA team. > > Fedora 8 will stay with 1.0.15 and only merge carefully selected bug fixes > from upstream ALSA. > > Fedora 9 / devel will track upstream ALSA development so we can shake out > bugs as soon as possible. This can be done by carrying the git-alsa-mm > patch from the -mm kernel. Sounds good to me. Dave -- http://www.codemonkey.org.uk From jwilson at redhat.com Mon Nov 19 19:01:31 2007 From: jwilson at redhat.com (Jarod Wilson) Date: Mon, 19 Nov 2007 14:01:31 -0500 Subject: ALSA versions in the Fedora kernel In-Reply-To: <20071119183615.GA6670@redhat.com> References: <4741CEDF.2070809@redhat.com> <20071119183615.GA6670@redhat.com> Message-ID: <4741DD8B.1070201@redhat.com> Dave Jones wrote: > On Mon, Nov 19, 2007 at 12:58:55PM -0500, Chuck Ebbert wrote: > > Here's a proposal for what version of ALSA we deliver with our kernel: > > > > Fedora 7 will stay with the version it has, 1.0.14, which is being > > maintained with stable patches by the ALSA team. > > > > Fedora 8 will stay with 1.0.15 and only merge carefully selected bug fixes > > from upstream ALSA. > > > > Fedora 9 / devel will track upstream ALSA development so we can shake out > > bugs as soon as possible. This can be done by carrying the git-alsa-mm > > patch from the -mm kernel. > > Sounds good to me. Likewise. -- Jarod Wilson jwilson at redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From gilboad at gmail.com Tue Nov 20 08:38:11 2007 From: gilboad at gmail.com (Gilboa Davara) Date: Tue, 20 Nov 2007 10:38:11 +0200 Subject: Review requested: Custom Kernel Doc updated In-Reply-To: <47402301.4040608@redhat.com> References: <47402301.4040608@redhat.com> Message-ID: <1195547891.17404.6.camel@gilboa-work-dev.localdomain> On Sun, 2007-11-18 at 06:33 -0500, Sam Folk-Williams wrote: > Hi, > > I have updated http://fedoraproject.org/wiki/Docs/CustomKernel for F8. > Would appreciate a technical review. > > The section on building only modules has not been updated - if anyone > has any comments on that, much appreciated. > > Any suggestions welcome. > > Thanks, > Sam I'd add something about jobs. (.rpmmacros/%_smp_mflags). While not strictly kernel related, it could prove useful for most kernel-building users. - Gilboa From drindt at mx-solutions.de Fri Nov 23 20:01:32 2007 From: drindt at mx-solutions.de (Daniel Rindt) Date: Fri, 23 Nov 2007 21:01:32 +0100 Subject: Kernel seems to crash in a xen environment and using crossover-office Message-ID: <1195848092.2618.10.camel@nxserver.mx-solutions.de> Hello Listmembers, iam running Fedora 8 into a Xen Environment. My Kernel on the domU is 2.6.21-2950.fc8xen. This domU has 1024M of Ram assigned. When iam starting the Crossover Installer Wizard and choose Install Internet Explorer 6 SP1 then the Kernel seems to crash. With the virt-manager i had taken a Screenshot from the console, he is attached. If iam lowering the Memory to 512M the Crash comes later in the Setup or using. Additionally i found these messages too: === 8< === 4gb seg fixup, process exe (pid 2457), cs:ip 73:0804d5a1 4gb seg fixup, process exe (pid 2457), cs:ip 73:0804d5a1 4gb seg fixup, process exe (pid 2457), cs:ip 73:00aea736 4gb seg fixup, process exe (pid 2457), cs:ip 73:0804d596 4gb seg fixup, process exe (pid 2457), cs:ip 73:00aebcb0 4gb seg fixup, process exe (pid 2457), cs:ip 73:0804d5a1 4gb seg fixup, process exe (pid 2457), cs:ip 73:00aea736 4gb seg fixup, process exe (pid 2457), cs:ip 73:0804d5a1 4gb seg fixup, process exe (pid 2457), cs:ip 73:00c153e7 4gb seg fixup, process exe (pid 2457), cs:ip 73:0804d596 printk: 171 messages suppressed. === 8< === If iam using some Windows Software with Crossover then i found after 2-4 minutes the following in my dmesg: === 8< === 4gb seg fixup, process wine-pthread (pid 2857), cs:ip 73:741dfb5a printk: 164944 messages suppressed. === 8< === the problem can definitly influenced through the memory dimensioning. I dont know why the machine knows that he had 4G of memory at all. In hope for answer and suggestions how to avoid/ solve that - many thanks in advance. Thanks for reading this mail. -Daniel P.S.: i had do a xm dump-core, its bzipped now so i can provide it if someone request it for analyzing. -------------- next part -------------- A non-text attachment was scrubbed... Name: xendomain-crash-cxoffice-ie6.png Type: image/png Size: 23367 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From davej at redhat.com Mon Nov 26 17:52:43 2007 From: davej at redhat.com (Dave Jones) Date: Mon, 26 Nov 2007 12:52:43 -0500 Subject: rpms/kernel/devel kernel.spec,1.251,1.252 config-generic,1.42,1.43 In-Reply-To: <200711261237.lAQCbY4m011230@cvs-int.fedora.redhat.com> References: <200711261237.lAQCbY4m011230@cvs-int.fedora.redhat.com> Message-ID: <20071126175243.GA22632@redhat.com> On Mon, Nov 26, 2007 at 07:37:34AM -0500, David Woodhouse wrote: > -# CONFIG_LIBERTAS is not set > - > +CONFIG_LIBERTAS=m > +CONFIG_LIBERTAS_USB=m > +CONFIG_LIBERTAS_CS=m > +CONFIG_LIBERTAS_SDIO=m > +CONFIG_LIBERTAS_DEBUG=y This is probably better placed in a per-arch override rather than building it everywhere no? Dave -- http://www.codemonkey.org.uk From dwmw2 at infradead.org Mon Nov 26 18:01:14 2007 From: dwmw2 at infradead.org (David Woodhouse) Date: Mon, 26 Nov 2007 18:01:14 +0000 Subject: rpms/kernel/devel kernel.spec,1.251,1.252 config-generic,1.42,1.43 In-Reply-To: <20071126175243.GA22632@redhat.com> References: <200711261237.lAQCbY4m011230@cvs-int.fedora.redhat.com> <20071126175243.GA22632@redhat.com> Message-ID: <1196100074.3166.75.camel@pmac.infradead.org> On Mon, 2007-11-26 at 12:52 -0500, Dave Jones wrote: > On Mon, Nov 26, 2007 at 07:37:34AM -0500, David Woodhouse wrote: > > > -# CONFIG_LIBERTAS is not set > > - > > +CONFIG_LIBERTAS=m > > +CONFIG_LIBERTAS_USB=m > > +CONFIG_LIBERTAS_CS=m > > +CONFIG_LIBERTAS_SDIO=m > > +CONFIG_LIBERTAS_DEBUG=y > > This is probably better placed in a per-arch override rather > than building it everywhere no? Why? What arches would you exclude it on? (please don't use tinfoil-hat address) -- dwmw2 From davej at redhat.com Mon Nov 26 18:03:11 2007 From: davej at redhat.com (Dave Jones) Date: Mon, 26 Nov 2007 13:03:11 -0500 Subject: rpms/kernel/devel kernel.spec,1.251,1.252 config-generic,1.42,1.43 In-Reply-To: <20071126175243.GA22632@redhat.com> References: <200711261237.lAQCbY4m011230@cvs-int.fedora.redhat.com> <20071126175243.GA22632@redhat.com> Message-ID: <20071126180311.GB22632@redhat.com> On Mon, Nov 26, 2007 at 12:52:43PM -0500, Dave Jones wrote: > On Mon, Nov 26, 2007 at 07:37:34AM -0500, David Woodhouse wrote: > > > -# CONFIG_LIBERTAS is not set > > - > > +CONFIG_LIBERTAS=m > > +CONFIG_LIBERTAS_USB=m > > +CONFIG_LIBERTAS_CS=m > > +CONFIG_LIBERTAS_SDIO=m > > +CONFIG_LIBERTAS_DEBUG=y > > This is probably better placed in a per-arch override rather > than building it everywhere no? That's my point, do we /want/ to build it everywhere? Is it likely to show up on ia64, sparc64, ppc64 etc etc? Dave -- http://www.codemonkey.org.uk From zaitcev at redhat.com Wed Nov 28 08:29:28 2007 From: zaitcev at redhat.com (Pete Zaitcev) Date: Wed, 28 Nov 2007 00:29:28 -0800 Subject: i686 build on x86_64 fails Message-ID: <20071128002928.8df049c7.zaitcev@redhat.com> Just FYI, I found that it's not possible to build an i686 kernel on x86_64 (in 2.6.23.1-42.fc8), because this happens: + gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=generic -fasynchronous-unwind-tables -o scripts/modsign/mod-extract scripts/modsign/mod-extract.c In file included from /usr/include/features.h:359, from /usr/include/stdio.h:28, from scripts/modsign/mod-extract.c:12: /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory It's not important why stubs-32.h does not exist in glibc-headers. The problem is using -m32 for a host executable, because the kernel.spec has this: gcc $RPM_OPT_FLAGS -o scripts/modsign/mod-extract scripts/modsign/mod-extract.c I suspect that hardcoding gcc -O would work just dandily, but on the other hand it's unclear if we want to bother fixing it. Thoughts? -- Pete From davej at redhat.com Wed Nov 28 18:31:37 2007 From: davej at redhat.com (Dave Jones) Date: Wed, 28 Nov 2007 13:31:37 -0500 Subject: i686 build on x86_64 fails In-Reply-To: <20071128002928.8df049c7.zaitcev@redhat.com> References: <20071128002928.8df049c7.zaitcev@redhat.com> Message-ID: <20071128183137.GA18686@redhat.com> On Wed, Nov 28, 2007 at 12:29:28AM -0800, Pete Zaitcev wrote: > Just FYI, I found that it's not possible to build an i686 kernel on x86_64 > (in 2.6.23.1-42.fc8), because this happens: > > + gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=generic -fasynchronous-unwind-tables -o scripts/modsign/mod-extract scripts/modsign/mod-extract.c > In file included from /usr/include/features.h:359, > from /usr/include/stdio.h:28, > from scripts/modsign/mod-extract.c:12: > /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory > > It's not important why stubs-32.h does not exist in glibc-headers. > The problem is using -m32 for a host executable, because the kernel.spec > has this: > > gcc $RPM_OPT_FLAGS -o scripts/modsign/mod-extract scripts/modsign/mod-extract.c > > I suspect that hardcoding gcc -O would work just dandily, but on the other > hand it's unclear if we want to bother fixing it. Thoughts? Just nuke the line completely, and turn off module signing. (It's already gone in devel/) Dave -- http://www.codemonkey.org.uk From cebbert at redhat.com Wed Nov 28 20:19:26 2007 From: cebbert at redhat.com (Chuck Ebbert) Date: Wed, 28 Nov 2007 15:19:26 -0500 Subject: i686 build on x86_64 fails In-Reply-To: <20071128002928.8df049c7.zaitcev@redhat.com> References: <20071128002928.8df049c7.zaitcev@redhat.com> Message-ID: <474DCD4E.8070902@redhat.com> On 11/28/2007 03:29 AM, Pete Zaitcev wrote: > It's not important why stubs-32.h does not exist in glibc-headers. stubs-32.h is in glibc-devel on Fedora 6 and was apparently removed sometime after that. From cebbert at redhat.com Thu Nov 29 23:17:41 2007 From: cebbert at redhat.com (Chuck Ebbert) Date: Thu, 29 Nov 2007 18:17:41 -0500 Subject: Automating build of stable kernel release candidates Message-ID: <474F4895.6030703@redhat.com> There are some manual hacks in the kernel specfile now for building stable release candidates. However, kernel 2.6.23.9-rc1 ends up being released as 2.6.23.8-NN because we don't have a good way to change the version. This update automates that; the only question is whether we should label the built kernel as an -rc. I didn't add that part, and the changes are untested: --- kernel.spec 29 Nov 2007 00:25:06 -0000 1.279 +++ kernel.spec 29 Nov 2007 22:45:41 -0000 @@ -34,6 +34,15 @@ %if 0%{?released_kernel} # Do we have a 2.6.21.y update to apply? %define stable_update 9 +# Do we have a stable RC update to apply? +%define stable_rc 0 +# Stable rc patches are incremental against the previous -stable +# If this is an rc we need the previous stable patch too +%if 0%{?stable_rc} +%define stable_base %(expr %{stable_update} - 1) +%else +%define stable_base %{stable_update} +%endif # Set rpm version accordingly %if 0%{?stable_update} %define stablerev .%{stable_update} @@ -534,8 +543,12 @@ # Here should be only the patches up to the upstream canonical Linus tree. # For a stable release kernel -%if 0%{?stable_update} -Patch00: patch-2.6.%{base_sublevel}.%{stable_update}.bz2 +%if 0%{?stable_base} +Patch00: patch-2.6.%{base_sublevel}.%{stable_base}.bz2 +%endif +%if 0%{?stable_rc} +Patch01: patch-2.6.%{base_sublevel}.%{stable_update}-rc%{stable_rc}.bz2 +%endif # non-released_kernel case # These are automagically defined by the rcrev and gitrev values set up @@ -1006,8 +1019,12 @@ # Update to latest upstream. # released_kernel with stable_update available case -%if 0%{?stable_update} -ApplyPatch patch-2.6.%{base_sublevel}.%{stable_update}.bz2 +%if 0%{?stable_base} +ApplyPatch patch-2.6.%{base_sublevel}.%{stable_base}.bz2 +%endif +%if 0%{?stable_rc} +ApplyPatch patch-2.6.%{base_sublevel}.%{stable_update}-rc%{stable_rc}.bz2 +%endif # non-released_kernel case %else