Bug 190811 - rhgb crash with new FC5 kernel 2107
Summary: rhgb crash with new FC5 kernel 2107
Keywords:
Status: CLOSED DUPLICATE of bug 190575
Alias: None
Product: Fedora
Classification: Fedora
Component: rhgb
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-05 12:25 UTC by Carlos N. Romero
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-06 18:34:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Carlos N. Romero 2006-05-05 12:25:34 UTC
Description of problem:

I installed new kernel FC5 2107.
Now rhgb crah in graphic mode with the X old cursor.
Note: With kernel 2096 rhgb run ok.

Version-Release number of selected component (if applicable):

rhgb 0.16.3-1
  
Actual results:

In grub I don't start kernel with rhgb.

Comment 1 Christian Krause 2006-05-05 13:21:54 UTC
I can confirm this bug report. It happens for me on two different system (laptop
and desktop) running FC 5 with all updates (5/4/2006)

booting the kernel 2107 with rhgb:
X screen appears, system doesn't keep booting, no login screen
It is possible to press Ctrl+Alt+backspace. After this boot process is resumed. 

booting the older 2096 kernel:
everthing works fine

Comment 2 Christian Krause 2006-05-06 16:27:39 UTC
It seems, that this problem disappeared in the last kernel update. With
2.6.16-1.2111_FC5 the problem doesn't occur any more on my system.

However, that kernel's changelog doesn't mention anything related:
* Thu May 04 2006 Dave Jones <davej> [2.6.16-1.2111_FC5]
- 2.6.16.14
- Revert broken Xen update that sneaked into the last update.

* Wed May 03 2006 Dave Jones <davej>
- disable MSI until 2.6.17.




Comment 3 Luya Tshimbalanga 2006-05-06 18:34:12 UTC

*** This bug has been marked as a duplicate of 190575 ***


Note You need to log in before you can comment on or make changes to this bug.