RE: Recent Changes to Rum driver - seems to have..
I am sure you're right Andrew I would not have expected the change unless there was a good reason for it - I find some time to do some testing and give feedback -Original Message- From: Andrew Thompson [mailto:thom...@freebsd.org] Sent: 12 February 2009 04:24 To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org; Thomas Sparrevohn Subject: Re: Recent Changes to Rum driver - seems to have.. On Wed, Feb 11, 2009 at 10:00:45AM +0100, Hans Petter Selasky wrote: On Tuesday 10 February 2009, Thomas Sparrevohn wrote: Reintroduced panics when the device is used heavily - it also reports the needs callback in dmesg - Unless this is known I can post a dmesg Hi Thomas, Andrew Thompson decided to re-port the driver from USB1. I've tried to fix most of the bugs now. If the fixes are not in -current yet you can fetch if_rum*[ch] from: svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 Do you have a backtrace of the panics ? Sorry about the inconvenience. Please watch the mud slinging, there were very good reasons for changing the wlan code back to the USB1 state (bugs and all). Each regression will be investigated and fixed. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
RE: Recent Changes to Rum driver - seems to have..
That explains it - Here you go -Original Message- From: Hans Petter Selasky [mailto:hsela...@c2i.net] Sent: 11 February 2009 09:01 To: freebsd-usb@freebsd.org; Andrew Thompson Cc: Thomas Sparrevohn Subject: Re: Recent Changes to Rum driver - seems to have.. On Tuesday 10 February 2009, Thomas Sparrevohn wrote: Reintroduced panics when the device is used heavily - it also reports the needs callback in dmesg - Unless this is known I can post a dmesg Hi Thomas, Andrew Thompson decided to re-port the driver from USB1. I've tried to fix most of the bugs now. If the fixes are not in -current yet you can fetch if_rum*[ch] from: svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 Do you have a backtrace of the panics ? Sorry about the inconvenience. --HPS core.txt.46.bz2 Description: Binary data ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
RE: Recent Changes to Rum driver - seems to have..
Ok will do - Just need to get out of Vista land - so it will take a little while -Original Message- From: Hans Petter Selasky [mailto:hsela...@c2i.net] Sent: 11 February 2009 15:17 To: Thomas Sparrevohn Cc: freebsd-usb@freebsd.org; 'Andrew Thompson' Subject: Re: Recent Changes to Rum driver - seems to have.. Hi Thomas, Thanks for reporting this bug! I've analysed your panic and have made the following patch: http://perforce.freebsd.org/chv.cgi?CH=157544 Accumulated patches are available from my private SVN. I recommend updating all files in the usb2 directory. svn --username anonsvn --password anonsvn \ checkout svn://svn.turbocat.net/i4b/trunk/i4b/src/sys/dev/usb2 --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Recent Changes to Rum driver - seems to have..
Reintroduced panics when the device is used heavily - it also reports the needs callback in dmesg - Unless this is known I can post a dmesg ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: HEADSUP usb2/usb4bsd to become default in GENERIC
On Friday 06 February 2009 15:19:01 M. Warner Losh wrote: Doesn't the busdma issue need to be solved before we do this? usb2 currently doesn't work if you have memory above 4GB due to this issue. I thought we tagged it as a show stopper for making it the default. Warner To be honst - I stongly recommend that it's fixed before. I know the problem is not related to the USB2 stack as such - However the way the problem occurs e.g. a corruption in the ATA dma load make it far from clear that it's a USB bounce buffer problem and my error reports was generally ignored with the - there nothing wrong with the ATA code - quite correctly as it turned out but - it kept me using an old kernel before the old brain got around to thinking about USB So I would love to see it fixed and I am not quite sure what the hold up is? Last time I heard - we seemed to be caugth in between - a double there nothing wrong with the dma code and that is the way USB works ;-) I am sure there is more to it however ;-0) Regards T. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
RE: USB2 patches
Before we switch GENERIC - would it be possibly to have the bus dma issue committed as well? Without the patch manually added none of my umass devices work under amd64 -Original Message- From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On Behalf Of Alfred Perlstein Sent: 01 February 2009 03:06 To: Andrew Thompson Cc: freebsd-usb@freebsd.org Subject: Re: USB2 patches I'll defer to Hans if he feels confident or not about this. For what it's worth, we're about to switch GENERIC to use usb4bsd. -Alfred * Andrew Thompson thom...@freebsd.org [090131 15:20] wrote: Hi, I have several patches in my svn user branch that I would like to see committed to HEAD. Some of these change the usb2 core code so I am interested in feedback or shootdowns. I am right behind the change to USB2 and this is an effort to help. The patch can be found here, http://people.freebsd.org/~thompsa/usb_head1.diff 73 files changed, 9229 insertions(+), 13261 deletions(-) but its rather large so it may be easier to look at the various changes via the svn web interface. http://svn.freebsd.org/viewvc/base/user/thompsa/usb/ r187750 http://svn.freebsd.org/viewvc/base?view=revisionrevision=187750 Change over to using taskqueue(9) instead of hand rolled threads and the config_td system. This removes the config_td code and makes the API much simpler to use. r187751, r187752, r187753, r187754, r187755, r187756 http://svn.freebsd.org/viewvc/base?view=revisionrevision=187751 Change over to usb2_proc w/ taskqueues for the usb2/ethernet, usb2/serial and usb2/wlan code. r187965 http://svn.freebsd.org/viewvc/base?view=revisionrevision=187965 Move most of the ifnet logic into the usb2_ethernet module, this includes, - make all usb ethernet interfaces named ue%d - handle all threading in usb2_ethernet - provide default ioctl handler - handle mbuf rx - provide locked callbacks for init,start,stop,etc The drivers are not much more than data pushers now. regards, Andrew -- - Alfred Perlstein ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Advice on booting from usb2
I have a 4GB SDHC card that I have formatted with ufs and installed a current kernel on - Its connected to a USB reader. Now here is the thing - I can boot the kernel with USB2 well enough but when it comes to mount root - it looks like USB2 has not probed and attached the device yet and I get the mount root from prompt - however it does not show the cam devices Any advice? ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Advice on booting from usb2
On Saturday 10 January 2009 15:23:48 Olivier SMEDTS wrote: The patch works for me and allows me to boot - however eventually I get the usb2_pc_common_mem_cb:429: Page offset was not preserved! Error - I wonder if the error is specific to the Nvidia Nforce 590 Intel chipset or its more generic as but seems to occur quite rarely ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Advice on booting from usb2
On Saturday 10 January 2009 18:40:10 Hans Petter Selasky wrote: It is chipset independent. It appears at the moment data is bounced, because you have too much memory in the computer :-) Currently the USB drivers only supports 32-bits of DMA addressing. --HPS Well I guess its not the worst kind of problem to have ;-) ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB4BSD release candidate number 3 - request for review
On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote: Hi, And one last thing: # usbdevs -v usbdevs: no USB controllers found That command is no longer supported. Use usbconfig instead. I'm not sure if it is currently installed by default. --HPS usbconfig does not install per default - it does not even seem to compile - ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Sunday 26 October 2008 15:33:20 Hans Petter Selasky wrote: What is the device naming change to? Hi, A new USB release is available: http://www.selasky.org/hans_petter/usb4bsd/for_review/ %md5 usb2_release_003.* MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf %sha256 usb2_release_003.* SHA256 (usb2_release_003.diff) = 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b SHA256 (usb2_release_003.tar.gz) = 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 Changes since 002 release: 1) LibUSB20 is now fully documented 2) LibUSB20 is now fully backwards compatible with LibUSB 0.1.12 from /usr/ports/devel/libusb . 3) All Makefiles have a license in them 4) usbconfig now supports dynamic quirks (add, remove and view) 5) All USB modules have been fragmented into smaller parts: ./Makefile ./bluetooth/Makefile ./bluetooth_fw/Makefile ./bluetooth_ng/Makefile ./controller/Makefile ./controller_at91dci/Makefile ./controller_ehci/Makefile ./controller_musb/Makefile ./controller_ohci/Makefile ./controller_uhci/Makefile ./controller_uss820dci/Makefile ./core/Makefile ./ethernet/Makefile ./ethernet_aue/Makefile ./ethernet_axe/Makefile ./ethernet_cdce/Makefile ./ethernet_cue/Makefile ./ethernet_dav/Makefile ./ethernet_kue/Makefile ./ethernet_rue/Makefile ./image/Makefile ./input/Makefile ./input_hid/Makefile ./input_kbd/Makefile ./input_ms/Makefile ./misc/Makefile ./misc_dbp/Makefile ./misc_fm/Makefile ./ndis/Makefile ./quirk/Makefile ./scanner/Makefile ./serial/Makefile ./serial_ark/Makefile ./serial_bsa/Makefile ./serial_bser/Makefile ./serial_chcom/Makefile ./serial_cycom/Makefile ./serial_foma/Makefile ./serial_ftdi/Makefile ./serial_gensa/Makefile ./serial_ipaq/Makefile ./serial_lpt/Makefile ./serial_mct/Makefile ./serial_modem/Makefile ./serial_moscom/Makefile ./serial_plcom/Makefile ./serial_visor/Makefile ./serial_vscom/Makefile ./storage/Makefile ./storage_ata/Makefile ./storage_fs/Makefile ./storage_mass/Makefile ./storage_rio/Makefile ./template/Makefile ./wlan/Makefile ./wlan_ral/Makefile ./wlan_rum/Makefile ./wlan_zyd/Makefile The following file has been deleted: src/sys/dev/usb2/controller/uss820dci_pccard.c --HPS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB4BSD release candidate number 3 - request for review
On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: On Friday 31 October 2008, Olivier SMEDTS wrote: Hello, Each device driver has been splitted since RC3. Look in /boot/kernel/usb2_*. You can use modules. For example, for my usb mouse, I use usb2_input_ums. Hi, Looks like I made a small typo there. The module is named usb2_input_ms while the kernel option is named usb2_input_ums. The kernel option should be named usb2_input_ms. Is this the same issue? config: Error: device usb2_controller_uss820dci is unknown config: Error: device usb2_ethernet_dav is unknown Alfred: Can you fix this before committing? --HPS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Panic with USB2 release candidate
I downloaded the release candidate 2 for the new USB stack and while it work very well for most things I am getting repeated panics when using heavy disk traffic - I believe the issue is related to the problems I described in the out of bounce buffers mail - Yet with the new stack it show up correctly in the USB UMASS dma code as a fault Anyhow its a pretty nasty panic - I have a number of core dumps if its of any use ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Out of bounce buffers
I will be answering this one myself Further debugging seems fortunately to vindicate the ATA drivers - I tried to disable most other drivers - USB, if etc. And the problem goes away I now need to tie down where the problem occurs - but what seems to happen is that a DMA read sanity check fails due to the segment has been overwritten/changed/freed while the ATA driver was holding the same tag -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Sparrevohn Sent: 13 October 2008 22:08 To: 'Søren Schmidt'; [EMAIL PROTECTED] Subject: Out of bounce buffers Hi I have had a weird issue since the change in April where the SATA Port multipliers was introduced. The system started issuing DATA load FAILURE in the ata-dmaload every time that disk subsystem got loaded. Because the code prior from 10/04-2008 worked fine and Ignored the problem and simply used the code prior to the SATA Port multiplier was introduced. The reason was twofold - One I did not time to investigate and two I suspected it could be a hw error - using cheap SATA disks. Well finally I have had time to investigate and the problem occurs because the system runs out of bounce buffers I have tested the entire disk for errors using a Hitachi tools and there seems to no problems - down to the degree that I can get the system to work with the current ATA subsystem as long as I only use one disk ;-) Regardless of which of the 4 disks - however if I add a second disk to the subsystem it will eventually (after 17-40GB of restores) give me a DATA load failures - Naturally I suspected the disk drives - however as I said - I can fully restore without the error occurring as long as I only use one disk Puzzled by this I started plastering the code with printf's to see what happened - patch included just FYI - It turns out that the kernel runs out of bounce buffers - which is very surprising - Can anybody give any advice on this? ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Native USB now works on MCP55 on AMD64
Thanks - Thanks - I am very very pleased to inform you that the MCP55 USB native USB stack now attaches correctly under the AMD64 and all my USB devices seems to work - I believe that I had a GNAT problem report about it that can be closed Thanks a million ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Advise on debugging ohci?
Hi I am currently trying to pin down a problem with the native USB stack on the AMD64 - when I am booting in 64bit mode with the MCP55 USB stack it fails in usb_attach - so far the only clear error I have found is that the first Unit is not found correctly - below is the 32BIT debug output ohci0: OHCI (generic) USB controller mem 0xdfffc000-0xdfffcfff irq 21 at device 11.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdfffc000 ioapic0: routing intpin 21 (PCI IRQ 21) to vector 49 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] ohci_init: start usb0: OHCI version 1.0, legacy support ohci_alloc_sed: allocating chunk ohci_init: SMM active, request owner change usb0: SMM does not respond, resetting usb0: resetting ohci_dumpregs: rev=0x0110 control=0x06bf command=0x intrstat=0x0004 intre=0x804a intrd=0x804a hcca=0x00287000 percur=0x ctrlhd=0x00286fe0 ctrlcur=0x bulkhd=0x00286fc0 bulkcur=0x done=0x fmival=0xa7782edf fmrem=0x80001f8d fmnum=0x0011 perst=0x2a2f lsthrs=0x0628 desca=0x0100120a descb=0x stat=0x port1=0x0100 port2=0x0100 HCCA: frame_number=0x0013 done_head=0x usbd_match usbd_match usb0: OHCI (generic) USB controller on ohci0 usbd_attach usb0: USB revision 1.0 usbd_new_device bus=0xc5b66000 port=0 depth=0 speed=2 ohci_open: pipe=0xc5b5c280, addr=0, endpt=0 (0) ohci_root_ctrl_control type=0x80 request=06 ohci_root_ctrl_control wValue=0x0100 usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=0, protocol=0, maxpacket=64, len=18, speed=2 ohci_root_ctrl_close On the AMD64 version the ohci the usbd_new_device seems to get the wrong information ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] ohci_init: start usb0: OHCI version 1.0, legacy support ohci_alloc_sed: allocating chunk ohci_init: SMM active, request owner change usb0: SMM does not respond, resetting usb0: resetting ohci_dumpregs: rev=0x0110 control=0x06bf command=0x intrstat=0x0004 intre=0x804a intrd=0x804a hcca=0x95853000 percur=0x ctrlhd=0x95852fe0 ctrlcur=0x bulkhd=0x95852fc0 bulkcur=0x done=0x fmival=0xa7782edf fmrem=0x8000207b fmnum=0x0011 perst=0x2a2f lsthrs=0x0628 desca=0x0100120a descb=0x stat=0x port1=0x0100 port2=0x0100 HCCA: frame_number=0x0013 done_head=0x usbd_match usbd_match usb0: OHCI (generic) USB controller on ohci0 usbd_attach usb0: USB revision 1.0 usbd_new_device bus=0x80e48000 port=0 depth=0 speed=2 ohci_open: pipe=0xff015f34b200, addr=0, endpt=0 (0) ohci_root_ctrl_control type=0x80 request=06 ohci_root_ctrl_control wValue=0x0100 usbd_new_device: adding unit addr=1, rev=00, class=0, subclass=0, protocol=0, maxpacket=0, len=0, speed=2 usbd_new_device: illegal descriptor 0 usbd_remove_device: 0xff015f34b300 ohci_root_ctrl_close When I compile with DIAGNOSTICS enabled on the amd64 - The system panics with No data or something like that at that point - does anybody have any suggestions? - With the HPS stack everything works fine - so its not the devices Regards Thomas ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: USB fails to attach in the SMP version of GENERIC with Nforce 590
Yes - I am always normally running CURRENT - It was when I couldn't get USB to work I tried with the 6.2 Image I had installed from and was surprised to discover it worked Under 6.2 - but then I discovered that SMP wasn't enabled -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Baldwin Sent: 20 February 2007 16:47 To: [EMAIL PROTECTED] Cc: Thomas Sparrevohn; freebsd-usb@freebsd.org Subject: Re: USB fails to attach in the SMP version of GENERIC with Nforce 590 On Saturday 17 February 2007 16:34, Thomas Sparrevohn wrote: HI Its a bit of a weird problem - If I boot the 6.2 RELEASE UP kernel - all USB devices works fine however it I boot with the most recent (cvsup today) - It fails attaching the root device. The only major difference are that the 6.2-RELEASE looks like its a UP kernel or at least it never starts the 3 other cores Well, you cvsupp'ed current (7.0) not 6.x-stable, was that on purpose? It does look like the uhub(4) driver is what is keeling over. -- John Baldwin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: amd64/109274: MCP55 USB Controller fails to attach in AMD64 Current SMP Kernel
The following reply was made to PR usb/109274; it has been noted by GNATS. From: Thomas Sparrevohn [EMAIL PROTECTED] To: 'John Baldwin' [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: amd64/109274: MCP55 USB Controller fails to attach in AMD64 Current SMP Kernel Date: Tue, 20 Feb 2007 18:39:15 - That what I did and USB does not work under SMP AMD64 with this chipset - I did send a mail to that effect on both Mailing lists including dmesg etc. -Original Message- From: John Baldwin [mailto:[EMAIL PROTECTED] Sent: 20 February 2007 16:48 To: [EMAIL PROTECTED] Cc: Thomas Sparrevohn; [EMAIL PROTECTED] Subject: Re: amd64/109274: MCP55 USB Controller fails to attach in AMD64 Current SMP Kernel On Sunday 18 February 2007 07:39, Thomas Sparrevohn wrote: Number: 109274 Category: amd64 Synopsis: MCP55 USB Controller fails to attach in AMD64 Current SMP Kernel Confidential: no Severity: critical Priority: high Responsible:freebsd-amd64 State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Sun Feb 18 12:40:06 GMT 2007 Closed-Date: Last-Modified: Originator: Thomas Sparrevohn Release:AMD64 Current (cvsup 17/02) Organization: Environment: Description: The USB MCP55 Controller fails to attach in AMD64 Current leaving no keyboards working etc. How-To-Repeat: Boot the system in AMD64 Mode - I have pciconf/devinfo dumps available Fix: Reverting to 6.2 RELEASE works - however that means that the system does not run in SMP Dude, just build an SMP kernel on 6.2. SMP isn't enabled in GENERIC on 6.x by default. -- John Baldwin ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: amd64/109274: MCP55 USB Controller fails to attach in AMD64 Current SMP Kernel
The following reply was made to PR usb/109274; it has been noted by GNATS. From: Thomas Sparrevohn [EMAIL PROTECTED] To: 'John Baldwin' [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: amd64/109274: MCP55 USB Controller fails to attach in AMD64 Current SMP Kernel Date: Tue, 20 Feb 2007 18:39:51 - By the way I am using CURRENT -Original Message- From: John Baldwin [mailto:[EMAIL PROTECTED] Sent: 20 February 2007 16:48 To: [EMAIL PROTECTED] Cc: Thomas Sparrevohn; [EMAIL PROTECTED] Subject: Re: amd64/109274: MCP55 USB Controller fails to attach in AMD64 Current SMP Kernel On Sunday 18 February 2007 07:39, Thomas Sparrevohn wrote: Number: 109274 Category: amd64 Synopsis: MCP55 USB Controller fails to attach in AMD64 Current SMP Kernel Confidential: no Severity: critical Priority: high Responsible:freebsd-amd64 State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Sun Feb 18 12:40:06 GMT 2007 Closed-Date: Last-Modified: Originator: Thomas Sparrevohn Release:AMD64 Current (cvsup 17/02) Organization: Environment: Description: The USB MCP55 Controller fails to attach in AMD64 Current leaving no keyboards working etc. How-To-Repeat: Boot the system in AMD64 Mode - I have pciconf/devinfo dumps available Fix: Reverting to 6.2 RELEASE works - however that means that the system does not run in SMP Dude, just build an SMP kernel on 6.2. SMP isn't enabled in GENERIC on 6.x by default. -- John Baldwin ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB fails to attach in the SMP version of GENERIC with Nforce 590
On 20 Feb 2007, at 21:12, John Baldwin wrote: On Tuesday 20 February 2007 13:42, Thomas Sparrevohn wrote: Yes - I am always normally running CURRENT - It was when I couldn't get USB to work I tried with the 6.2 Image I had installed from and was surprised to discover it worked Under 6.2 - but then I discovered that SMP wasn't enabled So what I see from your e-mail is that a 6.2 UP kernel works fine (but no SMP), and a 7.0 SMP kernel breaks, but you want SMP. Have you tried a 6.2 SMP kernel? I imagine that is going to work fine. You have way too many variables here. The USB breakage could be due to SMP vs UP (I doubt it) or due to 6.2 vs 7.0 (more likely). Well not really that many variables - as the DVD Drives does not work with 6.2.0-RELEASE and they do with Sorens latest changes and was ever only really concerned about CURRENT. But anyhow - I just tested with a 6.2.0-RELEASE SMP kernel and as you suspected it works fine meaning that we back at the fact that CURRENT does have a problem (Only tested with GENERIC). I am going to test with CURRENT and the new USB stack and feedback the results - Werner Losh had experienced problems that looked the same on a Dell Laptop - so maybe its specific to Dell - I don't really know - but that it works with 6.2 only seems to state that it is not inherent Regards Thomas ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
