|
Bugzilla – Full Text Bug Listing |
| Summary: | Multiple lockups on installation on HP DL380 G4 | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Rob Hutton <rhutton> |
| Component: | Kernel | Assignee: | E-mail List <kernel-maintainers> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Alpha 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Rob Hutton
2005-11-15 21:44:34 UTC
I guess it's a kernel problem... Can we have some more info? /var/log/messages? Output of 'dmesg'? When it hangs, it hangs hard. No resposiveness from keyboard at all. I can send in info from before the hang. What can I provide before that might help? If you could reproduce it on 10.0 with the kernel updated to the one from 10.1, you might be able to see more, possibly set up a serial console to catch the last messages, etc. I am able to recreate this on a 10.0 DVD X86_64 also. Note, these are XEONs with 64 bit extensions. We are successfully running X86_64 Redhat on these machines. I will get a serial console on now and we are going to try the i586 install also. This same behavior occurs on all three machines we have tried it on. 10.1 isn't really alpha yet, so this cannot be a blocker... give us some time to get our kernel fully up to speed :-) Some more questions - the Hardware field of this report says x86; you say "Xeon with 64bit extensions" which I assume means x86_64? If you set nmi_watchdog=1 or =2 on the kernel command line, does that give an oops message when the system gets hung? Does the SLES9SP3 kernel of the day (ftp://ftp.suse.com/pub/projects/kernel/kotd) work? No feedback, closing as WONTFIX Problem occurs on all versions of SUSE including 10.1 from 9 forward. Aborting the installation and loading the network driver to do a network install results in a successful installation every time. The problem only occures when installing WITHOUT ABORTING AND DROPPING TO THE TEXT MENU and doing a CD install. I see. If you provide the information we asked for in comments #3 amd 7 above, we may even be able to help you :-) What about the serial console output - in comment #5 you mentioned you were going to hook up a serial console. If you watch the list of kernel modules being loaded during installation (I think it's on Alt-F7), what are the last few modules that get loaded before the freeze? What happens if you abort the install and load these modules manually? No feedback, closing. |