those keys working ?
Where to dig ?
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
on 04/04/2007 11:56 Andriy Gapon said the following:
I have a problem similar to this:
http://www.freebsd.org/cgi/query-pr.cgi?pr=102066
[snip]
The problem is that under X xev program doesn't show any events for
pressing of extra keys (6 multimedia ones and 3 ACPI ones).
In Linux xev does
. Maybe some parameters were incorrect, or maybe different
devices need different parameters and that's where _no() comes useful.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe
on 16/08/2007 19:41 Hans Petter Selasky said the following:
On Thursday 16 August 2007, Andriy Gapon wrote:
on 16/08/2007 19:15 Hans Petter Selasky said the following:
Hi,
I would say that usbd_set_config_index() is more reliable and faster
than usbd_set_config_no(). I tried to get rid
on 16/08/2007 15:22 Andriy Gapon said the following:
I have ASUS P535 PPC+phone with Windows Mobile 5 on it.
It has an option to act as a USB mass storage (instead of attempting
acivesync).
[snip]
So I attempted the latter quirk and it helped me! But there is one not
good thing about the way
bInterval0
Codes Representing Languages by the Device:
bLength 4
bDescriptorType 03
wLANGID[0] 0409
String (index 1): ASUS
String (index 2): ASUS Windows Mobile Device
String (index 3): f553b4ec-0dee-9dcc-7a63-40a7b4d674b9
--
Andriy Gapon
devlist -v:
scbus6 on umass-sim0 bus 0:
Generic USB SD Reader 1.00 at scbus6 target 0 lun 0 (da0,pass2)
at scbus6 target 0 lun 2 (probe0)
at scbus6 target -1 lun -1 ()
--
Andriy Gapon
.
This is quite weird for me. My question if this is something most likely
caused by software or something caused by the hardware. And if the
latter - what is most likely at fault: the reader, connecting cable,
physical port, hub ?
--
Andriy Gapon
___
freebsd-usb
on 25/12/2007 13:03 Andriy Gapon said the following:
I have a strange problem - when I disconnect a certain USB card reader
its umass* and da* devices are not removed, there is complete silence in
the system log and usbdevs -vd still shows it as connected.
Restarting usbd and/or running usbd
100 mA, config 1, Mass Storage
Device(0x6362), Generic(0x058f), rev 1.26
on 25/12/2007 13:26 Andriy Gapon said the following:
on 27/11/2007 10:55 Remko Lodder said the following:
[snip]
Just in case:
the reader - Trust CR-1420P
the card - SanDisk SDSDM-2048
The above information
fields (), they get ignored.
on 16/08/2007 15:22 Andriy Gapon said the following:
I have ASUS P535 PPC+phone with Windows Mobile 5 on it.
It has an option to act as a USB mass storage (instead of attempting
acivesync).
When I tried it, it first got recognized by umass and then it
immediately
quirk
to force some inquiry data instead of dynamic inquiry response checking,
but I am not sure if that would be any better.
Would it be more convenient for everybody if I file a PR on this ?
Thank you for your attention.
on 24/01/2008 15:58 Andriy Gapon said the following:
This is me again
haven't checked)
by mistake used ttyU0 again
got the crash
I believe that this is another example of a bad use of our device
cloning, but I can be very wrong here.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman
on 28/02/2008 23:36 Andriy Gapon said the following:
I recently had a bad experience with ucom. I didn't try to reproduce it
in a controlled way, so that I could fully document it. So, here's my
recollection and impression/understanding of it with couple of facts on top.
The bad experience
) {
error(ioctl USB_REQUEST);
close(fd);
exit(EXIT_FAILURE);
}
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any
Marcin wrote:
Andriy Gapon wrote:
I believe that this is another example of a bad use of our device
cloning, but I can be very wrong here.
What driver are you using to have ucom device there (uftdi, ubsa, etc.)?
Is this behavior easy to reproduce?
This was palm/uppc-kmod module. I believe
if this is some brokenness of that driver or fighting of
several USB drivers over the same hardware.
P.S. sorry for the wide broadcast, but I think that users on all 3 lists
might be interested.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http
on 17/04/2008 18:31 Paul Schmehl said the following:
--On Thursday, April 17, 2008 18:06:28 +0300 Andriy Gapon [EMAIL PROTECTED]
wrote:
on 17/04/2008 17:56 Paul Schmehl said the following:
I wish I had a core file to analyze. *Every* time I reboot my machine, I
have to disconnect my usb
reset all - the same error. ktrace showed that the error came
from ioctl on xpt device.
I rebooted without the umass device and everything went back to normal.
I'll try to do more debugging later.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
on 22/04/2008 23:16 Andriy Gapon said the following:
BTW, I use RELENG_7, i386, UP.
Anyway, I see a different issue with booting while a umass device is
connected. First issue was that k3b hasn't found my two cd/atapicam
devices. Then I executed camcontrol rescan all, it failed with EINVAL
button presses (similarly to how
vertical scrolling is handled in it).
Thank you in advance for advices and opinions.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send
into kernel.
Weird...
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
on 06/11/2008 14:34 Andriy Gapon said the following:
I have a quite strange problem.
This is with 7-BETA amd64.
All of USB is out of kernel and is loaded via modules.
BIOS has Legacy USB enabled.
I have only a USB keyboard, no PS/2 port.
The keyboard works file in BIOS and for selecting
on 08/11/2008 14:31 Volker said the following:
Andriy,
On 12/23/-58 20:59, Andriy Gapon wrote:
I have a quite strange problem.
This is with 7-BETA amd64.
Did it work with earlier versions?
Can't say, this is a new machine, FreeBSD took its virginity :-)
All of USB is out of kernel
will have
to live with it (this system doesn't have PS/2 ports at all).
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
on 05/11/2008 17:24 Andriy Gapon said the following:
System is FreeBSD 7.1-BETA2 amd64.
Looking through my dmesg I see that relative order of ukbd attachment
and root mounting is not deterministic. Sometime keyboard is attached
first, sometimes root filesystem is mounted first. Quite more
on 12/11/2008 14:14 Jeremy Chadwick said the following:
On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote:
[snip]
2. if ukbd driver is not attached then I don't see any way USB keyboard
would work in non-legacy way
Regarding #2: at which stage? boot0/boot2/loader require
on 12/11/2008 13:53 Nate Eldredge said the following:
On Wed, 12 Nov 2008, Andriy Gapon wrote:
on 05/11/2008 17:24 Andriy Gapon said the following:
[...]
I have a legacy-free system (no PS/2 ports, only USB) and I wanted to
try a kernel without atkbd and psm (with ums, ukbd, kbdmux
on 12/11/2008 14:33 Jeremy Chadwick said the following:
On Wed, Nov 12, 2008 at 02:20:41PM +0200, Andriy Gapon wrote:
on 12/11/2008 14:14 Jeremy Chadwick said the following:
On Wed, Nov 12, 2008 at 01:58:58PM +0200, Andriy Gapon wrote:
[snip]
2. if ukbd driver is not attached then I don't see
chain, etc. I am not even interested
in speculations about whether keyboard would work or not at mountroot
prompt if it were attaching before it.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
Mouse, class 0/0, rev 2.00/24.30, addr
2 on uhub2
ums0: 8 buttons and Z dir.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
on 27/11/2008 15:23 Andriy Gapon said the following:
I increased debug level in uhub and also switched mouse and keyboard
ports hoping that order might matter. It didn't.
Here's fresh usbdevs output snippet:
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub
seconds.
Not sure how to explain this.
I think I've seen some changes to reduce memory usage of loader, I will
try them to see if that would make any difference for my situation.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http
at the loader prompt!
All in all, it seems that this is right direction.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
I would like to report that I am no longer seeing the issue in the subject line.
The problem was fixed by the recent commits of jhb ( I tested stable/7).
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman
,
Someone knows if a person works on usb video class driver ?
Thanks in advance,
Nicolas.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb
on 28/05/2009 07:52 Emil Mikulic said the following:
On Wed, May 27, 2009 at 03:29:19PM +0300, Andriy Gapon wrote:
I think it's time to remind of this issue again. I have no clue why
it happens but on my system I consistently see that my USB keyboard is
detected after mountroot. This worries
The following reply was made to PR usb/133989; it has been noted by GNATS.
From: Andriy Gapon a...@icyb.net.ua
To: bug-follo...@freebsd.org, emiku...@gmail.com
Cc:
Subject: Re: usb/133989: [newusb] [ukbd] USB keyboard dead at mountrootgt;
prompt
Date: Thu, 28 May 2009 18:22:29 +0300
Me too
) and in kbdmux_kbd_event (kbd callback).
But, these shouldn't get called in polling mode, right? (because there shouldn't
be any interrupts)
Maybe Giant asserts in ukbd are not needed?
Or should be asserted only in normal mode?
P.S. I am far from knowing this area, just got curious.
--
Andriy Gapon
;
--
Andriy Gapon
___
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
still get a mouse attachment problem during boot?
(No other devices during boot please :-) to simplify the testcase.)
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail
on 25/09/2009 11:02 Svein Skogen (listmail account) said the following:
Andriy Gapon wrote:
on 24/09/2009 17:51 Hans Petter Selasky said the following:
*SNIP!*
Not sure how to interpret this.
Either a timing issue, i.e. the register gets over-written some time after we
program
on 25/09/2009 10:28 Hans Petter Selasky said the following:
On Friday 25 September 2009 08:34:21 Andriy Gapon wrote:
Not sure how to interpret this.
In ohci_controller_init() try to disable the
DPRINTF(SMM active, request owner change\n);
part of the code for !(ohci_unit == 0
on 27/09/2009 15:17 Andriy Gapon said the following:
Another idea of working around this:
1) in pci fixup code disable USB SMI for these chipsets
2) (optional) in ohci code skip takeover step
Sounds messy.
BTW, just for the sake of experiment I did exactly what I suggested.
I've got
on 27/09/2009 16:10 Andriy Gapon said the following:
kernel: ohci_controller_init:195: SMM active, request owner change
kernel: usbus0: SMM does not respond, resetting
kernel: ohci_controller_init:195: SMM active, request owner change
kernel: usbus1: SMM does not respond, resetting
kernel
affect the bits of the other controllers - they remain set.
Not that it means that SMM code actually keeps on controlling them.
Actually, just checked - Linux also does it per controller:
http://lxr.linux.no/#linux+v2.6.31/drivers/usb/host/ohci-hcd.c#L495
--
Andriy Gapon
on 28/09/2009 17:10 John Baldwin said the following:
On Monday 28 September 2009 9:55:44 am Andriy Gapon wrote:
on 28/09/2009 14:48 John Baldwin said the following:
I don't think you can do this because it is a feature to not disable SMM
if
ohci(4) is not loaded so that a USB keyboard works
. The
keyboard itself I am using is Acer's standard one, and it works fine with
LiveCD. I wonder if GELI might mess the things up, but the geli attachment
process goes well, and all filesystems are attached just fine.
LiveCD is also 8.0-RC3?
--
Andriy Gapon
on 28/11/2008 15:12 Andriy Gapon said the following:
on 27/11/2008 15:23 Andriy Gapon said the following:
I increased debug level in uhub and also switched mouse and keyboard
ports hoping that order might matter. It didn't.
Here's fresh usbdevs output snippet:
Controller /dev/usb2:
addr 1
on all
but the good port:
I think that this problem is fixed in 8-STABLE but not 8.0-RELEASE.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb
on 03/12/2009 18:54 Ondřej Majerech said the following:
On Thu, 03 Dec 2009 14:51:11 +0100, Andriy Gapon a...@icyb.net.ua wrote:
I think that this problem is fixed in 8-STABLE but not 8.0-RELEASE.
I've had the same problem, updating to 8-STABLE did fix it, -RELEASE
doesn't work for me
.
--
Andriy Gapon
___
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
bLength = 0x07
bDescriptorType = 0x25
bDescriptorSubType = 0x01
RAW dump:
0x00 | 0x07, 0x25, 0x01, 0x01, 0x00, 0x00, 0x00
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
on 26/01/2010 20:36 Andriy Gapon said the following:
on 26/01/2010 19:37 Hans Petter Selasky said the following:
The string is just too big, so it gets truncated. Send me a dump of the
config
descriptor for the webcamera. If it says 0x0e for interface class, it's most
likely supported
on 26/01/2010 20:39 Andriy Gapon said the following:
Seems like webcamd indeed recognizes this webcam, but it does that...
eventually.
That is, I have to start webcamd several times until it seems the webcam.
The first few attempts end with 'Cannot find USB device'.
I always start it using
on 26/01/2010 20:43 Andriy Gapon said the following:
[snip]
Added control ----0101/2 to device entity 5
Added control ----0101/3 to device entity 5
Added control ----0101/6 to device entity 5
Added control
on 26/01/2010 20:47 Andriy Gapon said the following:
What's also strange is that webcam's in use light never turns on.
OK, it actually does turn on.
What I've discovered is that the webcam needs some short time to warm up.
I've modified pwcview to ignore a few initial v4l1_read error
on 26/01/2010 23:05 Hans Petter Selasky said the following:
On Tuesday 26 January 2010 19:43:20 Andriy Gapon wrote:
on 26/01/2010 20:39 Andriy Gapon said the following:
Seems like webcamd indeed recognizes this webcam, but it does that...
eventually. That is, I have to start webcamd several
And also I get the following on the stdout of webcamd (with Linux debug
converted
to printfs):
uvc_v4l2_open
Unknown ioctl 0x40047601
uvc_v4l2_release
P.S. I am using the latest versions of all required software _from ports_.
I haven't tried svn version of webcamd yet.
--
Andriy Gapon
on 27/01/2010 19:14 Hans Petter Selasky said the following:
On Wednesday 27 January 2010 17:11:08 Andriy Gapon wrote:
BTW, on Skype with video4bsd - when I start Skype and try to configure a
video device I get the following in system log:
kernel: linux: pid 21092 (skype): ioctl fd=10, cmd
USB emulation.
I think that Hans can't change the PR assignment.
So this message is mostly for Mark :-)
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail
on 10/03/2010 02:25 Fbsd1 said the following:
Thank you Andriy Gapon for the courteous and informative post. May I
suggest that the submit-pr web page be changed by replacing the USB
assignment with Kernel-usb assignment. That is more in line with the USB
charter and would reduce the number
on 07/04/2010 14:20 Julian H. Stacey said the following:
I wonder if it's eg a corrupt FS not being fsck'd first ?
Have you given a look to the backtrace that Mikhail had posted?
I think that it answers your question.
--
Andriy Gapon
___
freebsd-usb
/customfreebsdiso.html
But now the boot-process panics at a later stage in the process and it looks
like this:
http://www.pean.org/macbook_boot.jpg
Any pointers?
Wow, a 3833x2492 screenshot of a text console!
Can you execute 'bt' at the last prompt?
--
Andriy Gapon
on 26/04/2010 23:49 Peter Ankerstål said the following:
On 26 apr 2010, at 22.21, Andriy Gapon wrote:
on 26/04/2010 22:31 Peter Ankerstål said the following:
I managed to get the boot-process past the ACPI-part by adding
similar lines like above (MacBookPro7,1) to the FreeBSD HEAD branch
,
The USB threads are joined into a single process and not visible from ps.
Not sure how you can get a list of all threads.
-H option would that for ps.
But I am not why mentioned ps, because procstat shows the threads, e.g. procstat
-k -a will show stacks of all non-running kernel threads.
--
Andriy
The following reply was made to PR usb/138548; it has been noted by GNATS.
From: Andriy Gapon a...@freebsd.org
To: bug-follo...@freebsd.org, yeren...@gmail.com
Cc:
Subject: Re: usb/138548: [usb67] [usb8] usb devices periodically have unknown
activity
Date: Mon, 15 Nov 2010 10:50:19 +0200
BTW
much.
Are you sure?
The last two arguments to DRIVER_MODULE() look like what you want.
I need to run some code only once, at very
beginning, not for each probe/attach.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http
is attached )
--
Andriy Gapon
___
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
on 05/04/2011 14:21 Hans Petter Selasky said the following:
On Tuesday 05 April 2011 13:06:22 Andriy Gapon wrote:
on 03/04/2011 13:46 Andriy Gapon said the following:
Mostly out of curiosity (but not only because of that) I wonder why the
use_generic flag and two probing passes are needed
on 05/04/2011 15:55 Hans Petter Selasky said the following:
On Tuesday 05 April 2011 14:50:43 Andriy Gapon wrote:
I believe that newbus already supports ordering of children on a bus.
BTW, does USB have to pass anything from probe to attach?
Mostly only the driver info field. To avoid
.
--
Andriy Gapon
___
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
on 17/05/2011 10:19 Andriy Gapon said the following:
So I am going to commit this.
If it breaks anything for anyone and the problem would not be really trivial,
the I'll just revert the change.
r222051.
Please take this commit in consideration if you run into any USB-related
problems
description this sounds like a problem in USB driver.
I am not an expert in USB code, looks like some polling prodding would have to
be
added there (if it's not there yet). Hans Petter may be a better contact for
this
issue.
I am not sure if I can help you more.
--
Andriy Gapon
Just trying to find out if anyone got Epson Perfection v33 USB scanner working
with SANE on FreeBSD. Or any other similar Epson scanner that requires
proprietary drivers from Avasys under Linux.
Thanks!
--
Andriy Gapon
___
freebsd-usb@freebsd.org
in case.
--
Andriy Gapon
___
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
on secure
I can login to the box no problem. But That does not show bootup access
via the serial console. Is there a way to enable that ?
I don't believe so.
USB subsystem depends on so many kernel services that USB drivers become
functional quite late in the boot process.
--
Andriy Gapon
Does the following change do what I think that it does?
Thank you!
Author: Andriy Gapon a...@icyb.net.ua
Date: Thu Sep 1 16:50:13 2011 +0300
ukbd: drop local duplicate of kern_yield and use that instead
diff --git a/sys/dev/usb/input/ukbd.c b/sys/dev/usb/input/ukbd.c
index 086c178
on 11/12/2011 23:48 m...@freebsd.org said the following:
On Sun, Dec 11, 2011 at 1:12 PM, Andriy Gapon a...@freebsd.org wrote:
Does the following change do what I think that it does?
Thank you!
Author: Andriy Gapon a...@icyb.net.ua
Date: Thu Sep 1 16:50:13 2011 +0300
ukbd: drop local
/d td-td_user_pri
$10 = 139
(kgdb) p/d td-td_base_pri
$11 = 84
--
Andriy Gapon
___
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
on 13/12/2011 00:21 Andriy Gapon said the following:
on 12/12/2011 21:09 Hans Petter Selasky said the following:
On Monday 12 December 2011 20:05:38 John Baldwin wrote:
Hi,
hselasky@ or someone else familiar with the various usb threads would
have to answer that.
The problem is only
on 13/12/2011 10:17 Andriy Gapon said the following:
on 13/12/2011 00:21 Andriy Gapon said the following:
[snip]
And in the view of the below data I would like us to revisit this problem.
I looked over usb code and it seems that all usb threads are created with
priorities of either USB_PRI_MED
on 14/12/2011 23:56 Hans Petter Selasky said the following:
On Wednesday 14 December 2011 16:37:50 Andriy Gapon wrote:
So, Hans Petter, do you recall any details of this problem?
I am curious about which thread got starved by which.
From what I know this was 100% reproducible.
Remove
on 16/12/2011 00:56 Hans Petter Selasky said the following:
On Thursday 15 December 2011 15:17:01 Andriy Gapon wrote:
Hmm... I looked at the history of ukbd.c (which I should have done from the
very start) and I see two relevant revisions:
http://svnweb.freebsd.org/base/head/sys/dev/usb/input
);
return (retval);
So we are in a polling mode and Giant is not owned by us (T2) because it is
owned by T1 and so mtx_lock would be called and then we would probably get into
a recursion via mi_switch and kdb_reenter.
--
Andriy Gapon
___
freebsd-usb
Replying further...
on 16/12/2011 00:56 Hans Petter Selasky said the following:
On Thursday 15 December 2011 15:17:01 Andriy Gapon wrote:
Hmm... I looked at the history of ukbd.c (which I should have done from the
very start) and I see two relevant revisions:
http://svnweb.freebsd.org/base
. Thank you!
--
Andriy Gapon
___
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
on 18/12/2011 19:39 Hans Petter Selasky said the following:
On Sunday 18 December 2011 11:58:57 Andriy Gapon wrote:
on 17/12/2011 19:06 Hans Petter Selasky said the following:
If the problem is only in UKBD driver, I don't think this is a big
problem to solve. The reason for the auto-magic
that once those are used in the kdb
context then there is no safe way to go back to normal system operation.
What do you think?
Thank you.
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
shutdown/reboot.
P.S. I've just looked at the code in stable/7 and it seems that it didn't
actually unconfigured USB and detached device drivers. At least ohci_shutdown
and ohci_shutdown are not called on FreeBSD.
--
Andriy Gapon
___
freebsd-usb
already committed the change - thanks!
--
Andriy Gapon
___
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
{\
if (!cold !kdb_active panicstr == NULL) \
mtx_assert(Giant, MA_OWNED); \
} while (0)
#else
#define KBD_LOCK_ASSERT() (void)0
#endif
P.P.S. Did you have a chance to look at http://wiki.freebsd.org/AvgSyscons yet?
Thank you!
--
Andriy Gapon
)
this pattern does not make sense, because the Giant is recursive and can be
simply acquired without any check.
Do you agree?
--
Andriy Gapon
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail
on 20/12/2011 16:00 Attilio Rao said the following:
2011/12/20 Andriy Gapon a...@freebsd.org:
I completing a patch that changes some locking in ukbd to account for
SCHEDULER_STOPPED and for other realities of the code.
As a preview I would like to share couple of observations that had
And the new patch:
http://people.freebsd.org/~avg/usb.new.diff
--
Andriy Gapon
___
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
on 20/12/2011 18:41 Hans Petter Selasky said the following:
On Tuesday 20 December 2011 16:16:36 Andriy Gapon wrote:
And the new patch:
http://people.freebsd.org/~avg/usb.new.diff
Patch looks OK. I will give it a spin later today. Feel free to commit if
you've tested the three use-cases I
on 20/12/2011 14:25 Andriy Gapon said the following:
I just wanted to draw your attention to the fact that obtaining any locks in
the
kdb context (or USB polling code in general, even) is not a good idea.
Chances of getting into trouble on those locks are probably quite moderate or
even low
on 21/12/2011 18:38 Hans Petter Selasky said the following:
On Wednesday 21 December 2011 12:29:49 Andriy Gapon wrote:
on 20/12/2011 14:25 Andriy Gapon said the following:
I just wanted to draw your attention to the fact that obtaining any locks
in the kdb context (or USB polling code
on 29/02/2012 11:47 Karl Pielorz said the following:
http://www.tdx.com/x8dtl-if.txt
So the cause is that ukbd driver tries to attach after the mountroot stage.
The symptom is obvious, a fix is not.
--
Andriy Gapon
___
freebsd-usb@freebsd.org
:
dec2hex(17454747090944)
ans = FE0
So it looks like some additional bits have sneaked in there?
dec2hex(32463912960)
ans = 78F00
0xFE0 / 0x78F00
ans = 537.67
So it looks like the mediasize was multiplied by 512 when it shouldn't.
--HPS
--
Andriy Gapon
1 - 100 of 110 matches
Mail list logo
