Re: Problem with memory stick
On Sat, February 4, 2006 3:45 am, Stephen Montgomery-Smith wrote: I have a Crucial 1GB USB 2.0 Gizmo memory stick. It does work, but not without its problems. When I insert it into the USB port, the kernel spits out a large number of bad looking messages - I'll copy them below. /dev/da0 is created, but no /dev/da0s1 is created. If I then do mount_msdos /dev/da0 /mnt it gives an appropriate error message, but then /dev/da0s1 is mysteriously created. At this point mount_msdos /dev/da0s1 /mnt works just right, and it is ready to use. I just get the feeling that it is not quite working how it should be. I am using a fairly recent RELENG_6 (maybe two weeks old). Check your kernel, maybe you are using the ehci driver for USB 2.0 support, which is under development and buggy. Also take a look at ehci(4). -- Giorgos Kapetanakis ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with memory stick
Giorgos Kapetanakis wrote: On Sat, February 4, 2006 3:45 am, Stephen Montgomery-Smith wrote: I have a Crucial 1GB USB 2.0 Gizmo memory stick. It does work, but not without its problems. When I insert it into the USB port, the kernel spits out a large number of bad looking messages - I'll copy them below. /dev/da0 is created, but no /dev/da0s1 is created. If I then do mount_msdos /dev/da0 /mnt it gives an appropriate error message, but then /dev/da0s1 is mysteriously created. At this point mount_msdos /dev/da0s1 /mnt works just right, and it is ready to use. I just get the feeling that it is not quite working how it should be. I am using a fairly recent RELENG_6 (maybe two weeks old). Check your kernel, maybe you are using the ehci driver for USB 2.0 support, which is under development and buggy. Also take a look at ehci(4). I was. But when I added nodevice ehci to my kernel, the memory stick still malfunctioned in exactly the same way. Here is my kernel and dmesg. include GENERIC ident LAPTOP2 nooption INET6 device atapicam nodeviceehci Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-STABLE #1: Sat Feb 4 11:51:18 CST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP2 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1.70GHz (1698.56-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6d6 Stepping = 6 Features=0xafe9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE Features2=0x180EST,TM2 real memory = 536535040 (511 MB) avail memory = 511483904 (487 MB) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL CPi R on motherboard Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_acad0: AC Adapter on acpi0 battery0: ACPI Control Method Battery on acpi0 battery1: ACPI Control Method Battery on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci_link1: BIOS IRQ 11 for 0.31.INTB is invalid pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 nvidia0: GeForce FX Go5200 mem 0xfc00-0xfcff,0xd000-0xdfff irq 11 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xbf80-0xbf9f irq 11 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xbf40-0xbf5f irq 11 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xbf20-0xbf3f irq 11 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 29.7 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci_link1: BIOS IRQ 11 for 2.3.INTA is invalid pci2: ACPI PCI bus on pcib2 bge0: Broadcom BCM5705M Gigabit Ethernet, ASIC rev. 0x3001 mem 0xfaff-0xfaff irq 11 at device 0.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5705 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:0f:1f:21:d5:92 cbb0: PCI-CardBus Bridge at device 1.0 on pci2 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: PCI-CardBus Bridge irq 11 at device 1.1 on pci2 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 fwohci0: 1394 Open Host Controller Interface mem 0xfafef800-0xfafe,0xfafe8000-0xfafebfff irq 11 at device 1.2 on pci2 fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 48:4f:c0:00:36:a9:44:a1 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 4a:4f:c0:a9:44:a1 fwe0: Ethernet address: 4a:4f:c0:a9:44:a1 fwe0: if_start running deferred for Giant sbp0: SBP-2/SCSI over FireWire on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1
Problem with memory stick
I have a Crucial 1GB USB 2.0 Gizmo memory stick. It does work, but not without its problems. When I insert it into the USB port, the kernel spits out a large number of bad looking messages - I'll copy them below. /dev/da0 is created, but no /dev/da0s1 is created. If I then do mount_msdos /dev/da0 /mnt it gives an appropriate error message, but then /dev/da0s1 is mysteriously created. At this point mount_msdos /dev/da0s1 /mnt works just right, and it is ready to use. I just get the feeling that it is not quite working how it should be. I am using a fairly recent RELENG_6 (maybe two weeks old). Here are the messages from dmesg. umass0: USB Flash Disk, rev 2.00/2.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: CRUCIAL USB Flash Disk 2.00 Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: UNIT ATTENTION, Not ready to ready change, (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retries Exhausted Opened disk da0 - 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retries Exhausted Opened disk da0 - 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition