Re: Testers needed: Joe's MFC of USB code

2004-02-27 Thread Eugene Grosbein
On Tue, Feb 24, 2004 at 03:43:58PM -0800, Julian Elischer wrote:

> I've been running Joe's latest USB MFC patch and it seems to work ok for
> me... (both ohci and uhci)
> I have a limited set of devices to test with however..
> Anyone else care to test?
> Getting this in -Stable is a prerequisite to MFCing the EHCI USB 2.0 
> driver so if yu'd like to see USB-2 in 4.x please give this a run
> and net us know..
> The patch is at:
> http://www.josef-k.net/freebsd/
> It applied without hitch to yesterday's RELENG_4

Hi!

I've tested this patch on RELENG_4 (26 Feb 2004) because of the next
problem with HP ScanJet 2200C. Please read details:

1. Boot the system (uhci) and command 'startx'. XFree86-4 starts.
2. Run gimp.
3. Walk through menus: File/Aquire/xscanimage/Device dialog
4. Choose Scan mode: Color42/48, hit Scan button.
   It will complain: 'Gimp doesn't support images with 16bits/channel'
   Things seem to be time dependent - wait aboute 60 seconds then press Ok.
5. Change Scan mode to Color, it will complain:
   'Failed to set value of option mode: Device busy'.
6. Choose 'File/Exit' menu in this xscanimage window.

Several seconds later system will lock up. There is nothing to be done
if you are in X, only power down/up cycle will help.

There is several seconds long time window, one can switch to a vty quickly
and look at 'top' output. One will see xscanimage in state 'usbdly' just
before top will be frozen.

Seldom there will be no lockup, system will be alive and xscanimage
will be in state 'uscnrb'. Just send SIGKILL to xscanimage and lockup will
occur.

Sympthoms of lockup: system does not respond to pings, consoles do not switch.
Ctril-Alt-ESC will work for a few moments after lockup
but if you wait a little, it won't work and lockup will become 'total'.

Versions: sane-backends-1.0.13_2, sane-frontends-1.0.11_1, gimp-1.2.3_2,1

Now what do we have with a patch proposed? Well, instead of lockup
we obtain good old kernel panic (the patch is really usefull).
And crashdump, of course. The panic is 100% repeatable. Here comes gdb
backtrace (kernel compiled with INVARIANTS and debug info):

Script started on Fri Feb 27 00:38:08 2004
GNU gdb 4.18 (FreeBSD)
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called at 
/usr/local/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 
2627 in elfstab_build_psymtabs
Deprecated bfd_read called at 
/usr/local/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 
in fill_symbuf

IdlePTD at physical address 0x003ed000
initial pcb at physical address 0x0033df80
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x884
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc02263a2
stack pointer   = 0x10:0xdb2efcf8
frame pointer   = 0x10:0xdb2efcfc
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 = 493 (xscanimage)
interrupt mask  = bio 
trap number = 12
panic: page fault

syncing disks... 12 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 
0xcc5d18e0 1: dev:#ad/0x20017, flags:21021024, blkno:1112924, lblkno:0
0xcc5d1794 2: dev:#ad/0x20017, flags:0164, blkno:12394560, lblkno:12394560
0xcc5d1648 3: dev:#ad/0x20017, flags:0164, blkno:1093696, lblkno:1093696
0xcc53b1e0 4: dev:#ad/0x20017, flags:21021024, blkno:1094144, lblkno:1094144
0xcc52d2d0 5: dev:#ad/0x20014, flags:21021024, blkno:517888, lblkno:2
0xcc5276bc 6: dev:#ad/0x20017, flags:21021024, blkno:12394816, lblkno:12394816
0xcc511748 7: dev:#ad/0x20017, flags:2124, blkno:16, lblkno:16
0xcc5115fc 8: dev:#ad/0x20017, flags:2124, blkno:5728, lblkno:5728
giving up on 8 buffers
Uptime: 9m32s
/dev/vmmon: Module vmmon: unloaded

dumping to dev #ad/0x20011, offset 1048704
dump ata1: resetting devices .. done
511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 
490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 
469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 
448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 
427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 
406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 
385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 
364 363 362 361 360 359 358 357 356 355 354 353 352 351

getpwent and groups

2004-02-27 Thread Daniel Ellard

I use NIS to manage passwords, and due to a
policy change I recently changed the last line
of the password file from

+:

to

[EMAIL PROTECTED]:

so that only my "guests" are able to log in to my machines instead of
everyone in the entire department.

This works fine as far as logins are concerned.  The problem is that
now programs that use getpwent (i.e.  finger and top) now seg fault!

Is this a known problem, and if so is there a fix in the works?

I'm running 4.8p15.

Thanks,
-Dan

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


HEADSUP.. USB MFC coming..

2004-02-27 Thread Julian Elischer

I plan to commit the MFC at http://www.josef-k.net/freebsd/
(the latest one) in the next couple of days. If you really care about 
USB in 4.10 you might do well to test this on your equipment,
ESPECIALLY if you have unusual devices. Let me know of both successes
and failures please.. If I hear nothing I won't know if it's because
no-one tested it or it was just without problems..



Please also check these same devices without the patch BEFORE you let me
know of any failures so that we can tell if they are truely caused by
the patch..

I hope to commit on Sunday Afternoon California time..
(around 23:00 Sunday UTC)

I will then move on to merging in the EHCI USB-2.0 driver.


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


cue cat

2004-02-27 Thread quel
Has anyone had trouble w/ the usb cue cat?  It appears correctly in dmesg 
but fails to work.  On obsd/nbsd and linux is appears correctly.  (I have 
a modified cue cat which outputs to stdin the result of the scan)  On fbsd 
it appears to do nothing.  This is 5.2.1-RELEASE.  Any ideas?

-James
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"