Bug 385361

Created attachment 260301 [details]
dmesg output from installation of openSUSE 10.3

Can you remove quiet from the boot parameters and provide the output of when it
hangs?

(In reply to comment #2)
> Can you remove quiet from the boot parameters and provide the output of when it
> hangs?

I will need to find s different HD to do the install on and revert.

(In reply to comment #3)
> (In reply to comment #2)
> > Can you remove quiet from the boot parameters and provide the output of when it
> > hangs?
> 
> I will need to find s different HD to do the install on and revert.
OK I found a spare HD. Here's the result of the reinstall:

when I removed "quiet" things scrolled by and then a line sinmilar to the
following kept on repeating:

init[1] trap divide error rip:2aaaab5638a4 rsp: 7fff93e0e4f0 error: 0

followed by:

printk: 7545621 message suppressed

(numbers change, otherwise message is the same)

This is where a loop condition happens.

I hope this helps.

I have the same (init[1] trap divide) error after upgrading from f7 to f8 and
trying a fresh install. So I've tried some betas: 7.92 has the same problem
while 7.90 works.

Is it yet another duplicate of these bugs?
https://bugzilla.redhat.com/show_bug.cgi?id=374521
https://bugzilla.redhat.com/show_bug.cgi?id=375591

It this could suggest something to who is reading this, as I wrote in one of the
bug reports posted above, I had F8 in one HD and my other 2 HD are completely
devoted to FreeBSD.
If I unplug the all the HDs with FreeBSD, F8 boots regularly.

(In reply to comment #1)
> Created an attachment (id=260301) [edit]
> dmesg output from installation of openSUSE 10.3
> 

From your dmesg
sdb1: <bsd: sdb5 sdb6 sdb7 sdb8 sdb9 >

Ah Ahhhh...BSD partitions?
How dare you!?!

(In reply to comment #7)
> (In reply to comment #1)
> > Created an attachment (id=260301) [edit] [edit]
> > dmesg output from installation of openSUSE 10.3
> > 
> 
> From your dmesg
> sdb1: <bsd: sdb5 sdb6 sdb7 sdb8 sdb9 >
> 
> Ah Ahhhh...BSD partitions?
> How dare you!?!
> 

Buongiorno gnazio,

I guess to see how things are done on different OSes. The machine came with
WinXP, I added a HD to put Fedora (F7) on, then added another for FreeBSD.
Hence, each one is on a separate HD. This way there won't be a fight!

As you mentioned earlier I did disconnect everything and put in a "fresh" SATA
HD and the installation went OK. So the question is: what happens when the other
things (HDs and USB devices) are added to the mix? What trips the system and
makes it loop? Why is this happening with F8 and not openSUSE 10.3?

By the way, except for XP the other OSes are all of the 64-bit variety.

(In reply to comment #8)
> (In reply to comment #7)
> > 
> > From your dmesg
> > sdb1: <bsd: sdb5 sdb6 sdb7 sdb8 sdb9 >
> > 
> > Ah Ahhhh...BSD partitions?
> > How dare you!?!
> > 
> 
> Buongiorno gnazio,

Hi, (am I right saying Salaam Tarek? :) I can't guess from you domain, just from
name)

> I guess to see how things are done on different OSes. The machine came with
> WinXP, I added a HD to put Fedora (F7) on, then added another for FreeBSD.
> Hence, each one is on a separate HD. This way there won't be a fight!

Obviously it was just ironic!
I was referring to one of the bug reports I've posted as link. Also on
fedoraforums there is a long thread about the problematic F8 coexistence with
BSD partitions.

> As you mentioned earlier I did disconnect everything and put in a "fresh" SATA
> HD and the installation went OK.
> So the question is: what happens when the other
> things (HDs and USB devices) are added to the mix? What trips the system and
> makes it loop? Why is this happening with F8 and not openSUSE 10.3?

What I've wrote were not meant to be a solution, it was just to add some info
about the problem: the installation process is fully working even if bsd
partitions are present, but, in this case, the boot process fails even if on
different hd.
What I can say about your question is that from what I've seen it will not boot
if you add an HD with BSD. You can try to plug in you BSD disk: in the worst
case it will no boot, but it will do no harm, so if you want to stay with F8,
just unplug the HD and it will work again.
Not sure about USB devices with BSD partitions but I'm prone to think that it
will work.
I'm pretty sure that there is no problem with windows based os, as, in such
case, there should be far more people complaining!

> By the way, except for XP the other OSes are all of the 64-bit variety.
> 

Just for the record, I'm running 2 32bit FreeBSD versions and I was/I'm (not)
running the 64bit F7/F8.
Anyway, on the other thread, people are reporting the same problem with the
32bit version.
About OpenSUSE I don't know, but I think that it is not as bleeding edge as
Fedora, so probably a really new version of $SOMETHING is b0rked.

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