Displaying 9 results from an estimated 9 matches for "gdth".
Did you mean:
gdt
2005 Nov 16
0
(large, external) data journal BUG (Assertion failure in __journal_drop_transaction() at fs/jbd/checkpoint.c:626: "transaction->t_forget == NULL")
Hi,
A couple of our important servers, both running FC4 but one i386 and one
x86_64, have been crashing recently. They both are running ext3
data=journal with large external journals and high commit intervals.
Both machines use the gdth driver for their hardware RAID sets, if
that's of any use. I think the hardware is good in both cases.
I hope someone finds this data useful enough to be able to fix the bug.
IMAP server crash (once only, thus far):
Assertion failure in __journal_drop_transaction() at
fs/jbd/checkpoint.c:6...
2005 Oct 17
1
CentOS 4.1 - Hang on boot
Hi
Trying to install 4.1 on a chassis that has an Intel hardware RAID card
in it - RedHat 7.3 was fine on this box.
On boot the install runs through until i opt to skip the media test -
After that it 'loading gdth driver' and the system hangs
Any ideas as google is not my friend
thanks
2007 Jun 16
1
had 3 kernel panics since upgrade from 3.0.21a to 3.0.25 and 3.0.25a on CentOS 4.4
...0:58:28 uk kernel: SMP
Jun 9 10:58:28 uk kernel: Modules linked in: nls_utf8 usb_storage vfat
fat md5 ipv6 parport_pc lp parport tun sunrpc ipt_MASQUERADE ipt_TOS
ipt_LOG iptable_filter iptable_mangle iptable_nat ip_conntrack ip_tables
button battery ac ohci_hcd e1000 tg3 floppy st ext3 jbd dm_mod gdth
aic79xx sata_sil libata sd_mod scsi_mod
Jun 9 10:58:28 uk kernel: CPU: 0
Jun 9 10:58:28 uk kernel: EIP: 0060:[<c01450fd>] Not tainted VLI
Jun 9 10:58:28 uk kernel: EFLAGS: 00010216 (2.6.9-22.0.1.EL.1omsmp)
Jun 9 10:58:28 uk kernel: EIP is at vma_prio_tree_add+0x36/0x95
Jun 9 1...
2003 Aug 05
5
(no subject)
Does anyone keep a known telemarketer caller id database? If not has anyone
proposed an Asterisk community project to share this information? Sort of a
nation wide blacklist so Asterisk'ers can cut down on the garbage calls...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2002 Feb 12
1
2.4.17: BUG()at transaction.c:609
very modular 2.4.17; 2xPIII-800; no HIGHMEM; gcc-2.96-98; all ext3;
modules loaded include autofs4, nfs, nfsd, eepro100, acenic, ipchains,
unix, gdth. This happened during the dump (incrcp.pl is a custom backup
script also happening at the time).
Does ext3-0.9.17 fix this?
kernel BUG at transaction.c:609!
invalid operand: 0000
CPU: 1
EIP: 0010:[unix:__insmod_unix_O/lib/modules/2.4.17/kernel/net/unix/unix.o_M+-1684041/96] Not tainted
E...
2020 Apr 07
0
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
...ave typically:
>>
>> drivers/scsi/hisi_sas/hisi_sas_v3_hw.c: .this_id??????????????? = -1,
>>
>> It's _very_ uncommon to have a negative number as the SCSI target
>> device; in fact, it _is_ an unsigned int already.
>>
>
> FWIW, the only other driver (gdth) which I see uses this API has this_id
> = -1 in the scsi host template.
>
>> But alright, I'll give it a go; let's see what I'll end up with.
>
> note: If we want a fixed scsi_device per host, calling
> scsi_mq_setup_tags() -> scsi_get_host_dev() will fail a...
2002 Apr 14
1
hardware or software bug?
I had the following spat out by syslog on my (2.4.18-pre7-ac3) mailer /
web server:
Assertion failure in do_get_write_access() at transaction.c:611: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)"
One of its partitions froze hard--I've rebooted it, and I have an oops
which the BUG() triggered which won't decode at the moment, but I'll sort
that one out
2020 Mar 11
6
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
On Tue, Mar 10, 2020 at 09:08:56PM +0000, John Garry wrote:
> On 10/03/2020 18:32, Christoph Hellwig wrote:
> > On Wed, Mar 11, 2020 at 12:25:28AM +0800, John Garry wrote:
> > > From: Hannes Reinecke <hare at suse.com>
> > >
> > > Allocate a separate 'reserved_cmd_q' for sending reserved commands.
> >
> > Why? Reserved command
2020 Mar 11
6
[PATCH RFC v2 02/24] scsi: allocate separate queue for reserved commands
On Tue, Mar 10, 2020 at 09:08:56PM +0000, John Garry wrote:
> On 10/03/2020 18:32, Christoph Hellwig wrote:
> > On Wed, Mar 11, 2020 at 12:25:28AM +0800, John Garry wrote:
> > > From: Hannes Reinecke <hare at suse.com>
> > >
> > > Allocate a separate 'reserved_cmd_q' for sending reserved commands.
> >
> > Why? Reserved command