Thread: [SSI-devel] [ ssic-linux-Bugs-3033977 ] ssi-addnode-dynamic causes new nodes to kernel panic
Brought to you by:
brucewalker,
rogertsang
From: SourceForge.net <no...@so...> - 2010-07-24 11:03:23
|
Bugs item #3033977, was opened at 2010-07-24 21:03 Message generated for change (Tracker Item Submitted) made by djdoomsday You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-27 04:36:56
|
Bugs item #3033977, was opened at 2010-07-24 21:03 Message generated for change (Comment added) made by djdoomsday You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 14:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-27 10:19:13
|
Bugs item #3033977, was opened at 2010-07-24 13:03 Message generated for change (Comment added) made by hughesj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 12:19 Message: "Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic" What panic? "On an unrelated note - Is this the right place to post?" This is the right place to report bugs. If you have questions about using OpenSSI check the openssi-users mailing list. for development check the developers mailing list. For general info check the website http://www.openssi.org ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 06:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-27 11:04:59
|
Bugs item #3033977, was opened at 2010-07-24 21:03 Message generated for change (Comment added) made by djdoomsday You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 21:04 Message: Unfortunately I'm unable to get the exact error as I don't know how to dump the panic to any sort of log. I have patched together as many frames of a captured video session of it here: http://i32.tinypic.com/2rw5h5y.jpg ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 20:19 Message: "Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic" What panic? "On an unrelated note - Is this the right place to post?" This is the right place to report bugs. If you have questions about using OpenSSI check the openssi-users mailing list. for development check the developers mailing list. For general info check the website http://www.openssi.org ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 14:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-27 15:09:03
|
Bugs item #3033977, was opened at 2010-07-24 13:03 Message generated for change (Comment added) made by hughesj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 17:09 Message: It's crashing maybe at at a call to kmem_cache_alloc The call trace is sys_select -> do_select -> ssidev_poll_cli_alloc -> BANG! Looks dodgy. ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 13:04 Message: Unfortunately I'm unable to get the exact error as I don't know how to dump the panic to any sort of log. I have patched together as many frames of a captured video session of it here: http://i32.tinypic.com/2rw5h5y.jpg ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 12:19 Message: "Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic" What panic? "On an unrelated note - Is this the right place to post?" This is the right place to report bugs. If you have questions about using OpenSSI check the openssi-users mailing list. for development check the developers mailing list. For general info check the website http://www.openssi.org ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 06:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-27 15:09:54
|
Bugs item #3033977, was opened at 2010-07-24 13:03 Message generated for change (Comment added) made by hughesj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 17:09 Message: (by looks dodgy I mean it looks like we're trying to do some cluster stuff before the cluster is initialised). ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 17:09 Message: It's crashing maybe at at a call to kmem_cache_alloc The call trace is sys_select -> do_select -> ssidev_poll_cli_alloc -> BANG! Looks dodgy. ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 13:04 Message: Unfortunately I'm unable to get the exact error as I don't know how to dump the panic to any sort of log. I have patched together as many frames of a captured video session of it here: http://i32.tinypic.com/2rw5h5y.jpg ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 12:19 Message: "Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic" What panic? "On an unrelated note - Is this the right place to post?" This is the right place to report bugs. If you have questions about using OpenSSI check the openssi-users mailing list. for development check the developers mailing list. For general info check the website http://www.openssi.org ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 06:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-27 21:30:17
|
Bugs item #3033977, was opened at 2010-07-24 11:03 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-07-27 21:30 Message: mmm, if that is the case then the init script is broken - We did a lot of tracing and it happens right at when udhcpc is called. You should be able to easily replicate the situation by making sure the node you're adding has no static IP entry and you have udhcpc installed and added to /etc/mkinitrd/exe. Those are the conditions you require to have the init script call udhcpc. You can also see from the log that udhcpc does successfully start, but must explode somewhere within itself and cause init to die. I'm wondering if there isn't some dependency that we're missing for udhcpc? I also noticed that busybox is installed, but not used? Should we be using a busybox environment instead? ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 15:09 Message: (by looks dodgy I mean it looks like we're trying to do some cluster stuff before the cluster is initialised). ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 15:09 Message: It's crashing maybe at at a call to kmem_cache_alloc The call trace is sys_select -> do_select -> ssidev_poll_cli_alloc -> BANG! Looks dodgy. ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 11:04 Message: Unfortunately I'm unable to get the exact error as I don't know how to dump the panic to any sort of log. I have patched together as many frames of a captured video session of it here: http://i32.tinypic.com/2rw5h5y.jpg ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 10:19 Message: "Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic" What panic? "On an unrelated note - Is this the right place to post?" This is the right place to report bugs. If you have questions about using OpenSSI check the openssi-users mailing list. for development check the developers mailing list. For general info check the website http://www.openssi.org ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 04:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-28 06:46:54
|
Bugs item #3033977, was opened at 2010-07-24 07:03 Message generated for change (Comment added) made by rogertsang You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- >Comment By: Roger Tsang (rogertsang) Date: 2010-07-28 02:46 Message: Try attached patch for linux-2.6.11-ssi. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-07-27 17:30 Message: mmm, if that is the case then the init script is broken - We did a lot of tracing and it happens right at when udhcpc is called. You should be able to easily replicate the situation by making sure the node you're adding has no static IP entry and you have udhcpc installed and added to /etc/mkinitrd/exe. Those are the conditions you require to have the init script call udhcpc. You can also see from the log that udhcpc does successfully start, but must explode somewhere within itself and cause init to die. I'm wondering if there isn't some dependency that we're missing for udhcpc? I also noticed that busybox is installed, but not used? Should we be using a busybox environment instead? ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 11:09 Message: (by looks dodgy I mean it looks like we're trying to do some cluster stuff before the cluster is initialised). ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 11:09 Message: It's crashing maybe at at a call to kmem_cache_alloc The call trace is sys_select -> do_select -> ssidev_poll_cli_alloc -> BANG! Looks dodgy. ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 07:04 Message: Unfortunately I'm unable to get the exact error as I don't know how to dump the panic to any sort of log. I have patched together as many frames of a captured video session of it here: http://i32.tinypic.com/2rw5h5y.jpg ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 06:19 Message: "Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic" What panic? "On an unrelated note - Is this the right place to post?" This is the right place to report bugs. If you have questions about using OpenSSI check the openssi-users mailing list. for development check the developers mailing list. For general info check the website http://www.openssi.org ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 00:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-28 07:15:02
|
Bugs item #3033977, was opened at 2010-07-24 21:03 Message generated for change (Comment added) made by djdoomsday You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-28 17:15 Message: mmm, I'm currently running 2.6.14. Are you suggesting I will need to compile ssi to 2.6.11 with this patch? ---------------------------------------------------------------------- Comment By: Roger Tsang (rogertsang) Date: 2010-07-28 16:46 Message: Try attached patch for linux-2.6.11-ssi. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-07-28 07:30 Message: mmm, if that is the case then the init script is broken - We did a lot of tracing and it happens right at when udhcpc is called. You should be able to easily replicate the situation by making sure the node you're adding has no static IP entry and you have udhcpc installed and added to /etc/mkinitrd/exe. Those are the conditions you require to have the init script call udhcpc. You can also see from the log that udhcpc does successfully start, but must explode somewhere within itself and cause init to die. I'm wondering if there isn't some dependency that we're missing for udhcpc? I also noticed that busybox is installed, but not used? Should we be using a busybox environment instead? ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-28 01:09 Message: (by looks dodgy I mean it looks like we're trying to do some cluster stuff before the cluster is initialised). ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-28 01:09 Message: It's crashing maybe at at a call to kmem_cache_alloc The call trace is sys_select -> do_select -> ssidev_poll_cli_alloc -> BANG! Looks dodgy. ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 21:04 Message: Unfortunately I'm unable to get the exact error as I don't know how to dump the panic to any sort of log. I have patched together as many frames of a captured video session of it here: http://i32.tinypic.com/2rw5h5y.jpg ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 20:19 Message: "Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic" What panic? "On an unrelated note - Is this the right place to post?" This is the right place to report bugs. If you have questions about using OpenSSI check the openssi-users mailing list. for development check the developers mailing list. For general info check the website http://www.openssi.org ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 14:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-28 08:48:33
|
Bugs item #3033977, was opened at 2010-07-24 13:03 Message generated for change (Comment added) made by hughesj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-28 10:48 Message: You'll need to port Rogers patch from 2.6.11 to 2.6.14, or wait for me to do it (I'll be able to get around to this this weekend - sorry it will take so much time but the disk on my laptop blew up and I have to rebuild my build environment (lenny chroot)). ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-28 09:15 Message: mmm, I'm currently running 2.6.14. Are you suggesting I will need to compile ssi to 2.6.11 with this patch? ---------------------------------------------------------------------- Comment By: Roger Tsang (rogertsang) Date: 2010-07-28 08:46 Message: Try attached patch for linux-2.6.11-ssi. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-07-27 23:30 Message: mmm, if that is the case then the init script is broken - We did a lot of tracing and it happens right at when udhcpc is called. You should be able to easily replicate the situation by making sure the node you're adding has no static IP entry and you have udhcpc installed and added to /etc/mkinitrd/exe. Those are the conditions you require to have the init script call udhcpc. You can also see from the log that udhcpc does successfully start, but must explode somewhere within itself and cause init to die. I'm wondering if there isn't some dependency that we're missing for udhcpc? I also noticed that busybox is installed, but not used? Should we be using a busybox environment instead? ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 17:09 Message: (by looks dodgy I mean it looks like we're trying to do some cluster stuff before the cluster is initialised). ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 17:09 Message: It's crashing maybe at at a call to kmem_cache_alloc The call trace is sys_select -> do_select -> ssidev_poll_cli_alloc -> BANG! Looks dodgy. ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 13:04 Message: Unfortunately I'm unable to get the exact error as I don't know how to dump the panic to any sort of log. I have patched together as many frames of a captured video session of it here: http://i32.tinypic.com/2rw5h5y.jpg ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 12:19 Message: "Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic" What panic? "On an unrelated note - Is this the right place to post?" This is the right place to report bugs. If you have questions about using OpenSSI check the openssi-users mailing list. for development check the developers mailing list. For general info check the website http://www.openssi.org ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 06:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |
From: SourceForge.net <no...@so...> - 2010-07-28 09:42:57
|
Bugs item #3033977, was opened at 2010-07-24 21:03 Message generated for change (Comment added) made by djdoomsday You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Booting / init Group: v1.9.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: djdoomsday (djdoomsday) Assigned to: Nobody/Anonymous (nobody) Summary: ssi-addnode-dynamic causes new nodes to kernel panic Initial Comment: Running Debian v5 2.6.14. Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic when init calls the DHCP client (udhcpc). The cluster works perfectly when using manual ssi-addnode. This has been tested in VMWARE (e1000 emulation) and several dissimilar physical machines. Further debug info forth-coming - Any feedback on what you'd require? ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-28 19:42 Message: Aye that would be great thanks. Take your time. :) ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-28 18:48 Message: You'll need to port Rogers patch from 2.6.11 to 2.6.14, or wait for me to do it (I'll be able to get around to this this weekend - sorry it will take so much time but the disk on my laptop blew up and I have to rebuild my build environment (lenny chroot)). ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-28 17:15 Message: mmm, I'm currently running 2.6.14. Are you suggesting I will need to compile ssi to 2.6.11 with this patch? ---------------------------------------------------------------------- Comment By: Roger Tsang (rogertsang) Date: 2010-07-28 16:46 Message: Try attached patch for linux-2.6.11-ssi. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-07-28 07:30 Message: mmm, if that is the case then the init script is broken - We did a lot of tracing and it happens right at when udhcpc is called. You should be able to easily replicate the situation by making sure the node you're adding has no static IP entry and you have udhcpc installed and added to /etc/mkinitrd/exe. Those are the conditions you require to have the init script call udhcpc. You can also see from the log that udhcpc does successfully start, but must explode somewhere within itself and cause init to die. I'm wondering if there isn't some dependency that we're missing for udhcpc? I also noticed that busybox is installed, but not used? Should we be using a busybox environment instead? ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-28 01:09 Message: (by looks dodgy I mean it looks like we're trying to do some cluster stuff before the cluster is initialised). ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-28 01:09 Message: It's crashing maybe at at a call to kmem_cache_alloc The call trace is sys_select -> do_select -> ssidev_poll_cli_alloc -> BANG! Looks dodgy. ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 21:04 Message: Unfortunately I'm unable to get the exact error as I don't know how to dump the panic to any sort of log. I have patched together as many frames of a captured video session of it here: http://i32.tinypic.com/2rw5h5y.jpg ---------------------------------------------------------------------- Comment By: John Hughes (hughesj) Date: 2010-07-27 20:19 Message: "Whenever we attempt to use the ssi-addnode-dynamic all nodes booting will kernel panic" What panic? "On an unrelated note - Is this the right place to post?" This is the right place to report bugs. If you have questions about using OpenSSI check the openssi-users mailing list. for development check the developers mailing list. For general info check the website http://www.openssi.org ---------------------------------------------------------------------- Comment By: djdoomsday (djdoomsday) Date: 2010-07-27 14:36 Message: We've tried a many multitude of things such as another DHCP client, a newly compiled version of udhcpc, the version of udhcpc within the latest busybox, etc to no avail. Has anyone had any success with addnode-dynamic? On an unrelated note - Is this the right place to post? It has been difficult to find where this community hands out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=405834&aid=3033977&group_id=32541 |