From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Alan Piszcz <ap@solarrain.com>
Subject: Re: 2.6.33: Xorg+khubd lockup (D-state) BUG / ioctl EVIOCGNAME failed: Inappropriate ioctl for device / PreInit returned NULL
Date: Mon, 29 Mar 2010 12:38:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1003291237480.27175@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.1003291224170.27175@p34.internal.lan>
On Mon, 29 Mar 2010, Justin Piszcz wrote:
>
>
> On Mon, 29 Mar 2010, Alan Stern wrote:
> For your patch, what does this patch against? It does not apply cleanly
> for 2.6.33.
It also fails against 2.6.34-rc2, can you diff -u and show the patch so
I can patch manually or include a patch against 2.6.33 or 2.6.34-rc2?
Thanks.
>
>>
>> Alan Stern
>>
>>
>> Index: usb-2.6/drivers/usb/host/ohci-hcd.c
>> ===================================================================
>> --- usb-2.6.orig/drivers/usb/host/ohci-hcd.c
>> +++ usb-2.6/drivers/usb/host/ohci-hcd.c
>> @@ -290,6 +290,8 @@ static int ohci_urb_dequeue(struct usb_h
>> */
>> urb_priv = urb->hcpriv;
>> if (urb_priv) {
>> + ohci_info(ohci, "start unlink urb %p, ed %p\n",
>> + urb, urb_priv->ed);
>> if (urb_priv->ed->state == ED_OPER)
>> start_ed_unlink (ohci, urb_priv->ed);
>> }
>> @@ -324,6 +326,9 @@ ohci_endpoint_disable (struct usb_hcd *h
>>
>> if (!ed)
>> return;
>> + ohci_info(ohci, "disable ed %p (#%02x) state %d%s\n",
>> + ed, ep->desc.bEndpointAddress, ed->state,
>> + list_empty(&ed->td_list) ? "" : " (has tds)");
>>
>> rescan:
>> spin_lock_irqsave (&ohci->lock, flags);
>> @@ -770,6 +775,10 @@ static irqreturn_t ohci_irq (struct usb_
>> return IRQ_HANDLED;
>> }
>>
>> + ohci_info(ohci, "int %x enable %x rm_list %p\n", ints,
>> + ohci_readl(ohci, ®s->intrenable),
>> + ohci->ed_rm_list);
>> +
>> /* We only care about interrupts that are enabled */
>> ints &= ohci_readl(ohci, ®s->intrenable);
>>
>>
>
next prev parent reply other threads:[~2010-03-29 16:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 12:29 Justin Piszcz
2010-03-25 12:35 ` Justin Piszcz
2010-03-25 13:40 ` Justin Piszcz
2010-03-25 14:17 ` Alan Stern
2010-03-25 14:47 ` Justin Piszcz
2010-03-25 15:53 ` Alan Stern
2010-03-25 16:45 ` Justin Piszcz
2010-03-25 21:02 ` Alan Stern
2010-03-25 21:14 ` Michael Tokarev
2010-03-29 11:45 ` Justin Piszcz
2010-03-29 15:33 ` Alan Stern
2010-03-29 16:26 ` Justin Piszcz
2010-03-29 16:38 ` Justin Piszcz [this message]
2010-03-29 16:58 ` Alan Stern
2010-03-29 18:44 ` Justin Piszcz
2010-03-30 12:58 ` Justin Piszcz
2010-03-30 17:40 ` Alan Stern
2010-03-30 18:02 ` Justin Piszcz
2010-03-30 23:19 ` Tiago Vignatti
2010-03-31 11:08 ` Justin Piszcz
2010-03-31 18:25 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1003291237480.27175@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®