Bug 160974
Summary: | lengthy rsync copy through ssh from fc2 to fc4 produced Oops | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lennart Rolland <chimenigfx> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-04 13:54:45 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: |
Description
Lennart Rolland
2005-06-19 12:04:31 UTC
Discovered some typos. Replace CODE 41 8B 45 48 FF C8 /E 45 48 C7 83 F0 01 00 00 00 00 00 00 48 With CODE 41 8B 45 48 FF C8 7E 45 48 C7 83 F0 01 00 00 00 00 00 00 48 unfortunatly, the useful part of the oops is above all this code. And this part.. RIP mm_release+86 Badness in do_unblank_screen at drivers/char/vt.c:2822(not tainted) do_unblank_screen+100 bust_spin_lock+28 Is very likely a symptom of the earlier oops rather than something useful. If you have the chance to reproduce this, please make sure that the console blanking is disabled (setterm -blank 0 -a) It'll also be useful to get more lines of text on the console, so boot with something like vga=791 (or vga=1 if your monitor doesnt like that mode). You're also playing with fire a little with XFS, as it's known to have problems with 4KB stacks. If any subsequent oopses you capture show XFS or reiserfs in the traces, I recommend filing bugs upstream at http://bugme.osdl.org as those filesystems are unsupported by fedora, and bugs in them get little to no attention from folks at Red Hat. I'll leave this open for now, but if it hasn't been reproduced after a while, there's not much else I can do but close this. [This comment has been added as a mass update for all FC4 kernel bugs. If you have migrated this bug from an FC3 bug today, ignore this comment.] Please retest your problem with todays 2.6.12-1.1398_FC4 update. If your problem involved being unable to boot, or some hardware not being detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE* installing any kernel updates. If in doubt, you can recreate this file using.. mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak mv /etc/modprobe.conf /etc/modprobe.conf.bak kudzu Thank you. Mass update to all FC4 bugs: An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream kernel (2.6.13.2). As there were ~3500 changes upstream between this and the previous kernel, it's possible your bug has been fixed already. Please retest with this update, and update this bug if necessary. Thanks. 2.6.14-1.1637_FC4 has been released as an update for FC4. Please retest with this update, as a large amount of code has been changed in this release, which may have fixed your problem. Thank you. This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. Closing per previous comment. |