Bug 1574

Summary:	First boot after a fresh install freezes just after udev start (due to firewire modules)
Product:	Mageia	Reporter:	Chris Denice <eatdirt>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, thierry.vignaud
Version:	1	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
URL:	https://qa.mandriva.com/show_bug.cgi?id=62631
Whiteboard:
Source RPM:	kernel-2.6.38.7-1.mga1.src.rpm	CVE:
Status comment:

Description Chris Denice 2011-06-04 13:23:03 CEST

Exploring the sysrq commands shows kernel errors on firewire-core and
firewire-ohci modules. The concerned hardware device is

01:00.4 FireWire (IEEE 1394): ALi Corporation M5253 P1394 OHCI 1.1 Controller

I solved the pb by blacklisting them after having mounted my partition by other
means. I guess I am a bit unlucky on that one, but that certainly needs to be
reported in the install notes because is a no-go install for those having that
card :-/

That precise card is known to have pb with the firewire module, but up to now,
it was not imparing the kernel to boot:

see https://qa.mandriva.com/show_bug.cgi?id=62631

Cheers,
Chris.

Ahmad Samir 2011-06-04 23:00:41 CEST

Assignee: bugsquad => tmb

Thierry Vignaud 2011-10-04 17:42:18 CEST

CC: (none) => thierry.vignaud
Component: Installer => RPM Packages
Assignee: tmb => bugsquad

Thierry Vignaud 2011-10-04 17:42:27 CEST

URL: (none) => https://qa.mandriva.com/show_bug.cgi?id=62631

Comment 1 Manuel Hiebel 2011-10-29 15:55:52 CEST

Hello sorry for the delay, bug still valid with the updates ?

P.S: the link https://ieee1394.wiki.kernel.org/index.php/Juju_Migration in the Mandriva's bug doesn't work any more.

Keywords: (none) => NEEDINFO

Comment 2 Marja Van Waes 2011-12-20 09:21:37 CET

Reporter, please reply to the question above within two weeks from now, to avoid this bug being closed as OLD. Thank you.

CC: (none) => marja11

Comment 3 Marja Van Waes 2012-01-18 08:21:50 CET

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD