On Thu, Apr 10, 2014 at 07:59:38AM +, Narasimharao Bolisetti wrote:
>
> Hi,
>
> I have checked the same in the recent kernel versions also. Issue is still
> remain.
What versions have you tried, and what are the logs from those versions?
> ::DISCLAIMER::
> -
;
de...@linuxdriverproject.org; linux-ser...@vger.kernel.org;
linux-hotp...@vger.kernel.org; g...@kroah.com; Narasimharao Bolisetti;
nrbolise...@gmail.com; sta...@vger.kernel.org; linux-...@vger.kernel.org;
linux-...@vger.kernel.org
Subject: Re: system hang
On Thu, Apr 10, 2014 at 12:05:52AM
On Thu, Apr 10, 2014 at 12:05:52AM -0700, narasimharo bolisetti wrote:
> My kernel version is:
> 2.6.35.6-45.fc14.i686
Maintenance for this kernel has been dropped years ago, so it very
likely contains many bugs that were fixed in more recent ones. You
should definitely upgrade.
Hoping this he
On Tue, Jan 29, 2008 at 10:38:52PM +0100, Jens Axboe wrote:
> Please try this.
[...]
> The latter is the problem, but since the queue lock is also held before
> doing the double_spin_lock(), we get into even more trouble. The locking
> hierarchy is fine, it's always queue lock -> io context locks
On Tue, Jan 29 2008, Olof Johansson wrote:
> On Tue, Jan 29, 2008 at 09:16:48PM +0100, Jens Axboe wrote:
>
> > Actually, can you try this? It has a known race but nothing to worry
> > about, and it removes ioc->lock from irq context.
>
> I just tried this myself, since I saw hangs within seconds
On Tue, Jan 29, 2008 at 09:16:48PM +0100, Jens Axboe wrote:
> Actually, can you try this? It has a known race but nothing to worry
> about, and it removes ioc->lock from irq context.
I just tried this myself, since I saw hangs within seconds of running
'aiostress' from autotest on this morning's
On Tue, Jan 29 2008, Jens Axboe wrote:
> On Tue, Jan 29 2008, Luck, Tony wrote:
> > I pulled Linus' tree this morning (git head =
> > 0ba6c33bcddc64a54b5f1c25a696c4767dc76292)
> > and built for ia64 (using arch/ia64/configs/tiger_defconfig). System
> > booted
> > OK, but when I stressed it a li
On Tue, Jan 29 2008, Luck, Tony wrote:
> I pulled Linus' tree this morning (git head =
> 0ba6c33bcddc64a54b5f1c25a696c4767dc76292)
> and built for ia64 (using arch/ia64/configs/tiger_defconfig). System booted
> OK, but when I stressed it a little (building another kernel with "make -j32")
> it h
> On 3/16/07, Langsdorf, Mark <[EMAIL PROTECTED]> wrote:
> > The processor is not changing frequency in response to your
> > launch of mplayer. The powersave governor forces it to the
> > lowest frequency regardless of system load. You really want
> > to use ondemand for dynamic frequency scali
On 3/16/07, Langsdorf, Mark <[EMAIL PROTECTED]> wrote:
The processor is not changing frequency in response to your
launch of mplayer. The powersave governor forces it to the
lowest frequency regardless of system load. You really want
to use ondemand for dynamic frequency scaling.
Can you use a
> My kernel boots up with performance cpufreq governor, thus setting
> frequency to 2hgz. Then I change it to powersave governor, thus
> setting frequency to 1ghz just like that:
>
> echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>
> Everything works well. Then I launch mp
From: "Chris Evans" <[EMAIL PROTECTED]>
>
> I thought (on Intel) there was a 4092 hard limit?
>
That's the 2.2 limit, it's gone.
The new limit is total memory and pid space. The pid's are intentionally
limited to 15 bits, the remaining bits are reserved.
In the worst case one running process can
On Tue, 13 Mar 2001, Manfred Spraul wrote:
> * bugfixes for get_pid(). This is the longest part of the patch, but
> it's only necessary if you have more than 10.000 threads running. If you
> have enough memory: launch a forkbomb. If ~ 32760 thread are running the
> kernel enters an endless loop
>
> Maybe it would be good to lower the default threads-max to
> about 10% or less of physical memory ?
>
And MIN_THREADS_FOR_ROOT should be reintroduced: the define is still
there, but the actual code is missing.
I've attached an older patch that:
* reintroduces MIN_THREADS_FOR_ROOT (or remo
On Tue, 13 Mar 2001, Mike Galbraith wrote:
> (A workaround is to lower max_threads to 25% of memory.. works, but is
> really cheezy. OTOH, allowing half of memory to be allocated in task
> structs is a bit cheezy looking too. That means that these tasks
> can't be big enough to be doing real wo
On Tue, 13 Mar 2001, David Shoon wrote:
> Hi,
Greetings,
> After some testing, 2.4.2, 2.4.2-pre3, and 2.4.3-ac18 and ac19 both
> crash/hang when a fork loop (bomb) is executed (under a normal user) and
> killed (by a superuser). This isn't what you'd expect in previous
> kernels (2.2.x, and 2.0
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
> What drive are you using? AFAIR, Andre Hedrick once said certain Maxtor
> drives aren't quite safe with DMA.
Depends on the controller. Maxtor drives play badly with Highpoint
controllers, but are OK with Promise.
-Dan
-
To unsubscribe from this lis
On Wed, 6 Dec 2000, Udo A. Steinberg wrote:
> I also have an A7V and both of my IBM IDE drives are connected to the
> Promise controller, running in UDMA-5 mode. There hasn't been any
> corruption on either of the drives that had to do with UDMA-5 mode.
> And the ext2 bugs that 2.4 kernels had, h
I have not tested of checked the nature of the PCD20265 which is the
onboard version.
On Wed, 6 Dec 2000, Skip Collins wrote:
> After running 2.4.0-test11 for a while, my system would occasionally
> hang during heavy disk activity resulting in a corrupt ext2 filesystem.
> Fortunately, none of
"Udo A. Steinberg" wrote:
> What drive are you using? AFAIR, Andre Hedrick once said certain Maxtor
> drives aren't quite safe with DMA.
Using an IBM 45GB udma5 capable drive. The problems only occur under
_heavy_ disk activity. I have -d 1 -c 3 -m 16 set.
Have you tried thrashing your drive f
On Wed, 6 Dec 2000, Skip Collins wrote:
> For now I am going to fall back to the slower ide bus. But I wanted to
> let people know that there still may be problems with ext2 corruption in
> the latest test kernel.
If your kernel halts, you should not be surprised if you get file system
errors. Y
Skip Collins wrote:
>
> I have a 900MHz Athlon/Asus A7V mobo system with an onboard ata100
> promise controller. I have only had problems when my ata100/udma5
> harddrive is connected to the promise controller. Using the ATA66 ide
> bus eliminates the problem. I typically see the corruption when
I'd be more inclined to think its the combination of drive/controller
more than an ext2fs problem. If it was a fs corruption issue, you should
still see it on the slower bus.
On Wed, 6 Dec 2000, Skip Collins wrote:
> I have a 900MHz Athlon/Asus A7V mobo system with an onboard ata100
> promise con
> From: Narayan Desai [mailto:[EMAIL PROTECTED]]
>
> > "Randy" == Dunlap, Randy <[EMAIL PROTECTED]> writes:
>
> >> Hi, I have been having problems with the usb audio driver on a set
> >> of Philips DSS330. The driver seemed to work properly up until
> >> 2.3.99-6. The driver included with 2
> "Randy" == Dunlap, Randy <[EMAIL PROTECTED]> writes:
>> Hi, I have been having problems with the usb audio driver on a set
>> of Philips DSS330. The driver seemed to work properly up until
>> 2.3.99-6. The driver included with 2.3.99-6 worked correctly when
>> included with kernels up to 2
> Hi, I have been having problems with the usb audio driver on a set of
> Philips DSS330. The driver seemed to work properly up until 2.3.99-6.
> The driver included with 2.3.99-6 worked correctly when included with
> kernels up to 2.4.0test6 or so. The current driver (2.4.0test7+) will
> hang my
26 matches
Mail list logo
