On Fri, 25 Mar 2005, Jeremy Fitzhardinge wrote:
> Though it looks a lot better; no more streams of messages.
>
> Now when I resume, I get:
>
> PCI: Enabling device :00:1d.7 ( -> 0002)
> <1>Unable to handle kernel NULL pointer dereference
>
> a second or so after resume. It is completel
Though it looks a lot better; no more streams of messages.
Now when I resume, I get:
PCI: Enabling device :00:1d.7 ( -> 0002)
<1>Unable to handle kernel NULL pointer dereference
a second or so after resume. It is completely locked up at this point;
magic-sysreq gets no response.
lspci
On Fri, Mar 25, 2005 at 06:04:42PM +0530, [EMAIL PROTECTED] wrote:
> Hello Alan Stern ,
>
> I tried the same kernel "2.6.5-7.97-smp" SuSE and it gives no errors .
Then I suggest you stick with the SuSE kernel :)
> Since I need to use the same Linux kernel could you let me know why it
> should n
$B$3$s$K$A$O!"(BYahoo!$B%0%k!<%W(B$B$G$9!#(B
(B
(B[light-bowl-club]$B%0%k!<%W$X$N;[EMAIL PROTECTED](B
(B[EMAIL PROTECTED]"%0%k!<%W$X$N;22CC$7$?$$(B
$B$3$N%a!<%k$rL5;k$7$F$/[EMAIL PROTECTED]l9g$O$=$N$^$^:o=|$7$F$/[EMAIL PROTECTED](B
$B!!%3%s%T%e!<%?%&%$%k%9$N1F6A$G!"$"$J$?$N%a!<%k%"%I%
On R, 2005-03-25 at 13:30 -0800, David Brownell wrote:
> If that's an ISO-IN then I'd still not expect it to work.
> Though Karsten has some "not clean" patches that may help you.
It probably is an ISO-IN transaction, and opening sound device in output
only mode does produce exactly the same error
On Friday 25 March 2005 12:38 pm, Antti Andreimann wrote:
> Ühel kenal päeval (teisipäev, 22. märts 2005, 11:38-0800), kirjutas
> David Brownell:
>
> > Well, this looks right to me, but as you know I don't have a good way to
> > reproduce it. See if this version behaves for you.
>
> I tested the
Ãhel kenal pÃeval (teisipÃev, 22. mÃrts 2005, 11:38-0800), kirjutas
David Brownell:
> Well, this looks right to me, but as you know I don't have a good way to
> reproduce it. See if this version behaves for you.
I tested the patch with 2.6.11.
Here is what I get, when I try to start jackd:
ehci
On Thu, 24 Mar 2005 16:37:21 +0100 Paul Koster <[EMAIL PROTECTED]> wrote:
> When I disable the iso URB submitting, the bulk works well for
> about 2 minutes. Unloading the
> driver results most of the time in kernel panics, but only when I actively
> used the driver in a open/close session.
I
Le 25.03.2005 04:54, Pete Zaitcev a écrit :
On Thu, 24 Mar 2005 13:23:19 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
ub_disconnect() calls ub_cleanup() under ub_lock.
ub_cleanup() calls blk_cleanup_queue(), which can sleep in
elevator_exit()->flush_workqueue().
I'm a little surprised that this
On Fri, Mar 25, 2005 at 10:43:01AM +0300, Roman Kagan wrote:
> > > The patch expects a matching change in scripts/mod/file2alias.c I sent
> > > to linux-hotplug-devel list a few days ago (i.e. puts
> > > bcdDevice in MODNAME as d, rather that dldh).
> >
> > I changed this back, as this
On Fri, 25 Mar 2005 [EMAIL PROTECTED] wrote:
> Hello Alan Stern ,
>
> I tried the same kernel "2.6.5-7.97-smp" SuSE and it gives no errors .
>
> Since I need to use the same Linux kernel could you let me know why it
> should not work on 2.6.9 Enterprise Edition .
> What is the problem due to wh
On Thu, 24 Mar 2005, Matthew Dharm wrote:
> Well, let's start with the obvious: Remove the line of code you mention,
> and instead do:
> snprintf(onetouch->name, 128, "Maxtor Test String");
>
> If that doesn't fix the problem, then it's not the culprit and you need to
> keep looking.
>
>
Hello Alan Stern ,
I tried the same kernel "2.6.5-7.97-smp" SuSE and it gives no errors .
Since I need to use the same Linux kernel could you let me know why it
should not work on 2.6.9 Enterprise Edition .
What is the problem due to which the USB core is unable to read these
descriptors.
Rega
> Hm, something has changed here. Can you just send me the whole new
> driver file and I'll create the diff myself? That will be faster than
> my trying to try to resolve the whole large diff by hand...
please find it attached
--
Kind regards,
Georges Toth
/***
Hi,
It's currently impossible to associate with a shared-key-only access
point using the zd1201 driver. The attached patch fixes it. The reason
was (probably) a typo in the definitions of the authentification types.
I found that they should be (1,2) instead of (0,1) by looking at the
old linux-wla
15 matches
Mail list logo
