3.2-rc2 regression: floppy driver breaks boot

3.2-rc2 regression: floppy driver breaks boot

[Pavel Machek]

Hi!

3.2-rc1..rc2 fail to boot, due to some warn-on in block layer. It
seems that floppy driver is responsible.

I'll try to turn the floppy driver off and see what happens.

Seems like floppy driver has no maintianer :-(.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: 3.2-rc2 regression: floppy driver breaks boot

[Bob Tracy]

On Tue, Nov 22, 2011 at 12:14:06PM +0100, Pavel Machek wrote:
> 3.2-rc1..rc2 fail to boot, due to some warn-on in block layer. It
> seems that floppy driver is responsible.
> 
> I'll try to turn the floppy driver off and see what happens.
> 
> Seems like floppy driver has no maintianer :-(.

Might be my issue as well.  I've got an old AMD K6-III/450 system with
two floppy drives.  When booting 3.2-rc2 (didn't try "-rc1"), the system
switches video modes (VESA FB console), and then hangs/panics.  No
further info available because the panic happens too early for syslog to
record it, and the console goes blank at the time of the mode switch:
there's nothing on the screen I might transcribe manually.  3.1-final
works fine.

--Bob

Re: 3.2-rc2 regression: floppy driver breaks boot

[Pavel Machek]

On Tue 2011-11-22 08:21:21, Bob Tracy wrote:
> On Tue, Nov 22, 2011 at 12:14:06PM +0100, Pavel Machek wrote:
> > 3.2-rc1..rc2 fail to boot, due to some warn-on in block layer. It
> > seems that floppy driver is responsible.
> > 
> > I'll try to turn the floppy driver off and see what happens.

Without floppy support my x60 boot. iwlwifi driver
(CONFIG_IWLWIFI_LEGACY=y) went crazy after hibernation, but thats
separate issue.

> > Seems like floppy driver has no maintianer :-(.
> 
> Might be my issue as well.  I've got an old AMD K6-III/450 system with
> two floppy drives.  When booting 3.2-rc2 (didn't try "-rc1"), the system
> switches video modes (VESA FB console), and then hangs/panics.  No
> further info available because the panic happens too early for syslog to
> record it, and the console goes blank at the time of the mode switch:
> there's nothing on the screen I might transcribe manually.  3.1-final

Try turning off floppy support. That helped for me.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html