[Bug 42716] Boot failure with KMS enabled (radeon)

2012-02-27 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=42716





--- Comment #4 from Paul Menzel   
2012-02-27 09:41:59 ---
(In reply to comment #2)
> I'm marking this as invalid.  The machine I was seeing this on has died, and 
> it
> started with all of the usb ports going bad.  From there, other parts stopped
> working over the course of several days.  I suspect a bad motherboard that was
> introducing faults, and 3.1.x was somehow working around them better than
> 3.2.x.  Who knows?  :/

Could you please document what machine and what board this was? In case others
experience problems with the same machine it is quite helpful to know of
quality issues.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.


[Bug 42716] Boot failure with KMS enabled (radeon)

2012-02-27 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=42716


Paul Menzel  changed:

   What|Removed |Added

 CC||paulepanter at users.sourcefor
   ||ge.net




--- Comment #3 from Paul Menzel   
2012-02-27 09:40:14 ---
(In reply to comment #0)

[?]

> Any idea what's going on here?  I don't have the option to attach a serial
> console, for what that's worth, so that aside, any suggestions for further
> debugging?

Next time you can try netconsole. Although it has to be loaded before the
radeon module. I guess a way to come around that issue is to build the module
for the network card into the Linux kernel.

Additionally you could have started using a standard driver like vesafb(?) and
then load the radeon module manually after the system booted.

Thanks and good luck with your new system.

[1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.


[Bug 42716] Boot failure with KMS enabled (radeon)

2012-02-27 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=42716


Robby Workman  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Comment #2 from Robby Workman   2012-02-27 04:05:44 ---
I'm marking this as invalid.  The machine I was seeing this on has died, and it
started with all of the usb ports going bad.  From there, other parts stopped
working over the course of several days.  I suspect a bad motherboard that was
introducing faults, and 3.1.x was somehow working around them better than
3.2.x.  Who knows?  :/

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.


[Bug 42716] Boot failure with KMS enabled (radeon)

2012-02-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=42716


Paul Menzel paulepan...@users.sourceforge.net changed:

   What|Removed |Added

 CC||paulepanter@users.sourcefor
   ||ge.net




--- Comment #3 from Paul Menzel paulepan...@users.sourceforge.net  2012-02-27 
09:40:14 ---
(In reply to comment #0)

[…]

 Any idea what's going on here?  I don't have the option to attach a serial
 console, for what that's worth, so that aside, any suggestions for further
 debugging?

Next time you can try netconsole. Although it has to be loaded before the
radeon module. I guess a way to come around that issue is to build the module
for the network card into the Linux kernel.

Additionally you could have started using a standard driver like vesafb(?) and
then load the radeon module manually after the system booted.

Thanks and good luck with your new system.

[1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 42716] Boot failure with KMS enabled (radeon)

2012-02-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=42716


Robby Workman r...@rlworkman.net changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Comment #2 from Robby Workman r...@rlworkman.net  2012-02-27 04:05:44 ---
I'm marking this as invalid.  The machine I was seeing this on has died, and it
started with all of the usb ports going bad.  From there, other parts stopped
working over the course of several days.  I suspect a bad motherboard that was
introducing faults, and 3.1.x was somehow working around them better than
3.2.x.  Who knows?  :/

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 42716] Boot failure with KMS enabled (radeon)

2012-02-02 Thread bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=42716





--- Comment #1 from Michel D?nzer   2012-02-02 11:59:30 
---
(In reply to comment #0)
> Any idea what's going on here?

Given your mixed testing results, I suspect the bisect result is bogus; you
probably need to at least test each kernel a couple of times before declaring
it as good.


> I don't have the option to attach a serial console, for what that's
> worth, so that aside, any suggestions for further debugging?

You could try netconsole.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.


[Bug 42716] Boot failure with KMS enabled (radeon)

2012-02-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=42716





--- Comment #1 from Michel Dänzer mic...@daenzer.net  2012-02-02 11:59:30 ---
(In reply to comment #0)
 Any idea what's going on here?

Given your mixed testing results, I suspect the bisect result is bogus; you
probably need to at least test each kernel a couple of times before declaring
it as good.


 I don't have the option to attach a serial console, for what that's
 worth, so that aside, any suggestions for further debugging?

You could try netconsole.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel