From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: I can install on the blades with as2.1-u5 (which used the e.49 kernel for the installation). Once the system is up and running (the network interfaces show up as tg3 interfaces btw), and I up2date the box to get the latest kernel (e.57), at which point I cannot reboot into the latest kernel. I have seen two conditions so far in the test installations that I have done. Either the system panics upon bootup (and actually never boots up completely), or the integrated Cisco switch in the BladeCenter chassis sees errors on the tg3 interface, and disables the port, rendering the environment offline. Are you aware of anyone else reporting this sort of unexpected behavior? Thanks Kambiz Version-Release number of selected component (if applicable): kernel-enterprise-2.4.9-e.57 How reproducible: Always Steps to Reproduce: 1. See description. Additional info:
Kambiz, could you please attach the kernel errors to this bug report ?
Are you still seeing this behavior? Can you attach console logs to provide more information?
Due to the age of this bug and lack of response from the reporter, I am closing this as WONTFIX.