On Sun, Dec 02, 2001 at 11:46:35AM +0100, Emmanuel Fleury wrote:
> So you are using the ice1712 driver ?
> Actually the bug has been fixed only on the ens1370 driver.
Thanks to all who worked on this -- I've been getting hangs with the ens1370
for as long as I can remember. I'll await the next rel
[EMAIL PROTECTED] wrote:
>
> Yes, following your advice, I downloaded the brand new tree and
> compiled it. SMP Abit VP6 with 2 PIII locks up whenever I launch the
> first numID of amixer contents (it makes search for configuration of
> cs8427 chip -Cirrus Logic-), or whenever launching any
Emmanuel wrote:
> Did you tried to get the last CVS archive ?
Yes, following your advice, I downloaded the brand new tree and
compiled it. SMP Abit VP6 with 2 PIII locks up whenever I launch the
first numID of amixer contents (it makes search for configuration of
cs8427 chip -Cirrus L
[EMAIL PROTECTED] wrote:
> HELP !!! Still freeze on smp-machine with card Terratec ewx24/96
> ice1712. Any patch for this card. I suspect here too there is a
> problem of spin_unlock.
Did you tried to get the last CVS archive ?
What sort of freeze are you getting ? (what software are running,
HELP !!! Still freeze on smp-machine with card Terratec ewx24/96
ice1712. Any patch for this card. I suspect here too there is a
problem of spin_unlock.
Thank you.
Paolo
> Fixed.
>
>
> Jaroslav Kysela produced a patch that fixed this problem perfectly. It
> seems to be a spinl
Fixed.
Jaroslav Kysela produced a patch that fixed this problem perfectly. It
seems to be a spinlock problem.
The patch is now available from the CVS archive.
Thanks a lot to Jaroslav
--
Emmanuel
Either
(a) Solaris has solved the faster-than-light problem, and Sun engineers
should get
On Thu, Nov 29, 2001 at 04:21:31PM +0100, Jaroslav Kysela wrote:
>
> Can you try the lasest CVS code or this patch?
Nice one. Tried CVS, seems to have fixed it. I got a segfault from ardour,
and my machine is still up.
I'l stress it some more, and shout if I manage to make it lock up.
Thanks,
On Thu, 29 Nov 2001, Steve Harris wrote:
> On Wed, Nov 28, 2001 at 05:32:15PM +0100, Jaroslav Kysela wrote:
> > It's very much better to use the alsa-driver/utils/insert script, and look
> > to alsa-driver/snd.map file for the IP address, where driver crashed. We
> > can determine easily the func
On Wed, Nov 28, 2001 at 05:32:15PM +0100, Jaroslav Kysela wrote:
> It's very much better to use the alsa-driver/utils/insert script, and look
> to alsa-driver/snd.map file for the IP address, where driver crashed. We
> can determine easily the function.
OK, done that now. I'm a bit lost now thoug
Freeze on SMP with Alsa-0.9.0 CVS
So that the problem has ran out as an non-hardware specific, - few weeks
ago we were searching for incompatibility between Abit VP6 and
alsa-0.9beta > than beta7, which is working - I ask if anyone had an
idea for re-reading lowlevel code (i2c and cs8427.
Freeze on SMP with Alsa-0.9.0 CVS
So that the problem has ran out as an non-hardware specific, - few weeks
ago we were searching for incompatibility between Abit VP6 and
alsa-0.9beta > than beta7, which is working - I ask if anyone had an
idea for re-reading lowlevel code (i2c and cs8427.
Robert Siemer wrote:
>
> Like any driver, it owns the cpu until finished or until driver code
> gives cpu away. The driver can only be pre-empted by interrupts and
> such.
>
> The kernel is not monitoring itself, it's monitoring user space
> processes...
Yes, I think I get it. Of course the k
From: Emmanuel Fleury <[EMAIL PROTECTED]>
> What is suprising me is that the kernel should take care of the
> liveness of the system and it seems to not detect this problem (I
> mean the distribution of cpu time should be fair among processes).
>
> I can add that I noticed that even if there is
Hi folks,
Ok, I had made some tests yesterday evening and I will go on this evening.
I tried the magic key and the insert (actually now I get what it is
doing and this is very nice!).
But I did those things in the wrong order and I have to start again the
'get ready and freeze' session this
On Wed, Nov 28, 2001 at 10:43:21PM +0100, Peter Enderborg wrote:
> Emmanuel Fleury wrote:
>
> I have also a freez.
> This is on the midipart. I have got it two times now. And the oops is not
> in my kernel log so I got it by paper. I hope this can help.
> My test is simple:
> run pmidi-1.5.4 (mo
Emmanuel Fleury wrote:
I have also a freez.
This is on the midipart. I have got it two times now. And the oops is not
in my kernel log so I got it by paper. I hope this can help.
My test is simple:
run pmidi-1.5.4 (more then one at once)
And start and stop them with kill -STOP/-CONT.
After a whi
On Wed, 28 Nov 2001, Emmanuel Fleury wrote:
> Jaroslav Kysela wrote:
>
> > On Wed, 28 Nov 2001, Steve Harris wrote:
> >
> > It's very much better to use the alsa-driver/utils/insert script, and look
> > to alsa-driver/snd.map file for the IP address, where driver crashed. We
> > can determine eas
Jaroslav Kysela wrote:
> On Wed, 28 Nov 2001, Steve Harris wrote:
>
> It's very much better to use the alsa-driver/utils/insert script, and look
> to alsa-driver/snd.map file for the IP address, where driver crashed. We
> can determine easily the function.
Ooops, I already got the Sys Rq key in
From: Emmanuel Fleury <[EMAIL PROTECTED]>
> Steve Harris wrote:
> > On Wed, Nov 28, 2001 at 01:12:17AM +0100, Emmanuel Fleury wrote:
> >
> > If you're hitting the same bug as me then the oops never gets written
> > because the IRQ handler gets disabled.
>
> I don't know exactly if it is the same
On Wed, 28 Nov 2001, Steve Harris wrote:
> On Wed, Nov 28, 2001 at 01:12:17AM +0100, Emmanuel Fleury wrote:
> >
> > My BIG problem was that I really can't get any log from this problem.
> > No ooops, no strace output (the file was existing but was empty), no
> > syslog, nothing ! :-/
>
> If you'r
Steve Harris wrote:
> On Wed, Nov 28, 2001 at 01:12:17AM +0100, Emmanuel Fleury wrote:
>
> If you're hitting the same bug as me then the oops never gets written
> because the IRQ handler gets disabled.
I don't know exactly if it is the same than you. I don't have enough
information to be sure
On Wed, Nov 28, 2001 at 01:12:17AM +0100, Emmanuel Fleury wrote:
>
> My BIG problem was that I really can't get any log from this problem.
> No ooops, no strace output (the file was existing but was empty), no
> syslog, nothing ! :-/
If you're hitting the same bug as me then the oops never gets
Hi again,
Some new infos (just in case somebody is interested :-)).
The Alsa-OSS modules are not involved (it crash even if they are not loaded.
I tried to reach my computer via the network after a crash. Suprisingly,
ping is working fine but neither ssh neither telnet or ftp or anything
is
Duncan Sands wrote:
>
> Try using the magic SysRq key to get information (see the
> sysrq.txt file in the linux/Documentation directory of your
> kernel sources; you will probably have to recompile your
> kernel).
Good idea ! I wasn't thinking about it !
I will try, thanks
--
Emmanuel
We
Josh Green wrote
>
> So I take it machine is unusable after freeze?
Well, the freeze seems to stop all keyboard and mouse events.
The cursor is still blinking, and the mpeg123 weird bug is telling me
that the computer is somehow still active. But I didn't tried to reach
it by the network (I
> So I tried to collect as much information as I can about this freezing
> bug.
Try using the magic SysRq key to get information (see the
sysrq.txt file in the linux/Documentation directory of your
kernel sources; you will probably have to recompile your
kernel).
Duncan.
___
On Tue, 2001-11-27 at 16:12, Emmanuel Fleury wrote:
>
> Moreover, I don't know WHERE it is freezing. It must definitely be
> somewhere in the kernel (you can't blow up Linux like this without being
> directly in the kernel), but where precisely ??? Dunno.
>
> So, Hlp ! :-)
So I take it m
Hi,
So I tried to collect as much information as I can about this freezing
bug.
First I am running with a Debian testing/unstable (Sid). To 'celebrate'
the bug, I compiled two kernel 2.4.16, one smp and one mono (to see if
it was SMP related).
My hardware is:
- Dual-proc PentiumII@450MHz
- Moth
28 matches
Mail list logo
