From: Sipos Ferenc <frank@sudo.hu>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Re: [Xen-devel] bt878 based dvr card vs. pci pass-thru
Date: Mon, 18 Dec 2006 10:56:06 +0100 [thread overview]
Message-ID: <1166435766.4291.58.camel@cage> (raw)
In-Reply-To: <C1AC0B5C.5FEC%keir@xensource.com>
Hi All.
> This file should contain your device id, not slot address. Find out the
> numeric device id from 'lspci -n'.
It was clearly stated in the docs that I should have used the output of
'lspci -n' but somehow it supressed my attention. Sorry for wasting your
time on that.
On an other note, I've did what you and the manual suggested and here is
the result:
"""
Dec 18 10:47:43 hive kernel: pciback 0000:07:0e.0: enabling permissive
mode configuration space accesses!
Dec 18 10:47:43 hive kernel: pciback 0000:07:0e.0: permissive mode is
potentially unsafe!
Dec 18 10:47:43 hive kernel: pciback 0000:07:0e.1: enabling permissive
mode configuration space accesses!
Dec 18 10:47:43 hive kernel: pciback 0000:07:0e.1: permissive mode is
potentially unsafe!
Dec 18 10:47:43 hive kernel: pciback 0000:07:0f.0: enabling permissive
mode configuration space accesses!
Dec 18 10:47:43 hive kernel: pciback 0000:07:0f.0: permissive mode is
potentially unsafe!
Dec 18 10:47:43 hive kernel: pciback 0000:07:0f.1: enabling permissive
mode configuration space accesses!
Dec 18 10:47:43 hive kernel: pciback 0000:07:0f.1: permissive mode is
potentially unsafe!
Dec 18 10:47:43 hive kernel: pciback: vpci: 0000:07:0c.0: assign to
virtual slot 0
Dec 18 10:47:43 hive kernel: pciback: vpci: 0000:07:0c.1: assign to
virtual slot 0 func 1
Dec 18 10:47:43 hive kernel: pciback: vpci: 0000:07:0d.0: assign to
virtual slot 1
Dec 18 10:47:43 hive kernel: pciback: vpci: 0000:07:0d.1: assign to
virtual slot 1 func 1
Dec 18 10:47:43 hive kernel: pciback: vpci: 0000:07:0e.0: assign to
virtual slot 2
Dec 18 10:47:43 hive kernel: pciback: vpci: 0000:07:0e.1: assign to
virtual slot 2 func 1
Dec 18 10:47:43 hive kernel: pciback: vpci: 0000:07:0f.0: assign to
virtual slot 3
Dec 18 10:47:43 hive kernel: pciback: vpci: 0000:07:0f.1: assign to
virtual slot 3 func 1
Dec 18 10:47:43 hive kernel: device vif2.0 entered promiscuous mode
Dec 18 10:47:43 hive kernel: ADDRCONF(NETDEV_UP): vif2.0: link is not
ready
Dec 18 10:47:47 hive kernel: ADDRCONF(NETDEV_CHANGE): vif2.0: link
becomes ready
Dec 18 10:47:47 hive kernel: xenbr0: port 3(vif2.0) entering learning
state
Dec 18 10:47:47 hive kernel: xenbr0: topology change detected,
propagating
Dec 18 10:47:47 hive kernel: xenbr0: port 3(vif2.0) entering forwarding
state
Dec 18 10:47:55 hive kernel: PCI: Enabling device 0000:07:0c.0 (0000 ->
0002)
Dec 18 10:47:55 hive kernel: ACPI: PCI Interrupt 0000:07:0c.0[A] -> GSI
16 (level, low) -> IRQ 16
Dec 18 10:47:55 hive kernel: PCI: Enabling device 0000:07:0d.0 (0000 ->
0002)
Dec 18 10:47:55 hive kernel: ACPI: PCI Interrupt 0000:07:0d.0[A] -> GSI
17 (level, low) -> IRQ 20
Dec 18 10:47:57 hive kernel: [__report_bad_irq+36/128] __report_bad_irq
+0x24/0x80
Dec 18 10:47:57 hive kernel: [note_interrupt+162/256] note_interrupt
+0xa2/0x100
Dec 18 10:47:57 hive kernel: [__do_IRQ+233/256] __do_IRQ+0xe9/0x100
Dec 18 10:47:57 hive kernel: [do_IRQ+55/112] do_IRQ+0x37/0x70
Dec 18 10:47:57 hive kernel: [__do_IRQ+179/256] __do_IRQ+0xb3/0x100
Dec 18 10:47:57 hive kernel: [evtchn_do_upcall+146/256]
evtchn_do_upcall+0x92/0x100
Dec 18 10:47:57 hive kernel: [hypervisor_callback+61/72]
hypervisor_callback+0x3d/0x48
Dec 18 10:47:57 hive kernel: [<cd8b5107>] uhci_irq+0x27/0x190
[uhci_hcd]
Dec 18 10:47:57 hive kernel: [<cd8e03a4>] usb_hcd_irq+0x24/0x60
[usbcore]
Dec 18 10:47:57 hive kernel: [handle_IRQ_event+89/160] handle_IRQ_event
+0x59/0xa0
Dec 18 10:47:57 hive kernel: [__do_IRQ+138/256] __do_IRQ+0x8a/0x100
Dec 18 10:47:57 hive kernel: [do_IRQ+55/112] do_IRQ+0x37/0x70
Dec 18 10:47:57 hive kernel: [evtchn_do_upcall+146/256]
evtchn_do_upcall+0x92/0x100
Dec 18 10:47:57 hive kernel: [hypervisor_callback+61/72]
hypervisor_callback+0x3d/0x48
Dec 18 10:47:57 hive kernel: [safe_halt+32/80] safe_halt+0x20/0x50
Dec 18 10:47:57 hive kernel: [start_hz_timer+18/32] start_hz_timer
+0x12/0x20
Dec 18 10:47:57 hive kernel: [xen_idle+44/96] xen_idle+0x2c/0x60
Dec 18 10:47:57 hive kernel: [cpu_idle+139/224] cpu_idle+0x8b/0xe0
Dec 18 10:47:57 hive kernel: [start_kernel+427/496] start_kernel
+0x1ab/0x1f0
Dec 18 10:47:57 hive kernel: [unknown_bootoption+0/480]
unknown_bootoption+0x0/0x1e0
"""
I needed to force my machine to reboot physically. Any suggestions are
very welcome.
(Ubuntu 6.10 - dom0 & domU - and Xen-3.0.3 binary install with Kodicom
4400R-like bt878 based DVR card)
Should you need more info on my setup, I'm happy to provide you with
that.
Frank
next prev parent reply other threads:[~2006-12-18 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 21:05 bt878 based dvr card vs. pci pass-thru Sipos Ferenc
2006-12-18 9:09 ` Keir Fraser
2006-12-18 9:56 ` Sipos Ferenc [this message]
2006-12-20 14:42 ` [Xen-users] " Chris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1166435766.4291.58.camel@cage \
--to=frank@sudo.hu \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.