Hi Allan, Le lundi 30 juillet 2007 10:30, vous avez écrit : > Hi Geoffrey, > It is totally unpredicatble that a BIOS setting on a mobo for video > from 8MB to 1MB would cause a kernel panic on reboot yet install perfectly. > I had a tough time debugging it and i did it systematically through a > process of elimination. Since it was not the sata 2 it could have been > the video on board but not neccessarily so as > a kernel panic usually caused by a unrecognized hard drive( So i think > ..) So i took the long shot of actually installing a pci express video > card and trying and then tackling the bios: > remember the number of binary possibilities to try for bios settings of > 7 binaray vars is 2^7=128 possibilities. > I also set the p5b-vm with on board video with 1mb video and no problems. > I still do not know whether it is a buggy bios or a ich9 chipset problem > or oscar problem.
It is _not_ an OSCAR problem. As i said your problem is typical and i do not agree with your analysis based on which you say you have 128 possibilities. Of course this is theoretically correct but my experience shows that this kind of problem happens periodically and if often caused by buggy BIOS (note that since the beginning i tell you to check your bios). Also note that your kernel panic was a crash of the i915 driver after registration of the AGP driver so it is not a surprise to see that that BIOS associated to the video card is responsible of the crash. This is purely an hardware issue and OSCAR cannot provide any suitable solution to address that at least because i do not know a systematic way to address this issue. > I installed fc7 from dvd with 1mb video memory in text mode ( as X would > not work with such little memory or annaconda did not recognize the > graphics card Intel) > and it reboot to a command prompt without problems - no kernel panic on > the same p5k-vm mobo but if i changed the videon mem to 8mb then X > worked and everything worked in gui and it installed and rebooted into > graphics mode. Again that happens. It depends on the combination hardware/BIOS/driver. It is the same kind of issue when you can use a specific hardware with a specific OS and with another. > This documentation is for future users of Oscar with any mobo - expect > the unexpected and Murphy's Laws of Computing! I agree that you can put a note somewhere but OSCAR does not aim at logging all the weird hardware behavior. And again according to me this is not the unexpected, this is a typical issue when you install new clusters. I have periodically the issue (about 2-3% of the time). Regards, > Cheers, > Allan Menezes > > Geoffroy Vallée wrote: > >Allan, > > > >It is not a surprise. The description of your problem was a typical BIOS > >issue, most of time from the motherboard and in your case from the video > >card. That's why since OSCAR developers asked you to check your bios > >first. :-) This kind of issue is always difficult to figure out and > >unfortunately we cannot do much to improve the situation. Remember that > > you should be able to update the BIOS of the video cards, which may fix > > your problem. > > > >Enjoy your new cluster! > > > >Le dimanche 29 juillet 2007 20:23, vous avez écrit : > >>Hi, > >> Sorry about the confusion but the bios settings of the video card are > >>causing kernel panic: > >>i now set it to Memory remap feature disabled > >>Initiate Graphics adapter [peg/pci] > >>Internal Graphics mode Select [Enabled , 8MB] > >>Caution on above : setting to 1 MB causes kernel panic on compute nodes. > >>Strange! > >>PEG Port Control [Auto] > >> Peg port Force x1 [Disabled] > >> > >> >Video Function Configuration > >> > >>DVMT Mode Select [Fixed Mode] > >>DVMT/FIXED M<emory 128MB > >>ASMT Resolution disabled > >>and it works so it must be a bios bug! > >>the p5b-vm bioses are okay this p5k-vm bios is 0401 > >>Cheers, > >>Allan Menezes > >> > >>Geoffroy VALLEE wrote: > >>>Hi Allan, > >>> > >>>It is still a problem with your i915 driver, last time i asked you to > >>>check the bios and so on but you did not reply. Therefore, i cannot help > >>>you more... maybe others can. > >>> > >>>Anyway, a couple of questions to try to understand you problem: > >>>- you said all the nodes are the same, right? > >>>- do you have this problem with all the compute nodes (it may be a > >>>hardware problem on a single compute node)? > >>>- do you try to take the "default" bios options and not the "optimal" > >>> one? - what is the PCI device 0xcd/0x134? > >>>- did you try to disable ACPI? > >>> > >>>Regards, > >>> > >>>On Saturday 28 July 2007 21:02, Allan Menezes wrote: > >>>>Hi All, > >>>> i am still having problems with the p5k-vm mobo. The fc7 kernel is the > >>>>latest now at 2.6.22.1-33.fc7. > >>>>I put an external Adaptec Sata2 pci expansion card on the pci bus and > >>>>installed the clent image but i still get get a kernel panic with the > >>>>same error meassages below. > >>>>Please help. I think it's the new chipset (g33 and ich9). Iif only some > >>>>body could ask Intel about this new mobo. IT is a good mobo for cluster > >>>>building costs $130.00 cdn and has DDR3 and FSB1333 support. > >>>>Quad core support too and Quad core Q6600 cpus have come down to > >>>> $266.00 US! Regards, > >>>>Allan > >>>> > >>>>Hi Bernard, Geoffrey, > >>>>I cannot take ascreen capture after the kernel panic message because > >>>>the system hangs. > >>>>Yes the head node has the identical hardware as two other client nodes > >>>>that kernel panic. > >>>>I tried copying the modprobe.conf from the head node to the client > >>>> image in ../oscarimage//etc. > >>>>but i still got a kernel panic. > >>>>Since I cannot get a screen capture I am copying this down from the > >>>>screen: Call Trace: > >>>>agp_add_bridge+0x1c4/0x2dc > >>>>pci_device_probe+0xcd/0x134 > >>>>driver_probe_device+0xff/0x17c > >>>>__driver_attach+0x90/0xcc > >>>>__driver_attach+0x0/0xcc > >>>>__driver_attach+0x0/0xcc > >>>>bus_for_each_dev+0x43/0x6e > >>>>bus_add_driver+0x7b/0x19d > >>>>__pci_register_driver+0x58/0x8a > >>>>kernel_init+0x206/0x370 > >>>>child_rip+0xa/0x12 > >>>>acpi_ds_init_one_object+0x0/0x7c > >>>>kernel_init+0x0/0x370 > >>>>child_rip+0x0/0x12 > >>>>Code: 89 10 48 89 c8 48 03 05 39 af 37 00 48 83 c1 04 8b 00 3b 73 > >>>>RIP [<ffffffff8117b60b>] intel_i915_configure+0xf3/0x115 > >>>> RSP <ffff8100bf977d60> > >>>>CR2: ffffc2000147fffc > >>>>Kernel panic - not syncing: Attempted to kill init! > >>>> > >>>>and then it hangs .. > >>>>the kernel of fc7 oscar installs in oscarimage is 2.6.22.27-fc7 > >>>>Thank you and your help would be appreciated! > >>>>'Regards, > >>>>Allan > >>>> > >>>>Bernard Li wrote: > >>>>>Hi Allan: > >>>>> > >>>>>Please take a screen capture of the screen when you get the "kernel > >>>>>panic" message -- we need additional information from the screen (like > >>>>>the messages which came before that message) to troubleshoot this > >>>>>issue further. > >>>>> > >>>>>Does your headnode have the same hardware as the client nodes you are > >>>>>having issues with? Copying modprobe.conf to the image only works if > >>>>>they are of the same hardware -- in your case you need to get a > >>>>>working modprobe.conf for the _clients_ and then copy it to the image, > >>>>>but of course this may not work with other hardware, so maybe you need > >>>>>to create a separate image or somehow make the modprobe.conf work for > >>>>>all your hardware. > >>>>> > >>>>>Regards, > >>>>> > >>>>>Bernard > >>>>> > >>>>>On 7/24/07, Geoffroy Vallée <[EMAIL PROTECTED]> wrote: > >>>>>>Hi Allan, > >>>>>> > >>>>>>If you have the message "kernel panic - not syncing: Attempted to > >>>>>> kill init." you most certainly have other usefull logs just before. > >>>>>> And without these logs it is almost impossible to help you. > >>>>>> > >>>>>>Therefore as i said in my previous email, we need at least the logs > >>>>>>before the kernel panic. Without these logs it is impossible to know > >>>>>>what causes the panic. > >>>>>> > >>>>>>Regards, > >>>>>> > >>>>>>Le lundi 23 juillet 2007 22:58, Allan Menezes a écrit: > >>>>>>>Geoffroy Vallée wrote: > >>>>>>>>Allan, > >>>>>>>> > >>>>>>>>Can you the full log before the kernel panic? Without these > >>>>>>>> messages is kind of difficult to know what is the problem. > >>>>>>>> > >>>>>>>>Thanks, > >>>>>>>> > >>>>>>>>Le lundi 23 juillet 2007 21:02, Allan Menezes a écrit : > >>>>>>>>>Can anybody help me with the p5k-vm mobo which is just out problem > >>>>>>>>>of instralling an image (client) and giving a kernel panic on > >>>>>>>>>reboot, PLease? > >>>>>>> > >>>>>>>Hi Geoffrey, > >>>>>>> Oscar installs and works with fc7 on a head node of p5k-vm but > >>>>>>>client p5k-vm install the client image perfectly > >>>>>>>but it is on reboot to set up the network with the installed > >>>>>>>oscarimage that i get : > >>>>>>>kernel panic - not syncing: Attempted to kill init. > >>>>>>>So the log file will be perfect. It will not show aproblem.There is > >>>>>>>none with installation. the oscarimage grabs the latest kernel for > >>>>>>>fc7 which is 2.6.22.27-fc7 > >>>>>>>and install it into oscarimage. > >>>>>>>I can install fc7 with a fc7 dvd on these mobos without any problems > >>>>>>>with the latest kernel. It's just on client install that i get the > >>>>>>>above error on reboot! > >>>>>>>the p5b-vm is an intel g33 ich9 chipset mobo. The p5b-vm which are > >>>>>>>intel 965 ich8 work fine on reboot! > >>>>>>>The intel website does not show support for linux for their g33 > >>>>>>> mobos on their website. > >>>>>>>I can howevever install fc7 with the stock kernel on the p5k-vm mobo > >>>>>>>perfectly as a head node with dvd (fc7) > >>>>>>>however. They just don't like to be oscar clients. > >>>>>>>Do not know what the problem is. > >>>>>>>BUt I can get the mobo to not reboot and go to the busy box screen > >>>>>>> and maybe trouble shoot the installed image before rebooting? > >>>>>>>Can you give me some help on that ,please? It's seems its the only > >>>>>>>likely way to get it working as a client right now. > >>>>>>>Thank you very much for your response, > >>>>>>>Best Wishes, > >>>>>>>Allan Menezes > >>>>>> > >>>>>>-- > >>>>>>Geoffroy > >>>>>> > >>>>>>--------------------------------------------------------------------- > >>>>>>-- -- This SF.net email is sponsored by: Splunk Inc. > >>>>>>Still grepping through log files to find problems? Stop. > >>>>>>Now Search log events and configuration files using AJAX and a > >>>>>> browser. Download your FREE copy of Splunk now >> > >>>>>> http://get.splunk.com/ > >>>>>> _______________________________________________ > >>>>>>Oscar-devel mailing list > >>>>>>[email protected] > >>>>>>https://lists.sourceforge.net/lists/listinfo/oscar-devel > >>>>> > >>>>>---------------------------------------------------------------------- > >>>>>-- - This SF.net email is sponsored by: Splunk Inc. > >>>>>Still grepping through log files to find problems? Stop. > >>>>>Now Search log events and configuration files using AJAX and a > >>>>> browser. Download your FREE copy of Splunk now >> > >>>>> http://get.splunk.com/ > >>>>> _______________________________________________ > >>>>>Oscar-devel mailing list > >>>>>[email protected] > >>>>>https://lists.sourceforge.net/lists/listinfo/oscar-devel -- Geoffroy ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
