Re: X unkillable in R state sometimes on startx , /proc/sysrq-trigger T output attached

>
>     BUG: fb_imageblit called before fb_check_var and fb_set_par function
>

> present in all recent kernels. It might be argued that this is not a
> kernel bug
> but a problem of  X - have a look at the Linux-fbdevel thread.
>
> Does X start reliably without a linux framebuffer driver?
> Does X start reliably with vesafb?

Hmm I missed the fact that you are using radeonfb, this could point to
the X chipset initialisation code as well...

I'll try and track down if the evil patch made it into xorg in FC4..

Dave.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: X unkillable in R state sometimes on startx , /proc/sysrq-trigger T output attached
    • From: Knut Petersen <[email protected]>

• Prev by Date: Re: X unkillable in R state sometimes on startx , /proc/sysrq-trigger T output attached
• Next by Date: Re: [RFC patch 2/3] remove pci_driver.owner and .name fields
• Previous by thread: Re: X unkillable in R state sometimes on startx , /proc/sysrq-trigger T output attached
• Next by thread: [PATCH] 1/5 ibmveth fix bonding
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]