Bug 430390
| Summary: | Boot time crash 2.6.23.14-107.fc8 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | vikram goyal <vikigoyal> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 8 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-01-29 21:19:44 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
vikram goyal
2008-01-27 11:24:50 UTC
Created attachment 293072 [details]
copied info from the monitor
disassembly: 0: 8b 54 24 20 mov 0x20(%esp),%edx 4: 03 46 28 add 0x28(%esi),%eax 7: 13 56 2c adc 0x2c(%esi),%edx a: 89 44 24 0c mov %eax,0xc(%esp) e: 89 54 24 10 mov %edx,0x10(%esp) 12: e9 cb 00 00 00 jmp 0xe2 17: 8b 53 10 mov 0x10(%ebx),%edx 1a: 39 54 24 10 cmp %edx,0x10(%esp) 1e: 8b 43 0c mov 0xc(%ebx),%eax 21: 7f 31 jg 0x54 23: 7c 06 jl 0x2b 25: 39 44 24 0c cmp %eax,0xc(%esp) 29: 73 29 jae 0x54 00000000 <.text>: 0: 2b 44 28 1b sub 0x1b(%eax,%ebp,1),%eax eax = 636ce589, ebp = 1 4: 56 push %esi 5: 2c 3b sub $0x3b,%al 7: 54 push %esp 8: 24 18 and $0x18,%al a: 0f 8f b2 00 00 00 jg 0xc2 10: 7c 0a jl 0x1c (In reply to comment #2) > disassembly: > Wrong bug. There isn't enough there to debug this one. Please boot with kernel option 'vga=1' (or 'vga=791') and take a picture of the screen with a digital camera next time. System is oopsing at random places, this is almost certainly a hardware problem (see bug 430442.) |