Re: [Xen-users] Create domU with pciback fails, then my system re-boots! xen-hypervisor-4.3-amd64

[Jo Mills <jo@xxxxxxxxxxxxxxxx>]

Hi,

I probably should have pasted this in with the original mail, 
apologies.  Is this the same as?

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742432

Regards,

Jo.

----------

Apr 27 11:07:54 green root: /etc/xen/scripts/block-drbd: add 
XENBUS_PATH=backend/vbd/2/51728
Apr 27 11:07:54 green root: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/2/51712
Apr 27 11:07:54 green kernel: [570108.754409] block drbd21: role( Secondary -> 
Primary ) 
Apr 27 11:07:54 green root: /etc/xen/scripts/block-drbd: Writing 
backend/vbd/2/51728/physical-device 93:15 to xenstore.
Apr 27 11:07:54 green root: /etc/xen/scripts/block-drbd: Writing 
backend/vbd/2/51728/hotplug-status connected to xenstore.
Apr 27 11:07:55 green kernel: [570109.316546] xen-blkback:ring-ref 9, 
event-channel 9, protocol 1 (x86_64-abi) 
Apr 27 11:07:55 green kernel: [570109.322049] xen-blkback:ring-ref 10, 
event-channel 10, protocol 1 (x86_64-abi) 
Apr 27 11:07:55 green kernel: [570109.609820] pciback 0000:04:01.0: enabling 
device (0000 -> 0003)
Apr 27 11:07:55 green kernel: [570109.609890] xen: registering gsi 17 
triggering 0 polarity 1
Apr 27 11:07:55 green kernel: [570109.609894] Already setup the GSI :17
Apr 27 11:07:57 green kernel: [570111.820063] ------------[ cut here 
]------------
Apr 27 11:07:57 green kernel: [570111.820073] WARNING: CPU: 0 PID: 0 at 
/build/linux-oxWk_8/linux-3.13.7/net/sched/sch_generic.c:264 
dev_watchdog+0x226/0x230()
Apr 27 11:07:57 green kernel: [570111.820074] NETDEV WATCHDOG: eth0 
(via-rhine): transmit queue 0 timed out
Apr 27 11:07:57 green kernel: [570111.820075] Modules linked in: xen_blkback 
fuse btrfs raid6_pq xor ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs 
xen_gntdev xen_evtchn xenfs xen_privcmd drbd lru_cache crc32c libcrc32c bridge 
stp llc xen_pciback loop psmouse iTCO_wdt iTCO_vendor_support coretemp 
serio_raw evdev pcspkr processor i2c_i801 i2c_core lpc_ich mfd_core button 
i3200_edac thermal_sys edac_core ext4 crc16 mbcache jbd2 dm_mod sg sd_mod 
sr_mod crc_t10dif cdrom crct10dif_common ata_generic e1000 via_rhine ata_piix 
mii libata scsi_mod floppy e1000e ptp pps_core uhci_hcd ehci_pci ehci_hcd 
usbcore usb_common
Apr 27 11:07:57 green kernel: [570111.820112] CPU: 0 PID: 0 Comm: swapper/0 Not 
tainted 3.13-1-amd64 #1 Debian 3.13.7-1
Apr 27 11:07:57 green kernel: [570111.820114] Hardware name: Intel Corporation 
S3210SH/S3210SH, BIOS S3200X38.86B.00.00.0052.112920101508 11/29/2010
Apr 27 11:07:57 green kernel: [570111.820115]  0000000000000009 
ffffffff814a1327 ffff88007f603e20 ffffffff8105ba72
Apr 27 11:07:57 green kernel: [570111.820118]  0000000000000000 
ffff88007f603e70 0000000000000001 0000000000000000
Apr 27 11:07:57 green kernel: [570111.820120]  ffff8800047ea000 
ffffffff8105bad7 ffffffff81746c98 ffff880000000030
Apr 27 11:07:57 green kernel: [570111.820122] Call Trace:
Apr 27 11:07:57 green kernel: [570111.820123]  <IRQ>  [<ffffffff814a1327>] ? 
dump_stack+0x41/0x51
Apr 27 11:07:57 green kernel: [570111.820130]  [<ffffffff8105ba72>] ? 
warn_slowpath_common+0x72/0x90
Apr 27 11:07:57 green kernel: [570111.820132]  [<ffffffff8105bad7>] ? 
warn_slowpath_fmt+0x47/0x50
Apr 27 11:07:57 green kernel: [570111.820136]  [<ffffffff813dd1a6>] ? 
dev_watchdog+0x226/0x230
Apr 27 11:07:57 green kernel: [570111.820138]  [<ffffffff813dcf80>] ? 
dev_graft_qdisc+0x70/0x70
Apr 27 11:07:57 green kernel: [570111.820140]  [<ffffffff81066cec>] ? 
call_timer_fn+0x2c/0x100
Apr 27 11:07:57 green kernel: [570111.820142]  [<ffffffff813dcf80>] ? 
dev_graft_qdisc+0x70/0x70
Apr 27 11:07:57 green kernel: [570111.820144]  [<ffffffff81067b29>] ? 
run_timer_softirq+0x1f9/0x2b0
Apr 27 11:07:57 green kernel: [570111.820147]  [<ffffffff81060802>] ? 
__do_softirq+0xe2/0x260
Apr 27 11:07:57 green kernel: [570111.820149]  [<ffffffff81060c35>] ? 
irq_exit+0x95/0xa0
Apr 27 11:07:57 green kernel: [570111.820152]  [<ffffffff8130e457>] ? 
xen_evtchn_do_upcall+0x27/0x40
Apr 27 11:07:57 green kernel: [570111.820155]  [<ffffffff814afdfe>] ? 
xen_do_hypervisor_callback+0x1e/0x30
Apr 27 11:07:57 green kernel: [570111.820156]  <EOI>  [<ffffffff810013aa>] ? 
xen_hypercall_sched_op+0xa/0x20
Apr 27 11:07:57 green kernel: [570111.820160]  [<ffffffff810013aa>] ? 
xen_hypercall_sched_op+0xa/0x20
Apr 27 11:07:57 green kernel: [570111.820163]  [<ffffffff8100997c>] ? 
xen_safe_halt+0xc/0x20
Apr 27 11:07:57 green kernel: [570111.820165]  [<ffffffff8101a5e4>] ? 
default_idle+0x14/0xb0
Apr 27 11:07:57 green kernel: [570111.820169]  [<ffffffff810a777e>] ? 
cpu_startup_entry+0xbe/0x280
Apr 27 11:07:57 green kernel: [570111.820171]  [<ffffffff818c4f2d>] ? 
start_kernel+0x44e/0x459
Apr 27 11:07:57 green kernel: [570111.820173]  [<ffffffff818c4904>] ? 
repair_env_string+0x58/0x58
Apr 27 11:07:57 green kernel: [570111.820175]  [<ffffffff818c6dbc>] ? 
xen_start_kernel+0x535/0x53f
Apr 27 11:07:57 green kernel: [570111.820177] ---[ end trace f02180c3887e92fb 
]---
Apr 27 11:07:57 green kernel: [570111.820348] via-rhine 0000:04:00.0 eth0: 
Transmit timed out, status 0000, PHY status 786d, resetting...
Apr 27 11:07:57 green kernel: [570111.820453] via-rhine 0000:04:00.0 eth0: 
Reset not complete yet. Trying harder.
Apr 27 11:07:58 green kernel: [570111.908065] d-con vm-12-disk: PingAck did not 
arrive in time.
Apr 27 11:07:58 green kernel: [570111.935732] d-con vm-12-disk: peer( Primary 
-> Unknown ) conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown ) 
Apr 27 11:07:58 green kernel: [570111.981665] d-con vm-12-disk: asender 
terminated
Apr 27 11:07:58 green kernel: [570111.981669] d-con vm-12-disk: Terminating 
drbd_a_vm-12-di
Apr 27 11:07:58 green kernel: [570111.981719] d-con vm-12-disk: Connection 
closed
Apr 27 11:07:58 green kernel: [570111.981730] d-con vm-12-disk: conn( 
NetworkFailure -> Unconnected ) 
Apr 27 11:07:58 green kernel: [570111.981732] d-con vm-12-disk: receiver 
terminated
Apr 27 11:07:58 green kernel: [570111.981733] d-con vm-12-disk: Restarting 
receiver thread
Apr 27 11:07:58 green kernel: [570111.981734] d-con vm-12-disk: receiver 
(re)started
Apr 27 11:07:58 green kernel: [570111.981741] d-con vm-12-disk: conn( 
Unconnected -> WFConnection ) 
Apr 27 11:08:00 green kernel: [570114.208239] e1000 0000:04:02.0 eth2: Detected 
Tx Unit Hang
Apr 27 11:08:00 green kernel: [570114.208239]   Tx Queue             <0>
Apr 27 11:08:00 green kernel: [570114.208239]   TDH                  <80>
Apr 27 11:08:00 green kernel: [570114.208239]   TDT                  <90>
Apr 27 11:08:00 green kernel: [570114.208239]   next_to_use          <90>
Apr 27 11:08:00 green kernel: [570114.208239]   next_to_clean        <80>
Apr 27 11:08:00 green kernel: [570114.208239] buffer_info[next_to_clean]
Apr 27 11:08:00 green kernel: [570114.208239]   time_stamp           <1087da874>
Apr 27 11:08:00 green kernel: [570114.208239]   next_to_watch        <81>
Apr 27 11:08:00 green kernel: [570114.208239]   jiffies              <1087dab30>
Apr 27 11:08:00 green kernel: [570114.208239]   next_to_watch.status <0>

    .
    .
    .
    
Then a bit more along the same lines until the "looping" display starts.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users