Bug 155328 - Reiserfs oops during booting
Summary: Reiserfs oops during booting
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: x86 SuSE Linux 10.0
: P2 - High : Major
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-05 21:02 UTC by Joseph Wenninger
Modified: 2006-04-03 03:12 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
screen shot remote console (46.29 KB, image/png)
2006-03-05 21:04 UTC, Joseph Wenninger 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Wenninger 2006-03-05 21:02:04 UTC 
Hi!

I'm using the YOU kernel version 2.6.13-15.8-smp, The system is a dual xeon with a 3ware sata raid. About every second reboot reiserfs causes a kernel oops during mounting of the root partition. I guess it is some kind of race condition because every know and then it works.

I guess this could be related to Bug 155099 - frequent reiserfs oops with 10.0 (inkl. latest patches), altough I didn't notice the problem yet, once the system has completely started up. And the other difference is that I'm using a 32 bit system, not an amd64

Kind regards
Joseph Wenninger
Comment 1 Joseph Wenninger 2006-03-05 21:04:59 UTC 
Created attachment 71280 [details]
screen shot remote console
Comment 2 Olaf Kirch 2006-03-06 08:54:11 UTC 
The oops your screen shot shows is probably just a consequence
of (one of) the previous oopses which your screen shot does not show.
Can you provide these as well, please?
Comment 3 Greg Kroah-Hartman 2006-04-03 03:12:24 UTC 
Closing due to lack of response.

If you can provide the needed information, please add it here, and reopen
the bug.

Also, can you try the 10.1 beta releases to see if this is solved there?