Re: Hangup on USB mass device
According to the file /usr/src/sys/dev/usb/usbdevs on my 7-STABLE system, this is a C-700 camera, which should be recognized. Actually it a C-310 but maybe the drive can handle both models? Apr 23 22:17:48 mellba kernel: umass2: OLYMPUS X100,D540Z,C310Z, class 0/0, rev 2.00/1.00, addr 2 on uhub0 And it does not seem to be recognized properly. So My USB device has been seen and then nothing until the first message of the next boot OK, so it goes wrong before the usb subsystem hands the camera off as a da device. This is uhub0, so it's recognized as a USB 1.0 device. Is it USB 2.0 capable Is the mp3 player a usb 1.0 device as well? In that case the trouble is probably with the ohci driver, since the USB 2.0 devices seem to work well. Both of them are USB 2,0 capable devices (according to manufactor AND I test them under windows, they are recognized as usb 2.0 devices with Hi speed. On 7.x you should have /boot/kernel/kernel.symbols, which is the debugging kernel (/boot/kernel/kernel is the regular, stripped, kernel). Ok here is what I get (I have 3 dumps and all give the same results): Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0x0 stack pointer = 0x28:0xe4ab369c frame pointer = 0x28:0xe4ab36dc code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock sio) trap number = 12 panic: page fault cpuid = 0 Uptime: 34m10s Physical memory: 1003 MB Dumping 180 MB: 165 149 133 117 101 85 69 53 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 37 21 5 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h There should be a space between no and . I could have guessed this one :-) Sebastien ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hangup on USB mass device
On Fri, Apr 25, 2008 at 07:57:42AM +, Sébastien Morand wrote: OK, so it goes wrong before the usb subsystem hands the camera off as a da device. This is uhub0, so it's recognized as a USB 1.0 device. Is it USB 2.0 capable Is the mp3 player a usb 1.0 device as well? In that case the trouble is probably with the ohci driver, since the USB 2.0 devices seem to work well. Both of them are USB 2,0 capable devices (according to manufactor AND I test them under windows, they are recognized as usb 2.0 devices with Hi speed. On 7.x you should have /boot/kernel/kernel.symbols, which is the debugging kernel (/boot/kernel/kernel is the regular, stripped, kernel). Ok here is what I get (I have 3 dumps and all give the same results): Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code= supervisor read, page not present instruction pointer = 0x20:0x0 stack pointer = 0x28:0xe4ab369c frame pointer = 0x28:0xe4ab36dc code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock sio) trap number = 12 panic: page fault cpuid = 0 Uptime: 34m10s Physical memory: 1003 MB Dumping 180 MB: 165 149 133 117 101 85 69 53 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 37 21 5 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h At this point, you should give the command 'bt' (for backtrace) and report its output. There seem to be several people who have similar problems lately. Maybe you should report it to the -usb list as well. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpwQHreVBEOJ.pgp Description: PGP signature
Re: Hangup on USB mass device
On Wed, Apr 23, 2008 at 10:39:19PM +, Sébastien Morand wrote:
What kind of USB chip do you have on the motherboard? Try 'dmesg | grep
^usb' and post the output.
$ dmesg | grep usb
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: OHCI (generic) USB controller on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0
usb1: waiting for BIOS to give up control
usb1: timed out waiting for BIOS
usb1: EHCI version 1.0
usb1: companion controller, 4 ports each: usb0
usb1: NVIDIA nForce4 USB 2.0 controller on ehci0
usb1: USB revision 2.0
uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb1
It could be a hardware problem, or a bug.
Hardware is fine under linux (same machine) or windows on my wife's laptop (no
pb with the USB devices), so I don't think so.
Does anything appear in the dmesg output when you try to plug in a USB
device? look in /var/log/messages, at the correct time.
E.g, the following appears when I plug in a USB flash drive;
I get this:
Apr 23 22:17:48 mellba root: Unknown USB device: vendor 0x07b4 product 0x0105
bus uhub0
According to the file /usr/src/sys/dev/usb/usbdevs on my 7-STABLE
system, this is a C-700 camera, which should be recognized.
Apr 23 22:17:48 mellba kernel: umass2: OLYMPUS X100,D540Z,C310Z, class 0/0,
rev
2.00/1.00, addr 2 on uhub0
And it does not seem to be recognized properly.
So My USB device has been seen and then nothing until the first message of the
next boot
OK, so it goes wrong before the usb subsystem hands the camera off as a
da device.
This is uhub0, so it's recognized as a USB 1.0 device. Is it USB 2.0 capable
Actually it's quite funny because I have a hard disk on my da0 which
is working fine:
da0 at umass-sim0 bus 0 target 0 lun 0
da0: WD 2500JB External 0108 Fixed Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C)
GEOM_LABEL: Label for provider da0s1 is msdosfs/My Book.
From the transfer rate I infer that this is a USB 2.0 device. It should
be connected to uhub1.
User sebastien is a member if wheel, so hot plug should be working (and it
is with my usb key and my usb hard disk ... it's only my mp3 player and my
camera which make my pc hanging up).
Is the mp3 player a usb 1.0 device as well? In that case the trouble is
probably with the ohci driver, since the USB 2.0 devices seem to work well.
I try do disable both these services and the result is the same.
Seeing which of these lines appear or not makes it easier to track down
the bug.
Try to read the crashdump with the kernel debugger, as described in
§10.2 of the FreeBSD Developers' Handbook. Obtain a so-called
backtrace. (using the 'bt' command in the debugger).
I can't do that. It required a built kernel, didn't it?
The handbook said to launch:
# cd /usr/obj/usr/src/sys/GENERIC
# kgdb kernel.debug /var/crash/vmcore.0
But ... I don't have this directory since I don't compile my kernel, so Itry
to
On 7.x you should have /boot/kernel/kernel.symbols, which is the
debugging kernel (/boot/kernel/kernel is the regular, stripped, kernel).
compile the generic kernel:
Here is what I read trying to build the generic kernel:
=== [23\04\2008 22:09:14] [EMAIL PROTECTED]:/usr/src
# make buildkernel KERNCONF=GENERIC
Makefile.inc1, line 1034: Malformed conditional (${MK_LIBTHR} != no
${MK_LIBKSE} != no)
There should be a space between no and .
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpN8Q8jBfE0P.pgp
Description: PGP signature
Re: Hangup on USB mass device
In the future, please don't reply on top, but on the bottom of the original.
No problem
The default location is /var/crash. Look for files named vmcore.N, where
N is a number.
Yes there is.
What kind of USB chip do you have on the motherboard? Try 'dmesg | grep
^usb' and post the output.
$ dmesg | grep usb
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: OHCI (generic) USB controller on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0
usb1: waiting for BIOS to give up control
usb1: timed out waiting for BIOS
usb1: EHCI version 1.0
usb1: companion controller, 4 ports each: usb0
usb1: NVIDIA nForce4 USB 2.0 controller on ehci0
usb1: USB revision 2.0
uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb1
It could be a hardware problem, or a bug.
Hardware is fine under linux (same machine) or windows on my wife's laptop (no
pb with the USB devices), so I don't think so.
Does anything appear in the dmesg output when you try to plug in a USB
device? look in /var/log/messages, at the correct time.
E.g, the following appears when I plug in a USB flash drive;
I get this:
Apr 23 22:17:48 mellba root: Unknown USB device: vendor 0x07b4 product 0x0105
bus uhub0
Apr 23 22:17:48 mellba kernel: umass2: OLYMPUS X100,D540Z,C310Z, class 0/0, rev
2.00/1.00, addr 2 on uhub0
Apr 23 22:19:53 mellba syslogd: kernel boot file is /boot/kernel/kernel
Apr 23 22:19:53 mellba kernel: Copyright (c) 1992-2008 The FreeBSD Project.
Apr 23 22:19:53 mellba kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989,
1991, 1992, 1993, 1994
Apr 23 22:19:53 mellba kernel: The Regents of the University of California. All
rights reserved.
Apr 23 22:19:53 mellba kernel: FreeBSD is a registered trademark of The FreeBSD
Foundation.
Apr 23 22:19:53 mellba kernel: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC
2008
So My USB device has been seen and then nothing until the first message of the
next boot
Apr 22 18:24:45 slackbox kernel: umass0: vendor 0x3538 USB Mass Storage Device,
class 0/0, rev 2.00/1.00, addr 2 on uhub4
Apr 22 18:24:45 slackbox kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Apr 22 18:24:45 slackbox kernel: da0: Generic USB Flash Disk 0.00 Removable Direct Access SCSI-2 device
Apr 22 18:24:45 slackbox kernel: da0: 40.000MB/s transfers
Apr 22 18:24:45 slackbox kernel: da0: 250MB (512000 512 byte sectors: 64H 32S/T
250C)
Actually it's quite funny because I have a hard disk on my da0 which is working
fine:
da0 at umass-sim0 bus 0 target 0 lun 0
da0: WD 2500JB External 0108 Fixed Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C)
GEOM_LABEL: Label for provider da0s1 is msdosfs/My Book.
It's plugged at boot time.
I'm just thinking that I forget mention some stuff ...
I activated the hot plug using hald et dbus (using xfce4):
Here is my PolicyKit.conf I modified for my need:
$ more PolicyKit.conf
?xml version=1.0 encoding=UTF-8? !-- -*- XML -*- --
!DOCTYPE pkconfig PUBLIC -//freedesktop//DTD PolicyKit Configuration 1.0//EN
http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd;
!-- See the manual page PolicyKit.conf(5) for file format --
config version=0.1
match user=root
return result=yes/
/match
define_admin_auth group=wheel/
match action=org.freedesktop.hal.storage.mount-removable
match user=sebastien
return result=yes/
/match
/match
match action=org.freedesktop.hal.storage.mount-fixed
match user=sebastien
return result=yes/
/match
/match
/config
User sebastien is a member if wheel, so hot plug should be working (and it is
with my usb key and my usb hard disk ... it's only my mp3 player and my camera
which make my pc hanging up).
I try do disable both these services and the result is the same.
Seeing which of these lines appear or not makes it easier to track down
the bug.
Try to read the crashdump with the kernel debugger, as described in
§10.2 of the FreeBSD Developers' Handbook. Obtain a so-called
backtrace. (using the 'bt' command in the debugger).
I can't do that. It required a built kernel, didn't it?
The handbook said to launch:
# cd /usr/obj/usr/src/sys/GENERIC
# kgdb kernel.debug /var/crash/vmcore.0
But ... I don't have this directory since I don't compile my kernel, so Itry to
compile the generic kernel:
Here is what I read trying to build the generic kernel:
=== [23\04\2008 22:09:14] [EMAIL PROTECTED]:/usr/src
# make buildkernel KERNCONF=GENERIC
Makefile.inc1, line 1034: Malformed conditional (${MK_LIBTHR} != no
${MK_LIBKSE} != no)
Makefile.inc1, line 1036: if-less elif
Makefile.inc1, line 1038: if-less elif
Makefile.inc1, line 1040: if-less endif
make: fatal errors encountered -- cannot continue
Post your question and the information that you've gathered to the
-stable mailing list. There are more people there who are
Hangup on USB mass device
Hi everybody, I have a problem with some usb mass devices. Camera or music player make my system hang up whenever I plug then in one of my USB ports? What is the problem? Thanks by advance for you help. Sebastien ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hangup on USB mass device
On Tue, Apr 22, 2008 at 07:33:57AM +, Sébastien Morand wrote: Hi everybody, I have a problem with some usb mass devices. Camera or music player make my system hang up whenever I plug then in one of my USB ports? What is the problem? That is impossible to tell with the limited amount of information you provide. Which version of FreeBSD are you using? On what kind of hardware? Is a crashdump available? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpdCaFZdxMJ0.pgp Description: PGP signature
Re: Hangup on USB mass device
Hi, thanks for the answer, I'm sorry for the little information I send. FreeBSD 7.0-STABLE kernel GENERIC on i386. I don't see anything in the message, but I'm not sure where to look at for crashdump. My computer is either hanging up for ever, I can't move mouse or use keyboard anymore, juste reset, or hang up a few seconds and reboot by it self. Sébastien On Tue, Apr 22, 2008 at 3:34 PM, Roland Smith [EMAIL PROTECTED] wrote: On Tue, Apr 22, 2008 at 07:33:57AM +, Sébastien Morand wrote: Hi everybody, I have a problem with some usb mass devices. Camera or music player make my system hang up whenever I plug then in one of my USB ports? What is the problem? That is impossible to tell with the limited amount of information you provide. Which version of FreeBSD are you using? On what kind of hardware? Is a crashdump available? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hangup on USB mass device
--On Tuesday, April 22, 2008 15:42:47 + Sébastien Morand [EMAIL PROTECTED] wrote: Hi, thanks for the answer, I'm sorry for the little information I send. FreeBSD 7.0-STABLE kernel GENERIC on i386. I don't see anything in the message, but I'm not sure where to look at for crashdump. My computer is either hanging up for ever, I can't move mouse or use keyboard anymore, juste reset, or hang up a few seconds and reboot by it self. Please don't top post. I too am having a problem with umass on 7.0-STABLE. Not quite the same as yours, but similar. During reboots, the umass device cases the kernel to core dump and the system reboots. If I unplug the drive and wait for the system to come up to a login prompt, I can login, plug in the drive, watch it's detection and then mount it with no problem. Dont' know what the problem is, but other problems with umass have been reported on the STABLE list as well. I've recompiled my kernel six times now. The umass device has gone from unmountable to stable in the OS but still fails during boot. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hangup on USB mass device
On Tue, Apr 22, 2008 at 03:42:47PM +, Sébastien Morand wrote: Hi, thanks for the answer, I'm sorry for the little information I send. In the future, please don't reply on top, but on the bottom of the original. FreeBSD 7.0-STABLE kernel GENERIC on i386. I don't see anything in the message, but I'm not sure where to look at for crashdump. The default location is /var/crash. Look for files named vmcore.N, where N is a number. What kind of USB chip do you have on the motherboard? Try 'dmesg | grep ^usb' and post the output. My computer is either hanging up for ever, I can't move mouse or use keyboard anymore, juste reset, or hang up a few seconds and reboot by it self. It could be a hardware problem, or a bug. Does anything appear in the dmesg output when you try to plug in a USB device? look in /var/log/messages, at the correct time. E.g, the following appears when I plug in a USB flash drive; Apr 22 18:24:45 slackbox kernel: umass0: vendor 0x3538 USB Mass Storage Device, class 0/0, rev 2.00/1.00, addr 2 on uhub4 Apr 22 18:24:45 slackbox kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Apr 22 18:24:45 slackbox kernel: da0: Generic USB Flash Disk 0.00 Removable Direct Access SCSI-2 device Apr 22 18:24:45 slackbox kernel: da0: 40.000MB/s transfers Apr 22 18:24:45 slackbox kernel: da0: 250MB (512000 512 byte sectors: 64H 32S/T 250C) Seeing which of these lines appear or not makes it easier to track down the bug. Try to read the crashdump with the kernel debugger, as described in §10.2 of the FreeBSD Developers' Handbook. Obtain a so-called backtrace. (using the 'bt' command in the debugger). Post your question and the information that you've gathered to the -stable mailing list. There are more people there who are familiar with the kernel internals. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpGYFriyg3Xp.pgp Description: PGP signature
Re: Hangup on USB mass device
Paul Schmehl wrote: --On Tuesday, April 22, 2008 15:42:47 + Sébastien Morand [EMAIL PROTECTED] wrote: Hi, thanks for the answer, I'm sorry for the little information I send. FreeBSD 7.0-STABLE kernel GENERIC on i386. I don't see anything in the message, but I'm not sure where to look at for crashdump. My computer is either hanging up for ever, I can't move mouse or use keyboard anymore, juste reset, or hang up a few seconds and reboot by it self. Please don't top post. I too am having a problem with umass on 7.0-STABLE. Not quite the same as yours, but similar. During reboots, the umass device cases the kernel to core dump and the system reboots. If I unplug the drive and wait for the system to come up to a login prompt, I can login, plug in the drive, watch it's detection and then mount it with no problem. Dont' know what the problem is, but other problems with umass have been reported on the STABLE list as well. I've recompiled my kernel six times now. The umass device has gone from unmountable to stable in the OS but still fails during boot. Aloha, FWIW: I have had several FreeBSD boxes from 4.11 to 7* that wont boot with the usb device in the slot, but work just fine if you boot first than insert the usb device. In my case the device is a flash/thumb drive for backing up files. I never figured out why so I just leave them unpluged during a reboot. Maybe it tries to boot from the usb drive which is not bootable so it just hangs in my case. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
