similar to: ext3 EIP

Does anyone know how to diagnose the error "Unable to handle kernel paging request at virtual address xxxxxx"? I got this error (followed by a panic and a crash) on a server running CentOS 4.4 with the 2.6.9-42.0.8.ELsmp kernel. The machine is based on an Intel 975XBX2 motherboard (975X chipset). I have built several of these and they have been extremely stable. This one is

Hi all. Every few days I am getting a message that looks like the one I have cut and pasted below. It is accompanied by a severe slowdown of the system. In fact, it's practically locked. The machine runs gnome-desktops for 40 users plus about a hundred sessions of a curses based point of sale software, plus a few other functions, so it's a busy machine. Dual Xeon 3.2GHz processors.

Hello, Stephen, It seem that in the presence of several jornalling file systems in the kernel some mechanism is needed for proper sharing of the ->journal_info pointer in the task_struct. One journalled file system can indirectly call another during page fault in copy_from_user, quota file modification, or __alloc_pages()->balance_classzone()->shrink_cache()->vm_writeback()

http://www.sample.banga.lt/crash.gif System - fully (except kernel) updated RedHat 7.3. Filesystems - ext3 in default ordered mode. What could be the cause of the crash? Kernel update will solve the problem? Thanks, Mindaugas

Hi, I have a server configured as follows: a standard 2.4.18 kernel, IDE discs, 1Gb RAM (not all used), load avg around 1-2. a large partition, formatted reiserfs within large partition are 80 300Mb loopback file systems, formatted ext3. I got the following assertion yesterday which forced a lot of processes into D state. I'm not sure how easy it is to reproduce this problem.

Signed-off-by: Alexey Dobriyan <adobriyan at mail.ru> Index: linux-2.6.10-bk11-warnings/fs/ext3/inode.c =================================================================== --- linux-2.6.10-bk11-warnings/fs/ext3/inode.c (revision 11) +++ linux-2.6.10-bk11-warnings/fs/ext3/inode.c (revision 12) @@ -803,7 +803,7 @@ if (create) { handle = ext3_journal_current_handle(); - J_ASSERT(handle

Hi, I'm running redhat 9 (kernel 2.4.20-8) as a heavy file server using ext3 file system. The server hang once a week and I found the following my log in /var/log/messages It looks like some ext3 quota problem. Anyone has similar experience ? Any suggestion ? Unable to handle kernel paging request at virtual address ffffffff printing eip: ffffffff *pde = 00001067 *pte = 00000000

Hello ext3-users, we have an oopsy situation here: we have 4 machines: 3 client nodes, 1 master: the master holds a fairly big repository of small files. The repo's current size is ~40GB with ~1.2 M files in ~100 directories. Now, we like to rsync changes from the master to the client nodes, which is working perfectly for 2 nodes, but our 3rd node oopses "sometimes", rendering

Hi, If this is a redundant post I apologize. I am running 2.4.20 on what has been a very stable Athlon machine for months, tried to move a 2 GB file from an ext2 partition to an ext3 and kjournald crashed. Here are the last reminants of my shell scrollback: [*ROOT* mofo /mnt/sda1/mysql/fd 641 ] ll oldmail/ total 2363288 -rw-rw---- 1 mysql mysql 2147483647 Jan 23 18:04 maillog.MYD

Hi, If this is a redundant post I apologize. I am running 2.4.20 on what has been a very stable Athlon machine for months, tried to move a 2 GB file from an ext2 partition to an ext3 and kjournald crashed. Here are the last reminants of my shell scrollback: [*ROOT* mofo /mnt/sda1/mysql/fd 641 ] ll oldmail/ total 2363288 -rw-rw---- 1 mysql mysql 2147483647 Jan 23 18:04 maillog.MYD

Hi Ext3! I'm running about 30 dedicated MySQL machines under quite decent loads, and they are occassionally crashing. I've been logging console messages recently in an effort to find the cause, and some appear to be related to I perused your lists and found the message I'm replying to. If you don't mind, I've included messages and ksymoops from two crashes that I had

Hello List, Running 2.4.21-pre3-ac1 SMP with new quotas (usr and grp), this oops showed up while copying a large amount (about 50gigs, only 1.6 made it before the oops). I'm trying to reproduce as we speak. Unable to handle kernel NULL pointer dereference at virtual address 00000004 c0130956 *pde = 00000000 Oops: 0002 CPU: 0 EIP: 0010:[<c0130956>] Not tainted Using defaults

Hi, A problem with EVMS and Xen: I have patched a 2.6 kernel with the evms patches and then with the Xen patched, compiled and installed it. (kernel is 2.6.11.9 - which is what this server has been running for the past few months w/o the evms patches) At first everything seems to work just fine, I am able to use evms to create a new "volume", in this case it is based on MD/RAID-5 but

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

Hello all: I was getting a reproducible crash during an update of a xen system. The problem went away after I set SELinux to permissive, but the fact that it crashed was alarming (first one on a non-dev system that I've had in over a year). I attempted the update earlier but it crashed at the same point after attempting to update selinux. After verifying hardware (all clean) I ran it again

btree_releasepage is a callback and can be passed unknown gfp flags and then they may end up in kmem_cache_alloc called from alloc_extent_state, slab allocator will BUG_ON when there is HIGHMEM or DMA32 flag set. This may happen when btrfs is mounted from a loop device, which masks out __GFP_IO flag. The check in try_release_extent_state 3399 if ((mask & GFP_NOFS) ==

Hi, One of my servers has had its dom0 "oops" over and over twice in the last week. Unfortunately this is newly deployed so I have no idea if it is down to Xen or not. xen_changeset : Mon Dec 12 18:47:47 2005 +0100 8270:4ad23e798798 dom0 kernel is a vanilla 2.6.12 with Ralph''s .6+xen kernel patch applied. x86_32 sarge packages were used. The .config is

Originally, the test is on a tiger with RHEL installed. The fs is ext3 as default. Then the oops came up. I've installed the test kernel on another tiger with Suse, reiserfs as default. The kernel can boot successfully without any trouble. Is it a known issue? Or what causes this happen? thanks, -zhen -----Original Message----- From: Wang, Zhenyu Z Sent: 2004?7?20? 16:59 To: linux-ia64 at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm experiencing frequent kernel panics when using the X100P card under the 2.6.6 Fedora kernel. I've attached the kernel output to this message - - it looks like the IRQ stack is overflowing and trashing some memory, causing a series of oopses followed by a complete crash. I have just hacked the kernel to reenable 8k stacks and will see

It appears that this bug in data=journal mode, https://listman.redhat.com/archives/ext3-users/2005-February/msg00045.html isn't fixed in 2.6.11.11. Andrew, I've CC'd you since you have previously looked at this specific issue. I'm seeing this problem on dual-Opteron x86-64 boxes serving NFS + Samba3 to a few dozen clients; it takes several hours at high load to reproduce. We