Re: Nasty Wine/kernel bug, anyone?

2001-04-06 Thread Andreas Mohr
On Thu, Mar 29, 2001 at 01:23:59AM +0200, Ulrich Weigand wrote: In any case, this would seem to be clearly a bug in that sound module. I don't know, however, why only Wine would trigger that bug ... Bye, Ulrich Any progress on that one ? BTW, we just had our first operating system

Re: Nasty Wine/kernel bug, anyone?

2001-03-28 Thread Ulrich Weigand
If I were going to make more WAGs (Wild Assed guesses), I'd hazard a guess that this was due to my Alsa sound system (running on the AC97 codec on my Asus motherboard). I tried to walk the stack back, but didn't get very far (after the first time of wrongly computing the hex offset from

Re: Nasty Wine/kernel bug, anyone?

2001-03-27 Thread Ulrich Weigand
Process 1503 found at c2cd8000, esp c2cd9e04 Call Trace: [c010794f] [c2cd8000] Hmpf, this is not quite what I expected :-/ (Maybe the kernel is compiled with -fomit-frame-pointer?) Could you try using a modified version of dump that will at least dump out the complete kernel stack so that we

Re: Nasty Wine/kernel bug, anyone?

2001-03-26 Thread Ulrich Weigand
Hi Jeremy, Could you check in which kernel routine the process is blocked? (e.g. using ps -Ao pid,wchan) USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jwhite2531 2.3 14.8 86144 38016 pts/0 D16:02 0:05 wine --debugmsg +server msimn.exe PID

Re: Nasty Wine/kernel bug, anyone?

2001-03-26 Thread Jeremy White
PID WCHAN 2531 down Great :-( Now the interesting thing would be to know *which* semaphore this is waiting on ... I'd really like to see a kernel stack backtrace on this. However, there doesn't appear to be an easy way to do so ... I was pretty sure this was going to be a

Re: Nasty Wine/kernel bug, anyone?

2001-03-26 Thread Jeremy White
Just spent 30 minutes trying to reproduce with Outlook, and now, of course, I can't. I may well have pressed ^C at some point; I'm learning that Outlook does, eventually (2-3 minutes) come up (but promptly crashes). However, whilst trying something else, I had another winelib program crash.

Re: Nasty Wine/kernel bug, anyone?

2001-03-26 Thread Ulrich Weigand
Hi Jeremy, Great :-( Now the interesting thing would be to know *which* semaphore this is waiting on ... I'd really like to see a kernel stack backtrace on this. However, there doesn't appear to be an easy way to do so ... I was pretty sure this was going to be a fun one...

Re: Nasty Wine/kernel bug, anyone?

2001-03-25 Thread Jeremy White
gerard patel wrote: At 12:14 PM 20/03/2001 -0600, you wrote: snip I saw at least other user report on this (Steve Fox reported this with Lotus Notes). My best guess is that this is a bug in the vfat driver, but that's just a hunch. Where did this Notes bug turn up ? I never saw it on

Re: Nasty Wine/kernel bug, anyone?

2001-03-25 Thread Jeremy White
Could you check in which kernel routine the process is blocked? (e.g. using ps -Ao pid,wchan) USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jwhite2531 2.3 14.8 86144 38016 pts/0 D16:02 0:05 wine --debugmsg +server msimn.exe PID WCHAN 2531 down Hmm.

Re: Nasty Wine/kernel bug, anyone?

2001-03-22 Thread Steve Fox
Could you check in which kernel routine the process is blocked? (e.g. using ps -Ao pid,wchan) Running 'ps -Ao pid,wchan' shows that all the processes in uninterruptible sleep are in the do_exit routine. Because the process is already gone, I can't strace or gdb it. What do you mean 'the