kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #43599
[Bug 1276298] [NEW] iscsi booted system hangs on 3.8.0.19 ramdisk .(ppc - e500mc)
Public bug reported:
I was experimenting with an iscsi boot device as root device , and
one of the preliminary steps is getting a network connection established via
the default initrd.
It appears that starting the network from init hangs the
system.
I installed Ubuntu directly to an iSCSI target via the Ubuntu install , copied
the default vmlinux+initrd to a USB, then attempted to setup the boot
environment via USB where we launch vmlinux and initrd via kexec:
svy-boot# mount /dev/sda1 /mnt
svy-boot# cd /mnt/iscsi
svy-boot# ls
abi-3.8.0-19-powerpc-e500mc
bootargs initrd.img-3.8.0-19-powerpc-e500mc
bootiscsi.sh kernel
config-3.8.0-19-powerpc-e500mc vmlinux-3.8.0-19-powerpc-e500mc
go.sh
svy-boot# ./go.sh
/sbin/kexec --command='root=/dev/ram ro
UUID=3967a9b2-91f5-4dce-98ae-874fcb2d5a7d ro break debug console=tty0
console=ttyS0,115200 interface=eth3
192.168.1.110:192.168.1.140:192.168.1.1:255.255.0.0:jade-iscsi0:eth3:none
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 '
--initrd=/mnt/iscsi/initrd.img-3.8.0-19-powerpc-e500mc -l
/mnt/iscsi/vmlinux-3.8.0-19-powerpc-e500mc
I started the system so it would break if a error occured:
[ 0.000000] Using P4080 DS machine description
[ 0.000000] Memory CAM mapping: 256/256/256 Mb, residual: 3328Mb
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.0-19-powerpc-e500mc (buildd@ross) (gcc version
4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #25-Ubuntu SMP Mon Dec 23 12:18:15 UTC
2013 (Ubuntu 3.8.0-19.25-powerpc-e500mc 3.8.13.13)
The system would likely find the iSCSI device but it hangs when the iscsi stack
is started :
(initramfs) sh +x ./iscissi
[ 1750.717666] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[ 1750.730184] Loading iSCSI transport class v2.0-870.
[ 1750.739849] iscsi: registered transport (tcp)
iscsistart: Logging into iqn.2001-04.com.jade:storage.disk0
192.168.1.140:3260,1
iscsistart: version 2.0-873
[ 1753.621329] tg3 0000:01:00.0 eth3: Link is up at 1000 Mbps, full duplex
- The iSCSI target target was created ona CentOS server ,
#startiscsi.sh
#
# tgtadm --lld iscsi --op new --mode account --user ronnie --password password
# tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
#
# dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10
tgtadm --lld iscsi --op delete --mode target --tid 1
tgtadm --lld iscsi --op new --mode target --tid 1 -T iqn.2001-04.com.jade:storage.disk0
tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b `pwd`/iscsi.disk0
tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
tgtadm --lld iscsi --op show --mode target
** Affects: linux-ppc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ppc in Ubuntu.
https://bugs.launchpad.net/bugs/1276298
Title:
iscsi booted system hangs on 3.8.0.19 ramdisk .(ppc - e500mc)
Status in “linux-ppc” package in Ubuntu:
New
Bug description:
I was experimenting with an iscsi boot device as root device , and
one of the preliminary steps is getting a network connection established via
the default initrd.
It appears that starting the network from init hangs the
system.
I installed Ubuntu directly to an iSCSI target via the Ubuntu install , copied
the default vmlinux+initrd to a USB, then attempted to setup the boot
environment via USB where we launch vmlinux and initrd via kexec:
svy-boot# mount /dev/sda1 /mnt
svy-boot# cd /mnt/iscsi
svy-boot# ls
abi-3.8.0-19-powerpc-e500mc
bootargs initrd.img-3.8.0-19-powerpc-e500mc
bootiscsi.sh kernel
config-3.8.0-19-powerpc-e500mc vmlinux-3.8.0-19-powerpc-e500mc
go.sh
svy-boot# ./go.sh
/sbin/kexec --command='root=/dev/ram ro
UUID=3967a9b2-91f5-4dce-98ae-874fcb2d5a7d ro break debug console=tty0
console=ttyS0,115200 interface=eth3
192.168.1.110:192.168.1.140:192.168.1.1:255.255.0.0:jade-iscsi0:eth3:none
ISCSI_INITIATOR=iqn.1993-08.org.debian:01:53694d75a62e
ISCSI_TARGET_NAME=iqn.2001-04.com.jade:storage.disk0
ISCSI_TARGET_IP=192.168.1.140 ISCSI_TARGET_PORT=3260 ISCSI_TARGET_GROUP=1 '
--initrd=/mnt/iscsi/initrd.img-3.8.0-19-powerpc-e500mc -l
/mnt/iscsi/vmlinux-3.8.0-19-powerpc-e500mc
I started the system so it would break if a error occured:
[ 0.000000] Using P4080 DS machine description
[ 0.000000] Memory CAM mapping: 256/256/256 Mb, residual: 3328Mb
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.0-19-powerpc-e500mc (buildd@ross) (gcc version
4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #25-Ubuntu SMP Mon Dec 23 12:18:15 UTC
2013 (Ubuntu 3.8.0-19.25-powerpc-e500mc 3.8.13.13)
The system would likely find the iSCSI device but it hangs when the iscsi stack
is started :
(initramfs) sh +x ./iscissi
[ 1750.717666] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[ 1750.730184] Loading iSCSI transport class v2.0-870.
[ 1750.739849] iscsi: registered transport (tcp)
iscsistart: Logging into iqn.2001-04.com.jade:storage.disk0
192.168.1.140:3260,1
iscsistart: version 2.0-873
[ 1753.621329] tg3 0000:01:00.0 eth3: Link is up at 1000 Mbps, full duplex
- The iSCSI target target was created ona CentOS server ,
#startiscsi.sh
#
# tgtadm --lld iscsi --op new --mode account --user ronnie --password password
# tgtadm --lld iscsi --op bind --mode account --tid 1 --user ronnie
#
# dd if=/dev/zero of=iscsi.disk0 bs=1024M count=10
tgtadm --lld iscsi --op delete --mode target --tid 1
tgtadm --lld iscsi --op new --mode target --tid 1 -T iqn.2001-04.com.jade:storage.disk0
tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b `pwd`/iscsi.disk0
tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
tgtadm --lld iscsi --op show --mode target
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1276298/+subscriptions
Follow ups
References