[DRBD-user] oops on 2.6.5-rc3-bk2 + drbd-0.7-cvs

Andreas Schultz aschultz at tpip.net
Tue Apr 6 14:42:26 CEST 2004

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 05 April 2004 16:22, Andreas Schultz wrote:
> Hi,
>
> When attempting to start a drbd device on 2.6.5-rc3-bk2, i get the
> following oops:
>
> Apr  5 16:12:50 sdev01 kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000 Apr  5 16:12:50 sdev01 kernel: 
> printing eip:
> Apr  5 16:12:50 sdev01 kernel: c01fcf46
> Apr  5 16:12:50 sdev01 kernel: *pde = 00000000
> Apr  5 16:12:50 sdev01 kernel: Oops: 0002 [#1]
> Apr  5 16:12:50 sdev01 kernel: PREEMPT SMP
> Apr  5 16:12:50 sdev01 kernel: CPU:    0
> Apr  5 16:12:51 sdev01 kernel: EIP:    0060:[blk_run_queue+38/128]    Not
> tainted Apr  5 16:12:51 sdev01 kernel: EFLAGS: 00010002  
> (2.6.5-rc3-bk2-vs0.09.29) Apr  5 16:12:51 sdev01 kernel: EIP is at
> blk_run_queue+0x26/0x80

I have tracked this down in drivers/block/ll_rw_blk.c to:

void blk_run_queue(struct request_queue *q)
{
        unsigned long flags;

        spin_lock_irqsave(q->queue_lock, flags);
^^^^^^^^^^^^^
here, the queue_lock has not been inititalized

        blk_remove_plug(q);
        q->request_fn(q);
        spin_unlock_irqrestore(q->queue_lock, flags);
}

The cruelprint is that i want to use a lvm device as the backend for my drbd 
device and dm devices do not initialise the queue_lock.

setup command: /sbin/drbdsetup /dev/drbd0 disk /dev/nsys/db internal -1 
- --on-io-error=panic

comments?

Andreas

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAcqW6bukMzn5TCZERAub7AKCIxmMCSwb1DfTec/X+dCXytTWq9ACfU1g2
4q9lvYq717RR1DIJm5rfxjY=
=ppoV
-----END PGP SIGNATURE-----



More information about the drbd-user mailing list