Just to alert potential readers, that the bug is now discussed there :
http://bugzilla.kernel.org/show_bug.cgi?id=8143
Eric Lacombe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Just to alert potential readers, that the bug is now discussed there :
http://bugzilla.kernel.org/show_bug.cgi?id=8143
Eric Lacombe
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hello,
I've just triggered the bug again but _now_ without the nvidia proprietary
module. Unfortunately, I hadn't enable the DEBUG options yet.
Nevertheless, It seems that the bug was triggered when the NAS was going to
awake and that 2 user applications wanted to access it during his
Hello,
I've just triggered the bug again but _now_ without the nvidia proprietary
module. Unfortunately, I hadn't enable the DEBUG options yet.
Nevertheless, It seems that the bug was triggered when the NAS was going to
awake and that 2 user applications wanted to access it during his
Eric Lacombe <[EMAIL PROTECTED]> :
[...]
> Also, if you have some new ideas about the problem or what I could try to
> trigger it more frequently (I already wake up the NAS as more as I can, but
> maybe I could write a script to do that), I would be thankful.
You can add more DEBUG options for
Hello,
Sorry for the long time without giving new information about the problem/bug,
but I wasn't able to trigger it since now.
Well, this time, my system freeze on a 2.6.20.1.
I try to use the magic sysrq (which works fine when my system is running), but
nothing happen (unraw, reboot, etc.).
Hello,
Sorry for the long time without giving new information about the problem/bug,
but I wasn't able to trigger it since now.
Well, this time, my system freeze on a 2.6.20.1.
I try to use the magic sysrq (which works fine when my system is running), but
nothing happen (unraw, reboot, etc.).
Eric Lacombe [EMAIL PROTECTED] :
[...]
Also, if you have some new ideas about the problem or what I could try to
trigger it more frequently (I already wake up the NAS as more as I can, but
maybe I could write a script to do that), I would be thankful.
You can add more DEBUG options for
On Tuesday 13 February 2007 21:30:47 Francois Romieu wrote:
> Eric Lacombe <[EMAIL PROTECTED]> :
> [...]
>
> > That problem also remind me that when I compiled this driver without
> > the "CONFIG_NET_ETHERNET" (in the section "Ethernet (10 or 100Mbit)"), I
> > have really poor performance with the
On Tuesday 13 February 2007 21:30:47 Francois Romieu wrote:
Eric Lacombe [EMAIL PROTECTED] :
[...]
That problem also remind me that when I compiled this driver without
the CONFIG_NET_ETHERNET (in the section Ethernet (10 or 100Mbit)), I
have really poor performance with the net device.
Eric Lacombe <[EMAIL PROTECTED]> :
[...]
> That problem also remind me that when I compiled this driver without
> the "CONFIG_NET_ETHERNET" (in the section "Ethernet (10 or 100Mbit)"), I have
> really poor performance with the net device. Maybe it is related, or not ;)
>
> If it gives you more
Eric Lacombe [EMAIL PROTECTED] :
[...]
That problem also remind me that when I compiled this driver without
the CONFIG_NET_ETHERNET (in the section Ethernet (10 or 100Mbit)), I have
really poor performance with the net device. Maybe it is related, or not ;)
If it gives you more ideas ?
12 matches
Mail list logo
