date:20090927

Re: 8-RC1: iwn0 suspend/resume issues

2009-09-27 Thread Scott Lambert

On Sun, Sep 27, 2009 at 12:50:34PM -0700, Sam Leffler wrote:
> Scott Lambert wrote:
> > I did just notice:
> > 
> > iwn0: Reg Domain: \M^?\M^?\M^?\M^?iwn0: iwn_mem_lock: could not lock memory
> > 
> > Maybe I should set the regulatory domain?  But having just spent a few
> > minutes trying, it doesn't seem to be interested...
> > 
> > lamb...@slambert:~> sudo ifconfig wlan0 regdomain FCC
> > ifconfig: SIOCS80211: Device busy
> 
> wlan0 is marked UP; you cannot set regulatory state unless the interface
> is down.
> 
> > Exit 1
> > lamb...@slambert:~> sudo ifconfig iwn0 regdomain FCC
> > ifconfig: unable to get regulatory domain info: Invalid argument
> 
> iwn0 is the wrong interface to use; use wlan0

Ah, a little education is a dangerous thing.  Setting regdomain does not
give errors when I use wlan0 and it is configured down.  

> Regarding regdomain stuff; AFAIK you cannot alter regulatory state of
> any intel wireless card; it will enforce whatever is in the EEPROM.
> Can't recall if the driver pushes EEPROM state up to net80211; if
> not then it should and it should also reject all requests to change
> regulatory until there's fw that supports it.

It did let me set country to jp and regdomain to JAPAN while playing.
That may not mean much.  The iwn driver is confused right now because it
has been through a suspend and resume cycle.
 
Thank you, Sam!

-- 
Scott LambertKC5MLE   Unix SysAdmin
lamb...@lambertfam.org

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

locate(1) ZFS addition

2009-09-27 Thread CmdLnKid



I just came across what I believe to be just a oversight on locate(1). By 
default as stated in its locate.rc file in /etc it states that the default 
file systems that will be searched is "ufs ext2fs". Would it be wise to have the 
default be "ufs zfs xfs ext2fs" ? or some other combination.


PS: Should a PR be filed for this ?

Best regards

--

  - (2^(N-1))
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 7.2-release/amd64: panic, spin lock held too long

2009-09-27 Thread C. C. Tang


C. C. Tang wrote:

Attilio Rao wrote:

2009/9/22 C. C. Tang :



I have patched the sched_ule.c and did a make buildkernel & make
installkernel (is buildworld and installworld necessary?), 
rebooted and

the
machine is running now.
I will post here again if there is any update.

My server is up for 3.5 days now with HyperThreading & powerd enabled.
No panic occured yet.


Usually how long did it take to panic?

Attilio



It is rather random, but will usually panic within one week.
Anyway my server will keep running and I will report if it has any problem.

Thanks,
C.C.


My server is up for 9.5 days now. Seems working fine.

C.C.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8.0-RC1 panic attaching ppc

2009-09-27 Thread Daniel O'Connor

On Sun, 27 Sep 2009, Alan Cox wrote:
> Ok, now I can explain what is happening.  The kernel is using 1GB
> pages to implement the direct map.  Unfortunately, pmap_extract()
> doesn't know how to handle a 1GB page mapping.  pmap_kextract() only
> works by an "accident" of its different implementation.  In other
> words, it should not be relied upon to work either.
>
> Please revert whatever patch John gave you and try the attached
> patch. It simply disables the use of 1GB page mapping by the direct
> map.

Your patch fixes (works around?) the problem.

Thanks!

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


signature.asc
Description: This is a digitally signed message part.

Re: Excessivly cheap USB device issue

2009-09-27 Thread Mike Tancsa


At 10:47 AM 9/27/2009, Robert Noland wrote:
> Sep 27 14:29:18 midget kernel: da1: Attempt to query device size 
failed: NOT READY, Medium not present

>
> If I connect a CF card to da1 and run 'fdisk da1' I get..
> [midget 0:06] ~ >fdisk da1
> load: 0.29  cmd: fdisk 69630 [cgticb] 1.50r 0.00u 0.00s 0% 1160k
> load: 0.19  cmd: fdisk 69630 [cbwait] 24.42r 0.00u 0.00s 0% 1160k
> load: 0.19  cmd: fdisk 69630 [cbwait] 27.01r 0.00u 0.00s 0% 1160k
> fdisk: unable to get correct path for da1: Input/output error
>
> [midget 0:05] ~ >sudo usbconfig -u 5 -a 2 dump_device_desc
> ugen5.2:  at usbus5, cfg=0 md=HOST 
spd=HIGH (480Mbps) pwr=ON

>
>   bLength = 0x0012
>   bDescriptorType = 0x0001
>   bcdUSB = 0x0200
>   bDeviceClass = 0x
>   bDeviceSubClass = 0x
>   bDeviceProtocol = 0x
>   bMaxPacketSize0 = 0x0040
>   idVendor = 0x058f
>   idProduct = 0x6362
>   bcdDevice = 0x0129
> load: 0.21  cmd: usbconfig 69643 [WCTRL] 1.73r 0.00u 0.00s 0% 1080k
>   iManufacturer = 0x0001  
> load: 0.19  cmd: usbconfig 69643 [WCTRL] 8.56r 0.00u 0.00s 0% 1104k
>   iProduct = 0x0002  
>   iSerialNumber = 0x0003  
>   bNumConfigurations = 0x0001
>
> Perhaps some quirk would help but I'm not sure which one :)

I also have a similar device, which I've been messing with a bit the
last couple of days.  In your case, it isn't seeing the media, just the
"drive".  I've had to try various combinations of unplugging the adapter
from usb, inserting the media then plugging it back in.  It does seem to
work fairly reliably if you boot with the media already inserted, but it
doesn't seem to detect media change at all.



I get around it (on my cheap reader) by  always doing a
cat /dev/null > /dev/da1
whever I change or insert new media into the reader

That seems to work with the gear I have 99% of the time.

---Mike

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: glabel+gmirror (8.0-RC1 problem)

2009-09-27 Thread Oliver Lehmann

Hi,

that gmirror together with glabel cannot be used looks like a problem
introduced with 8.0-RC1 to me.

What I did:

2. Installation
3. reboot
4. mirror Root-hdd
sysctl kern.geom.debugflags=17
gmirror label -vb round-robin gm0 da0
gmirror load
echo 'geom_mirror_load="YES"' >> /boot/loader.conf
echo 'geom_label_load="YES"' >> /boot/loader.conf

5. adjust fstab
vi /etc/fstab
:%s/ad/mirror\/gm/g

6. reboot

7. mirror Root-hdd
gmirror insert gm0 da1
gmirror status

8. wait until gmirror is done

9. reboot

10. glabel status

With 8.0-RC1 I see only da0s1a, da0s1d, da0s1e and da0s1f as Components
shown by glabel(8).
With 8.0-BETA3 I see mirror/gm0s1a, mirror/gm0s1d, mirror/gm0s1e and
mirror/gm0s1f as Components which would be correct here.

I use old IBM 2GB DFHS harddisks for that tests. I have a bunch of them
so I used for both tries "fresh" drives.

I can't see what has changed here between BETA3 and RC1 but something
must have changed in a way which renders gmirror together with glabel on
RC1 non-working.

I just did that as testing the configuration I want to use for my
fileserver when the new harddisks arrived but now I'm not sure If I
should rely on gmirror+glabel

Oliver Lehmann wrote:

> Hi,
> 
> I try to glabel (tunefs -L) my gmirror RAID-1. After labeling
> the /usr, /tmp, /var partition, glabel status shows the labes are being
> assigned to the mirror/gm0s1* partitions.
> I then changed my /etc/fstab to use the ufs/ devices instead of
> the mirror/gm0s1* devices.
> After the system got rebootet, the system is now unable to mount the
> partitions and puts me into the single user mode.
> glabel status shows me now, that the labels are all assigned to da0s1*
> instead of mirror/gm0s1*. How did this happen? glabel never shows the
> mirror/gm0s1* partitions anyhow - only after labeling them. But after
> reboot the labels are reassigned to da0s1* and glabel does not show any
> mirror/gm0s1* label.
> 
> How can I prevent this to happen?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8-RC1: iwn0 suspend/resume issues

2009-09-27 Thread Sam Leffler

Scott Lambert wrote:
> Threading broken to avoid potential takover of ral0 thread.
> 
> On Sat, Sep 26, 2009 at 02:33:26AM +, Brandon Gooch wrote:
>> On Fri, Sep 25, 2009 at 11:29 PM, Scott Lambert  
>> wrote:
>>> iwn does not function after resume so I've actually run ethernet cables
>>> to where I use the laptop now.
>> I have to unload the if_iwn module on suspend, and reload it on resume
>> (via /etc/rc.[suspend|resume], of course).
>>
>> Have you tried that?
> 
> I am glad to hear that it works for somebody.  There is hope!  I have:
> 
>  kldunload if_iwn
> 
> in /etc/rc.suspend and:
> 
>  kldload if_iwn
> 
> in /etc/rc.resume.
> 
> On resume there are lots of
> 
> iwn0: iwn_mem_lock: could not lock memory
> 
> and
> 
> iwn0: iwn_transfer_microcode: could not load boot firmware
> iwn0: iwn_transfer_firmware: could not load boot firmware, error 60
> iwn0: iwn_init_locked: could not load firmware, error 60
> 
> I did just notice:
> 
> iwn0: Reg Domain: \M^?\M^?\M^?\M^?iwn0: iwn_mem_lock: could not lock memory
> 
> Maybe I should set the regulatory domain?  But having just spent a few
> minutes trying, it doesn't seem to be interested...
> 
> lamb...@slambert:~> sudo ifconfig wlan0 regdomain FCC
> ifconfig: SIOCS80211: Device busy

wlan0 is marked UP; you cannot set regulatory state unless the interface
is down.

> Exit 1
> lamb...@slambert:~> sudo ifconfig iwn0 regdomain FCC
> ifconfig: unable to get regulatory domain info: Invalid argument

iwn0 is the wrong interface to use; use wlan0

> Exit 1
> 
> Same result with the other regulatory domains.  Maybe iwn just doesn't
> support it?
> 
> lamb...@slambert:~> sudo ifconfig wlan0 list regdomain
> :regdomain 0 country US anywhere -ecm
> 
> 
> 
>   http://www.lambertfam.org/~lambert/laptop/TravelMate_5720-6911  
> 
> has my rc.[suspend|resume] and dmesg.[boot|resume] showing the
> issues.  Other stuff in there that might be relevant too, if anyone is
> interested.
> 

Regarding regdomain stuff; AFAIK you cannot alter regulatory state of
any intel wireless card; it will enforce whatever is in the EEPROM.
Can't recall if the driver pushes EEPROM state up to net80211; if not
then it should and it should also reject all requests to change
regulatory until there's fw that supports it.

Sam
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8.0-RC1: kernel page fault in NLM master thread (VIMAGE or ZFS related?)

2009-09-27 Thread Dag-Erling Smørgrav

Jamie Gritton  writes:
> Index: kern/vfs_export.c
> ===
> --- kern/vfs_export.c (revision 197506)
> +++ kern/vfs_export.c (working copy)
> @@ -122,6 +122,8 @@
>   np->netc_anon->cr_uid = argp->ex_anon.cr_uid;
>   crsetgroups(np->netc_anon, argp->ex_anon.cr_ngroups,
>   argp->ex_anon.cr_groups);
> + np->netc_anon->cr_prison = &prison0;
> + prison_hold(np->netc_anon->cr_prison);
>   np->netc_numsecflavors = argp->ex_numsecflavors;
>   bcopy(argp->ex_secflavors, np->netc_secflavors,
>   sizeof(np->netc_secflavors));

You need to #include  for prison0...  See attached patch.

DES
-- 
Dag-Erling Smørgrav - d...@des.no

Index: sys/kern/vfs_export.c
===
--- sys/kern/vfs_export.c	(revision 197539)
+++ sys/kern/vfs_export.c	(working copy)
@@ -40,6 +40,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -122,6 +123,8 @@
 		np->netc_anon->cr_uid = argp->ex_anon.cr_uid;
 		crsetgroups(np->netc_anon, argp->ex_anon.cr_ngroups,
 		argp->ex_anon.cr_groups);
+		np->netc_anon->cr_prison = &prison0;
+		prison_hold(np->netc_anon->cr_prison);
 		np->netc_numsecflavors = argp->ex_numsecflavors;
 		bcopy(argp->ex_secflavors, np->netc_secflavors,
 		sizeof(np->netc_secflavors));
@@ -206,6 +209,8 @@
 	np->netc_anon->cr_uid = argp->ex_anon.cr_uid;
 	crsetgroups(np->netc_anon, argp->ex_anon.cr_ngroups,
 	np->netc_anon->cr_groups);
+	np->netc_anon->cr_prison = &prison0;
+	prison_hold(np->netc_anon->cr_prison);
 	np->netc_numsecflavors = argp->ex_numsecflavors;
 	bcopy(argp->ex_secflavors, np->netc_secflavors,
 	sizeof(np->netc_secflavors));
Index: sys/rpc/rpcsec_gss/svc_rpcsec_gss.c
===
--- sys/rpc/rpcsec_gss/svc_rpcsec_gss.c	(revision 197539)
+++ sys/rpc/rpcsec_gss/svc_rpcsec_gss.c	(working copy)
@@ -449,6 +449,8 @@
 	cr->cr_uid = cr->cr_ruid = cr->cr_svuid = uc->uid;
 	cr->cr_rgid = cr->cr_svgid = uc->gid;
 	crsetgroups(cr, uc->gidlen, uc->gidlist);
+	cr->cr_prison = &prison0;
+	prison_hold(cr->cr_prison);
 	*crp = crhold(cr);
 
 	return (TRUE);
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

6.4-STABLE @r197533: iwi(4) implicated in page fault while in kernel mode

2009-09-27 Thread David Wolfskill

See  for more
details.  Here's the first part of it:

g1-89.catwhisker.org dumped core - see ./vmcore.9

Sun Sep 27 10:24:20 PDT 2009

FreeBSD g1-89.catwhisker.org 6.4-STABLE FreeBSD 6.4-STABLE #695 r197533: Sun 
Sep 27 04:22:07 PDT 2009 
r...@g1-88.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY  i386

panic: page fault

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:
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x78
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc06ad115
stack pointer   = 0x28:0xe4528aa0
frame pointer   = 0x28:0xe4528aa4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 8027 (ifconfig)
trap number = 12
panic: page fault
Uptime: 3h11m29s
Dumping 767 MB (2 chunks)
  chunk 0: 1MB (159 pages) ... ok
  chunk 1: 767MB (196322 pages) 751 735 719 703 687 671 655 639 623 607 591 575 
559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 
239 223 207 191 175 159 143 127 111 95 79 63 47 31 15

Reading symbols from /boot/kernel/linux.ko...done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/if_iwi.ko...done.
Loaded symbols for /boot/kernel/if_iwi.ko
Reading symbols from /boot/kernel/firmware.ko...done.
Loaded symbols for /boot/kernel/firmware.ko
Reading symbols from /boot/kernel/acpi.ko...done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/linprocfs.ko...done.
Loaded symbols for /boot/kernel/linprocfs.ko
Reading symbols from /boot/modules/iwi_bss.ko...done.
Loaded symbols for /boot/modules/iwi_bss.ko
Reading symbols from /usr/local/modules/rtc.ko...done.
Loaded symbols for /usr/local/modules/rtc.ko
Reading symbols from /boot/kernel/radeon.ko...done.
Loaded symbols for /boot/kernel/radeon.ko
Reading symbols from /boot/kernel/drm.ko...done.
Loaded symbols for /boot/kernel/drm.ko
#0  doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) #0  doadump () at pcpu.h:165
#1  0xc068c1e6 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
#2  0xc068c47c in panic (fmt=0xc0957dd5 "%s")
at /usr/src/sys/kern/kern_shutdown.c:566
#3  0xc08fd5a4 in trap_fatal (frame=0xe4528a60, eva=120)
at /usr/src/sys/i386/i386/trap.c:838
#4  0xc08fcd42 in trap (frame=
  {tf_fs = 333447176, tf_es = 40, tf_ds = 780009512, tf_edi = -992778212, 
tf_esi = -985385088, tf_ebp = -464352604, tf_isp = -464352628, tf_ebx = 
-994579200, tf_edx = 0, tf_ecx = 4, tf_eax = -985385056, tf_trapno = 12, tf_err 
= 0, tf_eip = -1066741483, tf_cs = 32, tf_eflags = 65538, tf_esp = -985385088, 
tf_ss = -464352568}) at /usr/src/sys/i386/i386/trap.c:270
#5  0xc08ea1da in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6  0xc06ad115 in turnstile_setowner (ts=0xc4b7ed00, owner=0x4)
at /usr/src/sys/kern/subr_turnstile.c:456
#7  0xc06ad472 in turnstile_wait (lock=0xc554557c, owner=0x4, queue=0)
at /usr/src/sys/kern/subr_turnstile.c:661
#8  0xc0683082 in _mtx_lock_sleep (m=0xc554557c, tid=3309582208, opts=0, 
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:579
#9  0xc070a618 in rtrequest1 (req=1, info=0xe4528b60, ret_nrt=0xe4528b54)
at /usr/src/sys/net/route.c:792
#10 0xc070b0ff in rtinit (ifa=0xc5545500, cmd=1, flags=1)
at /usr/src/sys/net/route.c:1201
#11 0xc0727b41 in in_addprefix (target=0xc5545500, flags=1)
at /usr/src/sys/netinet/in.c:851
#12 0xc0727a6d in in_ifinit (ifp=0xc4922000, ia=0xc5545500, sin=0x4, scrub=0)
at /usr/src/sys/netinet/in.c:778
#13 0xc0726d68 in in_control (so=0xc543bde8, cmd=1, data=0xc54911c0 "iwi0", 
ifp=0xc4922000, td=0xc5443780) at /usr/src/sys/netinet/in.c:440
#14 0xc06fb2b8 in ifioctl (so=0xc543bde8, cmd=2151704858, 
data=0xc54911c0 "iwi0", td=0xc5443780) at /usr/src/sys/net/if.c:1612
#15 0xc06b4e7b in soo_ioctl (fp=0xc54437a0, cmd=2151704858, data=0xc54911c0, 
active_cred=0xc47d8d80, td=0xc5443780)
at /usr/src/sys/kern/sys_socket.c:214
#16 0xc06af31d in ioctl (td=0xc5443780, uap=0xe4528d04) at file.h:265
#17 0xc08fd8bb in syscall (frame=
  {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 134570944, tf_esi = 
134580448, tf_ebp = -1077941288, tf_isp = -464351900, tf_ebx = -2143262438, 
tf_edx = 134583233, tf_ecx = 134570944, tf_eax = 54, tf_trapno = 12, tf_err = 
2, tf_eip = 869574699, tf_cs = 51, tf_eflags = 646, tf_e

Re: problem with link aggregation failover

2009-09-27 Thread Ulrich Spörlein

On Sun, 27.09.2009 at 09:49:03 -0400, Daniel Eischen wrote:
> On Sun, 27 Sep 2009, Ulrich Spörlein wrote:
> 
> > On Sat, 12.09.2009 at 22:34:41 +0200, Maciej Jan Broniarz wrote:
> >> Hello,
> >>
> >> I am trying to configure lagg failover mode on 7.2.
> >>
> >> I do:
> >>
> >> # ifconfig xl0 up
> >> # ifconfig fxp0 up
> >> # ifconfig lagg0 create
> >> # ifconfig lagg0 up laggproto failover laggport xl0 laggport fxp0
> >> # dhclient lagg0
> >>
> >> And all seems to work ok. Still I disconnect the cable from the master 
> >> card the connection stops.
> >> Although fxp0 becomes active the connection is still dead. If I start 
> >> pinging any host from that machine
> >> the conection comes back to live, but having ping in background all the 
> >> time is not the solution.
> >>
> >> Am I doing something wrong or have I missed something in the configuration?
> >
> > Well, where is xl0 and fxp0 connected to? My first bet would be a
> > standard switch, if so try setting both devices to the same MAC address.
> > Otherwise the peers you connect to will send the IP packets to the wrong
> > MAC address and only after a timeout (or a forced push thanks to the
> > ping) will get their ARP cache into shape.
> 
> lagg should automatically make xl0 and fxp0 appear at the same MAC
> address.  The only time you should have to manually set the MAC
> address would be on cloned interfaces such as wlan, because the
> cloned interfaces don't propagate the MAC change down to the
> interface from which they were cloned.

Interesting, thanks for the hint. I only use it for LAN/WLAN failover,
so that's why I have to do this anyway.

Regards,
Uli
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

glabel+gmirror

2009-09-27 Thread Oliver Lehmann

Hi,

I try to glabel (tunefs -L) my gmirror RAID-1. After labeling
the /usr, /tmp, /var partition, glabel status shows the labes are being
assigned to the mirror/gm0s1* partitions.
I then changed my /etc/fstab to use the ufs/ devices instead of
the mirror/gm0s1* devices.
After the system got rebootet, the system is now unable to mount the
partitions and puts me into the single user mode.
glabel status shows me now, that the labels are all assigned to da0s1*
instead of mirror/gm0s1*. How did this happen? glabel never shows the
mirror/gm0s1* partitions anyhow - only after labeling them. But after
reboot the labels are reassigned to da0s1* and glabel does not show any
mirror/gm0s1* label.

How can I prevent this to happen?

-- 
 Oliver Lehmann
  http://www.pofo.de/
  http://wishlist.ans-netz.de/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Excessivly cheap USB device issue

2009-09-27 Thread Robert Noland

On Mon, 2009-09-28 at 00:09 +0930, Daniel O'Connor wrote:
> I have a very cheap USB CF/SD/SM/MS connected to an 8.0-RC1 system and
>  it is detected, ie..
> Sep 27 14:29:18 midget kernel: da0 at umass-sim0 bus 0 target 0 lun 0
> Sep 27 14:29:18 midget kernel: da0:  Removable 
> Direct Access SCSI-0 device
> Sep 27 14:29:18 midget kernel: da0: 40.000MB/s transfers
> Sep 27 14:29:18 midget kernel: da0: Attempt to query device size failed: NOT 
> READY, Medium not present
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): TEST UNIT READY. 
> CDB: 0 20 0 0 0 0
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): CAM Status: SCSI 
> Status Error
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): SCSI Status: Check 
> Condition
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): NOT READY 
> csi:0,aa,55,40 asc:3a,0
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): Medium not present
> Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): Unretryable error
> Sep 27 14:29:18 midget kernel: da1 at umass-sim0 bus 0 target 0 lun 1
> Sep 27 14:29:18 midget kernel: da1:  Removable 
> Direct Access SCSI-0 device
> Sep 27 14:29:18 midget kernel: da1: 40.000MB/s transfers
> Sep 27 14:29:18 midget kernel: da1: Attempt to query device size failed: NOT 
> READY, Medium not present
> 
> If I connect a CF card to da1 and run 'fdisk da1' I get..
> [midget 0:06] ~ >fdisk da1
> load: 0.29  cmd: fdisk 69630 [cgticb] 1.50r 0.00u 0.00s 0% 1160k
> load: 0.19  cmd: fdisk 69630 [cbwait] 24.42r 0.00u 0.00s 0% 1160k
> load: 0.19  cmd: fdisk 69630 [cbwait] 27.01r 0.00u 0.00s 0% 1160k
> fdisk: unable to get correct path for da1: Input/output error
> 
> [midget 0:05] ~ >sudo usbconfig -u 5 -a 2 dump_device_desc
> ugen5.2:  at usbus5, cfg=0 md=HOST spd=HIGH 
> (480Mbps) pwr=ON
> 
>   bLength = 0x0012
>   bDescriptorType = 0x0001
>   bcdUSB = 0x0200
>   bDeviceClass = 0x
>   bDeviceSubClass = 0x
>   bDeviceProtocol = 0x
>   bMaxPacketSize0 = 0x0040
>   idVendor = 0x058f
>   idProduct = 0x6362
>   bcdDevice = 0x0129
> load: 0.21  cmd: usbconfig 69643 [WCTRL] 1.73r 0.00u 0.00s 0% 1080k
>   iManufacturer = 0x0001  
> load: 0.19  cmd: usbconfig 69643 [WCTRL] 8.56r 0.00u 0.00s 0% 1104k
>   iProduct = 0x0002  
>   iSerialNumber = 0x0003  
>   bNumConfigurations = 0x0001
> 
> Perhaps some quirk would help but I'm not sure which one :)

I also have a similar device, which I've been messing with a bit the
last couple of days.  In your case, it isn't seeing the media, just the
"drive".  I've had to try various combinations of unplugging the adapter
from usb, inserting the media then plugging it back in.  It does seem to
work fairly reliably if you boot with the media already inserted, but it
doesn't seem to detect media change at all.

robert.

-- 
Robert Noland 
FreeBSD

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Excessivly cheap USB device issue

2009-09-27 Thread Daniel O'Connor

I have a very cheap USB CF/SD/SM/MS connected to an 8.0-RC1 system and
 it is detected, ie..
Sep 27 14:29:18 midget kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Sep 27 14:29:18 midget kernel: da0:  Removable 
Direct Access SCSI-0 device
Sep 27 14:29:18 midget kernel: da0: 40.000MB/s transfers
Sep 27 14:29:18 midget kernel: da0: Attempt to query device size failed: NOT 
READY, Medium not present
Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): TEST UNIT READY. CDB: 
0 20 0 0 0 0
Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): CAM Status: SCSI 
Status Error
Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): SCSI Status: Check 
Condition
Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): NOT READY 
csi:0,aa,55,40 asc:3a,0
Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): Medium not present
Sep 27 14:29:18 midget kernel: (probe7:umass-sim0:0:0:1): Unretryable error
Sep 27 14:29:18 midget kernel: da1 at umass-sim0 bus 0 target 0 lun 1
Sep 27 14:29:18 midget kernel: da1:  Removable 
Direct Access SCSI-0 device
Sep 27 14:29:18 midget kernel: da1: 40.000MB/s transfers
Sep 27 14:29:18 midget kernel: da1: Attempt to query device size failed: NOT 
READY, Medium not present

If I connect a CF card to da1 and run 'fdisk da1' I get..
[midget 0:06] ~ >fdisk da1
load: 0.29  cmd: fdisk 69630 [cgticb] 1.50r 0.00u 0.00s 0% 1160k
load: 0.19  cmd: fdisk 69630 [cbwait] 24.42r 0.00u 0.00s 0% 1160k
load: 0.19  cmd: fdisk 69630 [cbwait] 27.01r 0.00u 0.00s 0% 1160k
fdisk: unable to get correct path for da1: Input/output error

[midget 0:05] ~ >sudo usbconfig -u 5 -a 2 dump_device_desc
ugen5.2:  at usbus5, cfg=0 md=HOST spd=HIGH 
(480Mbps) pwr=ON

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0040
  idVendor = 0x058f
  idProduct = 0x6362
  bcdDevice = 0x0129
load: 0.21  cmd: usbconfig 69643 [WCTRL] 1.73r 0.00u 0.00s 0% 1080k
  iManufacturer = 0x0001  
load: 0.19  cmd: usbconfig 69643 [WCTRL] 8.56r 0.00u 0.00s 0% 1104k
  iProduct = 0x0002  
  iSerialNumber = 0x0003  
  bNumConfigurations = 0x0001

Perhaps some quirk would help but I'm not sure which one :)

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


signature.asc
Description: This is a digitally signed message part.

Re: problem with link aggregation failover

2009-09-27 Thread Daniel Eischen


On Sun, 27 Sep 2009, Ulrich Sp??rlein wrote:


On Sat, 12.09.2009 at 22:34:41 +0200, Maciej Jan Broniarz wrote:

Hello,

I am trying to configure lagg failover mode on 7.2.

I do:

# ifconfig xl0 up
# ifconfig fxp0 up
# ifconfig lagg0 create
# ifconfig lagg0 up laggproto failover laggport xl0 laggport fxp0
# dhclient lagg0

And all seems to work ok. Still I disconnect the cable from the master card the 
connection stops.
Although fxp0 becomes active the connection is still dead. If I start pinging 
any host from that machine
the conection comes back to live, but having ping in background all the time is 
not the solution.

Am I doing something wrong or have I missed something in the configuration?


Well, where is xl0 and fxp0 connected to? My first bet would be a
standard switch, if so try setting both devices to the same MAC address.
Otherwise the peers you connect to will send the IP packets to the wrong
MAC address and only after a timeout (or a forced push thanks to the
ping) will get their ARP cache into shape.


lagg should automatically make xl0 and fxp0 appear at the same MAC
address.  The only time you should have to manually set the MAC
address would be on cloned interfaces such as wlan, because the
cloned interfaces don't propagate the MAC change down to the
interface from which they were cloned.

--
DE___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How to upgrade kernel with gmirror boot?

2009-09-27 Thread Chris Shenton



On Sep 26, 2009, at 5:47 PM, Stefan Bethke wrote:


Am 26.09.2009 um 21:04 schrieb Chris Shenton:


PS: Current "gmirror list" output:

$ gmirror list
Geom name: boot
State: COMPLETE
Components: 1

   ^^^

There's your problem: your mirror consist of only ad6s1a.  You need  
to add ad4s1a using gmirror insert, or tell your BIOS to boot from  
the second disk.


That was it, exactly. I've been running with a broken mirror all this  
time, doh!  Added the second disk partition and was able to build and  
install kernel and boot from it.


Many thanks.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

NFS server replies on wrong IP

2009-09-27 Thread Daniel O'Connor

Hi,
I recently upgraded a system from 7.x to 8.0-RC1 (well, got new guts for 
it and copied the data over..) and I am having trouble getting NFS to 
work.

I have re0 like so
re0: flags=8943 metric 0 
mtu 1500

options=389b
ether 00:24:1d:d1:92:cc
inet 10.0.2.1 netmask 0xff00 broadcast 10.0.2.255
inet 10.0.2.3 netmask 0x broadcast 10.0.2.3
inet 10.0.2.4 netmask 0x broadcast 10.0.2.4
inet 10.0.2.7 netmask 0x broadcast 10.0.2.7
media: Ethernet autoselect (1000baseT )
status: active

and when I try and NFS mount something on 10.0.2.7 I see that the reply 
comes from the wrong address (10.0.2.1). ie from wireshark..
7   0.80170410.0.2.110.0.2.103  NFS V3 NULL Reply 
(Call In 6)
8   0.80274210.0.2.103  10.0.2.1ICMPDestination 
unreachable (Port 
unreachable)

Interestingly Linux works OK, but perhaps it specifically allows it some 
how?

I can work around this by using -h to bind to 10.0.2.7 though, which is 
what I did on 7.x. I was wondering if there was a "correct" solution 
though.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


signature.asc
Description: This is a digitally signed message part.

8-RC1: iwn0 suspend/resume issues

2009-09-27 Thread Scott Lambert

Threading broken to avoid potential takover of ral0 thread.

On Sat, Sep 26, 2009 at 02:33:26AM +, Brandon Gooch wrote:
> On Fri, Sep 25, 2009 at 11:29 PM, Scott Lambert  
> wrote:
> > iwn does not function after resume so I've actually run ethernet cables
> > to where I use the laptop now.
> 
> I have to unload the if_iwn module on suspend, and reload it on resume
> (via /etc/rc.[suspend|resume], of course).
> 
> Have you tried that?

I am glad to hear that it works for somebody.  There is hope!  I have:

 kldunload if_iwn

in /etc/rc.suspend and:

 kldload if_iwn

in /etc/rc.resume.

On resume there are lots of

iwn0: iwn_mem_lock: could not lock memory

and

iwn0: iwn_transfer_microcode: could not load boot firmware
iwn0: iwn_transfer_firmware: could not load boot firmware, error 60
iwn0: iwn_init_locked: could not load firmware, error 60

I did just notice:

iwn0: Reg Domain: \M^?\M^?\M^?\M^?iwn0: iwn_mem_lock: could not lock memory

Maybe I should set the regulatory domain?  But having just spent a few
minutes trying, it doesn't seem to be interested...

lamb...@slambert:~> sudo ifconfig wlan0 regdomain FCC
ifconfig: SIOCS80211: Device busy
Exit 1
lamb...@slambert:~> sudo ifconfig iwn0 regdomain FCC
ifconfig: unable to get regulatory domain info: Invalid argument
Exit 1

Same result with the other regulatory domains.  Maybe iwn just doesn't
support it?

lamb...@slambert:~> sudo ifconfig wlan0 list regdomain
:regdomain 0 country US anywhere -ecm



  http://www.lambertfam.org/~lambert/laptop/TravelMate_5720-6911  

has my rc.[suspend|resume] and dmesg.[boot|resume] showing the
issues.  Other stuff in there that might be relevant too, if anyone is
interested.

-- 
Scott LambertKC5MLE   Unix SysAdmin
lamb...@lambertfam.org

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: problem with link aggregation failover

2009-09-27 Thread Ulrich Spörlein

On Sat, 12.09.2009 at 22:34:41 +0200, Maciej Jan Broniarz wrote:
> Hello,
> 
> I am trying to configure lagg failover mode on 7.2. 
> 
> I do:
> 
> # ifconfig xl0 up
> # ifconfig fxp0 up
> # ifconfig lagg0 create
> # ifconfig lagg0 up laggproto failover laggport xl0 laggport fxp0
> # dhclient lagg0 
> 
> And all seems to work ok. Still I disconnect the cable from the master card 
> the connection stops. 
> Although fxp0 becomes active the connection is still dead. If I start pinging 
> any host from that machine
> the conection comes back to live, but having ping in background all the time 
> is not the solution.
> 
> Am I doing something wrong or have I missed something in the configuration?

Well, where is xl0 and fxp0 connected to? My first bet would be a
standard switch, if so try setting both devices to the same MAC address.
Otherwise the peers you connect to will send the IP packets to the wrong
MAC address and only after a timeout (or a forced push thanks to the
ping) will get their ARP cache into shape.

Regards,
Uli
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: various kde programs spin in a poll/read loop against their respective config files

2009-09-27 Thread Patrick Lamaiziere

Le Sat, 26 Sep 2009 15:25:17 +0200,
Christof Schulze  a écrit :

> Hello everyone,

Hi,

> the discussion in -current and the behavior of my hard disk caused me
> to investigate. Whenever kde programs are run on this system, the
> hard disk will not spin down (even when excessive timeouts for syncs
> are in effect) So I ran truss against kwallet and plasma-desktop to
> find out they do the same thing:
> 
> stat("/home/erika/.kde4/share/apps/kwallet",{ mode=drwx-- 
> ,inode=56314,size=3,blksize=4096 }) = 0 (0x0)

> Shouldn't this be handled by fam/gamin in order to avoid this
> overhead? While it does not produce notable load it prevents my
> processor from saving power as well as spinning down the disks.

KDE with fam is broken, according to 
http://wiki.freebsd.org/KDE4

A work-around is to change the PollInterval in kdedrc
baby-jane:~$ less .kde4/share/config/kdedrc
[$Version]
update_info=kded.upd:kde3.0

[DirWatch]
PollInterval=6

(IMHO, for KDE issues you should ask on the kde-free...@kde.org mailing
list).

See also this thread :
http://mail.kde.org/pipermail/kde-freebsd/2009-September/006447.html

Regards.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 8-RC1: iwn0 suspend/resume issues

locate(1) ZFS addition

Re: 7.2-release/amd64: panic, spin lock held too long

Re: 8.0-RC1 panic attaching ppc

Re: Excessivly cheap USB device issue

Re: glabel+gmirror (8.0-RC1 problem)

Re: 8-RC1: iwn0 suspend/resume issues

Re: 8.0-RC1: kernel page fault in NLM master thread (VIMAGE or ZFS related?)

6.4-STABLE @r197533: iwi(4) implicated in page fault while in kernel mode

Re: problem with link aggregation failover

glabel+gmirror

Re: Excessivly cheap USB device issue

Excessivly cheap USB device issue

Re: problem with link aggregation failover

Re: How to upgrade kernel with gmirror boot?

NFS server replies on wrong IP

8-RC1: iwn0 suspend/resume issues

Re: problem with link aggregation failover

Re: various kde programs spin in a poll/read loop against their respective config files

19 matches

Site Navigation

Mail list logo

Footer information