WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] pciback for usb-controller and usb-storage on x86_64ends

To: "Patrick Scharrenberg" <pittipatti@xxxxxx>, "Xen-Devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] pciback for usb-controller and usb-storage on x86_64ends in Oops
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 1 Nov 2006 19:25:41 -0000
Delivery-date: Thu, 02 Nov 2006 13:40:21 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4548F353.1000604@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acb96vfl5l3lA6JbQIuKvYw0pDp95QAAFvgQ
Thread-topic: [Xen-devel] pciback for usb-controller and usb-storage on x86_64ends in Oops
> I tried to pcipassthrough usb-controllers to domu to use it with a
> memory-stick.
> 
> First xen complained that the driver needs write-access to its
> configuration space, so I added these to pci-quirks.
> Since it still didn't work I also added the device to pci-permissive
but
> I still get an errormessage with Oops (at the end of this email) when
> sticking in the memory-stick.
> 
> I tried xen-3.0.3 and latest unstable (12053:874cc0ff214d).
> I use the fedora 2.6.18.1-xen0 since otherwise my sata-controller is
not
> detected.
> 
> What can I do?

Have you made sure the device is hidden from dom0? Having two drivers
going at it would be bad...

Ian

 
> Patrick
> 
> lspci:
> 00:10.0 0c03: 1106:3038 (rev a0) (prog-if 00 [UHCI])
>         Subsystem: 1462:7253
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64, Cache Line Size: 32 bytes
>         Interrupt: pin A routed to IRQ 21
>         Region 4: I/O ports at f900 [size=32]
>         Capabilities: [80] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:10.1 0c03: 1106:3038 (rev a0) (prog-if 00 [UHCI])
>         Subsystem: 1462:7253
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64, Cache Line Size: 32 bytes
>         Interrupt: pin B routed to IRQ 22
>         Region 4: I/O ports at f800 [size=32]
>         Capabilities: [80] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:10.2 0c03: 1106:3038 (rev a0) (prog-if 00 [UHCI])
>         Subsystem: 1462:7253
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64, Cache Line Size: 32 bytes
>         Interrupt: pin C routed to IRQ 20
>         Region 4: I/O ports at f700 [size=32]
>         Capabilities: [80] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:10.3 0c03: 1106:3038 (rev a0) (prog-if 00 [UHCI])
>         Subsystem: 1462:7253
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64, Cache Line Size: 32 bytes
>         Interrupt: pin D routed to IRQ 19
>         Region 4: I/O ports at f600 [size=32]
>         Capabilities: [80] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 00:10.4 0c03: 1106:3104 (rev 86) (prog-if 20 [EHCI])
>         Subsystem: 1462:7253
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64, Cache Line Size: 32 bytes
>         Interrupt: pin C routed to IRQ 5
>         Region 0: Memory at dffff000 (32-bit, non-prefetchable)
[size=256]
>         Capabilities: [80] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 
> Errormessage:
> 
> 
> usb usb3: wakeup_rh (auto-start)
> hub 3-0:1.0: state 7 ports 2 chg 0000 evt 0002
> uhci_hcd 0000:00:10.2: port 1 portsc 0093,00
> hub 3-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
> hub 3-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
> usb 3-1: new full speed USB device using uhci_hcd and address 2
> usb 3-1: default language 0x0409
> usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=3
> usb 3-1: Product: USB Mass Storage Device
> usb 3-1: Manufacturer: USBest Technology
> usb 3-1: SerialNumber: 551114559c3fc7
> usb 3-1: uevent
> usb 3-1: configuration #1 chosen from 1 choice
> usb 3-1: adding 3-1:1.0 (config #1, interface 0)
> usb 3-1:1.0: uevent
> libusual 3-1:1.0: usb_probe_interface
> libusual 3-1:1.0: usb_probe_interface - got id
> drivers/usb/core/inode.c: creating file '002'
> Initializing USB Mass Storage driver...
> usb-storage 3-1:1.0: usb_probe_interface
> usb-storage 3-1:1.0: usb_probe_interface - got id
> usb-storage: USB Mass Storage device detected
> usb-storage: -- associate_dev
> usb-storage: Vendor: 0x0457, Product: 0x0150, Revision: 0x0100
> usb-storage: Interface Subclass: 0x06, Protocol: 0x50
> usb-storage: Transport: Bulk
> usb-storage: Protocol: Transparent SCSI
> scsi0 : SCSI emulation for USB Mass Storage devices
> usb-storage: *** thread sleeping.
> usbcore: registered new driver usb-storage
> USB Mass Storage support registered.
> usb-storage: device found at 2
> usb-storage: waiting for device to settle before scanning
> usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value=0000 index=00
> len=1
> usb-storage: GetMaxLUN command result is 1, data is 0
> Unable to handle kernel NULL pointer dereference at 0000000000000078
RIP:
>  [<ffffffff804a3929>] scsi_calculate_bounce_limit+0x19/0x60
> PGD 7d6c067 PUD 7c53067 PMD 0
> Oops: 0000 [1]
> CPU 0
> Modules linked in: usb_storage uhci_hcd
> Pid: 2017, comm: usb-stor-scan Not tainted 2.6.18.1-xen0 #7
> RIP: e030:[<ffffffff804a3929>]  [<ffffffff804a3929>]
> scsi_calculate_bounce_limit+0x19/0x60
> RSP: e02b:ffff880006ddbc20  EFLAGS: 00010246
> RAX: 0000000000000000 RBX: ffff880007e0c188 RCX: 0000000000000067
> RDX: 0000000000000071 RSI: 00000000000000f0 RDI: ffff8800083a2800
> RBP: ffff880006ddbc20 R08: ffff880007e35000 R09: 000000000000000d
> R10: ffff8800000caec0 R11: 00000000000001a0 R12: ffff8800083a2800
> R13: ffff880007139028 R14: ffff8800083a2800 R15: 0000000000000000
> FS:  00002aebaf08cae0(0000) GS:ffffffff80757000(0000)
> knlGS:0000000000000000
> CS:  e033 DS: 0000 ES: 0000
> Process usb-stor-scan (pid: 2017, threadinfo ffff880006dda000, task
> ffff880007d35610)
> Stack:  ffff880006ddbc40  ffffffff804a412a  ffff8800080e0800
> ffff880007139000
>  ffff880006ddbc80  ffffffff804a5fc6  ffff880006ddbc80
ffff8800083a2800
>  0000000000000000  0000000000000000
> Call Trace:
>  [<ffffffff804a412a>] scsi_alloc_queue+0x6a/0xc0
>  [<ffffffff804a5fc6>] scsi_alloc_sdev+0x126/0x1e0
>  [<ffffffff804a6192>] scsi_probe_and_add_lun+0xe2/0x8f0
>  [<ffffffff804a6fd2>] __scsi_scan_target+0xd2/0x5b0
>  [<ffffffff80233990>] process_timeout+0x0/0x10
>  [<ffffffff8023e360>] keventd_create_kthread+0x0/0x70
>  [<ffffffff8022b6e7>] printk+0x67/0x70
>  [<ffffffff804a7515>] scsi_scan_channel+0x65/0xa0
>  [<ffffffff804a75e6>] scsi_scan_host_selected+0x96/0xe0
>  [<ffffffff8023e360>] keventd_create_kthread+0x0/0x70
>  [<ffffffff804a7645>] scsi_scan_host+0x15/0x20
>  [<ffffffff8800c53a>] :usb_storage:usb_stor_scan_thread+0x17a/0x19e
>  [<ffffffff8023e790>] autoremove_wake_function+0x0/0x40
>  [<ffffffff8800c3c0>] :usb_storage:usb_stor_scan_thread+0x0/0x19e
>  [<ffffffff8023e4a9>] kthread+0xd9/0x110
>  [<ffffffff8020a814>] child_rip+0xa/0x12
>  [<ffffffff8023e360>] keventd_create_kthread+0x0/0x70
>  [<ffffffff8023e3d0>] kthread+0x0/0x110
>  [<ffffffff8020a80a>] child_rip+0x0/0x12
> 
> 
> Code: 8b 40 78 85 c0 75 10 48 8b 05 51 31 34 00 48 c1 e0 0c eb 25
> RIP  [<ffffffff804a3929>] scsi_calculate_bounce_limit+0x19/0x60
>  RSP <ffff880006ddbc20>
> CR2: 0000000000000078
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>