Hi Michael,
Michael Edwards wrote:
Can you boot the system from a liveCD like knopix (theres some for FC7
too I am sure).
I did boot from fc7 resuce mode chrooted /mnt/syimage and found no log
file in the / or /tmp dir do you know where it may be hidden, please?
I can modifiy any file this way . I modified grub.conf to include
pci=nommconfig -all-generic-ide -noapic on the kernel command parameters
but still the kernel panics!
Allan
You may be able to get some of the boot log info by mounting the
drives that way. Probably not the dump from the kernel panic, but
maybe...
Even if you can't you can do "shift+pgup" (sometimes) to scroll back
on terminal screens and see if there are any interesting things at the
begining of the panic. The later messages are usually less helpful
than the last message before the panic and the start of the error.
I think you did, but have you tried booting into single user mode?
You can try reimaging the nodes with the "correct" modules loaded
(from the modprobe.conf) by doing something like
/var/lib/systemimager/scripts/pre-install/01all.load_sata_driver
#!/bin/sh
#
echo
echo "loading ahci sata driver"
echo
modprobe mptspi
modprobe mptsas
modprobe mptfc
But I would think this would just make the install fail completely and
not just give you a bad kernel, so this is probably grabbing at
straws.
On 7/25/07, Allan Menezes <[EMAIL PROTECTED]> wrote:
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
-------------------------------------------------------------------------
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
-------------------------------------------------------------------------
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
