On 1/22/2011 2:53 PM, Alan Cox wrote:
> Ok try this
> Remove the 'quiet' add
>
> irqpoll initcall_debug
>
> The first one tries to catch and deal with hangs due to IRQ routing bugs
> in the BIOS etc, the second will print a trace of each function called
> during initialisation. It's not exciting to most people but as part of a
> Fedora bug report it will let the Fedora kernel maintainers see which
> initialiser hung the machine.

     Ok, finally got a moment to try this.  Current kernel line is:

     xdriver=vesa nomodeset ide=nodma noapic acpi=off ignore_loglevel 
enforcing=0 initcall_debug

     That doesn't give me anything I don't already know or have seen - 
it looks up after discovering the main drive and CD.  Adding 'irqpoll' 
to the line just locks up way earlier in the boot process:

     ....
     [   0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, 
MinObjects=0, CPUs=2, Nodes=1
     [   0.000000] Hierarchical RCU implementation.
     [   0.000000] - RCU dyntick-idle grace-period acceleration is enabled.
     [   0.000000] - RCU-based detection of stalled CPUs is disabled.
     [   0.000000] - Verbose stalled-CPUs detection is disabled.
     [   0.000000] NR_IRQS:2304
     [   0.000000] Console: colour VGS+ 80x25
     [   0.000000] console [tty0] enabled
     [   0.000000] spurious 8259A interrupt: IRQ7.

     ... and it dies.

     If I try to boot with *just* 'ignore_loglevel irqpoll', same thing, 
it dies like above.

     What I don't get is how this dies with FC14 but not with CentOS 5 
... did they figure out something that the FC developers haven't?

     A



-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Reply via email to