|
Bugzilla – Full Text Bug Listing |
| Summary: | Kernel Lock Ups | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Stephan Binner <stbinner> |
| Component: | Kernel | Assignee: | E-mail List <kernel-maintainers> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | kernel01 |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | serial console logfile | ||
|
Description
Stephan Binner
2006-02-02 09:57:12 UTC
Created attachment 66152 [details]
serial console logfile
Well, something has indeed gone horribly wrong. Which kernel are you running? That was 2.6.16-rc1-git3-4-smp. After that I upgraded and tonight 2.6.16-rc1-git3-7-smp #1 SMP Mon Jan 30 21:52:12 UTC 2006 locked up. Happened again with 2.6.16-rc3-git3-2-smp , seems a ReiserFS corruption triggers it? Will attach talky serial console logfile. Definitely seeing disk corruption in there. Does this machine run stable on any older kernels? Ok, I've been assuming this was a clean install. If you are not reinstalling between sessions, have you run reiserfsck? I ran reiserfsck today and there was a structural bug detected which required to rebuild the whole tree to fix it. Still, should the whole kernel lockup because of it (assuming there is a relation)? That depends on what caused the corruption. The simple reiserfs corruption you saw should not lock the kernel. But the corruption should not have happened without some memory corruption problem. So, I'd like you to beat up on the system as much as you can and try to trigger it again. Waiting for feedback as per comment #9. Otherwise, we'll assume we can close this bug. No feedback, closing |