similar to: Assertion failure in do_get_write_access() at transaction.c:737: "(((jh2bh(jh)) on a 2.4.18-14 (RH8.0) kernel while experiencing SCSI errors

Hi, By running some scripts on our target system for a while, I lost all means of access to the system. It seems that the kernel is crashed with the following error message: Assertion failure in do_get_write_access() at transaction.c:731: "(((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0)" Oops: Exception in kernel mode, sig: 4 We are currently running Linux version

Hi all (and developers in particular) I just got bitten by this Assertion. The one that starts as in the subject, and ends with: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" Google reminds me that it was mentioned a few times earlier this year, but I couldn't find any statement saying that it has been fixed. I got this in a 2.4.16 kernel, though the

I noticed in the archives that there were patches for this problem, but I've yet to find the patches. Has this been fixed in any of the released kernel RPMs from Redhat? Right now this system is running Redhat 7.2. When I can get a maintenance window I'm going to upgrade to 7.3 and I'm hoping there is a standard kernel available that fixes these problems. kernel: Assertion failure in

* compiled from cvs, i am trying call ip phones in callmanager 3.2 10.17.0.2 is my callmanager i noticed from network dumps that instead of sending rtp to the ip phone, * sends it to 10.17.0.2! thereby causing no audio from * to ip phone. audio from ip phone to * is ok. only callmanager calls fail. netmeeting works ok... here is the debug, thanks for any info ~kelvin H323 debug enabled --

Hi! Samba 2.2.4, Linux. smbd loses connection to the PDC - although rest of organization feels fine... I've had the following cropping up: Jul 25 07:40:13 10.17.0.2 smbd[6994]: [2002/07/25 07:40:13, 0] lib/fault.c:fault_report(38) Jul 25 07:40:13 10.17.0.2 smbd[6994]: [2002/07/25 07:40:13, 0] lib/fault.c:fault_report(39) Jul 25 07:40:13 10.17.0.2 smbd[6994]: Please read the file

If you decide to run kernel 2.4.20 under RH8.0, you may want to apply the following patch in /etc/rc.d: --- rc.sysinit.orig 2002-08-22 14:10:52.000000000 -0700 +++ rc.sysinit 2002-12-05 19:46:31.000000000 -0800 @@ -178,8 +178,8 @@ if [ $usb = "1" ]; then needusbstorage=`grep -e "^I.*Cls=08" /proc/bus/usb/devices 2>/dev/null` action $"Initializing USB

Howdy. We've got a couple IBM x440 (Summit) 8-way Xeon systems that I've been trying to get netbooting for a while. Since we use Kickstart and SystemImager to load OSes on our systems, a system has to be able to netboot before it can be made available to folks for project use. System BIOS is the current one, v1.08. They're booting from a planar BroadCom Tigon3 adapter. BIOS

We've been noticing some problems with ext3 and, in our case, postfix, that appear to come to light under heavy disk i/o loading. A previous thread found here (http://www.redhat.com/mailing-lists/ext3-users/msg04189.html) documents an identical set of symptons (and similar setup), but with RH 7.2 The specifics are this: 1. Stock install of RH8.0 with postfix. 2. Linux mx 2.4.18-14 #1

Hi, I just had my server cry this out to the console: Assertion failure in do_get_write_access() at transaction.c:658: "jh->b_transaction == journal->j_committing_transaction" kernel BUG at transaction.c:658! invalid operand: 0000 CPU: 0 EIP: 0010:[<c015e1f6>] Not tainted EFLAGS: 00010286 eax: 0000007d ebx: c2ff4200 ecx: c243e000 edx: c068af00 esi: c0d6d900

On my Debian box: Package: lilo Version: 1:22.2-5 Severity: normal lilo seems to cause a kernel warning (see subject) when / is a ext3 partition. Maybe a kernel problem? Who knows. I'm running 2.4.19-rc1-ac7 -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux hummus 2.4.19-rc1-ac7 #1 Wed Jul 17 22:14:20 CEST 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions

Hello, I am not subscribed to this mailing list. My apologies if non-members are not allowed to post in this forum. I have a Linux-2.4.19pre10aa4 computer and I have seen an error message "Unexpected dirty buffer encountered at do_get_write_access:598 (03:05 blocknr 0)" appears in the log. With a little bit of research I found that this message is printed from fs/jbd/journal.c,

Hi, I'm running stock kernel 2.4.18, and was downloading some things when I filled up one of my partitions. This was sent to all attached terminals: Assertion failure in do_get_write_access() at transaction.c:708: "handle->h_buffer_credits > 0" I think: invalid operand: 0000 may have followed. Anyway, it also gave a stack trace and register dump (to syslog), which I've

I'm using redhat 7.2 without kernel upgrade and encountered following error. Assertion failure in do_get_write_access() at transaction.c:611: blah blah In this mailing list, I found out this is a kernel bug. ;( Which kernel can I use safely? in 2.4.9-31 from redhat, is it fixed? -- Chung Ha-nyung <alita@[kldp.org|neowiz.com> NeoWiz <http://www.neowiz.com> SayClub

I have two networked pcs. pc 1- RH8.0 which came with Samba-backend 1.0.8 and Samba 2.2.5 pc 2- XP Home I am able to access the shared folders from pc2 on pc1. However from pc2 I can not even see the ressources of pc1. In My Network Places/Entire Network/Microsoft Windows Network/"My Workgroup" I can see "pc1" but when I click on it I get an error message: \\"pc1"

Good evening: I am running RedHat Linux 8.0 on a box that has my Epson Stylus Color 777 printer attached to it. The printer works fine from all applications on my Linux box using a driver I picked up from TurboPrint. I have downloaded and installed Samba 2.7.2 and am trying to print from a Windows 2000 box to this Linux machine. The problem is that when I print, the document seems to queue up

I guess this could be filed under the 'shot myself in the foot' section, but I figured I'd report it anyways.. Kernel 2.5.50-bk6, x86, preempt, PIIX IDE, ext3 fs. I dd'ed the first part of a ext3 partition to tmp, then mounted it via loopback. (the image passed a fsck, except for warning about corrupt part. table or superblock) I tried to 'cd' into a directory within

We have DELL 2650 with CENTOS 3.4 installed. Today I saw following messages on /var/log/messages. Anyone know what it mean? Does it point to which disk? =================================== Jun 4 06:58:40 ORA03 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Jun 4 06:58:40 ORA03 kernel: Possible IO failure. Jun 4 06:58:40 ORA03 kernel:

This patch adds jbd_lock_bh_state() and jbd_unlock_bh_state() around accessses to jh->b_committed_data. Fixes oss bugzilla#1131 http://oss.oracle.com/bugzilla/show_bug.cgi?id=1131 Signed-off-by: Sunil Mushran <sunil.mushran at oracle.com> --- fs/ocfs2/suballoc.c | 28 ++++++++++++++++++++++++---- 1 files changed, 24 insertions(+), 4 deletions(-) diff --git a/fs/ocfs2/suballoc.c

hi michael, here are the core dumps. only kphone works when 0.5.5 and * cvs. audiocodes and msn messenger all cause seg faults when calling ccm thru * (or vice-versa) ~kelvin [chan_oh323.so] => (OpenH323 Channel Driver) == Parsing '/etc/asterisk/rtp.conf': Found == Parsing '/etc/asterisk/oh323.conf': Found 0:00.004 OpenH323 Wrapper OpenH323 Wrapper

Hi, We''re trying to run Xen on a Debian "Etch" base system (kernel 2.6.18-6-xen-amd64), but have come across a strange networking error whenever bridging (vif-bridge/network-bridge) is in operation. The symptom is that the dom0 base system loses all network connectivity to the outside world while the two guest instances function perfectly well. As far as we can tell, we