Prev: linux-next: Tree for May 28 (tm6000)
Next: intel_menlow: fix memory leaks in error path
From: Shirish Pargaonkar on 28 May 2010 12:50
After this sequence of calls, system hangs (smp, x86 box based with
..34 kernel), can ping only.
I have not been able to break in with Alt Sysrq t, working on that

rc = wait_event_interruptible_timeout(ses->server->response_q,
(midQ->midState != MID_REQUEST_SUBMITTED), timeout);
if (rc < 0) {
cFYI(1, ("command 0x%x interrupted", midQ->command));
return -1;
}

and when function that invoking function after coming out with ERESTARTSYS
(I kill the command with Ctrl C) calls
spin_lock(&GlobalMid_Lock);

system hangs. If I sleep before return -1 (e.g. msleep(1), no hang)

I do not have to use wait_event_interruptible_timeout and no such problems with
wait_event_timeout, it is only when signal/interrupt is involved, I
run into this problem

Any pointers/ideas what could be happening, would be really really appreciated.

Regards,

Shirish
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Maciej Rutecki on 6 Jun 2010 04:10
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=16139
for your bug report, please add your address to the CC list in there, thanks!

On piątek, 28 maja 2010 o 18:44:46 Shirish Pargaonkar wrote:
> After this sequence of calls, system hangs (smp, x86 box based with
> .34 kernel), can ping only.
> I have not been able to break in with Alt Sysrq t, working on that
>
> rc = wait_event_interruptible_timeout(ses->server->response_q,
> (midQ->midState != MID_REQUEST_SUBMITTED),
> timeout); if (rc < 0) {
> cFYI(1, ("command 0x%x interrupted", midQ->command));
> return -1;
> }
>
> and when function that invoking function after coming out with ERESTARTSYS
> (I kill the command with Ctrl C) calls
> spin_lock(&GlobalMid_Lock);
>
> system hangs. If I sleep before return -1 (e.g. msleep(1), no hang)
>
> I do not have to use wait_event_interruptible_timeout and no such problems
> with wait_event_timeout, it is only when signal/interrupt is involved, I
> run into this problem
>
> Any pointers/ideas what could be happening, would be really really
> appreciated.
>
> Regards,
>
> Shirish
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo(a)vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

--
Maciej Rutecki
http://www.maciek.unixy.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: linux-next: Tree for May 28 (tm6000)
Next: intel_menlow: fix memory leaks in error path