* Problems with NFTL in 2.4.22
@ 2003-11-12 0:30 Karim Yaghmour
2003-11-12 9:57 ` David Woodhouse
0 siblings, 1 reply; 2+ messages in thread
From: Karim Yaghmour @ 2003-11-12 0:30 UTC (permalink / raw)
To: Linux-MTD
I haven't seen anything in the archives about this, so here goes:
I've had quite a few problems trying to interface with an 8MB DOC with
2.4.22. The system would simply freeze when I tried doing things like
mount, unmount, mke2fs, cat fs image to device, etc. No oops no nothing,
just the tools would not return to the command line and I'd have to
hard-reset the system. I tried a few variations in the commands to try
to get the same results, but nothing really got it working. I eventually
gave up and tried 2.4.21 instead, and then everything I was trying to
do before just worked fine ...
I cannot say exactly what's the problem, and I don't have the time
to track it down, but I can say that 2.4.22 has a problem with handling
at least the 8MB DOC.
HTH,
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 514-812-4145
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Problems with NFTL in 2.4.22
2003-11-12 0:30 Problems with NFTL in 2.4.22 Karim Yaghmour
@ 2003-11-12 9:57 ` David Woodhouse
0 siblings, 0 replies; 2+ messages in thread
From: David Woodhouse @ 2003-11-12 9:57 UTC (permalink / raw)
To: karim; +Cc: Linux-MTD
On Tue, 2003-11-11 at 19:30 -0500, Karim Yaghmour wrote:
> I haven't seen anything in the archives about this, so here goes:
>
> I've had quite a few problems trying to interface with an 8MB DOC with
> 2.4.22. The system would simply freeze when I tried doing things like
> mount, unmount, mke2fs, cat fs image to device, etc. No oops no nothing,
> just the tools would not return to the command line and I'd have to
> hard-reset the system.
Did you get a backtrace of the offending process(es) with SysRq-T?
I suspected it might be because we're calling cond_resched() when one of
our callers has already set current->state to TASK_UNINTERRUPTIBLE. But
I've had a report that it still happens in the current CVS code, in
which that definitely shouldn't be the case. Can you confirm that?
--
dwmw2
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-11-12 9:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-11-12 0:30 Problems with NFTL in 2.4.22 Karim Yaghmour
2003-11-12 9:57 ` David Woodhouse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox