Getting Logitech USB Receiver ("Cordless Desktop") auto-detected on boot

2009-04-19 Thread Raphael Becker
Hi all,

my Logitech USB Receiver isn't automatically detected by the kernel on
system boot, not even a LED is glowing. The keyboard is detected and working 
perfectly by the system BIOS and is usable in BIOS and for the boot
loader until the kernel is running.

A workaround is disconnecting/reconnecting the USB connector to the PC,
to get it detected by the kernel (after mounting root).

ukbd0:  on uhub2
kbd1 at ukbd0
ums1:  on uhub2
ums1: 16 buttons and Z dir.

My mainboard has PS/2 connectors for keyboard and mouse so I tried to
workaround the USB-problems by disabling the devices in the kernel:

nodevice  atkbdc  # AT keyboard controller
nodevice  atkbd   # AT keyboard
nodevice  psm # PS/2 mouse
 
But this makes no real difference for USB, just the kernel isn't
detecting an "virtual" AT-Keyboard (which isn't really connected to
ps/2):


before: --- kernel with ps/2 and atkbd support
now: +++ kernel without ps/2 and adkbd support 


--- HW_20090419220146/dmesg.boot2009-04-19 22:01:46.0 +0200
+++ HW_20090419222851/dmesg.boot2009-04-19 22:28:51.0 +0200

-FreeBSD 7.2-RC1 #0: Sat Apr 18 14:57:37 CEST 2009
+FreeBSD 7.2-RC1 #1: Sun Apr 19 22:19:26 CEST 2009
[...]
-atkbdc0:  port 0x60,0x64 irq 1 on acpi0
-atkbd0:  irq 1 on atkbdc0
-kbd0 at atkbd0
-atkbd0: [GIANT-LOCKED]
-atkbd0: [ITHREAD]
[...]
 Trying to mount root from ufs:/dev/ufs/ROOT <-- !!
 ukbd0:  on uhub2
-kbd2 at ukbd0
+kbd1 at ukbd0
 ums1:  on uhub2
 ums1: 16 buttons and Z dir.

I had to reconnect the USB (to type geli-passphrases), so before and now 
the ukbd0 is detected after mounting root.  

I guess most of you have USB keyboards and mouse. Is this problem very common? 
Is this related to mainboard / usb handling or related to the usb devices? 
Is this related to the usb connetor on the pc?
(actually the receiver is connected to uhub2->usb2->uhci2)


My board has about 4 different usb chips
uh...@pci0:0:26:0:  class=0x0c0300 card=0x82771043 chip=0x29378086 rev=0x02 
hdr=0x00
uh...@pci0:0:26:1:  class=0x0c0300 card=0x82771043 chip=0x29388086 rev=0x02 
hdr=0x00
uh...@pci0:0:26:2:  class=0x0c0300 card=0x82771043 chip=0x29398086 rev=0x02 
hdr=0x00
eh...@pci0:0:26:7:  class=0x0c0320 card=0x82771043 chip=0x293c8086 rev=0x02 
hdr=0x00

All the USB stuff from dmesg:

uhci0:  port 0xc480-0xc49f irq 16 at device 26.0 
on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0:  on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xc800-0xc81f irq 21 at device 26.1 
on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1:  on uhci1
usb1: USB revision 1.0
uhub1:  on usb1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0xc880-0xc89f irq 18 at device 26.2 
on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb2:  on uhci2
usb2: USB revision 1.0
uhub2:  on usb2
uhub2: 2 ports with 2 removable, self powered
ehci0:  mem 0xfe7fbc00-0xfe7fbfff irq 18 at 
device 26.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb3: EHCI version 1.0
usb3: companion controllers, 2 ports each: usb0 usb1 usb2
usb3:  on ehci0
usb3: USB revision 2.0
uhub3:  on usb3
uhub3: 6 ports with 6 removable, self powered
uhub4:  on
uhub3
uhub4: single transaction translator
uhub4: 4 ports with 4 removable, self powered
ums0:  on 
uhub4
ums0: 3 buttons and Z dir.
ulpt0:  on uhub4
ulpt0: using bi-directional mode
 
(ums0 is not the logitec mouse)

Why doesn't the kernel detect the Logitech USB Receiver? 
Any suggestions?


TIA and Regards
Raphael



-- 
Raphael Beckerhttp://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgpcDrIVNs27z.pgp
Description: PGP signature


crash on 7.2-RC1 when inserting an empty DVD: supervisor write, page not present

2009-04-19 Thread Raphael Becker
 symbols from /boot/kernel/sound.ko...Reading symbols from 
/boot/kernel/sound.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/sound.ko
Reading symbols from /boot/kernel/ichsmb.ko...Reading symbols from 
/boot/kernel/ichsmb.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ichsmb.ko
Reading symbols from /boot/kernel/smbus.ko...Reading symbols from 
/boot/kernel/smbus.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/smbus.ko
Reading symbols from /boot/kernel/atapicam.ko...Reading symbols from 
/boot/kernel/atapicam.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/atapicam.ko
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from 
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from 
/boot/kernel/linprocfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linprocfs.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from 
/boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/nullfs.ko...Reading symbols from 
/boot/kernel/nullfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/nullfs.ko
Reading symbols from /usr/local/modules/fuse.ko...done.
Loaded symbols for /usr/local/modules/fuse.ko
Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from 
/boot/kernel/fdescfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/fdescfs.ko
Reading symbols from /usr/local/modules/rtc.ko...done.
Loaded symbols for /usr/local/modules/rtc.ko
Reading symbols from /boot/kernel/i915.ko...Reading symbols from 
/boot/kernel/i915.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/i915.ko
Reading symbols from /boot/kernel/drm.ko...Reading symbols from 
/boot/kernel/drm.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/drm.ko
#0  doadump () at pcpu.h:196
196 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) where
#0  doadump () at pcpu.h:196
#1  0xc07df277 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2  0xc07df549 in panic (fmt=Variable "fmt" is not available.) at 
/usr/src/sys/kern/kern_shutdown.c:574
#3  0xc0ae0bac in trap_fatal (frame=0xc6779bd4, eva=3210718950) at 
/usr/src/sys/i386/i386/trap.c:939
#4  0xc0ae0e30 in trap_pfault (frame=0xc6779bd4, usermode=0, eva=3210718950) at 
/usr/src/sys/i386/i386/trap.c:852
#5  0xc0ae17dc in trap (frame=0xc6779bd4) at /usr/src/sys/i386/i386/trap.c:530
#6  0xc0ac5eeb in calltrap () at /usr/src/sys/i386/i386/exception.s:159
#7  0xc0519b00 in ata_pio_read (request=0xc7bedd80, length=18) at cpufunc.h:229
#8  0xc051b195 in ata_end_transaction (request=0xc7bedd80) at 
/usr/src/sys/dev/ata/ata-lowlevel.c:386
#9  0xc05053f2 in ata_interrupt (data=0xc6a37c00) at 
/usr/src/sys/dev/ata/ata-all.c:343
#10 0xc0506225 in ata_generic_intr (data=0xc69b9b00) at 
/usr/src/sys/dev/ata/ata-chipset.c:230
#11 0xc07bd1db in ithread_loop (arg=0xc69f7a70) at 
/usr/src/sys/kern/kern_intr.c:1088
#12 0xc07b9d29 in fork_exit (callout=0xc07bd020 , arg=0xc69f7a70, 
frame=0xc6779d38)
at /usr/src/sys/kern/kern_fork.c:810
#13 0xc0ac5f60 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264

Regards
Raphael

-- 
Raphael Beckerhttp://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgpZkeUJA8tb4.pgp
Description: PGP signature


Re: RELENG_7: chatty geom

2009-04-14 Thread Raphael Becker
On Tue, Apr 14, 2009 at 01:52:27AM +0200, Ivan Voras wrote:

[Labels apperaring ad disappearing]

> Now Glabel is complaining you didn't use a label and have used a device
> node as the mount point :)

This isn't new (to me). Having ufs-labelled md-devices brings me those 
messages since 6.x (since in use geom labels), because the mdconfig 
rc-scripts don't know about "/dev/md0 == /dev/ufs/FOO" and therefore mount 
the md-devices directly instead of the labels which makes the labels
disappear directly after mdconfig has just "created" them.
 
> I'll commit a silencing patch as soon as I get approval for it.

How would one get the ids of ufsid-labels when hidden? glabel list shows
only the "active" labels, especially doesn't show the ufsid-label if the
device is mounted by its "legacy" devicename (just tried that). dmesg  
seems the only source of information for that so far.

Regards
Raphael Becker

PS: In gerneral I find it very useful to operate on labels instead of 
"legacy" device names, especially for S-SATA disks. I even use 
/dev/ufs/ROOT instead of /dev/ads1a which works perfectly:

# dmesg | grep ROOT
GEOM_LABEL: Label for provider ad6s1a is ufs/ROOT.
Trying to mount root from ufs:/dev/ufs/ROOT


-- 
Raphael Beckerhttp://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgpj2M1Toh3ic.pgp
Description: PGP signature


mount_ext2fs in 7-STABLE?

2009-04-14 Thread Raphael Becker
Hi,

I noticed that mount_ext2 isn't "connected" to the normal "buildworld"
but sys/*/ext2fs seems to.

Building and using it from recent RELENG_7 sources works for me (having
ext2fs loaded as module in GENERIC). I mounted an ext3 rw, edited
grub's menu.lst, wrote and umounted without any problems.

It seems recent bugs got pathched in January
(http://www.freebsd.org/cgi/query-pr.cgi?pr=131024)

Is there a good reason NOT to use ext2fs in 7.2-PRE?

BTW: dmesg conseals the Linux-partitions (hda5, hda6 alias /dev/ad0s5 and 
/dev/ad0s6) residing in a "DOS Extended" partition (/dev/ad0s3).  Shouldn't 
there be a notice about the mapped ad0s5 and ad0s6? 

BTW2: shouldn't the mapped by label to /dev/ext2fs/foo like
/dev/ntfs/bar or /dev/msdosfs/baz ? 

Regards
Raphael



-- 
Raphael Beckerhttp://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgprYaeLBInBo.pgp
Description: PGP signature


Re: apache 2.0.63 and php5

2009-04-12 Thread Raphael Becker
On Sat, Apr 11, 2009 at 06:37:48PM +0200, xer wrote:
> For fix it, i need to make a simple apachectl stop and start, then the php 
> pages start to works...
>
> any ideas?

When you use apachectl start apache inherits the environment of the user
from apachectl, especially PATH. PATH is different for /root and boot.   

Create a simple php  with "" in it and compare the
Values for PATH a) after boot b) after restart by apachectl



HTH

Raphael

-- 
Raphael Beckerhttp://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgpzfacEzSTFe.pgp
Description: PGP signature


Re: problems with 7.2, vm_page_insert: page already inserted

2009-04-12 Thread Raphael Becker
On Sat, Apr 11, 2009 at 08:30:42PM -0400, Ken Smith wrote:
> That said if there is a bug it's likely to be something fairly difficult
> to reproduce (lots of people are running 7.2-PRERELEASE and so far only
> two reports of this issue) so it's not a shock for you to have only had
> it happen once so far.  Odds are it takes a rare sequence of events to
> trigger it.

I also reported this in Mar 19th with some kgdb-output:
http://lists.freebsd.org/pipermail/freebsd-stable/2009-March/048911.html

== uname -a ==
FreeBSD top.uugrn.org 7.1-STABLE FreeBSD 7.1-STABLE #0: Sat Mar 14
20:06:04 CET 2009
r...@top.uugrn.org:/usr/obj/usr/src_RELENG_7/sys/TOP  i386


== /usr/src/sys/i386/conf/TOP ==
include GENERIC
ident   TOP
nodeviceplip# TCP/IP over parallel

== kldstat ==
Id Refs AddressSize Name
 19 0xc040 9ec994   kernel
 21 0xc0ded000 164e8geom_mirror.ko
 31 0xc0e04000 6a45cacpi.ko
 41 0xc5b9a000 e000 ipfw.ko
 51 0xc5c94000 4000 logo_saver.ko
 61 0xc5cf4000 4000 nullfs.ko
 71 0xc5cfc000 4000 fdescfs.ko



== Hardware == 

The machine ran about 30 months without crashes, at last with 6.4-RELEASE. 
The storage was on a 3ware with two attached SATA150 drives. 

Then we replaced the old 3ware + 2xSATA by two onboard-attached SATA300
drives with geom mirror configuration. The new OS is 7.1-STABLE from Mar
14th, which crashed with "vm_page_insert: page already inserted" under
i/o load.

geom mirror status:
  NameStatus  Components
mirror/TOPRAID  COMPLETE  ad4
  ad6

atap...@pci0:0:31:2:class=0x010601 card=0x778015d9 chip=0x27c18086 rev=0x01 
hdr=0x00
vendor = 'Intel Corporation'
device = '82801GB I/O Controller Hub SATA cc=AHCI'
class  = mass storage
subclass   = SATA


Mar 14 22:45:37 top kernel: atapci1:  port 
0x6898-0x689f,0x687c-0x687f,0x6890-0x6897,0x6878-0x687b,0x6880-0x688f mem 
0xed000400-0xed0007ff irq 19 at device 31.2 on pci0
Mar 14 22:45:37 top kernel: atapci1: [ITHREAD]
Mar 14 22:45:37 top kernel: atapci1: AHCI Version 01.10 controller with 4 ports 
detected
Mar 14 22:45:37 top kernel: ata2:  on atapci1
Mar 14 22:45:37 top kernel: ata2: [ITHREAD]
Mar 14 22:45:37 top kernel: ata3:  on atapci1
Mar 14 22:45:37 top kernel: ata3: [ITHREAD]

 
Mar 14 22:45:37 top kernel: ad4: 381554MB  at 
ata2-master SATA300
Mar 14 22:45:37 top kernel: ad6: 381554MB  at 
ata3-master SATA300


== What happened ==
The crash happened while cvsupping from local cvsup-mirror, hence there
was pretty much read-write i/o on the geom while having some CPU load.

After rebooting the geom-mirror was degraded and rebuilded within some 
couple of hours. I didn't have had any crashes since then but don't 
want to provoke this since this server is kind of "productive".

Maybe those "environmental" information does help someone to spot the
cause of this error.

Regards
Raphael Becker

-- 
Raphael Beckerhttp://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgpl3pAHJVDMF.pgp
Description: PGP signature


Re: GCC build causes panic: page already inserted

2009-03-18 Thread Raphael Becker
On Thu, Mar 19, 2009 at 12:34:56AM +0100, Raphael Becker wrote:
> info.0 says:
> Dump header from device /dev/label/TOPSWAP
>   Architecture: i386
>   Architecture Version: 2
>   Dump Length: 246185984B (234 MB)
>   Blocksize: 512
>   Dumptime: Sat Mar 14 22:43:46 2009
>   Hostname: top.uugrn.org
>   Magic: FreeBSD Kernel Dump
>   Version String: FreeBSD 7.1-STABLE #0: Sat Mar 14 20:06:04 CET 2009
> r...@top.uugrn.org:/usr/obj/usr/src_RELENG_7/sys/TOP
>   Panic String: vm_page_insert: page already inserted
>   Dump Parity: 31664128
>   Bounds: 0
>   Dump Status: good

Some more details ... maybe someone will get somethin interesing from
this:

[r...@top /usr/obj/usr/src_RELENG_7/sys/TOP]# kgdb kernel.debug 
/var/crash/vmcore.0
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 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-marcel-freebsd"...

Unread portion of the kernel message buffer:
panic: vm_page_insert: page already inserted
cpuid = 1
Uptime: 1h41m26s
Physical memory: 2034 MB
Dumping 234 MB: 219 203 187

Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address   = 0x186a0
fault code  = supervisor read, page not present
instruction pointer = 0x20:0x186a0
stack pointer   = 0x28:0xe571da48
frame pointer   = 0x28:0xe571da68
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 = 4 (g_down)
trap number = 12
panic: page fault
cpuid = 1
 171 155 139 123 107 91 75 59 43 27 11

Reading symbols from /boot/kernel/geom_mirror.ko...Reading symbols from
/boot/kernel/geom_mirror.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/geom_mirror.ko
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/ipfw.ko...Reading symbols from
/boot/kernel/ipfw.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ipfw.ko
Reading symbols from /boot/kernel/logo_saver.ko...Reading symbols from
/boot/kernel/logo_saver.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/logo_saver.ko
Reading symbols from /boot/kernel/nullfs.ko...Reading symbols from
/boot/kernel/nullfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/nullfs.ko
Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from
/boot/kernel/fdescfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/fdescfs.ko
#0  doadump () at pcpu.h:196
196 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb)
(kgdb) where
#0  doadump () at pcpu.h:196
#1  0xc07d3a87 in boot (howto=260) at 
/usr/src_RELENG_7/sys/kern/kern_shutdown.c:418
#2  0xc07d3d59 in panic (fmt=Variable "fmt" is not available.) at 
/usr/src_RELENG_7/sys/kern/kern_shutdown.c:574
#3  0xc0a1d4ca in vm_page_insert (m=0xc3735b20, object=0xc1461200, 
pindex=Unhandled dwarf expression opcode 0x93) at 
/usr/src_RELENG_7/sys/vm/vm_page.c:665
#4  0xc0a1da29 in vm_page_alloc (object=0xc1461200, pindex=5785959, req=546) at 
/usr/src_RELENG_7/sys/vm/vm_page.c:1171
#5  0xc083bd6b in allocbuf (bp=0xc51fe0c8, size=16384) at 
/usr/src_RELENG_7/sys/kern/vfs_bio.c:2895
#6  0xc083f62d in getblk (vp=0xc58969b4, blkno=46287648, size=16384, slpflag=0, 
slptimeo=0, flags=Variable "flags" is not available.) at 
/usr/src_RELENG_7/sys/kern/vfs_bio.c:2666
#7  0xc083ffe4 in breadn (vp=0xc58969b4, blkno=Unhandled dwarf expression 
opcode 0x93) at /usr/src_RELENG_7/sys/kern/vfs_bio.c:786
#8  0xc084011c in bread (vp=0xc58969b4, blkno=Unhandled dwarf expression opcode 
0x93) at /usr/src_RELENG_7/sys/kern/vfs_bio.c:734
#9  0xc09edecb in ffs_vgetf (mp=0xc5852b40, ino=2897024, flags=2, 
vpp=0xe83338e8, ffs_flags=Variable "ffs_flags" is not available.) at 
/usr/src_RELENG_7/sys/ufs/ffs/ffs_vfsops.c:1477
#10 0xc09ee09e in ffs_vget (mp=0xc5852b40, ino=2897024, flags=2, 
vpp=0xe83338e8) at /usr/src_RELENG_7/sys/ufs/ffs/ffs_vfsops.c:1379 #11 
0xc09fa44b in ufs_lookup (ap=0xe8333930) at 
/usr/src_RELENG_7/sys/ufs/ufs/ufs_lookup.c:600
#12 0xc0aeada2 in VOP_CACHEDLOOKUP_APV (vop=0xc0c5ff00, a=0xe8333930) at 
vnode_if.c:153
#13 0xc084178c in vfs_cache_lookup (ap=0xe83339b4) at vnode_if.h:83
#14 0xc0aeca76 in VOP_LOOKUP_APV (vop=0xc0c60420, a=0xe83339b4) at vnode_if.c:99
#15 0xc08481b1 in lookup (ndp=0xe8333b7c) at vnode_if.h:57
#16 0xc0848eff in namei (ndp=0xe8333b7c) at 
/usr/src_RELENG_7/sys/kern/vfs_lookup.c:215
#17 0xc08600c7 in vn_open_cred (ndp=0xe8333b7c

Re: GCC build causes panic: page already inserted

2009-03-18 Thread Raphael Becker
On Mon, Mar 16, 2009 at 11:59:25AM -0600, Dan Allen wrote:
> I saw that someone else had this happen last week...  It is not a  
> hardware failure.
> 
> While building the latest GCC 4.4 from /usr/ports/lang/gcc44 I got a  
> core dump with the message
> 
>   vm_page_insert: page already inserted

I had the same thing on 7.1-STABLE with sources @2009-03-14 (last
Saturday). The machine had no hardware failures running 6.x...6.4 in 
the last 3 years running about 20..25 Jails.

Therefore I don't think it is a hardware error.

The crash happened during someone recompiling most of his packages in
jail while running cvsup on /usr/ports in another jail. So there was 
pretty much I/O and CPU usage. After crash the geom_mirror was degraded 
on ad4 (ad6 working).

I guess 
  a) the vmcore was successfully written to the SWAP 
  b) geom_mirror is unstable under heavy load, maybe it's the 
 origin of the crash. swap resides on that geom_mirror, too. 

I'm not yet able to get some useful information out of the 230MB vmcore.0
Maybe I may provide useful information about the crash if someone can
tell me about how to get theese from vmcore.0.

info.0 says:
Dump header from device /dev/label/TOPSWAP
  Architecture: i386
  Architecture Version: 2
  Dump Length: 246185984B (234 MB)
  Blocksize: 512
  Dumptime: Sat Mar 14 22:43:46 2009
  Hostname: top.uugrn.org
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 7.1-STABLE #0: Sat Mar 14 20:06:04 CET 2009
r...@top.uugrn.org:/usr/obj/usr/src_RELENG_7/sys/TOP
  Panic String: vm_page_insert: page already inserted
  Dump Parity: 31664128
  Bounds: 0
  Dump Status: good


Regards
Raphael Becker

-- 
Raphael Beckerhttp://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgpeqlW0RKPEi.pgp
Description: PGP signature


Re: USB keyboard locking up on 7-RELEASE/amd64

2008-04-11 Thread Raphael Becker
On Wed, Apr 09, 2008 at 05:07:24PM -0500, H. Wade Minter wrote:
> The install went fine, but post-install I'm running into a problem  
> where the USB keyboard will just lock up.  I can still ping and SSH  
> into the system, but after about 2 minutes of activity, the keyboard  
> becomes nonresponsive.
 
As far I understood this is caused by the BIOS which emulates PS/2 
for USB keyboard and mouse. So FreeBSD double-detects your keyboard as
PS/2 by atkbd(c) and directly via USB. 

There is no Option in the (my) BIOS to disable this USB-PS/2 emulation.
Banning atkbd(c) and psm from the kernel worked for me. 


$ cat /usr/src70/sys/amd64/conf/DELL755 
# Kernel-Config for Dell Optiplex 755 / amd64
#
# From: Baldur Gislason 
# To: freebsd-gnats-submit at FreeBSD.org
# Cc:  
# Subject: Re: usb/119509: USB flaky on Dell Optiplex 755
# Date: Mon, 4 Feb 2008 15:30:52 +
# 


include GENERIC
ident   DELL755

nodevice  atkbdc  # AT keyboard controller
nodevice  atkbd   # AT keyboard
nodevice  psm # PS/2 mouse


YMMV

Regards

Raphael

-- 
Raphael Becker  <[EMAIL PROTECTED]>  http://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgpC3DLmUJKwI.pgp
Description: PGP signature


Re: Using /etc/rc.d/geli with labeled devices on 6.3

2008-03-20 Thread Raphael Becker
On Tue, Mar 18, 2008 at 04:04:52PM +0100, Raphael Becker wrote:

[ getting /dev/label/FOOcrypt.eli configured through /etc/rc.d/geli ]

> How should I set up /etc/rc.conf to get this by /etc/rc.d/geli on boot?
> 
> geli_enable="YES"
> geli_devices="label/FOOcrypt"
> geli_label/FOOcrypt_flags="-k /root/keys/geli.FOO.key"
>  ^^ 
> This won't work. How?

geli_label_FOOcrytp_flags="-k /root/keys/geli.FOO.key" 
 ^^^

from /etc/rc.d/geli:
provider_=`ltr ${provider} '/' '_'`
eval "flags=\${geli_${provider_}_flags}"

Seems to work. This should be documented in rc.conf(5) as ppl who use 
'geli' for encryption might also know about and use 'glabel'.

Regards
Raphael Becker
-- 
Raphael Becker  <[EMAIL PROTECTED]>  http://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgpALpBity1uU.pgp
Description: PGP signature


Using /etc/rc.d/geli with labeled devices on 6.3

2008-03-18 Thread Raphael Becker
Hi,

given that /dev/ad12 is a geli encryptet device, you might set up
/etc/rc.conf like

geli_enable="YES"
geli_devices="ad12"
geli_ad12_flags="-k /root/keys/geli.ad12.key"

I don't like absolute device names (they might change) so I label them
e.g. FOOcrypt so it show up like /dev/label/FOOcrypt

Attaching the FOOcrypt manually works like

# geli attach -k /root/geli.FOO.key /dev/label/FOOcrypt 
Enter passphrase:

The UFS on /dev/label/FOOcrypt.eli is labeled FOO[1]  so 
it will be available on /dev/ufs/FOO and can be mounted:

# mount /dev/ufs/FOO

How should I set up /etc/rc.conf to get this by /etc/rc.d/geli on boot?

geli_enable="YES"
geli_devices="label/FOOcrypt"
geli_label/FOOcrypt_flags="-k /root/keys/geli.FOO.key"
 ^^ 
This won't work. How?

TIA.

Regards
Raphael Becker

[1] newfs -L FOO ... /dev/label/FOOcrypt.eli --> /dev/ufs/FOO

-- 
Raphael Becker  <[EMAIL PROTECTED]>  http://rabe.uugrn.org/
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


pgpyJmUaycp48.pgp
Description: PGP signature