Re: Status, USB/Olympus E-10
* Nick Hibma [EMAIL PROTECTED] [020415 08:48]: Running with a debug kernel should be no problem and not much slower than running with a production kernel. I thought the '-g' flag created two kernels, kernel and kernel.debug. I've always found I can run with kernel, then just pass kernel.debug to 'gdb -k' after a panic/reboot (see below). The only problem is that the machine no longer can be used in unattended mode as it drops into the debugger on panic. options DDB_UNATTENDED # reboot after panics is fine for me (so long as savecore is enabled and you have enough swap). Mr Lucas (he of blackhelicopter fame) did a good howto at: http://www.onlamp.com/lpt/a//bsd/2002/04/04/Big_Scary_Daemons.html (that's part 2 - part 1 is linked from there) (Not for Nicks benefit, I just thought it explained stuff well in case anyone else on the list in unsure how to do this). -- Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Status, USB/Olympus E-10
Running with a debug kernel should be no problem and not much slower than running with a production kernel. I thought the '-g' flag created two kernels, kernel and kernel.debug. I've always found I can run with kernel, then just pass kernel.debug to 'gdb -k' after a panic/reboot (see below). That requires you to set up a dumpdev as well as compiling a debugging kernel. But, yes, kernel.debug corresponds to /boot/kernel/kernel. As a side note: If you get the panic PC you can do a gdb -k /sys/i386/KERNELNAME/kernel.debug dis 0xADDRESS and get the disassembly and program listing of the address where things went wrong. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Status, USB/Olympus E-10
Compile a kernel with UMASS_DEBUG (or load the module compile with CFLAGS+=-DUMASS_DEBUG) and send me the output of an attach. It should be possible to make it work. The fact that it reboots without reason is very very strange indeed. If that is the case, check that your machine is grounded properly. Static electricity nuked my Win2k box every once in a while when I did a sync with my Palm. Nick On Sun, 6 Jan 2002, Kenneth W Cochran wrote: (cc'ed to -scsi) Hello, A couple of committers I were working last July (2001) with support for the Olympus E-10 digital camera in FreeBSD. This is a USB device. I just saw some commits in cam/scsi_da for Nikon I'm wondering what the situation is wrt Olympus? The problem I was having was that even though FreeBSD (then 4.3-stable) would recognise the camera, if I tried to mount() it the os would reboot(!) :(( No panic, no nothing, just a hard freeze rebooting. Obviously, this is Very Very Bad. I've seen Linux (2.4-something) working with this just fine. Linux sees this camera as a SCSI device with a MS-DOS filesystem. I'm now running a 4.5-PRERELEASE wonder if, assuming this hasn't been fixed since 4.3, that this might be fixed in 4.5? At least if the camera isn't/can't be supported in time (for 4.5), is there some way we could at least protect the system from the rebooting? I can probably help test. I'm thinking of filing a PR, but seek advice before doing that. Many thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-scsi in the body of the message -- [EMAIL PROTECTED] http://www.van-laarhoven.org/ [EMAIL PROTECTED]http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Status, USB/Olympus E-10
Then a panic reboot. I guess it's better than before -
previously I got no message whatsoever; the OS just froze
rebooted. At the same time I'd think a panic/reboot is Very
Very Bad; at least if something is wrong shouldn't the OS
just say no?
Well, perhaps you could consider a panic an exceptional condition. One
which has not been taken into account
Could you compile a kernel with debugging and with DDB and then do a
backtrace ('trace') when the kernel hits the debugger on the divide
panic? To know _where_ the divide by zero happens is crucial.
Cheers,
Nick
Here are the related pices of the kernel config:
# SCSI peripherals
devicescbus # SCSI bus (required)
deviceda # Direct Access (disks)
devicesa # Sequential Access (tape etc)
devicecd # CD
devicepass# Passthrough device (direct SCSI access)
.
.
.
# USB support
deviceuhci# UHCI PCI-USB interface
# device ohci# OHCI PCI-USB interface
deviceusb # USB Bus (required)
# device ugen# Generic
# device uhid# Human Interface Devices
# device ukbd# Keyboard
# device ulpt# Printer
deviceumass # Disks/Mass storage - Requires scbus and da
I think the kernel config is ok, because everything works fine
with a USB Zip drive. Any other ideas
-kc
Date: Sun, 6 Jan 2002 18:15:52 -0800 (PST)
From: Kelly Yancey [EMAIL PROTECTED]
To: Kenneth W Cochran [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Status, USB/Olympus E-10
On Sun, 6 Jan 2002, Kenneth W Cochran wrote:
(cc'ed to -scsi)
Hello,
A couple of committers I were working last July (2001) with
support for the Olympus E-10 digital camera in FreeBSD. This
is a USB device.
I just saw some commits in cam/scsi_da for Nikon I'm wondering
what the situation is wrt Olympus?
Bernd Walter submitted a quirk that fixed the problem for E-100RS digital
cameras a while back. I committed the quirk, but I have not MFC'ed it to
-stable. Besides, without other reports the quirk entry I added was specific
to the E-100RS. I'll extend the quirk to the entire E-* seriese and ask RE if
it's OK to MFC in time for 4.5.
Kelly
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-scsi in the body of the message
--
[EMAIL PROTECTED] http://www.van-laarhoven.org/
[EMAIL PROTECTED]http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Status, USB/Olympus E-10
(cc'ed to -scsi) Hello, A couple of committers I were working last July (2001) with support for the Olympus E-10 digital camera in FreeBSD. This is a USB device. I just saw some commits in cam/scsi_da for Nikon I'm wondering what the situation is wrt Olympus? The problem I was having was that even though FreeBSD (then 4.3-stable) would recognise the camera, if I tried to mount() it the os would reboot(!) :(( No panic, no nothing, just a hard freeze rebooting. Obviously, this is Very Very Bad. I've seen Linux (2.4-something) working with this just fine. Linux sees this camera as a SCSI device with a MS-DOS filesystem. I'm now running a 4.5-PRERELEASE wonder if, assuming this hasn't been fixed since 4.3, that this might be fixed in 4.5? At least if the camera isn't/can't be supported in time (for 4.5), is there some way we could at least protect the system from the rebooting? I can probably help test. I'm thinking of filing a PR, but seek advice before doing that. Many thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
