From khaelin at gmail.com Sat Nov 1 04:11:00 2008 From: khaelin at gmail.com (Nicolas Martyanoff) Date: Sat Nov 1 04:11:09 2008 Subject: ZFS for a desktop computer Message-ID: <20081101114717.0ffc2ec8@valhala> Hi, I'm thinking about switching my main desktop to FreeBSD for various reasons (main one, I love it on my laptop and server), and I've been considering using ZFS. I'd like to have a disk-modular system, ie.: - Being able to have mirroring. - Being able to add new disks without effort. - Being able to add new disks AND mirroring disks (spare disks ?) at the same time. I'm gonna begin with 2x 1TB disks with mirroring, and I'd like to be able to add, if needed, new disks, for example 2x 1.5TB to get 2.5TB diskspace fully mirrored. The whole process shouldn't need to reinstall the system, or to change the slice/partition layout, ie. be totally transparent for the data. And for this particular need, ZFS seems to be the way to go. However, I'm a bit worried about FreeBSD's ZFS implementation: - I've got a 64bits dual core 2GHz CPU, but can't use an amd64 FreeBSD since Xen, NVidia drivers and wine don't work on it; but ZFS is said to be unsuitable for i386. - It's said you can't boot from a ZFS pool. So could you please tell me if using ZFS is ok for me, or should I use a gmirror system (but I don't think I can easily add new disks to this). Thank you. -- Nicolas Martyanoff http://codemore.org khaelin@gmail.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081101/9e1cecc5/signature.pgp From lme at FreeBSD.org Sat Nov 1 04:38:01 2008 From: lme at FreeBSD.org (Lars Engels) Date: Sat Nov 1 04:38:07 2008 Subject: ZFS for a desktop computer In-Reply-To: <20081101114717.0ffc2ec8@valhala> References: <20081101114717.0ffc2ec8@valhala> Message-ID: <20081101113759.GW8256@e.0x20.net> On Sat, Nov 01, 2008 at 11:47:17AM +0100, Nicolas Martyanoff wrote: > > Hi, > > I'm thinking about switching my main desktop to FreeBSD for various > reasons (main one, I love it on my laptop and server), and I've been > considering using ZFS. I'd like to have a disk-modular system, ie.: > > - Being able to have mirroring. > - Being able to add new disks without effort. > - Being able to add new disks AND mirroring disks (spare disks ?) at > the same time. > > I'm gonna begin with 2x 1TB disks with mirroring, and I'd like to be > able to add, if needed, new disks, for example 2x 1.5TB to get 2.5TB > diskspace fully mirrored. The whole process shouldn't need to reinstall > the system, or to change the slice/partition layout, ie. be totally > transparent for the data. > And for this particular need, ZFS seems to be the way to go. > > However, I'm a bit worried about FreeBSD's ZFS implementation: > > - I've got a 64bits dual core 2GHz CPU, but can't use an amd64 FreeBSD > since Xen, NVidia drivers and wine don't work on it; but ZFS is said > to be unsuitable for i386. > > - It's said you can't boot from a ZFS pool. > > So could you please tell me if using ZFS is ok for me, or should I use > a gmirror system (but I don't think I can easily add new disks to this). > > Thank you. You could try PC-BSD. There you can install the system with ZFS from the graphical installer. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081101/9e9ecb59/attachment.pgp From 000.fbsd at quip.cz Sat Nov 1 04:56:04 2008 From: 000.fbsd at quip.cz (Miroslav Lachman) Date: Sat Nov 1 04:56:12 2008 Subject: ZFS for a desktop computer In-Reply-To: <20081101114717.0ffc2ec8@valhala> References: <20081101114717.0ffc2ec8@valhala> Message-ID: <490C401A.9000700@quip.cz> Nicolas Martyanoff wrote: > Hi, > > I'm thinking about switching my main desktop to FreeBSD for various > reasons (main one, I love it on my laptop and server), and I've been > considering using ZFS. I'd like to have a disk-modular system, ie.: > > - Being able to have mirroring. > - Being able to add new disks without effort. > - Being able to add new disks AND mirroring disks (spare disks ?) at > the same time. > > I'm gonna begin with 2x 1TB disks with mirroring, and I'd like to be > able to add, if needed, new disks, for example 2x 1.5TB to get 2.5TB > diskspace fully mirrored. The whole process shouldn't need to reinstall > the system, or to change the slice/partition layout, ie. be totally > transparent for the data. > And for this particular need, ZFS seems to be the way to go. > > However, I'm a bit worried about FreeBSD's ZFS implementation: > > - I've got a 64bits dual core 2GHz CPU, but can't use an amd64 FreeBSD > since Xen, NVidia drivers and wine don't work on it; but ZFS is said > to be unsuitable for i386. > > - It's said you can't boot from a ZFS pool. > > So could you please tell me if using ZFS is ok for me, or should I use > a gmirror system (but I don't think I can easily add new disks to this). I can't speek of 64bit vs. 32bit. In case of booting problem, you can create small partition on your 1TB disks, put it in gmirror with UFS2, put boot loader code to the both disks, create /boot partition (or whole root) on it and use it just for booting (ad0s1 + ad1s1 will be gmirrored as gms1). Second partition (ad0s2 + ad1s2) can be used for zpool mirror. Another disks can be added as usual. The second way - you can use CF card + CF to IDE reduction to create /boot on it (UFS2) and use it just for booting the system. Or internally connected USB flash disk / small SSD. Useful links: http://wiki.freebsd.org/ZFS http://wiki.freebsd.org/JeremyChadwick/FreeBSD_7.x_on_a_ZFS_pool http://yds.coolrat.org/zfsboot.shtml https://ish.com.au/solutions/articles/freebsdzfs Miroslav Lachman From annona2 at gmail.com Sat Nov 1 06:52:26 2008 From: annona2 at gmail.com (G .Otsuji) Date: Sat Nov 1 06:52:32 2008 Subject: AMD Family 10h cpufreq driver In-Reply-To: <48D98E42.5040801@fluffles.net> References: <200809232121.m8NLLnig001691@softbank219001162114.bbtec.net> <26111.1222205043@critter.freebsd.dk> <200809232307.m8NN79th001888@softbank219001162114.bbtec.net> <48D98E42.5040801@fluffles.net> Message-ID: <200811011327.mA1DRKrk002761@localhost> Thank you very much for your kindness, and I came back again after a long time.sorry. I've spent quite time with cpufreq and acpidump , and renewed. Prelude: This is the first time of my kernel driver developping, so, i'm very happy with this, but some mistake would be there! Hardware P-state is a new power state of AMD Family 10h. powernow.c has also p-state. So i renamed pstate.c to hwpstate.c. From "acpidump -d" , my mother board has only two hw-pstate. It is very few for me. But my old kernel driver was dangerlous. So I decided to use for bios pstate. only 2 state though. but I think it is a compromise. and 1250 MHz is supported by the bios .so that's enough. Changelog: 1). with many verbose message without boot -v. you can hush up with hwpstate_verbose=0 in the source. (not sysctl, I don't know how to make it :-) ). 2). renamed to hwpstate.c. because powernow.c has also a pstate. 3). looking at the bios supported hardware P-state. So it is not dangerous ( I hope.) How to install and more: ( 0. shell> /etc/rc.d/powerd stop ) 1. shell> patch < "[this mail]" 2. shell> cp hwpstate.c /sys/i386/cpufreq/ 3. edit /sys/modules/cpufreq/Makefile and change, -SRCS+= est.c p4tcc.c powernow.c +SRCS+= est.c p4tcc.c powernow.c hwpstate.c 4. delete the line "device cpufreq" from KERNCONF file. and make kernel without cpufreq. 5. shell> cd /sys/module/cpufreq/ && make && make install 6. "umount -a" or "mount -u -o ro /somewhere" as possible, and sync;sync;sync; ) 7. shell> kldload cpufreq 8. the verbose messages will be there. 9, shell> sysctl dev.cpu.0.freq_levels 10, shell> sysctl dev.cpu.0.freq=XXXX 11, shell> /etc/rc.d/powerd start Please try this renewed cpufreq module if there is Phenom or Opteron [128]3XX 's. Thank you in advance. Best Regards, G. Otsuji --- /dev/null 2008-11-01 22:22:00.000000000 +0900 +++ ./hwpstate.c 2008-11-01 22:23:15.000000000 +0900 @@ -0,0 +1,372 @@ +/*- + * Copyright (c) 2008 Gen Otsuji + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted providing that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * + * THIS SOFTWARE IS PROVIDED BY THE AUTHOR``AS IS'' AND ANY EXPRESS OR + * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED + * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY + * DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, + * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING + * IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE + * POSSIBILITY OF SUCH DAMAGE. + */ + +/** + * Reference: + * Rev 3.06 March 26, 2008 - BIOS and Kernel Developer's Guide(BKDG) + * for AMD Family 10h Processors + */ + +#include +__FBSDID("$FreeBSD$"); + +#include +#include +#include +#include +#include +#include +#include +#include + +#include +#include + +#include "acpi_if.h" +#include "cpufreq_if.h" + +#define MSR_AMD10H_LIMIT 0xc0010061 +#define MSR_AMD10H_CONTROL 0xc0010062 +#define MSR_AMD10H_STATUS 0xc0010063 +#define MSR_AMD10H_CONFIG 0xc0010064 +#define AMD10H_PVI_MODE 1 +#define AMD10H_SVI_MODE 0 +#define AMD10H_MAX_STATES 16 + +/* for MSR_AMD10H_LIMIT C001_0061 */ +#define AMD10H_GET_PSTATE_MAX_VAL(msr) (((msr) >> 4) & 0xF) +/* for MSR_AMD10H_CONFIG C001_0064:68 */ +#define MSR_AMD10H_CUR_VID(msr) (((msr) >> 9) & 0x3F) +#define MSR_AMD10H_CUR_DID(msr) (((msr) >> 6) & 0x07) +#define MSR_AMD10H_CUR_FID(msr) ((msr) & 0x3F) + +/** + * setting this to 0 can hush up verbose messages. + */ +static int hwpstate_verbose = 1; + +struct hwpstate_setting { + int freq; /* CPU clock in Mhz or 100ths of a percent. */ + int volts; /* Voltage in mV. */ + int power; /* Power consumed in mW. */ + int lat; /* Transition latency in us. */ + int pstate_id; + device_t dev; /* Driver providing this setting. */ +}; + +struct hwpstate_softc { + device_t dev; + struct hwpstate_setting hwpstate_settings[AMD10H_MAX_STATES]; + int cfnum; + int voltage_mode; /* for AMD10H_PVI_MODE / AMD10H_SVI_MODE */ + int curpstate; +}; + +static void hwpstate_identify(driver_t * driver, device_t parent); +static int hwpstate_probe(device_t dev); +static int hwpstate_attach(device_t dev); +static int hwpstate_detach(device_t dev); +static int hwpstate_set(device_t dev, const struct cf_setting *cf); +static int hwpstate_get(device_t dev, struct cf_setting *cf); +static int hwpstate_settings(device_t dev, struct cf_setting *sets, int *count); +static int hwpstate_type(device_t dev, int *type); +static int hwpstate_shutdown(device_t dev); +static int hwpstate_features(driver_t * driver, u_int * features); + +static device_method_t hwpstate_methods[] = { + /* Device interface */ + DEVMETHOD(device_identify, hwpstate_identify), + DEVMETHOD(device_probe, hwpstate_probe), + DEVMETHOD(device_attach, hwpstate_attach), + DEVMETHOD(device_detach, hwpstate_detach), + DEVMETHOD(device_shutdown, hwpstate_shutdown), + + /* cpufreq interface */ + DEVMETHOD(cpufreq_drv_set, hwpstate_set), + DEVMETHOD(cpufreq_drv_get, hwpstate_get), + DEVMETHOD(cpufreq_drv_settings, hwpstate_settings), + DEVMETHOD(cpufreq_drv_type, hwpstate_type), + + /* ACPI interface */ + DEVMETHOD(acpi_get_features, hwpstate_features), + + {0, 0} +}; + +static devclass_t hwpstate_devclass; +static driver_t hwpstate_driver = { + "hwpstate", + hwpstate_methods, + sizeof(struct hwpstate_softc), +}; +DRIVER_MODULE(hwpstate, cpu, hwpstate_driver, hwpstate_devclass, 0, 0); + +static void +hwpstate_goto_pstate(device_t dev,int pstate) +{ + struct hwpstate_softc *sc; + uint64_t msr; + int i; + sc = device_get_softc(dev); + sc->curpstate = pstate; + wrmsr(MSR_AMD10H_CONTROL, pstate); + for(i=0;i<100;i++){ + msr=rdmsr(MSR_AMD10H_STATUS); + if(msr==pstate){ + break; + } + DELAY(100); + } + msr=rdmsr(MSR_AMD10H_STATUS); + if(hwpstate_verbose) + device_printf(dev,"Now P%d-state.\n",(int)msr); + return; +} + +static int +hwpstate_set(device_t dev, const struct cf_setting *cf) +{ + struct hwpstate_softc *sc; + struct hwpstate_setting *set; + int i; + if (cf == NULL) + return (EINVAL); + sc = device_get_softc(dev); + set = sc->hwpstate_settings; + for (i = 0; i < sc->cfnum; i++) + if (cf->freq == set[i].freq) + break; + if (i == sc->cfnum) + return EINVAL; + if(hwpstate_verbose) + device_printf(dev,"goto P%d-state\n",set[i].pstate_id); + sc->curpstate = set[i].pstate_id; + hwpstate_goto_pstate(dev,set[i].pstate_id); + return (0); +} + +static int +hwpstate_get(device_t dev, struct cf_setting *cf) +{ + struct hwpstate_softc *sc; + struct hwpstate_setting set; + sc = device_get_softc(dev); + if (cf == NULL) + return (EINVAL); + set = sc->hwpstate_settings[sc->curpstate]; + cf->freq = set.freq; + cf->volts = set.volts; + cf->power = CPUFREQ_VAL_UNKNOWN; + cf->lat = 16; + cf->dev = dev; + return (0); +} + +static int +hwpstate_settings(device_t dev, struct cf_setting *sets, int *count) +{ + struct hwpstate_softc *sc; + struct hwpstate_setting set; + int i; + if (sets == NULL || count == NULL) + return (EINVAL); + sc = device_get_softc(dev); + if (*count < sc->cfnum) + return (E2BIG); + for (i = 0; i < sc->cfnum; i++, sets++) { + set = sc->hwpstate_settings[i]; + sets->freq = set.freq; + sets->volts = set.volts; + sets->power = set.power; + sets->lat = set.lat; + sets->dev = set.dev; + } + *count = sc->cfnum; + return (0); +} + +static int +hwpstate_type(device_t dev, int *type) +{ + + if (type == NULL) + return (EINVAL); + *type = CPUFREQ_TYPE_ABSOLUTE; + return (0); +} + +static int +hwpstate_is_capable(void) +{ + u_int regs[4]; + if (strcmp(cpu_vendor, "AuthenticAMD") != 0 || + cpu_exthigh < 0x80000007) + return (FALSE); + do_cpuid(0x80000007, regs); + if (regs[3] & 0x80) { /* HwPstate Enable bit */ + return (TRUE); + } + return (FALSE); +} + +static void +hwpstate_identify(driver_t * driver, device_t parent) +{ + device_t child; + if (device_find_child(parent, "hwpstate", -1) != NULL) { + return; + } + if ((child = BUS_ADD_CHILD(parent, 10, "hwpstate", -1)) == NULL) + device_printf(parent, "hwpstate: add child failed\n"); +} + +static int +hwpstate_probe(device_t dev) +{ + struct hwpstate_softc *sc; + device_t perf_dev; + uint64_t msr; + int error, type; + if (resource_disabled("hwpstate", 0)) + return (ENXIO); + + /* this had not to be in hwpstate_identify() */ + if (hwpstate_is_capable() == FALSE) { + return (ENXIO); + } + perf_dev = device_find_child(device_get_parent(dev), "acpi_perf", -1); + if (perf_dev && device_is_attached(perf_dev)) { + error = CPUFREQ_DRV_TYPE(perf_dev, &type); + if (error == 0 && (type & CPUFREQ_FLAG_INFO_ONLY) == 0) + return (ENXIO); + } + sc = device_get_softc(dev); + switch (cpu_id) { + case 0x100f2A: /* family 10h rev.DR-BA */ + case 0x100f22: /* family 10h rev.DR-B2 */ + case 0x100f23: /* family 10h rev.DR-B3 */ + break; + default: + return (ENXIO); + } + msr = rdmsr(MSR_AMD10H_LIMIT); + sc->cfnum = AMD10H_GET_PSTATE_MAX_VAL(msr); + if (sc->cfnum == 0) { + device_printf(dev, "hardware-pstate is not supported by the bios.\n"); + return ENXIO; + } + device_set_desc(dev, "Cool`n'Quiet 2.0"); + return (0); +} + +static int +hwpstate_attach(device_t dev) +{ + struct hwpstate_softc *sc; + struct hwpstate_setting *set; + device_t F3; + uint64_t msr; + uint32_t cfg; + int i, vid, did, fid; + sc = device_get_softc(dev); + + /** + * following 24 means the 1st cpu. 25-31 instead of 24 is MP system. + * I don't have MP system . But only for reading from 1st cpu. + * so if the same 2*cpu , 4*cpu ,or 8*cpu , this can work , I think. + */ + F3 = pci_find_bsf(0, 24, 3); + cfg = pci_read_config(F3, 0xA0, 4); + if (cfg & 0x10) { /* PVI mode */ + if (hwpstate_verbose) + device_printf(dev, "PVI mode\n"); + sc->voltage_mode = AMD10H_PVI_MODE; + } else { /* SVI mode */ + if (hwpstate_verbose) + device_printf(dev, "SVI mode\n"); + sc->voltage_mode = AMD10H_SVI_MODE; + } + msr = rdmsr(MSR_AMD10H_LIMIT); + sc->cfnum = 1 + AMD10H_GET_PSTATE_MAX_VAL(msr); + if (hwpstate_verbose) + device_printf(dev, "you have %d P-state.\n", sc->cfnum); + set = sc->hwpstate_settings; + for (i = 0; i < sc->cfnum; i++, set++) { + msr = rdmsr(MSR_AMD10H_CONFIG + i); + if ((msr & 0x8000000000000000)) { + vid = MSR_AMD10H_CUR_VID(msr); + did = MSR_AMD10H_CUR_DID(msr); + fid = MSR_AMD10H_CUR_FID(msr); + set->freq = 100 * (fid + 0x10) / (1 << did); + if (sc->voltage_mode == AMD10H_PVI_MODE) { + /* 2.4.1.6.2 Parallel VID Encodings */ + if (vid >= 0x20) + set->volts = (7625 - 125 * (vid - 0x20)) / 10; + else + set->volts = 1550 - 25 * vid; + } else { + /* 2.4.1.6.3 Serial VID Encodings */ + if (vid >= 0x7F) + set->volts = 0; + else + set->volts = (15500 - 125 * vid) / 10; + } + if (hwpstate_verbose) + device_printf(dev, "freq=%dMHz volts=%dmV\n", set->freq, set->volts); + set->pstate_id = i; + set->power = CPUFREQ_VAL_UNKNOWN; + set->lat = 16; + set->dev = dev; + } + } + cpufreq_register(dev); + hwpstate_goto_pstate(dev,0); + return (0); +} + +static int +hwpstate_detach(device_t dev) +{ + + hwpstate_goto_pstate(dev,0); + return (cpufreq_unregister(dev)); +} + +static int +hwpstate_shutdown(device_t dev) +{ + + hwpstate_goto_pstate(dev,0); + return (0); +} + +static int +hwpstate_features(driver_t * driver, u_int * features) +{ + + *features = ACPI_CAP_PERF_MSRS; + return (0); +} From kris at FreeBSD.org Sat Nov 1 12:22:53 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Sat Nov 1 12:23:00 2008 Subject: ZFS for a desktop computer In-Reply-To: <20081101114717.0ffc2ec8@valhala> References: <20081101114717.0ffc2ec8@valhala> Message-ID: <490CACBC.9050805@FreeBSD.org> Nicolas Martyanoff wrote: > Hi, > > I'm thinking about switching my main desktop to FreeBSD for various > reasons (main one, I love it on my laptop and server), and I've been > considering using ZFS. I'd like to have a disk-modular system, ie.: > > - Being able to have mirroring. > - Being able to add new disks without effort. > - Being able to add new disks AND mirroring disks (spare disks ?) at > the same time. > > I'm gonna begin with 2x 1TB disks with mirroring, and I'd like to be > able to add, if needed, new disks, for example 2x 1.5TB to get 2.5TB > diskspace fully mirrored. The whole process shouldn't need to reinstall > the system, or to change the slice/partition layout, ie. be totally > transparent for the data. > And for this particular need, ZFS seems to be the way to go. > > However, I'm a bit worried about FreeBSD's ZFS implementation: > > - I've got a 64bits dual core 2GHz CPU, but can't use an amd64 FreeBSD > since Xen, NVidia drivers and wine don't work on it; but ZFS is said > to be unsuitable for i386. > > - It's said you can't boot from a ZFS pool. > > So could you please tell me if using ZFS is ok for me, or should I use > a gmirror system (but I don't think I can easily add new disks to this). It is tough to get ZFS to fit on an 32-bit system because of memory and address space limitations of the architecture. Kris From lists at jnielsen.net Sat Nov 1 12:37:59 2008 From: lists at jnielsen.net (John Nielsen) Date: Sat Nov 1 12:38:06 2008 Subject: ZFS for a desktop computer In-Reply-To: <20081101114717.0ffc2ec8@valhala> References: <20081101114717.0ffc2ec8@valhala> Message-ID: <200811011517.37640.lists@jnielsen.net> On Saturday 01 November 2008, Nicolas Martyanoff wrote: > I'm thinking about switching my main desktop to FreeBSD for various > reasons (main one, I love it on my laptop and server), and I've been > considering using ZFS. I'd like to have a disk-modular system, ie.: > > - Being able to have mirroring. > - Being able to add new disks without effort. > - Being able to add new disks AND mirroring disks (spare disks ?) at > the same time. > > I'm gonna begin with 2x 1TB disks with mirroring, and I'd like to be > able to add, if needed, new disks, for example 2x 1.5TB to get 2.5TB > diskspace fully mirrored. The whole process shouldn't need to reinstall > the system, or to change the slice/partition layout, ie. be totally > transparent for the data. > And for this particular need, ZFS seems to be the way to go. I'm happily using ZFS on a 32-bit FreeBSD desktop system (that also plays a home server role). It should meet your disk-modularity requirements above, with the exception that it's not possible to add disks to a raidZ set (though it is possible to add additional sets to the same zpool). > However, I'm a bit worried about FreeBSD's ZFS implementation: > > - I've got a 64bits dual core 2GHz CPU, but can't use an amd64 FreeBSD > since Xen, NVidia drivers and wine don't work on it; but ZFS is said > to be unsuitable for i386. That's overstating the case. The extra memory headroom on amd64 may make things simpler, but it's certianly possible to run ZFS on FreeBSD i386 as long as you have a couple gigs of RAM (I actually only have 1.5 GB) and follow the tuning guidelines. You should also be willing to monitor your system and go through one or two fine-tuning cycles > - It's said you can't boot from a ZFS pool. There are patches available to allow this but frankly I don't see the appeal. I think it makes much more sense to have / (including /boot) be a regular UFS2 filesystem on a small partition. If something goes wrong you can boot from a CD or single-user and not have to worry about getting your ZFS pools back online before you can even start troubleshooting the system. Since (unlike Solaris) FreeBSD doesn't force you to dedicate whole disks to ZFS, this is a viable option. As Miroslav mentioned you can make a small root partition on two disks and set them up as a gmirror, leaving the remainder of the disks available for your zpool(s). > So could you please tell me if using ZFS is ok for me, or should I use > a gmirror system (but I don't think I can easily add new disks to this). You could get most if not all of what you're after with gmirror, gvirstor, gjournal, etc but it sounds like ZFS is really what you're after and I think you'll be fine. I haven't actually added any disks to my setup since I switched to ZFS but it's nice knowing that I can. Add to that cheap snapshots, checksumming and self-healing and easy administration and I tink it's an easy sale. JN From kerneljack at gmail.com Sat Nov 1 16:31:20 2008 From: kerneljack at gmail.com (Khusro Jaleel) Date: Sat Nov 1 16:31:27 2008 Subject: problems with wireless using iwi drivers Message-ID: Hi, I'm new to FreeBSD-CURRENT and am having problems getting my wireless to work on my laptop. It is an old Centrino ASUS laptop with built-in IPW2200 wireless. I've had no problems getting wireless to work on this for the past few years now with many flavors of linux and of course Windows so I'm sure it should also work in FreeBSD without any issues. However, I'm not having much luck. I've followed the instructions in the Handbook's Wireless page and read the iwi(4) man page and added the following to my /boot/loader.conf: ------------- legal.intel_iwi.license_ack=1 if_iwi_load="YES" wlan_load="YES" firmware_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" hw.psm.synaptics_support=1 -------------- When I reboot and do a "dmesg | grep iwi" I get: ---------- iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Am I forgetting to load the firmware somehow? In /boot/kernel, I see the following files: ----------- [root@asus ~]# ls -l /boot/kernel/iwi_* -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko ----------- ifconfig: bge0: flags=8843 metric 0 mtu 1500 options=9b ether 00:11:2f:0c:e8:7f inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:e0:18:1b:1f:63 ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 iwi0: flags=8803 metric 0 mtu 2290 ether 00:0e:35:0d:7c:65 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier plip0: flags=108810 metric 0 mtu 1500 lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 But if I try to do "ifconfig iwi0 up" I get: ---------- iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Any help appreciated. Thanks. From jille at quis.cx Sat Nov 1 17:39:59 2008 From: jille at quis.cx (Jille Timmermans) Date: Sat Nov 1 17:40:11 2008 Subject: device snp build broken? In-Reply-To: <20081101061930.GA34365@regency.nsu.ru> References: <20081101061930.GA34365@regency.nsu.ru> Message-ID: <490C7625.6060608@quis.cx> Hello, snp(4) in -CURRENT is currently not supported. Ed made a patch for it; which worked for me. You can get the latest version from: http://people.freebsd.org/~ed/mpsafetty/ (The patch-set also includes other things; like a new /dev/console) -- Jille Alexey Dokuchaev schreef: > Hi there, > > Looks like device snp is broken on recent -CURRENT. Is it being > supported at all? How useful it is in modern environment? > > Thanks. Relevant part of build log attached. > > ./danfe > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From jbolivar at cantv.net Sat Nov 1 22:46:20 2008 From: jbolivar at cantv.net (Julian Bolivar) Date: Sat Nov 1 22:46:28 2008 Subject: /stand/sysinstall freezed on FreeBSD 7.1 install Message-ID: <490D3C00.4040708@cantv.net> Dear Friends, I try to install FreeBSD 7.1 AMD64 beta 2 in an Intel Core 2 Duo and motherboard MSI 975X Platinum V.2m, but when /stand/sysinstall try to start from the installation CD, the system freezed and don't continue the install process. Anyone know how to solved this problem to install it Thanks and regards, Julian Bolivar From kerneljack at gmail.com Sun Nov 2 01:04:38 2008 From: kerneljack at gmail.com (Khusro Jaleel) Date: Sun Nov 2 01:04:45 2008 Subject: problems configuring wireless using iwi Message-ID: Hi, I'm new to FreeBSD-CURRENT and am having problems getting my wireless to work on my laptop. It is an old Centrino ASUS laptop with built-in IPW2200 wireless. I've had no problems getting wireless to work on this for the past few years now with many flavors of linux and of course Windows so I'm sure it should also work in FreeBSD without any issues. However, I'm not having much luck. I've followed the instructions in the Handbook's Wireless page and read the iwi(4) man page and added the following to my /boot/loader.conf: ------------- legal.intel_iwi.license_ack=1 if_iwi_load="YES" wlan_load="YES" firmware_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" hw.psm.synaptics_support=1 -------------- When I reboot and do a "dmesg | grep iwi" I get: ---------- iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Am I forgetting to load the firmware somehow? In /boot/kernel, I see the following files: ----------- [root@asus ~]# ls -l /boot/kernel/iwi_* -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko ----------- ifconfig: bge0: flags=8843 metric 0 mtu 1500 options=9b ether 00:11:2f:0c:e8:7f inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:e0:18:1b:1f:63 ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 iwi0: flags=8803 metric 0 mtu 2290 ether 00:0e:35:0d:7c:65 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier plip0: flags=108810 metric 0 mtu 1500 lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 But if I try to do "ifconfig iwi0 up" I get: ---------- iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Any help appreciated. Thanks. From kerneljack at gmail.com Sun Nov 2 01:26:03 2008 From: kerneljack at gmail.com (Khusro Jaleel) Date: Sun Nov 2 01:26:09 2008 Subject: problems configuring wireless using iwi Message-ID: Hi, I'm new to FreeBSD-CURRENT and am having problems getting my wireless to work on my laptop. It is an old Centrino ASUS laptop with built-in IPW2200 wireless. I've had no problems getting wireless to work on this for the past few years now with many flavors of linux and of course Windows so I'm sure it should also work in FreeBSD without any issues. However, I'm not having much luck. I've followed the instructions in the Handbook's Wireless page and read the iwi(4) man page and added the following to my /boot/loader.conf: ------------- legal.intel_iwi.license_ack=1 if_iwi_load="YES" wlan_load="YES" firmware_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" hw.psm.synaptics_support=1 -------------- When I reboot and do a "dmesg | grep iwi" I get: ---------- iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Am I forgetting to load the firmware somehow? In /boot/kernel, I see the following files: ----------- [root@asus ~]# ls -l /boot/kernel/iwi_* -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko ----------- ifconfig: bge0: flags=8843 metric 0 mtu 1500 options=9b ether 00:11:2f:0c:e8:7f inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:e0:18:1b:1f:63 ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 iwi0: flags=8803 metric 0 mtu 2290 ether 00:0e:35:0d:7c:65 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier plip0: flags=108810 metric 0 mtu 1500 lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 But if I try to do "ifconfig iwi0 up" I get: ---------- iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Any help appreciated. Thanks. From ari at ish.com.au Sun Nov 2 01:58:04 2008 From: ari at ish.com.au (Aristedes Maniatis) Date: Sun Nov 2 01:58:12 2008 Subject: ZFS for a desktop computer In-Reply-To: <20081101114717.0ffc2ec8@valhala> References: <20081101114717.0ffc2ec8@valhala> Message-ID: On 01/11/2008, at 9:47 PM, Nicolas Martyanoff wrote: > - I've got a 64bits dual core 2GHz CPU, but can't use an amd64 FreeBSD > since Xen, NVidia drivers and wine don't work on it; but ZFS is said > to be unsuitable for i386. ZFS will run on i386, however since ZFS requires lots of RAM it has been said that it doesn't make sense to run it on systems with less than 1Gb of RAM dedicated to ZFS. I believe the requirement for large amounts of RAM will be slightly eased in later versions of ZFS (well, it still like RAM but will not hang your system when it runs out quite so easily). Read these instructions on how to get i386 to play with ZFS: http://wiki.freebsd.org/ZFSTuningGuide > - It's said you can't boot from a ZFS pool. Miroslav has answered this one with a couple of useful links (including one I co-wrote :-) Ari Maniatis --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A From ohartman at mail.zedat.fu-berlin.de Sun Nov 2 01:30:44 2008 From: ohartman at mail.zedat.fu-berlin.de (O. Hartmann) Date: Sun Nov 2 04:10:22 2008 Subject: GPT(8): gone in FreeBSD 8.0-CURRENT? Message-ID: <490D6F88.4050609@mail.zedat.fu-berlin.de> Hello, I'm looking for the gpt(8) tool, found in FreeBSD 7. When switching to FreeBSD 8-CUR I missed it. Has it been dumped? Why, how to handle GUID partitions in FBSD8? Regards, Oliver -- From rpaulo at freebsd.org Sun Nov 2 04:19:58 2008 From: rpaulo at freebsd.org (Rui Paulo) Date: Sun Nov 2 04:20:06 2008 Subject: GPT(8): gone in FreeBSD 8.0-CURRENT? In-Reply-To: <490D6F88.4050609@mail.zedat.fu-berlin.de> References: <490D6F88.4050609@mail.zedat.fu-berlin.de> Message-ID: <22FEED13-2E4B-4873-B1A5-EA841369E3AE@freebsd.org> On 2 Nov 2008, at 09:14, O. Hartmann wrote: > Hello, > I'm looking for the gpt(8) tool, found in FreeBSD 7. When switching to > FreeBSD 8-CUR I missed it. Has it been dumped? Why, how to handle GUID > partitions in FBSD8? Yes, gpt is gone. We now use gpart. Regards, -- Rui Paulo From yuri.pankov at gmail.com Sun Nov 2 04:59:25 2008 From: yuri.pankov at gmail.com (Yuri Pankov) Date: Sun Nov 2 04:59:32 2008 Subject: reproducible panic with mount_smbfs Message-ID: <20081102123100.GA1434@darklight.homeunix.org> Hi, Trying to mount nonexistent smb share with mount_smbfs leads to following panic: # mount_smbfs //yuri@lifebane/blahblah /mnt Unread portion of the kernel message buffer: smb_co_lock: recursive lock for object 1 panic: Lock (lockmgr) smb_vc not locked @ /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x182 witness_assert() at witness_assert+0x21a __lockmgr_args() at __lockmgr_args+0x17a smb_co_put() at smb_co_put+0x76 smb_sm_lookup() at smb_sm_lookup+0xfe smb_usr_lookup() at smb_usr_lookup+0xcd nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 giant_ioctl() at giant_ioctl+0x75 devfs_ioctl_f() at devfs_ioctl_f+0x76 kern_ioctl() at kern_ioctl+0x92 ioctl() at ioctl+0xfd syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = 0x7fffffffe038, rbp = 0x7fffffffe450 --- Uptime: 6m46s Physical memory: 2032 MB Dumping 148 MB: 133 117 101 85 69 53 37 21 5 #0 doadump () at pcpu.h:196 #1 0xffffffff804ea413 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xffffffff804ea89c in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xffffffff8052afea in witness_assert (lock=Variable "lock" is not available. ) at /usr/src/sys/kern/subr_witness.c:2199 #4 0xffffffff804d6b4a in __lockmgr_args (lk=0xffffff004a5bf408, flags=1048832, ilk=0xffffff004a5bf430, wmesg=Variable "wmesg" is not available. ) at /usr/src/sys/kern/kern_lock.c:659 #5 0xffffffff81023536 in smb_co_put (cp=0xffffff004a5bf400, scred=0xfffffffe7fd879b0) at lockmgr.h:93 #6 0xffffffff81023fce in smb_sm_lookup (vcspec=0xfffffffe7fd87890, shspec=0xfffffffe7fd87900, scred=0xfffffffe7fd879b0, vcpp=0xfffffffe7fd87928) at /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:222 #7 0xffffffff8102995d in smb_usr_lookup (dp=0xffffff0003738000, scred=0xfffffffe7fd879b0, vcpp=0xfffffffe7fd879c8, sspp=0xfffffffe7fd879c0) at /usr/src/sys/modules/smbfs/../../netsmb/smb_usr.c:154 #8 0xffffffff81024386 in nsmb_dev_ioctl (dev=Variable "dev" is not available. ) at /usr/src/sys/modules/smbfs/../../netsmb/smb_dev.c:285 #9 0xffffffff804b6375 in giant_ioctl (dev=0xffffff004a5bf800, cmd=2198367850, data=0xffffff0003738000 "\002", fflag=3, td=0xffffff004a5c7370) at /usr/src/sys/kern/kern_conf.c:407 #10 0xffffffff8047a636 in devfs_ioctl_f (fp=0xffffff0003e14870, com=2198367850, data=Variable "data" is not available. ) at /usr/src/sys/fs/devfs/devfs_vnops.c:588 #11 0xffffffff8052e9c2 in kern_ioctl (td=0xffffff004a5c7370, fd=Variable "fd" is not available. ) at file.h:262 #12 0xffffffff8052ec2d in ioctl (td=0xffffff004a5c7370, uap=0xfffffffe7fd87c00) at /usr/src/sys/kern/sys_generic.c:676 #13 0xffffffff807c081f in syscall (frame=0xfffffffe7fd87c90) at /usr/src/sys/amd64/amd64/trap.c:898 #14 0xffffffff807a32db in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:338 #15 0x0000000800939aec in ?? () Previous frame inner to this frame (corrupt stack?) FreeBSD 8.0-CURRENT amd64 World and kernel are built from sources synced on Nov, 1. Yuri From some.else at gmail.com Sun Nov 2 04:19:51 2008 From: some.else at gmail.com (Annan) Date: Sun Nov 2 05:03:06 2008 Subject: Trouble installing FreeBSD on ASUS M3A78-EM with firewire enabled Message-ID: <490D937A.8020103@gmail.com> When trying to install FreeBSD 7.1-BETA2 (amd64) on a computer with the motherboard ASUS M3A78-EM, the installation freezes with the error message: run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config Booting without ACPI, it still freezes, right after: Trying to mount root from ufs:/ufs/md0. I also tried 8.0-HEAD from http://pub.allbsd.org/FreeBSD-snapshots/amd64/8.0-HEAD-20081101-JPSNAP/cdrom/, which resulted in the same error messages. To get it to boot (7.1-BETA2, though I assume 8.0-HEAD will also boot :-)), deactivate firewire in BIOS (discovered after trying all sorts of things). I have no use for firewire so it's not a problem, but maybe it is for someone else. If you want to install 7.0-RELEASE, you also have to deactivate USB (as pointed out by this comment: http://www.vanutsteen.nl/2008/07/21/new-virtualization-server-htpc-machine/#comment-315). I found it to be true for M3A78-EM too. From ohartman at mail.zedat.fu-berlin.de Sun Nov 2 04:26:13 2008 From: ohartman at mail.zedat.fu-berlin.de (O. Hartmann) Date: Sun Nov 2 05:18:31 2008 Subject: OpenLDAP 2.4.11: won't work anymore, crashes with SIGNAL 11 after start Message-ID: <490D9C71.1050401@mail.zedat.fu-berlin.de> Hello, I migrtaed this day to FreeBSD 8.0-CURRENT, most recent buildworld since last night. I'm about reinstalling everything I need from scratch, so OpenLDAP 2.4.11 (with SASL support). After pulling back the backup of the LDAP configurations and assuring that access rights etc. is in the right place, I tried starting openldap-2.4.11 and witnessed a crash. Immediately after the slapd-daemon starts it suffers from SIGNAL 11: Starting slapd. @(#) $OpenLDAP: slapd 2.4.11 (Nov 2 2008 11:42:11) $ root@foo.org:/usr/ports/net/openldap24-server/work/openldap-2.4.11/servers/slapd Segmentation fault /usr/local/etc/rc.d/slapd: WARNING: failed to start slapd Well, removing all of my configurations (especially schemata, the slapd.d-directory) and replacing everything needed by those files coming with the installation package and trying starting this results in an 'Abort trap': Starting slapd. @(#) $OpenLDAP: slapd 2.4.11 (Nov 2 2008 11:42:11) $ root@foo.org:/usr/ports/net/openldap24-server/work/openldap-2.4.11/servers/slapd Assertion failed: (schema_init_done == 1), function slap_schema_check, file schema_prep.c, line 1340. Abort trap /usr/local/etc/rc.d/slapd: WARNING: failed to start slapd The used configuration and installation works fine with FreeBSD 7.1-PRE (exactly the same way installed ports, used the same make.conf!). Well, before submitting a PR or investigating deeper, please can someone using LDAP 2.4.11 (from ports) on FBSD 8.0-CUR report whether he is successfully using LDAP or not? If there is more than a stupid config-error I will investigate deeper with all the debugging facilities switched on. Regards, thanks in advance, oliver From ohartman at mail.zedat.fu-berlin.de Sun Nov 2 04:27:01 2008 From: ohartman at mail.zedat.fu-berlin.de (O. Hartmann) Date: Sun Nov 2 05:18:40 2008 Subject: GPT(8): gone in FreeBSD 8.0-CURRENT? In-Reply-To: <22FEED13-2E4B-4873-B1A5-EA841369E3AE@freebsd.org> References: <490D6F88.4050609@mail.zedat.fu-berlin.de> <22FEED13-2E4B-4873-B1A5-EA841369E3AE@freebsd.org> Message-ID: <490D9CA2.6050006@mail.zedat.fu-berlin.de> Rui Paulo wrote: > > On 2 Nov 2008, at 09:14, O. Hartmann wrote: > >> Hello, >> I'm looking for the gpt(8) tool, found in FreeBSD 7. When switching to >> FreeBSD 8-CUR I missed it. Has it been dumped? Why, how to handle GUID >> partitions in FBSD8? > > Yes, gpt is gone. > We now use gpart. > > Regards, > -- > Rui Paulo > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" all right, thanks a lot. oliver From peter.schuller at infidyne.com Sun Nov 2 06:48:45 2008 From: peter.schuller at infidyne.com (Peter Schuller) Date: Sun Nov 2 06:48:52 2008 Subject: ZFS for a desktop computer In-Reply-To: <200811011517.37640.lists@jnielsen.net> References: <20081101114717.0ffc2ec8@valhala> <200811011517.37640.lists@jnielsen.net> Message-ID: <20081102144842.GA59552@hyperion.scode.org> > There are patches available to allow this but frankly I don't see the > appeal. I think it makes much more sense to have / (including /boot) be a > regular UFS2 filesystem on a small partition. If something goes wrong you > can boot from a CD or single-user and not have to worry about getting your > ZFS pools back online before you can even start troubleshooting the system. FWIW let me just put the vote in there that to me, personally, there is a lot of appeal. For recovery, I don't find minimalistic /:s or fixit CD:s very useful anyway (in fact I don't think I have ever fixed a system that way; if there is some trouble that prevents booting, I tend to end up booting a separate fully installed system from another drive or similar to have full flexibility). If you're using ZFS because you want to avoid certain failure conditions (such as "oh, there was a bad block during reconstruction and my mirror got blown away even though it was a 4-way mirror"), it is nice to have that applied to your *entire* system instead of having a small root partition or boot partition that is somehow exempted. Especially since these are the ones you really need to boot the system. I appreciate that supporting direct booting off of ZFS is not easy to implement, and this is not any kind of complaint. I just want to respond to the claim that there is no appeal to having it supported. I doubt I am alone in thinking it would be great to boot natively off ZFS, even if not every one under the sun agrees :) -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081102/3d876401/attachment.pgp From mad at madpilot.net Sun Nov 2 07:16:28 2008 From: mad at madpilot.net (Guido Falsi) Date: Sun Nov 2 07:16:35 2008 Subject: ZFS for a desktop computer In-Reply-To: <20081102144842.GA59552@hyperion.scode.org> References: <20081101114717.0ffc2ec8@valhala> <200811011517.37640.lists@jnielsen.net> <20081102144842.GA59552@hyperion.scode.org> Message-ID: <490DC02E.7020701@madpilot.net> Peter Schuller wrote: > I appreciate that supporting direct booting off of ZFS is not easy to > implement, and this is not any kind of complaint. I just want to > respond to the claim that there is no appeal to having it supported. I > doubt I am alone in thinking it would be great to boot natively off > ZFS, even if not every one under the sun agrees :) > Just to cast a "vote" I subscribe to this opinion. It would be great...In fact if direct boot from ZFS was supported I'd convert my work PC to AMD64+ZFS immediately. At home it would be hardware since my PCs have at most 512 Mb ram, which is more than enough for what I do here. -- Guido Falsi From attilio at freebsd.org Sun Nov 2 08:05:10 2008 From: attilio at freebsd.org (Attilio Rao) Date: Sun Nov 2 08:05:16 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <20081102123100.GA1434@darklight.homeunix.org> References: <20081102123100.GA1434@darklight.homeunix.org> Message-ID: <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> 2008/11/2, Yuri Pankov : > Hi, > > Trying to mount nonexistent smb share with mount_smbfs leads to > following panic: > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > Unread portion of the kernel message buffer: > smb_co_lock: recursive lock for object 1 > panic: Lock (lockmgr) smb_vc not locked @ > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x182 > witness_assert() at witness_assert+0x21a > __lockmgr_args() at __lockmgr_args+0x17a > smb_co_put() at smb_co_put+0x76 > smb_sm_lookup() at smb_sm_lookup+0xfe > smb_usr_lookup() at smb_usr_lookup+0xcd > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > giant_ioctl() at giant_ioctl+0x75 > devfs_ioctl_f() at devfs_ioctl_f+0x76 > kern_ioctl() at kern_ioctl+0x92 > ioctl() at ioctl+0xfd > syscall() at syscall+0x1bf > Xfast_syscall() at Xfast_syscall+0xab > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > Uptime: 6m46s > Physical memory: 2032 MB So, what is happening here is that smb_co_lock() is AFU. Infact looking at the code: int smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) { ... if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && (flags & LK_CANRECURSE) == 0) { SMBERROR("recursive lock for object %d\n", cp->co_level); return 0; } ... from that it is obvious that smb_co_lock() won't recurse the lock really, but will let believe the consumer it acquired the lock successfully without panicking at all (the printf is like a little joke there). I think that we don't panic here mainly because these are "user driver" events and we want avoid to get a DoS for the kernel but it is an unacceptable code also. This can be fixed by allowing recuring lockmgr by default but the problem is more vaste. For example, it would be very nice to drop the LK_DRAIN support from netsmb in order to completely remove it from the 8.0 kernel serie and kill a bogus / dangerous option for lockmgr. It would be a cornerstone for lockmgr wealth really. What really is missing here is a valid netsmb maintainer, someone that knows well the layers involved, is motivated to work on it and can take advantage from the other kernel developer experience on the most hardcore parts. It would be also nice, for example, to bring in some Apple's changes (like the crypto support). Someone willing to step in would be very appreciated. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From stephen at math.missouri.edu Sun Nov 2 08:11:03 2008 From: stephen at math.missouri.edu (Stephen Montgomery-Smith) Date: Sun Nov 2 08:11:10 2008 Subject: problems configuring wireless using iwi In-Reply-To: References: Message-ID: <490DD114.3000901@math.missouri.edu> FreeBSD CURRENT has a different approach to wireless cards. Somewhere in /etc/rc.conf you need lines like wlans_iwi0="wlan0" and then all future ifconfig command should refer to wlan0 instead of iwi0. I am not sure if this will fix your problem or not, but you must have not done this somewhere, otherwise ifconfig would have listed wlan0 as well as iwi0. If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. I think iwi is already a part of that. Khusro Jaleel wrote: > Hi, > > I'm new to FreeBSD-CURRENT and am having problems getting my wireless > to work on my laptop. It is an old Centrino ASUS laptop with built-in > IPW2200 wireless. I've had no problems getting wireless to work on > this for the past few years now with many flavors of linux and of > course Windows so I'm sure it should also work in FreeBSD without any > issues. > > However, I'm not having much luck. I've followed the instructions in > the Handbook's Wireless page and read the iwi(4) man page and added > the following to my /boot/loader.conf: > > ------------- > legal.intel_iwi.license_ack=1 > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > iwi_bss_load="YES" > iwi_ibss_load="YES" > iwi_monitor_load="YES" > hw.psm.synaptics_support=1 > -------------- > > When I reboot and do a "dmesg | grep iwi" I get: > > ---------- > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > ---------- > > Am I forgetting to load the firmware somehow? In /boot/kernel, I see > the following files: > > ----------- > [root@asus ~]# ls -l /boot/kernel/iwi_* > -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko > -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko > -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko > ----------- > > ifconfig: > bge0: flags=8843 metric 0 mtu 1500 > options=9b > ether 00:11:2f:0c:e8:7f > inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > fwe0: flags=8802 metric 0 mtu 1500 > options=8 > ether 02:e0:18:1b:1f:63 > ch 1 dma -1 > fwip0: flags=8802 metric 0 mtu 1500 > lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 > iwi0: flags=8803 metric 0 mtu 2290 > ether 00:0e:35:0d:7c:65 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > plip0: flags=108810 metric 0 mtu 1500 > lo0: flags=8049 metric 0 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > > But if I try to do "ifconfig iwi0 up" I get: > > ---------- > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > ---------- > > Any help appreciated. Thanks. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From attilio at freebsd.org Sun Nov 2 08:17:21 2008 From: attilio at freebsd.org (Attilio Rao) Date: Sun Nov 2 08:17:35 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> Message-ID: <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> 2008/11/2, Attilio Rao : > 2008/11/2, Yuri Pankov : > > > Hi, > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > following panic: > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > Unread portion of the kernel message buffer: > > smb_co_lock: recursive lock for object 1 > > panic: Lock (lockmgr) smb_vc not locked @ > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > cpuid = 0 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > panic() at panic+0x182 > > witness_assert() at witness_assert+0x21a > > __lockmgr_args() at __lockmgr_args+0x17a > > smb_co_put() at smb_co_put+0x76 > > smb_sm_lookup() at smb_sm_lookup+0xfe > > smb_usr_lookup() at smb_usr_lookup+0xcd > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > giant_ioctl() at giant_ioctl+0x75 > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > kern_ioctl() at kern_ioctl+0x92 > > ioctl() at ioctl+0xfd > > syscall() at syscall+0x1bf > > Xfast_syscall() at Xfast_syscall+0xab > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > Uptime: 6m46s > > Physical memory: 2032 MB > > > So, what is happening here is that smb_co_lock() is AFU. > Infact looking at the code: > int > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > { > ... > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > (flags & LK_CANRECURSE) == 0) { > SMBERROR("recursive lock for object %d\n", cp->co_level); > return 0; > } > ... Yuri, could you please test this fix: http://www.freebsd.org/~attilio/netsmb.diff and report if it works? You could get a KASSERT running but this is expected as I want to identify on the callers who passes a malformed request and fix it. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From yuri.pankov at gmail.com Sun Nov 2 08:33:14 2008 From: yuri.pankov at gmail.com (Yuri Pankov) Date: Sun Nov 2 08:33:21 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> Message-ID: <20081102163307.GB1434@darklight.homeunix.org> On Sun, Nov 02, 2008 at 05:17:18PM +0100, Attilio Rao wrote: > 2008/11/2, Attilio Rao : > > 2008/11/2, Yuri Pankov : > > > > > Hi, > > > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > > following panic: > > > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > > > Unread portion of the kernel message buffer: > > > smb_co_lock: recursive lock for object 1 > > > panic: Lock (lockmgr) smb_vc not locked @ > > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > > cpuid = 0 > > > KDB: stack backtrace: > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > panic() at panic+0x182 > > > witness_assert() at witness_assert+0x21a > > > __lockmgr_args() at __lockmgr_args+0x17a > > > smb_co_put() at smb_co_put+0x76 > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > > smb_usr_lookup() at smb_usr_lookup+0xcd > > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > > giant_ioctl() at giant_ioctl+0x75 > > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > > kern_ioctl() at kern_ioctl+0x92 > > > ioctl() at ioctl+0xfd > > > syscall() at syscall+0x1bf > > > Xfast_syscall() at Xfast_syscall+0xab > > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > > Uptime: 6m46s > > > Physical memory: 2032 MB > > > > > > So, what is happening here is that smb_co_lock() is AFU. > > Infact looking at the code: > > int > > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > > { > > ... > > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > > (flags & LK_CANRECURSE) == 0) { > > SMBERROR("recursive lock for object %d\n", cp->co_level); > > return 0; > > } > > ... > > Yuri, > could you please test this fix: > http://www.freebsd.org/~attilio/netsmb.diff > > and report if it works? > You could get a KASSERT running but this is expected as I want to > identify on the callers who passes a malformed request and fix it. > > Thanks, > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein Thanks, Attilio. With this patch system doesn't panic anymore with nonexistent share names (though I had to comment out smb_co_lockstatus prototype and function to get rid of -Werror complaints). Still getting a LOR: netsmb_dev: loaded lock order reversal: 1st 0xffffff0021644008 smb_vc (smb_vc) @ /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:332 2nd 0xffffffff81037368 smbsm (smbsm) @ /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:348 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e __lockmgr_args() at __lockmgr_args+0xc2a smb_co_lock() at smb_co_lock+0x38 smb_co_gone() at smb_co_gone+0x38 smb_sm_lookup() at smb_sm_lookup+0xfe smb_usr_lookup() at smb_usr_lookup+0xcd nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 giant_ioctl() at giant_ioctl+0x75 devfs_ioctl_f() at devfs_ioctl_f+0x76 kern_ioctl() at kern_ioctl+0x92 ioctl() at ioctl+0xfd syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = 0x7fffffffe048, rbp = 0x7fffffffe460 --- Thanks, Yuri From stephen at math.missouri.edu Sun Nov 2 08:35:21 2008 From: stephen at math.missouri.edu (Stephen Montgomery-Smith) Date: Sun Nov 2 08:35:29 2008 Subject: problems configuring wireless using iwi In-Reply-To: References: Message-ID: <490DD114.3000901@math.missouri.edu> FreeBSD CURRENT has a different approach to wireless cards. Somewhere in /etc/rc.conf you need lines like wlans_iwi0="wlan0" and then all future ifconfig command should refer to wlan0 instead of iwi0. I am not sure if this will fix your problem or not, but you must have not done this somewhere, otherwise ifconfig would have listed wlan0 as well as iwi0. If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. I think iwi is already a part of that. Khusro Jaleel wrote: > Hi, > > I'm new to FreeBSD-CURRENT and am having problems getting my wireless > to work on my laptop. It is an old Centrino ASUS laptop with built-in > IPW2200 wireless. I've had no problems getting wireless to work on > this for the past few years now with many flavors of linux and of > course Windows so I'm sure it should also work in FreeBSD without any > issues. > > However, I'm not having much luck. I've followed the instructions in > the Handbook's Wireless page and read the iwi(4) man page and added > the following to my /boot/loader.conf: > > ------------- > legal.intel_iwi.license_ack=1 > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > iwi_bss_load="YES" > iwi_ibss_load="YES" > iwi_monitor_load="YES" > hw.psm.synaptics_support=1 > -------------- > > When I reboot and do a "dmesg | grep iwi" I get: > > ---------- > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > ---------- > > Am I forgetting to load the firmware somehow? In /boot/kernel, I see > the following files: > > ----------- > [root@asus ~]# ls -l /boot/kernel/iwi_* > -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko > -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko > -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko > ----------- > > ifconfig: > bge0: flags=8843 metric 0 mtu 1500 > options=9b > ether 00:11:2f:0c:e8:7f > inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > fwe0: flags=8802 metric 0 mtu 1500 > options=8 > ether 02:e0:18:1b:1f:63 > ch 1 dma -1 > fwip0: flags=8802 metric 0 mtu 1500 > lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 > iwi0: flags=8803 metric 0 mtu 2290 > ether 00:0e:35:0d:7c:65 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > plip0: flags=108810 metric 0 mtu 1500 > lo0: flags=8049 metric 0 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > > But if I try to do "ifconfig iwi0 up" I get: > > ---------- > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > ---------- > > Any help appreciated. Thanks. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From attilio at freebsd.org Sun Nov 2 09:53:29 2008 From: attilio at freebsd.org (Attilio Rao) Date: Sun Nov 2 09:53:36 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <20081102163307.GB1434@darklight.homeunix.org> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <20081102163307.GB1434@darklight.homeunix.org> Message-ID: <3bbf2fe10811020953l29f1a7eesa4f4eeb49f0a2eba@mail.gmail.com> 2008/11/2, Yuri Pankov : > On Sun, Nov 02, 2008 at 05:17:18PM +0100, Attilio Rao wrote: > > 2008/11/2, Attilio Rao : > > > 2008/11/2, Yuri Pankov : > > > > > > > Hi, > > > > > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > > > following panic: > > > > > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > > > > > Unread portion of the kernel message buffer: > > > > smb_co_lock: recursive lock for object 1 > > > > panic: Lock (lockmgr) smb_vc not locked @ > > > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > > > cpuid = 0 > > > > KDB: stack backtrace: > > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > > panic() at panic+0x182 > > > > witness_assert() at witness_assert+0x21a > > > > __lockmgr_args() at __lockmgr_args+0x17a > > > > smb_co_put() at smb_co_put+0x76 > > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > > > smb_usr_lookup() at smb_usr_lookup+0xcd > > > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > > > giant_ioctl() at giant_ioctl+0x75 > > > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > > > kern_ioctl() at kern_ioctl+0x92 > > > > ioctl() at ioctl+0xfd > > > > syscall() at syscall+0x1bf > > > > Xfast_syscall() at Xfast_syscall+0xab > > > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > > > Uptime: 6m46s > > > > Physical memory: 2032 MB > > > > > > > > > So, what is happening here is that smb_co_lock() is AFU. > > > Infact looking at the code: > > > int > > > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > > > { > > > ... > > > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > > > (flags & LK_CANRECURSE) == 0) { > > > SMBERROR("recursive lock for object %d\n", cp->co_level); > > > return 0; > > > } > > > ... > > > > Yuri, > > could you please test this fix: > > http://www.freebsd.org/~attilio/netsmb.diff > > > > and report if it works? > > You could get a KASSERT running but this is expected as I want to > > identify on the callers who passes a malformed request and fix it. > > > > Thanks, > > Attilio > > > > > > -- > > Peace can only be achieved by understanding - A. Einstein > > > Thanks, Attilio. > > With this patch system doesn't panic anymore with nonexistent share > names (though I had to comment out smb_co_lockstatus prototype and > function to get rid of -Werror complaints). Still getting a LOR: > > netsmb_dev: loaded > lock order reversal: > 1st 0xffffff0021644008 smb_vc (smb_vc) @ > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:332 > 2nd 0xffffffff81037368 smbsm (smbsm) @ > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:348 > > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x81e > __lockmgr_args() at __lockmgr_args+0xc2a > smb_co_lock() at smb_co_lock+0x38 > smb_co_gone() at smb_co_gone+0x38 > > smb_sm_lookup() at smb_sm_lookup+0xfe > smb_usr_lookup() at smb_usr_lookup+0xcd > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > giant_ioctl() at giant_ioctl+0x75 > devfs_ioctl_f() at devfs_ioctl_f+0x76 > kern_ioctl() at kern_ioctl+0x92 > ioctl() at ioctl+0xfd > syscall() at syscall+0x1bf > Xfast_syscall() at Xfast_syscall+0xab > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > 0x7fffffffe048, rbp = 0x7fffffffe460 --- I've updated the patch in order to fix smb_co_lockstatus problem. Could you please stress test it while I investigate the LOR problem? Are you running with INVARIANTS? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From tinderbox at freebsd.org Sun Nov 2 11:26:00 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sun Nov 2 11:26:07 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081102192556.DEE7A73039@freebsd-current.sentex.ca> TB --- 2008-11-02 18:11:26 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-02 18:11:26 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-11-02 18:11:26 - cleaning the object tree TB --- 2008-11-02 18:11:56 - cvsupping the source tree TB --- 2008-11-02 18:11:56 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-11-02 18:12:05 - building world (CFLAGS=-O -pipe) TB --- 2008-11-02 18:12:05 - cd /src TB --- 2008-11-02 18:12:05 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 2 18:12:06 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Nov 2 19:25:55 UTC 2008 TB --- 2008-11-02 19:25:55 - generating LINT kernel config TB --- 2008-11-02 19:25:55 - cd /src/sys/powerpc/conf TB --- 2008-11-02 19:25:55 - /usr/bin/make -B LINT TB --- 2008-11-02 19:25:55 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-02 19:25:55 - cd /src TB --- 2008-11-02 19:25:55 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 2 19:25:55 UTC 2008 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/powerpc/conf; PATH=/obj/powerpc/src/tmp/legacy/usr/sbin:/obj/powerpc/src/tmp/legacy/usr/bin:/obj/powerpc/src/tmp/legacy/usr/games:/obj/powerpc/src/tmp/usr/sbin:/obj/powerpc/src/tmp/usr/bin:/obj/powerpc/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/powerpc/src/sys/LINT /src/sys/powerpc/conf/LINT WARNING: duplicate option `GEOM_PART_APM' encountered. WARNING: duplicate option `GEOM_PART_MBR' encountered. WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. /src/sys/powerpc/conf/LINT: unknown option "RL_TWISTER_ENABLE" *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-02 19:25:56 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-02 19:25:56 - ERROR: failed to build lint kernel TB --- 2008-11-02 19:25:56 - tinderbox aborted TB --- 3170.28 user 368.91 system 4470.08 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Sun Nov 2 12:19:00 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sun Nov 2 12:19:06 2008 Subject: [head tinderbox] failure on sparc64/sparc64 Message-ID: <20081102201856.1C6FF73039@freebsd-current.sentex.ca> TB --- 2008-11-02 19:09:11 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-02 19:09:11 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-11-02 19:09:11 - cleaning the object tree TB --- 2008-11-02 19:09:41 - cvsupping the source tree TB --- 2008-11-02 19:09:41 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-02 19:09:48 - building world (CFLAGS=-O -pipe) TB --- 2008-11-02 19:09:48 - cd /src TB --- 2008-11-02 19:09:48 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 2 19:09:50 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Nov 2 20:18:55 UTC 2008 TB --- 2008-11-02 20:18:55 - generating LINT kernel config TB --- 2008-11-02 20:18:55 - cd /src/sys/sparc64/conf TB --- 2008-11-02 20:18:55 - /usr/bin/make -B LINT TB --- 2008-11-02 20:18:55 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-02 20:18:55 - cd /src TB --- 2008-11-02 20:18:55 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 2 20:18:55 UTC 2008 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/sparc64/conf; PATH=/obj/sparc64/src/tmp/legacy/usr/sbin:/obj/sparc64/src/tmp/legacy/usr/bin:/obj/sparc64/src/tmp/legacy/usr/games:/obj/sparc64/src/tmp/usr/sbin:/obj/sparc64/src/tmp/usr/bin:/obj/sparc64/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/sparc64/src/sys/LINT /src/sys/sparc64/conf/LINT WARNING: duplicate option `GEOM_BSD' encountered. WARNING: duplicate option `GEOM_SUNLABEL' encountered. WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. WARNING: duplicate option `SUNKBD_EMULATE_ATKBD' encountered. /src/sys/sparc64/conf/LINT: unknown option "RL_TWISTER_ENABLE" *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-02 20:18:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-02 20:18:55 - ERROR: failed to build lint kernel TB --- 2008-11-02 20:18:55 - tinderbox aborted TB --- 2970.84 user 364.32 system 4184.88 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From tinderbox at freebsd.org Sun Nov 2 12:32:17 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sun Nov 2 12:32:29 2008 Subject: [head tinderbox] failure on sparc64/sun4v Message-ID: <20081102203215.60C4173039@freebsd-current.sentex.ca> TB --- 2008-11-02 19:25:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-02 19:25:56 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-11-02 19:25:56 - cleaning the object tree TB --- 2008-11-02 19:26:22 - cvsupping the source tree TB --- 2008-11-02 19:26:22 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-11-02 19:26:30 - building world (CFLAGS=-O -pipe) TB --- 2008-11-02 19:26:30 - cd /src TB --- 2008-11-02 19:26:30 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 2 19:26:31 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Nov 2 20:32:15 UTC 2008 TB --- 2008-11-02 20:32:15 - generating LINT kernel config TB --- 2008-11-02 20:32:15 - cd /src/sys/sun4v/conf TB --- 2008-11-02 20:32:15 - /usr/bin/make -B LINT TB --- 2008-11-02 20:32:15 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-02 20:32:15 - cd /src TB --- 2008-11-02 20:32:15 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 2 20:32:15 UTC 2008 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/sun4v/conf; PATH=/obj/sun4v/src/tmp/legacy/usr/sbin:/obj/sun4v/src/tmp/legacy/usr/bin:/obj/sun4v/src/tmp/legacy/usr/games:/obj/sun4v/src/tmp/usr/sbin:/obj/sun4v/src/tmp/usr/bin:/obj/sun4v/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/sun4v/src/sys/LINT /src/sys/sun4v/conf/LINT WARNING: duplicate option `GEOM_BSD' encountered. WARNING: duplicate option `GEOM_SUNLABEL' encountered. WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. /src/sys/sun4v/conf/LINT: unknown option "RL_TWISTER_ENABLE" *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-02 20:32:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-02 20:32:15 - ERROR: failed to build lint kernel TB --- 2008-11-02 20:32:15 - tinderbox aborted TB --- 2957.13 user 363.23 system 3978.42 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From yuri.pankov at gmail.com Sun Nov 2 12:45:49 2008 From: yuri.pankov at gmail.com (Yuri Pankov) Date: Sun Nov 2 12:45:55 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <3bbf2fe10811020953l29f1a7eesa4f4eeb49f0a2eba@mail.gmail.com> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <20081102163307.GB1434@darklight.homeunix.org> <3bbf2fe10811020953l29f1a7eesa4f4eeb49f0a2eba@mail.gmail.com> Message-ID: <20081102202211.GA1549@darklight.homeunix.org> On Sun, Nov 02, 2008 at 06:53:25PM +0100, Attilio Rao wrote: > 2008/11/2, Yuri Pankov : > > On Sun, Nov 02, 2008 at 05:17:18PM +0100, Attilio Rao wrote: > > > 2008/11/2, Attilio Rao : > > > > 2008/11/2, Yuri Pankov : > > > > > > > > > Hi, > > > > > > > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > > > > following panic: > > > > > > > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > > > > > > > Unread portion of the kernel message buffer: > > > > > smb_co_lock: recursive lock for object 1 > > > > > panic: Lock (lockmgr) smb_vc not locked @ > > > > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > > > > cpuid = 0 > > > > > KDB: stack backtrace: > > > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > > > panic() at panic+0x182 > > > > > witness_assert() at witness_assert+0x21a > > > > > __lockmgr_args() at __lockmgr_args+0x17a > > > > > smb_co_put() at smb_co_put+0x76 > > > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > > > > smb_usr_lookup() at smb_usr_lookup+0xcd > > > > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > > > > giant_ioctl() at giant_ioctl+0x75 > > > > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > > > > kern_ioctl() at kern_ioctl+0x92 > > > > > ioctl() at ioctl+0xfd > > > > > syscall() at syscall+0x1bf > > > > > Xfast_syscall() at Xfast_syscall+0xab > > > > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > > > > Uptime: 6m46s > > > > > Physical memory: 2032 MB > > > > > > > > > > > > So, what is happening here is that smb_co_lock() is AFU. > > > > Infact looking at the code: > > > > int > > > > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > > > > { > > > > ... > > > > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > > > > (flags & LK_CANRECURSE) == 0) { > > > > SMBERROR("recursive lock for object %d\n", cp->co_level); > > > > return 0; > > > > } > > > > ... > > > > > > Yuri, > > > could you please test this fix: > > > http://www.freebsd.org/~attilio/netsmb.diff > > > > > > and report if it works? > > > You could get a KASSERT running but this is expected as I want to > > > identify on the callers who passes a malformed request and fix it. > > > > > > Thanks, > > > Attilio > > > > > > > > > -- > > > Peace can only be achieved by understanding - A. Einstein > > > > > > Thanks, Attilio. > > > > With this patch system doesn't panic anymore with nonexistent share > > names (though I had to comment out smb_co_lockstatus prototype and > > function to get rid of -Werror complaints). Still getting a LOR: > > > > netsmb_dev: loaded > > lock order reversal: > > 1st 0xffffff0021644008 smb_vc (smb_vc) @ > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:332 > > 2nd 0xffffffff81037368 smbsm (smbsm) @ > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:348 > > > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > > _witness_debugger() at _witness_debugger+0x2e > > witness_checkorder() at witness_checkorder+0x81e > > __lockmgr_args() at __lockmgr_args+0xc2a > > smb_co_lock() at smb_co_lock+0x38 > > smb_co_gone() at smb_co_gone+0x38 > > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > smb_usr_lookup() at smb_usr_lookup+0xcd > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > giant_ioctl() at giant_ioctl+0x75 > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > kern_ioctl() at kern_ioctl+0x92 > > ioctl() at ioctl+0xfd > > syscall() at syscall+0x1bf > > Xfast_syscall() at Xfast_syscall+0xab > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > > 0x7fffffffe048, rbp = 0x7fffffffe460 --- > > I've updated the patch in order to fix smb_co_lockstatus problem. > Could you please stress test it while I investigate the LOR problem? Not sure what do you mean by "stress test". I've tried mounting several different shares and copied ~100Gb from them, hope this should suffice. > Are you running with INVARIANTS? Yes. > > Thanks, > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein Thanks, Yuri From gaijin.k at gmail.com Sun Nov 2 15:15:03 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Sun Nov 2 15:15:10 2008 Subject: ZFS for a desktop computer In-Reply-To: <200811011517.37640.lists@jnielsen.net> References: <20081101114717.0ffc2ec8@valhala> <200811011517.37640.lists@jnielsen.net> Message-ID: <1225667670.12521.7.camel@RabbitsDen> On Sat, 2008-11-01 at 15:17 -0400, John Nielsen wrote: > On Saturday 01 November 2008, Nicolas Martyanoff wrote: > > I'm thinking about switching my main desktop to FreeBSD for various > > reasons (main one, I love it on my laptop and server), and I've been > > considering using ZFS. I'd like to have a disk-modular system, ie.: > > > > - Being able to have mirroring. > > - Being able to add new disks without effort. > > - Being able to add new disks AND mirroring disks (spare disks ?) at > > the same time. > > > > I'm gonna begin with 2x 1TB disks with mirroring, and I'd like to be > > able to add, if needed, new disks, for example 2x 1.5TB to get 2.5TB > > diskspace fully mirrored. The whole process shouldn't need to reinstall > > the system, or to change the slice/partition layout, ie. be totally > > transparent for the data. > > And for this particular need, ZFS seems to be the way to go. > > I'm happily using ZFS on a 32-bit FreeBSD desktop system (that also plays a > home server role). It should meet your disk-modularity requirements above, > with the exception that it's not possible to add disks to a raidZ set > (though it is possible to add additional sets to the same zpool). > > > However, I'm a bit worried about FreeBSD's ZFS implementation: > > > > - I've got a 64bits dual core 2GHz CPU, but can't use an amd64 FreeBSD > > since Xen, NVidia drivers and wine don't work on it; but ZFS is said > > to be unsuitable for i386. > > That's overstating the case. The extra memory headroom on amd64 may make > things simpler, but it's certianly possible to run ZFS on FreeBSD i386 as > long as you have a couple gigs of RAM (I actually only have 1.5 GB) and > follow the tuning guidelines. You should also be willing to monitor your > system and go through one or two fine-tuning cycles Just a "me too". I am using ZFS on my i386 (Core Duo) laptop: / and /boot are UFS2, /usr and /home are ZFS. Main appeal in my case was the startup time after the panic -- doing fsck on 120GB /home was not fun. I have to admit that machine has 3GB of real memory in it, though. -- Alexandre "Sunny" Kovalenko (????????? ?????????) From conrads at cox.net Sun Nov 2 17:49:48 2008 From: conrads at cox.net (Conrad J. Sabatier) Date: Sun Nov 2 17:49:55 2008 Subject: More on non-recognized SATA hardware Message-ID: <20081102194947.031d6896@serene.no-ip.org> I just noticed something today in the boot messages that I hadn't noticed before: it appears that my SATA controller is being probed as a RAID controller, but without any driver being attached. Booting a CURRENT snapshot from 11/02, I'm seeing something like: pci0: at PCI 9.0 (no driver attached) Would it be a simple matter of patching one of the existing RAID hardware drivers (ahci, perhaps?) to recognize my specific device? And if so, how can I go about doing this with no existing FreeBSD installation? Or, could somebody do this for me and create a mini-iso, just enough to get me started with a minimal base system? For what it's worth, here's the relevant info from Ubuntu's lspci command: 00:09.0 RAID bus controller: nVidia Corporation Device 0ad8 (rev a2) Subsystem: Hewlett-Packard Company Device 2a6e Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable+ Address: 00000000fee0f00c Data: 41a9 Capabilities: [ec] HyperTransport: MSI Mapping Enable+ Fixed+ Kernel driver in use: ahci Kernel modules: ahci Please help! I've got a serious FreeBSD jones going on here! It's been about two months now since my last computer died and I've been without FreeBSD ever since. Ubuntu is an OK temporary substitute, but I want my FreeBSD back! :-) Thanks! -- Conrad J. Sabatier From tinderbox at freebsd.org Sun Nov 2 19:00:20 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sun Nov 2 19:00:32 2008 Subject: [head tinderbox] failure on sparc64/sparc64 Message-ID: <20081103030015.4D73273039@freebsd-current.sentex.ca> TB --- 2008-11-03 01:49:36 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-03 01:49:36 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-11-03 01:49:36 - cleaning the object tree TB --- 2008-11-03 01:49:58 - cvsupping the source tree TB --- 2008-11-03 01:49:58 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-03 01:50:04 - building world (CFLAGS=-O -pipe) TB --- 2008-11-03 01:50:04 - cd /src TB --- 2008-11-03 01:50:04 - /usr/bin/make -B buildworld >>> World build started on Mon Nov 3 01:50:09 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Nov 3 03:00:13 UTC 2008 TB --- 2008-11-03 03:00:13 - generating LINT kernel config TB --- 2008-11-03 03:00:13 - cd /src/sys/sparc64/conf TB --- 2008-11-03 03:00:13 - /usr/bin/make -B LINT TB --- 2008-11-03 03:00:13 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-03 03:00:13 - cd /src TB --- 2008-11-03 03:00:13 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 3 03:00:13 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree [...] ===> aio (cleandir) rm -f export_syms aio.ko aio.kld vfs_aio.o opt_vfs_aio.h vnode_if.h vnode_if_newproto.h vnode_if_typedef.h rm -f @ machine rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> amr (cleandir) rm -f export_syms amr.ko amr.kld amr.o amr_pci.o amr_disk.o pci_if.h bus_if.h device_if.h ===> amr/amr_cam (clean) cd: can't cd to /src/sys/modules/amr/amr_cam *** Error code 2 Stop in /src/sys/modules/amr. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-03 03:00:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-03 03:00:15 - ERROR: failed to build lint kernel TB --- 2008-11-03 03:00:15 - tinderbox aborted TB --- 2972.62 user 362.02 system 4238.88 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From tinderbox at freebsd.org Sun Nov 2 19:35:09 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sun Nov 2 19:35:28 2008 Subject: [head tinderbox] failure on sparc64/sun4v Message-ID: <20081103033506.E3E2473039@freebsd-current.sentex.ca> TB --- 2008-11-03 02:33:11 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-03 02:33:11 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-11-03 02:33:11 - cleaning the object tree TB --- 2008-11-03 02:33:28 - cvsupping the source tree TB --- 2008-11-03 02:33:28 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-11-03 02:33:36 - building world (CFLAGS=-O -pipe) TB --- 2008-11-03 02:33:36 - cd /src TB --- 2008-11-03 02:33:36 - /usr/bin/make -B buildworld >>> World build started on Mon Nov 3 02:33:38 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Nov 3 03:35:05 UTC 2008 TB --- 2008-11-03 03:35:05 - generating LINT kernel config TB --- 2008-11-03 03:35:05 - cd /src/sys/sun4v/conf TB --- 2008-11-03 03:35:05 - /usr/bin/make -B LINT TB --- 2008-11-03 03:35:05 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-03 03:35:05 - cd /src TB --- 2008-11-03 03:35:05 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 3 03:35:05 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree [...] ===> aio (cleandir) rm -f export_syms aio.ko aio.kld vfs_aio.o opt_vfs_aio.h vnode_if.h vnode_if_newproto.h vnode_if_typedef.h rm -f @ machine sparc64 rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> amr (cleandir) rm -f export_syms amr.ko amr.kld amr.o amr_pci.o amr_disk.o pci_if.h bus_if.h device_if.h ===> amr/amr_cam (clean) cd: can't cd to /src/sys/modules/amr/amr_cam *** Error code 2 Stop in /src/sys/modules/amr. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sun4v/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-03 03:35:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-03 03:35:06 - ERROR: failed to build lint kernel TB --- 2008-11-03 03:35:06 - tinderbox aborted TB --- 2936.71 user 358.66 system 3715.55 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From tinderbox at freebsd.org Sun Nov 2 21:25:48 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Sun Nov 2 21:26:05 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20081103052544.C884573039@freebsd-current.sentex.ca> TB --- 2008-11-03 03:40:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-03 03:40:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-11-03 03:40:01 - cleaning the object tree TB --- 2008-11-03 03:40:48 - cvsupping the source tree TB --- 2008-11-03 03:40:48 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-11-03 03:40:56 - building world (CFLAGS=-O -pipe) TB --- 2008-11-03 03:40:56 - cd /src TB --- 2008-11-03 03:40:56 - /usr/bin/make -B buildworld >>> World build started on Mon Nov 3 03:40:58 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Mon Nov 3 05:25:41 UTC 2008 TB --- 2008-11-03 05:25:41 - generating LINT kernel config TB --- 2008-11-03 05:25:41 - cd /src/sys/amd64/conf TB --- 2008-11-03 05:25:41 - /usr/bin/make -B LINT TB --- 2008-11-03 05:25:42 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-03 05:25:42 - cd /src TB --- 2008-11-03 05:25:42 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 3 05:25:42 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree [...] ===> aio (cleandir) rm -f export_syms aio.ko aio.kld vfs_aio.o opt_vfs_aio.h vnode_if.h vnode_if_newproto.h vnode_if_typedef.h rm -f @ machine rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> amr (cleandir) rm -f export_syms amr.ko amr.kld amr.o amr_pci.o amr_disk.o pci_if.h bus_if.h device_if.h ===> amr/amr_cam (clean) cd: can't cd to /src/sys/modules/amr/amr_cam *** Error code 2 Stop in /src/sys/modules/amr. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-03 05:25:44 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-03 05:25:44 - ERROR: failed to build lint kernel TB --- 2008-11-03 05:25:44 - tinderbox aborted TB --- 4543.31 user 566.83 system 6343.48 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From kerneljack at gmail.com Mon Nov 3 02:22:13 2008 From: kerneljack at gmail.com (Khusro Jaleel) Date: Mon Nov 3 02:22:22 2008 Subject: problems configuring wireless using iwi In-Reply-To: <490DD114.3000901@math.missouri.edu> References: <490DD114.3000901@math.missouri.edu> Message-ID: Thanks for your reply, Stephen, just a few other questions: Am I supposed to download the firmware from somewhere or not? I tried going to /usr/ports/net/iwi-firmware/ and iwi-firmware-kmod and running "make install" but both of them error out saying something about "please run make rmconfig and remove CONTROL" but when I run "make rmconfig" I get "No user-configurable ...." something like that. I'm still not sure whether I need to get the firmware from somewhere or not? I hope you can clarify this. My /boot/kernel has those iwi_bss.ko etc files that I mentioned, but I'm not sure if those are firmware or not? Should I get the firmware from somewhere and put it in /boot/firmware instead? I will try putting those lines /etc/rc.conf tonight and will see what happens. Thanks again. On Sun, Nov 2, 2008 at 4:11 PM, Stephen Montgomery-Smith wrote: > FreeBSD CURRENT has a different approach to wireless cards. Somewhere in > /etc/rc.conf you need lines like > wlans_iwi0="wlan0" > and then all future ifconfig command should refer to wlan0 instead of iwi0. > > I am not sure if this will fix your problem or not, but you must have not > done this somewhere, otherwise ifconfig would have listed wlan0 as well as > iwi0. > > If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. > I think iwi is already a part of that. > > > Khusro Jaleel wrote: >> >> Hi, >> >> I'm new to FreeBSD-CURRENT and am having problems getting my wireless >> to work on my laptop. It is an old Centrino ASUS laptop with built-in >> IPW2200 wireless. I've had no problems getting wireless to work on >> this for the past few years now with many flavors of linux and of >> course Windows so I'm sure it should also work in FreeBSD without any >> issues. >> >> However, I'm not having much luck. I've followed the instructions in >> the Handbook's Wireless page and read the iwi(4) man page and added >> the following to my /boot/loader.conf: >> >> ------------- >> legal.intel_iwi.license_ack=1 >> if_iwi_load="YES" >> wlan_load="YES" >> firmware_load="YES" >> iwi_bss_load="YES" >> iwi_ibss_load="YES" >> iwi_monitor_load="YES" >> hw.psm.synaptics_support=1 >> -------------- >> >> When I reboot and do a "dmesg | grep iwi" I get: >> >> ---------- >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> ---------- >> >> Am I forgetting to load the firmware somehow? In /boot/kernel, I see >> the following files: >> >> ----------- >> [root@asus ~]# ls -l /boot/kernel/iwi_* >> -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko >> -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko >> -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko >> ----------- >> >> ifconfig: >> bge0: flags=8843 metric 0 mtu 1500 >> options=9b >> ether 00:11:2f:0c:e8:7f >> inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 >> media: Ethernet autoselect (100baseTX ) >> status: active >> fwe0: flags=8802 metric 0 mtu 1500 >> options=8 >> ether 02:e0:18:1b:1f:63 >> ch 1 dma -1 >> fwip0: flags=8802 metric 0 mtu 1500 >> lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 >> iwi0: flags=8803 metric 0 mtu 2290 >> ether 00:0e:35:0d:7c:65 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> plip0: flags=108810 metric 0 mtu >> 1500 >> lo0: flags=8049 metric 0 mtu 16384 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 >> inet6 ::1 prefixlen 128 >> inet 127.0.0.1 netmask 0xff000000 >> >> But if I try to do "ifconfig iwi0 up" I get: >> >> ---------- >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> ---------- >> >> Any help appreciated. Thanks. >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> >> > > From onemda at gmail.com Mon Nov 3 04:40:40 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Mon Nov 3 04:40:50 2008 Subject: problems configuring wireless using iwi In-Reply-To: References: <490DD114.3000901@math.missouri.edu> Message-ID: <3a142e750811030440u66c6e320sd2f1a414480d27d9@mail.gmail.com> On 11/3/08, Khusro Jaleel wrote: > Thanks for your reply, Stephen, just a few other questions: > > Am I supposed to download the firmware from somewhere or not? > > I tried going to /usr/ports/net/iwi-firmware/ and iwi-firmware-kmod > and running "make install" but both of them error out saying something > about "please run make rmconfig and remove CONTROL" but when I run > "make rmconfig" I get "No user-configurable ...." something like that. > > I'm still not sure whether I need to get the firmware from somewhere > or not? I hope you can clarify this. My /boot/kernel has those > iwi_bss.ko etc files that I mentioned, but I'm not sure if those are > firmware or not? Should I get the firmware from somewhere and put it > in /boot/firmware instead? iwi_bss.ko module and others are firmware for iwi and their Makefiles are located in /sys/modules/iwifw Firmware files are located in: /sys/contrib/dev/iwi/ > I will try putting those lines /etc/rc.conf tonight and will see what > happens. > > Thanks again. > > On Sun, Nov 2, 2008 at 4:11 PM, Stephen Montgomery-Smith > wrote: >> FreeBSD CURRENT has a different approach to wireless cards. Somewhere in >> /etc/rc.conf you need lines like >> wlans_iwi0="wlan0" >> and then all future ifconfig command should refer to wlan0 instead of >> iwi0. >> >> I am not sure if this will fix your problem or not, but you must have not >> done this somewhere, otherwise ifconfig would have listed wlan0 as well as >> iwi0. >> >> If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. >> I think iwi is already a part of that. >> >> >> Khusro Jaleel wrote: >>> >>> Hi, >>> >>> I'm new to FreeBSD-CURRENT and am having problems getting my wireless >>> to work on my laptop. It is an old Centrino ASUS laptop with built-in >>> IPW2200 wireless. I've had no problems getting wireless to work on >>> this for the past few years now with many flavors of linux and of >>> course Windows so I'm sure it should also work in FreeBSD without any >>> issues. >>> >>> However, I'm not having much luck. I've followed the instructions in >>> the Handbook's Wireless page and read the iwi(4) man page and added >>> the following to my /boot/loader.conf: >>> >>> ------------- >>> legal.intel_iwi.license_ack=1 >>> if_iwi_load="YES" >>> wlan_load="YES" >>> firmware_load="YES" >>> iwi_bss_load="YES" >>> iwi_ibss_load="YES" >>> iwi_monitor_load="YES" >>> hw.psm.synaptics_support=1 >>> -------------- >>> >>> When I reboot and do a "dmesg | grep iwi" I get: >>> >>> ---------- >>> iwi0: mem 0xff9de000-0xff9defff irq 4 >>> at device 2.0 on pci2 >>> iwi0: [ITHREAD] >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: mem 0xff9de000-0xff9defff irq 4 >>> at device 2.0 on pci2 >>> iwi0: [ITHREAD] >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: mem 0xff9de000-0xff9defff irq 4 >>> at device 2.0 on pci2 >>> iwi0: [ITHREAD] >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: mem 0xff9de000-0xff9defff irq 4 >>> at device 2.0 on pci2 >>> iwi0: [ITHREAD] >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> ---------- >>> >>> Am I forgetting to load the firmware somehow? In /boot/kernel, I see >>> the following files: >>> >>> ----------- >>> [root@asus ~]# ls -l /boot/kernel/iwi_* >>> -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko >>> -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko >>> -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 >>> /boot/kernel/iwi_monitor.ko >>> ----------- >>> >>> ifconfig: >>> bge0: flags=8843 metric 0 mtu >>> 1500 >>> options=9b >>> ether 00:11:2f:0c:e8:7f >>> inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 >>> media: Ethernet autoselect (100baseTX ) >>> status: active >>> fwe0: flags=8802 metric 0 mtu 1500 >>> options=8 >>> ether 02:e0:18:1b:1f:63 >>> ch 1 dma -1 >>> fwip0: flags=8802 metric 0 mtu 1500 >>> lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 >>> iwi0: flags=8803 metric 0 mtu 2290 >>> ether 00:0e:35:0d:7c:65 >>> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >>> status: no carrier >>> plip0: flags=108810 metric 0 >>> mtu >>> 1500 >>> lo0: flags=8049 metric 0 mtu 16384 >>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 >>> inet6 ::1 prefixlen 128 >>> inet 127.0.0.1 netmask 0xff000000 >>> >>> But if I try to do "ifconfig iwi0 up" I get: >>> >>> ---------- >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> ---------- >>> >>> Any help appreciated. Thanks. >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >>> >>> >> >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From jonathan at onegoodidea.com Mon Nov 3 04:49:27 2008 From: jonathan at onegoodidea.com (Jonathan Hogg) Date: Mon Nov 3 04:49:34 2008 Subject: ZFS for a desktop computer In-Reply-To: <1225667670.12521.7.camel@RabbitsDen> References: <20081101114717.0ffc2ec8@valhala> <200811011517.37640.lists@jnielsen.net> <1225667670.12521.7.camel@RabbitsDen> Message-ID: <3BB3B5B4-D3A7-4A1E-A5F5-3B33B6479154@onegoodidea.com> On 2 Nov 2008, at 23:14, Alexandre Sunny Kovalenko wrote: > Just a "me too". I am using ZFS on my i386 (Core Duo) laptop: / > and /boot are UFS2, /usr and /home are ZFS. Main appeal in my case was > the startup time after the panic -- doing fsck on 120GB /home was not > fun. I have to admit that machine has 3GB of real memory in it, > though. I have everything except /boot on ZFS on an i386 machine with 2GB of RAM. I've not had any problems. Being able to snapshot the whole system before doing an installworld is a major plus in my view. Not to mention the warm fuzzy feeling one gets from doing a full scrub of 1.5TB of RAIDZ data and knowing it's all clean on disk. I'd be happier still if the more recent ZFS patch had made it into 7.1. It'd be nice for it to make it into CURRENT at least. Is there any news on that? Jonathan From rea-fbsd at codelabs.ru Mon Nov 3 08:37:15 2008 From: rea-fbsd at codelabs.ru (Eygene Ryabinkin) Date: Mon Nov 3 08:37:22 2008 Subject: problems configuring wireless using iwi In-Reply-To: References: <490DD114.3000901@math.missouri.edu> Message-ID: <3q3LHpRtXrg+xqcqNOM7j33dNpE@Nxyl89WskzuM4RJ7pF/cdJZbOMo> Mon, Nov 03, 2008 at 10:22:12AM +0000, Khusro Jaleel wrote: > Am I supposed to download the firmware from somewhere or not? It should be built as a kernel module. In 7.x it is already included to the base system, so there is no need for the port. As written in iwi(4), include the following devices to the kernel configuration, ----- device iwi device pci device wlan device firmware ----- and make sure that the iwifw module is built. If you have no 'makeoptions MODULES_OVERRIDE=""' directives in the kernel configuration, then you should already have the module. If not, add the 'iwifw' to the MODULES_OVERRIDE contents. The actual module should be in the /boot/kernel, named iwifw.ko. Your error messages indicate that you likely have no /boot/kernel/iwifw.ko. Of course, your actual mileage may vary. For the custom kernels, make sure that you have some 802.11 stuff included: ----- device wlan_wep # 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support ----- The actual devices depend on your needs, but it is safe to include them all -- you can never know what encryption you'll be using. -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081103/c105a231/attachment.pgp From bsam at ipt.ru Mon Nov 3 09:23:06 2008 From: bsam at ipt.ru (Boris Samorodov) Date: Mon Nov 3 09:23:14 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <20081030114845.GE78796@cdnetworks.co.kr> (Pyun YongHyeon's message of "Thu\, 30 Oct 2008 20\:48\:45 +0900") References: <20081030040637.GA78796@cdnetworks.co.kr> <20081030114845.GE78796@cdnetworks.co.kr> Message-ID: <14721476@bb.ipt.ru> Pyun YongHyeon writes: > As bruffer pointed out the device name chosen conflicts with other > driver in tree so I renamed it to ale(4).The URL for the driver is > http://people.freebsd.org/~yongari/ale/if_ale.c > http://people.freebsd.org/~yongari/ale/if_alereg.h > http://people.freebsd.org/~yongari/ale/if_alevar.h > http://people.freebsd.org/~yongari/ale/Makefile > or > http://people.freebsd.org/~yongari/ale/ale.20081030.tar.gz > Sorry for confusion. Tested at EeePC-1000, works fine. BIG thank you, much appreciated. Here is some additional info. -- dmesg -- ale0: port 0xec80-0xecff mem 0xfbfc0000-0xfbffffff irq 17 at device 0.0 on pci4 ale0: Reserved 0x40000 bytes for rid 0x10 type 3 at 0xfbfc0000 ale0: PCI device revision : 0x00b0 ale0: Chip id/revision : 0xb002 ale0: 960 Tx FIFO, 1024 Rx FIFO ale0: MSIX count : 0 ale0: MSI count : 1 ale0: attempting to allocate 1 MSI vectors (1 supported) ale0: using IRQ 256 for MSI ale0: Using 1 MSI messages. ale0: Read request size : 512 bytes. ale0: TLP payload size : 128 bytes. ale0: bpf attached ale0: Ethernet address: 00:22:15:91:e7:98 ale0: [MPSAFE] ale0: [FILTER] ale0: link state changed to DOWN ale0: interrupt moderation is 100 us. ale0: link state changed to UP -- pciconf -- ale0@pci0:4:0:0: class=0x020000 card=0x83241043 chip=0x10261969 rev=0xb0 hdr=0x00 vendor = 'Attansic (Now owned by Atheros)' class = network subclass = ethernet -- devinfo -- pci4 ale0 pnpinfo vendor=0x1969 device=0x1026 subvendor=0x1043 subdevice=0x8324 class=0x020000 at slot=0 function=0 Interrupt request lines: 256 I/O ports: 0xec80-0xecff I/O memory addresses: 0xfbfc0000-0xfbffffff miibus0 atphy0 pnpinfo oui=0x1374 model=0x1 rev=0x9 at phyno=0 ----- WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From onemda at gmail.com Mon Nov 3 09:30:51 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Mon Nov 3 09:30:59 2008 Subject: problems configuring wireless using iwi In-Reply-To: <3q3LHpRtXrg+xqcqNOM7j33dNpE@Nxyl89WskzuM4RJ7pF/cdJZbOMo> References: <490DD114.3000901@math.missouri.edu> <3q3LHpRtXrg+xqcqNOM7j33dNpE@Nxyl89WskzuM4RJ7pF/cdJZbOMo> Message-ID: <3a142e750811030930j7916137drfe0c72dc4dfd873a@mail.gmail.com> On 11/3/08, Eygene Ryabinkin wrote: > Mon, Nov 03, 2008 at 10:22:12AM +0000, Khusro Jaleel wrote: >> Am I supposed to download the firmware from somewhere or not? > > It should be built as a kernel module. In 7.x it is already included > to the base system, so there is no need for the port. > > As written in iwi(4), include the following devices to the kernel > configuration, > ----- > device iwi > device pci > device wlan > device firmware > ----- > and make sure that the iwifw module is built. If you have no > 'makeoptions MODULES_OVERRIDE=""' directives in the kernel > configuration, then you should already have the module. If not, add the > 'iwifw' to the MODULES_OVERRIDE contents. The actual module should be > in the /boot/kernel, named iwifw.ko. OP is using CURRENT where iwifw.ko is split in several files. It is not required to build custom kernel just to have iwi support. > Your error messages indicate that you likely have no /boot/kernel/iwifw.ko. > Of course, your actual mileage may vary. > > For the custom kernels, make sure that you have some 802.11 stuff > included: > ----- > device wlan_wep # 802.11 WEP support > device wlan_ccmp # 802.11 CCMP support > device wlan_tkip # 802.11 TKIP support > ----- > The actual devices depend on your needs, but it is safe to include them > all -- you can never know what encryption you'll be using. > -- More debug output from iwi would be more useful. Something like: # sysctl dev.iwi.0.debug=1 From shuvaev at physik.uni-wuerzburg.de Mon Nov 3 10:35:58 2008 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Mon Nov 3 10:36:05 2008 Subject: Call for testers: fxp(4) WOL In-Reply-To: <20081015003745.GG14769@cdnetworks.co.kr> References: <20081015003745.GG14769@cdnetworks.co.kr> Message-ID: <20081103183556.GA2009@localhost.my.domain> On Wed, Oct 15, 2008 at 09:37:45AM +0900, Pyun YongHyeon wrote: > I've implemented WOL for fxp(4) and it works ok to me. Because > there too many variants of fxp(4) hardwares I'd like to hear > success/failure report before committing attached patch to tree. > It seems that the following Intel 8255x supports WOL. Apparently > 82557 lacks WOL capabillity. > > 82558 > 82559 > 82550 > 82551 > How can one figure out which chip he has? I have relative old Toshiba notebook with integrated intel network card. The system is: FreeBSD localhost.my.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Oct 27 01:25:54 CET 2008 root@localhost.my.domain:/usr/obj/usr/src/sys/GENERIC i386 Here are relevant messages from the verbose boot: fxp0: port 0xdf40-0xdf7f mem 0xfceff000-0xfcefffff irq 11 at device 8.0 on pci2 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfceff000 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 1031 1179 0001 0042 fxp0: Dynamic Standby mode is disabled miibus0: on fxp0 fxp0: XXX: driver didn't set ifq_maxlen ^^^ Is this something to fix? fxp0: bpf attached fxp0: Ethernet address: xx:xx:xx:xx:xx:xx fxp0: [MPSAFE] fxp0: [ITHREAD] and this is the output from pciconv -lvc: fxp0@pci0:2:8:0: class=0x020000 card=0x00011179 chip=0x10318086 rev=0x42 hdr=0x00 vendor = 'Intel Corporation' device = '82801CAM (ICH3) PRO/100 VE (LOM) Network Connection' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D1 D2 D3 current D0 It seems that driver changes something, after boot or 'ifconfig fxp0 wol': fxp0: flags=8843 metric 0 mtu 1500 options=2008 and after 'ifconfig fxp0 -wol': fxp0: flags=8843 metric 0 mtu 1500 options=8 However the system seems to honors only the BIOS settings, if I enable WOL in the BIOS the system wakes up from power-down or suspend (to ram) states regardless of fxp settings and with disabled WOL in BIOS it never wakes up. The worse thing I have noticed is if I send WOL packet while the system is running it reliably hangs. It does not panic and switching virtual consoles works (and typing/deleting something in the shell prompt too), but the cooler runs at full power and you can't do anything else. This is both with patched fxp and that from -CURRENT. > If your suspend/resume works on your system you can also wake up > your system in suspend by WOL. > Actually, the system does not wake up from suspended mode properly, either by power button or by WOL packet, but it tries. > Thanks. Thank you, if you need something more (debugging output, testing new patches, digging deeper...) just let me know. Alexey. From me at janh.de Mon Nov 3 11:04:46 2008 From: me at janh.de (Jan Henrik Sylvester) Date: Mon Nov 3 11:41:31 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet References: 20081030114845.GE78796@cdnetworks.co.kr Message-ID: <490F47BE.9080205@janh.de> Boris wrote: >Pyun YongHyeon writes: > >> As bruffer pointed out the device name chosen conflicts with other >> driver in tree so I renamed it to ale(4).The URL for the driver is >> http://people.freebsd.org/~yongari/ale/if_ale.c >> http://people.freebsd.org/~yongari/ale/if_alereg.h >> http://people.freebsd.org/~yongari/ale/if_alevar.h >> http://people.freebsd.org/~yongari/ale/Makefile >> or >> http://people.freebsd.org/~yongari/ale/ale.20081030.tar.gz >> Sorry for confusion. > >Tested at EeePC-1000, works fine. BIG thank you, much appreciated. I got an Eee PC 1000H, too, with 7.1-BETA2 and just used scp to copy with 11.5MB/s -- much better than wlan for big files. Great! This will probably not go into 7.1-RELEASE, will it? Thanks! Jan Henrik From rohit.x.tripathi at jpmchase.com Mon Nov 3 12:56:07 2008 From: rohit.x.tripathi at jpmchase.com (rohit.x.tripathi@jpmchase.com) Date: Mon Nov 3 12:56:17 2008 Subject: ndis fix near? In-Reply-To: <490F47BE.9080205@janh.de> Message-ID: I was quite happy with 7.0 until I found that it doesn't support 4965 AGN card and then switched to CURRENT. Now that ndis isn't working, I want to offer help but know very little about wifi devices and freebsd code to contribute anything. If someone's already working on it, it'll be great to let us know. regards, Rohit P.S. please pardon the lengthy disclaimer below my email..its appended automatically by outgoing servers at my company. ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities. From jhb at freebsd.org Mon Nov 3 13:03:55 2008 From: jhb at freebsd.org (John Baldwin) Date: Mon Nov 3 13:04:07 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> Message-ID: <200811031458.42549.jhb@freebsd.org> On Sunday 02 November 2008 11:17:18 am Attilio Rao wrote: > 2008/11/2, Attilio Rao : > > 2008/11/2, Yuri Pankov : > > > > > Hi, > > > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > > following panic: > > > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > > > Unread portion of the kernel message buffer: > > > smb_co_lock: recursive lock for object 1 > > > panic: Lock (lockmgr) smb_vc not locked @ > > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > > cpuid = 0 > > > KDB: stack backtrace: > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > panic() at panic+0x182 > > > witness_assert() at witness_assert+0x21a > > > __lockmgr_args() at __lockmgr_args+0x17a > > > smb_co_put() at smb_co_put+0x76 > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > > smb_usr_lookup() at smb_usr_lookup+0xcd > > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > > giant_ioctl() at giant_ioctl+0x75 > > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > > kern_ioctl() at kern_ioctl+0x92 > > > ioctl() at ioctl+0xfd > > > syscall() at syscall+0x1bf > > > Xfast_syscall() at Xfast_syscall+0xab > > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > > Uptime: 6m46s > > > Physical memory: 2032 MB > > > > > > So, what is happening here is that smb_co_lock() is AFU. > > Infact looking at the code: > > int > > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > > { > > ... > > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > > (flags & LK_CANRECURSE) == 0) { > > SMBERROR("recursive lock for object %d\n", cp->co_level); > > return 0; > > } > > ... > > Yuri, > could you please test this fix: > http://www.freebsd.org/~attilio/netsmb.diff > > and report if it works? > You could get a KASSERT running but this is expected as I want to > identify on the callers who passes a malformed request and fix it. This allows all smb locks to recurse unlike the original code I think. It may be better if smb_vclist was initialized with LK_RECURSE, but not all the other smb locks. Also, in smb_co_addchild() I think you should just replace the existing asserts with appropriate lockmgr_assert() (you could add a smb_co_assert() to preserve the layering) rather than removing assertions altogether. -- John Baldwin From rwatson at FreeBSD.org Mon Nov 3 13:07:28 2008 From: rwatson at FreeBSD.org (Robert Watson) Date: Mon Nov 3 13:07:40 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <200811031458.42549.jhb@freebsd.org> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> Message-ID: On Mon, 3 Nov 2008, John Baldwin wrote: >> Yuri, could you please test this fix: >> http://www.freebsd.org/~attilio/netsmb.diff >> >> and report if it works? You could get a KASSERT running but this is >> expected as I want to identify on the callers who passes a malformed >> request and fix it. > > This allows all smb locks to recurse unlike the original code I think. It > may be better if smb_vclist was initialized with LK_RECURSE, but not all the > other smb locks. Also, in smb_co_addchild() I think you should just replace > the existing asserts with appropriate lockmgr_assert() (you could add a > smb_co_assert() to preserve the layering) rather than removing assertions > altogether. My general feeling is that the locking in netsmb needs a bit of cleanup, updating, etc. I'm reluctant to change the underlying primitives (as this patch does) without first clarifying what's going on in the code a layer or two above. Robert N M Watson Computer Laboratory University of Cambridge From attilio at freebsd.org Mon Nov 3 13:20:06 2008 From: attilio at freebsd.org (Attilio Rao) Date: Mon Nov 3 13:20:20 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> Message-ID: <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> 2008/11/3, Robert Watson : > On Mon, 3 Nov 2008, John Baldwin wrote: > > > > > > > Yuri, could you please test this fix: > http://www.freebsd.org/~attilio/netsmb.diff > > > > > > and report if it works? You could get a KASSERT running but this is > expected as I want to identify on the callers who passes a malformed request > and fix it. > > > > > > > This allows all smb locks to recurse unlike the original code I think. It > may be better if smb_vclist was initialized with LK_RECURSE, but not all the > other smb locks. Also, in smb_co_addchild() I think you should just replace > the existing asserts with appropriate lockmgr_assert() (you could add a > smb_co_assert() to preserve the layering) rather than removing assertions > altogether. > > > > My general feeling is that the locking in netsmb needs a bit of cleanup, > updating, etc. I'm reluctant to change the underlying primitives (as this > patch does) without first clarifying what's going on in the code a layer or > two above. I agree with Robert. We need to make an upper layers analysis and decide what is the best solution for locks. This was a quick hack just to let it not panic when mounting. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From kerneljack at gmail.com Mon Nov 3 13:23:19 2008 From: kerneljack at gmail.com (Khusro Jaleel) Date: Mon Nov 3 13:23:27 2008 Subject: problems configuring wireless using iwi In-Reply-To: <490DD114.3000901@math.missouri.edu> References: <490DD114.3000901@math.missouri.edu> Message-ID: Thanks for all your kind replies, Stephen got it right! All I needed to do was add a line like he suggested in /etc/rc.conf and everything just worked straight away after that. No need to get firmware or anything else. I did however manage to completely spontaneously rebooot my laptop by trying to run "/etc/rc.d/netif restart" a few too many times, which I thought should never happen in FreeBSD ... but anyway, all is fine now. Thanks for all your help. On Sun, Nov 2, 2008 at 4:11 PM, Stephen Montgomery-Smith wrote: > FreeBSD CURRENT has a different approach to wireless cards. Somewhere in > /etc/rc.conf you need lines like > wlans_iwi0="wlan0" > and then all future ifconfig command should refer to wlan0 instead of iwi0. > > I am not sure if this will fix your problem or not, but you must have not > done this somewhere, otherwise ifconfig would have listed wlan0 as well as > iwi0. > > If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. > I think iwi is already a part of that. > > > Khusro Jaleel wrote: >> >> Hi, >> >> I'm new to FreeBSD-CURRENT and am having problems getting my wireless >> to work on my laptop. It is an old Centrino ASUS laptop with built-in >> IPW2200 wireless. I've had no problems getting wireless to work on >> this for the past few years now with many flavors of linux and of >> course Windows so I'm sure it should also work in FreeBSD without any >> issues. >> >> However, I'm not having much luck. I've followed the instructions in >> the Handbook's Wireless page and read the iwi(4) man page and added >> the following to my /boot/loader.conf: >> >> ------------- >> legal.intel_iwi.license_ack=1 >> if_iwi_load="YES" >> wlan_load="YES" >> firmware_load="YES" >> iwi_bss_load="YES" >> iwi_ibss_load="YES" >> iwi_monitor_load="YES" >> hw.psm.synaptics_support=1 >> -------------- >> >> When I reboot and do a "dmesg | grep iwi" I get: >> >> ---------- >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> ---------- >> >> Am I forgetting to load the firmware somehow? In /boot/kernel, I see >> the following files: >> >> ----------- >> [root@asus ~]# ls -l /boot/kernel/iwi_* >> -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko >> -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko >> -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko >> ----------- >> >> ifconfig: >> bge0: flags=8843 metric 0 mtu 1500 >> options=9b >> ether 00:11:2f:0c:e8:7f >> inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 >> media: Ethernet autoselect (100baseTX ) >> status: active >> fwe0: flags=8802 metric 0 mtu 1500 >> options=8 >> ether 02:e0:18:1b:1f:63 >> ch 1 dma -1 >> fwip0: flags=8802 metric 0 mtu 1500 >> lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 >> iwi0: flags=8803 metric 0 mtu 2290 >> ether 00:0e:35:0d:7c:65 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> plip0: flags=108810 metric 0 mtu >> 1500 >> lo0: flags=8049 metric 0 mtu 16384 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 >> inet6 ::1 prefixlen 128 >> inet 127.0.0.1 netmask 0xff000000 >> >> But if I try to do "ifconfig iwi0 up" I get: >> >> ---------- >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> ---------- >> >> Any help appreciated. Thanks. >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> >> > > From nick at van-laarhoven.org Mon Nov 3 14:31:22 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Mon Nov 3 14:31:30 2008 Subject: problems with wireless using iwi drivers In-Reply-To: References: Message-ID: <200811032331.14854.nick@van-laarhoven.org> > ------------- > legal.intel_iwi.license_ack=1 > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > iwi_bss_load="YES" > iwi_ibss_load="YES" > iwi_monitor_load="YES" > hw.psm.synaptics_support=1 > -------------- I don't have any of the iwi_*_load="YES" in my kernel config and it still has loaded the firmware alright. Loading 3 different ones looks wrong to me. 100%|nick@hind:/usr/home/nick % kldstat |grep iwi 16 1 0xc4088000 30000 iwi_bss.ko iwi is in the kernel, as is firmware. Have you installed the iwi-firmware port? I guess you have. Nick From fbsd-fs at mawer.org Mon Nov 3 14:48:18 2008 From: fbsd-fs at mawer.org (Antony Mawer) Date: Mon Nov 3 15:03:35 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> Message-ID: <490F77ED.9050501@mawer.org> Attilio Rao wrote: > 2008/11/3, Robert Watson : >> On Mon, 3 Nov 2008, John Baldwin wrote: >>>> Yuri, could you please test this fix: >> http://www.freebsd.org/~attilio/netsmb.diff >>>> and report if it works? You could get a KASSERT running but this is >> expected as I want to identify on the callers who passes a malformed request >> and fix it. >>> This allows all smb locks to recurse unlike the original code I think. It >> may be better if smb_vclist was initialized with LK_RECURSE, but not all the >> other smb locks. Also, in smb_co_addchild() I think you should just replace >> the existing asserts with appropriate lockmgr_assert() (you could add a >> smb_co_assert() to preserve the layering) rather than removing assertions >> altogether. >> My general feeling is that the locking in netsmb needs a bit of cleanup, >> updating, etc. I'm reluctant to change the underlying primitives (as this >> patch does) without first clarifying what's going on in the code a layer or >> two above. > > I agree with Robert. > We need to make an upper layers analysis and decide what is the best > solution for locks. > This was a quick hack just to let it not panic when mounting. This probably also applies to NWFS and netncp as well -- I haven't had a chance to test NWFS in 7.x as of yet, but will hope to do so in the coming months... --Antony From rwatson at FreeBSD.org Mon Nov 3 15:11:39 2008 From: rwatson at FreeBSD.org (Robert Watson) Date: Mon Nov 3 15:11:51 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <490F77ED.9050501@mawer.org> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> <490F77ED.9050501@mawer.org> Message-ID: On Tue, 4 Nov 2008, Antony Mawer wrote: > This probably also applies to NWFS and netncp as well -- I haven't had a > chance to test NWFS in 7.x as of yet, but will hope to do so in the coming > months... Ah, someone who actually uses netncp and nwfs! I've been trying to keep the ipx/spx code alive and working through the MPSAFE network stack work, but I'm really not set up to test that, let alone the Netware file system parts. Let us know how it goes. The netsmb and netncp code is well-structured, but designed with pre-SMPng locking primitives and network stack in mind, so will need quite a bit of work to pull forwards. As Attilio has already been running into, netsmb has rather intimate knowledge and reliance on some of the more obscure behaviors of lockmgr :-). This is something that will need to be fairly high on the list of things to change. Apple has started doing some of this in their fork of our netsmb code, but there's a lot more to do I think. Robert N M Watson Computer Laboratory University of Cambridge From sgk at troutmask.apl.washington.edu Mon Nov 3 15:20:10 2008 From: sgk at troutmask.apl.washington.edu (Steve Kargl) Date: Mon Nov 3 15:20:17 2008 Subject: TTY or SSH character echoing issue Message-ID: <20081103232009.GA3161@troutmask.apl.washington.edu> With current source of 16 Oct 08, I'm seeing a seemly strange echoing problem when I use ssh to connect from one node in my cluster to another. At the (t)csh command line prompt, I want to execute ~/trunk/cmd. So, I have % ~/trunk/cmd The strange behavior is that the ~ character does not appear on the terminal until after I enter the / character. Any advice at determining whether this a tty or ssh or some other problem would be appreciated. -- Steve From ivoras at gmail.com Mon Nov 3 15:54:18 2008 From: ivoras at gmail.com (Ivan Voras) Date: Mon Nov 3 16:20:34 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> <490F77ED.9050501@mawer.org> Message-ID: <9bbcef730811031554m61bc6762g7f503ad56f0981bd@mail.gmail.com> 2008/11/4 Robert Watson : >Apple has started doing > some of this in their fork of our netsmb code, but there's a lot more to do > I think. Like replacing SMB with CIFS :) I think that right now the only operating systems that use plain old SMB instead of CIFS are Windows 98, NT 4 and FreeBSD :) From aragon at phat.za.net Mon Nov 3 16:24:24 2008 From: aragon at phat.za.net (Aragon Gouveia) Date: Mon Nov 3 16:24:31 2008 Subject: TTY or SSH character echoing issue Message-ID: <20081104000431.GA94638@phat.za.net> Hi, > % ~/trunk/cmd > > The strange behavior is that the ~ character does not > appear on the terminal until after I enter the / character. In SSH (OpenSSH in any case), ~ is an escape character if sent on a newline. What you describe sounds normal. It can be changed if necessary. See the -e argument and EscapeChar configuration directive in ssh(1). Regards, Aragon From pyunyh at gmail.com Mon Nov 3 17:44:51 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Mon Nov 3 17:44:58 2008 Subject: Call for testers: fxp(4) WOL In-Reply-To: <20081103183556.GA2009@localhost.my.domain> References: <20081015003745.GG14769@cdnetworks.co.kr> <20081103183556.GA2009@localhost.my.domain> Message-ID: <20081104014246.GA98154@cdnetworks.co.kr> On Mon, Nov 03, 2008 at 07:35:56PM +0100, Alexey Shuvaev wrote: > On Wed, Oct 15, 2008 at 09:37:45AM +0900, Pyun YongHyeon wrote: > > I've implemented WOL for fxp(4) and it works ok to me. Because > > there too many variants of fxp(4) hardwares I'd like to hear > > success/failure report before committing attached patch to tree. > > It seems that the following Intel 8255x supports WOL. Apparently > > 82557 lacks WOL capabillity. > > > > 82558 > > 82559 > > 82550 > > 82551 > > > How can one figure out which chip he has? > I have relative old Toshiba notebook with integrated intel network card. > The system is: > > FreeBSD localhost.my.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Oct 27 01:25:54 CET 2008 root@localhost.my.domain:/usr/obj/usr/src/sys/GENERIC i386 > > Here are relevant messages from the verbose boot: > > fxp0: port 0xdf40-0xdf7f mem 0xfceff000-0xfcefffff irq 11 at device 8.0 on pci2 If it's based on ICH controller it would be 82559. > fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfceff000 > fxp0: using memory space register mapping > fxp0: PCI IDs: 8086 1031 1179 0001 0042 > fxp0: Dynamic Standby mode is disabled > miibus0: on fxp0 > fxp0: XXX: driver didn't set ifq_maxlen > ^^^ > Is this something to fix? > fxp(4) didn't set ifq_maxlen and if_attach corrected this with its default value. Normally network device drivers set this queue length to number of Tx descriptors but it's completely up to driver writers and I don't see compeling reason to change that. > fxp0: bpf attached > fxp0: Ethernet address: xx:xx:xx:xx:xx:xx > fxp0: [MPSAFE] > fxp0: [ITHREAD] > > and this is the output from pciconv -lvc: > > fxp0@pci0:2:8:0: class=0x020000 card=0x00011179 chip=0x10318086 rev=0x42 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801CAM (ICH3) PRO/100 VE (LOM) Network Connection' > class = network > subclass = ethernet > cap 01[dc] = powerspec 2 supports D0 D1 D2 D3 current D0 > > It seems that driver changes something, after boot or 'ifconfig fxp0 wol': > > fxp0: flags=8843 metric 0 mtu 1500 > options=2008 > It indicates your controller supports WOL with magic packet. > and after 'ifconfig fxp0 -wol': > > fxp0: flags=8843 metric 0 mtu 1500 > options=8 > > However the system seems to honors only the BIOS settings, if I enable WOL in > the BIOS the system wakes up from power-down or suspend (to ram) states > regardless of fxp settings and with disabled WOL in BIOS it never > wakes up. > Yes that's an expected behaviour. BIOS option should be changed to enable WOL if you want to wake up your box from power down. If you don't want to wake up your box regardless of BIOS configuration you have to disable WOL with ifconfig before shutting down your box. Likewise even if you enable WOL with ifconfig(8) to wake up your system, BIOS WOL option also should be enabled to make it work. > The worse thing I have noticed is if I send WOL packet while the system is > running it reliably hangs. It does not panic and switching virtual > consoles works (and typing/deleting something in the shell prompt too), > but the cooler runs at full power and you can't do anything else. > This is both with patched fxp and that from -CURRENT. Hmm, I think that was old bebahviour of stock fxp(4). Previously fxp(4) was programmed to accept WOL packets regardless of running state of hardware. With my patch the WOL should be disabled for normal operation and WOL is enabled again when you shutdown your box. If sotck fxp(4) also show the same behaviour it's big security hole. ATM I have no idea how WOL packets can affect running box. :-( > > > If your suspend/resume works on your system you can also wake up > > your system in suspend by WOL. > > > Actually, the system does not wake up from suspended mode properly, either > by power button or by WOL packet, but it tries. > The system I tried didn't resume properly (blank screen) but I could login via network after sending WOL magic packets so I thought resume also works. > > Thanks. > Thank you, if you need something more (debugging output, > testing new patches, digging deeper...) just let me know. Thanks for testing. I'll think again. By chance can you try Linux on your system and check whether it works? -- Regards, Pyun YongHyeon From pyunyh at gmail.com Mon Nov 3 17:54:41 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Mon Nov 3 17:54:47 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <490F47BE.9080205@janh.de> References: <490F47BE.9080205@janh.de> Message-ID: <20081104015235.GC98154@cdnetworks.co.kr> On Mon, Nov 03, 2008 at 07:49:34PM +0100, Jan Henrik Sylvester wrote: > Boris wrote: > >Pyun YongHyeon writes: > > > >> As bruffer pointed out the device name chosen conflicts with other > >> driver in tree so I renamed it to ale(4).The URL for the driver is > >> http://people.freebsd.org/~yongari/ale/if_ale.c > >> http://people.freebsd.org/~yongari/ale/if_alereg.h > >> http://people.freebsd.org/~yongari/ale/if_alevar.h > >> http://people.freebsd.org/~yongari/ale/Makefile > >> or > >> http://people.freebsd.org/~yongari/ale/ale.20081030.tar.gz > >> Sorry for confusion. > > > >Tested at EeePC-1000, works fine. BIG thank you, much appreciated. > > I got an Eee PC 1000H, too, with 7.1-BETA2 and just used scp to copy > with 11.5MB/s -- much better than wlan for big files. Great! > Thanks for testing! > This will probably not go into 7.1-RELEASE, will it? It was too late to go into 7.1-RELEASE, I guess. -- Regards, Pyun YongHyeon From zbeeble at gmail.com Mon Nov 3 17:58:26 2008 From: zbeeble at gmail.com (Zaphod Beeblebrox) Date: Mon Nov 3 17:58:32 2008 Subject: ndis fix near? In-Reply-To: References: <490F47BE.9080205@janh.de> Message-ID: <5f67a8c40811031758k310b36epf088781c8fe2f1b9@mail.gmail.com> On Mon, Nov 3, 2008 at 3:55 PM, wrote: > I was quite happy with 7.0 until I found that it doesn't support 4965 AGN > card and then switched to CURRENT. > Now that ndis isn't working, I want to offer help but know very little > about wifi devices and freebsd code to contribute anything. > If someone's already working on it, it'll be great to let us know. > I thought the 4965 had it's own driver in -current. From pyunyh at gmail.com Mon Nov 3 18:07:00 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Mon Nov 3 18:07:06 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <14721476@bb.ipt.ru> References: <20081030040637.GA78796@cdnetworks.co.kr> <20081030114845.GE78796@cdnetworks.co.kr> <14721476@bb.ipt.ru> Message-ID: <20081104020456.GD98154@cdnetworks.co.kr> On Mon, Nov 03, 2008 at 08:22:51PM +0300, Boris Samorodov wrote: > Pyun YongHyeon writes: > > > As bruffer pointed out the device name chosen conflicts with other > > driver in tree so I renamed it to ale(4).The URL for the driver is > > http://people.freebsd.org/~yongari/ale/if_ale.c > > http://people.freebsd.org/~yongari/ale/if_alereg.h > > http://people.freebsd.org/~yongari/ale/if_alevar.h > > http://people.freebsd.org/~yongari/ale/Makefile > > or > > http://people.freebsd.org/~yongari/ale/ale.20081030.tar.gz > > Sorry for confusion. > > Tested at EeePC-1000, works fine. BIG thank you, much appreciated. No problem. It's my pleasure to add new hardware to the supported lists of hardwares. > Here is some additional info. > > -- dmesg -- > ale0: port 0xec80-0xecff mem 0xfbfc0000-0xfbffffff irq 17 at device 0.0 on pci4 > ale0: Reserved 0x40000 bytes for rid 0x10 type 3 at 0xfbfc0000 > ale0: PCI device revision : 0x00b0 > ale0: Chip id/revision : 0xb002 > ale0: 960 Tx FIFO, 1024 Rx FIFO > ale0: MSIX count : 0 > ale0: MSI count : 1 > ale0: attempting to allocate 1 MSI vectors (1 supported) > ale0: using IRQ 256 for MSI > ale0: Using 1 MSI messages. > ale0: Read request size : 512 bytes. > ale0: TLP payload size : 128 bytes. > ale0: bpf attached > ale0: Ethernet address: 00:22:15:91:e7:98 > ale0: [MPSAFE] > ale0: [FILTER] > ale0: link state changed to DOWN > ale0: interrupt moderation is 100 us. > ale0: link state changed to UP > -- pciconf -- > ale0@pci0:4:0:0: class=0x020000 card=0x83241043 chip=0x10261969 rev=0xb0 hdr=0x00 > vendor = 'Attansic (Now owned by Atheros)' > class = network > subclass = ethernet > -- devinfo -- > pci4 > ale0 pnpinfo vendor=0x1969 device=0x1026 subvendor=0x1043 subdevice=0x8324 class=0x020000 at slot=0 function=0 > Interrupt request lines: > 256 > I/O ports: > 0xec80-0xecff > I/O memory addresses: > 0xfbfc0000-0xfbffffff > miibus0 > atphy0 pnpinfo oui=0x1374 model=0x1 rev=0x9 at phyno=0 > ----- > I had one report that link state changing was not handled correctly for the first time boot. He said unpluging and replugging UTP cable was necessary to make it work on EeePC-1000. Did you also see the same issue? -- Regards, Pyun YongHyeon From sam at freebsd.org Mon Nov 3 18:13:28 2008 From: sam at freebsd.org (Sam Leffler) Date: Mon Nov 3 18:13:35 2008 Subject: problems with wireless using iwi drivers In-Reply-To: <200811032331.14854.nick@van-laarhoven.org> References: <200811032331.14854.nick@van-laarhoven.org> Message-ID: <490FAFC6.5010102@freebsd.org> Nick Hibma wrote: >> ------------- >> legal.intel_iwi.license_ack=1 >> if_iwi_load="YES" >> wlan_load="YES" >> firmware_load="YES" >> iwi_bss_load="YES" >> iwi_ibss_load="YES" >> iwi_monitor_load="YES" >> hw.psm.synaptics_support=1 >> -------------- >> > > I don't have any of the iwi_*_load="YES" in my kernel config and it still > has loaded the firmware alright. Loading 3 different ones looks wrong to > me. > > 100%|nick@hind:/usr/home/nick % kldstat |grep iwi > 16 1 0xc4088000 30000 iwi_bss.ko > > iwi is in the kernel, as is firmware. > > Have you installed the iwi-firmware port? I guess you have. > > RELENG_7 and HEAD include all Intel wireless firmware in the base system. Do not install ports. iwi automatically loads it's firmware as needed. The firmware is packaged in modules using firmware(9). These modules must be present in /boot/kernel or similar for it to find them. I don't believe it's been necessary to explicitly load them for a long time. man iwi(4) is out of date and needs to be updated. You need only to include the iwifw device/module when you build a kernel to get the required firmware. Sam From imp at bsdimp.com Mon Nov 3 18:56:22 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Nov 3 18:56:29 2008 Subject: TTY or SSH character echoing issue In-Reply-To: <20081103232009.GA3161@troutmask.apl.washington.edu> References: <20081103232009.GA3161@troutmask.apl.washington.edu> Message-ID: <20081103.195709.-1674606699.imp@bsdimp.com> In message: <20081103232009.GA3161@troutmask.apl.washington.edu> Steve Kargl writes: : With current source of 16 Oct 08, I'm seeing a seemly : strange echoing problem when I use ssh to connect from : one node in my cluster to another. At the (t)csh command : line prompt, I want to execute ~/trunk/cmd. So, I have : : % ~/trunk/cmd : : The strange behavior is that the ~ character does not : appear on the terminal until after I enter the / character. : : Any advice at determining whether this a tty or ssh or : some other problem would be appreciated. Are you using tip? Warner From bp at freebsd.org Mon Nov 3 19:27:29 2008 From: bp at freebsd.org (Boris Popov) Date: Mon Nov 3 19:27:36 2008 Subject: reproducible panic with mount_smbfs In-Reply-To: <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> Message-ID: <35ab6dd50811031907t2ecd2ddeq82187464a1bbf3c0@mail.gmail.com> On Sun, Nov 2, 2008 at 10:17 PM, Attilio Rao wrote: > Yuri, > could you please test this fix: > http://www.freebsd.org/~attilio/netsmb.diff This patch looks wrong to me. AFAIR, the test (LK_EXCLUSIVE && (flags & LK_CANRECURSE)) were intended to prevent situations when SMB connection can not handle multiple requests (eg, during connection setup). But I do agree, that error processing of the lock status is bogus. -- Boris Popov From tinderbox at freebsd.org Mon Nov 3 21:01:22 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Nov 3 21:01:28 2008 Subject: [head tinderbox] failure on i386/pc98 Message-ID: <20081104050118.92A6973039@freebsd-current.sentex.ca> TB --- 2008-11-04 03:43:05 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 03:43:05 - starting HEAD tinderbox run for i386/pc98 TB --- 2008-11-04 03:43:05 - cleaning the object tree TB --- 2008-11-04 03:43:40 - cvsupping the source tree TB --- 2008-11-04 03:43:40 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/i386/pc98/supfile TB --- 2008-11-04 03:43:54 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 03:43:54 - cd /src TB --- 2008-11-04 03:43:54 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 03:43:56 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Nov 4 04:56:58 UTC 2008 TB --- 2008-11-04 04:56:58 - generating LINT kernel config TB --- 2008-11-04 04:56:58 - cd /src/sys/pc98/conf TB --- 2008-11-04 04:56:58 - /usr/bin/make -B LINT TB --- 2008-11-04 04:56:58 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-04 04:56:58 - cd /src TB --- 2008-11-04 04:56:58 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Nov 4 04:56:58 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] mkdep -f .depend -a -nostdinc -DPC98 -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/pc98/src/sys/LINT usb_if.c /src/sys/modules/usb/../../dev/usb/hid.c /src/sys/modules/usb/../../dev/usb/uhub.c /src/sys/modules/usb/../../dev/usb/usb.c /src/sys/modules/usb/../../dev/usb/usb_mem.c /src/sys/modules/usb/../../dev/usb/usb_quirks.c /src/sys/modules/usb/../../dev/usb/usb_subr.c /src/sys/modules/usb/../../dev/usb/usbdi.c /src/sys/modules/usb/../../dev/usb/usbdi_util.c /src/sys/modules/usb/../../dev/usb/usb_ethersubr.c ===> usb2 (depend) ===> usb2/bluetooth (depend) @ -> /src/sys machine -> /src/sys/pc98/include i386 -> /src/sys/i386/include awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h make: don't know how to make usb2_if.h. Stop *** Error code 2 Stop in /src/sys/modules/usb2. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 05:01:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 05:01:18 - ERROR: failed to build lint kernel TB --- 2008-11-04 05:01:18 - tinderbox aborted TB --- 3227.59 user 414.06 system 4692.88 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-pc98.full From tinderbox at freebsd.org Mon Nov 3 22:30:01 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Mon Nov 3 22:30:09 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081104062958.B861D73039@freebsd-current.sentex.ca> TB --- 2008-11-04 05:01:18 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 05:01:18 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-11-04 05:01:18 - cleaning the object tree TB --- 2008-11-04 05:01:53 - cvsupping the source tree TB --- 2008-11-04 05:01:53 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-11-04 05:02:00 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 05:02:00 - cd /src TB --- 2008-11-04 05:02:00 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 05:02:03 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Nov 4 06:14:47 UTC 2008 TB --- 2008-11-04 06:14:47 - generating LINT kernel config TB --- 2008-11-04 06:14:47 - cd /src/sys/powerpc/conf TB --- 2008-11-04 06:14:47 - /usr/bin/make -B LINT TB --- 2008-11-04 06:14:47 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-04 06:14:47 - cd /src TB --- 2008-11-04 06:14:47 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Nov 4 06:14:47 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] awk -f /src/sys/modules/usb2/wlan_rum/../../../conf/kmod_syms.awk usb2_wlan_rum.kld export_syms | xargs -J% objcopy % usb2_wlan_rum.kld ld -Bshareable -d -warn-common -o usb2_wlan_rum.ko usb2_wlan_rum.kld objcopy --strip-debug usb2_wlan_rum.ko ===> usb2/wlan_zyd (all) cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/powerpc/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mlongcall -fno-omit-frame-pointer -I/obj/powerpc/src/sys/LINT -msoft-float -ffreestanding -fstack-protector -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c: In function 'zyd_intr_read_callback': /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c:396: error: case label does not reduce to an integer constant /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c:398: error: case label does not reduce to an integer constant *** Error code 1 Stop in /src/sys/modules/usb2/wlan_zyd. *** Error code 1 Stop in /src/sys/modules/usb2. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 06:29:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 06:29:58 - ERROR: failed to build lint kernel TB --- 2008-11-04 06:29:58 - tinderbox aborted TB --- 3812.61 user 440.16 system 5319.77 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From onemda at gmail.com Tue Nov 4 04:51:20 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Tue Nov 4 04:51:26 2008 Subject: ndis fix near? In-Reply-To: References: <490F47BE.9080205@janh.de> Message-ID: <3a142e750811040451r3ade52c5r869cebc18f71428f@mail.gmail.com> On 11/3/08, rohit.x.tripathi@jpmchase.com wrote: > I was quite happy with 7.0 until I found that it doesn't support 4965 AGN > card and then switched to CURRENT. > Now that ndis isn't working, I want to offer help but know very little > about wifi devices and freebsd code to contribute anything. > If someone's already working on it, it'll be great to let us know. > That type of card should work with iwn(4) driver, ndis on CURRENT should get fixed soon. From tinderbox at freebsd.org Tue Nov 4 06:06:20 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 06:06:27 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081104140614.DD22F73039@freebsd-current.sentex.ca> TB --- 2008-11-04 12:36:21 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 12:36:21 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-11-04 12:36:21 - cleaning the object tree TB --- 2008-11-04 12:36:48 - cvsupping the source tree TB --- 2008-11-04 12:36:48 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-11-04 12:36:54 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 12:36:54 - cd /src TB --- 2008-11-04 12:36:54 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 12:36:55 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Nov 4 13:51:28 UTC 2008 TB --- 2008-11-04 13:51:28 - generating LINT kernel config TB --- 2008-11-04 13:51:28 - cd /src/sys/powerpc/conf TB --- 2008-11-04 13:51:28 - /usr/bin/make -B LINT TB --- 2008-11-04 13:51:28 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-04 13:51:28 - cd /src TB --- 2008-11-04 13:51:28 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Nov 4 13:51:29 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] awk -f /src/sys/modules/usb2/wlan_rum/../../../conf/kmod_syms.awk usb2_wlan_rum.kld export_syms | xargs -J% objcopy % usb2_wlan_rum.kld ld -Bshareable -d -warn-common -o usb2_wlan_rum.ko usb2_wlan_rum.kld objcopy --strip-debug usb2_wlan_rum.ko ===> usb2/wlan_zyd (all) cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/powerpc/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mlongcall -fno-omit-frame-pointer -I/obj/powerpc/src/sys/LINT -msoft-float -ffreestanding -fstack-protector -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c: In function 'zyd_intr_read_callback': /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c:396: error: case label does not reduce to an integer constant /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c:398: error: case label does not reduce to an integer constant *** Error code 1 Stop in /src/sys/modules/usb2/wlan_zyd. *** Error code 1 Stop in /src/sys/modules/usb2. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 14:06:14 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 14:06:14 - ERROR: failed to build lint kernel TB --- 2008-11-04 14:06:14 - tinderbox aborted TB --- 3815.56 user 441.05 system 5392.95 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Nov 4 08:03:43 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 08:04:02 2008 Subject: [head tinderbox] failure on arm/arm Message-ID: <20081104160337.5650373039@freebsd-current.sentex.ca> TB --- 2008-11-04 15:40:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 15:40:01 - starting HEAD tinderbox run for arm/arm TB --- 2008-11-04 15:40:01 - cleaning the object tree TB --- 2008-11-04 15:40:32 - cvsupping the source tree TB --- 2008-11-04 15:40:32 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/arm/arm/supfile TB --- 2008-11-04 15:40:40 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 15:40:40 - cd /src TB --- 2008-11-04 15:40:40 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 15:40:42 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 16:03:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 16:03:37 - ERROR: failed to build world TB --- 2008-11-04 16:03:37 - tinderbox aborted TB --- 974.42 user 136.70 system 1416.09 real http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full From rbgarga at gmail.com Tue Nov 4 08:11:11 2008 From: rbgarga at gmail.com (Renato Botelho) Date: Tue Nov 4 08:11:18 2008 Subject: -CURRENT rev. 184639: i386 kernel doesn't build Message-ID: <747dc8f30811040744y62587d5cn538cdc6eef3af161@mail.gmail.com> After up my svn repo to 184639, kernel stops building with this error: ===> nfsclient (all) ===> nfslockd (all) ===> nfsserver (all) cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror /usr/src/sys/kern/vfs_cache.c cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/GARGA/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/usr/obj/usr/src/sys/GARGA -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:101: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'nfsrv_nmbclusters_tag' cc1: warnings being treated as errors /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c: In function 'nfsrv_init': /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:545: warning: implicit declaration of function 'EVENTHANDLER_DEREGISTER' /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:545: warning: nested extern declaration of 'EVENTHANDLER_DEREGISTER' /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:545: error: 'nmbclusters_change' undeclared (first use in this function) /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:545: error: (Each undeclared identifier is reported only once /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:545: error: for each function it appears in.) /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:546: error: 'nfsrv_nmbclusters_tag' undeclared (first use in this function) /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:559: warning: implicit declaration of function 'EVENTHANDLER_REGISTER' /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:559: warning: nested extern declaration of 'EVENTHANDLER_REGISTER' /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvkrpc.c:560: error: 'EVENTHANDLER_PRI_FIRST' undeclared (first use in this function) *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error [1] 53070 exit 2 make -j2 buildkernel -- Renato Botelho From bsam at ipt.ru Tue Nov 4 08:16:35 2008 From: bsam at ipt.ru (Boris Samorodov) Date: Tue Nov 4 08:16:43 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <20081104020456.GD98154@cdnetworks.co.kr> (Pyun YongHyeon's message of "Tue\, 4 Nov 2008 11\:04\:56 +0900") References: <20081030040637.GA78796@cdnetworks.co.kr> <20081030114845.GE78796@cdnetworks.co.kr> <14721476@bb.ipt.ru> <20081104020456.GD98154@cdnetworks.co.kr> Message-ID: <91518878@bs1.sp34.ru> Pyun YongHyeon writes: > I had one report that link state changing was not handled correctly > for the first time boot. He said unpluging and replugging UTP cable > was necessary to make it work on EeePC-1000. Did you also see the > same issue? No. In my case all is OK. Tested with two switches (3COM/1G at work and 3COM/100M at home). Both loading from /etc/loader.conf and manually kldloading autodetecting works just fine ending with 100 Mbit/s full-duplex. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From dfr at rabson.org Tue Nov 4 08:43:41 2008 From: dfr at rabson.org (Doug Rabson) Date: Tue Nov 4 08:43:48 2008 Subject: -CURRENT rev. 184639: i386 kernel doesn't build In-Reply-To: <747dc8f30811040744y62587d5cn538cdc6eef3af161@mail.gmail.com> References: <747dc8f30811040744y62587d5cn538cdc6eef3af161@mail.gmail.com> Message-ID: On 4 Nov 2008, at 15:44, Renato Botelho wrote: > After up my svn repo to 184639, kernel stops building with this error: Try again with r184643. From tinderbox at freebsd.org Tue Nov 4 10:31:08 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 10:31:25 2008 Subject: [head tinderbox] failure on ia64/ia64 Message-ID: <20081104183104.8DA3A73039@freebsd-current.sentex.ca> TB --- 2008-11-04 18:05:23 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 18:05:23 - starting HEAD tinderbox run for ia64/ia64 TB --- 2008-11-04 18:05:23 - cleaning the object tree TB --- 2008-11-04 18:06:05 - cvsupping the source tree TB --- 2008-11-04 18:06:05 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/ia64/ia64/supfile TB --- 2008-11-04 18:06:14 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 18:06:14 - cd /src TB --- 2008-11-04 18:06:14 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 18:06:16 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 18:31:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 18:31:04 - ERROR: failed to build world TB --- 2008-11-04 18:31:04 - tinderbox aborted TB --- 1075.59 user 135.95 system 1541.27 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From rbgarga at gmail.com Tue Nov 4 11:25:00 2008 From: rbgarga at gmail.com (Renato Botelho) Date: Tue Nov 4 11:25:07 2008 Subject: -CURRENT rev. 184639: i386 kernel doesn't build In-Reply-To: References: <747dc8f30811040744y62587d5cn538cdc6eef3af161@mail.gmail.com> Message-ID: <747dc8f30811041125t7a6caa48q3206d13454b0d1a@mail.gmail.com> On Tue, Nov 4, 2008 at 2:43 PM, Doug Rabson wrote: > > On 4 Nov 2008, at 15:44, Renato Botelho wrote: > >> After up my svn repo to 184639, kernel stops building with this error: > > Try again with r184643. Fixed. Thanks! -- Renato Botelho From tinderbox at freebsd.org Tue Nov 4 11:59:37 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 11:59:55 2008 Subject: [head tinderbox] failure on powerpc/powerpc Message-ID: <20081104195935.588CB73039@freebsd-current.sentex.ca> TB --- 2008-11-04 18:31:04 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 18:31:04 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-11-04 18:31:04 - cleaning the object tree TB --- 2008-11-04 18:31:29 - cvsupping the source tree TB --- 2008-11-04 18:31:29 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-11-04 18:31:37 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 18:31:37 - cd /src TB --- 2008-11-04 18:31:37 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 18:31:38 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Nov 4 19:44:24 UTC 2008 TB --- 2008-11-04 19:44:24 - generating LINT kernel config TB --- 2008-11-04 19:44:24 - cd /src/sys/powerpc/conf TB --- 2008-11-04 19:44:24 - /usr/bin/make -B LINT TB --- 2008-11-04 19:44:24 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-04 19:44:24 - cd /src TB --- 2008-11-04 19:44:24 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Nov 4 19:44:24 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] awk -f /src/sys/modules/usb2/wlan_rum/../../../conf/kmod_syms.awk usb2_wlan_rum.kld export_syms | xargs -J% objcopy % usb2_wlan_rum.kld ld -Bshareable -d -warn-common -o usb2_wlan_rum.ko usb2_wlan_rum.kld objcopy --strip-debug usb2_wlan_rum.ko ===> usb2/wlan_zyd (all) cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/powerpc/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mlongcall -fno-omit-frame-pointer -I/obj/powerpc/src/sys/LINT -msoft-float -ffreestanding -fstack-protector -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c: In function 'zyd_intr_read_callback': /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c:396: error: case label does not reduce to an integer constant /src/sys/modules/usb2/wlan_zyd/../../../dev/usb2/wlan/if_zyd2.c:398: error: case label does not reduce to an integer constant *** Error code 1 Stop in /src/sys/modules/usb2/wlan_zyd. *** Error code 1 Stop in /src/sys/modules/usb2. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 19:59:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 19:59:35 - ERROR: failed to build lint kernel TB --- 2008-11-04 19:59:35 - tinderbox aborted TB --- 3815.37 user 439.14 system 5310.50 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From tinderbox at freebsd.org Tue Nov 4 12:14:44 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 12:14:57 2008 Subject: [head tinderbox] failure on sparc64/sparc64 Message-ID: <20081104201440.EF5B573039@freebsd-current.sentex.ca> TB --- 2008-11-04 19:51:50 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 19:51:50 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-11-04 19:51:50 - cleaning the object tree TB --- 2008-11-04 19:52:24 - cvsupping the source tree TB --- 2008-11-04 19:52:24 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-04 19:52:31 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 19:52:31 - cd /src TB --- 2008-11-04 19:52:31 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 19:52:34 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 20:14:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 20:14:40 - ERROR: failed to build world TB --- 2008-11-04 20:14:40 - tinderbox aborted TB --- 937.29 user 133.59 system 1370.37 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From tinderbox at freebsd.org Tue Nov 4 12:21:05 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 12:21:12 2008 Subject: [head tinderbox] failure on sparc64/sun4v Message-ID: <20081104202102.F1FEC73039@freebsd-current.sentex.ca> TB --- 2008-11-04 19:59:35 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 19:59:35 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-11-04 19:59:35 - cleaning the object tree TB --- 2008-11-04 20:00:00 - cvsupping the source tree TB --- 2008-11-04 20:00:00 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-11-04 20:00:06 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 20:00:06 - cd /src TB --- 2008-11-04 20:00:06 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 20:00:08 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 20:21:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 20:21:02 - ERROR: failed to build world TB --- 2008-11-04 20:21:02 - tinderbox aborted TB --- 936.58 user 130.71 system 1287.57 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From tinderbox at freebsd.org Tue Nov 4 13:03:23 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 13:03:41 2008 Subject: [head tinderbox] failure on arm/arm Message-ID: <20081104210320.9B06573039@freebsd-current.sentex.ca> TB --- 2008-11-04 20:40:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 20:40:00 - starting HEAD tinderbox run for arm/arm TB --- 2008-11-04 20:40:00 - cleaning the object tree TB --- 2008-11-04 20:40:20 - cvsupping the source tree TB --- 2008-11-04 20:40:20 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/arm/arm/supfile TB --- 2008-11-04 20:40:29 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 20:40:29 - cd /src TB --- 2008-11-04 20:40:29 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 20:40:30 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 21:03:20 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 21:03:20 - ERROR: failed to build world TB --- 2008-11-04 21:03:20 - tinderbox aborted TB --- 973.32 user 137.12 system 1400.28 real http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full From lme at FreeBSD.org Tue Nov 4 13:22:56 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Nov 4 13:23:03 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200810311716.10165.Thomas.Sparrevohn@btinternet.com> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> Message-ID: <20081104212254.GB8256@e.0x20.net> On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: > On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: > > On Friday 31 October 2008, Olivier SMEDTS wrote: > > > Hello, > > > > > > Each device driver has been splitted since RC3. > > > Look in /boot/kernel/usb2_*. You can use modules. > > > For example, for my usb mouse, I use usb2_input_ums. > > > > Hi, > > > > Looks like I made a small typo there. The module is named "usb2_input_ms" > > while the kernel option is named "usb2_input_ums". The kernel option should > > be named "usb2_input_ms". > > > > Is this the same issue? > > config: Error: device "usb2_controller_uss820dci" is unknown > config: Error: device "usb2_ethernet_dav" is unknown > device usb2_ethernet_dav is still unknown in the commit version in HEAD. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081104/b82da649/attachment.pgp From lme at FreeBSD.org Tue Nov 4 13:22:56 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Nov 4 13:23:14 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200810311716.10165.Thomas.Sparrevohn@btinternet.com> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> Message-ID: <20081104212254.GB8256@e.0x20.net> On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: > On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: > > On Friday 31 October 2008, Olivier SMEDTS wrote: > > > Hello, > > > > > > Each device driver has been splitted since RC3. > > > Look in /boot/kernel/usb2_*. You can use modules. > > > For example, for my usb mouse, I use usb2_input_ums. > > > > Hi, > > > > Looks like I made a small typo there. The module is named "usb2_input_ms" > > while the kernel option is named "usb2_input_ums". The kernel option should > > be named "usb2_input_ms". > > > > Is this the same issue? > > config: Error: device "usb2_controller_uss820dci" is unknown > config: Error: device "usb2_ethernet_dav" is unknown > device usb2_ethernet_dav is still unknown in the commit version in HEAD. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081104/b82da649/attachment-0001.pgp From me at janh.de Tue Nov 4 13:37:37 2008 From: me at janh.de (Jan Henrik Sylvester) Date: Tue Nov 4 13:46:20 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <20081104015235.GC98154@cdnetworks.co.kr> References: <490F47BE.9080205@janh.de> <20081104015235.GC98154@cdnetworks.co.kr> Message-ID: <4910C055.8000505@janh.de> Pyun YongHyeon wrote: > On Mon, Nov 03, 2008 at 07:49:34PM +0100, Jan Henrik Sylvester wrote: > > >Pyun YongHyeon writes: > > >> http://people.freebsd.org/~yongari/ale/if_ale.c > > > > I got an Eee PC 1000H, too, with 7.1-BETA2 and just used scp to copy > > with 11.5MB/s -- much better than wlan for big files. Great! > > > > Thanks for testing! I was happy too early. Now I keep getting these: ale0: DMA read error! -- resetting ale0: could not disable Tx/Rx MAC(0x00000008)! ale0: interrupt moderation is 100 us. The speed of copying a file has dropped to <50kB/s. Stopping and restarting the interface does not help, even if I kldunload the driver in the meantime. I have yet to reboot the machine. I do not know what is different, though. I left the computer alone for an hour before using the network... > > This will probably not go into 7.1-RELEASE, will it? > > It was too late to go into 7.1-RELEASE, I guess. It seems to be too early, anyhow. Do you want me to try anything specific? (I hope it does not involve recompiling the kernel on this slow Eee PC.) Cheers, Jan Henrik From jille at quis.cx Tue Nov 4 13:56:27 2008 From: jille at quis.cx (Jille Timmermans) Date: Tue Nov 4 13:56:34 2008 Subject: device snp build broken? In-Reply-To: <4910C0DF.2040501@lissyara.su> References: <20081101061930.GA34365@regency.nsu.ru> <490C7625.6060608@quis.cx> <4910C0DF.2040501@lissyara.su> Message-ID: <4910C505.9070809@quis.cx> Alex Keda schreef: > Jille Timmermans ?????: >> Hello, >> >> snp(4) in -CURRENT is currently not supported. >> Ed made a patch for it; which worked for me. >> You can get the latest version from: >> >> http://people.freebsd.org/~ed/mpsafetty/ >> >> (The patch-set also includes other things; like a new /dev/console) > > What was the reason not to support the device? Ed rewrote the TTY system and left out snp(4): * He didn't thought anyone was really needing it * Because it reads from a TTY, and writes to another TTY; it would have caused problems with blocking (full queues, etc) After a while he got convinced to fix snp(4). It is now experimental, so only available through his patchset. But it will make it into HEAD before 8.0. Ed: Please correct me if I'm wrong somewhere -- Jille > >> >> -- Jille >> >> Alexey Dokuchaev schreef: >>> Hi there, >>> >>> Looks like device snp is broken on recent -CURRENT. Is it being >>> supported at all? How useful it is in modern environment? >>> >>> Thanks. Relevant part of build log attached. >>> >>> ./danfe >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" > From rbgarga at gmail.com Tue Nov 4 13:56:48 2008 From: rbgarga at gmail.com (Renato Botelho) Date: Tue Nov 4 13:56:54 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104212254.GB8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> Message-ID: <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> On Tue, Nov 4, 2008 at 7:22 PM, Lars Engels wrote: > On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: >> On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: >> > On Friday 31 October 2008, Olivier SMEDTS wrote: >> > > Hello, >> > > >> > > Each device driver has been splitted since RC3. >> > > Look in /boot/kernel/usb2_*. You can use modules. >> > > For example, for my usb mouse, I use usb2_input_ums. >> > >> > Hi, >> > >> > Looks like I made a small typo there. The module is named "usb2_input_ms" >> > while the kernel option is named "usb2_input_ums". The kernel option should >> > be named "usb2_input_ms". >> > >> >> Is this the same issue? >> >> config: Error: device "usb2_controller_uss820dci" is unknown >> config: Error: device "usb2_ethernet_dav" is unknown >> > > device usb2_ethernet_dav is still unknown in the commit version in HEAD. I believe it was just a typo, the correct is usb2_ethernet_udav -- Renato Botelho From vova at fbsd.ru Tue Nov 4 14:05:02 2008 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Tue Nov 4 14:05:09 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200810092344.10388.nick@van-laarhoven.org> References: <200810092344.10388.nick@van-laarhoven.org> Message-ID: <1225836292.3428.37.camel@localhost> On Thu, 2008-10-09 at 23:44 +0200, Nick Hibma wrote: > Just now I have committed a driver for Option and Huawei cards previously > supported by the ubsa driver. More information is in the commit message. > > I am looking for people who would be able to provide more information after > testing with the 3G cards branded by: > > OEM: > Merlin > Huawei > Option > Sierra > Novatel > Qualcomm > > Rebranded: > Dell > Vodafone > > Note: The driver can be copied across to FreeBSD 7-STABLE if you copy the > sys/modules/u3g directory and sys/dev/usb/u3g.c and sys/dev/usb/usbdevs > files from HEAD and _move_ the ID from ubsa to u3g. > > More information can be found on > > http://people.freebsd.org/~n_hibma/u3g.html Ehh, I have Huawei card, and it works ok before with ubsa driver: Controller /dev/usb5: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), NEC(0x0000), rev 1.00 port 1 addr 2: full speed, power 500 mA, config 1, Huawei Mobile(0x1001), Huawei Technologies(0x12d1), rev 0.00 ucom0: on uhub5 ucom0: configured 3 serial ports (U0.%d) Now (5-days old current), everything looks fine, chat finishes, but ppp failed to handshake (same ppp config works before with ubsa): Nov 5 00:57:35 vbook ppp[4644]: tun0: Phase: PPP Started (background mode). Nov 5 00:57:35 vbook ppp[4644]: tun0: Phase: bundle: Establish Nov 5 00:57:35 vbook ppp[4644]: tun0: Phase: deflink: closed -> opening Nov 5 00:57:35 vbook ppp[4644]: tun0: Phase: deflink: Connected! Nov 5 00:57:35 vbook ppp[4644]: tun0: Phase: deflink: opening -> dial Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Phone: #777 Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: deflink: Dial attempt 1 of 1 Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Send: AT^M Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Expect(15): OK Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Received: ^M Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Received: OK^M Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Send: ATE1Q0^M Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Expect(15): OK Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Received: Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Received: OK^M Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Send: ATDT#777^M Nov 5 00:57:37 vbook ppp[4644]: tun0: Chat: Expect(40): CONNECT Nov 5 00:57:37 vbook ppp[4644]: tun0: Chat: Received: ^M Nov 5 00:57:37 vbook ppp[4644]: tun0: Chat: Received: CONNECT^M Nov 5 00:57:37 vbook ppp[4644]: tun0: Phase: deflink: dial -> carrier Nov 5 00:57:38 vbook ppp[4644]: tun0: Phase: deflink: /dev/ttyU0.0 doesn't support CD Nov 5 00:57:38 vbook ppp[4644]: tun0: Phase: deflink: carrier -> login Nov 5 00:57:38 vbook ppp[4644]: tun0: Phase: deflink: login -> lcp Nov 5 00:57:38 vbook ppp[4644]: tun0: LCP: FSM: Using "deflink" as a transport Nov 5 00:57:38 vbook ppp[4644]: tun0: LCP: deflink: State change Initial --> Closed Nov 5 00:57:38 vbook ppp[4644]: tun0: LCP: deflink: State change Closed --> Stopped Nov 5 00:57:39 vbook ppp[4644]: tun0: LCP: deflink: LayerStart Nov 5 00:57:39 vbook ppp[4644]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Nov 5 00:57:39 vbook ppp[4644]: tun0: LCP: ACCMAP[6] 0x00000000 Nov 5 00:57:39 vbook ppp[4644]: tun0: LCP: MRU[4] 1500 Nov 5 00:57:39 vbook ppp[4644]: tun0: LCP: MAGICNUM[6] 0xb88169a8 Nov 5 00:57:39 vbook ppp[4644]: tun0: LCP: QUALPROTO[8] proto c025, interval 10000ms Nov 5 00:57:39 vbook ppp[4644]: tun0: LCP: deflink: State change Stopped --> Req-Sent Nov 5 00:57:40 vbook ppp[4644]: tun0: LCP: deflink: RecvConfigAck(1) state = Req-Sent Nov 5 00:57:40 vbook ppp[4644]: tun0: LCP: ACCMAP[6] 0x00000000 Nov 5 00:57:40 vbook ppp[4644]: tun0: LCP: MRU[4] 1500 Nov 5 00:57:40 vbook ppp[4644]: tun0: LCP: MAGICNUM[6] 0xb88169a8 Nov 5 00:57:40 vbook ppp[4644]: tun0: LCP: QUALPROTO[8] proto c025, interval 10000ms Nov 5 00:57:40 vbook ppp[4644]: tun0: LCP: deflink: State change Req-Sent --> Ack-Rcvd Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: deflink: RecvConfigReq(3) state = Ack-Rcvd Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: ACCMAP[6] 0x00000000 Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: MAGICNUM[6] 0x2e7ad2d8 Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: deflink: SendConfigAck(3) state = Ack-Rcvd Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: ACCMAP[6] 0x00000000 Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: MAGICNUM[6] 0x2e7ad2d8 Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: deflink: State change Ack-Rcvd --> Opened Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: deflink: LayerUp Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: deflink: SendIdent(0) state = Opened Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: MAGICNUM b88169a8 Nov 5 00:57:42 vbook ppp[4644]: tun0: LCP: TEXT user-ppp 3.4.2 (built COMPILATIONDATE) Nov 5 00:57:42 vbook ppp[4644]: tun0: Phase: bundle: Authenticate Nov 5 00:57:42 vbook ppp[4644]: tun0: Phase: deflink: his = CHAP 0x05, mine = none Nov 5 00:57:52 vbook ppp[4644]: tun0: Phase: Chap Input: CHALLENGE (16 bytes from pdsn-m22-7cm2) Nov 5 00:57:52 vbook ppp[4644]: tun0: Phase: Chap Output: RESPONSE (mobile) Nov 5 00:57:53 vbook ppp[4644]: tun0: LCP: deflink: RecvEchoRequest(1) state = Opened Nov 5 00:57:53 vbook ppp[4644]: tun0: LCP: deflink: SendEchoReply(1) state = Opened Nov 5 00:57:53 vbook ppp[4644]: tun0: CCP: deflink: Error: Unexpected CCP in phase Authenticate (ignored) Nov 5 00:58:03 vbook last message repeated 3 times Nov 5 00:58:07 vbook ppp[4644]: tun0: IPCP: deflink: Error: Unexpected IPCP in phase Authenticate (ignored) Nov 5 00:58:07 vbook ppp[4644]: tun0: CCP: deflink: Error: Unexpected CCP in phase Authenticate (ignored) Nov 5 00:58:11 vbook ppp[4644]: tun0: CCP: deflink: Error: Unexpected CCP in phase Authenticate (ignored) Nov 5 00:58:42 vbook ppp[4644]: tun0: Phase: deflink: HDLC errors -> FCS: 26, ADDR: 0, COMD: 0, PROTO: 0 Nov 5 00:58:52 vbook ppp[4644]: tun0: Phase: deflink: ** Too many LQR packets lost ** Nov 5 00:58:52 vbook ppp[4644]: tun0: LCP: deflink: LayerDown Nov 5 00:58:52 vbook ppp[4644]: tun0: LCP: deflink: State change Opened --> Starting Nov 5 00:58:52 vbook ppp[4644]: tun0: LCP: deflink: LayerFinish Nov 5 00:58:52 vbook ppp[4644]: tun0: LCP: deflink: State change Starting --> Initial Nov 5 00:58:52 vbook ppp[4644]: tun0: Phase: deflink: Disconnected! It looks like that characters are delivered not reliable way through ucom port: Same on U0.2 port: Below output, just after entring AT\n three times: # cu -l /dev/cuaU0.2 can't open log file /var/log/aculog. Connected ^RSSILVL: 20 8 OK It OK I ^RSSILVL: 20 8em0X?6T OK I -------------------- Any hints will be very appriciated. > Thanks, > > Nick P.S. I have also two other problems with same card, (they was with ubsa also): - after disconnecting ppp from port card is not reset, so no more any chat if start ppp again (you just need skip chat phase). - How to reset card before start ? - Disconnecting card crashes kernel, it is possible to catch that crash with DDB, but dump can't be written. Modem is on cardbus device. (probbaly will be fixed by new usb stack ?) -- Vladimir B. Grebenschikov vova@fbsd.ru From lme at FreeBSD.org Tue Nov 4 14:07:27 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Nov 4 14:07:42 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> Message-ID: <20081104220725.GC8256@e.0x20.net> On Tue, Nov 04, 2008 at 07:56:47PM -0200, Renato Botelho wrote: > On Tue, Nov 4, 2008 at 7:22 PM, Lars Engels wrote: > > On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: > >> On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: > >> > On Friday 31 October 2008, Olivier SMEDTS wrote: > >> > > Hello, > >> > > > >> > > Each device driver has been splitted since RC3. > >> > > Look in /boot/kernel/usb2_*. You can use modules. > >> > > For example, for my usb mouse, I use usb2_input_ums. > >> > > >> > Hi, > >> > > >> > Looks like I made a small typo there. The module is named "usb2_input_ms" > >> > while the kernel option is named "usb2_input_ums". The kernel option should > >> > be named "usb2_input_ms". > >> > > >> > >> Is this the same issue? > >> > >> config: Error: device "usb2_controller_uss820dci" is unknown > >> config: Error: device "usb2_ethernet_dav" is unknown > >> > > > > device usb2_ethernet_dav is still unknown in the commit version in HEAD. > > I believe it was just a typo, the correct is usb2_ethernet_udav Good point. :) After changing it to _udav I am getting this: In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, from /usr/src/sys/dev/usb2/sound/uaudio2.c:79: /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No such file or directory /usr/src/sys/dev/usb2/sound/uaudio2.c:81:23: error: feeder_if.h: No such file or directory In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, from /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:31: /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No such file or directory /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:36:22: error: mixer_if.h: No such file or directory mkdep: compile failed -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081104/3fb57a47/attachment.pgp From lme at FreeBSD.org Tue Nov 4 14:07:27 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Nov 4 14:07:52 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> Message-ID: <20081104220725.GC8256@e.0x20.net> On Tue, Nov 04, 2008 at 07:56:47PM -0200, Renato Botelho wrote: > On Tue, Nov 4, 2008 at 7:22 PM, Lars Engels wrote: > > On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: > >> On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: > >> > On Friday 31 October 2008, Olivier SMEDTS wrote: > >> > > Hello, > >> > > > >> > > Each device driver has been splitted since RC3. > >> > > Look in /boot/kernel/usb2_*. You can use modules. > >> > > For example, for my usb mouse, I use usb2_input_ums. > >> > > >> > Hi, > >> > > >> > Looks like I made a small typo there. The module is named "usb2_input_ms" > >> > while the kernel option is named "usb2_input_ums". The kernel option should > >> > be named "usb2_input_ms". > >> > > >> > >> Is this the same issue? > >> > >> config: Error: device "usb2_controller_uss820dci" is unknown > >> config: Error: device "usb2_ethernet_dav" is unknown > >> > > > > device usb2_ethernet_dav is still unknown in the commit version in HEAD. > > I believe it was just a typo, the correct is usb2_ethernet_udav Good point. :) After changing it to _udav I am getting this: In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, from /usr/src/sys/dev/usb2/sound/uaudio2.c:79: /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No such file or directory /usr/src/sys/dev/usb2/sound/uaudio2.c:81:23: error: feeder_if.h: No such file or directory In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, from /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:31: /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No such file or directory /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:36:22: error: mixer_if.h: No such file or directory mkdep: compile failed -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081104/3fb57a47/attachment-0001.pgp From admin at lissyara.su Tue Nov 4 14:22:27 2008 From: admin at lissyara.su (Alex Keda) Date: Tue Nov 4 14:22:34 2008 Subject: device snp build broken? In-Reply-To: <490C7625.6060608@quis.cx> References: <20081101061930.GA34365@regency.nsu.ru> <490C7625.6060608@quis.cx> Message-ID: <4910C0DF.2040501@lissyara.su> Jille Timmermans ?????: > Hello, > > snp(4) in -CURRENT is currently not supported. > Ed made a patch for it; which worked for me. > You can get the latest version from: > > http://people.freebsd.org/~ed/mpsafetty/ > > (The patch-set also includes other things; like a new /dev/console) What was the reason not to support the device? > > -- Jille > > Alexey Dokuchaev schreef: >> Hi there, >> >> Looks like device snp is broken on recent -CURRENT. Is it being >> supported at all? How useful it is in modern environment? >> >> Thanks. Relevant part of build log attached. >> >> ./danfe >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From rbgarga at gmail.com Tue Nov 4 14:22:35 2008 From: rbgarga at gmail.com (Renato Botelho) Date: Tue Nov 4 14:22:41 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104212254.GB8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> Message-ID: <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> On Tue, Nov 4, 2008 at 7:22 PM, Lars Engels wrote: > On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: >> On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: >> > On Friday 31 October 2008, Olivier SMEDTS wrote: >> > > Hello, >> > > >> > > Each device driver has been splitted since RC3. >> > > Look in /boot/kernel/usb2_*. You can use modules. >> > > For example, for my usb mouse, I use usb2_input_ums. >> > >> > Hi, >> > >> > Looks like I made a small typo there. The module is named "usb2_input_ms" >> > while the kernel option is named "usb2_input_ums". The kernel option should >> > be named "usb2_input_ms". >> > >> >> Is this the same issue? >> >> config: Error: device "usb2_controller_uss820dci" is unknown >> config: Error: device "usb2_ethernet_dav" is unknown >> > > device usb2_ethernet_dav is still unknown in the commit version in HEAD. I believe it was just a typo, the correct is usb2_ethernet_udav -- Renato Botelho From ed at 80386.nl Tue Nov 4 14:24:36 2008 From: ed at 80386.nl (Ed Schouten) Date: Tue Nov 4 14:24:43 2008 Subject: device snp build broken? In-Reply-To: <4910C505.9070809@quis.cx> References: <20081101061930.GA34365@regency.nsu.ru> <490C7625.6060608@quis.cx> <4910C0DF.2040501@lissyara.su> <4910C505.9070809@quis.cx> Message-ID: <20081104222434.GZ1165@hoeg.nl> Hello Jille, Alex, Alexey, * Jille Timmermans wrote: > Alex Keda schreef: > > Jille Timmermans ?????: > >> Hello, > >> > >> snp(4) in -CURRENT is currently not supported. > >> Ed made a patch for it; which worked for me. > >> You can get the latest version from: > >> > >> http://people.freebsd.org/~ed/mpsafetty/ > >> > >> (The patch-set also includes other things; like a new /dev/console) > > > > What was the reason not to support the device? > Ed rewrote the TTY system and left out snp(4): > * He didn't thought anyone was really needing it > * Because it reads from a TTY, and writes to another TTY; it would have > caused problems with blocking (full queues, etc) > > After a while he got convinced to fix snp(4). > It is now experimental, so only available through his patchset. > > But it will make it into HEAD before 8.0. > > Ed: Please correct me if I'm wrong somewhere The main problem with snp(4) was that its design didn't really fit into the model of the new TTY layer that I imported back in August. The reason the new snp(4) isn't available in SVN yet, is because it isn't finished. It doesn't return the traditional snp(4) status codes and doesn't allow descriptors to /dev/snp to switch to a different TTY after being used. I really want to fix at least the first issue, but so far I haven't found {time,interest,etc}. The new snp(4) code is already pretty sweet - it works a lot better than the old driver. Maybe someone else is interested in fixing it? -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081104/e1cc432a/attachment.pgp From nick at van-laarhoven.org Tue Nov 4 14:25:38 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Tue Nov 4 14:25:49 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <1225836292.3428.37.camel@localhost> References: <200810092344.10388.nick@van-laarhoven.org> <1225836292.3428.37.camel@localhost> Message-ID: <200811042325.26574.nick@van-laarhoven.org> > Now (5-days old current), everything looks fine, chat finishes, but ppp > failed to handshake (same ppp config works before with ubsa): > > Nov 5 00:57:35 vbook ppp[4644]: tun0: Phase: PPP Started (background > mode). Nov 5 00:57:35 vbook ppp[4644]: tun0: Phase: bundle: Establish > Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Send: ATDT#777^M Are you sure this phone number is correct? I'd have to check the 3GPP spec, but something like ATDT*99***1# is more like the Huawei expects. The general format is *****#. If you have set multiple PDP contexts through AT+CGDCONT you can select the one you need by replacing the '1' in the line above with the appropriate number. The 'Unexpected * in phase *' I've not seen before and would indicate that a valid packet is received but one that is not appropriate at that point. You might want to add some more logging options to see what is going on. > It looks like that characters are delivered not reliable way through ucom > port: Same on U0.2 port: Weird. Should not happen. > - after disconnecting ppp from port card is not reset, so no more any > chat if start ppp again (you just need skip chat phase). - How to reset > card before start ? We've had this problem with an EDGE card from Option, and we basically power down the port and power up again the card to get it back. Patches have been sent to Warner to get committed. > - Disconnecting card crashes kernel, it is possible to catch that crash > with DDB, but dump can't be written. Modem is on cardbus device. > (probbaly will be fixed by new usb stack ?) kldunload usb first. The USB stack crashes if the device disappears. This takes some effort as you will have to unload all related modules. If you have ums_load="YES" in your /boot/loader.conf without usb_load="YES", then you are in luck as you should be able to unload ums and usb will unload as well. Once these are unloaded you should be able to unload the PCMCIA card without problems. Works with Option cards this way. Nick From lme at FreeBSD.org Tue Nov 4 15:04:04 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Nov 4 15:04:22 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104220725.GC8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> <20081104220725.GC8256@e.0x20.net> Message-ID: <20081104230402.GD8256@e.0x20.net> On Tue, Nov 04, 2008 at 11:07:25PM +0100, Lars Engels wrote: > On Tue, Nov 04, 2008 at 07:56:47PM -0200, Renato Botelho wrote: > > On Tue, Nov 4, 2008 at 7:22 PM, Lars Engels wrote: > > > device usb2_ethernet_dav is still unknown in the commit version in HEAD. > > > > I believe it was just a typo, the correct is usb2_ethernet_udav > > Good point. :) After changing it to _udav I am getting this: > In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, > from /usr/src/sys/dev/usb2/sound/uaudio2.c:79: > /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No > such file or directory > /usr/src/sys/dev/usb2/sound/uaudio2.c:81:23: error: feeder_if.h: No such > file or directory > In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, > from /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:31: > /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No > such file or directory > /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:36:22: error: mixer_if.h: No > such file or directory > > mkdep: compile failed > Now I just removed everything but usb2_core from the kernel config and load the modules manually. So far it runs pretty good. Mounting a umass device, removing it and doing an 'ls' on the mountpoint freezes the system, I thought this should not happen with the new stack? sysctl hw.usb2.uscanner.uscanner: 0 ^^^^^^^^ Could it be that this should be "debug"? -- Lars Engels E-Mail: lars.engels@0x20.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081104/e5f0f4b1/attachment-0002.pgp From lme at FreeBSD.org Tue Nov 4 15:04:04 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Nov 4 15:04:23 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104220725.GC8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> <20081104220725.GC8256@e.0x20.net> Message-ID: <20081104230402.GD8256@e.0x20.net> On Tue, Nov 04, 2008 at 11:07:25PM +0100, Lars Engels wrote: > On Tue, Nov 04, 2008 at 07:56:47PM -0200, Renato Botelho wrote: > > On Tue, Nov 4, 2008 at 7:22 PM, Lars Engels wrote: > > > device usb2_ethernet_dav is still unknown in the commit version in HEAD. > > > > I believe it was just a typo, the correct is usb2_ethernet_udav > > Good point. :) After changing it to _udav I am getting this: > In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, > from /usr/src/sys/dev/usb2/sound/uaudio2.c:79: > /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No > such file or directory > /usr/src/sys/dev/usb2/sound/uaudio2.c:81:23: error: feeder_if.h: No such > file or directory > In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, > from /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:31: > /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No > such file or directory > /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:36:22: error: mixer_if.h: No > such file or directory > > mkdep: compile failed > Now I just removed everything but usb2_core from the kernel config and load the modules manually. So far it runs pretty good. Mounting a umass device, removing it and doing an 'ls' on the mountpoint freezes the system, I thought this should not happen with the new stack? sysctl hw.usb2.uscanner.uscanner: 0 ^^^^^^^^ Could it be that this should be "debug"? -- Lars Engels E-Mail: lars.engels@0x20.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081104/e5f0f4b1/attachment-0003.pgp From lme at FreeBSD.org Tue Nov 4 15:05:48 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Nov 4 15:05:55 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104230402.GD8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> Message-ID: <20081104230547.GE8256@e.0x20.net> On Wed, Nov 05, 2008 at 12:04:02AM +0100, Lars Engels wrote: > > > Now I just removed everything but usb2_core from the kernel config and > load the modules manually. So far it runs pretty good. > > Mounting a umass device, removing it and doing an 'ls' on the mountpoint > freezes the system, I thought this should not happen with the new stack? > > sysctl hw.usb2.uscanner.uscanner: 0 > ^^^^^^^^ > Could it be that this should be "debug"? And one last thing: # usbdevs -v usbdevs: no USB controllers found Huh? :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081104/346b7440/attachment.pgp From lme at FreeBSD.org Tue Nov 4 15:05:48 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Nov 4 15:06:06 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104230402.GD8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> Message-ID: <20081104230547.GE8256@e.0x20.net> On Wed, Nov 05, 2008 at 12:04:02AM +0100, Lars Engels wrote: > > > Now I just removed everything but usb2_core from the kernel config and > load the modules manually. So far it runs pretty good. > > Mounting a umass device, removing it and doing an 'ls' on the mountpoint > freezes the system, I thought this should not happen with the new stack? > > sysctl hw.usb2.uscanner.uscanner: 0 > ^^^^^^^^ > Could it be that this should be "debug"? And one last thing: # usbdevs -v usbdevs: no USB controllers found Huh? :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081104/346b7440/attachment-0001.pgp From tinderbox at freebsd.org Tue Nov 4 15:30:23 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 15:30:34 2008 Subject: [head tinderbox] failure on ia64/ia64 Message-ID: <20081104233019.09F5373039@freebsd-current.sentex.ca> TB --- 2008-11-04 23:05:24 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-04 23:05:24 - starting HEAD tinderbox run for ia64/ia64 TB --- 2008-11-04 23:05:24 - cleaning the object tree TB --- 2008-11-04 23:05:34 - cvsupping the source tree TB --- 2008-11-04 23:05:34 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/ia64/ia64/supfile TB --- 2008-11-04 23:05:40 - building world (CFLAGS=-O -pipe) TB --- 2008-11-04 23:05:40 - cd /src TB --- 2008-11-04 23:05:40 - /usr/bin/make -B buildworld >>> World build started on Tue Nov 4 23:05:42 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-04 23:30:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-04 23:30:18 - ERROR: failed to build world TB --- 2008-11-04 23:30:18 - tinderbox aborted TB --- 1074.46 user 134.05 system 1493.98 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From thompsa at FreeBSD.org Tue Nov 4 15:38:27 2008 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Tue Nov 4 15:38:46 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104230547.GE8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <20081104230547.GE8256@e.0x20.net> Message-ID: <20081104231135.GB840@citylink.fud.org.nz> On Wed, Nov 05, 2008 at 12:05:47AM +0100, Lars Engels wrote: > On Wed, Nov 05, 2008 at 12:04:02AM +0100, Lars Engels wrote: > > > > > > Now I just removed everything but usb2_core from the kernel config and > > load the modules manually. So far it runs pretty good. > > > > Mounting a umass device, removing it and doing an 'ls' on the mountpoint > > freezes the system, I thought this should not happen with the new stack? > > > > sysctl hw.usb2.uscanner.uscanner: 0 > > ^^^^^^^^ > > Could it be that this should be "debug"? > > And one last thing: > # usbdevs -v > usbdevs: no USB controllers found usbdevs does not work with it, there is a new usbconfig util that should do what you want. Andrew From thompsa at FreeBSD.org Tue Nov 4 15:38:27 2008 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Tue Nov 4 15:38:46 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104230547.GE8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <20081104230547.GE8256@e.0x20.net> Message-ID: <20081104231135.GB840@citylink.fud.org.nz> On Wed, Nov 05, 2008 at 12:05:47AM +0100, Lars Engels wrote: > On Wed, Nov 05, 2008 at 12:04:02AM +0100, Lars Engels wrote: > > > > > > Now I just removed everything but usb2_core from the kernel config and > > load the modules manually. So far it runs pretty good. > > > > Mounting a umass device, removing it and doing an 'ls' on the mountpoint > > freezes the system, I thought this should not happen with the new stack? > > > > sysctl hw.usb2.uscanner.uscanner: 0 > > ^^^^^^^^ > > Could it be that this should be "debug"? > > And one last thing: > # usbdevs -v > usbdevs: no USB controllers found usbdevs does not work with it, there is a new usbconfig util that should do what you want. Andrew From rbgarga at gmail.com Tue Nov 4 16:49:34 2008 From: rbgarga at gmail.com (Renato Botelho) Date: Tue Nov 4 16:49:40 2008 Subject: device snp build broken? In-Reply-To: <490C7625.6060608@quis.cx> References: <20081101061930.GA34365@regency.nsu.ru> <490C7625.6060608@quis.cx> Message-ID: <747dc8f30811041649s29561c8en75adcc353f9e9da2@mail.gmail.com> On Sat, Nov 1, 2008 at 1:30 PM, Jille Timmermans wrote: > Hello, > > snp(4) in -CURRENT is currently not supported. > Ed made a patch for it; which worked for me. > You can get the latest version from: > > http://people.freebsd.org/~ed/mpsafetty/ JFYI, the patch is not applying clean, at least on sys/dev/snp/snp.c -- Renato Botelho From tinderbox at freebsd.org Tue Nov 4 17:13:17 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 17:13:35 2008 Subject: [head tinderbox] failure on sparc64/sparc64 Message-ID: <20081105011314.4165573039@freebsd-current.sentex.ca> TB --- 2008-11-05 00:50:25 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 00:50:25 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-11-05 00:50:25 - cleaning the object tree TB --- 2008-11-05 00:50:34 - cvsupping the source tree TB --- 2008-11-05 00:50:34 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-05 00:50:41 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 00:50:41 - cd /src TB --- 2008-11-05 00:50:41 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 00:50:45 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 01:13:13 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 01:13:13 - ERROR: failed to build world TB --- 2008-11-05 01:13:13 - tinderbox aborted TB --- 936.92 user 132.16 system 1368.16 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From tinderbox at freebsd.org Tue Nov 4 17:31:23 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 17:31:30 2008 Subject: [head tinderbox] failure on sparc64/sun4v Message-ID: <20081105013120.8FAAF73039@freebsd-current.sentex.ca> TB --- 2008-11-05 01:11:55 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 01:11:55 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-11-05 01:11:55 - cleaning the object tree TB --- 2008-11-05 01:12:03 - cvsupping the source tree TB --- 2008-11-05 01:12:03 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-11-05 01:12:08 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 01:12:08 - cd /src TB --- 2008-11-05 01:12:08 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 01:12:09 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 01:31:20 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 01:31:20 - ERROR: failed to build world TB --- 2008-11-05 01:31:20 - tinderbox aborted TB --- 926.62 user 128.38 system 1165.56 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From imp at bsdimp.com Tue Nov 4 17:32:17 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Tue Nov 4 17:32:29 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104165029.225511d8@tau.draftnet> References: <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <20081104165029.225511d8@tau.draftnet> Message-ID: <20081104.183051.689649421.imp@bsdimp.com> In message: <20081104165029.225511d8@tau.draftnet> Bruce Cran writes: : On Wed, 5 Nov 2008 00:04:02 +0100 : Lars Engels wrote: : > Now I just removed everything but usb2_core from the kernel config and : > load the modules manually. So far it runs pretty good. : > : > Mounting a umass device, removing it and doing an 'ls' on the : > mountpoint freezes the system, I thought this should not happen with : > the new stack? : > : : I seem to remember the problem was tracked back to something in the cam : layer not liking surprise removals? For msdos filesystem, there were a number of minor tweaks that were made to make this suck less. Some were in the old usb layer, but most were in the buffer cache of FreeBSD to make it more resilient to errors from the device... But it wasn't totally fixed... Hans' stack did have a period of time when card removal was working better than the stock FreeBSD stack, but that got cleaned up before 7.0. Warner From imp at bsdimp.com Tue Nov 4 17:32:17 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Tue Nov 4 17:32:29 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104165029.225511d8@tau.draftnet> References: <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <20081104165029.225511d8@tau.draftnet> Message-ID: <20081104.183051.689649421.imp@bsdimp.com> In message: <20081104165029.225511d8@tau.draftnet> Bruce Cran writes: : On Wed, 5 Nov 2008 00:04:02 +0100 : Lars Engels wrote: : > Now I just removed everything but usb2_core from the kernel config and : > load the modules manually. So far it runs pretty good. : > : > Mounting a umass device, removing it and doing an 'ls' on the : > mountpoint freezes the system, I thought this should not happen with : > the new stack? : > : : I seem to remember the problem was tracked back to something in the cam : layer not liking surprise removals? For msdos filesystem, there were a number of minor tweaks that were made to make this suck less. Some were in the old usb layer, but most were in the buffer cache of FreeBSD to make it more resilient to errors from the device... But it wasn't totally fixed... Hans' stack did have a period of time when card removal was working better than the stock FreeBSD stack, but that got cleaned up before 7.0. Warner From pyunyh at gmail.com Tue Nov 4 17:38:05 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Tue Nov 4 17:38:12 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <4910C055.8000505@janh.de> References: <490F47BE.9080205@janh.de> <20081104015235.GC98154@cdnetworks.co.kr> <4910C055.8000505@janh.de> Message-ID: <20081105013558.GA99795@cdnetworks.co.kr> On Tue, Nov 04, 2008 at 10:36:21PM +0100, Jan Henrik Sylvester wrote: > Pyun YongHyeon wrote: > >On Mon, Nov 03, 2008 at 07:49:34PM +0100, Jan Henrik Sylvester wrote: > > > >Pyun YongHyeon writes: > > > >> http://people.freebsd.org/~yongari/ale/if_ale.c > > > > > > I got an Eee PC 1000H, too, with 7.1-BETA2 and just used scp to copy > > > with 11.5MB/s -- much better than wlan for big files. Great! > > > > > > >Thanks for testing! > > I was happy too early. Now I keep getting these: > ale0: DMA read error! -- resetting > ale0: could not disable Tx/Rx MAC(0x00000008)! It looks like Tx queue processing is still in progress. Would you show me hardware MAC statistics? ("sysctl dev.ale.0.stats" will show you detailed information.) Also ale(4) related dmesg output might be useful. > ale0: interrupt moderation is 100 us. > > The speed of copying a file has dropped to <50kB/s. Stopping and > restarting the interface does not help, even if I kldunload the driver > in the meantime. I have yet to reboot the machine. > > I do not know what is different, though. I left the computer alone for > an hour before using the network... > Hmm, this is the first severe report that is related to stability of driver. Personally I've nerver met this kind of error during writing of ale(4). ATM I have no idea why DMA read error happens on your box though. As you guess I don't have access to datasheet. Is there any reliable way to reproduce it? Also I've slightly changed code which may help to stop MAC in case of critical condition. Would you get the latest if_ale.c at the following URL and try again? http://people.freebsd.org/~yongari/ale/if_ale.c > > > This will probably not go into 7.1-RELEASE, will it? > > > >It was too late to go into 7.1-RELEASE, I guess. > > It seems to be too early, anyhow. > That's one of reason why I need more wider testing. :-) > Do you want me to try anything specific? (I hope it does not involve > recompiling the kernel on this slow Eee PC.) > Since you're using kernel module, just unload ale(4) and rebuilding ale(4) is enough. For example, #cd /path/to/ale_directory/ #fetch http://people.freebsd.org/~yongari/ale/if_ale.c #ifconfig ale0 down #kldunload if_ale #make && make install #kldload if_ale #ifconfig ale0 inet x.x.x.x netmask y.y.y.y or #dhclinet ale0 if you use DHCP. -- Regards, Pyun YongHyeon From tinderbox at freebsd.org Tue Nov 4 18:03:21 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 18:03:29 2008 Subject: [head tinderbox] failure on arm/arm Message-ID: <20081105020319.3EAEE73039@freebsd-current.sentex.ca> TB --- 2008-11-05 01:40:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 01:40:00 - starting HEAD tinderbox run for arm/arm TB --- 2008-11-05 01:40:00 - cleaning the object tree TB --- 2008-11-05 01:40:18 - cvsupping the source tree TB --- 2008-11-05 01:40:18 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/arm/arm/supfile TB --- 2008-11-05 01:40:26 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 01:40:26 - cd /src TB --- 2008-11-05 01:40:26 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 01:40:27 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 02:03:19 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 02:03:19 - ERROR: failed to build world TB --- 2008-11-05 02:03:19 - tinderbox aborted TB --- 975.84 user 135.00 system 1398.46 real http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full From pyunyh at gmail.com Tue Nov 4 18:12:02 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Tue Nov 4 18:12:09 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <91518878@bs1.sp34.ru> References: <20081030040637.GA78796@cdnetworks.co.kr> <20081030114845.GE78796@cdnetworks.co.kr> <14721476@bb.ipt.ru> <20081104020456.GD98154@cdnetworks.co.kr> <91518878@bs1.sp34.ru> Message-ID: <20081105020959.GB99795@cdnetworks.co.kr> On Tue, Nov 04, 2008 at 07:16:33PM +0300, Boris Samorodov wrote: > Pyun YongHyeon writes: > > > I had one report that link state changing was not handled correctly > > for the first time boot. He said unpluging and replugging UTP cable > > was necessary to make it work on EeePC-1000. Did you also see the > > same issue? > > No. In my case all is OK. Tested with two switches (3COM/1G at work > and 3COM/100M at home). Both loading from /etc/loader.conf and > manually kldloading autodetecting works just fine ending with > 100 Mbit/s full-duplex. > Ok. Thanks. -- Regards, Pyun YongHyeon From bruce at cran.org.uk Tue Nov 4 17:07:08 2008 From: bruce at cran.org.uk (Bruce Cran) Date: Tue Nov 4 18:55:52 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104230402.GD8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <367b2c980810310828q2f4f0ecfmdb8cae313c91e8c8@mail.gmail.com> <200810311656.44467.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> Message-ID: <20081104165029.225511d8@tau.draftnet> On Wed, 5 Nov 2008 00:04:02 +0100 Lars Engels wrote: > Now I just removed everything but usb2_core from the kernel config and > load the modules manually. So far it runs pretty good. > > Mounting a umass device, removing it and doing an 'ls' on the > mountpoint freezes the system, I thought this should not happen with > the new stack? > I seem to remember the problem was tracked back to something in the cam layer not liking surprise removals? -- Bruce Cran From scf at FreeBSD.org Tue Nov 4 20:23:16 2008 From: scf at FreeBSD.org (Sean C. Farley) Date: Tue Nov 4 20:23:23 2008 Subject: [head tinderbox] failure on sparc64/sun4v In-Reply-To: <20081105013120.8FAAF73039@freebsd-current.sentex.ca> References: <20081105013120.8FAAF73039@freebsd-current.sentex.ca> Message-ID: On Tue, 4 Nov 2008, FreeBSD Tinderbox wrote: *snip* > cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c > cc1: warnings being treated as errors > /src/lib/libutil/gr_util.c: In function 'gr_dup': > /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type > *** Error code 1 Does the following patch fix this warning (due to r184635) correctly? It should align the (char **) pointer correctly within the allocated buffer. The (void *) cast is necessary because gcc is not able to detect that the alignment was fixed. Better solutions are welcome. http://www.farley.org/freebsd/tmp/libutil.patch Sean -- scf@FreeBSD.org From tinderbox at freebsd.org Tue Nov 4 20:30:07 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 20:30:16 2008 Subject: [head tinderbox] failure on ia64/ia64 Message-ID: <20081105043003.E2ED373039@freebsd-current.sentex.ca> TB --- 2008-11-05 04:04:52 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 04:04:52 - starting HEAD tinderbox run for ia64/ia64 TB --- 2008-11-05 04:04:52 - cleaning the object tree TB --- 2008-11-05 04:05:06 - cvsupping the source tree TB --- 2008-11-05 04:05:06 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/ia64/ia64/supfile TB --- 2008-11-05 04:05:12 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 04:05:12 - cd /src TB --- 2008-11-05 04:05:12 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 04:05:14 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 04:30:03 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 04:30:03 - ERROR: failed to build world TB --- 2008-11-05 04:30:03 - tinderbox aborted TB --- 1074.21 user 134.16 system 1511.02 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From tinderbox at freebsd.org Tue Nov 4 22:14:04 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 22:14:16 2008 Subject: [head tinderbox] failure on sparc64/sparc64 Message-ID: <20081105061401.1F47373039@freebsd-current.sentex.ca> TB --- 2008-11-05 05:51:35 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 05:51:35 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-11-05 05:51:35 - cleaning the object tree TB --- 2008-11-05 05:51:41 - cvsupping the source tree TB --- 2008-11-05 05:51:41 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-05 05:51:47 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 05:51:47 - cd /src TB --- 2008-11-05 05:51:47 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 05:51:49 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 06:14:00 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 06:14:00 - ERROR: failed to build world TB --- 2008-11-05 06:14:00 - tinderbox aborted TB --- 935.91 user 131.13 system 1345.47 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From bsam at ipt.ru Tue Nov 4 22:30:56 2008 From: bsam at ipt.ru (Boris Samorodov) Date: Tue Nov 4 22:31:03 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <20081105013558.GA99795@cdnetworks.co.kr> (Pyun YongHyeon's message of "Wed\, 5 Nov 2008 10\:35\:58 +0900") References: <490F47BE.9080205@janh.de> <20081104015235.GC98154@cdnetworks.co.kr> <4910C055.8000505@janh.de> <20081105013558.GA99795@cdnetworks.co.kr> Message-ID: <12943517@bb.ipt.ru> Pyun YongHyeon writes: > On Tue, Nov 04, 2008 at 10:36:21PM +0100, Jan Henrik Sylvester wrote: > > Pyun YongHyeon wrote: > > >On Mon, Nov 03, 2008 at 07:49:34PM +0100, Jan Henrik Sylvester wrote: > > > > >Pyun YongHyeon writes: > > > > >> http://people.freebsd.org/~yongari/ale/if_ale.c > > > > > > > > I got an Eee PC 1000H, too, with 7.1-BETA2 and just used scp to copy > > > > with 11.5MB/s -- much better than wlan for big files. Great! > > > > > > > > > >Thanks for testing! > > > > I was happy too early. Now I keep getting these: > > ale0: DMA read error! -- resetting > > ale0: could not disable Tx/Rx MAC(0x00000008)! > > It looks like Tx queue processing is still in progress. > Would you show me hardware MAC statistics? > ("sysctl dev.ale.0.stats" will show you detailed information.) > Also ale(4) related dmesg output might be useful. > > > ale0: interrupt moderation is 100 us. > > > > The speed of copying a file has dropped to <50kB/s. Stopping and > > restarting the interface does not help, even if I kldunload the driver > > in the meantime. I have yet to reboot the machine. > > > > I do not know what is different, though. I left the computer alone for > > an hour before using the network... > > > > Hmm, this is the first severe report that is related to stability > of driver. Personally I've nerver met this kind of error during > writing of ale(4). ATM I have no idea why DMA read error happens on > your box though. As you guess I don't have access to datasheet. > > Is there any reliable way to reproduce it? I tried to reproduce under heavy net load but failed. I created a tmpfs 500M disk and fetched big files (i.e. openoffice.org3 distro as of 300M) to /tmp (at 11-12MB/s rate). No traces of failure. Here is some info: ----- # ifconfig ale0 ale0: flags=8843 metric 0 mtu 1500 options=3199 ether 00:22:15:XX:XX:XX inet 192.168.233.80 netmask 0xffffffc0 broadcast 192.168.233.127 media: Ethernet autoselect (100baseTX ) status: active # sysctl dev.ale.0.stats dev.ale.0.stats.rx.good_frames: 779733 dev.ale.0.stats.rx.good_bcast_frames: 232 dev.ale.0.stats.rx.good_mcast_frames: 0 dev.ale.0.stats.rx.pause_frames: 0 dev.ale.0.stats.rx.control_frames: 0 dev.ale.0.stats.rx.crc_errs: 0 dev.ale.0.stats.rx.len_errs: 0 dev.ale.0.stats.rx.good_octets: 1115319790 dev.ale.0.stats.rx.good_bcast_octets: 20376 dev.ale.0.stats.rx.good_mcast_octets: 0 dev.ale.0.stats.rx.runts: 0 dev.ale.0.stats.rx.fragments: 0 dev.ale.0.stats.rx.frames_64: 370 dev.ale.0.stats.rx.frames_65_127: 159 dev.ale.0.stats.rx.frames_128_255: 108 dev.ale.0.stats.rx.frames_256_511: 124 dev.ale.0.stats.rx.frames_512_1023: 58 dev.ale.0.stats.rx.frames_1024_1518: 779088 dev.ale.0.stats.rx.frames_1519_max: 0 dev.ale.0.stats.rx.trunc_errs: 0 dev.ale.0.stats.rx.fifo_oflows: 0 dev.ale.0.stats.rx.desc_oflows: 0 dev.ale.0.stats.rx.align_errs: 0 dev.ale.0.stats.rx.filtered: 174 dev.ale.0.stats.tx.good_frames: 516845 dev.ale.0.stats.tx.good_bcast_frames: 4 dev.ale.0.stats.tx.good_mcast_frames: 0 dev.ale.0.stats.tx.pause_frames: 0 dev.ale.0.stats.tx.control_frames: 0 dev.ale.0.stats.tx.excess_defers: 0 dev.ale.0.stats.tx.defers: 0 dev.ale.0.stats.tx.good_octets: 34113213 dev.ale.0.stats.tx.good_bcast_octets: 0 dev.ale.0.stats.tx.good_mcast_octets: 0 dev.ale.0.stats.tx.frames_64: 5 dev.ale.0.stats.tx.frames_65_127: 516840 dev.ale.0.stats.tx.frames_128_255: 0 dev.ale.0.stats.tx.frames_256_511: 0 dev.ale.0.stats.tx.frames_512_1023: 0 dev.ale.0.stats.tx.frames_1024_1518: 0 dev.ale.0.stats.tx.frames_1519_max: 0 dev.ale.0.stats.tx.single_colls: 0 dev.ale.0.stats.tx.multi_colls: 0 dev.ale.0.stats.tx.late_colls: 0 dev.ale.0.stats.tx.excess_colls: 0 dev.ale.0.stats.tx.abort: 0 dev.ale.0.stats.tx.underruns: 0 dev.ale.0.stats.tx.desc_underruns: 0 dev.ale.0.stats.tx.len_errs: 0 dev.ale.0.stats.tx.trunc_errs: 240 ----- > Also I've slightly changed code which may help to stop MAC in case > of critical condition. Would you get the latest if_ale.c at the > following URL and try again? > http://people.freebsd.org/~yongari/ale/if_ale.c I didn't use this file version though. > > > > This will probably not go into 7.1-RELEASE, will it? > > > > > >It was too late to go into 7.1-RELEASE, I guess. > > > > It seems to be too early, anyhow. > > > > That's one of reason why I need more wider testing. :-) > > > Do you want me to try anything specific? (I hope it does not involve > > recompiling the kernel on this slow Eee PC.) > > > > Since you're using kernel module, just unload ale(4) and > rebuilding ale(4) is enough. For example, > #cd /path/to/ale_directory/ > #fetch http://people.freebsd.org/~yongari/ale/if_ale.c > #ifconfig ale0 down > #kldunload if_ale > #make && make install > #kldload if_ale > #ifconfig ale0 inet x.x.x.x netmask y.y.y.y > or > #dhclinet ale0 if you use DHCP. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From tinderbox at freebsd.org Tue Nov 4 22:31:09 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 22:31:26 2008 Subject: [head tinderbox] failure on sparc64/sun4v Message-ID: <20081105063107.4C2A373039@freebsd-current.sentex.ca> TB --- 2008-11-05 06:11:41 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 06:11:41 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-11-05 06:11:41 - cleaning the object tree TB --- 2008-11-05 06:11:47 - cvsupping the source tree TB --- 2008-11-05 06:11:47 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-11-05 06:11:53 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 06:11:53 - cd /src TB --- 2008-11-05 06:11:53 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 06:11:54 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 06:31:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 06:31:07 - ERROR: failed to build world TB --- 2008-11-05 06:31:07 - tinderbox aborted TB --- 925.80 user 129.03 system 1166.10 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From tinderbox at freebsd.org Tue Nov 4 23:03:32 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Tue Nov 4 23:03:45 2008 Subject: [head tinderbox] failure on arm/arm Message-ID: <20081105070330.0690973039@freebsd-current.sentex.ca> TB --- 2008-11-05 06:40:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 06:40:00 - starting HEAD tinderbox run for arm/arm TB --- 2008-11-05 06:40:00 - cleaning the object tree TB --- 2008-11-05 06:40:20 - cvsupping the source tree TB --- 2008-11-05 06:40:20 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/arm/arm/supfile TB --- 2008-11-05 06:40:28 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 06:40:28 - cd /src TB --- 2008-11-05 06:40:28 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 06:40:30 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 07:03:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 07:03:29 - ERROR: failed to build world TB --- 2008-11-05 07:03:29 - tinderbox aborted TB --- 975.59 user 135.36 system 1409.02 real http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full From kevinxlinuz at 163.com Tue Nov 4 23:57:09 2008 From: kevinxlinuz at 163.com (kevin) Date: Tue Nov 4 23:57:27 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200810261633.22020.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <20081025181603.GD83037@elvis.mu.org> <200810261633.22020.hselasky@c2i.net> Message-ID: <49114E3D.9080201@163.com> Hans Petter Selasky wrote: > Hi, > > A new USB release is available: > > http://www.selasky.org/hans_petter/usb4bsd/for_review/ > > %md5 usb2_release_003.* > MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > %sha256 usb2_release_003.* > SHA256 (usb2_release_003.diff) = > 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > SHA256 (usb2_release_003.tar.gz) = > 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > > Changes since 002 release: > I try to compile kernel with usb2. Link error: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=nocona -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror vers.c ctfconvert -L VERSION vers.o linking kernel ng_ubt2.o(.text+0x38): In function `ubt_detach': : undefined reference to `ng_rmnode_self' ng_ubt2.o(.text+0x488): In function `ubt_attach': : undefined reference to `ng_make_node_common' ng_ubt2.o(.text+0x4be): In function `ubt_attach': : undefined reference to `ng_name_node' ng_ubt2.o(.text+0x52b): In function `ubt_attach': : undefined reference to `ng_unref_node' ng_ubt2.o(.text+0xc02): In function `ubt_modevent': : undefined reference to `ng_newtype' ng_ubt2.o(.text+0xde0): In function `ubt_bulk_read_complete': : undefined reference to `ng_package_data' ng_ubt2.o(.text+0xdfb): In function `ubt_bulk_read_complete': : undefined reference to `ng_address_hook' ng_ubt2.o(.text+0xe39): In function `ubt_bulk_read_complete': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0xfce): In function `ubt_intr_read_complete': : undefined reference to `ng_package_data' ng_ubt2.o(.text+0xfe9): In function `ubt_intr_read_complete': : undefined reference to `ng_address_hook' ng_ubt2.o(.text+0x1027): In function `ubt_intr_read_complete': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0x105d): In function `ng_ubt_rcvdata': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x10a7): In function `ng_ubt_rcvdata': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x124e): In function `ng_ubt_rcvmsg': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x12b3): In function `ng_ubt_rcvmsg': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x12bf): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1314): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1413): In function `ng_ubt_rcvmsg': : undefined reference to `ng_address_ID' ng_ubt2.o(.text+0x142a): In function `ng_ubt_rcvmsg': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0x1480): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1561): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x162e): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1a7a): In function `ng_ubt_shutdown': : undefined reference to `ng_unref_node' ng_ubt2.o(.text+0x1ab5): In function `ng_ubt_shutdown': : undefined reference to `ng_make_node_common' ng_ubt2.o(.text+0x1acc): In function `ng_ubt_shutdown': : undefined reference to `ng_name_node' ng_ubt2.o(.text+0x1b6b): In function `ng_ubt_shutdown': : undefined reference to `ng_unref_node' ng_ubt2.o(.text+0x1c28): In function `ubt_isoc_read_complete': : undefined reference to `ng_package_data' ng_ubt2.o(.text+0x1c43): In function `ubt_isoc_read_complete': : undefined reference to `ng_address_hook' ng_ubt2.o(.text+0x1d01): In function `ubt_isoc_read_complete': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0x1eaf): In function `ubt_bulk_read_callback': : undefined reference to `ng_send_fn' ng_ubt2.o(.text+0x20cd): In function `ubt_intr_read_callback': : undefined reference to `ng_send_fn' ng_ubt2.o(.text+0x242c): In function `ubt_isoc_read_callback': : undefined reference to `ng_send_fn' ng_ubt2.o(.text+0xc36): In function `ubt_modevent': : undefined reference to `ng_rmtype' ng_ubt2.o(.rodata+0x5f0): undefined reference to `ng_parse_uint16_type' ng_ubt2.o(.rodata+0x618): undefined reference to `ng_parse_uint16_type' ng_ubt2.o(.rodata+0x6c0): undefined reference to `ng_parse_struct_type' ng_ubt2.o(.rodata+0x700): undefined reference to `ng_parse_struct_type' ng_ubt2.o(.rodata+0x748): undefined reference to `ng_parse_int32_type' ng_ubt2.o(.rodata+0x760): undefined reference to `ng_parse_int32_type' ng_ubt2.o(.rodata+0x7a8): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x7c0): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x7d8): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x7f0): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x808): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x820): more undefined references to `ng_parse_uint32_type' follow *** Error code 1 I removed all old usb config. any other depends for usb2_bluetooth_ng? # USB core support device usb2_core # USB controller support device usb2_controller device usb2_controller_ehci device usb2_controller_ohci device usb2_controller_uhci # USB mass storage support device usb2_storage device usb2_storage_mass # USB ethernet support, requires miibus #device usb2_ethernet #device usb2_ethernet_aue #device usb2_ethernet_axe #device usb2_ethernet_cdce #device usb2_ethernet_cue #device usb2_ethernet_kue #device usb2_ethernet_rue #device usb2_ethernet_dav # USB wireless LAN support #device usb2_wlan #device usb2_wlan_rum #device usb2_wlan_ral #device usb2_wlan_zyd # USB serial device support #device usb2_serial #device usb2_serial_ark #device usb2_serial_bsa #device usb2_serial_bser #device usb2_serial_chcom #device usb2_serial_cycom #device usb2_serial_foma #device usb2_serial_ftdi #device usb2_serial_gensa #device usb2_serial_ipaq #device usb2_serial_lpt #device usb2_serial_mct #device usb2_serial_modem #device usb2_serial_moscom #device usb2_serial_plcom #device usb2_serial_visor #device usb2_serial_vscom # USB bluetooth support device usb2_bluetooth device usb2_bluetooth_ng # USB input device support device usb2_input device usb2_input_hid device usb2_input_kbd device usb2_input_ms # USB sound and MIDI device support #device usb2_sound Thanks, kevin From kevinxlinuz at 163.com Tue Nov 4 23:57:09 2008 From: kevinxlinuz at 163.com (kevin) Date: Tue Nov 4 23:57:27 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200810261633.22020.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <20081025181603.GD83037@elvis.mu.org> <200810261633.22020.hselasky@c2i.net> Message-ID: <49114E3D.9080201@163.com> Hans Petter Selasky wrote: > Hi, > > A new USB release is available: > > http://www.selasky.org/hans_petter/usb4bsd/for_review/ > > %md5 usb2_release_003.* > MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > %sha256 usb2_release_003.* > SHA256 (usb2_release_003.diff) = > 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > SHA256 (usb2_release_003.tar.gz) = > 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > > Changes since 002 release: > I try to compile kernel with usb2. Link error: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=nocona -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror vers.c ctfconvert -L VERSION vers.o linking kernel ng_ubt2.o(.text+0x38): In function `ubt_detach': : undefined reference to `ng_rmnode_self' ng_ubt2.o(.text+0x488): In function `ubt_attach': : undefined reference to `ng_make_node_common' ng_ubt2.o(.text+0x4be): In function `ubt_attach': : undefined reference to `ng_name_node' ng_ubt2.o(.text+0x52b): In function `ubt_attach': : undefined reference to `ng_unref_node' ng_ubt2.o(.text+0xc02): In function `ubt_modevent': : undefined reference to `ng_newtype' ng_ubt2.o(.text+0xde0): In function `ubt_bulk_read_complete': : undefined reference to `ng_package_data' ng_ubt2.o(.text+0xdfb): In function `ubt_bulk_read_complete': : undefined reference to `ng_address_hook' ng_ubt2.o(.text+0xe39): In function `ubt_bulk_read_complete': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0xfce): In function `ubt_intr_read_complete': : undefined reference to `ng_package_data' ng_ubt2.o(.text+0xfe9): In function `ubt_intr_read_complete': : undefined reference to `ng_address_hook' ng_ubt2.o(.text+0x1027): In function `ubt_intr_read_complete': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0x105d): In function `ng_ubt_rcvdata': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x10a7): In function `ng_ubt_rcvdata': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x124e): In function `ng_ubt_rcvmsg': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x12b3): In function `ng_ubt_rcvmsg': : undefined reference to `ng_free_item' ng_ubt2.o(.text+0x12bf): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1314): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1413): In function `ng_ubt_rcvmsg': : undefined reference to `ng_address_ID' ng_ubt2.o(.text+0x142a): In function `ng_ubt_rcvmsg': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0x1480): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1561): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x162e): In function `ng_ubt_rcvmsg': : undefined reference to `M_NETGRAPH_MSG' ng_ubt2.o(.text+0x1a7a): In function `ng_ubt_shutdown': : undefined reference to `ng_unref_node' ng_ubt2.o(.text+0x1ab5): In function `ng_ubt_shutdown': : undefined reference to `ng_make_node_common' ng_ubt2.o(.text+0x1acc): In function `ng_ubt_shutdown': : undefined reference to `ng_name_node' ng_ubt2.o(.text+0x1b6b): In function `ng_ubt_shutdown': : undefined reference to `ng_unref_node' ng_ubt2.o(.text+0x1c28): In function `ubt_isoc_read_complete': : undefined reference to `ng_package_data' ng_ubt2.o(.text+0x1c43): In function `ubt_isoc_read_complete': : undefined reference to `ng_address_hook' ng_ubt2.o(.text+0x1d01): In function `ubt_isoc_read_complete': : undefined reference to `ng_snd_item' ng_ubt2.o(.text+0x1eaf): In function `ubt_bulk_read_callback': : undefined reference to `ng_send_fn' ng_ubt2.o(.text+0x20cd): In function `ubt_intr_read_callback': : undefined reference to `ng_send_fn' ng_ubt2.o(.text+0x242c): In function `ubt_isoc_read_callback': : undefined reference to `ng_send_fn' ng_ubt2.o(.text+0xc36): In function `ubt_modevent': : undefined reference to `ng_rmtype' ng_ubt2.o(.rodata+0x5f0): undefined reference to `ng_parse_uint16_type' ng_ubt2.o(.rodata+0x618): undefined reference to `ng_parse_uint16_type' ng_ubt2.o(.rodata+0x6c0): undefined reference to `ng_parse_struct_type' ng_ubt2.o(.rodata+0x700): undefined reference to `ng_parse_struct_type' ng_ubt2.o(.rodata+0x748): undefined reference to `ng_parse_int32_type' ng_ubt2.o(.rodata+0x760): undefined reference to `ng_parse_int32_type' ng_ubt2.o(.rodata+0x7a8): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x7c0): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x7d8): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x7f0): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x808): undefined reference to `ng_parse_uint32_type' ng_ubt2.o(.rodata+0x820): more undefined references to `ng_parse_uint32_type' follow *** Error code 1 I removed all old usb config. any other depends for usb2_bluetooth_ng? # USB core support device usb2_core # USB controller support device usb2_controller device usb2_controller_ehci device usb2_controller_ohci device usb2_controller_uhci # USB mass storage support device usb2_storage device usb2_storage_mass # USB ethernet support, requires miibus #device usb2_ethernet #device usb2_ethernet_aue #device usb2_ethernet_axe #device usb2_ethernet_cdce #device usb2_ethernet_cue #device usb2_ethernet_kue #device usb2_ethernet_rue #device usb2_ethernet_dav # USB wireless LAN support #device usb2_wlan #device usb2_wlan_rum #device usb2_wlan_ral #device usb2_wlan_zyd # USB serial device support #device usb2_serial #device usb2_serial_ark #device usb2_serial_bsa #device usb2_serial_bser #device usb2_serial_chcom #device usb2_serial_cycom #device usb2_serial_foma #device usb2_serial_ftdi #device usb2_serial_gensa #device usb2_serial_ipaq #device usb2_serial_lpt #device usb2_serial_mct #device usb2_serial_modem #device usb2_serial_moscom #device usb2_serial_plcom #device usb2_serial_visor #device usb2_serial_vscom # USB bluetooth support device usb2_bluetooth device usb2_bluetooth_ng # USB input device support device usb2_input device usb2_input_hid device usb2_input_kbd device usb2_input_ms # USB sound and MIDI device support #device usb2_sound Thanks, kevin From hselasky at c2i.net Wed Nov 5 00:05:42 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 00:06:00 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104212254.GB8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> Message-ID: <200811050907.49411.hselasky@c2i.net> On Tuesday 04 November 2008, Lars Engels wrote: > On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: > > On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: > > > On Friday 31 October 2008, Olivier SMEDTS wrote: > > > > Hello, > > > > > > > > Each device driver has been splitted since RC3. > > > > Look in /boot/kernel/usb2_*. You can use modules. > > > > For example, for my usb mouse, I use usb2_input_ums. > > > > > > Hi, > > > > > > Looks like I made a small typo there. The module is named > > > "usb2_input_ms" while the kernel option is named "usb2_input_ums". The > > > kernel option should be named "usb2_input_ms". > > > > Is this the same issue? > > > > config: Error: device "usb2_controller_uss820dci" is unknown > > config: Error: device "usb2_ethernet_dav" is unknown > > device usb2_ethernet_dav is still unknown in the commit version in HEAD. Hi, It is going to be named usb2_ethernet_dav in the future. Currently it is named usb2_ethernet_udav . --HPS From hselasky at c2i.net Wed Nov 5 00:05:42 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 00:06:01 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104212254.GB8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <200810311716.10165.Thomas.Sparrevohn@btinternet.com> <20081104212254.GB8256@e.0x20.net> Message-ID: <200811050907.49411.hselasky@c2i.net> On Tuesday 04 November 2008, Lars Engels wrote: > On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: > > On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: > > > On Friday 31 October 2008, Olivier SMEDTS wrote: > > > > Hello, > > > > > > > > Each device driver has been splitted since RC3. > > > > Look in /boot/kernel/usb2_*. You can use modules. > > > > For example, for my usb mouse, I use usb2_input_ums. > > > > > > Hi, > > > > > > Looks like I made a small typo there. The module is named > > > "usb2_input_ms" while the kernel option is named "usb2_input_ums". The > > > kernel option should be named "usb2_input_ms". > > > > Is this the same issue? > > > > config: Error: device "usb2_controller_uss820dci" is unknown > > config: Error: device "usb2_ethernet_dav" is unknown > > device usb2_ethernet_dav is still unknown in the commit version in HEAD. Hi, It is going to be named usb2_ethernet_dav in the future. Currently it is named usb2_ethernet_udav . --HPS From hselasky at c2i.net Wed Nov 5 00:06:33 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 00:06:46 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <49114E3D.9080201@163.com> References: <200810251925.47273.hselasky@c2i.net> <200810261633.22020.hselasky@c2i.net> <49114E3D.9080201@163.com> Message-ID: <200811050908.35744.hselasky@c2i.net> On Wednesday 05 November 2008, kevin wrote: > Hans Petter Selasky wrote: > > Hi, > > > > A new USB release is available: > > > > http://www.selasky.org/hans_petter/usb4bsd/for_review/ > > > > %md5 usb2_release_003.* > > MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > > MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > > %sha256 usb2_release_003.* > > SHA256 (usb2_release_003.diff) = > > 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > > SHA256 (usb2_release_003.tar.gz) = > > 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > > > > Changes since 002 release: > > I try to compile kernel with usb2. > Link error: > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=nocona > -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -include opt_global.h -fno-common -finline-limit=8000 --param > inline-unit-growth=100 --param large-function-growth=1000 > -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 > -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector > -Werror vers.c > ctfconvert -L VERSION vers.o > linking kernel > > ng_ubt2.o(.text+0x38): In function `ubt_detach': > : undefined reference to `ng_rmnode_self' > > ng_ubt2.o(.text+0x488): In function `ubt_attach': > : undefined reference to `ng_make_node_common' > > ng_ubt2.o(.text+0x4be): In function `ubt_attach': > : undefined reference to `ng_name_node' > > ng_ubt2.o(.text+0x52b): In function `ubt_attach': > : undefined reference to `ng_unref_node' > > ng_ubt2.o(.text+0xc02): In function `ubt_modevent': > : undefined reference to `ng_newtype' > > ng_ubt2.o(.text+0xde0): In function `ubt_bulk_read_complete': > : undefined reference to `ng_package_data' > > ng_ubt2.o(.text+0xdfb): In function `ubt_bulk_read_complete': > : undefined reference to `ng_address_hook' > > ng_ubt2.o(.text+0xe39): In function `ubt_bulk_read_complete': > : undefined reference to `ng_snd_item' > > ng_ubt2.o(.text+0xfce): In function `ubt_intr_read_complete': > : undefined reference to `ng_package_data' > > ng_ubt2.o(.text+0xfe9): In function `ubt_intr_read_complete': > : undefined reference to `ng_address_hook' > > ng_ubt2.o(.text+0x1027): In function `ubt_intr_read_complete': > : undefined reference to `ng_snd_item' > > ng_ubt2.o(.text+0x105d): In function `ng_ubt_rcvdata': > : undefined reference to `ng_free_item' > > ng_ubt2.o(.text+0x10a7): In function `ng_ubt_rcvdata': > : undefined reference to `ng_free_item' > > ng_ubt2.o(.text+0x124e): In function `ng_ubt_rcvmsg': > : undefined reference to `ng_free_item' > > ng_ubt2.o(.text+0x12b3): In function `ng_ubt_rcvmsg': > : undefined reference to `ng_free_item' > > ng_ubt2.o(.text+0x12bf): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x1314): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x1413): In function `ng_ubt_rcvmsg': > : undefined reference to `ng_address_ID' > > ng_ubt2.o(.text+0x142a): In function `ng_ubt_rcvmsg': > : undefined reference to `ng_snd_item' > > ng_ubt2.o(.text+0x1480): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x1561): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x162e): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x1a7a): In function `ng_ubt_shutdown': > : undefined reference to `ng_unref_node' > > ng_ubt2.o(.text+0x1ab5): In function `ng_ubt_shutdown': > : undefined reference to `ng_make_node_common' > > ng_ubt2.o(.text+0x1acc): In function `ng_ubt_shutdown': > : undefined reference to `ng_name_node' > > ng_ubt2.o(.text+0x1b6b): In function `ng_ubt_shutdown': > : undefined reference to `ng_unref_node' > > ng_ubt2.o(.text+0x1c28): In function `ubt_isoc_read_complete': > : undefined reference to `ng_package_data' > > ng_ubt2.o(.text+0x1c43): In function `ubt_isoc_read_complete': > : undefined reference to `ng_address_hook' > > ng_ubt2.o(.text+0x1d01): In function `ubt_isoc_read_complete': > : undefined reference to `ng_snd_item' > > ng_ubt2.o(.text+0x1eaf): In function `ubt_bulk_read_callback': > : undefined reference to `ng_send_fn' > > ng_ubt2.o(.text+0x20cd): In function `ubt_intr_read_callback': > : undefined reference to `ng_send_fn' > > ng_ubt2.o(.text+0x242c): In function `ubt_isoc_read_callback': > : undefined reference to `ng_send_fn' > > ng_ubt2.o(.text+0xc36): In function `ubt_modevent': > : undefined reference to `ng_rmtype' > > ng_ubt2.o(.rodata+0x5f0): undefined reference to `ng_parse_uint16_type' > ng_ubt2.o(.rodata+0x618): undefined reference to `ng_parse_uint16_type' > ng_ubt2.o(.rodata+0x6c0): undefined reference to `ng_parse_struct_type' > ng_ubt2.o(.rodata+0x700): undefined reference to `ng_parse_struct_type' > ng_ubt2.o(.rodata+0x748): undefined reference to `ng_parse_int32_type' > ng_ubt2.o(.rodata+0x760): undefined reference to `ng_parse_int32_type' > ng_ubt2.o(.rodata+0x7a8): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x7c0): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x7d8): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x7f0): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x808): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x820): more undefined references to > `ng_parse_uint32_type' follow > *** Error code 1 > > I removed all old usb config. any other depends for usb2_bluetooth_ng? Hi, Try to load the module instead of having bluetooth in the kernel. Then all dependancies are loaded automatically. Depends on some bluetooth stuff. --HPS From hselasky at c2i.net Wed Nov 5 00:06:33 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 00:06:46 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <49114E3D.9080201@163.com> References: <200810251925.47273.hselasky@c2i.net> <200810261633.22020.hselasky@c2i.net> <49114E3D.9080201@163.com> Message-ID: <200811050908.35744.hselasky@c2i.net> On Wednesday 05 November 2008, kevin wrote: > Hans Petter Selasky wrote: > > Hi, > > > > A new USB release is available: > > > > http://www.selasky.org/hans_petter/usb4bsd/for_review/ > > > > %md5 usb2_release_003.* > > MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > > MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > > %sha256 usb2_release_003.* > > SHA256 (usb2_release_003.diff) = > > 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > > SHA256 (usb2_release_003.tar.gz) = > > 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > > > > Changes since 002 release: > > I try to compile kernel with usb2. > Link error: > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=nocona > -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -include opt_global.h -fno-common -finline-limit=8000 --param > inline-unit-growth=100 --param large-function-growth=1000 > -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 > -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector > -Werror vers.c > ctfconvert -L VERSION vers.o > linking kernel > > ng_ubt2.o(.text+0x38): In function `ubt_detach': > : undefined reference to `ng_rmnode_self' > > ng_ubt2.o(.text+0x488): In function `ubt_attach': > : undefined reference to `ng_make_node_common' > > ng_ubt2.o(.text+0x4be): In function `ubt_attach': > : undefined reference to `ng_name_node' > > ng_ubt2.o(.text+0x52b): In function `ubt_attach': > : undefined reference to `ng_unref_node' > > ng_ubt2.o(.text+0xc02): In function `ubt_modevent': > : undefined reference to `ng_newtype' > > ng_ubt2.o(.text+0xde0): In function `ubt_bulk_read_complete': > : undefined reference to `ng_package_data' > > ng_ubt2.o(.text+0xdfb): In function `ubt_bulk_read_complete': > : undefined reference to `ng_address_hook' > > ng_ubt2.o(.text+0xe39): In function `ubt_bulk_read_complete': > : undefined reference to `ng_snd_item' > > ng_ubt2.o(.text+0xfce): In function `ubt_intr_read_complete': > : undefined reference to `ng_package_data' > > ng_ubt2.o(.text+0xfe9): In function `ubt_intr_read_complete': > : undefined reference to `ng_address_hook' > > ng_ubt2.o(.text+0x1027): In function `ubt_intr_read_complete': > : undefined reference to `ng_snd_item' > > ng_ubt2.o(.text+0x105d): In function `ng_ubt_rcvdata': > : undefined reference to `ng_free_item' > > ng_ubt2.o(.text+0x10a7): In function `ng_ubt_rcvdata': > : undefined reference to `ng_free_item' > > ng_ubt2.o(.text+0x124e): In function `ng_ubt_rcvmsg': > : undefined reference to `ng_free_item' > > ng_ubt2.o(.text+0x12b3): In function `ng_ubt_rcvmsg': > : undefined reference to `ng_free_item' > > ng_ubt2.o(.text+0x12bf): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x1314): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x1413): In function `ng_ubt_rcvmsg': > : undefined reference to `ng_address_ID' > > ng_ubt2.o(.text+0x142a): In function `ng_ubt_rcvmsg': > : undefined reference to `ng_snd_item' > > ng_ubt2.o(.text+0x1480): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x1561): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x162e): In function `ng_ubt_rcvmsg': > : undefined reference to `M_NETGRAPH_MSG' > > ng_ubt2.o(.text+0x1a7a): In function `ng_ubt_shutdown': > : undefined reference to `ng_unref_node' > > ng_ubt2.o(.text+0x1ab5): In function `ng_ubt_shutdown': > : undefined reference to `ng_make_node_common' > > ng_ubt2.o(.text+0x1acc): In function `ng_ubt_shutdown': > : undefined reference to `ng_name_node' > > ng_ubt2.o(.text+0x1b6b): In function `ng_ubt_shutdown': > : undefined reference to `ng_unref_node' > > ng_ubt2.o(.text+0x1c28): In function `ubt_isoc_read_complete': > : undefined reference to `ng_package_data' > > ng_ubt2.o(.text+0x1c43): In function `ubt_isoc_read_complete': > : undefined reference to `ng_address_hook' > > ng_ubt2.o(.text+0x1d01): In function `ubt_isoc_read_complete': > : undefined reference to `ng_snd_item' > > ng_ubt2.o(.text+0x1eaf): In function `ubt_bulk_read_callback': > : undefined reference to `ng_send_fn' > > ng_ubt2.o(.text+0x20cd): In function `ubt_intr_read_callback': > : undefined reference to `ng_send_fn' > > ng_ubt2.o(.text+0x242c): In function `ubt_isoc_read_callback': > : undefined reference to `ng_send_fn' > > ng_ubt2.o(.text+0xc36): In function `ubt_modevent': > : undefined reference to `ng_rmtype' > > ng_ubt2.o(.rodata+0x5f0): undefined reference to `ng_parse_uint16_type' > ng_ubt2.o(.rodata+0x618): undefined reference to `ng_parse_uint16_type' > ng_ubt2.o(.rodata+0x6c0): undefined reference to `ng_parse_struct_type' > ng_ubt2.o(.rodata+0x700): undefined reference to `ng_parse_struct_type' > ng_ubt2.o(.rodata+0x748): undefined reference to `ng_parse_int32_type' > ng_ubt2.o(.rodata+0x760): undefined reference to `ng_parse_int32_type' > ng_ubt2.o(.rodata+0x7a8): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x7c0): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x7d8): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x7f0): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x808): undefined reference to `ng_parse_uint32_type' > ng_ubt2.o(.rodata+0x820): more undefined references to > `ng_parse_uint32_type' follow > *** Error code 1 > > I removed all old usb config. any other depends for usb2_bluetooth_ng? Hi, Try to load the module instead of having bluetooth in the kernel. Then all dependancies are loaded automatically. Depends on some bluetooth stuff. --HPS From hselasky at c2i.net Wed Nov 5 00:07:12 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 00:07:24 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104220725.GC8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> <20081104220725.GC8256@e.0x20.net> Message-ID: <200811050909.14866.hselasky@c2i.net> On Tuesday 04 November 2008, Lars Engels wrote: > On Tue, Nov 04, 2008 at 07:56:47PM -0200, Renato Botelho wrote: > > On Tue, Nov 4, 2008 at 7:22 PM, Lars Engels wrote: > > > On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: > > >> On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: > > >> > On Friday 31 October 2008, Olivier SMEDTS wrote: > > >> > > Hello, > > >> > > > > >> > > Each device driver has been splitted since RC3. > > >> > > Look in /boot/kernel/usb2_*. You can use modules. > > >> > > For example, for my usb mouse, I use usb2_input_ums. > > >> > > > >> > Hi, > > >> > > > >> > Looks like I made a small typo there. The module is named > > >> > "usb2_input_ms" while the kernel option is named "usb2_input_ums". > > >> > The kernel option should be named "usb2_input_ms". > > >> > > >> Is this the same issue? > > >> > > >> config: Error: device "usb2_controller_uss820dci" is unknown > > >> config: Error: device "usb2_ethernet_dav" is unknown > > > > > > device usb2_ethernet_dav is still unknown in the commit version in > > > HEAD. > > > > I believe it was just a typo, the correct is usb2_ethernet_udav > > Good point. :) After changing it to _udav I am getting this: > In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, > from /usr/src/sys/dev/usb2/sound/uaudio2.c:79: > /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No > such file or directory > /usr/src/sys/dev/usb2/sound/uaudio2.c:81:23: error: feeder_if.h: No such > file or directory > In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, > from /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:31: > /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No > such file or directory > /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:36:22: error: mixer_if.h: No > such file or directory > > mkdep: compile failed Hi, Dependancy towards "device sound" I think. Try loading the module instead of having the device in the kernel. --HPS From hselasky at c2i.net Wed Nov 5 00:12:37 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 00:12:44 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104230402.GD8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> Message-ID: <200811050914.44225.hselasky@c2i.net> On Wednesday 05 November 2008, Lars Engels wrote: Hi Lars, > Now I just removed everything but usb2_core from the kernel config and > load the modules manually. So far it runs pretty good. > > Mounting a umass device, removing it and doing an 'ls' on the mountpoint > freezes the system, I thought this should not happen with the new stack? It is not a USB problem. It is the CAM layer that is hanging on the disk. > > sysctl hw.usb2.uscanner.uscanner: 0 > ^^^^^^^^ > Could it be that this should be "debug"? Fixed in P4 now. Will soon sync my private SVN. --HPS From hselasky at c2i.net Wed Nov 5 00:13:51 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 00:14:00 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104230547.GE8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <20081104230402.GD8256@e.0x20.net> <20081104230547.GE8256@e.0x20.net> Message-ID: <200811050915.54175.hselasky@c2i.net> Hi, > And one last thing: > # usbdevs -v > usbdevs: no USB controllers found > That command is no longer supported. Use "usbconfig" instead. I'm not sure if it is currently installed by default. --HPS From hselasky at c2i.net Wed Nov 5 00:13:51 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 00:14:09 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104230547.GE8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <20081104230402.GD8256@e.0x20.net> <20081104230547.GE8256@e.0x20.net> Message-ID: <200811050915.54175.hselasky@c2i.net> Hi, > And one last thing: > # usbdevs -v > usbdevs: no USB controllers found > That command is no longer supported. Use "usbconfig" instead. I'm not sure if it is currently installed by default. --HPS From vova at fbsd.ru Wed Nov 5 00:58:18 2008 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Wed Nov 5 00:58:27 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200811042325.26574.nick@van-laarhoven.org> References: <200810092344.10388.nick@van-laarhoven.org> <1225836292.3428.37.camel@localhost> <200811042325.26574.nick@van-laarhoven.org> Message-ID: <1225875486.1713.37.camel@localhost> On Tue, 2008-11-04 at 23:25 +0100, Nick Hibma wrote: > > Now (5-days old current), everything looks fine, chat finishes, but ppp > > failed to handshake (same ppp config works before with ubsa): > > > > Nov 5 00:57:35 vbook ppp[4644]: tun0: Phase: PPP Started (background > > mode). Nov 5 00:57:35 vbook ppp[4644]: tun0: Phase: bundle: Establish > > Nov 5 00:57:35 vbook ppp[4644]: tun0: Chat: Send: ATDT#777^M > > Are you sure this phone number is correct? I'd have to check the 3GPP spec, > but something like > > ATDT*99***1# > > is more like the Huawei expects. The general format is > *****#. If you have set multiple PDP contexts > through AT+CGDCONT you can select the one you need by replacing the '1' in > the line above with the appropriate number. Actually it is not exactly 3G modem - it is Huawei EC500 for CDMA2000 network (hybrid 2.5G / 3G - Skylink operator in Russia) ATDT#777 is usual dial for that operator. > The 'Unexpected * in phase *' I've not seen before and would indicate that a > valid packet is received but one that is not appropriate at that point. You > might want to add some more logging options to see what is going on. > > > It looks like that characters are delivered not reliable way through ucom > > port: Same on U0.2 port: > > Weird. Should not happen. What I can do to help track the problem ? > > - after disconnecting ppp from port card is not reset, so no more any > > chat if start ppp again (you just need skip chat phase). - How to reset > > card before start ? > > We've had this problem with an EDGE card from Option, and we basically power > down the port and power up again the card to get it back. Patches have been > sent to Warner to get committed. Nice, are these patches attached to some PR ? > > - Disconnecting card crashes kernel, it is possible to catch that crash > > with DDB, but dump can't be written. Modem is on cardbus device. > > (probbaly will be fixed by new usb stack ?) > > kldunload usb first. The USB stack crashes if the device disappears. This > takes some effort as you will have to unload all related modules. If you > have ums_load="YES" in your /boot/loader.conf without usb_load="YES", then > you are in luck as you should be able to unload ums and usb will unload as > well. > > Once these are unloaded you should be able to unload the PCMCIA card without > problems. Works with Option cards this way. Uhh, really need to try new USB stack (I will try). > Nick -- Vladimir B. Grebenschikov vova@fbsd.ru From hselasky at c2i.net Wed Nov 5 01:07:13 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 01:07:26 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104220725.GC8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <747dc8f30811041356j72b3507cxbcdc077cf6f7ff12@mail.gmail.com> <20081104220725.GC8256@e.0x20.net> Message-ID: <200811050909.14866.hselasky@c2i.net> On Tuesday 04 November 2008, Lars Engels wrote: > On Tue, Nov 04, 2008 at 07:56:47PM -0200, Renato Botelho wrote: > > On Tue, Nov 4, 2008 at 7:22 PM, Lars Engels wrote: > > > On Fri, Oct 31, 2008 at 05:16:09PM +0000, Thomas Sparrevohn wrote: > > >> On Friday 31 October 2008 15:56:42 Hans Petter Selasky wrote: > > >> > On Friday 31 October 2008, Olivier SMEDTS wrote: > > >> > > Hello, > > >> > > > > >> > > Each device driver has been splitted since RC3. > > >> > > Look in /boot/kernel/usb2_*. You can use modules. > > >> > > For example, for my usb mouse, I use usb2_input_ums. > > >> > > > >> > Hi, > > >> > > > >> > Looks like I made a small typo there. The module is named > > >> > "usb2_input_ms" while the kernel option is named "usb2_input_ums". > > >> > The kernel option should be named "usb2_input_ms". > > >> > > >> Is this the same issue? > > >> > > >> config: Error: device "usb2_controller_uss820dci" is unknown > > >> config: Error: device "usb2_ethernet_dav" is unknown > > > > > > device usb2_ethernet_dav is still unknown in the commit version in > > > HEAD. > > > > I believe it was just a typo, the correct is usb2_ethernet_udav > > Good point. :) After changing it to _udav I am getting this: > In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, > from /usr/src/sys/dev/usb2/sound/uaudio2.c:79: > /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No > such file or directory > /usr/src/sys/dev/usb2/sound/uaudio2.c:81:23: error: feeder_if.h: No such > file or directory > In file included from /usr/src/sys/dev/sound/pcm/sound.h:94, > from /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:31: > /usr/src/sys/dev/sound/pcm/channel.h:216:24: error: channel_if.h: No > such file or directory > /usr/src/sys/dev/usb2/sound/uaudio2_pcm.c:36:22: error: mixer_if.h: No > such file or directory > > mkdep: compile failed Hi, Dependancy towards "device sound" I think. Try loading the module instead of having the device in the kernel. --HPS From hselasky at c2i.net Wed Nov 5 01:12:38 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 01:12:45 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081104230402.GD8256@e.0x20.net> References: <200810251925.47273.hselasky@c2i.net> <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> Message-ID: <200811050914.44225.hselasky@c2i.net> On Wednesday 05 November 2008, Lars Engels wrote: Hi Lars, > Now I just removed everything but usb2_core from the kernel config and > load the modules manually. So far it runs pretty good. > > Mounting a umass device, removing it and doing an 'ls' on the mountpoint > freezes the system, I thought this should not happen with the new stack? It is not a USB problem. It is the CAM layer that is hanging on the disk. > > sysctl hw.usb2.uscanner.uscanner: 0 > ^^^^^^^^ > Could it be that this should be "debug"? Fixed in P4 now. Will soon sync my private SVN. --HPS From imp at bsdimp.com Wed Nov 5 01:17:23 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Nov 5 01:17:36 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811050914.44225.hselasky@c2i.net> References: <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <200811050914.44225.hselasky@c2i.net> Message-ID: <20081105.021817.-332174942.imp@bsdimp.com> In message: <200811050914.44225.hselasky@c2i.net> Hans Petter Selasky writes: : On Wednesday 05 November 2008, Lars Engels wrote: : : Hi Lars, : : > Now I just removed everything but usb2_core from the kernel config and : > load the modules manually. So far it runs pretty good. : > : > Mounting a umass device, removing it and doing an 'ls' on the mountpoint : > freezes the system, I thought this should not happen with the new stack? : : It is not a USB problem. It is the CAM layer that is hanging on the disk. Sure it is CAM layer and not buffer cache or filesystem code? Warner From imp at bsdimp.com Wed Nov 5 01:17:23 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Nov 5 01:17:36 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811050914.44225.hselasky@c2i.net> References: <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <200811050914.44225.hselasky@c2i.net> Message-ID: <20081105.021817.-332174942.imp@bsdimp.com> In message: <200811050914.44225.hselasky@c2i.net> Hans Petter Selasky writes: : On Wednesday 05 November 2008, Lars Engels wrote: : : Hi Lars, : : > Now I just removed everything but usb2_core from the kernel config and : > load the modules manually. So far it runs pretty good. : > : > Mounting a umass device, removing it and doing an 'ls' on the mountpoint : > freezes the system, I thought this should not happen with the new stack? : : It is not a USB problem. It is the CAM layer that is hanging on the disk. Sure it is CAM layer and not buffer cache or filesystem code? Warner From tinderbox at freebsd.org Wed Nov 5 01:32:51 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Nov 5 01:33:03 2008 Subject: [head tinderbox] failure on ia64/ia64 Message-ID: <20081105093248.713B373039@freebsd-current.sentex.ca> TB --- 2008-11-05 09:07:43 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 09:07:43 - starting HEAD tinderbox run for ia64/ia64 TB --- 2008-11-05 09:07:43 - cleaning the object tree TB --- 2008-11-05 09:07:57 - cvsupping the source tree TB --- 2008-11-05 09:07:57 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/ia64/ia64/supfile TB --- 2008-11-05 09:08:03 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 09:08:03 - cd /src TB --- 2008-11-05 09:08:03 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 09:08:04 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 09:32:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 09:32:48 - ERROR: failed to build world TB --- 2008-11-05 09:32:48 - tinderbox aborted TB --- 1074.77 user 132.99 system 1504.41 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From rink at FreeBSD.org Wed Nov 5 02:04:38 2008 From: rink at FreeBSD.org (Rink Springer) Date: Wed Nov 5 02:04:50 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081105.021817.-332174942.imp@bsdimp.com> References: <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <200811050914.44225.hselasky@c2i.net> <20081105.021817.-332174942.imp@bsdimp.com> Message-ID: <20081105100433.GA43232@rink.nu> On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: > In message: <200811050914.44225.hselasky@c2i.net> > Hans Petter Selasky writes: > : On Wednesday 05 November 2008, Lars Engels wrote: > : > Mounting a umass device, removing it and doing an 'ls' on the mountpoint > : > freezes the system, I thought this should not happen with the new stack? > : > : It is not a USB problem. It is the CAM layer that is hanging on the disk. > > Sure it is CAM layer and not buffer cache or filesystem code? Well, the CAM layer problem will immediately first - it does not like CAM busses disappearing. Once this is fixed or avoided and the problem still shows up, we can blame buffer cache / filesystem code. As I suggested before, a good fix is to create one CAM bus per USB root hub, and use that to attach all umass devices to. This will also get rid of the one-bus-per-umass-device which is visually unappealling. Regards, Rink -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder From rink at FreeBSD.org Wed Nov 5 02:04:38 2008 From: rink at FreeBSD.org (Rink Springer) Date: Wed Nov 5 02:04:51 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081105.021817.-332174942.imp@bsdimp.com> References: <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <200811050914.44225.hselasky@c2i.net> <20081105.021817.-332174942.imp@bsdimp.com> Message-ID: <20081105100433.GA43232@rink.nu> On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: > In message: <200811050914.44225.hselasky@c2i.net> > Hans Petter Selasky writes: > : On Wednesday 05 November 2008, Lars Engels wrote: > : > Mounting a umass device, removing it and doing an 'ls' on the mountpoint > : > freezes the system, I thought this should not happen with the new stack? > : > : It is not a USB problem. It is the CAM layer that is hanging on the disk. > > Sure it is CAM layer and not buffer cache or filesystem code? Well, the CAM layer problem will immediately first - it does not like CAM busses disappearing. Once this is fixed or avoided and the problem still shows up, we can blame buffer cache / filesystem code. As I suggested before, a good fix is to create one CAM bus per USB root hub, and use that to attach all umass devices to. This will also get rid of the one-bus-per-umass-device which is visually unappealling. Regards, Rink -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder From kevinxlinuz at 163.com Wed Nov 5 02:41:26 2008 From: kevinxlinuz at 163.com (kevin) Date: Wed Nov 5 02:41:35 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811050908.35744.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <200810261633.22020.hselasky@c2i.net> <49114E3D.9080201@163.com> <200811050908.35744.hselasky@c2i.net> Message-ID: <49117846.9080301@163.com> Hans Petter Selasky wrote: > On Wednesday 05 November 2008, kevin wrote: > >> Hans Petter Selasky wrote: >> >>> Hi, >>> >>> A new USB release is available: >>> >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ >>> >>> %md5 usb2_release_003.* >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf >>> %sha256 usb2_release_003.* >>> SHA256 (usb2_release_003.diff) = >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b >>> SHA256 (usb2_release_003.tar.gz) = >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 >>> >>> Changes since 002 release: >>> >> I try to compile kernel with usb2. >> >> > Hi, > > Try to load the module instead of having bluetooth in the kernel. Then all > dependancies are loaded automatically. > > Depends on some bluetooth stuff. > > --HPS > > I build kernel without usb2_bluetooth_ng successfully. i notice that fingerpring and bluetooth mouse nolonger work now. in dmesg: ugen0.2: at usbus0 ugen0.3: at usbus0 maybe /etc/rc.d/bthidd and fprint package need update now. Thanks, kevin From kevinxlinuz at 163.com Wed Nov 5 02:41:26 2008 From: kevinxlinuz at 163.com (kevin) Date: Wed Nov 5 02:41:44 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811050908.35744.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <200810261633.22020.hselasky@c2i.net> <49114E3D.9080201@163.com> <200811050908.35744.hselasky@c2i.net> Message-ID: <49117846.9080301@163.com> Hans Petter Selasky wrote: > On Wednesday 05 November 2008, kevin wrote: > >> Hans Petter Selasky wrote: >> >>> Hi, >>> >>> A new USB release is available: >>> >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ >>> >>> %md5 usb2_release_003.* >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf >>> %sha256 usb2_release_003.* >>> SHA256 (usb2_release_003.diff) = >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b >>> SHA256 (usb2_release_003.tar.gz) = >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 >>> >>> Changes since 002 release: >>> >> I try to compile kernel with usb2. >> >> > Hi, > > Try to load the module instead of having bluetooth in the kernel. Then all > dependancies are loaded automatically. > > Depends on some bluetooth stuff. > > --HPS > > I build kernel without usb2_bluetooth_ng successfully. i notice that fingerpring and bluetooth mouse nolonger work now. in dmesg: ugen0.2: at usbus0 ugen0.3: at usbus0 maybe /etc/rc.d/bthidd and fprint package need update now. Thanks, kevin From tinderbox at freebsd.org Wed Nov 5 03:17:39 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Nov 5 03:17:51 2008 Subject: [head tinderbox] failure on sparc64/sparc64 Message-ID: <20081105111736.18E2273039@freebsd-current.sentex.ca> TB --- 2008-11-05 10:54:58 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 10:54:58 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-11-05 10:54:58 - cleaning the object tree TB --- 2008-11-05 10:55:07 - cvsupping the source tree TB --- 2008-11-05 10:55:07 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-05 10:55:13 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 10:55:13 - cd /src TB --- 2008-11-05 10:55:13 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 10:55:15 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 11:17:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 11:17:35 - ERROR: failed to build world TB --- 2008-11-05 11:17:35 - tinderbox aborted TB --- 937.66 user 130.27 system 1357.38 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From tinderbox at freebsd.org Wed Nov 5 03:33:56 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Wed Nov 5 03:34:03 2008 Subject: [head tinderbox] failure on sparc64/sun4v Message-ID: <20081105113354.1EF6873039@freebsd-current.sentex.ca> TB --- 2008-11-05 11:14:02 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-05 11:14:02 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-11-05 11:14:02 - cleaning the object tree TB --- 2008-11-05 11:14:13 - cvsupping the source tree TB --- 2008-11-05 11:14:13 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-11-05 11:14:19 - building world (CFLAGS=-O -pipe) TB --- 2008-11-05 11:14:19 - cd /src TB --- 2008-11-05 11:14:19 - /usr/bin/make -B buildworld >>> World build started on Wed Nov 5 11:14:21 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ /src/lib/libutil/_secure_path.c /src/lib/libutil/auth.c /src/lib/libutil/gr_util.c /src/lib/libutil/expand_number.c /src/lib/libutil/flopen.c /src/lib/libutil/fparseln.c /src/lib/libutil/hexdump.c /src/lib/libutil/humanize_number.c /src/lib/libutil/kld.c /src/lib/libutil/login.c /src/lib/libutil/login_auth.c /src/lib/libutil/login_cap.c /src/lib/libutil/login_class.c /src/lib/libutil/login_crypt.c /src/lib/libutil/login_ok.c /src/lib/libutil/login_times.c /src/lib/libutil/login_tty.c /src/lib/libutil/logout.c /src/lib/libutil/logwtmp.c /src/lib/libutil/pidfile.c /src/lib/libutil/property.c /src/lib/libutil/pty.c /src/lib/libutil/pw_util.c /src/lib/libutil/realhostname.c /src/lib/libutil/stub.c /src/lib/libutil/trimdomain.c /src/lib/libutil/uucplock.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/_secure_path.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/auth.c cc -O -pipe -DLIBC_SCCS -DINET6 -I/src/lib/libutil -I/src/lib/libutil/../libc/gen/ -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/lib/libutil/gr_util.c cc1: warnings being treated as errors /src/lib/libutil/gr_util.c: In function 'gr_dup': /src/lib/libutil/gr_util.c:154: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/lib/libutil. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-05 11:33:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-05 11:33:54 - ERROR: failed to build world TB --- 2008-11-05 11:33:54 - tinderbox aborted TB --- 925.65 user 129.72 system 1191.24 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From Thomas.Sparrevohn at btinternet.com Wed Nov 5 04:36:46 2008 From: Thomas.Sparrevohn at btinternet.com (Thomas Sparrevohn) Date: Wed Nov 5 04:37:05 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811050915.54175.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <20081104230547.GE8256@e.0x20.net> <200811050915.54175.hselasky@c2i.net> Message-ID: <200811051236.41450.Thomas.Sparrevohn@btinternet.com> On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote: > Hi, > > > And one last thing: > > # usbdevs -v > > usbdevs: no USB controllers found > > > > That command is no longer supported. Use "usbconfig" instead. I'm not sure if > it is currently installed by default. > > --HPS > usbconfig does not install per default - it does not even seem to compile - From Thomas.Sparrevohn at btinternet.com Wed Nov 5 04:36:47 2008 From: Thomas.Sparrevohn at btinternet.com (Thomas Sparrevohn) Date: Wed Nov 5 04:37:06 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811050915.54175.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <20081104230547.GE8256@e.0x20.net> <200811050915.54175.hselasky@c2i.net> Message-ID: <200811051236.41450.Thomas.Sparrevohn@btinternet.com> On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote: > Hi, > > > And one last thing: > > # usbdevs -v > > usbdevs: no USB controllers found > > > > That command is no longer supported. Use "usbconfig" instead. I'm not sure if > it is currently installed by default. > > --HPS > usbconfig does not install per default - it does not even seem to compile - From pawel.worach at gmail.com Wed Nov 5 05:04:10 2008 From: pawel.worach at gmail.com (Pawel Worach) Date: Wed Nov 5 05:04:18 2008 Subject: panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 Message-ID: Hi, Got the following panic after I built some ports with WRKDIRPREFIX=/tmp/work where /tmp is tmpfs. FreeBSD one 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r184639M: Tue Nov 4 18:39:44 CET 2008 root@one:/usr/obj/usr/src/sys/IBMT61 amd64 panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 Unread portion of the kernel message buffer: panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x17d tmpfs_alloc_vp() at tmpfs_alloc_vp+0x255 tmpfs_lookup() at tmpfs_lookup+0x17a vfs_cache_lookup() at vfs_cache_lookup+0xda VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x41 lookup() at lookup+0x4ab namei() at namei+0x4a5 kern_statat() at kern_statat+0x7a stat() at stat+0x22 syscall() at syscall+0x237 Xfast_syscall() at Xfast_syscall+0xab --- syscall (188, FreeBSD ELF64, stat), rip = 0x80098bd7c, rsp = 0x7fffffffe318, rbp = 0x3 --- Uptime: 32m30s Physical memory: 503 MB Dumping 121 MB: 106 90 74 58 42 26 10 Reading symbols from /boot/kernel/geom_eli.ko...Reading symbols from /boot/kernel/geom_eli.ko.symbols...done. done. Loaded symbols for /boot/kernel/geom_eli.ko Reading symbols from /boot/kernel/snd_es137x.ko...Reading symbols from /boot/kernel/snd_es137x.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_es137x.ko Reading 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/snd_hda.ko...Reading symbols from /boot/kernel/snd_hda.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_hda.ko Reading symbols from /boot/kernel/acpi_ibm.ko...Reading symbols from /boot/kernel/acpi_ibm.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi_ibm.ko Reading symbols from /boot/kernel/if_iwn.ko...Reading symbols from /boot/kernel/if_iwn.ko.symbols...done. done. Loaded symbols for /boot/kernel/if_iwn.ko Reading symbols from /boot/kernel/tmpfs.ko...Reading symbols from /boot/kernel/tmpfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/tmpfs.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 #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:196 #1 0xffffffff802a6cc6 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xffffffff802a7162 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xffffffff8090ef64 in tmpfs_alloc_vp (mp=0xffffff000139f2f0, node=0xffffff000143d380, lkflag=525312, vpp=0xfffffffe528079a0, td=0xffffff00184f8a50) at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_subr.c:382 #4 0xffffffff8090d56c in tmpfs_lookup (v=Variable "v" is not available. ) at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_vnops.c:97 #5 0xffffffff80316930 in vfs_cache_lookup (ap=Variable "ap" is not available. ) at vnode_if.h:80 #6 0xffffffff804ea4df in VOP_LOOKUP_APV (vop=0xffffffff809101a0, a=0xfffffffe52807830) at vnode_if.c:99 #7 0xffffffff8031cb2d in lookup (ndp=0xfffffffe52807970) at vnode_if.h:54 #8 0xffffffff8031da67 in namei (ndp=0xfffffffe52807970) at /usr/src/sys/kern/vfs_lookup.c:235 #9 0xffffffff8032b64a in kern_statat (td=0xffffff00184f8a50, flag=Variable "flag" is not available. ) at /usr/src/sys/kern/vfs_syscalls.c:2333 #10 0xffffffff8032b96c in stat (td=Variable "td" is not available. ) at /usr/src/sys/kern/vfs_syscalls.c:2284 #11 0xffffffff804c7096 in syscall (frame=0xfffffffe52807c90) at /usr/src/sys/amd64/amd64/trap.c:898 #12 0xffffffff804aab3b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:338 #13 0x000000080098bd7c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) f 3 #3 0xffffffff8090ef64 in tmpfs_alloc_vp (mp=0xffffff000139f2f0, node=0xffffff000143d380, lkflag=525312, vpp=0xfffffffe528079a0, td=0xffffff00184f8a50) at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_subr.c:382 382 panic("tmpfs_alloc_vp: type %p %d", node, (int)node->tn_type); (kgdb) p *mp $1 = {mnt_mtx = {lock_object = {lo_name = 0xffffffff80528b3c "struct mount mtx", lo_flags = 16973824, lo_data = 0, lo_witness = 0x0}, mtx_lock = 4}, mnt_gen = 1, mnt_list = {tqe_next = 0x0, tqe_prev = 0xffffff000139f608}, mnt_op = 0xffffffff80910620, mnt_vfc = 0xffffffff80910800, mnt_vnodecovered = 0xffffff00013f5588, mnt_syncer = 0xffffff00013ed000, mnt_ref = 10, mnt_nvnodelist = {tqh_first = 0xffffff00013ed1d8, tqh_last = 0xffffff0010e135b0}, mnt_nvnodelistsize = 10, mnt_writeopcount = 0, mnt_kern_flag = 536870912, mnt_flag = 4096, mnt_noasync = 0, mnt_opt = 0xffffff00013253b0, mnt_optnew = 0x0, mnt_maxsymlinklen = 0, mnt_stat = {f_version = 537068824, f_type = 1, f_flags = 4096, f_bsize = 4096, f_iosize = 4096, f_blocks = 335705, f_bfree = 335696, f_bavail = 335696, f_files = 6138457, f_ffree = 6138441, f_syncwrites = 0, f_asyncwrites = 0, f_syncreads = 0, f_asyncreads = 0, f_spare = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0}, f_namemax = 255, f_owner = 0, f_fsid = {val = {16842497, 1}}, f_charspare = '\0' , f_fstypename = "tmpfs\000\000\000\000\000\000\000\000\000\000", f_mntfromname = "tmpfs", '\0' , f_mntonname = "/tmp", '\0' }, mnt_cred = 0xffffff0001442000, mnt_data = 0xffffff000133f480, mnt_time = 0, mnt_iosize_max = 65536, mnt_export = 0x0, mnt_label = 0x0, mnt_hashseed = 816498104, mnt_lockref = 0, mnt_secondary_writes = 0, mnt_secondary_accwrites = 0, mnt_susp_owner = 0x0, mnt_gjprovider = 0x0, mnt_explock = {lock_object = { lo_name = 0xffffffff80528b4d "explock", lo_flags = 91947008, lo_data = 0, lo_witness = 0x0}, lk_lock = 1, lk_timo = 0, lk_pri = 80}} (kgdb) p *node $2 = {tn_entries = {le_next = 0xffffff001855fc40, le_prev = 0xffffff001854c9a0}, tn_type = VNON, tn_id = 323, tn_status = 0, tn_size = 2608, tn_uid = 0, tn_gid = 0, tn_mode = 420, tn_flags = 0, tn_links = 0, tn_atime = {tv_sec = 1225890653, tv_nsec = 0}, tn_mtime = {tv_sec = 1225890653, tv_nsec = 0}, tn_ctime = {tv_sec = 1225890653, tv_nsec = 0}, tn_birthtime = {tv_sec = 1225890653, tv_nsec = 0}, tn_gen = 2381436011, tn_vnode = 0x0, tn_interlock = {lock_object = { lo_name = 0xffffffff809100a6 "tmpfs node interlock", lo_flags = 16973824, lo_data = 0, lo_witness = 0x0}, mtx_lock = 4}, tn_vpstate = 1, tn_spec = {tn_rdev = 26841288, tn_dir = {tn_parent = 0xffffff00019990c8, tn_dirhead = {tqh_first = 0x1, tqh_last = 0xffffff000143d440}, tn_readdir_lastn = 0, tn_readdir_lastp = 0x0}, tn_link = 0xffffff00019990c8 "G?T\200????", tn_reg = {tn_aobj = 0xffffff00019990c8, tn_aobj_pages = 1}, tn_fifo = {tn_fo_read = 0xffffff00019990c8, tn_fo_write = 0x1}}} (kgdb) p *vpp $3 = (struct vnode *) 0x0 (kgdb) p *td $4 = {td_lock = 0xffffffff806f6540, td_proc = 0xffffff0018617860, td_plist = {tqe_next = 0x0, tqe_prev = 0xffffff0018617870}, td_runq = {tqe_next = 0x0, tqe_prev = 0xffffffff806f6788}, td_slpq = {tqe_next = 0x0, tqe_prev = 0xffffff00011981c0}, td_lockq = { tqe_next = 0x0, tqe_prev = 0x0}, td_cpuset = 0xffffff000119bdc8, td_sel = 0xffffff000195b380, td_sleepqueue = 0xffffff00011981c0, td_turnstile = 0xffffff00013d8630, td_umtxq = 0xffffff001843e400, td_tid = 100098, td_sigqueue = {sq_signals = {__bits = {0, 0, 0, 0}}, sq_kill = {__bits = {0, 0, 0, 0}}, sq_list = {tqh_first = 0x0, tqh_last = 0xffffff00184f8af0}, sq_proc = 0xffffff0018617860, sq_flags = 1}, td_flags = 65542, td_inhibitors = 0, td_pflags = 0, td_dupfd = 0, td_sqqueue = 0, td_wchan = 0x0, td_wmesg = 0x0, td_lastcpu = 0 '\0', td_oncpu = 0 '\0', td_owepreempt = 0 '\0', td_tsqueue = 0 '\0', td_locks = 1, td_rw_rlocks = 0, td_lk_slocks = 0, td_blocked = 0x0, td_lockname = 0x0, td_contested = {lh_first = 0x0}, td_sleeplocks = 0x0, td_intr_nesting_level = 0, td_pinned = 2, td_ucred = 0xffffff0001736a00, td_estcpu = 0, td_slptick = 0, td_ru = {ru_utime = {tv_sec = 0, tv_usec = 0}, ru_stime = { tv_sec = 0, tv_usec = 0}, ru_maxrss = 1704, ru_ixrss = 33936, ru_idrss = 277548, ru_isrss = 38784, ru_minflt = 107, ru_majflt = 0, ru_nswap = 0, ru_inblock = 0, ru_oublock = 0, ru_msgsnd = 0, ru_msgrcv = 0, ru_nsignals = 0, ru_nvcsw = 0, ru_nivcsw = 0}, td_incruntime = 0, td_runtime = 0, td_pticks = 303, td_sticks = 303, td_iticks = 0, td_uticks = 0, td_uuticks = 0, td_usticks = 0, td_intrval = 0, td_oldsigmask = {__bits = {0, 0, 0, 0}}, td_sigmask = {__bits = {0, 0, 0, 0}}, td_generation = 0, td_sigstk = {ss_sp = 0x0, ss_size = 0, ss_flags = 4}, td_xsig = 0, td_profil_addr = 0, td_profil_ticks = 0, td_name = "sh\000lient", '\0' , td_fpop = 0x0, td_dbgflags = 0, td_rqindex = 32 ' ', td_base_pri = 128 '\200', td_priority = 128 '\200', td_pri_class = 3 '\003', td_user_pri = 190 '?', td_base_user_pri = 190 '?', td_pcb = 0xfffffffe52807d50, td_state = TDS_RUNNING, td_retval = {0, 16842497}, td_slpcallout = {c_links = {sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0, tqe_prev = 0xfffffffe4a5b6370}}, c_time = 37493, c_arg = 0xffffff00184f8a50, c_func = 0xffffffff802dc578 , c_lock = 0x0, c_flags = 16, c_cpu = 0}, td_frame = 0xfffffffe52807c90, td_kstack_obj = 0xffffff00019e2640, td_kstack = 18446744066503753728, td_kstack_pages = 4, td_altkstack_obj = 0x0, td_altkstack = 0, td_altkstack_pages = 0, td_critnest = 0, td_md = {md_spinlock_count = 0, md_saved_flags = 582}, td_sched = 0xffffff00184f8d90, td_ar = 0x0, td_syscalls = 245774, td_lprof = {{lh_first = 0x0}, {lh_first = 0x0}}, td_dtrace = 0x0, td_errno = 0} (kgdb) -- Pawel From kevinxlinuz at 163.com Wed Nov 5 07:01:01 2008 From: kevinxlinuz at 163.com (kevin) Date: Wed Nov 5 07:01:07 2008 Subject: shutdown and reboot do not work correct Message-ID: <4911B529.1030804@163.com> Hi, I update everything this afternoon(both kernel and world). when i try to reboot or shutdown system,i find something goes wrong.After system output "All buffers synced" and "Accounting disabled",system does not power off as normal. the keyboard still works and when i press the power button ,it output "acpi: suspend request ignored (not ready yet)", "acpi: request to enter state S5 failed (error 6)". Any one meet same problem? Thanks, kevin From ed at 80386.nl Wed Nov 5 07:06:39 2008 From: ed at 80386.nl (Ed Schouten) Date: Wed Nov 5 07:06:58 2008 Subject: device snp build broken? In-Reply-To: <4910C505.9070809@quis.cx> References: <20081101061930.GA34365@regency.nsu.ru> <490C7625.6060608@quis.cx> <4910C0DF.2040501@lissyara.su> <4910C505.9070809@quis.cx> Message-ID: <20081105150638.GD1165@hoeg.nl> Hello all, * Jille Timmermans wrote: > But it will make it into HEAD before 8.0. Small status update: I've just committed it to HEAD. As said in my previous email, it's not 100% finished yet, but it should already be good enough to do most basic things. It's always better than having a broken driver sitting in the tree. I really hope someone else gets tempted to fix the error condition handling, etc. Please contact me if you have any questions about the code or if you feel tempted to continue my work. Thanks! -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081105/4a49f3de/attachment.pgp From ed at 80386.nl Wed Nov 5 07:14:40 2008 From: ed at 80386.nl (Ed Schouten) Date: Wed Nov 5 07:14:46 2008 Subject: device snp build broken? In-Reply-To: <747dc8f30811041649s29561c8en75adcc353f9e9da2@mail.gmail.com> References: <20081101061930.GA34365@regency.nsu.ru> <490C7625.6060608@quis.cx> <747dc8f30811041649s29561c8en75adcc353f9e9da2@mail.gmail.com> Message-ID: <20081105151438.GE1165@hoeg.nl> Hello Renato, * Renato Botelho wrote: > JFYI, the patch is not applying clean, at least on sys/dev/snp/snp.c Well, it should, but the problem is that P4 (the VCS that a lot of developers use for hacking stuff) imports it code from CVS instead of SVN, which means patches that replace $FreeBSD$ tags won't apply to SVN checkouts properly. This shouldn't be a problem anymore, now that snp(4) is in SVN. Have fun! -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081105/bcfa37de/attachment.pgp From imp at bsdimp.com Wed Nov 5 08:02:59 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Nov 5 08:03:22 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <49117846.9080301@163.com> References: <49114E3D.9080201@163.com> <200811050908.35744.hselasky@c2i.net> <49117846.9080301@163.com> Message-ID: <20081105.090218.1678770569.imp@bsdimp.com> In message: <49117846.9080301@163.com> kevin writes: : Hans Petter Selasky wrote: : > On Wednesday 05 November 2008, kevin wrote: : > : >> Hans Petter Selasky wrote: : >> : >>> Hi, : >>> : >>> A new USB release is available: : >>> : >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ : >>> : >>> %md5 usb2_release_003.* : >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 : >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf : >>> %sha256 usb2_release_003.* : >>> SHA256 (usb2_release_003.diff) = : >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b : >>> SHA256 (usb2_release_003.tar.gz) = : >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 : >>> : >>> Changes since 002 release: : >>> : >> I try to compile kernel with usb2. : >> : >> : > Hi, : > : > Try to load the module instead of having bluetooth in the kernel. Then all : > dependancies are loaded automatically. : > : > Depends on some bluetooth stuff. : > : > --HPS : > : > : I build kernel without usb2_bluetooth_ng successfully. i notice that : fingerpring and bluetooth mouse nolonger work now. : in dmesg: : ugen0.2: at usbus0 : ugen0.3: at usbus0 : maybe /etc/rc.d/bthidd and fprint package need update now. Almost certainly... And they will likely have to deal with both stacks for a while... Warner From imp at bsdimp.com Wed Nov 5 08:02:59 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Nov 5 08:03:23 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <49117846.9080301@163.com> References: <49114E3D.9080201@163.com> <200811050908.35744.hselasky@c2i.net> <49117846.9080301@163.com> Message-ID: <20081105.090218.1678770569.imp@bsdimp.com> In message: <49117846.9080301@163.com> kevin writes: : Hans Petter Selasky wrote: : > On Wednesday 05 November 2008, kevin wrote: : > : >> Hans Petter Selasky wrote: : >> : >>> Hi, : >>> : >>> A new USB release is available: : >>> : >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ : >>> : >>> %md5 usb2_release_003.* : >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 : >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf : >>> %sha256 usb2_release_003.* : >>> SHA256 (usb2_release_003.diff) = : >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b : >>> SHA256 (usb2_release_003.tar.gz) = : >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 : >>> : >>> Changes since 002 release: : >>> : >> I try to compile kernel with usb2. : >> : >> : > Hi, : > : > Try to load the module instead of having bluetooth in the kernel. Then all : > dependancies are loaded automatically. : > : > Depends on some bluetooth stuff. : > : > --HPS : > : > : I build kernel without usb2_bluetooth_ng successfully. i notice that : fingerpring and bluetooth mouse nolonger work now. : in dmesg: : ugen0.2: at usbus0 : ugen0.3: at usbus0 : maybe /etc/rc.d/bthidd and fprint package need update now. Almost certainly... And they will likely have to deal with both stacks for a while... Warner From imp at bsdimp.com Wed Nov 5 08:03:02 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Nov 5 08:03:23 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081105100433.GA43232@rink.nu> References: <200811050914.44225.hselasky@c2i.net> <20081105.021817.-332174942.imp@bsdimp.com> <20081105100433.GA43232@rink.nu> Message-ID: <20081105.090111.-861032299.imp@bsdimp.com> In message: <20081105100433.GA43232@rink.nu> Rink Springer writes: : On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: : > In message: <200811050914.44225.hselasky@c2i.net> : > Hans Petter Selasky writes: : > : On Wednesday 05 November 2008, Lars Engels wrote: : > : > Mounting a umass device, removing it and doing an 'ls' on the mountpoint : > : > freezes the system, I thought this should not happen with the new stack? : > : : > : It is not a USB problem. It is the CAM layer that is hanging on the disk. : > : > Sure it is CAM layer and not buffer cache or filesystem code? : : Well, the CAM layer problem will immediately first - it does not like : CAM busses disappearing. Once this is fixed or avoided and the problem : still shows up, we can blame buffer cache / filesystem code. : : As I suggested before, a good fix is to create one CAM bus per USB root : hub, and use that to attach all umass devices to. This will also get rid : of the one-bus-per-umass-device which is visually unappealling. That might work. It might also be useful to see if the DragonFly patches to allow this port over or not... Warner From imp at bsdimp.com Wed Nov 5 08:03:02 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Wed Nov 5 08:03:33 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081105100433.GA43232@rink.nu> References: <200811050914.44225.hselasky@c2i.net> <20081105.021817.-332174942.imp@bsdimp.com> <20081105100433.GA43232@rink.nu> Message-ID: <20081105.090111.-861032299.imp@bsdimp.com> In message: <20081105100433.GA43232@rink.nu> Rink Springer writes: : On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: : > In message: <200811050914.44225.hselasky@c2i.net> : > Hans Petter Selasky writes: : > : On Wednesday 05 November 2008, Lars Engels wrote: : > : > Mounting a umass device, removing it and doing an 'ls' on the mountpoint : > : > freezes the system, I thought this should not happen with the new stack? : > : : > : It is not a USB problem. It is the CAM layer that is hanging on the disk. : > : > Sure it is CAM layer and not buffer cache or filesystem code? : : Well, the CAM layer problem will immediately first - it does not like : CAM busses disappearing. Once this is fixed or avoided and the problem : still shows up, we can blame buffer cache / filesystem code. : : As I suggested before, a good fix is to create one CAM bus per USB root : hub, and use that to attach all umass devices to. This will also get rid : of the one-bus-per-umass-device which is visually unappealling. That might work. It might also be useful to see if the DragonFly patches to allow this port over or not... Warner From nick at van-laarhoven.org Wed Nov 5 08:06:16 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Wed Nov 5 08:06:31 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200811051548.mA5Fmsot040177@lava.sentex.ca> References: <200810092344.10388.nick@van-laarhoven.org> <200811051548.mA5Fmsot040177@lava.sentex.ca> Message-ID: <200811051706.00850.nick@van-laarhoven.org> > At 04:44 PM 10/9/2008, Nick Hibma wrote: > >Just now I have committed a driver for Option and Huawei cards > > previously supported by the ubsa driver. More information is in the > > commit message. > > > >I am looking for people who would be able to provide more information > > after testing with the 3G cards branded by: > > Hi, > I gave it a try on the Sierra USB card and it seems to work > really well on RELENG_7! There is however also a mini-pci express > version of the Sierra card, the MC8775. Do you have plans to add > support for it ? I am not sure how the unit is even supposed to show > up as I dont see it in the dmesg, but I do see that it shows some > sort of umass device > > # usbdevs > addr 1: OHCI root hub, AMD > addr 2: USB MMC Storage, Sierra Wireless > addr 1: EHCI root hub, AMD If you could run usbdevs -v and then jot down the IDs you can add those to the top of u3g.c. You'll have to add a quirk like for other sierra devices that show up as mass storage and need to be kicked into modem mode. It pretends to be a mass storage device (with drivers on it) and after installation switches to modem mode. Or that's my guess. Nick > dmesg snippet > ... > isa_probe_children: probing PnP devices > umass0: addr 2> on uhub0 > umass0:0:0:-1: Attached to scbus0 > Device configuration finished. > procfs registered > Timecounter "TSC" frequency 498053687 Hz quality 800 > Timecounters tick every 1.000 msec > crypto: > vlan: initialized, using hash tables with chaining > IPsec: Initialized Security Association Processing. > pflog0: bpf attached > lo0: bpf attached > ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire > ad0: setting PIO4 on CS5536 chip > ad0: 1953MB at ata0-master PIO4 > ad0: 4001760 sectors [3970C/16H/63S] 4 sectors/interrupt 1 depth queue > GEOM: new disk ad0 > pass0 at umass-sim0 bus 0 target 0 lun 0 > pass0: Removable CD-ROM SCSI-0 device > pass0: 1.000MB/s transfers > Trying to mount root from ufs:/dev/ad0s1a > start_init: trying /sbin/init > bridge0: bpf attached > bridge0: Ethernet address: 3a:72:35:a3:25:ce > tun0: bpf attached > > Not sure why it shows up as a passthrough device ? > > ---Mike From swell.k at gmail.com Wed Nov 5 08:08:37 2008 From: swell.k at gmail.com (swell.k@gmail.com) Date: Wed Nov 5 08:08:43 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811051236.41450.Thomas.Sparrevohn@btinternet.com> (Thomas Sparrevohn's message of "Wed, 5 Nov 2008 12:36:40 +0000") References: <200810251925.47273.hselasky@c2i.net> <20081104230547.GE8256@e.0x20.net> <200811050915.54175.hselasky@c2i.net> <200811051236.41450.Thomas.Sparrevohn@btinternet.com> Message-ID: <863ai6yx36.fsf@gmail.com> Thomas Sparrevohn writes: > On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote: >> Hi, >> >> > And one last thing: >> > # usbdevs -v >> > usbdevs: no USB controllers found >> > >> >> That command is no longer supported. Use "usbconfig" instead. I'm not sure if >> it is currently installed by default. >> >> --HPS >> > > usbconfig does not install per default - it does not even seem to compile - I think this patch might be a workaround then. -------------- next part -------------- Index: share/man/man4/Makefile =================================================================== --- share/man/man4/Makefile (revision 184644) +++ share/man/man4/Makefile (working copy) @@ -416,6 +416,20 @@ ural.4 \ urio.4 \ usb.4 \ + usb2_bluetooth.4 \ + usb2_controller.4 \ + usb2_core.4 \ + usb2_ethernet.4 \ + usb2_image.4 \ + usb2_input.4 \ + usb2_misc.4 \ + usb2_ndis.4 \ + usb2_quirk.4 \ + usb2_serial.4 \ + usb2_sound.4 \ + usb2_storage.4 \ + usb2_template.4 \ + usb2_wlan.4 \ uscanner.4 \ uslcom.4 \ utopia.4 \ Index: usr.sbin/Makefile =================================================================== --- usr.sbin/Makefile (revision 184644) +++ usr.sbin/Makefile (working copy) @@ -181,6 +181,7 @@ trpt \ tzsetup \ ugidfw \ + ${_usbconfig} \ ${_usbdevs} \ ${_vidcontrol} \ vipw \ @@ -401,6 +402,7 @@ .endif .if ${MK_USB} != "no" +_usbconfig= usbconfig _usbdevs= usbdevs .endif Index: lib/Makefile =================================================================== --- lib/Makefile (revision 184644) +++ lib/Makefile (working copy) @@ -38,7 +38,8 @@ ${_libpmc} libproc librt ${_libsdp} ${_libsm} ${_libsmb} \ ${_libsmdb} \ ${_libsmutil} libstand ${_libtelnet} ${_libthr} libthread_db libufs \ - libugidfw ${_libusbhid} ${_libvgl} libwrap liby libz ${_bind} + libugidfw ${_libusb20} ${_libusbhid} ${_libvgl} libwrap liby libz \ + ${_bind} .if exists(${.CURDIR}/csu/${MACHINE_ARCH}-elf) _csu=csu/${MACHINE_ARCH}-elf @@ -135,6 +136,7 @@ .endif .if ${MK_USB} != "no" +_libusb20= libusb20 _libusbhid= libusbhid .endif Index: lib/libusb20/Makefile =================================================================== --- lib/libusb20/Makefile (revision 184644) +++ lib/libusb20/Makefile (working copy) @@ -18,7 +18,7 @@ INCS+= libusb20_compat10.h MAN= libusb20.3 MKLINT= no +CFLAGS+= -I${.CURDIR}/../../sys NOGCCERROR= .include - From hselasky at c2i.net Wed Nov 5 08:17:30 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 08:17:37 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081105.021817.-332174942.imp@bsdimp.com> References: <20081104220725.GC8256@e.0x20.net> <200811050914.44225.hselasky@c2i.net> <20081105.021817.-332174942.imp@bsdimp.com> Message-ID: <200811051719.30962.hselasky@c2i.net> On Wednesday 05 November 2008, M. Warner Losh wrote: > In message: <200811050914.44225.hselasky@c2i.net> > > : It is not a USB problem. It is the CAM layer that is hanging on the disk. > > Sure it is CAM layer and not buffer cache or filesystem code? > No, I'm not sure, except it is not an USB problem. I currently keep the CAM instance around after that the device has been removed from USB, returning an error on all subsequent SCSI requests. --HPS From hselasky at c2i.net Wed Nov 5 08:17:30 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 08:17:48 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081105.021817.-332174942.imp@bsdimp.com> References: <20081104220725.GC8256@e.0x20.net> <200811050914.44225.hselasky@c2i.net> <20081105.021817.-332174942.imp@bsdimp.com> Message-ID: <200811051719.30962.hselasky@c2i.net> On Wednesday 05 November 2008, M. Warner Losh wrote: > In message: <200811050914.44225.hselasky@c2i.net> > > : It is not a USB problem. It is the CAM layer that is hanging on the disk. > > Sure it is CAM layer and not buffer cache or filesystem code? > No, I'm not sure, except it is not an USB problem. I currently keep the CAM instance around after that the device has been removed from USB, returning an error on all subsequent SCSI requests. --HPS From hselasky at c2i.net Wed Nov 5 08:19:24 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 08:19:38 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081105100433.GA43232@rink.nu> References: <20081104220725.GC8256@e.0x20.net> <20081105.021817.-332174942.imp@bsdimp.com> <20081105100433.GA43232@rink.nu> Message-ID: <200811051721.26082.hselasky@c2i.net> On Wednesday 05 November 2008, Rink Springer wrote: > On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: > > In message: <200811050914.44225.hselasky@c2i.net> > > > > Hans Petter Selasky writes: > > : On Wednesday 05 November 2008, Lars Engels wrote: > > : > Mounting a umass device, removing it and doing an 'ls' on the > > : > mountpoint freezes the system, I thought this should not happen with > > : > the new stack? > > : > > : It is not a USB problem. It is the CAM layer that is hanging on the > > : disk. > > > > Sure it is CAM layer and not buffer cache or filesystem code? > > Well, the CAM layer problem will immediately first - it does not like > CAM busses disappearing. Once this is fixed or avoided and the problem > still shows up, we can blame buffer cache / filesystem code. > > As I suggested before, a good fix is to create one CAM bus per USB root > hub, and use that to attach all umass devices to. This will also get rid > of the one-bus-per-umass-device which is visually unappealling. > I've temporarily created one CAM bus per module, and release it when the usb2_storage_mass module is unloaded. --HPS From hselasky at c2i.net Wed Nov 5 08:19:24 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 08:19:39 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081105100433.GA43232@rink.nu> References: <20081104220725.GC8256@e.0x20.net> <20081105.021817.-332174942.imp@bsdimp.com> <20081105100433.GA43232@rink.nu> Message-ID: <200811051721.26082.hselasky@c2i.net> On Wednesday 05 November 2008, Rink Springer wrote: > On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote: > > In message: <200811050914.44225.hselasky@c2i.net> > > > > Hans Petter Selasky writes: > > : On Wednesday 05 November 2008, Lars Engels wrote: > > : > Mounting a umass device, removing it and doing an 'ls' on the > > : > mountpoint freezes the system, I thought this should not happen with > > : > the new stack? > > : > > : It is not a USB problem. It is the CAM layer that is hanging on the > > : disk. > > > > Sure it is CAM layer and not buffer cache or filesystem code? > > Well, the CAM layer problem will immediately first - it does not like > CAM busses disappearing. Once this is fixed or avoided and the problem > still shows up, we can blame buffer cache / filesystem code. > > As I suggested before, a good fix is to create one CAM bus per USB root > hub, and use that to attach all umass devices to. This will also get rid > of the one-bus-per-umass-device which is visually unappealling. > I've temporarily created one CAM bus per module, and release it when the usb2_storage_mass module is unloaded. --HPS From mike at sentex.net Wed Nov 5 08:19:48 2008 From: mike at sentex.net (Mike Tancsa) Date: Wed Nov 5 08:20:01 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200810092344.10388.nick@van-laarhoven.org> References: <200810092344.10388.nick@van-laarhoven.org> Message-ID: <200811051548.mA5Fmsot040177@lava.sentex.ca> At 04:44 PM 10/9/2008, Nick Hibma wrote: >Just now I have committed a driver for Option and Huawei cards previously >supported by the ubsa driver. More information is in the commit message. > >I am looking for people who would be able to provide more information after >testing with the 3G cards branded by: Hi, I gave it a try on the Sierra USB card and it seems to work really well on RELENG_7! There is however also a mini-pci express version of the Sierra card, the MC8775. Do you have plans to add support for it ? I am not sure how the unit is even supposed to show up as I dont see it in the dmesg, but I do see that it shows some sort of umass device # usbdevs addr 1: OHCI root hub, AMD addr 2: USB MMC Storage, Sierra Wireless addr 1: EHCI root hub, AMD dmesg snippet ... isa_probe_children: probing PnP devices umass0: on uhub0 umass0:0:0:-1: Attached to scbus0 Device configuration finished. procfs registered Timecounter "TSC" frequency 498053687 Hz quality 800 Timecounters tick every 1.000 msec crypto: vlan: initialized, using hash tables with chaining IPsec: Initialized Security Association Processing. pflog0: bpf attached lo0: bpf attached ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire ad0: setting PIO4 on CS5536 chip ad0: 1953MB at ata0-master PIO4 ad0: 4001760 sectors [3970C/16H/63S] 4 sectors/interrupt 1 depth queue GEOM: new disk ad0 pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Removable CD-ROM SCSI-0 device pass0: 1.000MB/s transfers Trying to mount root from ufs:/dev/ad0s1a start_init: trying /sbin/init bridge0: bpf attached bridge0: Ethernet address: 3a:72:35:a3:25:ce tun0: bpf attached Not sure why it shows up as a passthrough device ? ---Mike >OEM: > Merlin > Huawei > Option > Sierra > Novatel > Qualcomm > >Rebranded: > Dell > Vodafone > >Note: The driver can be copied across to FreeBSD 7-STABLE if you copy the >sys/modules/u3g directory and sys/dev/usb/u3g.c and sys/dev/usb/usbdevs >files from HEAD and _move_ the ID from ubsa to u3g. > >More information can be found on > > http://people.freebsd.org/~n_hibma/u3g.html > >Thanks, > >Nick >---------- Forwarded Message ---------- >Subject: svn commit: r183735 - in head: share/man/man4 sys/conf sys/dev/usb >sys/i386/conf sys/modules sys/modules/u3g >Date: Thu October 9 2008 >From: Nick Hibma >To: src-committers@freebsd.org, svn-src-all@freebsd.org, >svn-src-head@freebsd.org > >Author: n_hibma >Date: Thu Oct 9 21:25:01 2008 >New Revision: 183735 >URL: http://svn.freebsd.org/changeset/base/183735 > >Log: > Say hello to the u3g driver, implementing support for 3G modems. > > This was located in the ubsa driver, but should be moved into a separate > driver: > > - 3G modems provide multiple serial ports to allow AT commands while the >PPP > connection is up. > - 3G modems do not provide baud rate or other serial port settings. > - Huawei cards need specific initialisation. > - ubsa is for Belkin adapters, an Linuxy choice for another device like >3G. > > Speeds achieved here with a weak signal at best is ~40kb/s (UMTS). No >spooky > STALLED messages as well. > > Next: Move over all entries for Sierra and Novatel cards once I have found > testers, and implemented serial port enumeration for Sierra (or rather >have > Andrea Guzzo do it). They list all endpoints in 1 iface instead of 4 >ifaces. > > Submitted by: aguzzo@anywi.com > MFC after: 3 weeks > >Added: > head/share/man/man4/u3g.4 (contents, props changed) > head/sys/dev/usb/u3g.c (contents, props changed) > head/sys/modules/u3g/ > head/sys/modules/u3g/Makefile (contents, props changed) >Modified: > head/share/man/man4/Makefile > head/sys/conf/NOTES > head/sys/conf/files > head/sys/dev/usb/ubsa.c > head/sys/dev/usb/usbdevs > head/sys/i386/conf/GENERIC > head/sys/modules/Makefile > >Modified: head/share/man/man4/Makefile >============================================================================== >--- head/share/man/man4/Makefile Thu Oct 9 20:51:25 >2008 (r183734) >+++ head/share/man/man4/Makefile Thu Oct 9 21:25:01 >2008 (r183735) >@@ -384,6 +384,7 @@ MAN= aac.4 \ > twe.4 \ > tx.4 \ > txp.4 \ >+ u3g.4 \ > uark.4 \ > uart.4 \ > ubsa.4 \ > >Added: head/share/man/man4/u3g.4 >============================================================================== >--- /dev/null 00:00:00 1970 (empty, because file is newly added) >+++ head/share/man/man4/u3g.4 Thu Oct 9 21:25:01 2008 (r183735) >@@ -0,0 +1,100 @@ >+.\" >+.\" Copyright (c) 2008 AnyWi Technologies >+.\" All rights reserved. >+.\" >+.\" This code is derived from uark.c >+.\" >+.\" Permission to use, copy, modify, and distribute this software for any >+.\" purpose with or without fee is hereby granted, provided that the above >+.\" copyright notice and this permission notice appear in all copies. >+.\" >+.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL >WARRANTIES >+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF >+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR >+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES >+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN >+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF >+.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. >+.\" >+.\" $FreeBSD$ >+.\" >+.Dd October 7, 2008 >+.Dt U3G 4 >+.Os >+.Sh NAME >+.Nm u3g >+.Nd USB support for 3G datacards >+.Sh SYNOPSIS >+To compile this driver into the kernel, >+place the following lines in your >+kernel configuration file: >+.Bd -ragged -offset indent >+.Cd "device u3g" >+.Cd "device ucom" >+.Ed >+.Pp >+Alternatively, to load the driver as a >+module at boot time, place the following line in >+.Xr loader.conf 5 : >+.Bd -literal -offset indent >+u3g_load="YES" >+.Ed >+.Sh DESCRIPTION >+The >+.Nm >+driver provides support for the multiple USB-to-serial interfaces exposed >by >+many 3G usb/pccard modems. >+.Pp >+The device is accessed through the >+.Xr ucom 4 >+driver which makes it behave like a >+.Xr tty 4 . >+.Sh HARDWARE >+The >+.Nm >+driver supports the following adapters: >+.Pp >+.Bl -bullet -compact >+.It >+Option Globetrotter 3G Fusion (only 3G part, not WLAN) >+.It >+Option Globetrotter 3G Fusion Quad (only 3G part, not WLAN) >+.It >+Option Globetrotter 3G Quad >+.It >+Option Globetrotter 3G >+.It >+Vodafone Mobile Connect Card 3G >+.It >+Huawei E220 (E270?) >+.It >+Huawei Mobile >+.El >+.Pp >+The supported 3G cards provide the necessary modem port for ppp, >+pppd, or mpd connections as well as extra ports (depending on the specific >+device) to provide other functions (diagnostic port, SIM toolkit port) >+.Sh SEE ALSO >+.Xr tty 4 , >+.Xr ucom 4 , >+.Xr usb 4 , >+.Xr ubsa 4 >+.Sh HISTORY >+The >+.Nm >+driver >+appeared in >+.Fx 7.0 . >+The >+.Xr ubsa 4 >+manual page was modified for >+.Nm >+by >+.An Andrea Guzzo Aq aguzzo@anywi.com >+in September 2008. >+.Sh AUTHORS >+The >+.Nm >+driver was written by >+.An Andrea Guzzo Aq aguzzo@anywi.com . >+Hardware for testing provided by AnyWi Technologies, Leiden, NL. > >Modified: head/sys/conf/NOTES >============================================================================== >--- head/sys/conf/NOTES Thu Oct 9 20:51:25 2008 (r183734) >+++ head/sys/conf/NOTES Thu Oct 9 21:25:01 2008 (r183735) >@@ -2416,6 +2416,8 @@ device uscanner > # > # USB serial support > device ucom >+# USB support for 3G modem cards by Option, Huawei and Sierra >+device u3g > # USB support for Technologies ARK3116 based serial adapters > device uark > # USB support for Belkin F5U103 and compatible serial adapters >@@ -2441,7 +2443,6 @@ device aue > > # ASIX Electronics AX88172 USB 2.0 ethernet driver. Used in the > # LinkSys USB200M and various other adapters. >- > device axe > > # > >Modified: head/sys/conf/files >============================================================================== >--- head/sys/conf/files Thu Oct 9 20:51:25 2008 (r183734) >+++ head/sys/conf/files Thu Oct 9 21:25:01 2008 (r183735) >@@ -1327,6 +1327,7 @@ dev/usb/ohci_pci.c optional ohci pci > dev/usb/sl811hs.c optional slhci > dev/usb/slhci_pccard.c optional slhci pccard > dev/usb/uark.c optional uark >+dev/usb/u3g.c optional u3g > dev/usb/ubsa.c optional ubsa > dev/usb/ubser.c optional ubser > dev/usb/ucom.c optional ucom > >Added: head/sys/dev/usb/u3g.c >============================================================================== >--- /dev/null 00:00:00 1970 (empty, because file is newly added) >+++ head/sys/dev/usb/u3g.c Thu Oct 9 21:25:01 2008 (r183735) >@@ -0,0 +1,330 @@ >+/* >+ * Copyright (c) 2008 AnyWi Technologies >+ * Author: Andrea Guzzo >+ * * based on uark.c 1.1 2006/08/14 08:30:22 jsg * >+ * * parts from ubsa.c 183348 2008-09-25 12:00:56Z phk * >+ * >+ * Permission to use, copy, modify, and distribute this software for any >+ * purpose with or without fee is hereby granted, provided that the above >+ * copyright notice and this permission notice appear in all copies. >+ * >+ * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES >+ * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF >+ * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR >+ * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES >+ * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN >+ * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF >+ * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. >+ * >+ * $FreeBSD$ >+ */ >+ >+#include >+#include >+#include >+#include >+#include >+#include >+#include >+#include >+#include >+#include >+#include >+#include >+ >+#include >+#include >+#include >+ >+#include >+ >+#include "usbdevs.h" >+ >+#ifdef U3G_DEBUG >+#define DPRINTFN(n, x) do { if (u3gdebug > (n)) printf x; } while (0) >+int u3gtebug = 0; >+#else >+#define DPRINTFN(n, x) >+#endif >+#define DPRINTF(x) DPRINTFN(0, x) >+ >+#define U3GBUFSZ 1024 >+#define U3G_MAXPORTS 4 >+ >+struct u3g_softc { >+ struct ucom_softc sc_ucom[U3G_MAXPORTS];; >+ device_t sc_dev; >+ usbd_device_handle sc_udev; >+ u_char sc_msr; >+ u_char sc_lsr; >+ u_char numports; >+ >+ usbd_interface_handle sc_intr_iface; /* interrupt interface */ >+#ifdef U3G_DEBUG >+ int sc_intr_number; /* interrupt number */ >+ usbd_pipe_handle sc_intr_pipe; /* interrupt pipe */ >+ u_char *sc_intr_buf; /* interrupt buffer */ >+#endif >+ int sc_isize; >+}; >+ >+struct ucom_callback u3g_callback = { >+ NULL, >+ NULL, >+ NULL, >+ NULL, >+ NULL, >+ NULL, >+ NULL, >+ NULL, >+}; >+ >+static const struct usb_devno u3g_devs[] = { >+ /* OEM: Option */ >+ { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, >+ { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, >+ { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, >+ { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, >+ { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, >+ /* OEM: Huawei */ >+ { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, >+ { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, >+ >+ { 0, 0 } >+}; >+ >+#ifdef U3G_DEBUG >+static void >+u3g_intr(usbd_xfer_handle xfer, usbd_private_handle priv, usbd_status >status) >+{ >+ struct u3g_softc *sc = (struct u3g_softc *)priv; >+ device_printf(sc->sc_dev, "INTERRUPT CALLBACK\n"); >+} >+#endif >+ >+static int >+u3g_huawei_reinit(usbd_device_handle dev) >+{ >+ /* The Huawei device presents itself as a umass device with Windows >+ * drivers on it. After installation of the driver, it reinits into a >+ * 3G serial device. >+ */ >+ usb_device_request_t req; >+ usb_config_descriptor_t *cdesc; >+ >+ /* Get the config descriptor */ >+ cdesc = usbd_get_config_descriptor(dev); >+ if (cdesc == NULL) >+ return (UMATCH_NONE); >+ >+ /* One iface means umass mode, more than 1 (4 usually) means >3G mode */ >+ if (cdesc->bNumInterface > 1) >+ return (UMATCH_VENDOR_PRODUCT); >+ >+ req.bmRequestType = UT_WRITE_DEVICE; >+ req.bRequest = UR_SET_FEATURE; >+ USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); >+ USETW(req.wIndex, UHF_PORT_SUSPEND); >+ USETW(req.wLength, 0); >+ >+ (void) usbd_do_request(dev, &req, 0); >+ >+ return UMATCH_NONE; /* mismatch; it will be gone and reappear */ >+} >+ >+static int >+u3g_match(device_t self) >+{ >+ struct usb_attach_arg *uaa = device_get_ivars(self); >+ >+ if (uaa->iface != NULL) >+ return (UMATCH_NONE); >+ >+ if (uaa->vendor == USB_VENDOR_HUAWEI) >+ return u3g_huawei_reinit(uaa->device); >+ >+ if (usb_lookup(u3g_devs, uaa->vendor, uaa->product)) >+ return UMATCH_VENDOR_PRODUCT; >+ >+ return UMATCH_NONE; >+} >+ >+static int >+u3g_attach(device_t self) >+{ >+ struct u3g_softc *sc = device_get_softc(self); >+ struct usb_attach_arg *uaa = device_get_ivars(self); >+ usbd_device_handle dev = uaa->device; >+ usbd_interface_handle iface; >+ usb_interface_descriptor_t *id; >+ usb_endpoint_descriptor_t *ed; >+ usbd_status error; >+ int i, n; >+ usb_config_descriptor_t *cdesc; >+ struct ucom_softc *ucom = NULL; >+ char devnamefmt[32]; >+ >+ sc->sc_dev = self; >+#ifdef DEBUG >+ sc->sc_intr_number = -1; >+ sc->sc_intr_pipe = NULL; >+#endif >+ /* Move the device into the configured state. */ >+ error = usbd_set_config_index(dev, 1, 1); >+ if (error) { >+ device_printf(self, "failed to set configuration: %s\n", >+ usbd_errstr(error)); >+ goto bad; >+ } >+ >+ /* get the config descriptor */ >+ cdesc = usbd_get_config_descriptor(dev); >+ >+ if (cdesc == NULL) { >+ device_printf(self, "failed to get configuration >descriptor\n"); >+ goto bad; >+ } >+ >+ sc->sc_udev = dev; >+ sc->numports = (cdesc->bNumInterface <= >U3G_MAXPORTS)?cdesc->bNumInterface:U3G_MAXPORTS; >+ for ( i = 0; i < sc->numports; i++ ) { >+ ucom = &sc->sc_ucom[i]; >+ >+ ucom->sc_dev = self; >+ ucom->sc_udev = dev; >+ error = usbd_device2interface_handle(dev, i, &iface); >+ if (error) { >+ device_printf(ucom->sc_dev, >+ "failed to get interface, err=%s\n", >+ usbd_errstr(error)); >+ ucom->sc_dying = 1; >+ goto bad; >+ } >+ id = usbd_get_interface_descriptor(iface); >+ ucom->sc_iface = iface; >+ >+ ucom->sc_bulkin_no = ucom->sc_bulkout_no = -1; >+ for (n = 0; n < id->bNumEndpoints; n++) { >+ ed = usbd_interface2endpoint_descriptor(iface, n); >+ if (ed == NULL) { >+ device_printf(ucom->sc_dev, >+ "could not read endpoint >descriptor\n"); >+ goto bad; >+ } >+ if (UE_GET_DIR(ed->bEndpointAddress) == UE_DIR_IN && >+ UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) >+ ucom->sc_bulkin_no = ed->bEndpointAddress; >+ else if (UE_GET_DIR(ed->bEndpointAddress) == >UE_DIR_OUT && >+ UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) >+ ucom->sc_bulkout_no = ed->bEndpointAddress; >+ } >+ if (ucom->sc_bulkin_no == -1 || ucom->sc_bulkout_no == -1) { >+ device_printf(ucom->sc_dev, "missing endpoint\n"); >+ goto bad; >+ } >+ ucom->sc_parent = sc; >+ ucom->sc_ibufsize = U3GBUFSZ; >+ ucom->sc_obufsize = U3GBUFSZ; >+ ucom->sc_ibufsizepad = U3GBUFSZ; >+ ucom->sc_opkthdrlen = 0; >+ >+ ucom->sc_callback = &u3g_callback; >+ >+ sprintf(devnamefmt,"U%d.%%d", device_get_unit(self)); >+ DPRINTF(("u3g: in=0x%x out=0x%x, devname=%s\n", >+ ucom->sc_bulkin_no, ucom->sc_bulkout_no, devnamefmt)); >+#if __FreeBSD_version < 800000 >+ ucom_attach_tty(ucom, TS_CALLOUT, devnamefmt, i); >+#else >+ ucom_attach_tty(ucom, devnamefmt, i); >+#endif >+ } >+#ifdef U3G_DEBUG >+ if (sc->sc_intr_number != -1 && sc->sc_intr_pipe == NULL) { >+ sc->sc_intr_buf = malloc(sc->sc_isize, M_USBDEV, M_WAITOK); >+ error = usbd_open_pipe_intr(sc->sc_intr_iface, >+ sc->sc_intr_number, >+ USBD_SHORT_XFER_OK, >+ &sc->sc_intr_pipe, >+ sc, >+ sc->sc_intr_buf, >+ sc->sc_isize, >+ u3g_intr, >+ 100); >+ if (error) { >+ device_printf(self, >+ "cannot open interrupt pipe (addr %d)\n", >+ sc->sc_intr_number); >+ goto bad; >+ } >+ } >+#endif >+ device_printf(self, "configured %d serial ports (/dev/cuaU%d.X)", >+ sc->numports, device_get_unit(self)); >+ >+ return 0; >+ >+bad: >+ DPRINTF(("u3g_attach: ATTACH ERROR\n")); >+ ucom->sc_dying = 1; >+ return ENXIO; >+} >+ >+static int >+u3g_detach(device_t self) >+{ >+ struct u3g_softc *sc = device_get_softc(self); >+ int rv = 0; >+ int i; >+ >+ DPRINTF(("u3g_detach: sc=%p\n", sc)); >+ >+ for (i = 0; i < sc->numports; i++) { >+ if(sc->sc_ucom[i].sc_udev) { >+ sc->sc_ucom[i].sc_dying = 1; >+ rv = ucom_detach(&sc->sc_ucom[i]); >+ if(rv != 0) { >+ device_printf(self, "Can't deallocat >port %d", i); >+ return rv; >+ } >+ } >+ } >+ >+#ifdef U3G_DEBUG >+ if (sc->sc_intr_pipe != NULL) { >+ int err = usbd_abort_pipe(sc->sc_intr_pipe); >+ if (err) >+ device_printf(self, >+ "abort interrupt pipe failed: %s\n", >+ usbd_errstr(err)); >+ err = usbd_close_pipe(sc->sc_intr_pipe); >+ if (err) >+ device_printf(self, >+ "close interrupt pipe failed: %s\n", >+ usbd_errstr(err)); >+ free(sc->sc_intr_buf, M_USBDEV); >+ sc->sc_intr_pipe = NULL; >+ } >+#endif >+ >+ return 0; >+} >+ >+static device_method_t u3g_methods[] = { >+ /* Device interface */ >+ DEVMETHOD(device_probe, u3g_match), >+ DEVMETHOD(device_attach, u3g_attach), >+ DEVMETHOD(device_detach, u3g_detach), >+ >+ { 0, 0 } >+}; >+ >+static driver_t u3g_driver = { >+ "ucom", >+ u3g_methods, >+ sizeof (struct u3g_softc) >+}; >+ >+DRIVER_MODULE(u3g, uhub, u3g_driver, ucom_devclass, usbd_driver_load, 0); >+MODULE_DEPEND(u3g, usb, 1, 1, 1); >+MODULE_DEPEND(u3g, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); > >Modified: head/sys/dev/usb/ubsa.c >============================================================================== >--- head/sys/dev/usb/ubsa.c Thu Oct 9 20:51:25 2008 (r183734) >+++ head/sys/dev/usb/ubsa.c Thu Oct 9 21:25:01 2008 (r183735) >@@ -161,8 +161,6 @@ SYSCTL_INT(_hw_usb_ubsa, OID_AUTO, debug > struct ubsa_softc { > struct ucom_softc sc_ucom; > >- int sc_huawei; >- > int sc_iface_number; /* > interface number */ > > usbd_interface_handle sc_intr_iface; /* interrupt interface */ >@@ -228,24 +226,11 @@ static const struct ubsa_product { > { USB_VENDOR_GOHUBS, USB_PRODUCT_GOHUBS_GOCOM232 }, > /* Peracom */ > { USB_VENDOR_PERACOM, USB_PRODUCT_PERACOM_SERIAL1 }, >- /* Dell version of the Novatel 740 */ >- { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, >- /* Option Vodafone MC3G */ >- { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, >- /* Option GlobeTrotter 3G */ >- { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, >- /* Option GlobeTrotter 3G QUAD */ >- { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, >- /* Option GlobeTrotter 3G+ */ >- { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, >- /* Option GlobeTrotter Max 3.6 */ >- { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, >- /* Huawei Mobile */ >- { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, >- { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E270 }, >+ /* Merlin */ > { USB_VENDOR_MERLIN, USB_PRODUCT_MERLIN_V620 }, > /* Qualcomm, Inc. ZTE CDMA */ > { USB_VENDOR_QUALCOMMINC, USB_PRODUCT_QUALCOMMINC_CDMA_MSM }, >+ /* Novatel */ > { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_CDMA_MODEM }, > /* Novatel Wireless Merlin ES620 */ > { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_ES620 }, >@@ -256,6 +241,8 @@ static const struct ubsa_product { > /* Novatel Wireless Merlin U740 */ > { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740 }, > { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740_2 }, >+ /* Dell version of the Novatel 740 */ >+ { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, > /* Novatel Wireless Merlin U950D */ > { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U950D }, > /* Novatel Wireless Merlin V620 */ >@@ -341,52 +328,6 @@ MODULE_DEPEND(ubsa, usb, 1, 1, 1); > MODULE_DEPEND(ubsa, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); > MODULE_VERSION(ubsa, UBSA_MODVER); > >-/* >- * Huawei Exxx radio devices have a built in flash disk which is their >- * default power up configuration. This allows the device to carry its >- * own installation software. >- * >- * Instead of following the USB spec, and create multiple configuration >- * descriptors for this, the devices expects the driver to send >- * UF_DEVICE_REMOTE_WAKEUP to endpoint 2 to reset the device, so it >- * reprobes, now with the radio exposed. >- */ >- >-static usbd_status >-ubsa_huawei(device_t self, struct usb_attach_arg *uaa) { >- usb_device_request_t req; usbd_device_handle dev; >- usb_config_descriptor_t *cdesc; >- >- if (self == NULL) >- return (UMATCH_NONE); >- if (uaa == NULL) >- return (UMATCH_NONE); >- dev = uaa->device; >- if (dev == NULL) >- return (UMATCH_NONE); >- /* get the config descriptor */ >- cdesc = usbd_get_config_descriptor(dev); >- if (cdesc == NULL) >- return (UMATCH_NONE); >- >- if (cdesc->bNumInterface > 1) >- return (0); >- >- /* Bend it like Beckham */ >- device_printf(self, "Kicking Huawei device into radio mode\n"); >- memset(&req, 0, sizeof req); >- req.bmRequestType = UT_WRITE_DEVICE; >- req.bRequest = UR_SET_FEATURE; >- USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); >- USETW(req.wIndex, 2); >- USETW(req.wLength, 0); >- >- /* We get error return, but it works */ >- (void)usbd_do_request(dev, &req, 0); >- return (UMATCH_NONE); >-} >- >- > static int > ubsa_match(device_t self) > { >@@ -399,9 +340,6 @@ ubsa_match(device_t self) > for (i = 0; ubsa_products[i].vendor != 0; i++) { > if (ubsa_products[i].vendor == uaa->vendor && > ubsa_products[i].product == uaa->product) { >- if (uaa->vendor == USB_VENDOR_HUAWEI && >- ubsa_huawei(self, uaa)) >- break; > return (UMATCH_VENDOR_PRODUCT); > } > } >@@ -424,9 +362,6 @@ ubsa_attach(device_t self) > dev = uaa->device; > ucom = &sc->sc_ucom; > >- if (uaa->vendor == USB_VENDOR_HUAWEI) >- sc->sc_huawei = 1; >- > /* > * initialize rts, dtr variables to something > * different from boolean 0, 1 >@@ -575,8 +510,6 @@ ubsa_request(struct ubsa_softc *sc, u_in > usbd_status err; > > /* The huawei Exxx devices support none of these tricks */ >- if (sc->sc_huawei) >- return (0); > req.bmRequestType = UT_WRITE_VENDOR_DEVICE; > req.bRequest = request; > USETW(req.wValue, value); > >Modified: head/sys/dev/usb/usbdevs >============================================================================== >--- head/sys/dev/usb/usbdevs Thu Oct 9 20:51:25 2008 (r183734) >+++ head/sys/dev/usb/usbdevs Thu Oct 9 21:25:01 2008 (r183735) >@@ -1434,7 +1434,7 @@ product HTC SMARTPHONE 0x0a51 SmartPhon > > /* HUAWEI products */ > product HUAWEI MOBILE 0x1001 Huawei Mobile >-product HUAWEI E270 0x1003 Huawei HSPA modem >+product HUAWEI E220 0x1003 Huawei HSDPA modem > > /* HUAWEI 3com products */ > product HUAWEI3COM WUB320G 0x0009 Aolynk WUB320g > >Modified: head/sys/i386/conf/GENERIC >============================================================================== >--- head/sys/i386/conf/GENERIC Thu Oct 9 20:51:25 2008 (r183734) >+++ head/sys/i386/conf/GENERIC Thu Oct 9 21:25:01 2008 (r183735) >@@ -304,6 +304,7 @@ device urio # Diamond >Rio 500 MP3 play > device uscanner # Scanners > # USB Serial devices > device ucom # Generic com ttys >+device u3g # USB-based 3G modems (Option, Huawei, Sierra) > device uark # Technologies ARK3116 based serial adapters > device ubsa # Belkin F5U103 and compatible > serial adapters > device uftdi # For FTDI usb serial adapters > >Modified: head/sys/modules/Makefile >============================================================================== >--- head/sys/modules/Makefile Thu Oct 9 20:51:25 2008 (r183734) >+++ head/sys/modules/Makefile Thu Oct 9 21:25:01 2008 (r183735) >@@ -269,6 +269,7 @@ SUBDIR= ${_3dfx} \ > twe \ > tx \ > txp \ >+ u3g \ > uark \ > uart \ > ubsa \ > >Added: head/sys/modules/u3g/Makefile >============================================================================== >--- /dev/null 00:00:00 1970 (empty, because file is newly added) >+++ head/sys/modules/u3g/Makefile Thu Oct 9 21:25:01 >2008 (r183735) >@@ -0,0 +1,8 @@ >+# $FreeBSD$ >+ >+.PATH: ${.CURDIR}/../../dev/usb >+ >+KMOD= u3g >+SRCS= u3g.c ucomvar.h opt_usb.h device_if.h bus_if.h usbdevs.h >+ >+.include >_______________________________________________ >svn-src-all@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/svn-src-all >To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" > >------------------------------------------------------- >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From hselasky at c2i.net Wed Nov 5 08:20:42 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 08:20:55 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <49117846.9080301@163.com> References: <200810251925.47273.hselasky@c2i.net> <200811050908.35744.hselasky@c2i.net> <49117846.9080301@163.com> Message-ID: <200811051722.44148.hselasky@c2i.net> On Wednesday 05 November 2008, kevin wrote: > Hans Petter Selasky wrote: > > On Wednesday 05 November 2008, kevin wrote: > >> Hans Petter Selasky wrote: > >>> Hi, > >>> > >>> A new USB release is available: > >>> > >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ > >>> > >>> %md5 usb2_release_003.* > >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > >>> %sha256 usb2_release_003.* > >>> SHA256 (usb2_release_003.diff) = > >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > >>> SHA256 (usb2_release_003.tar.gz) = > >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > >>> > >>> Changes since 002 release: > >> > >> I try to compile kernel with usb2. > > > > Hi, > > > > Try to load the module instead of having bluetooth in the kernel. Then > > all dependancies are loaded automatically. > > > > Depends on some bluetooth stuff. > > > > --HPS > > I build kernel without usb2_bluetooth_ng successfully. i notice that > fingerpring and bluetooth mouse nolonger work now. > in dmesg: > ugen0.2: at usbus0 > ugen0.3: at usbus0 > maybe /etc/rc.d/bthidd and fprint package need update now. > Try: kldload usb2_bluetooth_ng Or add: usb2_bluetooth_load=YES usb2_bluetooth_ng_load=YES to: /boot/loader.conf --HPS From hselasky at c2i.net Wed Nov 5 08:20:42 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 08:20:56 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <49117846.9080301@163.com> References: <200810251925.47273.hselasky@c2i.net> <200811050908.35744.hselasky@c2i.net> <49117846.9080301@163.com> Message-ID: <200811051722.44148.hselasky@c2i.net> On Wednesday 05 November 2008, kevin wrote: > Hans Petter Selasky wrote: > > On Wednesday 05 November 2008, kevin wrote: > >> Hans Petter Selasky wrote: > >>> Hi, > >>> > >>> A new USB release is available: > >>> > >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ > >>> > >>> %md5 usb2_release_003.* > >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > >>> %sha256 usb2_release_003.* > >>> SHA256 (usb2_release_003.diff) = > >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > >>> SHA256 (usb2_release_003.tar.gz) = > >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > >>> > >>> Changes since 002 release: > >> > >> I try to compile kernel with usb2. > > > > Hi, > > > > Try to load the module instead of having bluetooth in the kernel. Then > > all dependancies are loaded automatically. > > > > Depends on some bluetooth stuff. > > > > --HPS > > I build kernel without usb2_bluetooth_ng successfully. i notice that > fingerpring and bluetooth mouse nolonger work now. > in dmesg: > ugen0.2: at usbus0 > ugen0.3: at usbus0 > maybe /etc/rc.d/bthidd and fprint package need update now. > Try: kldload usb2_bluetooth_ng Or add: usb2_bluetooth_load=YES usb2_bluetooth_ng_load=YES to: /boot/loader.conf --HPS From hselasky at c2i.net Wed Nov 5 08:26:38 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 08:26:45 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <863ai6yx36.fsf@gmail.com> References: <200810251925.47273.hselasky@c2i.net> <200811051236.41450.Thomas.Sparrevohn@btinternet.com> <863ai6yx36.fsf@gmail.com> Message-ID: <200811051728.44513.hselasky@c2i.net> On Wednesday 05 November 2008, swell.k@gmail.com wrote: > Thomas Sparrevohn writes: > > On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote: > >> Hi, > >> > >> > And one last thing: > >> > # usbdevs -v > >> > usbdevs: no USB controllers found > >> > >> That command is no longer supported. Use "usbconfig" instead. I'm not > >> sure if it is currently installed by default. > >> > >> --HPS > > > > usbconfig does not install per default - it does not even seem to compile > > - > > I think this patch might be a workaround then. Hi, I will get this patch in next time an USB2 update gets committed to FreeBSD-current. Thanks! --HPS From swell.k at gmail.com Wed Nov 5 08:29:50 2008 From: swell.k at gmail.com (swell.k@gmail.com) Date: Wed Nov 5 08:29:57 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811051236.41450.Thomas.Sparrevohn@btinternet.com> (Thomas Sparrevohn's message of "Wed, 5 Nov 2008 12:36:40 +0000") References: <200810251925.47273.hselasky@c2i.net> <20081104230547.GE8256@e.0x20.net> <200811050915.54175.hselasky@c2i.net> <200811051236.41450.Thomas.Sparrevohn@btinternet.com> Message-ID: <863ai6yx36.fsf@gmail.com> Thomas Sparrevohn writes: > On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote: >> Hi, >> >> > And one last thing: >> > # usbdevs -v >> > usbdevs: no USB controllers found >> > >> >> That command is no longer supported. Use "usbconfig" instead. I'm not sure if >> it is currently installed by default. >> >> --HPS >> > > usbconfig does not install per default - it does not even seem to compile - I think this patch might be a workaround then. -------------- next part -------------- Index: share/man/man4/Makefile =================================================================== --- share/man/man4/Makefile (revision 184644) +++ share/man/man4/Makefile (working copy) @@ -416,6 +416,20 @@ ural.4 \ urio.4 \ usb.4 \ + usb2_bluetooth.4 \ + usb2_controller.4 \ + usb2_core.4 \ + usb2_ethernet.4 \ + usb2_image.4 \ + usb2_input.4 \ + usb2_misc.4 \ + usb2_ndis.4 \ + usb2_quirk.4 \ + usb2_serial.4 \ + usb2_sound.4 \ + usb2_storage.4 \ + usb2_template.4 \ + usb2_wlan.4 \ uscanner.4 \ uslcom.4 \ utopia.4 \ Index: usr.sbin/Makefile =================================================================== --- usr.sbin/Makefile (revision 184644) +++ usr.sbin/Makefile (working copy) @@ -181,6 +181,7 @@ trpt \ tzsetup \ ugidfw \ + ${_usbconfig} \ ${_usbdevs} \ ${_vidcontrol} \ vipw \ @@ -401,6 +402,7 @@ .endif .if ${MK_USB} != "no" +_usbconfig= usbconfig _usbdevs= usbdevs .endif Index: lib/Makefile =================================================================== --- lib/Makefile (revision 184644) +++ lib/Makefile (working copy) @@ -38,7 +38,8 @@ ${_libpmc} libproc librt ${_libsdp} ${_libsm} ${_libsmb} \ ${_libsmdb} \ ${_libsmutil} libstand ${_libtelnet} ${_libthr} libthread_db libufs \ - libugidfw ${_libusbhid} ${_libvgl} libwrap liby libz ${_bind} + libugidfw ${_libusb20} ${_libusbhid} ${_libvgl} libwrap liby libz \ + ${_bind} .if exists(${.CURDIR}/csu/${MACHINE_ARCH}-elf) _csu=csu/${MACHINE_ARCH}-elf @@ -135,6 +136,7 @@ .endif .if ${MK_USB} != "no" +_libusb20= libusb20 _libusbhid= libusbhid .endif Index: lib/libusb20/Makefile =================================================================== --- lib/libusb20/Makefile (revision 184644) +++ lib/libusb20/Makefile (working copy) @@ -18,7 +18,7 @@ INCS+= libusb20_compat10.h MAN= libusb20.3 MKLINT= no +CFLAGS+= -I${.CURDIR}/../../sys NOGCCERROR= .include - From mike at sentex.net Wed Nov 5 08:38:42 2008 From: mike at sentex.net (Mike Tancsa) Date: Wed Nov 5 08:38:49 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200811051706.00850.nick@van-laarhoven.org> References: <200810092344.10388.nick@van-laarhoven.org> <200811051548.mA5Fmsot040177@lava.sentex.ca> <200811051706.00850.nick@van-laarhoven.org> Message-ID: <200811051638.mA5Gcdtj040411@lava.sentex.ca> At 11:06 AM 11/5/2008, Nick Hibma wrote: > > At 04:44 PM 10/9/2008, Nick Hibma wrote: > > >Just now I have committed a driver for Option and Huawei cards > > > previously supported by the ubsa driver. More information is in the > > > commit message. > > > > > >I am looking for people who would be able to provide more information > > > after testing with the 3G cards branded by: > > > > Hi, > > I gave it a try on the Sierra USB card and it seems to work > > really well on RELENG_7! There is however also a mini-pci express > > version of the Sierra card, the MC8775. Do you have plans to add > > support for it ? I am not sure how the unit is even supposed to show > > up as I dont see it in the dmesg, but I do see that it shows some > > sort of umass device > > > > # usbdevs > > addr 1: OHCI root hub, AMD > > addr 2: USB MMC Storage, Sierra Wireless > > addr 1: EHCI root hub, AMD > >If you could run usbdevs -v and then jot down the IDs you can add those to >the top of u3g.c. You'll have to add a quirk like for other sierra devices >that show up as mass storage and need to be kicked into modem mode. > >It pretends to be a mass storage device (with drivers on it) and after >installation switches to modem mode. > >Or that's my guess. # usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), AMD(0x0000), rev 1.00 port 1 powered port 2 addr 2: full speed, power 100 mA, config 1, USB MMC Storage(0x0fff), Sierra Wireless(0x1199), rev 0.00 port 3 powered port 4 powered Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), AMD(0x0000), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered It looks like its already there in the drivers. Is it possible the mini-pci express card is conflicting with the USB of the Alix board ? ---Mike >Nick > > > dmesg snippet > > ... > > isa_probe_children: probing PnP devices > > umass0: > addr 2> on uhub0 > > umass0:0:0:-1: Attached to scbus0 > > Device configuration finished. > > procfs registered > > Timecounter "TSC" frequency 498053687 Hz quality 800 > > Timecounters tick every 1.000 msec > > crypto: > > vlan: initialized, using hash tables with chaining > > IPsec: Initialized Security Association Processing. > > pflog0: bpf attached > > lo0: bpf attached > > ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire > > ad0: setting PIO4 on CS5536 chip > > ad0: 1953MB at ata0-master PIO4 > > ad0: 4001760 sectors [3970C/16H/63S] 4 sectors/interrupt 1 depth queue > > GEOM: new disk ad0 > > pass0 at umass-sim0 bus 0 target 0 lun 0 > > pass0: Removable CD-ROM SCSI-0 device > > pass0: 1.000MB/s transfers > > Trying to mount root from ufs:/dev/ad0s1a > > start_init: trying /sbin/init > > bridge0: bpf attached > > bridge0: Ethernet address: 3a:72:35:a3:25:ce > > tun0: bpf attached > > > > Not sure why it shows up as a passthrough device ? > > > > ---Mike From hselasky at c2i.net Wed Nov 5 09:26:39 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 09:26:45 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <863ai6yx36.fsf@gmail.com> References: <200810251925.47273.hselasky@c2i.net> <200811051236.41450.Thomas.Sparrevohn@btinternet.com> <863ai6yx36.fsf@gmail.com> Message-ID: <200811051728.44513.hselasky@c2i.net> On Wednesday 05 November 2008, swell.k@gmail.com wrote: > Thomas Sparrevohn writes: > > On Wednesday 05 November 2008 08:15:52 Hans Petter Selasky wrote: > >> Hi, > >> > >> > And one last thing: > >> > # usbdevs -v > >> > usbdevs: no USB controllers found > >> > >> That command is no longer supported. Use "usbconfig" instead. I'm not > >> sure if it is currently installed by default. > >> > >> --HPS > > > > usbconfig does not install per default - it does not even seem to compile > > - > > I think this patch might be a workaround then. Hi, I will get this patch in next time an USB2 update gets committed to FreeBSD-current. Thanks! --HPS From nick at van-laarhoven.org Wed Nov 5 10:05:17 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Wed Nov 5 10:05:23 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200811051638.mA5Gcdtj040411@lava.sentex.ca> References: <200810092344.10388.nick@van-laarhoven.org> <200811051706.00850.nick@van-laarhoven.org> <200811051638.mA5Gcdtj040411@lava.sentex.ca> Message-ID: <200811051905.05294.nick@van-laarhoven.org> > >If you could run usbdevs -v and then jot down the IDs you can add those > > to the top of u3g.c. You'll have to add a quirk like for other sierra > > devices that show up as mass storage and need to be kicked into modem > > mode. > > > >It pretends to be a mass storage device (with drivers on it) and after > >installation switches to modem mode. > > > >Or that's my guess. > > # usbdevs -v > Controller /dev/usb0: > addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), > AMD(0x0000), rev 1.00 > port 1 powered > port 2 addr 2: full speed, power 100 mA, config 1, USB MMC > Storage(0x0fff), Sierra Wireless(0x1199), rev 0.00 > port 3 powered > port 4 powered > Controller /dev/usb1: > addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), > AMD(0x0000), rev 1.00 > port 1 powered > port 2 powered > port 3 powered > port 4 powered > > It looks like its already there in the drivers. Is it possible the > mini-pci express card is conflicting with the USB of the Alix board ? Well, it should change to modem mode, so perhaps the sierra_init function is not correct yet. I'll have to check that out. nick From ianf at clue.co.za Wed Nov 5 10:21:49 2008 From: ianf at clue.co.za (Ian FREISLICH) Date: Wed Nov 5 10:22:42 2008 Subject: shutdown and reboot do not work correct In-Reply-To: <4911B529.1030804@163.com> References: <4911B529.1030804@163.com> Message-ID: kevin wrote: > Hi, > I update everything this afternoon(both kernel and world). when i > try to reboot or shutdown system,i find something goes wrong.After > system output "All buffers synced" and "Accounting disabled",system does > not power off as normal. the keyboard still works and when i press the > power button ,it output "acpi: suspend request ignored (not ready yet)", > "acpi: request to enter state S5 failed (error 6)". Any one meet same > problem? I'm seeing a shutdown -p rebooting one of my machines. I haven't done any debugging. Ian -- Ian Freislich From attilio at freebsd.org Wed Nov 5 10:31:44 2008 From: attilio at freebsd.org (Attilio Rao) Date: Wed Nov 5 10:32:14 2008 Subject: shutdown and reboot do not work correct In-Reply-To: <4911B529.1030804@163.com> References: <4911B529.1030804@163.com> Message-ID: <3bbf2fe10811051031j25ed35e8r78dd5f21e3551579@mail.gmail.com> 2008/11/5, kevin : > Hi, > I update everything this afternoon(both kernel and world). when i try to > reboot or shutdown system,i find something goes wrong.After system output > "All buffers synced" and "Accounting disabled",system does not power off as > normal. the keyboard still works and when i press the power button ,it > output "acpi: suspend request ignored (not ready yet)", "acpi: request to > enter state S5 failed (error 6)". Any one meet same problem? Could you please break into DDB and see where it is hanging? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From jhb at freebsd.org Wed Nov 5 13:00:54 2008 From: jhb at freebsd.org (John Baldwin) Date: Wed Nov 5 13:01:07 2008 Subject: panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 In-Reply-To: References: Message-ID: <200811051141.27965.jhb@freebsd.org> On Wednesday 05 November 2008 07:34:56 am Pawel Worach wrote: > Hi, > > Got the following panic after I built some ports with > WRKDIRPREFIX=/tmp/work where /tmp is tmpfs. > > FreeBSD one 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r184639M: Tue Nov 4 > 18:39:44 CET 2008 root@one:/usr/obj/usr/src/sys/IBMT61 amd64 > > panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 > > Unread portion of the kernel message buffer: > panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x17d > tmpfs_alloc_vp() at tmpfs_alloc_vp+0x255 > tmpfs_lookup() at tmpfs_lookup+0x17a > vfs_cache_lookup() at vfs_cache_lookup+0xda I'm guessing the parent node of a file got free'd (maybe a missing refcount?) and that tn_parent is a stale pointer. Not sure how that would have happened though. Might be worth looking at the node passed to tmpfs_alloc_vp(). -- John Baldwin From jhb at freebsd.org Wed Nov 5 13:00:54 2008 From: jhb at freebsd.org (John Baldwin) Date: Wed Nov 5 13:01:08 2008 Subject: panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 In-Reply-To: References: Message-ID: <200811051141.27965.jhb@freebsd.org> On Wednesday 05 November 2008 07:34:56 am Pawel Worach wrote: > Hi, > > Got the following panic after I built some ports with > WRKDIRPREFIX=/tmp/work where /tmp is tmpfs. > > FreeBSD one 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r184639M: Tue Nov 4 > 18:39:44 CET 2008 root@one:/usr/obj/usr/src/sys/IBMT61 amd64 > > panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 > > Unread portion of the kernel message buffer: > panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x17d > tmpfs_alloc_vp() at tmpfs_alloc_vp+0x255 > tmpfs_lookup() at tmpfs_lookup+0x17a > vfs_cache_lookup() at vfs_cache_lookup+0xda I'm guessing the parent node of a file got free'd (maybe a missing refcount?) and that tn_parent is a stale pointer. Not sure how that would have happened though. Might be worth looking at the node passed to tmpfs_alloc_vp(). -- John Baldwin From trebestie at gmail.com Wed Nov 5 16:38:42 2008 From: trebestie at gmail.com (Diego Depaoli) Date: Wed Nov 5 16:39:12 2008 Subject: Usb2 and hal issue Message-ID: <83e5fb980811051638n5f9a1a5dr60160ed7e2ed7a1c@mail.gmail.com> Hi all, I don't know how provide further details, but on my system there is something of wrong between new usb2 drivers and hald. Top shows hald's cpu load at 100% while with old drivers it's 2-4%. I tried rebuilding hald, loading/unloading each usb2_* device but nothing changed, so I suspect the problem is located in usb2_core. -- Diego Depaoli From kevinxlinuz at 163.com Wed Nov 5 18:19:15 2008 From: kevinxlinuz at 163.com (kevin) Date: Wed Nov 5 18:19:24 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811051722.44148.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <200811050908.35744.hselasky@c2i.net> <49117846.9080301@163.com> <200811051722.44148.hselasky@c2i.net> Message-ID: <49125418.4040008@163.com> Hans Petter Selasky wrote: > On Wednesday 05 November 2008, kevin wrote: > >> Hans Petter Selasky wrote: >> >>> On Wednesday 05 November 2008, kevin wrote: >>> >>>> Hans Petter Selasky wrote: >>>> >>>>> Hi, >>>>> >>>>> A new USB release is available: >>>>> >>>>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ >>>>> >>>>> %md5 usb2_release_003.* >>>>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 >>>>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf >>>>> %sha256 usb2_release_003.* >>>>> SHA256 (usb2_release_003.diff) = >>>>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b >>>>> SHA256 (usb2_release_003.tar.gz) = >>>>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 >>>>> >>>>> Changes since 002 release: >>>>> >>>> I try to compile kernel with usb2. >>>> >>> Hi, >>> >>> Try to load the module instead of having bluetooth in the kernel. Then >>> all dependancies are loaded automatically. >>> >>> Depends on some bluetooth stuff. >>> >>> --HPS >>> >> I build kernel without usb2_bluetooth_ng successfully. i notice that >> fingerpring and bluetooth mouse nolonger work now. >> in dmesg: >> ugen0.2: at usbus0 >> ugen0.3: at usbus0 >> maybe /etc/rc.d/bthidd and fprint package need update now. >> >> > > Try: > > kldload usb2_bluetooth_ng > > > Or add: > > usb2_bluetooth_load=YES > usb2_bluetooth_ng_load=YES > > to: /boot/loader.conf > usb2_bluetooth was built into kernel already,and usb2_bluetooth_ng was included in ng_ubt. in /boot/loader.conf ng_ubt_load=YES usb2_bluetooth_fw_load=YES ubtbcmfw=YES Thanks, kevin From hselasky at c2i.net Wed Nov 5 23:58:57 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Nov 5 23:59:04 2008 Subject: Usb2 and hal issue In-Reply-To: <83e5fb980811051638n5f9a1a5dr60160ed7e2ed7a1c@mail.gmail.com> References: <83e5fb980811051638n5f9a1a5dr60160ed7e2ed7a1c@mail.gmail.com> Message-ID: <200811060900.59772.hselasky@c2i.net> On Thursday 06 November 2008, Diego Depaoli wrote: > Hi all, > I don't know how provide further details, but on my system there is > something of wrong between new usb2 drivers and hald. > Top shows hald's cpu load at 100% while with old drivers it's 2-4%. > I tried rebuilding hald, loading/unloading each usb2_* device but > nothing changed, so I suspect the problem is located in usb2_core. Hi, Hald is looping trying to open the wrong USB device. If hald is using libusb-0.1.12, you could try building and installing libusb20, most easily done from my private SVN repository, and then link hald with -lusb20 --HPS From alfred at freebsd.org Thu Nov 6 02:04:56 2008 From: alfred at freebsd.org (Alfred Perlstein) Date: Thu Nov 6 02:05:03 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811051728.44513.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <200811051236.41450.Thomas.Sparrevohn@btinternet.com> <863ai6yx36.fsf@gmail.com> <200811051728.44513.hselasky@c2i.net> Message-ID: <20081106100456.GF60438@elvis.mu.org> * Hans Petter Selasky [081105 08:26] wrote: > > Hi, > > I will get this patch in next time an USB2 update gets committed to > FreeBSD-current. Hey Hans, can you look into using svk for your repository? I think it will make commits to svn easier for both of us. Easier for me to pull your changes and easier for you to track changes in FreeBSD... ? -Alfred From alfred at freebsd.org Thu Nov 6 02:17:24 2008 From: alfred at freebsd.org (Alfred Perlstein) Date: Thu Nov 6 02:17:36 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811051728.44513.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <200811051236.41450.Thomas.Sparrevohn@btinternet.com> <863ai6yx36.fsf@gmail.com> <200811051728.44513.hselasky@c2i.net> Message-ID: <20081106100456.GF60438@elvis.mu.org> * Hans Petter Selasky [081105 08:26] wrote: > > Hi, > > I will get this patch in next time an USB2 update gets committed to > FreeBSD-current. Hey Hans, can you look into using svk for your repository? I think it will make commits to svn easier for both of us. Easier for me to pull your changes and easier for you to track changes in FreeBSD... ? -Alfred From bruce at cran.org.uk Thu Nov 6 05:04:32 2008 From: bruce at cran.org.uk (Bruce Cran) Date: Thu Nov 6 05:04:45 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811051722.44148.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <200811050908.35744.hselasky@c2i.net> <49117846.9080301@163.com> <200811051722.44148.hselasky@c2i.net> Message-ID: <20081106050416.09944ea2@tau.draftnet> On Wed, 5 Nov 2008 17:22:43 +0100 Hans Petter Selasky wrote: > On Wednesday 05 November 2008, kevin wrote: > > Hans Petter Selasky wrote: > > > On Wednesday 05 November 2008, kevin wrote: > > >> Hans Petter Selasky wrote: > > >>> Hi, > > >>> > > >>> A new USB release is available: > > >>> > > >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ > > >>> > > >>> %md5 usb2_release_003.* > > >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > > >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > > >>> %sha256 usb2_release_003.* > > >>> SHA256 (usb2_release_003.diff) = > > >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > > >>> SHA256 (usb2_release_003.tar.gz) = > > >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > > >>> > > >>> Changes since 002 release: > > >> > > >> I try to compile kernel with usb2. > > > > > > Hi, > > > > > > Try to load the module instead of having bluetooth in the kernel. > > > Then all dependancies are loaded automatically. > > > > > > Depends on some bluetooth stuff. > > > > > > --HPS > > > > I build kernel without usb2_bluetooth_ng successfully. i notice that > > fingerpring and bluetooth mouse nolonger work now. > > in dmesg: > > ugen0.2: at usbus0 > > ugen0.3: at usbus0 > > maybe /etc/rc.d/bthidd and fprint package need update now. > > > > Try: > > kldload usb2_bluetooth_ng I don't know if this is a problem in general, but I can't load usb2_serial_modem and have usb2_serial load automatically: > kldload usb2_serial_modem interface ucom.1 already present in the KLD 'ucom.ko'! kldload: /boot/kernel/usb2_serial.ko: Unsupported file type KLD usb2_serial_modem.ko: depends on usb2_serial - not available kldload: /boot/kernel/usb2_serial_modem.ko: Unsupported file type kldload'ing usb2_serial followed by usb2_serial_modem works though. -- Bruce Cran From bruce at cran.org.uk Thu Nov 6 05:04:32 2008 From: bruce at cran.org.uk (Bruce Cran) Date: Thu Nov 6 05:04:45 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811051722.44148.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <200811050908.35744.hselasky@c2i.net> <49117846.9080301@163.com> <200811051722.44148.hselasky@c2i.net> Message-ID: <20081106050416.09944ea2@tau.draftnet> On Wed, 5 Nov 2008 17:22:43 +0100 Hans Petter Selasky wrote: > On Wednesday 05 November 2008, kevin wrote: > > Hans Petter Selasky wrote: > > > On Wednesday 05 November 2008, kevin wrote: > > >> Hans Petter Selasky wrote: > > >>> Hi, > > >>> > > >>> A new USB release is available: > > >>> > > >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ > > >>> > > >>> %md5 usb2_release_003.* > > >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > > >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > > >>> %sha256 usb2_release_003.* > > >>> SHA256 (usb2_release_003.diff) = > > >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > > >>> SHA256 (usb2_release_003.tar.gz) = > > >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > > >>> > > >>> Changes since 002 release: > > >> > > >> I try to compile kernel with usb2. > > > > > > Hi, > > > > > > Try to load the module instead of having bluetooth in the kernel. > > > Then all dependancies are loaded automatically. > > > > > > Depends on some bluetooth stuff. > > > > > > --HPS > > > > I build kernel without usb2_bluetooth_ng successfully. i notice that > > fingerpring and bluetooth mouse nolonger work now. > > in dmesg: > > ugen0.2: at usbus0 > > ugen0.3: at usbus0 > > maybe /etc/rc.d/bthidd and fprint package need update now. > > > > Try: > > kldload usb2_bluetooth_ng I don't know if this is a problem in general, but I can't load usb2_serial_modem and have usb2_serial load automatically: > kldload usb2_serial_modem interface ucom.1 already present in the KLD 'ucom.ko'! kldload: /boot/kernel/usb2_serial.ko: Unsupported file type KLD usb2_serial_modem.ko: depends on usb2_serial - not available kldload: /boot/kernel/usb2_serial_modem.ko: Unsupported file type kldload'ing usb2_serial followed by usb2_serial_modem works though. -- Bruce Cran From shuvaev at physik.uni-wuerzburg.de Thu Nov 6 06:13:27 2008 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Thu Nov 6 06:13:34 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081106050416.09944ea2@tau.draftnet> References: <200810251925.47273.hselasky@c2i.net> <200811050908.35744.hselasky@c2i.net> <49117846.9080301@163.com> <200811051722.44148.hselasky@c2i.net> <20081106050416.09944ea2@tau.draftnet> Message-ID: <20081106141323.GA4489@wep4035.physik.uni-wuerzburg.de> On Thu, Nov 06, 2008 at 05:04:16AM -0800, Bruce Cran wrote: > > I don't know if this is a problem in general, but I can't load > usb2_serial_modem and have usb2_serial load automatically: > > > kldload usb2_serial_modem > interface ucom.1 already present in the KLD 'ucom.ko'! ^^^^^^^ I think it is a module from the old usb stack. > kldload: /boot/kernel/usb2_serial.ko: Unsupported file type > KLD usb2_serial_modem.ko: depends on usb2_serial - not available > kldload: /boot/kernel/usb2_serial_modem.ko: Unsupported file type > > kldload'ing usb2_serial followed by usb2_serial_modem works though. > I also see automatic loading of the old stack modules, for example (entries 17, 18): [wep4035] ~> kldstat Id Refs Address Size Name 1 55 0xffffffff80100000 8daac8 kernel (/boot/kernel/kernel) 2 1 0xffffffff809db000 21ed8 snd_hda.ko (/boot/kernel/snd_hda.ko) 3 2 0xffffffff809fd000 749c8 sound.ko (/boot/kernel/sound.ko) 4 1 0xffffffff80a72000 3090 speaker.ko (/boot/kernel/speaker.ko) 5 1 0xffffffff80a76000 59e8 ichsmb.ko (/boot/kernel/ichsmb.ko) 6 2 0xffffffff80a7c000 2440 smbus.ko (/boot/kernel/smbus.ko) 7 1 0xffffffff80a7f000 fa10 i915.ko (/boot/kernel/i915.ko) 8 2 0xffffffff80a8f000 21c48 drm.ko (/boot/kernel/drm.ko) 9 1 0xffffffff80ab1000 e648 usb2_controller_uhci.ko (/boot/kernel/usb2_controller_uhci.ko) 10 3 0xffffffff80ac0000 5168 usb2_controller.ko (/boot/kernel/usb2_controller.ko) 11 8 0xffffffff80ac6000 5c548 usb2_core.ko (/boot/kernel/usb2_core.ko) 12 1 0xffffffff80b23000 125a0 usb2_controller_ehci.ko (/boot/kernel/usb2_controller_ehci.ko) 13 1 0xffffffff80b36000 4e48 usb2_input_ms.ko (/boot/kernel/usb2_input_ms.ko) 14 2 0xffffffff80b3b000 560 usb2_input.ko (/boot/kernel/usb2_input.ko) 15 1 0xffffffff80b3c000 ff08 usb2_storage_mass.ko (/boot/kernel/usb2_storage_mass.ko) 16 2 0xffffffff80b4c000 570 usb2_storage.ko (/boot/kernel/usb2_storage.ko) 17 1 0xffffffff80c22000 18c7 ums.ko (/boot/kernel/ums.ko) 18 1 0xffffffff80c24000 9612 usb.ko (/boot/kernel/usb.ko) 19 1 0xffffffff80c2e000 216 green_saver.ko (/boot/kernel/green_saver.ko) Simple kldunload-ing of ums.ko unloads usb.ko also. I am having quite reliable panics with the new stack when I insert usb stick (actually during the first access to it). Trying to collect more information I haven't managed to produce memory dump. Is it working on amd64 SMP CURRENT? I remember there were some complains about it. I will report details of the panic when I get them. Alexey. From lars.engels at 0x20.net Thu Nov 6 06:31:01 2008 From: lars.engels at 0x20.net (Lars Engels) Date: Thu Nov 6 06:31:19 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <48DEA8E7.2080503@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> Message-ID: <20081106153059.1sf731434swc84so@0x20.net> Quoting Alexander Motin : > Hi. > > I would like to present initial revision of my generic PCI SD Host > Controller driver (sdhci). It support PCI devices with class 8 and > subclass 5 according to SD Host Controller Specification. With some > limitations it successfully works on my Acer TM6292 notebook with ENE > CB714 card reader. > > Things that are working now: > - PIO mode single and multiple block read and write, > - 1 and 4 bits bus width support. > > In PIO mode with 4GB SD card on 30MHz 4bit bus I have reached about > 3.5MB/s (limited by CPU) linear read and 7MB/s (limited by card) linear > write. Small blocks read/write performance limited by card. > > Things that are not working yet: > - DMA modes (code is written, but as my controller looks like has > broken DMA I have no ability to debug it), > - card insert/remove detection (need more thinking), you should reload > mmc module to rescan cards, > - SDHC and MMC cards (have no such cards now to debug that code), only > standard capacity SD Memory cards up to 4GB size are supported now, > - high speed (double rate) bus mode (need more thinking and DMA support). > > Also to get such results I have improved existing mmc and mmcsd drivers > a bit. mmc driver got: > - 4 bit bus width support, > - write protection switch support, > - cards with more then 2GB capacity support. > mmcsd driver got: > - multiple block read and write support, > - cards with more then 2GB capacity support, > - I/O error reporting, > - write protection switch support. > > Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found at: > http://people.freebsd.org/~mav/sdhci/ > > I will be grateful for any feedbacks, comments and support. Hi Alexander, I just tried your latest version of mmc + sdhci but it does not detect any SD Card inserted: sdhci0: mem 0xe4003000-0xe40030ff irq 19 at device 6.3 on pci2 sdhci0: slot 0 uses DMA sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000400 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000000 sdhci0-slot0: Present: 0x01f20000 | Host ctl: 0x00000000 sdhci0-slot0: Power: 0x00000000 | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000000 sdhci0-slot0: Timeout: 0x00000000 | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x018021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] sdhci0: detached sdhci0: mem 0xe4003000-0xe40030ff irq 19 at device 6.3 on pci2 sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] Nothing happens when I insert a card. The hardware is: sdhci0@pci0:2:6:3: class=0x080500 card=0x30c3103c chip=0x08221180 rev=0x20 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'R5C832, R5C843 SDA Standard Compliant SD Host Controller' class = base peripheral none2@pci0:2:6:4: class=0x088000 card=0x30c3103c chip=0x08431180 rev=0x10 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh MMC Host Controller' class = base peripheral none3@pci0:2:6:5: class=0x088000 card=0x30c3103c chip=0x05921180 rev=0x10 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = '13871043 Ricoh Memory Stick Host Controller' class = base peripheral none4@pci0:2:6:6: class=0x088000 card=0x30c3103c chip=0x08521180 rev=0x10 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh xD-Picture Card Host Controller' class = base peripheral Lars -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Digitale PGP-Unterschrift Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/e5271a5d/attachment.pgp From mav at FreeBSD.org Thu Nov 6 07:11:23 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Nov 6 07:11:41 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106153059.1sf731434swc84so@0x20.net> References: <48DEA8E7.2080503@FreeBSD.org> <20081106153059.1sf731434swc84so@0x20.net> Message-ID: <49130918.5030904@FreeBSD.org> Lars Engels wrote: > I just tried your latest version of mmc + sdhci but it does not detect > any SD Card inserted: > > sdhci0: mem 0xe4003000-0xe40030ff irq 19 at device 6.3 > on pci2 > > Nothing happens when I insert a card. > > The hardware is: > sdhci0@pci0:2:6:3: class=0x080500 card=0x30c3103c chip=0x08221180 > rev=0x20 hdr=0x00 > vendor = 'Ricoh Company, Ltd.' > device = 'R5C832, R5C843 SDA Standard Compliant SD Host Controller' > class = base peripheral > none2@pci0:2:6:4: class=0x088000 card=0x30c3103c chip=0x08431180 > rev=0x10 hdr=0x00 > vendor = 'Ricoh Company, Ltd.' > device = 'unknown Ricoh MMC Host Controller' > class = base peripheral > none3@pci0:2:6:5: class=0x088000 card=0x30c3103c chip=0x05921180 > rev=0x10 hdr=0x00 > vendor = 'Ricoh Company, Ltd.' > device = '13871043 Ricoh Memory Stick Host Controller' > class = base peripheral > none4@pci0:2:6:6: class=0x088000 card=0x30c3103c chip=0x08521180 > rev=0x10 hdr=0x00 > vendor = 'Ricoh Company, Ltd.' > device = 'unknown Ricoh xD-Picture Card Host Controller' > class = base peripheral Looks like there is two MMC/SD controllers (first two devices) in your chip while only one is detected as SD host controller. This thread looks related to your problem: http://list.drzeus.cx/pipermail/sdhci-devel/2007-September/002023.html 1. You may try to tune PCI configuration registers referred in that post. 2. Or (just an idea) you may try to power down unsupported devices with setting hw.pci.do_power_nodriver=3 into the device.hints. 3. Or (it works fine for my ENE CB714 chip) you may try to add 0x08431180 chip ID into the list of supported SD controllers like it is done for 0x08221180. They may be compatible enough. If you try it, report please about results. -- Alexander Motin From lars.engels at 0x20.net Thu Nov 6 07:37:31 2008 From: lars.engels at 0x20.net (Lars Engels) Date: Thu Nov 6 07:37:43 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <49130918.5030904@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> <20081106153059.1sf731434swc84so@0x20.net> <49130918.5030904@FreeBSD.org> Message-ID: <20081106163729.clcw2eulgk0k4w0c@0x20.net> Quoting Alexander Motin : > Lars Engels wrote: >> I just tried your latest version of mmc + sdhci but it does not detect >> any SD Card inserted: >> >> sdhci0: mem 0xe4003000-0xe40030ff irq 19 at device 6.3 >> on pci2 >> >> Nothing happens when I insert a card. >> >> The hardware is: >> sdhci0@pci0:2:6:3: class=0x080500 card=0x30c3103c chip=0x08221180 >> rev=0x20 hdr=0x00 >> vendor = 'Ricoh Company, Ltd.' >> device = 'R5C832, R5C843 SDA Standard Compliant SD Host Controller' >> class = base peripheral >> none2@pci0:2:6:4: class=0x088000 card=0x30c3103c chip=0x08431180 >> rev=0x10 hdr=0x00 >> vendor = 'Ricoh Company, Ltd.' >> device = 'unknown Ricoh MMC Host Controller' >> class = base peripheral >> none3@pci0:2:6:5: class=0x088000 card=0x30c3103c chip=0x05921180 >> rev=0x10 hdr=0x00 >> vendor = 'Ricoh Company, Ltd.' >> device = '13871043 Ricoh Memory Stick Host Controller' >> class = base peripheral >> none4@pci0:2:6:6: class=0x088000 card=0x30c3103c chip=0x08521180 >> rev=0x10 hdr=0x00 >> vendor = 'Ricoh Company, Ltd.' >> device = 'unknown Ricoh xD-Picture Card Host Controller' >> class = base peripheral > > Looks like there is two MMC/SD controllers (first two devices) in your > chip while only one is detected as SD host controller. This thread looks > related to your problem: > http://list.drzeus.cx/pipermail/sdhci-devel/2007-September/002023.html > > 1. You may try to tune PCI configuration registers referred in that post. > 2. Or (just an idea) you may try to power down unsupported devices with > setting hw.pci.do_power_nodriver=3 into the device.hints. > 3. Or (it works fine for my ENE CB714 chip) you may try to add > 0x08431180 chip ID into the list of supported SD controllers like it is > done for 0x08221180. They may be compatible enough. > > If you try it, report please about results. Alexander, thanks for the quick response! 1. How can I tune the PCI configuration? With pciconf -w or so? 2. Unfortunately the sysctl did not change a thing with regard to the Card reader. 3. I added the chip ID and the second device is now recognized as a sdhci device but still does not see any card inserted: Nov 6 16:32:20 NB0117232 kernel: sdhci0: mem 0xe4003000-0xe40030ff irq 19 at device 6.3 on pci2 Nov 6 16:32:20 NB0117232 kernel: sdhci0: 1 slot(s) allocated Nov 6 16:32:20 NB0117232 kernel: sdhci0: [ITHREAD] Nov 6 16:32:20 NB0117232 kernel: sdhci1: mem 0xe4004000-0xe40040ff irq 19 at device 6.4 on pci2 Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify base clock frequency. Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify timeout clock frequency. Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't report any support voltages. Nov 6 16:32:20 NB0117232 kernel: sdhci1: 1 slot(s) allocated Nov 6 16:32:20 NB0117232 kernel: sdhci1: [ITHREAD] Nov 6 16:32:31 NB0117232 kernel: mmc0: on sdhci1 sdhci1@pci0:2:6:4: class=0x088000 card=0x30c3103c chip=0x08431180 rev=0x10 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh MMC Host Controller' class = base peripheral -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Digitale PGP-Unterschrift Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/c845b6a5/attachment.pgp From mav at FreeBSD.org Thu Nov 6 07:45:17 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Nov 6 07:45:24 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106163729.clcw2eulgk0k4w0c@0x20.net> References: <48DEA8E7.2080503@FreeBSD.org> <20081106153059.1sf731434swc84so@0x20.net> <49130918.5030904@FreeBSD.org> <20081106163729.clcw2eulgk0k4w0c@0x20.net> Message-ID: <49131109.2020601@FreeBSD.org> Lars Engels wrote: > 1. How can I tune the PCI configuration? With pciconf -w or so? Yes. `pciconf -r -b device addr` to read and `pciconf -w -b device addr value` to write. > 2. Unfortunately the sysctl did not change a thing with regard to the > Card reader. Have you added it to the loader.conf and rebooted? > 3. I added the chip ID and the second device is now recognized as a > sdhci device but still does not see any card inserted: > > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify base > clock frequency. > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify > timeout clock frequency. > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't report any > support voltages. Looks like it is not enough compatible, or even not compatible. -- Alexander Motin From bz at FreeBSD.org Thu Nov 6 08:15:17 2008 From: bz at FreeBSD.org (Bjoern A. Zeeb) Date: Thu Nov 6 08:15:23 2008 Subject: Kernel without INET Message-ID: <20081106153035.R16105@maildrop.int.zabbadoz.net> Hi, some might have wondered about lots of small commits I have done the last two days. I had been trying to compile a kernel without any networking a few weeks ago and that failed; I had needed to add (I think it was) INET, ether and loop. So I had been trying to get rid of that requirement the last days. As a partial victory it seems to be possible again to build a kernel without any networking now. I'll have to check with my original setup but I have a stripped down LINT file I tested with. Obviously the long term goal is to be able to build a kernel without INET support (again?). As an intermediate step that will mean without INET and INET6 and once that works and IPX only would compile *cough*, then work on a (LINT) kernel with nooption INET. It'll be a long long way to go and this is nothing to finish within a week or two. Do not think about doing a quick sweep over the rest of the tree. You would wonder what depends on INET these days. I have more patches mailed out or pending here. While we had been trying to make it possible to build without INET6 most of the time, someone doing review on my code told me that if compaining about 'kernel needs INET' I should put some code under #ifdef INET. I did. The bottom line is that I now ask you to consider this for all new code as well. I am very well aware that some code, as is, would already require a maze of #ifdefs (I have a sample of that) so we need to be careful and apply the checks sensibly. Regards, Bjoern PS: please obey Reply-To: -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. From lars.engels at 0x20.net Thu Nov 6 08:25:17 2008 From: lars.engels at 0x20.net (Lars Engels) Date: Thu Nov 6 08:25:45 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <49131109.2020601@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> <20081106153059.1sf731434swc84so@0x20.net> <49130918.5030904@FreeBSD.org> <20081106163729.clcw2eulgk0k4w0c@0x20.net> <49131109.2020601@FreeBSD.org> Message-ID: <20081106172514.jbrq7aa8g0cowk4k@0x20.net> Quoting Alexander Motin : > Lars Engels wrote: >> 1. How can I tune the PCI configuration? With pciconf -w or so? > > Yes. `pciconf -r -b device addr` to read and `pciconf -w -b device addr > value` to write. Okay, so do you think I need to take the device of the first sdhci device or firewire's device like in the thread you mentioned? I should then set the value to 0x20 I guess? Which address do I need to use? FYI here is the pciconf -lv output with firewire and sdhci: fwohci0@pci0:2:6:2: class=0x0c0010 card=0x30c3103c chip=0x08321180 rev=0x03 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown IEEE 1394 (4 pin firewire) chip)' class = serial bus subclass = FireWire sdhci0@pci0:2:6:3: class=0x080500 card=0x30c3103c chip=0x08221180 rev=0x20 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'R5C832, R5C843 SDA Standard Compliant SD Host Controller' class = base peripheral none2@pci0:2:6:4: class=0x088000 card=0x30c3103c chip=0x08431180 rev=0x10 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh MMC Host Controller' class = base peripheral >> 2. Unfortunately the sysctl did not change a thing with regard to the >> Card reader. > > Have you added it to the loader.conf and rebooted? Yes, but without result. >> 3. I added the chip ID and the second device is now recognized as a >> sdhci device but still does not see any card inserted: >> >> Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify base >> clock frequency. >> Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify >> timeout clock frequency. >> Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't report any >> support voltages. > > Looks like it is not enough compatible, or even not compatible. Too bad... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Digitale PGP-Unterschrift Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/485ce2f0/attachment.pgp From hselasky at c2i.net Thu Nov 6 09:09:58 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Nov 6 09:10:16 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081106050416.09944ea2@tau.draftnet> References: <200810251925.47273.hselasky@c2i.net> <200811051722.44148.hselasky@c2i.net> <20081106050416.09944ea2@tau.draftnet> Message-ID: <200811061812.04449.hselasky@c2i.net> On Thursday 06 November 2008, Bruce Cran wrote: > On Wed, 5 Nov 2008 17:22:43 +0100 > > Hans Petter Selasky wrote: > > On Wednesday 05 November 2008, kevin wrote: > > > Hans Petter Selasky wrote: > > > > On Wednesday 05 November 2008, kevin wrote: > > > >> Hans Petter Selasky wrote: > > > >>> Hi, > > > >>> > > > >>> A new USB release is available: > > > >>> > > > >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ > > > >>> > > > >>> %md5 usb2_release_003.* > > > >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > > > >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > > > >>> %sha256 usb2_release_003.* > > > >>> SHA256 (usb2_release_003.diff) = > > > >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > > > >>> SHA256 (usb2_release_003.tar.gz) = > > > >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > > > >>> > > > >>> Changes since 002 release: > > > >> > > > >> I try to compile kernel with usb2. > > > > > > > > Hi, > > > > > > > > Try to load the module instead of having bluetooth in the kernel. > > > > Then all dependancies are loaded automatically. > > > > > > > > Depends on some bluetooth stuff. > > > > > > > > --HPS > > > > > > I build kernel without usb2_bluetooth_ng successfully. i notice that > > > fingerpring and bluetooth mouse nolonger work now. > > > in dmesg: > > > ugen0.2: at usbus0 > > > ugen0.3: at usbus0 > > > maybe /etc/rc.d/bthidd and fprint package need update now. > > > > Try: > > > > kldload usb2_bluetooth_ng > > I don't know if this is a problem in general, but I can't load > > usb2_serial_modem and have usb2_serial load automatically: > > kldload usb2_serial_modem > > interface ucom.1 already present in the KLD 'ucom.ko'! > kldload: /boot/kernel/usb2_serial.ko: Unsupported file type > KLD usb2_serial_modem.ko: depends on usb2_serial - not available > kldload: /boot/kernel/usb2_serial_modem.ko: Unsupported file type > > kldload'ing usb2_serial followed by usb2_serial_modem works though. Hi, Fixed in the following commit: http://perforce.freebsd.org/chv.cgi?CH=152584 Thanks again for your reporting. --HPS From hselasky at c2i.net Thu Nov 6 09:09:58 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Nov 6 09:10:16 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081106050416.09944ea2@tau.draftnet> References: <200810251925.47273.hselasky@c2i.net> <200811051722.44148.hselasky@c2i.net> <20081106050416.09944ea2@tau.draftnet> Message-ID: <200811061812.04449.hselasky@c2i.net> On Thursday 06 November 2008, Bruce Cran wrote: > On Wed, 5 Nov 2008 17:22:43 +0100 > > Hans Petter Selasky wrote: > > On Wednesday 05 November 2008, kevin wrote: > > > Hans Petter Selasky wrote: > > > > On Wednesday 05 November 2008, kevin wrote: > > > >> Hans Petter Selasky wrote: > > > >>> Hi, > > > >>> > > > >>> A new USB release is available: > > > >>> > > > >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ > > > >>> > > > >>> %md5 usb2_release_003.* > > > >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 > > > >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf > > > >>> %sha256 usb2_release_003.* > > > >>> SHA256 (usb2_release_003.diff) = > > > >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b > > > >>> SHA256 (usb2_release_003.tar.gz) = > > > >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 > > > >>> > > > >>> Changes since 002 release: > > > >> > > > >> I try to compile kernel with usb2. > > > > > > > > Hi, > > > > > > > > Try to load the module instead of having bluetooth in the kernel. > > > > Then all dependancies are loaded automatically. > > > > > > > > Depends on some bluetooth stuff. > > > > > > > > --HPS > > > > > > I build kernel without usb2_bluetooth_ng successfully. i notice that > > > fingerpring and bluetooth mouse nolonger work now. > > > in dmesg: > > > ugen0.2: at usbus0 > > > ugen0.3: at usbus0 > > > maybe /etc/rc.d/bthidd and fprint package need update now. > > > > Try: > > > > kldload usb2_bluetooth_ng > > I don't know if this is a problem in general, but I can't load > > usb2_serial_modem and have usb2_serial load automatically: > > kldload usb2_serial_modem > > interface ucom.1 already present in the KLD 'ucom.ko'! > kldload: /boot/kernel/usb2_serial.ko: Unsupported file type > KLD usb2_serial_modem.ko: depends on usb2_serial - not available > kldload: /boot/kernel/usb2_serial_modem.ko: Unsupported file type > > kldload'ing usb2_serial followed by usb2_serial_modem works though. Hi, Fixed in the following commit: http://perforce.freebsd.org/chv.cgi?CH=152584 Thanks again for your reporting. --HPS From imp at bsdimp.com Thu Nov 6 09:12:11 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Nov 6 09:12:19 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <49131109.2020601@FreeBSD.org> References: <49130918.5030904@FreeBSD.org> <20081106163729.clcw2eulgk0k4w0c@0x20.net> <49131109.2020601@FreeBSD.org> Message-ID: <20081106.101047.163264510.imp@bsdimp.com> In message: <49131109.2020601@FreeBSD.org> Alexander Motin writes: : Lars Engels wrote: : > 1. How can I tune the PCI configuration? With pciconf -w or so? : : Yes. `pciconf -r -b device addr` to read and `pciconf -w -b device addr : value` to write. I have changes that almost make my TI card do it. : > 2. Unfortunately the sysctl did not change a thing with regard to the : > Card reader. : : Have you added it to the loader.conf and rebooted? : : > 3. I added the chip ID and the second device is now recognized as a : > sdhci device but still does not see any card inserted: : > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify base : > clock frequency. : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify : > timeout clock frequency. : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't report any : > support voltages. : : Looks like it is not enough compatible, or even not compatible. Chances are good that you need to the workaround to turn on these things. Warner From hselasky at c2i.net Thu Nov 6 09:14:26 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Nov 6 09:14:33 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081106100456.GF60438@elvis.mu.org> References: <200810251925.47273.hselasky@c2i.net> <200811051728.44513.hselasky@c2i.net> <20081106100456.GF60438@elvis.mu.org> Message-ID: <200811061816.27429.hselasky@c2i.net> On Thursday 06 November 2008, Alfred Perlstein wrote: > * Hans Petter Selasky [081105 08:26] wrote: > > Hi, > > > > I will get this patch in next time an USB2 update gets committed to > > FreeBSD-current. > > Hey Hans, can you look into using svk for your repository? I think > it will make commits to svn easier for both of us. Easier for > me to pull your changes and easier for you to track changes > in FreeBSD... ? > Yes, I will try to set it up later today. Should we retire the USB P4 repository then ? --HPS From hselasky at c2i.net Thu Nov 6 09:14:26 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Nov 6 09:14:45 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081106100456.GF60438@elvis.mu.org> References: <200810251925.47273.hselasky@c2i.net> <200811051728.44513.hselasky@c2i.net> <20081106100456.GF60438@elvis.mu.org> Message-ID: <200811061816.27429.hselasky@c2i.net> On Thursday 06 November 2008, Alfred Perlstein wrote: > * Hans Petter Selasky [081105 08:26] wrote: > > Hi, > > > > I will get this patch in next time an USB2 update gets committed to > > FreeBSD-current. > > Hey Hans, can you look into using svk for your repository? I think > it will make commits to svn easier for both of us. Easier for > me to pull your changes and easier for you to track changes > in FreeBSD... ? > Yes, I will try to set it up later today. Should we retire the USB P4 repository then ? --HPS From lme at FreeBSD.org Thu Nov 6 09:28:52 2008 From: lme at FreeBSD.org (Lars Engels) Date: Thu Nov 6 09:29:09 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106.101047.163264510.imp@bsdimp.com> References: <49130918.5030904@FreeBSD.org> <20081106163729.clcw2eulgk0k4w0c@0x20.net> <49131109.2020601@FreeBSD.org> <20081106.101047.163264510.imp@bsdimp.com> Message-ID: <20081106172850.GG8256@e.0x20.net> On Thu, Nov 06, 2008 at 10:10:47AM -0700, M. Warner Losh wrote: > In message: <49131109.2020601@FreeBSD.org> > Alexander Motin writes: > : Lars Engels wrote: > : > 1. How can I tune the PCI configuration? With pciconf -w or so? > : > : Yes. `pciconf -r -b device addr` to read and `pciconf -w -b device addr > : value` to write. > > I have changes that almost make my TI card do it. So you're still working on this? > : > 2. Unfortunately the sysctl did not change a thing with regard to the > : > Card reader. > : > : Have you added it to the loader.conf and rebooted? > : > : > 3. I added the chip ID and the second device is now recognized as a > : > sdhci device but still does not see any card inserted: > : > > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify base > : > clock frequency. > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify > : > timeout clock frequency. > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't report any > : > support voltages. > : > : Looks like it is not enough compatible, or even not compatible. > > Chances are good that you need to the workaround to turn on these > things. Tell me where I can get the workaround when you have a working version or something to test. :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/8442c71b/attachment.pgp From imp at bsdimp.com Thu Nov 6 09:30:12 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Nov 6 09:30:19 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811061812.04449.hselasky@c2i.net> References: <200811051722.44148.hselasky@c2i.net> <20081106050416.09944ea2@tau.draftnet> <200811061812.04449.hselasky@c2i.net> Message-ID: <20081106.102738.-2043076325.imp@bsdimp.com> In message: <200811061812.04449.hselasky@c2i.net> Hans Petter Selasky writes: : On Thursday 06 November 2008, Bruce Cran wrote: : > On Wed, 5 Nov 2008 17:22:43 +0100 : > : > Hans Petter Selasky wrote: : > > On Wednesday 05 November 2008, kevin wrote: : > > > Hans Petter Selasky wrote: : > > > > On Wednesday 05 November 2008, kevin wrote: : > > > >> Hans Petter Selasky wrote: : > > > >>> Hi, : > > > >>> : > > > >>> A new USB release is available: : > > > >>> : > > > >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ : > > > >>> : > > > >>> %md5 usb2_release_003.* : > > > >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 : > > > >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf : > > > >>> %sha256 usb2_release_003.* : > > > >>> SHA256 (usb2_release_003.diff) = : > > > >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b : > > > >>> SHA256 (usb2_release_003.tar.gz) = : > > > >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 : > > > >>> : > > > >>> Changes since 002 release: : > > > >> : > > > >> I try to compile kernel with usb2. : > > > > : > > > > Hi, : > > > > : > > > > Try to load the module instead of having bluetooth in the kernel. : > > > > Then all dependancies are loaded automatically. : > > > > : > > > > Depends on some bluetooth stuff. : > > > > : > > > > --HPS : > > > : > > > I build kernel without usb2_bluetooth_ng successfully. i notice that : > > > fingerpring and bluetooth mouse nolonger work now. : > > > in dmesg: : > > > ugen0.2: at usbus0 : > > > ugen0.3: at usbus0 : > > > maybe /etc/rc.d/bthidd and fprint package need update now. : > > : > > Try: : > > : > > kldload usb2_bluetooth_ng : > : > I don't know if this is a problem in general, but I can't load : > : > usb2_serial_modem and have usb2_serial load automatically: : > > kldload usb2_serial_modem : > : > interface ucom.1 already present in the KLD 'ucom.ko'! : > kldload: /boot/kernel/usb2_serial.ko: Unsupported file type : > KLD usb2_serial_modem.ko: depends on usb2_serial - not available : > kldload: /boot/kernel/usb2_serial_modem.ko: Unsupported file type : > : > kldload'ing usb2_serial followed by usb2_serial_modem works though. : : Hi, : : Fixed in the following commit: : : http://perforce.freebsd.org/chv.cgi?CH=152584 : : Thanks again for your reporting. I've merged this into -head. Warner From imp at bsdimp.com Thu Nov 6 09:30:22 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Nov 6 09:30:35 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811061812.04449.hselasky@c2i.net> References: <200811051722.44148.hselasky@c2i.net> <20081106050416.09944ea2@tau.draftnet> <200811061812.04449.hselasky@c2i.net> Message-ID: <20081106.102738.-2043076325.imp@bsdimp.com> In message: <200811061812.04449.hselasky@c2i.net> Hans Petter Selasky writes: : On Thursday 06 November 2008, Bruce Cran wrote: : > On Wed, 5 Nov 2008 17:22:43 +0100 : > : > Hans Petter Selasky wrote: : > > On Wednesday 05 November 2008, kevin wrote: : > > > Hans Petter Selasky wrote: : > > > > On Wednesday 05 November 2008, kevin wrote: : > > > >> Hans Petter Selasky wrote: : > > > >>> Hi, : > > > >>> : > > > >>> A new USB release is available: : > > > >>> : > > > >>> http://www.selasky.org/hans_petter/usb4bsd/for_review/ : > > > >>> : > > > >>> %md5 usb2_release_003.* : > > > >>> MD5 (usb2_release_003.diff) = e31a032d0234bb7d72eb968c33118d84 : > > > >>> MD5 (usb2_release_003.tar.gz) = 0a0d9dd44e93ba2ceaa849c577f6fecf : > > > >>> %sha256 usb2_release_003.* : > > > >>> SHA256 (usb2_release_003.diff) = : > > > >>> 9b4359f76eeef43d9b6c0c524198e529f2debff14e6158ebac8f35d51efb211b : > > > >>> SHA256 (usb2_release_003.tar.gz) = : > > > >>> 3040714546fc21bc2943c2e7aec1734150845271664aad44639ff5c553e3ed31 : > > > >>> : > > > >>> Changes since 002 release: : > > > >> : > > > >> I try to compile kernel with usb2. : > > > > : > > > > Hi, : > > > > : > > > > Try to load the module instead of having bluetooth in the kernel. : > > > > Then all dependancies are loaded automatically. : > > > > : > > > > Depends on some bluetooth stuff. : > > > > : > > > > --HPS : > > > : > > > I build kernel without usb2_bluetooth_ng successfully. i notice that : > > > fingerpring and bluetooth mouse nolonger work now. : > > > in dmesg: : > > > ugen0.2: at usbus0 : > > > ugen0.3: at usbus0 : > > > maybe /etc/rc.d/bthidd and fprint package need update now. : > > : > > Try: : > > : > > kldload usb2_bluetooth_ng : > : > I don't know if this is a problem in general, but I can't load : > : > usb2_serial_modem and have usb2_serial load automatically: : > > kldload usb2_serial_modem : > : > interface ucom.1 already present in the KLD 'ucom.ko'! : > kldload: /boot/kernel/usb2_serial.ko: Unsupported file type : > KLD usb2_serial_modem.ko: depends on usb2_serial - not available : > kldload: /boot/kernel/usb2_serial_modem.ko: Unsupported file type : > : > kldload'ing usb2_serial followed by usb2_serial_modem works though. : : Hi, : : Fixed in the following commit: : : http://perforce.freebsd.org/chv.cgi?CH=152584 : : Thanks again for your reporting. I've merged this into -head. Warner From imp at bsdimp.com Thu Nov 6 09:41:40 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Nov 6 09:41:59 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106172850.GG8256@e.0x20.net> References: <49131109.2020601@FreeBSD.org> <20081106.101047.163264510.imp@bsdimp.com> <20081106172850.GG8256@e.0x20.net> Message-ID: <20081106.103945.660268105.imp@bsdimp.com> In message: <20081106172850.GG8256@e.0x20.net> Lars Engels writes: : On Thu, Nov 06, 2008 at 10:10:47AM -0700, M. Warner Losh wrote: : > In message: <49131109.2020601@FreeBSD.org> : > Alexander Motin writes: : > : Lars Engels wrote: : > : > 1. How can I tune the PCI configuration? With pciconf -w or so? : > : : > : Yes. `pciconf -r -b device addr` to read and `pciconf -w -b device addr : > : value` to write. : > : > I have changes that almost make my TI card do it. : : So you're still working on this? TI changes are different than Richo changes : > : > 2. Unfortunately the sysctl did not change a thing with regard to the : > : > Card reader. : > : : > : Have you added it to the loader.conf and rebooted? : > : : > : > 3. I added the chip ID and the second device is now recognized as a : > : > sdhci device but still does not see any card inserted: : > : > : > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify base : > : > clock frequency. : > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify : > : > timeout clock frequency. : > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't report any : > : > support voltages. : > : : > : Looks like it is not enough compatible, or even not compatible. : > : > Chances are good that you need to the workaround to turn on these : > things. : : Tell me where I can get the workaround when you have a working version : or something to test. :) I'll look at the linux workaround... Warner From gary.jennejohn at freenet.de Thu Nov 6 09:48:56 2008 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Thu Nov 6 09:49:08 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081106141323.GA4489@wep4035.physik.uni-wuerzburg.de> References: <200810251925.47273.hselasky@c2i.net> <200811050908.35744.hselasky@c2i.net> <49117846.9080301@163.com> <200811051722.44148.hselasky@c2i.net> <20081106050416.09944ea2@tau.draftnet> <20081106141323.GA4489@wep4035.physik.uni-wuerzburg.de> Message-ID: <20081106183720.4aa1a83f@ernst.jennejohn.org> On Thu, 6 Nov 2008 15:13:23 +0100 "Alexey Shuvaev" wrote: [big snip] > I am having quite reliable panics with the new stack when I insert > usb stick (actually during the first access to it). > Trying to collect more information I haven't managed to produce > memory dump. Is it working on amd64 SMP CURRENT? I remember there were > some complains about it. > It works just fine for me with SMP amd64. I tested several USB sticks and saw absolutely no problems. I have not tried it with a real external USB disk. It also works with my FTDI USB-to-serial adapters. I do not use any USB modules. --- Gary Jennejohn From lme at FreeBSD.org Thu Nov 6 10:05:59 2008 From: lme at FreeBSD.org (Lars Engels) Date: Thu Nov 6 10:06:11 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <48DEA8E7.2080503@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> Message-ID: <20081106180556.GH8256@e.0x20.net> On Sun, Sep 28, 2008 at 12:43:03AM +0300, Alexander Motin wrote: > Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found at: > http://people.freebsd.org/~mav/sdhci/ > > I will be grateful for any feedbacks, comments and support. > Me again... On another notebook with the same card reader I get a little further: sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 on pci5 sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] mmc0: on sdhci0 mmc0: detached sdhci0: detached sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 on pci5 sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] sdhci0: detached sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 on pci5 sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] mmc0: on sdhci0 mmc0: detached mmc0: on sdhci0 So the mmc device is detected everytime I insert a card and is removed when I take the card out. But I do not get a new disk device... pciconf tells me pretty much the same like on the other notebook: fwohci0@pci0:5:9:1: class=0x0c0010 card=0xc024144d chip=0x05521180 rev=0x09 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'RL5c552 IEEE-1394 Controller' class = serial bus subclass = FireWire sdhci0@pci0:5:9:2: class=0x080500 card=0xc024144d chip=0x08221180 rev=0x18 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'R5C832, R5C843 SDA Standard Compliant SD Host Controller' class = base peripheral none7@pci0:5:9:3: class=0x088000 card=0xc024144d chip=0x08431180 rev=0x00 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh MMC Host Controller' class = base peripheral none8@pci0:5:9:4: class=0x088000 card=0xc024144d chip=0x05921180 rev=0x09 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = '13871043 Ricoh Memory Stick Host Controller' class = base peripheral none9@pci0:5:9:5: class=0x088000 card=0xc024144d chip=0x08521180 rev=0x04 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh xD-Picture Card Host Controller' class = base peripheral -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/da8500bc/attachment.pgp From hselasky at c2i.net Thu Nov 6 10:08:14 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Nov 6 10:08:32 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081106183720.4aa1a83f@ernst.jennejohn.org> References: <200810251925.47273.hselasky@c2i.net> <20081106141323.GA4489@wep4035.physik.uni-wuerzburg.de> <20081106183720.4aa1a83f@ernst.jennejohn.org> Message-ID: <200811061910.21994.hselasky@c2i.net> On Thursday 06 November 2008, Gary Jennejohn wrote: > On Thu, 6 Nov 2008 15:13:23 +0100 > "Alexey Shuvaev" wrote: > > [big snip] > > > I am having quite reliable panics with the new stack when I insert > > usb stick (actually during the first access to it). > > Trying to collect more information I haven't managed to produce > > memory dump. Is it working on amd64 SMP CURRENT? I remember there were > > some complains about it. > > It works just fine for me with SMP amd64. I tested several USB sticks > and saw absolutely no problems. I have not tried it with a real > external USB disk. > > It also works with my FTDI USB-to-serial adapters. > > I do not use any USB modules. Hi Alexey, Maybe you are using the ATA interface for USB? Could you do a "kldstat" ? Or try: kldunload usb2_storage_ata And: kldload usb2_storage_mass --HPS From mav at FreeBSD.org Thu Nov 6 10:16:03 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Nov 6 10:16:15 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106180556.GH8256@e.0x20.net> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> Message-ID: <4913345F.2050801@FreeBSD.org> Lars Engels wrote: > On another notebook with the same card reader I get a little further: > > sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 > on pci5 > sdhci0: 1 slot(s) allocated > sdhci0: [ITHREAD] > mmc0: on sdhci0 > mmc0: detached > mmc0: on sdhci0 > > So the mmc device is detected everytime I insert a card and is removed > when I take the card out. It means that controller successfully reports card insertion. You must be a half way there. > But I do not get a new disk device... A bit more debugging can be produced with enabling verbose boot messages. > pciconf tells me pretty much the same like on the other notebook: Looks like it may depend or on controller version or on the way it is hardwired or somehow BIOS initialized. There are were some success stories reported with this controller. -- Alexander Motin From imp at bsdimp.com Thu Nov 6 10:23:35 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Nov 6 10:23:51 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <4913345F.2050801@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> Message-ID: <20081106.112338.1564836080.imp@bsdimp.com> In message: <4913345F.2050801@FreeBSD.org> Alexander Motin writes: : Lars Engels wrote: : > On another notebook with the same card reader I get a little further: : > : > sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 : > on pci5 : > sdhci0: 1 slot(s) allocated : > sdhci0: [ITHREAD] : > mmc0: on sdhci0 : > mmc0: detached : > mmc0: on sdhci0 : > : > So the mmc device is detected everytime I insert a card and is removed : > when I take the card out. : : It means that controller successfully reports card insertion. You must : be a half way there. : : > But I do not get a new disk device... : : A bit more debugging can be produced with enabling verbose boot messages. : : > pciconf tells me pretty much the same like on the other notebook: : : Looks like it may depend or on controller version or on the way it is : hardwired or somehow BIOS initialized. There are were some success : stories reported with this controller. Add mmcsd to the kernel? Load it as a module? Warner From lme at FreeBSD.org Thu Nov 6 10:40:19 2008 From: lme at FreeBSD.org (Lars Engels) Date: Thu Nov 6 10:40:39 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106.112338.1564836080.imp@bsdimp.com> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> <20081106.112338.1564836080.imp@bsdimp.com> Message-ID: <20081106184017.GB161@e.0x20.net> On Thu, Nov 06, 2008 at 11:23:38AM -0700, M. Warner Losh wrote: > In message: <4913345F.2050801@FreeBSD.org> > Alexander Motin writes: > : Lars Engels wrote: > : > On another notebook with the same card reader I get a little further: > : > > : > sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 > : > on pci5 > : > sdhci0: 1 slot(s) allocated > : > sdhci0: [ITHREAD] > : > mmc0: on sdhci0 > : > mmc0: detached > : > mmc0: on sdhci0 > : > > : > So the mmc device is detected everytime I insert a card and is removed > : > when I take the card out. > : > : It means that controller successfully reports card insertion. You must > : be a half way there. > : > : > But I do not get a new disk device... > : > : A bit more debugging can be produced with enabling verbose boot messages. > : > : > pciconf tells me pretty much the same like on the other notebook: > : > : Looks like it may depend or on controller version or on the way it is > : hardwired or somehow BIOS initialized. There are were some success > : stories reported with this controller. > > Add mmcsd to the kernel? Load it as a module? Much better! Loading mmcsd first, then mmc and sdhci gives me the mmcsd0 device: sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 on pci5 sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] mmc0: on sdhci0 mmcsd0: 1924MB at mmc0 16MHz/4bit sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x783ffe00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00010000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00002000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00040000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00008000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000400 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00002000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00010000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000200 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x783ffe00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0002fa00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00021a00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0005fa00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00027a00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fe00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00021a00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0002fa00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000013 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== But I still cannot use it: lars@pts/3 # ls -l /dev/mmcsd0* crw-r----- 1 root operator 0, 120 Nov 6 19:36 /dev/mmcsd0 crw-r----- 1 root operator 0, 121 Nov 6 19:36 /dev/mmcsd0s1 lars@pts/3 # fdisk /dev/mmcsd0 fdisk: could not detect sector size lars@pts/3 # mount -t msdosfs /dev/mmcsd0s1 /mnt mount_msdosfs: /dev/mmcsd0s1: : Input/output error What am I missing? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/c80c07fd/attachment-0001.pgp From mav at FreeBSD.org Thu Nov 6 11:02:06 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Nov 6 11:02:23 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106184017.GB161@e.0x20.net> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> <20081106.112338.1564836080.imp@bsdimp.com> <20081106184017.GB161@e.0x20.net> Message-ID: <49133F2B.4080801@FreeBSD.org> Lars Engels wrote: > Much better! Loading mmcsd first, then mmc and sdhci gives me the mmcsd0 > device: > > sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 > on pci5 > sdhci0: 1 slot(s) allocated > sdhci0: [ITHREAD] > mmc0: on sdhci0 > mmcsd0: 1924MB at mmc0 16MHz/4bit > sdhci0-slot0: Got data interrupt 0x00000002, but there is no active This error should not happen normally. Or this controller has some problems with DMA mode (it's PCI class reports that DMA is not supported, but as soon as we have some reports that it does working it is forcefully used) or it is some problem with driver. To get some info about what is happening actually, uncomment two fragments in driver. This: /* printf("%s cmd op %u arg %u flags %u data %ju\n", __func__, req->cmd->opcode, req->cmd->arg, req->cmd->flags, (req->cmd->data)?req->cmd->data->len:0); */ and this: /* slot_printf(slot, "got interrupt %x\n", intmask); */ Enable verbose messages, and send me what you will get. -- Alexander Motin From lme at FreeBSD.org Thu Nov 6 11:04:30 2008 From: lme at FreeBSD.org (Lars Engels) Date: Thu Nov 6 11:04:36 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106184017.GB161@e.0x20.net> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> <20081106.112338.1564836080.imp@bsdimp.com> <20081106184017.GB161@e.0x20.net> Message-ID: <20081106190428.GC161@e.0x20.net> On Thu, Nov 06, 2008 at 07:40:17PM +0100, Lars Engels wrote: > On Thu, Nov 06, 2008 at 11:23:38AM -0700, M. Warner Losh wrote: > > In message: <4913345F.2050801@FreeBSD.org> > > Alexander Motin writes: > > : Lars Engels wrote: > > : > On another notebook with the same card reader I get a little further: > > : > > > : > sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 > > : > on pci5 > > : > sdhci0: 1 slot(s) allocated > > : > sdhci0: [ITHREAD] > > : > mmc0: on sdhci0 > > : > mmc0: detached > > : > mmc0: on sdhci0 > > : > > > : > So the mmc device is detected everytime I insert a card and is removed > > : > when I take the card out. > > : > > : It means that controller successfully reports card insertion. You must > > : be a half way there. > > : > > : > But I do not get a new disk device... > > : > > : A bit more debugging can be produced with enabling verbose boot messages. > > : > > : > pciconf tells me pretty much the same like on the other notebook: > > : > > : Looks like it may depend or on controller version or on the way it is > > : hardwired or somehow BIOS initialized. There are were some success > > : stories reported with this controller. > > > > Add mmcsd to the kernel? Load it as a module? > > Much better! Loading mmcsd first, then mmc and sdhci gives me the mmcsd0 > device: > sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 > on pci5 > sdhci0: 1 slot(s) allocated > sdhci0: [ITHREAD] > mmc0: on sdhci0 > mmcsd0: 1924MB at mmc0 16MHz/4bit > sdhci0-slot0: Got data interrupt 0x00000002, but there is no active > command. > sdhci0-slot0: ============== REGISTER DUMP ============== > sdhci0-slot0: Sys addr: 0x30c68000 | Version: 0x00000200 > sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 > sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 > sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 > sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 > sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 > sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 > sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb > sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 > sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 > sdhci0-slot0: =========================================== [...] > But I still cannot use it: > lars@pts/3 # ls -l /dev/mmcsd0* > crw-r----- 1 root operator 0, 120 Nov 6 19:36 /dev/mmcsd0 > crw-r----- 1 root operator 0, 121 Nov 6 19:36 /dev/mmcsd0s1 > > lars@pts/3 # fdisk /dev/mmcsd0 > fdisk: could not detect sector size > > > lars@pts/3 # mount -t msdosfs /dev/mmcsd0s1 /mnt > mount_msdosfs: /dev/mmcsd0s1: : Input/output error > > > What am I missing? That seems to be the SD card I used... Now I tried a SDHCI card and fdisk printed the partition table. mmcsd0: 7580MB at mmc0 16MHz/4bit However, when I tried to mount it, I get this error: g_vfs_done():mmcsd0s1[WRITE(offset=2254848, length=4096)]error = 5 g_vfs_done():mmcsd0s1[WRITE(offset=2254848, length=4096)]error = 5 g_vfs_done():mmcsd0s1[WRITE(offset=2254848, length=4096)]error = 5 fsync: giving up on dirty 0xc5452d9c: tag devfs, type VCHR usecount 1, writecount 0, refcount 240 mountedhere 0xc474f700 flags () v_object 0xc48368b8 ref 0 pages 240 lock type devfs: UNLOCKED dev mmcsd0s1 And a (reproducable) kernel panic shortly after that: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc057e6a9 stack pointer = 0x28:0xc3fd5b84 frame pointer = 0x28:0xc3fd5bb0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 19 (syncer) Physical memory: 1002 MB Dumping 163 MB: 148 132 116 100 84 68 52 36 20 4 Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. [...] Loaded symbols for /boot/kernel/mmcsd.ko Reading symbols from /boot/kernel/mmc.ko...done. Loaded symbols for /boot/kernel/mmc.ko Reading symbols from /boot/kernel/sdhci.ko...done. Loaded symbols for /boot/kernel/sdhci.ko #0 doadump () at pcpu.h:246 246 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:246 #1 0xc0477b99 in db_fncall (dummy1=-1006806728, dummy2=0, dummy3=-1063504288, dummy4=0xc3fd5918 "k?N?") at /usr/src/sys/ddb/db_command.c:548 #2 0xc0477f91 in db_command (last_cmdp=0xc097143c, cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:445 #3 0xc04780ea in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 #4 0xc0479f2d in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:229 #5 0xc0602076 in kdb_trap (type=12, code=0, tf=0xc3fd5b44) at /usr/src/sys/kern/subr_kdb.c:534 #6 0xc0880f6f in trap_fatal (frame=0xc3fd5b44, eva=0) at /usr/src/sys/i386/i386/trap.c:920 #7 0xc0881210 in trap_pfault (frame=0xc3fd5b44, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:842 #8 0xc0881bf2 in trap (frame=0xc3fd5b44) at /usr/src/sys/i386/i386/trap.c:522 #9 0xc0866cfb in calltrap () at /usr/src/sys/i386/i386/exception.s:165 #10 0xc057e6a9 in g_io_request (bp=0xc56c58c4, cp=0xc5562100) at /usr/src/sys/geom/geom_io.c:364 #11 0xc0583a06 in g_vfs_strategy (bo=0xc57dc0a8, bp=0xd82b9bc0) at /usr/src/sys/geom/geom_vfs.c:107 #12 0xc06456e1 in bufwrite (bp=0xd82b9bc0) at buf.h:397 #13 0xc063ea48 in bawrite (bp=0xd82b9bc0) at buf.h:385 #14 0xc064a23c in vop_stdfsync (ap=0xc3fd5c74) at /usr/src/sys/kern/vfs_default.c:482 #15 0xc056221e in devfs_fsync (ap=0xc3fd5c74) at /usr/src/sys/fs/devfs/devfs_vnops.c:485 #16 0xc088e312 in VOP_FSYNC_APV (vop=0xc0931520, a=0xc3fd5c74) at vnode_if.c:1007 #17 0xc065ccce in sync_vnode (slp=Variable "slp" is not available. ) at vnode_if.h:529 #18 0xc065d0c2 in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1761 #19 0xc05b3b83 in fork_exit (callout=0xc065ce00 , arg=0x0, frame=0xc3fd5d38) at /usr/src/sys/kern/kern_fork.c:815 #20 0xc0866d70 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:270 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/eeb6a9c0/attachment.pgp From mav at FreeBSD.org Thu Nov 6 11:10:32 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Nov 6 11:10:50 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <49133F2B.4080801@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> <20081106.112338.1564836080.imp@bsdimp.com> <20081106184017.GB161@e.0x20.net> <49133F2B.4080801@FreeBSD.org> Message-ID: <49134124.8010004@FreeBSD.org> Alexander Motin wrote: > Lars Engels wrote: >> Much better! Loading mmcsd first, then mmc and sdhci gives me the mmcsd0 >> device: >> >> sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 >> on pci5 >> sdhci0: 1 slot(s) allocated >> sdhci0: [ITHREAD] >> mmc0: on sdhci0 >> mmcsd0: 1924MB at mmc0 16MHz/4bit >> sdhci0-slot0: Got data interrupt 0x00000002, but there is no active > > This error should not happen normally. Or this controller has some > problems with DMA mode (it's PCI class reports that DMA is not > supported, but as soon as we have some reports that it does working it > is forcefully used) or it is some problem with driver. Or you can also try PIO mode by removing SDHCI_QUIRK_FORCE_DMA for this chip. -- Alexander Motin From shuvaev at physik.uni-wuerzburg.de Thu Nov 6 11:12:32 2008 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Thu Nov 6 11:12:45 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811061910.21994.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <20081106141323.GA4489@wep4035.physik.uni-wuerzburg.de> <20081106183720.4aa1a83f@ernst.jennejohn.org> <200811061910.21994.hselasky@c2i.net> Message-ID: <20081106191230.GA47600@wep4035.physik.uni-wuerzburg.de> On Thu, Nov 06, 2008 at 07:10:20PM +0100, Hans Petter Selasky wrote: > On Thursday 06 November 2008, Gary Jennejohn wrote: > > On Thu, 6 Nov 2008 15:13:23 +0100 > > "Alexey Shuvaev" wrote: > > > > [big snip] Exactly here was output from kldstat :) > > > > > I am having quite reliable panics with the new stack when I insert > > > usb stick (actually during the first access to it). > > > Trying to collect more information I haven't managed to produce > > > memory dump. Is it working on amd64 SMP CURRENT? I remember there were > > > some complains about it. > > Here I was actually asking about kernel memory dumps... Will try harder this time. > > It works just fine for me with SMP amd64. I tested several USB sticks > > and saw absolutely no problems. I have not tried it with a real > > external USB disk. > > > > It also works with my FTDI USB-to-serial adapters. > > > > I do not use any USB modules. > > Hi Alexey, > > Maybe you are using the ATA interface for USB? > > Could you do a "kldstat" ? > Here it is: [wep4035] ~> kldstat Id Refs Address Size Name 1 46 0xffffffff80100000 8daac8 kernel (/boot/kernel/kernel) 2 1 0xffffffff809db000 21ed8 snd_hda.ko (/boot/kernel/snd_hda.ko) 3 2 0xffffffff809fd000 749c8 sound.ko (/boot/kernel/sound.ko) 4 1 0xffffffff80a72000 3090 speaker.ko (/boot/kernel/speaker.ko) 5 1 0xffffffff80a76000 59e8 ichsmb.ko (/boot/kernel/ichsmb.ko) 6 2 0xffffffff80a7c000 2440 smbus.ko (/boot/kernel/smbus.ko) 7 1 0xffffffff80a7f000 fa10 i915.ko (/boot/kernel/i915.ko) 8 2 0xffffffff80a8f000 21c48 drm.ko (/boot/kernel/drm.ko) 9 1 0xffffffff80ab1000 e648 usb2_controller_uhci.ko (/boot/kernel/usb2_controller_uhci.ko) 10 3 0xffffffff80ac0000 5168 usb2_controller.ko (/boot/kernel/usb2_controller.ko) 11 8 0xffffffff80ac6000 5c548 usb2_core.ko (/boot/kernel/usb2_core.ko) 12 1 0xffffffff80b23000 125a0 usb2_controller_ehci.ko (/boot/kernel/usb2_controller_ehci.ko) 13 1 0xffffffff80b36000 4e48 usb2_input_ms.ko (/boot/kernel/usb2_input_ms.ko) 14 2 0xffffffff80b3b000 560 usb2_input.ko (/boot/kernel/usb2_input.ko) 15 1 0xffffffff80b3c000 ff08 usb2_storage_mass.ko (/boot/kernel/usb2_storage_mass.ko) 16 2 0xffffffff80b4c000 570 usb2_storage.ko (/boot/kernel/usb2_storage.ko) 19 1 0xffffffff80c2e000 216 green_saver.ko (/boot/kernel/green_saver.ko) Actually here what I have: [wep4035] ~> cat /boot/loader.conf loader_logo="beastie" ichsmb_load="YES" snd_hda_load="YES" speaker_load="YES" i915_load="YES" usb2_controller_uhci_load="YES" usb2_controller_ehci_load="YES" usb2_input_ms_load="YES" usb2_storage_mass_load="YES" > Or try: > > kldunload usb2_storage_ata > > And: > > kldload usb2_storage_mass > Now I will play with offending usb stick and with another one (actually microSDHC-usb adapter). Can it be that some modules are automatically loaded when I insert usb stick? Alexey. From rdivacky at freebsd.org Thu Nov 6 11:17:07 2008 From: rdivacky at freebsd.org (Roman Divacky) Date: Thu Nov 6 11:17:15 2008 Subject: [RFC]: c99 compiled world Message-ID: <20081106185512.GA33153@freebsd.org> hi I tried to compile world in C99 (in fact gnu99) gcc mode. It compiles correctly with two trivial exceptions (in sendmail and opensolaris) which are going to get fixed soon. So, what is your opinion on turning C99 (gnu99) on default in -current to exposure it to some testing. can you see some drawbacks? thnx for your opinions roman From lme at FreeBSD.org Thu Nov 6 11:23:57 2008 From: lme at FreeBSD.org (Lars Engels) Date: Thu Nov 6 11:24:13 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <49133F2B.4080801@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> <20081106.112338.1564836080.imp@bsdimp.com> <20081106184017.GB161@e.0x20.net> <49133F2B.4080801@FreeBSD.org> Message-ID: <20081106192353.GD161@e.0x20.net> On Thu, Nov 06, 2008 at 09:02:03PM +0200, Alexander Motin wrote: > Lars Engels wrote: > >Much better! Loading mmcsd first, then mmc and sdhci gives me the mmcsd0 > >device: > >sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 > >on pci5 > >sdhci0: 1 slot(s) allocated > >sdhci0: [ITHREAD] > >mmc0: on sdhci0 > >mmcsd0: 1924MB at mmc0 16MHz/4bit > >sdhci0-slot0: Got data interrupt 0x00000002, but there is no active > > This error should not happen normally. Or this controller has some problems with DMA mode (it's > PCI class reports that DMA is not supported, but as soon as we have some reports that it does > working it is forcefully used) or it is some problem with driver. To get some info about what is > happening actually, uncomment two fragments in driver. This: > > /* printf("%s cmd op %u arg %u flags %u data %ju\n", __func__, > req->cmd->opcode, req->cmd->arg, req->cmd->flags, > (req->cmd->data)?req->cmd->data->len:0); */ > > and this: > > /* > slot_printf(slot, "got interrupt %x\n", intmask); > */ > > Enable verbose messages, and send me what you will get. Okay, I start with loading the three modules: Nov 6 20:19:42 maggie kernel: pci0: driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x8086, dev=0x27c8, revid=0x02 Nov 6 20:19:42 maggie kernel: domain=0, bus=0, slot=29, func=0 Nov 6 20:19:42 maggie kernel: class=0c-03-00, hdrtype=0x00, mfdev=1 Nov 6 20:19:42 maggie kernel: cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=a, irq=23 Nov 6 20:19:42 maggie kernel: pci0:0:29:0: reprobing on driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x8086, dev=0x27c9, revid=0x02 Nov 6 20:19:42 maggie kernel: domain=0, bus=0, slot=29, func=1 Nov 6 20:19:42 maggie kernel: class=0c-03-00, hdrtype=0x00, mfdev=0 Nov 6 20:19:42 maggie kernel: cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=b, irq=19 Nov 6 20:19:42 maggie kernel: pci0:0:29:1: reprobing on driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x8086, dev=0x27ca, revid=0x02 Nov 6 20:19:42 maggie kernel: domain=0, bus=0, slot=29, func=2 Nov 6 20:19:42 maggie kernel: class=0c-03-00, hdrtype=0x00, mfdev=0 Nov 6 20:19:42 maggie kernel: cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=c, irq=18 Nov 6 20:19:42 maggie kernel: pci0:0:29:2: reprobing on driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x8086, dev=0x27cb, revid=0x02 Nov 6 20:19:42 maggie kernel: domain=0, bus=0, slot=29, func=3 Nov 6 20:19:42 maggie kernel: class=0c-03-00, hdrtype=0x00, mfdev=0 Nov 6 20:19:42 maggie kernel: cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=d, irq=16 Nov 6 20:19:42 maggie kernel: pci0:0:29:3: reprobing on driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x8086, dev=0x27cc, revid=0x02 Nov 6 20:19:42 maggie kernel: domain=0, bus=0, slot=29, func=7 Nov 6 20:19:42 maggie kernel: class=0c-03-20, hdrtype=0x00, mfdev=0 Nov 6 20:19:42 maggie kernel: cmdreg=0x0006, statreg=0x0290, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=a, irq=23 Nov 6 20:19:42 maggie kernel: powerspec 2 supports D0 D3 current D0 Nov 6 20:19:42 maggie kernel: pci0:0:29:7: reprobing on driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x8086, dev=0x27da, revid=0x02 Nov 6 20:19:42 maggie kernel: domain=0, bus=0, slot=31, func=3 Nov 6 20:19:42 maggie kernel: class=0c-05-00, hdrtype=0x00, mfdev=0 Nov 6 20:19:42 maggie kernel: cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=b, irq=19 Nov 6 20:19:42 maggie kernel: pci0:0:31:3: reprobing on driver added Nov 6 20:19:42 maggie kernel: pci2: driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x8086, dev=0x4222, revid=0x02 Nov 6 20:19:42 maggie kernel: domain=0, bus=2, slot=0, func=0 Nov 6 20:19:42 maggie kernel: class=02-80-00, hdrtype=0x00, mfdev=0 Nov 6 20:19:42 maggie kernel: cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=a, irq=16 Nov 6 20:19:42 maggie kernel: powerspec 2 supports D0 D3 current D0 Nov 6 20:19:42 maggie kernel: MSI supports 1 message, 64 bit Nov 6 20:19:42 maggie kernel: pci0:2:0:0: reprobing on driver added Nov 6 20:19:42 maggie kernel: pci3: driver added Nov 6 20:19:42 maggie kernel: pci5: driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x1180, dev=0x0822, revid=0x18 Nov 6 20:19:42 maggie kernel: domain=0, bus=5, slot=9, func=2 Nov 6 20:19:42 maggie kernel: class=08-05-00, hdrtype=0x00, mfdev=1 Nov 6 20:19:42 maggie kernel: cmdreg=0x0000, statreg=0x0210, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=c, irq=22 Nov 6 20:19:42 maggie kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Nov 6 20:19:42 maggie kernel: pci0:5:9:2: reprobing on driver added Nov 6 20:19:42 maggie kernel: sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 on pci5 Nov 6 20:19:42 maggie kernel: pcib3: sdhci0 requested memory range 0xd8002800-0xd80028ff: good Nov 6 20:19:42 maggie kernel: sdhci0-slot0: 33MHz 4bits 3.3V DMA Nov 6 20:19:42 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:19:42 maggie kernel: sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 Nov 6 20:19:42 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:19:42 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000000 Nov 6 20:19:42 maggie kernel: sdhci0-slot0: Present: 0x01f20000 | Host ctl: 0x00000000 Nov 6 20:19:42 maggie kernel: sdhci0-slot0: Power: 0x00000000 | Blk gap: 0x00000000 Nov 6 20:19:42 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000000 Nov 6 20:19:42 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:19:42 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:19:42 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:19:42 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:19:42 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:19:42 maggie kernel: sdhci0: 1 slot(s) allocated Nov 6 20:19:42 maggie kernel: sdhci0: [MPSAFE] Nov 6 20:19:42 maggie kernel: sdhci0: [ITHREAD] Nov 6 20:19:42 maggie kernel: found-> vendor=0x1180, dev=0x0843, revid=0x00 Nov 6 20:19:42 maggie kernel: domain=0, bus=5, slot=9, func=3 Nov 6 20:19:42 maggie kernel: class=08-80-00, hdrtype=0x00, mfdev=1 Nov 6 20:19:42 maggie kernel: cmdreg=0x0002, statreg=0x0210, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=c, irq=255 Nov 6 20:19:42 maggie kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Nov 6 20:19:42 maggie kernel: pci0:5:9:3: reprobing on driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x1180, dev=0x0592, revid=0x09 Nov 6 20:19:42 maggie kernel: domain=0, bus=5, slot=9, func=4 Nov 6 20:19:42 maggie kernel: class=08-80-00, hdrtype=0x00, mfdev=1 Nov 6 20:19:42 maggie kernel: cmdreg=0x0002, statreg=0x0210, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=c, irq=255 Nov 6 20:19:42 maggie kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Nov 6 20:19:42 maggie kernel: pci0:5:9:4: reprobing on driver added Nov 6 20:19:42 maggie kernel: found-> vendor=0x1180, dev=0x0852, revid=0x04 Nov 6 20:19:42 maggie kernel: domain=0, bus=5, slot=9, func=5 Nov 6 20:19:42 maggie kernel: class=08-80-00, hdrtype=0x00, mfdev=1 Nov 6 20:19:42 maggie kernel: cmdreg=0x0002, statreg=0x0210, cachelnsz=0 (dwords) Nov 6 20:19:42 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 20:19:42 maggie kernel: intpin=c, irq=255 Nov 6 20:19:42 maggie kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Nov 6 20:19:42 maggie kernel: pci0:5:9:5: reprobing on driver added -------------------------------------------------------------------------------------------------------- Inserting the SD card: Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 40 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Card inserted Nov 6 20:21:11 maggie kernel: mmc0: on sdhci0 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 0 arg 0 flags 64 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 8 arg 426 flags 101 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1073741824 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 0 arg 0 flags 64 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 8 arg 426 flags 101 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 2 arg 0 flags 103 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 3 arg 0 flags 101 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 9 arg 131072 flags 103 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 7 arg 131072 flags 29 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 131072 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 51 arg 0 flags 53 data 8 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 6 arg 16777215 flags 53 data 64 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 7 arg 0 flags 0 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 7 arg 131072 flags 29 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 6 arg 2164260848 flags 53 data 64 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 7 arg 0 flags 0 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: mmc0: setting transfer rate to 30.000MHz Nov 6 20:21:11 maggie kernel: mmcsd0: 1924MB at mmc0 16MHz/4bit Nov 6 20:21:11 maggie kernel: GEOM: new disk mmcsd0 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 7 arg 131072 flags 29 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: mmc0: setting bus width to 4 bits Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 131072 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 6 arg 2 flags 21 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 512 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 2017459712 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 2017459712 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 2017459712 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x783ffe00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 65536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 65536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 65536 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00010000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 8192 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 8192 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 8192 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00002000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 262144 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 262144 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 262144 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00040000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 32768 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 32768 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 32768 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00008000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 1024 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 1024 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 1024 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00000400 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 8192 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 8192 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 8192 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00002000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 65536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 65536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 65536 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00010000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 512 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 512 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 512 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00000200 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 129536 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 2017459712 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 2017459712 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 2017459712 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x783ffe00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 195072 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 195072 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 195072 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x0002fa00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 137728 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 137728 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 137728 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00021a00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 129536 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 391680 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 391680 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 391680 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x0005fa00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 162304 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 162304 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 162304 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00027a00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 129536 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 130560 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 130560 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 130560 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x0001fe00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 137728 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 137728 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 137728 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x00021a00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 195072 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 195072 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 195072 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x0002fa00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 0 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 129536 flags 53 dlen 0 dflags 2) Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:21:11 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000013 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:21:11 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:21:11 maggie kernel: sdhci0-slot0: =========================================== -------------------------------------------------------------------------------------------------- # fdisk /dev/mmcsd0 Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:22:57 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:22:57 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:22:57 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:22:57 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: =========================================== Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 18002 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Nov 6 20:22:57 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Sys addr: 0x3a864000 | Version: 0x00000200 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000013 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 20:22:57 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 20:22:57 maggie kernel: sdhci0-slot0: =========================================== Sorry for the lengthy mail :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/46ee4c2f/attachment.pgp From tinderbox at freebsd.org Thu Nov 6 11:28:15 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Nov 6 11:28:22 2008 Subject: [head tinderbox] failure on amd64/amd64 Message-ID: <20081106192811.61FB773039@freebsd-current.sentex.ca> TB --- 2008-11-06 18:20:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-06 18:20:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-11-06 18:20:00 - cleaning the object tree TB --- 2008-11-06 18:20:58 - cvsupping the source tree TB --- 2008-11-06 18:20:58 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-11-06 18:21:05 - building world (CFLAGS=-O -pipe) TB --- 2008-11-06 18:21:05 - cd /src TB --- 2008-11-06 18:21:05 - /usr/bin/make -B buildworld >>> World build started on Thu Nov 6 18:21:07 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] ===> usr.bin/dirname (all) cc -O -pipe -fstack-protector -c /src/usr.bin/dirname/dirname.c cc -O -pipe -fstack-protector -o dirname dirname.o ===> usr.bin/du (all) cc -O -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/usr.bin/du/du.c cc1: warnings being treated as errors /src/usr.bin/du/du.c: In function 'main': /src/usr.bin/du/du.c:276: warning: format '%jd' expects type 'intmax_t', but argument 2 has type 'long long int' *** Error code 1 Stop in /src/usr.bin/du. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-06 19:28:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-06 19:28:11 - ERROR: failed to build world TB --- 2008-11-06 19:28:11 - tinderbox aborted TB --- 2877.90 user 358.85 system 4090.79 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From lme at FreeBSD.org Thu Nov 6 11:32:50 2008 From: lme at FreeBSD.org (Lars Engels) Date: Thu Nov 6 11:32:59 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <49134124.8010004@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> <20081106.112338.1564836080.imp@bsdimp.com> <20081106184017.GB161@e.0x20.net> <49133F2B.4080801@FreeBSD.org> <49134124.8010004@FreeBSD.org> Message-ID: <20081106193247.GE161@e.0x20.net> On Thu, Nov 06, 2008 at 09:10:28PM +0200, Alexander Motin wrote: > Alexander Motin wrote: > >Lars Engels wrote: > >>Much better! Loading mmcsd first, then mmc and sdhci gives me the mmcsd0 > >>device: > >> > >>sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 > >>on pci5 > >>sdhci0: 1 slot(s) allocated > >>sdhci0: [ITHREAD] > >>mmc0: on sdhci0 > >>mmcsd0: 1924MB at mmc0 16MHz/4bit > >>sdhci0-slot0: Got data interrupt 0x00000002, but there is no active > >This error should not happen normally. Or this controller has some problems with DMA mode (it's PCI class > >reports that DMA is not supported, but as soon as we have some reports that it does working it is forcefully > >used) or it is some problem with driver. > > Or you can also try PIO mode by removing SDHCI_QUIRK_FORCE_DMA for this chip. Doesn't work either. It is now recognized as a generic SD card reader but I still get errors: sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 on pci5 sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] sdhci0-slot0: got interrupt 40 mmc0: on sdhci0 sdhci_request cmd op 0 arg 0 flags 64 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 8 arg 426 flags 101 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1073741824 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 0 arg 0 flags 64 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 8 arg 426 flags 101 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 0 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 2 arg 0 flags 103 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 3 arg 0 flags 101 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 9 arg 131072 flags 103 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 7 arg 131072 flags 29 data 0 sdhci0-slot0: got interrupt 2 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 55 arg 131072 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 51 arg 0 flags 53 data 8 sdhci0-slot0: got interrupt 21 sdhci0-slot0: got interrupt 2 sdhci_request cmd op 6 arg 16777215 flags 53 data 64 sdhci0-slot0: got interrupt 21 sdhci0-slot0: got interrupt 2 sdhci_request cmd op 7 arg 0 flags 0 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 7 arg 131072 flags 29 data 0 sdhci0-slot0: got interrupt 2 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 6 arg 2164260848 flags 53 data 64 sdhci0-slot0: got interrupt 21 sdhci0-slot0: got interrupt 2 sdhci_request cmd op 7 arg 0 flags 0 data 0 sdhci0-slot0: got interrupt 1 mmcsd0: 1924MB at mmc0 16MHz/4bit sdhci_request cmd op 7 arg 131072 flags 29 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 55 arg 131072 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 6 arg 2 flags 21 data 0 sdhci0-slot0: got interrupt 1 sdhci_request cmd op 17 arg 0 flags 53 data 512 sdhci0-slot0: got interrupt 21 sdhci0-slot0: got interrupt 2 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 2017459712 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 2017459712 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x783ffe00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 65536 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 65536 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00010000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 8192 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 8192 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00002000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 262144 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 262144 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00040000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 32768 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 32768 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00008000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 1024 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 1024 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 1024 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 1024 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000400 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 8192 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 8192 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00002000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 65536 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 65536 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00010000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 512 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 512 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000200 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 129536 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 129536 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 2017459712 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 2017459712 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x783ffe00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 195072 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 195072 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0002fa00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 137728 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 137728 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00021a00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 129536 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 129536 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 391680 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 391680 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0005fa00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 162304 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 162304 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00027a00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 129536 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 129536 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 130560 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 130560 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fe00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 137728 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 137728 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00021a00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 195072 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 195072 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0002fa00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 129536 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 129536 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x0001fa00 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 3 sdhci_request cmd op 17 arg 0 flags 53 data 0 sdhci0-slot0: got interrupt 18002 sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. sdhci0-slot0: ============== REGISTER DUMP ============== sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000012 sdhci0-slot0: Present: 0x01ff0000 | Host ctl: 0x00000002 sdhci0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000107 sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 sdhci0-slot0: =========================================== -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/1c31537f/attachment-0001.pgp From sbangaru at panasas.com Thu Nov 6 11:46:55 2008 From: sbangaru at panasas.com (Bangaru, Sailaja) Date: Thu Nov 6 11:47:03 2008 Subject: Is there a need to hold the vnode lock across getnewbuf( ) in getblk? Message-ID: <977F1EB2DC429D40AB37C88180BFCD480352FD84@LAGUNA.int.panasas.com> One of the problems I'm running into is a deadlock where I have threads blocked on newbuf (with vnode lock held) due to buffer shortage and bufdaemon unable to flush buffers because it can't get the exclusive lock for the vnode. From the code: struct buf * getblk(struct vnode * vp, daddr_t blkno, int size, int slpflag, int slptimeo, int flags) { . . /* * Buffer is not in-core, create new buffer. The buffer * returned by getnewbuf() is locked. Note that the returned * buffer is also considered valid (not marked B_INVAL). */ BO_UNLOCK(bo); . . bp = getnewbuf(slpflag, slptimeo, size, maxsize, vp_to_buf_index(vp)); if (bp == NULL) { . . /* * This code is used to make sure that a buffer is not * created while the getnewbuf routine is blocked. * This can be a problem whether the vnode is locked or not. * If the buffer is created out from under us, we have to * throw away the one we just created. * * Note: this must occur before we associate the buffer * with the vp especially considering limitations in * the splay tree implementation when dealing with duplicate * lblkno's. */ BO_LOCK(bo); if (gbincore(bo, blkno)) { BO_UNLOCK(bo); bp->b_flags |= B_INVAL; brelse(bp); goto loop; } Given that this code rechecks if a buffer has already been created with the possibility that this thread might have blocked on getnewbuf (), Is there really any need to hold the vnode lock across getnewbuf call? thanks, --Sailaja From mav at FreeBSD.org Thu Nov 6 12:02:34 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Nov 6 12:02:52 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106192353.GD161@e.0x20.net> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> <20081106.112338.1564836080.imp@bsdimp.com> <20081106184017.GB161@e.0x20.net> <49133F2B.4080801@FreeBSD.org> <20081106192353.GD161@e.0x20.net> Message-ID: <49134D57.1050003@FreeBSD.org> Lars Engels wrote: > Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 55 arg 131072 flags 21 data 0 > Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 > Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 6 arg 2 flags 21 data 0 > Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 1 > Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 512 > Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 This is the first data request. 512 bytes reading. It was finished successfully: command end + data end = 3. > Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 > Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 3 But here is the problem. For some reason you have _zero_ data size. Controller reports successful competition, but it probably isn't > Nov 6 20:21:11 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 > Nov 6 20:21:11 maggie kernel: sdhci0-slot0: got interrupt 18002 > Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) > Nov 6 20:21:11 maggie kernel: sdhci0-slot0: Got data interrupt 0x00000002, but there is no active command. Here is the results of the previous. Card still sending something, does not responds to the command, controller signals error. > # fdisk /dev/mmcsd0 > > Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 > Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 3 > Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 > Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 18002 > Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) Here is just the same. And you have exactly the same with PIO mode. So looks like it is not card or driver problem, but sooner, mmc or mmcsd layer problem and it looks quite strange. Which sources exactly do you have, are they latest, are they in sync with each other and have you rebuilt all of them carefully? If so, you can try to uncomment // printf("Len %d %lld-%lld flags %#x sz // ... lines in mmcsd.c to look what happens. > Sorry for the lengthy mail :) Thanks, I like such mails, it's like a hunting. :) -- Alexander Motin From kostikbel at gmail.com Thu Nov 6 12:18:06 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Thu Nov 6 12:18:19 2008 Subject: Is there a need to hold the vnode lock across getnewbuf( ) in getblk? In-Reply-To: <977F1EB2DC429D40AB37C88180BFCD480352FD84@LAGUNA.int.panasas.com> References: <977F1EB2DC429D40AB37C88180BFCD480352FD84@LAGUNA.int.panasas.com> Message-ID: <20081106201750.GY18100@deviant.kiev.zoral.com.ua> On Thu, Nov 06, 2008 at 11:33:23AM -0800, Bangaru, Sailaja wrote: > One of the problems I'm running into is a deadlock where I have threads > blocked on newbuf (with vnode lock held) due to buffer shortage and > bufdaemon unable to flush buffers because it can't get the exclusive > lock for the vnode. From the code: > > struct buf * > getblk(struct vnode * vp, daddr_t blkno, int size, int slpflag, int > slptimeo, > int flags) > { > . > . > > /* > * Buffer is not in-core, create new buffer. The buffer > * returned by getnewbuf() is locked. Note that the > returned > * buffer is also considered valid (not marked B_INVAL). > */ > BO_UNLOCK(bo); > . > . > bp = getnewbuf(slpflag, slptimeo, size, maxsize, > vp_to_buf_index(vp)); > if (bp == NULL) { > . > . > /* > * This code is used to make sure that a buffer is not > * created while the getnewbuf routine is blocked. > * This can be a problem whether the vnode is locked or > not. > * If the buffer is created out from under us, we have > to > * throw away the one we just created. > * > * Note: this must occur before we associate the buffer > * with the vp especially considering limitations in > * the splay tree implementation when dealing with > duplicate > * lblkno's. > */ > BO_LOCK(bo); > if (gbincore(bo, blkno)) { > BO_UNLOCK(bo); > bp->b_flags |= B_INVAL; > brelse(bp); > goto loop; > } > > Given that this code rechecks if a buffer has already been created with > the possibility that this thread might have blocked on getnewbuf (), Is > there really > any need to hold the vnode lock across getnewbuf call? Vnode lock is not needed for the fragment you cited. But dropping it would allow for vnode to be reclaimed, that cause problems for the callers. Callers actually do not expect the vnode to become VI_DOOMED after call to bread(). Some time ago I developed patch that handles these bufdaemon deadlocks with another strategy. I loaned threads that called getblk, to help bufdaemon. The thread that is to blocked in getblk due to buffer or buffer KVA shortage, instead does flushing of the buffers belonging to the vnode locked by that thread. Also, I fixed the situation where ffs_bufwrite, called to flush buffer due to shortage, tries to allocate shadow buffer for cg block. I did not committed this because there is a problem, at least for UFS. Writing buffer while curthread may hold a buffer lock on the indirect inode block might cause a panic with recursive lock attempt. This is fixable, by changing UFS/FFS to never hold two buffer locks, but I did not got to do it. Peter Holm tested the patch, it eliminated "nbufkv" deadlocks for our test scenarious. diff --git a/sys/gnu/fs/xfs/FreeBSD/xfs_buf.c b/sys/gnu/fs/xfs/FreeBSD/xfs_buf.c index 9759d5a..ff06865 100644 --- a/sys/gnu/fs/xfs/FreeBSD/xfs_buf.c +++ b/sys/gnu/fs/xfs/FreeBSD/xfs_buf.c @@ -81,7 +81,7 @@ xfs_buf_get_empty(size_t size, xfs_buftarg_t *target) { struct buf *bp; - bp = geteblk(0); + bp = geteblk(0, 0); if (bp != NULL) { bp->b_bufsize = size; bp->b_bcount = size; @@ -100,7 +100,7 @@ xfs_buf_get_noaddr(size_t len, xfs_buftarg_t *target) if (len >= MAXPHYS) return (NULL); - bp = geteblk(len); + bp = geteblk(len, 0); if (bp != NULL) { BUF_ASSERT_HELD(bp); diff --git a/sys/kern/vfs_bio.c b/sys/kern/vfs_bio.c index f75963d..b5a5154 100644 --- a/sys/kern/vfs_bio.c +++ b/sys/kern/vfs_bio.c @@ -105,7 +105,8 @@ static void vfs_setdirty_locked_object(struct buf *bp); static void vfs_vmio_release(struct buf *bp); static int vfs_bio_clcheck(struct vnode *vp, int size, daddr_t lblkno, daddr_t blkno); -static int flushbufqueues(int, int); +static int buf_do_flush(struct vnode *vp); +static int flushbufqueues(struct vnode *, int, int); static void buf_daemon(void); static void bremfreel(struct buf *bp); @@ -247,6 +248,7 @@ static struct mtx nblock; #define QUEUE_DIRTY_GIANT 3 /* B_DELWRI buffers that need giant */ #define QUEUE_EMPTYKVA 4 /* empty buffer headers w/KVA assignment */ #define QUEUE_EMPTY 5 /* empty buffer headers */ +#define QUEUE_SENTINEL 1024 /* not an queue index, but mark for sentinel */ /* Queues for free buffers with various properties */ static TAILQ_HEAD(bqueues, buf) bufqueues[BUFFER_QUEUES] = { { 0 } }; @@ -1673,21 +1675,23 @@ vfs_bio_awrite(struct buf *bp) */ static struct buf * -getnewbuf(int slpflag, int slptimeo, int size, int maxsize) +getnewbuf(struct vnode *vp, int slpflag, int slptimeo, int size, int maxsize, + int gbflags) { + struct thread *td; struct buf *bp; struct buf *nbp; int defrag = 0; int nqindex; static int flushingbufs; + td = curthread; /* * We can't afford to block since we might be holding a vnode lock, * which may prevent system daemons from running. We deal with * low-memory situations by proactively returning memory and running * async I/O rather then sync I/O. */ - atomic_add_int(&getnewbufcalls, 1); atomic_subtract_int(&getnewbufrestarts, 1); restart: @@ -1919,8 +1923,9 @@ restart: */ if (bp == NULL) { - int flags; + int flags, norunbuf; char *waitmsg; + int fl; if (defrag) { flags = VFS_BIO_NEED_BUFSPACE; @@ -1938,9 +1943,35 @@ restart: mtx_unlock(&bqlock); bd_speedup(); /* heeeelp */ + if (gbflags & GB_NOWAIT_BD) + return (NULL); mtx_lock(&nblock); while (needsbuffer & flags) { + if (vp != NULL && (td->td_pflags & TDP_BUFNEED) == 0) { + mtx_unlock(&nblock); + /* + * getblk() is called with a vnode + * locked, and some majority of the + * dirty buffers may as well belong to + * the vnode. Flushing the buffers + * there would make a progress that + * cannot be achieved by the + * buf_daemon, that cannot lock the + * vnode. + */ + norunbuf = ~(TDP_BUFNEED | TDP_NORUNNINGBUF) | + (td->td_pflags & TDP_NORUNNINGBUF); + /* play bufdaemon */ + td->td_pflags |= TDP_BUFNEED | TDP_NORUNNINGBUF; + fl = buf_do_flush(vp); + td->td_pflags &= norunbuf; + mtx_lock(&nblock); + if (fl != 0) + continue; + if ((needsbuffer & flags) == 0) + break; + } if (msleep(&needsbuffer, &nblock, (PRIBIO + 4) | slpflag, waitmsg, slptimeo)) { mtx_unlock(&nblock); @@ -2009,6 +2040,35 @@ static struct kproc_desc buf_kp = { }; SYSINIT(bufdaemon, SI_SUB_KTHREAD_BUF, SI_ORDER_FIRST, kproc_start, &buf_kp); +static int +buf_do_flush(struct vnode *vp) +{ + int flushed; + + flushed = flushbufqueues(vp, QUEUE_DIRTY, 0); + /* The list empty check here is slightly racy */ + if (!TAILQ_EMPTY(&bufqueues[QUEUE_DIRTY_GIANT])) { + mtx_lock(&Giant); + flushed += flushbufqueues(vp, QUEUE_DIRTY_GIANT, 0); + mtx_unlock(&Giant); + } + if (flushed == 0) { + /* + * Could not find any buffers without rollback + * dependencies, so just write the first one + * in the hopes of eventually making progress. + */ + flushbufqueues(vp, QUEUE_DIRTY, 1); + if (!TAILQ_EMPTY( + &bufqueues[QUEUE_DIRTY_GIANT])) { + mtx_lock(&Giant); + flushbufqueues(vp, QUEUE_DIRTY_GIANT, 1); + mtx_unlock(&Giant); + } + } + return (flushed); +} + static void buf_daemon() { @@ -2022,7 +2082,7 @@ buf_daemon() /* * This process is allowed to take the buffer cache to the limit */ - curthread->td_pflags |= TDP_NORUNNINGBUF; + curthread->td_pflags |= TDP_NORUNNINGBUF | TDP_BUFNEED; mtx_lock(&bdlock); for (;;) { bd_request = 0; @@ -2037,30 +2097,8 @@ buf_daemon() * normally would so they can run in parallel with our drain. */ while (numdirtybuffers > lodirtybuffers) { - int flushed; - - flushed = flushbufqueues(QUEUE_DIRTY, 0); - /* The list empty check here is slightly racy */ - if (!TAILQ_EMPTY(&bufqueues[QUEUE_DIRTY_GIANT])) { - mtx_lock(&Giant); - flushed += flushbufqueues(QUEUE_DIRTY_GIANT, 0); - mtx_unlock(&Giant); - } - if (flushed == 0) { - /* - * Could not find any buffers without rollback - * dependencies, so just write the first one - * in the hopes of eventually making progress. - */ - flushbufqueues(QUEUE_DIRTY, 1); - if (!TAILQ_EMPTY( - &bufqueues[QUEUE_DIRTY_GIANT])) { - mtx_lock(&Giant); - flushbufqueues(QUEUE_DIRTY_GIANT, 1); - mtx_unlock(&Giant); - } + if (buf_do_flush(NULL) == 0) break; - } uio_yield(); } @@ -2106,7 +2144,7 @@ SYSCTL_INT(_vfs, OID_AUTO, flushwithdeps, CTLFLAG_RW, &flushwithdeps, 0, "Number of buffers flushed with dependecies that require rollbacks"); static int -flushbufqueues(int queue, int flushdeps) +flushbufqueues(struct vnode *lvp, int queue, int flushdeps) { struct buf sentinel; struct vnode *vp; @@ -2121,15 +2159,29 @@ flushbufqueues(int queue, int flushdeps) target /= 2; flushed = 0; bp = NULL; + sentinel.b_qindex = QUEUE_SENTINEL; mtx_lock(&bqlock); - TAILQ_INSERT_TAIL(&bufqueues[queue], &sentinel, b_freelist); + TAILQ_INSERT_HEAD(&bufqueues[queue], &sentinel, b_freelist); while (flushed != target) { - bp = TAILQ_FIRST(&bufqueues[queue]); - if (bp == &sentinel) + bp = TAILQ_NEXT(&sentinel, b_freelist); + if (bp != NULL) { + TAILQ_REMOVE(&bufqueues[queue], &sentinel, b_freelist); + TAILQ_INSERT_AFTER(&bufqueues[queue], bp, &sentinel, + b_freelist); + } else break; - TAILQ_REMOVE(&bufqueues[queue], bp, b_freelist); - TAILQ_INSERT_TAIL(&bufqueues[queue], bp, b_freelist); - + /* + * Skip sentinels inserted by other invocations of the + * flushbufqueues(), taking care to not reorder them. + */ + if (bp->b_qindex == QUEUE_SENTINEL) + continue; + /* + * Only flush the buffers that belong to the + * vnode locked by the curthread. + */ + if (lvp != NULL && bp->b_vp != lvp) + continue; if (BUF_LOCK(bp, LK_EXCLUSIVE | LK_NOWAIT, NULL) != 0) continue; if (bp->b_pin_count > 0) { @@ -2177,16 +2229,26 @@ flushbufqueues(int queue, int flushdeps) BUF_UNLOCK(bp); continue; } - if (vn_lock(vp, LK_EXCLUSIVE | LK_NOWAIT) == 0) { + if (vn_lock(vp, LK_EXCLUSIVE | LK_NOWAIT | LK_CANRECURSE) == 0) { mtx_unlock(&bqlock); CTR3(KTR_BUF, "flushbufqueue(%p) vp %p flags %X", bp, bp->b_vp, bp->b_flags); - vfs_bio_awrite(bp); + if (curproc == bufdaemonproc) + vfs_bio_awrite(bp); + else { + bremfree(bp); + bwrite(bp); + } vn_finished_write(mp); VOP_UNLOCK(vp, 0); flushwithdeps += hasdeps; flushed++; - waitrunningbufspace(); + /* + * Sleeping on runningbufspace while holding + * vnode lock leads to deadlock. + */ + if (curproc == bufdaemonproc) + waitrunningbufspace(); numdirtywakeup((lodirtybuffers + hidirtybuffers) / 2); mtx_lock(&bqlock); continue; @@ -2568,7 +2630,7 @@ loop: maxsize = vmio ? size + (offset & PAGE_MASK) : size; maxsize = imax(maxsize, bsize); - bp = getnewbuf(slpflag, slptimeo, size, maxsize); + bp = getnewbuf(vp, slpflag, slptimeo, size, maxsize, flags); if (bp == NULL) { if (slpflag || slptimeo) return NULL; @@ -2643,14 +2705,17 @@ loop: * set to B_INVAL. */ struct buf * -geteblk(int size) +geteblk(int size, int flags) { struct buf *bp; int maxsize; maxsize = (size + BKVAMASK) & ~BKVAMASK; - while ((bp = getnewbuf(0, 0, size, maxsize)) == 0) - continue; + while ((bp = getnewbuf(NULL, 0, 0, size, maxsize, flags)) == NULL) { + if ((flags & GB_NOWAIT_BD) && + (curthread->td_pflags & TDP_BUFNEED) != 0) + return (NULL); + } allocbuf(bp, size); bp->b_flags |= B_INVAL; /* b_dep cleared by getnewbuf() */ BUF_ASSERT_HELD(bp); diff --git a/sys/sys/buf.h b/sys/sys/buf.h index e05b20c..09e5c03 100644 --- a/sys/sys/buf.h +++ b/sys/sys/buf.h @@ -443,6 +443,7 @@ buf_countdeps(struct buf *bp, int i) */ #define GB_LOCK_NOWAIT 0x0001 /* Fail if we block on a buf lock. */ #define GB_NOCREAT 0x0002 /* Don't create a buf if not found. */ +#define GB_NOWAIT_BD 0x0004 /* Do not wait for bufdaemon */ #ifdef _KERNEL extern int nbuf; /* The number of buffer headers */ @@ -487,7 +488,7 @@ struct buf * getpbuf(int *); struct buf *incore(struct bufobj *, daddr_t); struct buf *gbincore(struct bufobj *, daddr_t); struct buf *getblk(struct vnode *, daddr_t, int, int, int, int); -struct buf *geteblk(int); +struct buf *geteblk(int, int); int bufwait(struct buf *); int bufwrite(struct buf *); void bufdone(struct buf *); diff --git a/sys/sys/proc.h b/sys/sys/proc.h index b326ba7..f38f0e4 100644 --- a/sys/sys/proc.h +++ b/sys/sys/proc.h @@ -344,7 +344,7 @@ do { \ #define TDP_OLDMASK 0x00000001 /* Need to restore mask after suspend. */ #define TDP_INKTR 0x00000002 /* Thread is currently in KTR code. */ #define TDP_INKTRACE 0x00000004 /* Thread is currently in KTRACE code. */ -#define TDP_UNUSED8 0x00000008 /* available */ +#define TDP_BUFNEED 0x00000008 /* Do not recurse into the buf flush */ #define TDP_COWINPROGRESS 0x00000010 /* Snapshot copy-on-write in progress. */ #define TDP_ALTSTACK 0x00000020 /* Have alternate signal stack. */ #define TDP_DEADLKTREAT 0x00000040 /* Lock aquisition - deadlock treatment. */ diff --git a/sys/ufs/ffs/ffs_vfsops.c b/sys/ufs/ffs/ffs_vfsops.c index 563473c..8118b80 100644 --- a/sys/ufs/ffs/ffs_vfsops.c +++ b/sys/ufs/ffs/ffs_vfsops.c @@ -1824,7 +1824,9 @@ ffs_bufwrite(struct buf *bp) ("bufwrite: needs chained iodone (%p)", bp->b_iodone)); /* get a new block */ - newbp = geteblk(bp->b_bufsize); + newbp = geteblk(bp->b_bufsize, GB_NOWAIT_BD); + if (newbp == NULL) + goto normal_write; /* * set it to be identical to the old block. We have to @@ -1864,6 +1866,7 @@ ffs_bufwrite(struct buf *bp) } /* Let the normal bufwrite do the rest for us */ +normal_write: return (bufwrite(bp)); } -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/a7ee5eb6/attachment.pgp From admin at lissyara.su Thu Nov 6 12:49:11 2008 From: admin at lissyara.su (Alex Keda) Date: Thu Nov 6 12:49:18 2008 Subject: Cannot buildworld in CURRENT Message-ID: <49135844.7010500@lissyara.su> ===> usr.bin/du (all) cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /usr/src/usr.bin/du/du.c cc1: warnings being treated as errors /usr/src/usr.bin/du/du.c: In function 'main': /usr/src/usr.bin/du/du.c:276: warning: format '%jd' expects type 'intmax_t', but argument 2 has type 'long long int' *** Error code 1 Stop in /usr/src/usr.bin/du. *** Error code 1 ============ updated 2 hour ago From admin at lissyara.su Thu Nov 6 12:51:27 2008 From: admin at lissyara.su (Alex Keda) Date: Thu Nov 6 12:51:34 2008 Subject: Cannot buildworld in CURRENT In-Reply-To: <49135844.7010500@lissyara.su> References: <49135844.7010500@lissyara.su> Message-ID: <491358CD.4090601@lissyara.su> Alex Keda ?????: > ===> usr.bin/du (all) > cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter > -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls > -Wno-pointer-sign -c /usr/src/usr.bin/du/du.c > cc1: warnings being treated as errors > /usr/src/usr.bin/du/du.c: In function 'main': > /usr/src/usr.bin/du/du.c:276: warning: format '%jd' expects type > 'intmax_t', but argument 2 has type 'long long int' > *** Error code 1 > > Stop in /usr/src/usr.bin/du. > *** Error code 1 > ============ > updated 2 hour ago acer# uname -a FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue Nov 4 23:23:29 MSK 2008 root@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console amd64 acer# From phk at phk.freebsd.dk Thu Nov 6 12:52:46 2008 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Thu Nov 6 12:52:53 2008 Subject: [RFC]: c99 compiled world In-Reply-To: Your message of "Thu, 06 Nov 2008 19:55:12 +0100." <20081106185512.GA33153@freebsd.org> Message-ID: <2350.1226004763@critter.freebsd.dk> In message <20081106185512.GA33153@freebsd.org>, Roman Divacky writes: >hi > >I tried to compile world in C99 (in fact gnu99) gcc mode. It >compiles correctly with two trivial exceptions (in sendmail >and opensolaris) which are going to get fixed soon. > >So, what is your opinion on turning C99 (gnu99) on default in >-current to exposure it to some testing. can you see some drawbacks? I think it is a good idea to avoid regressions. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From shuvaev at physik.uni-wuerzburg.de Thu Nov 6 13:03:03 2008 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Thu Nov 6 13:03:10 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081106191230.GA47600@wep4035.physik.uni-wuerzburg.de> References: <200810251925.47273.hselasky@c2i.net> <20081106141323.GA4489@wep4035.physik.uni-wuerzburg.de> <20081106183720.4aa1a83f@ernst.jennejohn.org> <200811061910.21994.hselasky@c2i.net> <20081106191230.GA47600@wep4035.physik.uni-wuerzburg.de> Message-ID: <20081106210300.GA1595@wep4035.physik.uni-wuerzburg.de> On Thu, Nov 06, 2008 at 08:12:30PM +0100, Alexey Shuvaev wrote: > On Thu, Nov 06, 2008 at 07:10:20PM +0100, Hans Petter Selasky wrote: > > On Thursday 06 November 2008, Gary Jennejohn wrote: > > > > > > Alexey Shuvaev wrote: > > > > I am having quite reliable panics with the new stack when I insert > > > > usb stick (actually during the first access to it). > > > > Well, they are not so reliable. I have managed to produce one, but not with this stick. It is with USB-microSDHC adapter with 8 Gb card. > > > > Trying to collect more information I haven't managed to produce > > > > memory dump. Is it working on amd64 SMP CURRENT? I remember there were > > > > some complains about it. > > > > Here I was actually asking about kernel memory dumps... > Will try harder this time. > Calling doadump at ddb prompt does the job. > Now I will play with offending usb stick and with another one > (actually microSDHC-usb adapter). > > Can it be that some modules are automatically loaded when I insert usb stick? > Seems not to be the case. Now I have a kernel dump. Some info from it: Unread portion of the kernel message buffer: [snip] ugen7.2: at usbus7 umass0: on usbus7 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:1:0:-1: Attached to scbus1 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 7790MB (15954944 512 byte sectors: 255H 63S/T 993C) <118># [here I have mounted it rw] <118># <118>.Spotlight-V100 IMG_2684.CR2 IMG_2836.JPG films <118>.Trashes IMG_2684.JPG My Documents gpsVP <118>._.Trashes IMG_2836.CR2 bombus-ng pilot [and here umounted, IIRC] <118># Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex UMASS lock (UMASS lock) r = 0 (0xffffffff80b426a0) locked @ /usr/src/sys/modules/usb2/core/../../../dev/usb2/core/usb2_transfer.c:1795 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x49 witness_warn() at witness_warn+0x2b7 trap() at trap+0x38f calltrap() at calltrap+0x8 --- trap 0xc, rip = 0xffffffff804b2466, rsp = 0xfffffffeba7f8ac0, rbp = 0xfffffffeba7f8b00 --- bcopy() at bcopy+0x16 usb2_bdma_pre_sync() at usb2_bdma_pre_sync+0x35 usb2_bdma_work_loop() at usb2_bdma_work_loop+0x29b usb2_command_wrapper() at usb2_command_wrapper+0x76 usb2_callback_wrapper() at usb2_callback_wrapper+0xfd usb2_command_wrapper() at usb2_command_wrapper+0x76 usb2_callback_proc() at usb2_callback_proc+0x68 usb2_process() at usb2_process+0xc0 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xfffffffeba7f8d40, rbp = 0 --- Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0xfffffffea429a000 fault code = supervisor write data, page not present instruction pointer = 0x8:0xffffffff804b2466 stack pointer = 0x10:0xfffffffeba7f8ac0 frame pointer = 0x10:0xfffffffeba7f8b00 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 3393 (USBPROC) lock order reversal: (Giant after non-sleepable) 1st 0xffffffff80b426a0 UMASS lock (UMASS lock) @ /usr/src/sys/modules/usb2/core/../../../dev/usb2/core/usb2_transfer.c:1795 2nd 0xffffffff806eeb20 Giant (Giant) @ /usr/src/sys/dev/kbdmux/kbdmux.c:1044 KDB: stack backtrace: lock order reversal: (sleepable after non-sleepable) 1st 0xffffffff80b426a0 UMASS lock (UMASS lock) @ /usr/src/sys/modules/usb2/core/../../../dev/usb2/core/usb2_transfer.c:1795 2nd 0xffffff00014ab3d0 user map (user map) @ /usr/src/sys/vm/vm_map.c:3115 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x49 witness_checkorder() at witness_checkorder+0x7e6 _sx_xlock() at _sx_xlock+0x44 vm_map_lookup() at vm_map_lookup+0x47 vm_fault() at vm_fault+0xfe trap_pfault() at trap_pfault+0x1fa trap() at trap+0x201 calltrap() at calltrap+0x8 --- trap 0xc, rip = 0xffffffff804b2466, rsp = 0xfffffffeba7f8ac0, rbp = 0xfffffffeba7f8b00 --- bcopy() at bcopy+0x16 usb2_bdma_pre_sync() at usb2_bdma_pre_sync+0x35 usb2_bdma_work_loop() at usb2_bdma_work_loop+0x29b usb2_command_wrapper() at usb2_command_wrapper+0x76 usb2_callback_wrapper() at usb2_callback_wrapper+0xfd usb2_command_wrapper() at usb2_command_wrapper+0x76 usb2_callback_proc() at usb2_callback_proc+0x68 usb2_process() at usb2_process+0xc0 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xfffffffeba7f8d40, rbp = 0 --- panic: vm_fault: fault on nofault entry, addr: fffffffea429a000 cpuid = 1 KDB: enter: panic Physical memory: 4075 MB Dumping 347 MB: 332 316 300 284 268 252 236 220 204 188 172 156 140 124 108 92 76 60 44 28 12 [here starts post-reboot session with kgdb] [snip] #0 doadump () at pcpu.h:196 196 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xffffffff80195f6c in db_fncall (dummy1=Variable "dummy1" is not available. ) at /usr/src/sys/ddb/db_command.c:548 #2 0xffffffff801962a1 in db_command (last_cmdp=0xffffffff806d1aa0, cmd_table=Variable "cmd_table" is not available. ) at /usr/src/sys/ddb/db_command.c:445 #3 0xffffffff801964e9 in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 #4 0xffffffff80198347 in db_trap (type=Variable "type" is not available. ) at /usr/src/sys/ddb/db_main.c:229 #5 0xffffffff802d4cd2 in kdb_trap (type=3, code=0, tf=0xfffffffeba7f84d0) at /usr/src/sys/kern/subr_kdb.c:534 #6 0xffffffff804b3b7f in trap (frame=0xfffffffeba7f84d0) at /usr/src/sys/amd64/amd64/trap.c:533 #7 0xffffffff80496d2e in calltrap () at /usr/src/sys/amd64/amd64/exception.S:217 #8 0xffffffff802d4e81 in kdb_enter (why=0xffffffff805183d9 "panic", msg=0xa
) at cpufunc.h:63 #9 0xffffffff802a804f in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:559 #10 0xffffffff804775f3 in vm_fault (map=0xffffff0001000000, vaddr=18446744067873808384, fault_type=Variable "fault_type" is not available. ) at /usr/src/sys/vm/vm_fault.c:277 #11 0xffffffff804b3359 in trap_pfault (frame=0xfffffffeba7f8a10, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:664 #12 0xffffffff804b3bec in trap (frame=0xfffffffeba7f8a10) at /usr/src/sys/amd64/amd64/trap.c:444 ---Type to continue, or q to quit--- #13 0xffffffff80496d2e in calltrap () at /usr/src/sys/amd64/amd64/exception.S:217 #14 0xffffffff804b2466 in bcopy () at /usr/src/sys/amd64/amd64/support.S:123 #15 0xffffffff804917b4 in _bus_dmamap_sync (dmat=0xffffff0005af6380, map=Variable "map" is not available. ) at /usr/src/sys/amd64/amd64/busdma_machdep.c:932 #16 0xffffffff80ac6549 in usb2_bdma_pre_sync (xfer=0xfffffffea429a000) at /usr/src/sys/modules/usb2/core/../../../dev/usb2/core/usb2_busdma.c:1358 #17 0xffffffff80ac691e in usb2_bdma_work_loop () from /boot/kernel/usb2_core.ko #18 0xffffffff80ad947c in usb2_command_wrapper (pq=0xfffffffe406fc000, xfer=Variable "xfer" is not available. ) at /usr/src/sys/modules/usb2/core/../../../dev/usb2/core/usb2_transfer.c:2515 #19 0xffffffff80adbcb8 in usb2_callback_wrapper (pq=Variable "pq" is not available. ) at /usr/src/sys/modules/usb2/core/../../../dev/usb2/core/usb2_transfer.c:1926 #20 0xffffffff80ad947c in usb2_command_wrapper (pq=0xfffffffe406fc028, xfer=Variable "xfer" is not available. ) at /usr/src/sys/modules/usb2/core/../../../dev/usb2/core/usb2_transfer.c:2515 #21 0xffffffff80ad95c7 in usb2_callback_proc (_pm=Variable "_pm" is not available. ) at /usr/src/sys/modules/usb2/core/../../../dev/usb2/core/usb2_transfer.c:1799 #22 0xffffffff80ad7221 in usb2_process (arg=Variable "arg" is not available. ) at /usr/src/sys/modules/usb2/core/../../../dev/usb2/core/usb2_process.c:139 #23 0xffffffff80289eea in fork_exit ( ---Type to continue, or q to quit--- callout=0xffffffff80ad7161 , arg=0xfffffffe406fc0f0, frame=0xfffffffeba7f8c90) at /usr/src/sys/kern/kern_fork.c:815 #24 0xffffffff8049713e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:521 #25 0x0000000000000000 in ?? () [snip] #50 0x0000000000000000 in ?? () #51 0xffffff00056a05a0 in ?? () #52 0xffffffff806f6900 in tdq_cpu () #53 0xffffff00014e96e0 in ?? () #54 0xfffffffeba7f8a70 in ?? () #55 0xfffffffeba7f8a28 in ?? () #56 0xffffff00056a1000 in ?? () #57 0xffffffff802c8de1 in sched_switch (td=0xfffffffe406fc0f0, newtd=0xffffffff80ad7161, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1848 Previous frame inner to this frame (corrupt stack?) (kgdb) I have a dump so let me know if you need more info. Alexey. From lme at FreeBSD.org Thu Nov 6 13:05:47 2008 From: lme at FreeBSD.org (Lars Engels) Date: Thu Nov 6 13:06:02 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <49134D57.1050003@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> <20081106.112338.1564836080.imp@bsdimp.com> <20081106184017.GB161@e.0x20.net> <49133F2B.4080801@FreeBSD.org> <20081106192353.GD161@e.0x20.net> <49134D57.1050003@FreeBSD.org> Message-ID: <20081106210545.GF161@e.0x20.net> On Thu, Nov 06, 2008 at 10:02:31PM +0200, Alexander Motin wrote: > Lars Engels wrote: > ># fdisk /dev/mmcsd0 > >Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 > >Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 3 > >Nov 6 20:22:57 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 0 > >Nov 6 20:22:57 maggie kernel: sdhci0-slot0: got interrupt 18002 > >Nov 6 20:22:57 maggie kernel: sdhci0-slot0: Command error 1 (opcode 17 arg 0 flags 53 dlen 0 dflags 2) > > Here is just the same. And you have exactly the same with PIO mode. So > looks like it is not card or driver problem, but sooner, mmc or mmcsd > layer problem and it looks quite strange. Which sources exactly do you > have, are they latest, are they in sync with each other and have you > rebuilt all of them carefully? Yes, that's what I have used: lars@pts/4 # ls ~/local-modules/sdhci/ mmc.20081011.tgz sdhci.20081019.tgz sdhci_mod.20081008.tgz > If so, you can try to uncomment > // printf("Len %d %lld-%lld flags %#x sz > // ... > lines in mmcsd.c to look what happens. I forgot to re-built mmcsd before, my fault... Now I re-built and loaded the modules again: Nov 6 21:50:55 maggie kernel: pci0: driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x8086, dev=0x27c8, revid=0x02 Nov 6 21:50:55 maggie kernel: domain=0, bus=0, slot=29, func=0 Nov 6 21:50:55 maggie kernel: class=0c-03-00, hdrtype=0x00, mfdev=1 Nov 6 21:50:55 maggie kernel: cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=a, irq=23 Nov 6 21:50:55 maggie kernel: pci0:0:29:0: reprobing on driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x8086, dev=0x27c9, revid=0x02 Nov 6 21:50:55 maggie kernel: domain=0, bus=0, slot=29, func=1 Nov 6 21:50:55 maggie kernel: class=0c-03-00, hdrtype=0x00, mfdev=0 Nov 6 21:50:55 maggie kernel: cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=b, irq=19 Nov 6 21:50:55 maggie kernel: pci0:0:29:1: reprobing on driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x8086, dev=0x27ca, revid=0x02 Nov 6 21:50:55 maggie kernel: domain=0, bus=0, slot=29, func=2 Nov 6 21:50:55 maggie kernel: class=0c-03-00, hdrtype=0x00, mfdev=0 Nov 6 21:50:55 maggie kernel: cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=c, irq=18 Nov 6 21:50:55 maggie kernel: pci0:0:29:2: reprobing on driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x8086, dev=0x27cb, revid=0x02 Nov 6 21:50:55 maggie kernel: domain=0, bus=0, slot=29, func=3 Nov 6 21:50:55 maggie kernel: class=0c-03-00, hdrtype=0x00, mfdev=0 Nov 6 21:50:55 maggie kernel: cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=d, irq=16 Nov 6 21:50:55 maggie kernel: pci0:0:29:3: reprobing on driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x8086, dev=0x27cc, revid=0x02 Nov 6 21:50:55 maggie kernel: domain=0, bus=0, slot=29, func=7 Nov 6 21:50:55 maggie kernel: class=0c-03-20, hdrtype=0x00, mfdev=0 Nov 6 21:50:55 maggie kernel: cmdreg=0x0006, statreg=0x0290, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=a, irq=23 Nov 6 21:50:55 maggie kernel: powerspec 2 supports D0 D3 current D0 Nov 6 21:50:55 maggie kernel: pci0:0:29:7: reprobing on driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x8086, dev=0x27da, revid=0x02 Nov 6 21:50:55 maggie kernel: domain=0, bus=0, slot=31, func=3 Nov 6 21:50:55 maggie kernel: class=0c-05-00, hdrtype=0x00, mfdev=0 Nov 6 21:50:55 maggie kernel: cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=b, irq=19 Nov 6 21:50:55 maggie kernel: pci0:0:31:3: reprobing on driver added Nov 6 21:50:55 maggie kernel: pci2: driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x8086, dev=0x4222, revid=0x02 Nov 6 21:50:55 maggie kernel: domain=0, bus=2, slot=0, func=0 Nov 6 21:50:55 maggie kernel: class=02-80-00, hdrtype=0x00, mfdev=0 Nov 6 21:50:55 maggie kernel: cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=a, irq=16 Nov 6 21:50:55 maggie kernel: powerspec 2 supports D0 D3 current D0 Nov 6 21:50:55 maggie kernel: MSI supports 1 message, 64 bit Nov 6 21:50:55 maggie kernel: pci0:2:0:0: reprobing on driver added Nov 6 21:50:55 maggie kernel: pci3: driver added Nov 6 21:50:55 maggie kernel: pci5: driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x1180, dev=0x0822, revid=0x18 Nov 6 21:50:55 maggie kernel: domain=0, bus=5, slot=9, func=2 Nov 6 21:50:55 maggie kernel: class=08-05-00, hdrtype=0x00, mfdev=1 Nov 6 21:50:55 maggie kernel: cmdreg=0x0000, statreg=0x0210, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=c, irq=22 Nov 6 21:50:55 maggie kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Nov 6 21:50:55 maggie kernel: pci0:5:9:2: reprobing on driver added Nov 6 21:50:55 maggie kernel: sdhci0: mem 0xd8002800-0xd80028ff irq 22 at device 9.2 on pci5 Nov 6 21:50:55 maggie kernel: pcib3: sdhci0 requested memory range 0xd8002800-0xd80028ff: good Nov 6 21:50:55 maggie kernel: sdhci0-slot0: 33MHz 4bits 3.3V PIO Nov 6 21:50:55 maggie kernel: sdhci0-slot0: ============== REGISTER DUMP ============== Nov 6 21:50:55 maggie kernel: sdhci0-slot0: Sys addr: 0x00000000 | Version: 0x00000200 Nov 6 21:50:55 maggie kernel: sdhci0-slot0: Blk size: 0x00000000 | Blk cnt: 0x00000000 Nov 6 21:50:55 maggie kernel: sdhci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000000 Nov 6 21:50:55 maggie kernel: sdhci0-slot0: Present: 0x01fa0000 | Host ctl: 0x00000000 Nov 6 21:50:55 maggie kernel: sdhci0-slot0: Power: 0x00000000 | Blk gap: 0x00000000 Nov 6 21:50:55 maggie kernel: sdhci0-slot0: Wake-up: 0x00000000 | Clock: 0x00000000 Nov 6 21:50:55 maggie kernel: sdhci0-slot0: Timeout: 0x0000000c | Int stat: 0x00000000 Nov 6 21:50:55 maggie kernel: sdhci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb Nov 6 21:50:55 maggie kernel: sdhci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 Nov 6 21:50:55 maggie kernel: sdhci0-slot0: Caps: 0x01c021a1 | Max curr: 0x00000040 Nov 6 21:50:55 maggie kernel: sdhci0-slot0: =========================================== Nov 6 21:50:55 maggie kernel: sdhci0: 1 slot(s) allocated Nov 6 21:50:55 maggie kernel: sdhci0: [MPSAFE] Nov 6 21:50:55 maggie kernel: sdhci0: [ITHREAD] Nov 6 21:50:55 maggie kernel: found-> vendor=0x1180, dev=0x0843, revid=0x00 Nov 6 21:50:55 maggie kernel: domain=0, bus=5, slot=9, func=3 Nov 6 21:50:55 maggie kernel: class=08-80-00, hdrtype=0x00, mfdev=1 Nov 6 21:50:55 maggie kernel: cmdreg=0x0002, statreg=0x0210, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=c, irq=255 Nov 6 21:50:55 maggie kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Nov 6 21:50:55 maggie kernel: pci0:5:9:3: reprobing on driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x1180, dev=0x0592, revid=0x09 Nov 6 21:50:55 maggie kernel: domain=0, bus=5, slot=9, func=4 Nov 6 21:50:55 maggie kernel: class=08-80-00, hdrtype=0x00, mfdev=1 Nov 6 21:50:55 maggie kernel: cmdreg=0x0002, statreg=0x0210, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=c, irq=255 Nov 6 21:50:55 maggie kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Nov 6 21:50:55 maggie kernel: pci0:5:9:4: reprobing on driver added Nov 6 21:50:55 maggie kernel: found-> vendor=0x1180, dev=0x0852, revid=0x04 Nov 6 21:50:55 maggie kernel: domain=0, bus=5, slot=9, func=5 Nov 6 21:50:55 maggie kernel: class=08-80-00, hdrtype=0x00, mfdev=1 Nov 6 21:50:55 maggie kernel: cmdreg=0x0002, statreg=0x0210, cachelnsz=0 (dwords) Nov 6 21:50:55 maggie kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Nov 6 21:50:55 maggie kernel: intpin=c, irq=255 Nov 6 21:50:55 maggie kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Nov 6 21:50:55 maggie kernel: pci0:5:9:5: reprobing on driver added ------------------------------------------------------------------------------------------- Card insertion: Nov 6 21:54:26 maggie kernel: sdhci0-slot0: got interrupt 40 Nov 6 21:54:26 maggie kernel: sdhci0-slot0: Card inserted Nov 6 21:54:27 maggie kernel: mmc0: on sdhci0 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 0 arg 0 flags 64 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 8 arg 426 flags 101 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1073741824 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 0 arg 0 flags 64 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 8 arg 426 flags 101 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-flot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 0 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 41 arg 1090486272 flags 97 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 2 arg 0 flags 103 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 3 arg 0 flags 101 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 9 arg 131072 flags 103 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 7 arg 131072 flags 29 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 131072 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 51 arg 0 flags 53 data 8 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 6 arg 16777215 flags 53 data 64 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 7 arg 0 flags 0 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 7 arg 131072 flags 29 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 6 arg 2164260848 flags 53 data 64 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 7 arg 0 flags 0 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: mmc0: setting transfer rate to 30.000MHz Nov 6 21:54:27 maggie kernel: mmcsd0: 1924MB at mmc0 16MHz/4bit Nov 6 21:54:27 maggie kernel: GEOM: new disk mmcsd0 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 7 arg 131072 flags 29 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 3 Nov 6 21:54:27 maggie kernel: mmc0: setting bus width to 4 bits Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 55 arg 131072 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 6 arg 2 flags 21 data 0 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 1 Nov 6 21:54:27 maggie kernel: Len 512 0-1 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 0-1 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 1-2 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 512 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 3940351-3940352 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 2017459712 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 3940351-3940352 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 2017459712 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 8192 128-144 flags 0xa sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 18 arg 65536 flags 53 data 8192 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 22 Nov 6 21:54:27 maggie kernel: Len 8192 16-32 flags 0xa sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 18 arg 8192 flags 53 data 8192 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 22 Nov 6 21:54:27 maggie kernel: Len 8192 0-16 flags 0xa sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 18 arg 0 flags 53 data 8192 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 22 Nov 6 21:54:27 maggie kernel: Len 8192 512-528 flags 0xa sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 18 arg 262144 flags 53 data 8192 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 22 Nov 6 21:54:27 maggie kernel: Len 512 64-65 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 32768 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 0-1 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 2-3 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 1024 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 16-17 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 8192 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 128-129 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 65536 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 0-1 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 1-2 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 512 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 0-1 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 253-254 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 254-255 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 130048 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 3940351-3940352 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 2017459712 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 3940351-3940352 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 2017459712 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 8192 381-397 flags 0xa sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 18 arg 195072 flags 53 data 8192 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 22 Nov 6 21:54:27 maggie kernel: Len 8192 269-285 flags 0xa sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 18 arg 137728 flags 53 data 8192 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 22 Nov 6 21:54:27 maggie kernel: Len 8192 253-269 flags 0xa sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 18 arg 129536 flags 53 data 8192 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 22 Nov 6 21:54:27 maggie kernel: Len 8192 765-781 flags 0xa sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 18 arg 391680 flags 53 data 8192 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 22 Nov 6 21:54:27 maggie kernel: Len 512 317-318 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 162304 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 253-254 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: GEOM_LABEL: Label for provider mmcsd0s1 is msdosfs/ . Nov 6 21:54:27 maggie kernel: Len 512 255-256 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 130560 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 269-270 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 137728 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 381-382 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 195072 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 253-254 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 253-254 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 253-254 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 129536 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 254-255 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 130048 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:54:27 maggie kernel: Len 512 3940351-3940352 flags 0x2 sz 512 Nov 6 21:54:27 maggie kernel: sdhci_request cmd op 17 arg 2017459712 flags 53 data 512 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:54:27 maggie kernel: sdhci0-slot0: got interrupt 2 -------------------------------------------------------------------------- yay, fdisk works: lars@pts/3 # fdisk /dev/mmcsd0 ******* Working on device /dev/mmcsd0 ******* parameters extracted from in-core disklabel are: cylinders=245 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=245 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6 (0x06),(Primary 'big' DOS (>= 32MB)) start 253, size 3940099 (1923 Meg), flag 0 beg: cyl 0/ head 4/ sector 2; end: cyl 977/ head 17/ sector 17 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: Nov 6 21:55:33 maggie kernel: Len 512 0-1 flags 0x2 sz 512 Nov 6 21:55:33 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 512 Nov 6 21:55:33 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:55:33 maggie kernel: sdhci0-slot0: got interrupt 2 Nov 6 21:55:33 maggie kernel: Len 512 0-1 flags 0x2 sz 512 Nov 6 21:55:33 maggie kernel: sdhci_request cmd op 17 arg 0 flags 53 data 512 Nov 6 21:55:33 maggie kernel: sdhci0-slot0: got interrupt 21 Nov 6 21:55:33 maggie kernel: sdhci0-slot0: got interrupt 2 And mounting also works! \o/ lars@pts/3 # touch /mnt/foo Thu, 06. Nov 2008, 21:57:01 [maggie:/usr/src/sys/modules/mmc] lars@pts/3 # ls /mnt foo And now also the sdhci card is recognized properly and I can mount it without a panic. Thanks a lot! :) > >Sorry for the lengthy mail :) > > Thanks, I like such mails, it's like a hunting. :) Yeah, I had (still have on the other notebook) some bait for you. :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081106/4f5a9daa/attachment.pgp From mike at sentex.net Thu Nov 6 14:03:47 2008 From: mike at sentex.net (Mike Tancsa) Date: Thu Nov 6 14:04:00 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200811051548.mA5Fmsot040177@lava.sentex.ca> References: <200810092344.10388.nick@van-laarhoven.org> <200811051548.mA5Fmsot040177@lava.sentex.ca> Message-ID: <200811062203.mA6M3ij3048835@lava.sentex.ca> At 10:48 AM 11/5/2008, Mike Tancsa wrote: >At 04:44 PM 10/9/2008, Nick Hibma wrote: >>Just now I have committed a driver for Option and Huawei cards previously >>supported by the ubsa driver. More information is in the commit message. >> >>I am looking for people who would be able to provide more information after >>testing with the 3G cards branded by: > >Hi, > I gave it a try on the Sierra USB card and it seems to work > really well on RELENG_7! There is however also a mini-pci express > version of the Sierra card, the MC8775. For the archives, I was able to get the card working with the latest version of the driver from the SVN tree! (http://people.freebsd.org/~n_hibma/u3g.html) For the hardware, I used http://www.pcengines.ch/alix6b2.htm with RELENG_7 and nanobsd. The board has dual SIM slots, but there are no drivers to switch between the two, so just the top one works. When I bought the mini-pciexpress card (or PCI Express Mini Card), it was listed as a MC8775, where as ati3 shows a Sierra MC8781. I bought it on ebay from the US and it works fine using my Roger's blackbery SIM here in Ontario, Canada. # cat /var/run/dmesg.boot Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #0: Thu Nov 6 12:05:41 EST 2008 mdtancsa@nanobsd2.sentex.ca:/usr/obj/nanobsd.alix/usr/src/sys/nano5501 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Geode(TM) Integrated Processor by AMD PCS (498.05-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x5a2 Stepping = 2 Features=0x88a93d AMD Features=0xc0400000 real memory = 268435456 (256 MB) avail memory = 253202432 (241 MB) pnpbios: Bad PnP BIOS data checksum K6-family MTRR support enabled (2 registers) cryptosoft0: on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 ... u3gstub0: at uhub0 port 2 (addr 2) disconnected u3gstub0: detached .... ucom0: on uhub0 ucom0: configured 3 serial ports (U0.%d) # cu -l /dev/cuaU0.2 Connected ati Manufacturer: Sierra Wireless, Inc. Model: MC8781 Revision: F1_0_0_4CAP C:/WS/FW/F1_0_0_4CAP/MSM7200R3/SRC/AMSS 2007/09/25 18:39:23 IMEI: 356685011922513 IMEI SV: 4 FSN: D350568535811 3GPP Release 6 +GCAP: +CGSM,+DS,+ES at!GSTATUS? !GSTATUS: Current Time: 3455 Temperature: 30 Bootup Time: 3201 Mode: ONLINE System mode: WCDMA PS state: Not attached WCDMA band: WCDMA800 GSM band: Unknown WCDMA channel: 1037 GSM channel: 65535 GMM (PS) state:DEREGISTERED NO IMSI MM (CS) state: IDLE NO IMSI WCDMA L1 State:L1M_PCH_SLEEP RRC State: DISCONNECTED RX level (dBm):-87 OK at^SYSINFO ^SYSINFO: 1,0,1,5,255 From keramida at freebsd.org Thu Nov 6 14:07:00 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Thu Nov 6 14:07:08 2008 Subject: Cannot buildworld in CURRENT In-Reply-To: <491358CD.4090601@lissyara.su> (Alex Keda's message of "Thu, 06 Nov 2008 23:51:25 +0300") References: <49135844.7010500@lissyara.su> <491358CD.4090601@lissyara.su> Message-ID: <87bpwsseof.fsf@kobe.laptop> On Thu, 06 Nov 2008 23:51:25 +0300, Alex Keda wrote: > Alex Keda ?????: >> ===> usr.bin/du (all) >> cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall >> -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes >> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual >> -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter >> -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls >> -Wno-pointer-sign -c /usr/src/usr.bin/du/du.c >> cc1: warnings being treated as errors >> /usr/src/usr.bin/du/du.c: In function 'main': >> /usr/src/usr.bin/du/du.c:276: warning: format '%jd' expects type >> intmax_t', but argument 2 has type 'long long int' >> *** Error code 1 >> >> Stop in /usr/src/usr.bin/du. >> *** Error code 1 >> ============ >> updated 2 hour ago > > acer# uname -a > FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: > Tue Nov 4 23:23:29 MSK 2008 > root@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console > amd64 > acer# Oops, this one slipped in because I only built in i386 and not amd64. Can you try this patch? %%% diff -r aa58af068624 usr.bin/du/du.c --- a/usr.bin/du/du.c Thu Nov 06 23:29:46 2008 +0200 +++ b/usr.bin/du/du.c Thu Nov 06 23:51:48 2008 +0200 @@ -273,7 +273,8 @@ (void)printf("\t%s\n", p->fts_path); } else { (void)printf("%jd\t%s\n", - howmany(p->fts_bignum * cblocksize, + (intmax_t)howmany( + p->fts_bignum * cblocksize, blocksize), p->fts_path); } } %%% From mav at FreeBSD.org Thu Nov 6 14:12:46 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Nov 6 14:12:53 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106210545.GF161@e.0x20.net> References: <48DEA8E7.2080503@FreeBSD.org> <20081106180556.GH8256@e.0x20.net> <4913345F.2050801@FreeBSD.org> <20081106.112338.1564836080.imp@bsdimp.com> <20081106184017.GB161@e.0x20.net> <49133F2B.4080801@FreeBSD.org> <20081106192353.GD161@e.0x20.net> <49134D57.1050003@FreeBSD.org> <20081106210545.GF161@e.0x20.net> Message-ID: <49136BDA.6060301@FreeBSD.org> Lars Engels wrote: > Yes, that's what I have used: > lars@pts/4 # ls ~/local-modules/sdhci/ > mmc.20081011.tgz sdhci.20081019.tgz sdhci_mod.20081008.tgz That should not be bad, but the latest version is now committed to the HEAD. > I forgot to re-built mmcsd before, my fault... > Now I re-built and loaded the modules again: > > And now also the sdhci card is recognized properly and I can mount it without a panic. > Thanks a lot! :) Welcome. :) >>> Sorry for the lengthy mail :) >> Thanks, I like such mails, it's like a hunting. :) > > Yeah, I had (still have on the other notebook) some bait for you. :) Fighting unknown hardware without touching it is probably the next level of enlightenment. :) I know, there is no spoon! :) -- Alexander Motin From trebestie at gmail.com Thu Nov 6 14:20:14 2008 From: trebestie at gmail.com (Diego Depaoli) Date: Thu Nov 6 14:20:21 2008 Subject: Usb2 and hal issue In-Reply-To: <200811060900.59772.hselasky@c2i.net> References: <83e5fb980811051638n5f9a1a5dr60160ed7e2ed7a1c@mail.gmail.com> <200811060900.59772.hselasky@c2i.net> Message-ID: <83e5fb980811061420k79f6c845yd9263bea2834e0cd@mail.gmail.com> 2008/11/6 Hans Petter Selasky : > Hald is looping trying to open the wrong USB device. If hald is using > libusb-0.1.12, Apparently It doesn't and Makefile contains two --disable-usb options. Since pkg_info -R lists a lot of other ports requiring libusb-0.1.12 I think each one may be linked with libusb20, or I'm wrong? Regards -- Diego Depaoli From tinderbox at freebsd.org Thu Nov 6 14:31:40 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Nov 6 14:31:58 2008 Subject: [head tinderbox] failure on ia64/ia64 Message-ID: <20081106223138.06BCB73039@freebsd-current.sentex.ca> TB --- 2008-11-06 21:19:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-06 21:19:00 - starting HEAD tinderbox run for ia64/ia64 TB --- 2008-11-06 21:19:00 - cleaning the object tree TB --- 2008-11-06 21:19:32 - cvsupping the source tree TB --- 2008-11-06 21:19:32 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/ia64/ia64/supfile TB --- 2008-11-06 21:19:40 - building world (CFLAGS=-O -pipe) TB --- 2008-11-06 21:19:40 - cd /src TB --- 2008-11-06 21:19:40 - /usr/bin/make -B buildworld >>> World build started on Thu Nov 6 21:19:41 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] ===> usr.bin/dirname (all) cc -O -pipe -c /src/usr.bin/dirname/dirname.c cc -O -pipe -o dirname dirname.o ===> usr.bin/du (all) cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/usr.bin/du/du.c cc1: warnings being treated as errors /src/usr.bin/du/du.c: In function 'main': /src/usr.bin/du/du.c:276: warning: format '%jd' expects type 'intmax_t', but argument 2 has type 'long long int' *** Error code 1 Stop in /src/usr.bin/du. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-06 22:31:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-06 22:31:37 - ERROR: failed to build world TB --- 2008-11-06 22:31:37 - tinderbox aborted TB --- 3174.26 user 351.07 system 4356.95 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From mav at FreeBSD.org Thu Nov 6 14:48:17 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Nov 6 14:48:34 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <20081106.101047.163264510.imp@bsdimp.com> References: <49130918.5030904@FreeBSD.org> <20081106163729.clcw2eulgk0k4w0c@0x20.net> <49131109.2020601@FreeBSD.org> <20081106.101047.163264510.imp@bsdimp.com> Message-ID: <4913742E.9040801@FreeBSD.org> M. Warner Losh wrote: > In message: <49131109.2020601@FreeBSD.org> > Alexander Motin writes: > : Lars Engels wrote: > : > 1. How can I tune the PCI configuration? With pciconf -w or so? > : > : Yes. `pciconf -r -b device addr` to read and `pciconf -w -b device addr > : value` to write. > > I have changes that almost make my TI card do it. > > : > 2. Unfortunately the sysctl did not change a thing with regard to the > : > Card reader. > : > : Have you added it to the loader.conf and rebooted? > : > : > 3. I added the chip ID and the second device is now recognized as a > : > sdhci device but still does not see any card inserted: > : > > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify base > : > clock frequency. > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't specify > : > timeout clock frequency. > : > Nov 6 16:32:20 NB0117232 kernel: sdhci1: Hardware doesn't report any > : > support voltages. > : > : Looks like it is not enough compatible, or even not compatible. > > Chances are good that you need to the workaround to turn on these > things. Here is some datasheet I have found for R5C832, but it looks not too detailed to say something for sure: http://www.aeneas.com.cn/PDF/Ricoh/2005/R5C832E1%5B1%5D.00.pdf At least it says that it's MMC interface is single-bit, while standard SD host controller has 4 bit's bus. -- Alexander Motin From hselasky at c2i.net Thu Nov 6 15:34:10 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Nov 6 15:34:23 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081106210300.GA1595@wep4035.physik.uni-wuerzburg.de> References: <200810251925.47273.hselasky@c2i.net> <20081106191230.GA47600@wep4035.physik.uni-wuerzburg.de> <20081106210300.GA1595@wep4035.physik.uni-wuerzburg.de> Message-ID: <200811070036.15816.hselasky@c2i.net> On Thursday 06 November 2008, Alexey Shuvaev wrote: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > _witness_debugger() at _witness_debugger+0x49 > witness_checkorder() at witness_checkorder+0x7e6 > _sx_xlock() at _sx_xlock+0x44 > vm_map_lookup() at vm_map_lookup+0x47 > vm_fault() at vm_fault+0xfe > trap_pfault() at trap_pfault+0x1fa > trap() at trap+0x201 > calltrap() at calltrap+0x8 > --- trap 0xc, rip = 0xffffffff804b2466, rsp = 0xfffffffeba7f8ac0, rbp = > 0xfffffffeba7f8b00 --- bcopy() at bcopy+0x16 > usb2_bdma_pre_sync() at usb2_bdma_pre_sync+0x35 > usb2_bdma_work_loop() at usb2_bdma_work_loop+0x29b > usb2_command_wrapper() at usb2_command_wrapper+0x76 > usb2_callback_wrapper() at usb2_callback_wrapper+0xfd > usb2_command_wrapper() at usb2_command_wrapper+0x76 > usb2_callback_proc() at usb2_callback_proc+0x68 > usb2_process() at usb2_process+0xc0 Hi Alexey, This looks more like a busdma problem to me. "bcopy()" is called from within "bus_dmamap_sync()". Maybe you can figure out if it is the source or the destination address that fails? Looks like your system has started bouncing data to the 32-bit address range. --HPS From tinderbox at freebsd.org Thu Nov 6 15:34:11 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Nov 6 15:34:34 2008 Subject: [head tinderbox] failure on sparc64/sparc64 Message-ID: <20081106233408.326F773039@freebsd-current.sentex.ca> TB --- 2008-11-06 22:31:38 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-06 22:31:38 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-11-06 22:31:38 - cleaning the object tree TB --- 2008-11-06 22:32:13 - cvsupping the source tree TB --- 2008-11-06 22:32:13 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-06 22:32:21 - building world (CFLAGS=-O -pipe) TB --- 2008-11-06 22:32:21 - cd /src TB --- 2008-11-06 22:32:21 - /usr/bin/make -B buildworld >>> World build started on Thu Nov 6 22:32:23 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] ===> usr.bin/dirname (all) cc -O -pipe -fstack-protector -c /src/usr.bin/dirname/dirname.c cc -O -pipe -fstack-protector -o dirname dirname.o ===> usr.bin/du (all) cc -O -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/usr.bin/du/du.c cc1: warnings being treated as errors /src/usr.bin/du/du.c: In function 'main': /src/usr.bin/du/du.c:276: warning: format '%jd' expects type 'intmax_t', but argument 2 has type 'long long int' *** Error code 1 Stop in /src/usr.bin/du. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-06 23:34:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-06 23:34:07 - ERROR: failed to build world TB --- 2008-11-06 23:34:07 - tinderbox aborted TB --- 2657.12 user 339.60 system 3749.73 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From hselasky at c2i.net Thu Nov 6 15:36:19 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Thu Nov 6 15:36:27 2008 Subject: Usb2 and hal issue In-Reply-To: <83e5fb980811061420k79f6c845yd9263bea2834e0cd@mail.gmail.com> References: <83e5fb980811051638n5f9a1a5dr60160ed7e2ed7a1c@mail.gmail.com> <200811060900.59772.hselasky@c2i.net> <83e5fb980811061420k79f6c845yd9263bea2834e0cd@mail.gmail.com> Message-ID: <200811070038.27601.hselasky@c2i.net> On Thursday 06 November 2008, Diego Depaoli wrote: > 2008/11/6 Hans Petter Selasky : > > Hald is looping trying to open the wrong USB device. If hald is using > > libusb-0.1.12, > > Apparently It doesn't and Makefile contains two --disable-usb options. > Since pkg_info -R lists a lot of other ports requiring libusb-0.1.12 I > think each one may be linked with libusb20, or I'm wrong? > > Regards That's right. The new FreeBSD libusb20 implement all globals found in libusb-0.1.12, except the C++ part. You can also just make a symlink in the libraries directories for testing. --HPS From max at love2party.net Thu Nov 6 15:49:43 2008 From: max at love2party.net (Max Laier) Date: Thu Nov 6 15:49:51 2008 Subject: [head tinderbox] failure on sparc64/sparc64 In-Reply-To: <20081106233408.326F773039@freebsd-current.sentex.ca> References: <20081106233408.326F773039@freebsd-current.sentex.ca> Message-ID: <200811070049.40852.max@love2party.net> On Friday 07 November 2008 00:34:08 FreeBSD Tinderbox wrote: > TB --- 2008-11-06 22:31:38 - tinderbox 2.3 running on > freebsd-current.sentex.ca TB --- 2008-11-06 22:31:38 - starting HEAD > tinderbox run for sparc64/sparc64 TB --- 2008-11-06 22:31:38 - cleaning the > object tree > TB --- 2008-11-06 22:32:13 - cvsupping the source tree > TB --- 2008-11-06 22:32:13 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s > /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-06 22:32:21 - > building world (CFLAGS=-O -pipe) > TB --- 2008-11-06 22:32:21 - cd /src > TB --- 2008-11-06 22:32:21 - /usr/bin/make -B buildworld > > >>> World build started on Thu Nov 6 22:32:23 UTC 2008 > >>> Rebuilding the temporary build tree > >>> stage 1.1: legacy release compatibility shims > >>> stage 1.2: bootstrap tools > >>> stage 2.1: cleaning up the object tree > >>> stage 2.2: rebuilding the object tree > >>> stage 2.3: build tools > >>> stage 3: cross tools > >>> stage 4.1: building includes > >>> stage 4.2: building libraries > >>> stage 4.3: make dependencies > >>> stage 4.4: building everything > > [...] > ===> usr.bin/dirname (all) > cc -O -pipe -fstack-protector -c /src/usr.bin/dirname/dirname.c > cc -O -pipe -fstack-protector -o dirname dirname.o > ===> usr.bin/du (all) > cc -O -pipe -fstack-protector -Wsystem-headers -Werror -Wall > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter > -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls > -Wno-pointer-sign -c /src/usr.bin/du/du.c cc1: warnings being treated as > errors > /src/usr.bin/du/du.c: In function 'main': > /src/usr.bin/du/du.c:276: warning: format '%jd' expects type 'intmax_t', > but argument 2 has type 'long long int' *** Error code 1 ups ... my bad, I'll fix it. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From max at love2party.net Thu Nov 6 16:02:20 2008 From: max at love2party.net (Max Laier) Date: Thu Nov 6 16:02:40 2008 Subject: [head tinderbox] failure on sparc64/sparc64 In-Reply-To: <20081106233408.326F773039@freebsd-current.sentex.ca> References: <20081106233408.326F773039@freebsd-current.sentex.ca> Message-ID: <200811070049.40852.max@love2party.net> On Friday 07 November 2008 00:34:08 FreeBSD Tinderbox wrote: > TB --- 2008-11-06 22:31:38 - tinderbox 2.3 running on > freebsd-current.sentex.ca TB --- 2008-11-06 22:31:38 - starting HEAD > tinderbox run for sparc64/sparc64 TB --- 2008-11-06 22:31:38 - cleaning the > object tree > TB --- 2008-11-06 22:32:13 - cvsupping the source tree > TB --- 2008-11-06 22:32:13 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s > /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-06 22:32:21 - > building world (CFLAGS=-O -pipe) > TB --- 2008-11-06 22:32:21 - cd /src > TB --- 2008-11-06 22:32:21 - /usr/bin/make -B buildworld > > >>> World build started on Thu Nov 6 22:32:23 UTC 2008 > >>> Rebuilding the temporary build tree > >>> stage 1.1: legacy release compatibility shims > >>> stage 1.2: bootstrap tools > >>> stage 2.1: cleaning up the object tree > >>> stage 2.2: rebuilding the object tree > >>> stage 2.3: build tools > >>> stage 3: cross tools > >>> stage 4.1: building includes > >>> stage 4.2: building libraries > >>> stage 4.3: make dependencies > >>> stage 4.4: building everything > > [...] > ===> usr.bin/dirname (all) > cc -O -pipe -fstack-protector -c /src/usr.bin/dirname/dirname.c > cc -O -pipe -fstack-protector -o dirname dirname.o > ===> usr.bin/du (all) > cc -O -pipe -fstack-protector -Wsystem-headers -Werror -Wall > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter > -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls > -Wno-pointer-sign -c /src/usr.bin/du/du.c cc1: warnings being treated as > errors > /src/usr.bin/du/du.c: In function 'main': > /src/usr.bin/du/du.c:276: warning: format '%jd' expects type 'intmax_t', > but argument 2 has type 'long long int' *** Error code 1 ups ... my bad, I'll fix it. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From tinderbox at freebsd.org Thu Nov 6 16:07:38 2008 From: tinderbox at freebsd.org (FreeBSD Tinderbox) Date: Thu Nov 6 16:07:44 2008 Subject: [head tinderbox] failure on sparc64/sun4v Message-ID: <20081107000735.2B4E573039@freebsd-current.sentex.ca> TB --- 2008-11-06 23:11:44 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-06 23:11:44 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-11-06 23:11:44 - cleaning the object tree TB --- 2008-11-06 23:12:11 - cvsupping the source tree TB --- 2008-11-06 23:12:11 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-11-06 23:12:18 - building world (CFLAGS=-O -pipe) TB --- 2008-11-06 23:12:18 - cd /src TB --- 2008-11-06 23:12:18 - /usr/bin/make -B buildworld >>> World build started on Thu Nov 6 23:12:20 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] ===> usr.bin/dirname (all) cc -O -pipe -fstack-protector -c /src/usr.bin/dirname/dirname.c cc -O -pipe -fstack-protector -o dirname dirname.o ===> usr.bin/du (all) cc -O -pipe -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c /src/usr.bin/du/du.c cc1: warnings being treated as errors /src/usr.bin/du/du.c: In function 'main': /src/usr.bin/du/du.c:276: warning: format '%jd' expects type 'intmax_t', but argument 2 has type 'long long int' *** Error code 1 Stop in /src/usr.bin/du. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-07 00:07:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-07 00:07:35 - ERROR: failed to build world TB --- 2008-11-07 00:07:35 - tinderbox aborted TB --- 2631.84 user 332.70 system 3350.66 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From todorov at paladin.bulgarpress.com Thu Nov 6 14:27:57 2008 From: todorov at paladin.bulgarpress.com (Todorov) Date: Thu Nov 6 17:05:19 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200811062203.mA6M3ij3048835@lava.sentex.ca> References: <200810092344.10388.nick@van-laarhoven.org> <200811051548.mA5Fmsot040177@lava.sentex.ca> <200811062203.mA6M3ij3048835@lava.sentex.ca> Message-ID: <49136B55.8040704@paladin.bulgarpress.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is this source supposed to support PCMCIA Huawei E630 card? I can give a test if so... Regards, Mike Tancsa ??????: | At 10:48 AM 11/5/2008, Mike Tancsa wrote: |> At 04:44 PM 10/9/2008, Nick Hibma wrote: |>> Just now I have committed a driver for Option and Huawei cards |>> previously |>> supported by the ubsa driver. More information is in the commit message. |>> |>> I am looking for people who would be able to provide more information |>> after |>> testing with the 3G cards branded by: |> |> Hi, |> I gave it a try on the Sierra USB card and it seems to work |> really well on RELENG_7! There is however also a mini-pci express |> version of the Sierra card, the MC8775. | | | For the archives, I was able to get the card working with the latest | version of the driver from the SVN tree! | (http://people.freebsd.org/~n_hibma/u3g.html) | | For the hardware, I used | http://www.pcengines.ch/alix6b2.htm | with RELENG_7 and nanobsd. The board has dual SIM slots, but there are | no drivers to switch between the two, so just the top one works. | | When I bought the mini-pciexpress card (or PCI Express Mini Card), it | was listed as a MC8775, where as ati3 shows a Sierra MC8781. I bought | it on ebay from the US and it works fine using my Roger's blackbery SIM | here in Ontario, Canada. | | | # cat /var/run/dmesg.boot | Copyright (c) 1992-2008 The FreeBSD Project. | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 | The Regents of the University of California. All rights reserved. | FreeBSD is a registered trademark of The FreeBSD Foundation. | FreeBSD 7.1-PRERELEASE #0: Thu Nov 6 12:05:41 EST 2008 | mdtancsa@nanobsd2.sentex.ca:/usr/obj/nanobsd.alix/usr/src/sys/nano5501 | Timecounter "i8254" frequency 1193182 Hz quality 0 | CPU: Geode(TM) Integrated Processor by AMD PCS (498.05-MHz 586-class CPU) | Origin = "AuthenticAMD" Id = 0x5a2 Stepping = 2 | Features=0x88a93d | AMD Features=0xc0400000 | real memory = 268435456 (256 MB) | avail memory = 253202432 (241 MB) | pnpbios: Bad PnP BIOS data checksum | K6-family MTRR support enabled (2 registers) | cryptosoft0: on motherboard | pcib0: pcibus 0 on motherboard | pci0: on pcib0 | ... | u3gstub0: at uhub0 port 2 (addr 2) disconnected | u3gstub0: detached | .... | ucom0: on uhub0 | ucom0: configured 3 serial ports (U0.%d) | | | | # cu -l /dev/cuaU0.2 | Connected | ati | Manufacturer: Sierra Wireless, Inc. | Model: MC8781 | Revision: F1_0_0_4CAP C:/WS/FW/F1_0_0_4CAP/MSM7200R3/SRC/AMSS 2007/09/25 | 18:39:23 | IMEI: 356685011922513 | IMEI SV: 4 | FSN: D350568535811 | 3GPP Release 6 | +GCAP: +CGSM,+DS,+ES | | at!GSTATUS? | !GSTATUS: | Current Time: 3455 Temperature: 30 | Bootup Time: 3201 Mode: ONLINE | System mode: WCDMA PS state: Not attached | WCDMA band: WCDMA800 GSM band: Unknown | WCDMA channel: 1037 GSM channel: 65535 | GMM (PS) state:DEREGISTERED NO IMSI | MM (CS) state: IDLE NO IMSI | | WCDMA L1 State:L1M_PCH_SLEEP RRC State: DISCONNECTED | RX level (dBm):-87 | | | OK | at^SYSINFO | ^SYSINFO: 1,0,1,5,255 | _______________________________________________ | freebsd-hardware@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-hardware | To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkTa1QACgkQibJkIG65HMcAnQCgyeSvhIubmFifIh/SDntGY65M 3fcAmgNG7cL5zrBuCvhizskwQEgGZ35/ =Xg4D -----END PGP SIGNATURE----- From weongyo.jeong at gmail.com Thu Nov 6 22:01:44 2008 From: weongyo.jeong at gmail.com (Weongyo Jeong) Date: Thu Nov 6 22:01:50 2008 Subject: CFT: Realtek 8187L wireless USB driver - urtw(4) Message-ID: <20081107052937.GA19400@freebsd.weongyo.org> Dear all, This driver supports 8187L which is one of Realtek's 8187x series and I'm looking for testers who have this device. :-) With lack of H/W I can't add codes for 8187/8187B devices that AFAIK they can share a lot of codes and can be supported without modifying many part of codes. In my environment the basic features (WEP/WPA and etc ...) are worked and the driver based on USB1 (not USB2) can be found at as follows: http://people.freebsd.org/~weongyo/urtw_20081107.tar.gz I think a current problem of urtw(4) is poor RX/TX performance about 8 ~ 10Mbps due to mishandling the rate controlling and I'm not sure it would easy to fix it without documents but I expect the connection would be stable. Please let me know if you encounter any problems or opinions. Always patches to improve or enhance features are welcome! regards, Weongyo Jeong From pyunyh at gmail.com Thu Nov 6 22:49:30 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Thu Nov 6 22:49:38 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <20081031034443.GF82781@cdnetworks.co.kr> References: <20081030040637.GA78796@cdnetworks.co.kr> <20081030114845.GE78796@cdnetworks.co.kr> <20081031034443.GF82781@cdnetworks.co.kr> Message-ID: <20081107064724.GA11486@cdnetworks.co.kr> On Fri, Oct 31, 2008 at 12:44:43PM +0900, To freebsd-current@FreeBSD.org wrote: > On Thu, Oct 30, 2008 at 08:48:45PM +0900, To freebsd-current@FreeBSD.org wrote: > > On Thu, Oct 30, 2008 at 01:06:37PM +0900, To freebsd-current@FreeBSD.org wrote: > > > > > > Hi, > > > > > > I had been working on writing a driver for Atheros AR8121(L1E), > > > AR8113/AR8114(L2E) ethernet controllers since Jeremy Chadwick sent > > > the hardware to me. I think it's feature complete state and time > > > for more testing for stability or some edge cases. I guess AR81xx > > > is commonly found on newer Asus EeePC or P5Q series of Asus > > > motherboard. If you have AR81xx controller would you give it spin > > > and let me know how it goes? You can get the latest driver at the > > > following URL. > > > http://people.freebsd.org/~yongari/ate/if_ate.c > > > http://people.freebsd.org/~yongari/ate/if_atereg.h > > > http://people.freebsd.org/~yongari/ate/if_atevar.h > > > http://people.freebsd.org/~yongari/ate/Makefile > > > or > > > http://people.freebsd.org/~yongari/ate/ate.20081030.tar.gz > > > The driver should build without problems on CURRENT, stable/7. > > > > > > ATM the driver supports the following hardware features. > > > - TSO > > > - Rx TCP/UDP/IP checksum offload > > > - VLAN tag insertion/stripping > > > - Jumbo frame > > > - WOL > > > It seems that hardware supports Tx checksum offload but I couldn't > > > make it work for TCP segments. Only short TCP segments seem to work > > > so I disabled Tx checksum offload. > > > Note, the hardware does not support descriptor based DMA on Rx side > > > so driver have to copy recevied frames to pass them to upper stack > > > so it will consume a lot of CPU cycles if you push the hardware to > > > the limit. > > > > > > > As bruffer pointed out the device name chosen conflicts with other > > driver in tree so I renamed it to ale(4).The URL for the driver is > > http://people.freebsd.org/~yongari/ale/if_ale.c > > http://people.freebsd.org/~yongari/ale/if_alereg.h > > http://people.freebsd.org/~yongari/ale/if_alevar.h > > http://people.freebsd.org/~yongari/ale/Makefile > > or > > http://people.freebsd.org/~yongari/ale/ale.20081030.tar.gz > > Sorry for confusion. > > > > FYI: > There was a typo that keep ale(4) from building on stable/7. It was > fixed now and I reuploaded related files(URLs are the same as before). Finally I've managed to make Tx checksum offload work and added one more workaround for silicon bug. As usual updated ale(4) can be found at the following URL. http://people.freebsd.org/~yongari/ale/if_ale.c http://people.freebsd.org/~yongari/ale/if_alereg.h http://people.freebsd.org/~yongari/ale/if_alevar.h http://people.freebsd.org/~yongari/ale/Makefile or http://people.freebsd.org/~yongari/ale/ale.20081107.tar.gz The workaround takes more CPU cycles than previous one but you can still saturate the link if you have fast CPU. I'll commit this version within a week unless severe issues are reported. Thanks. -- Regards, Pyun YongHyeon From koitsu at FreeBSD.org Fri Nov 7 00:02:35 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Nov 7 00:02:43 2008 Subject: USB4BSD (USB2): Microsoft 4000 keyboard unusable Message-ID: <20081107075232.GA1608@icarus.home.lan> So this weekend, as a result of some insane disk/controller/ZFS problems I experienced, followed by reproducible kernel wedging when trying to copy data to a USB flash drive, I thought I'd take the plunge and give CURRENT a shot. All went well, and so I decided to switch over to the USB2 stack to help test. Everything built (csup date: 2008/11/06 ~2200 PST) fine, no issues -- until I noticed my USB keyboard didn't function any longer. During boot0/boot2/loader, the keyboard functions (as expected, re: USB Legacy option is enabled in my BIOS), and the keyboard LEDs are lit as expected. The kernel loads, some drivers initialise, and the LEDs go off. Once the USB2 stack loads, the keyboard LEDs turn back up, but as stated, no keypresses are registered. I was forced to hook up a PS/2 keyboard. Situation is the same no matter if I try to enter single-user or not. Disabling atkbd/atkbdc via hints made no difference (other than killing my ability to use a real PS/2 keyboard), and disabling kbdmux also made no difference. In multi-user (with kbdmux enabled), I also tried doing what the last section of kbdcontrol(1) recommended, but I witnessed a series of errors during open() or ioctl(), and of course the USB keyboard still did not function. icarus# kbdcontrol -K < /dev/console kbd1 kbdmux0, type:AT 101/102 (2) icarus# kbdcontrol -a atkbd0 < /dev/kbdmux0 /dev/kbdmux0: Device busy. icarus# kbdcontrol -a ukbd0 < /dev/kbdmux0 /dev/kbdmux0: Device busy. icarus# kbdcontrol -k /dev/kbdmux0 < /dev/console kbdcontrol: cannot open /dev/kbdmux0: Device busy The keyboard in question is a Microsoft Natural Ergonomic 4000. This keyboard is known for being a real pain in the ass, since some of the multimedia keys, and the infamous F-Lock key, are HID-controlled, while alphanumeric are USB keyboard class controlled. (For sake of example, Linux has a *huge* web page dedicated to dealing with this keyboard alone.) dmesg and ls -l /dev/u* are below. Let me know if I can enable something to help debug this; if remote access is needed (once multi-user is up), I can provide it. usbus0: 12Mbps Full Speed USB v1.0 ugen0.1: at usbus0 ushub0: on usbus0 ushub0: 2 ports with 2 removable, self powered usbus1: 12Mbps Full Speed USB v1.0 ugen1.1: at usbus1 ushub1: on usbus1 ushub1: 2 ports with 2 removable, self powered usbus2: 12Mbps Full Speed USB v1.0 ugen2.1: at usbus2 ushub2: on usbus2 ushub2: 2 ports with 2 removable, self powered usbus3: 12Mbps Full Speed USB v1.0 ugen3.1: at usbus3 ushub3: on usbus3 ushub3: 2 ports with 2 removable, self powered usbus4: 480Mbps High Speed USB v2.0 ugen4.1: at usbus4 ushub4: on usbus4 ushub4: 8 ports with 8 removable, self powered acd0: DVDR at ata0-master UDMA33 ad4: 190782MB at ata2-master SATA150 ad6: 476940MB at ata3-master SATA300 ad8: 476940MB at ata4-master SATA300 ad10: 715404MB at ata5-master SATA300 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s1a ugen0.2: at usbus0 ukbd0: on usbus0 kbd2 at ukbd0 uhid0: on usbus0 Symlink: uhid0 -> usb0.2.1.16 $ ls -l /dev/u* crw------- 1 root wheel 0, 87 6 Nov 23:26 /dev/ukbd0 lrwxr-xr-x 1 root wheel 6 6 Nov 23:26 /dev/urandom -> random crwxrwxrwx 1 root operator 0, 67 6 Nov 23:26 /dev/usb -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From koitsu at FreeBSD.org Fri Nov 7 00:27:42 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Nov 7 00:27:49 2008 Subject: Kernel panic when copying data to umass device (USB4BSD) Message-ID: <20081107082740.GA1334@icarus.home.lan> Not sure if this is caused by problems with USB4BSD or not, as I can reproduce it on RELENG_7 (but there, the kernel does not panic; it just "wedges" in a loop/thread somewhere; SSH sessions remain up, but commands running stop; hitting Ctrl-T shows them in all sorts of different states, but the states never change; hitting Ctrl-Alt-Esc does in fact drop me to db>). Anyway, WRT CURRENT, here's the scenario: - Insert Sandisk U3 Cruzer (8GB) USB flash drive ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 7663MB (15695871 512 byte sectors: 255H 63S/T 977C) /storage is a ZFS pool /dev/da0s1a is a UFS1 filesystem (e.g. newfs -O1 /dev/da0s1a) # mdconfig -a -t vnode -u 0 -f /storage/7.1-BETA2-amd64-disc1.iso # mdconfig -a -t vnode -u 1 -f /storage/7.1-BETA2-i386-disc1.iso # mount /dev/md0 /iso0 # mount /dev/md1 /iso1 # mount /dev/da0s1a /mnt # cp -vpR /iso0/* /mnt The system will eventually kernel panic in the middle of this copy. I'm unable to obtain a crash dump; doing "panic" at the db> prompt causes the same trace to happen over and over, so I've taken a photo of the console. Kernel has KBD_TRACE set, hence the auto-backtrace: http://www.malkavian.com/~jdc/usb2_da0_crash.jpg -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From rea-fbsd at codelabs.ru Fri Nov 7 00:38:53 2008 From: rea-fbsd at codelabs.ru (Eygene Ryabinkin) Date: Fri Nov 7 00:39:01 2008 Subject: USB4BSD (USB2): Microsoft 4000 keyboard unusable In-Reply-To: <20081107075232.GA1608@icarus.home.lan> References: <20081107075232.GA1608@icarus.home.lan> Message-ID: <4bSZ78p2klKnbZ/rhiyIIUK0VNE@qm7gbYKMPO53E/nl+D5eD8YyL1A> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081107/eac9c947/attachment.pgp From rea-fbsd at codelabs.ru Fri Nov 7 00:42:35 2008 From: rea-fbsd at codelabs.ru (Eygene Ryabinkin) Date: Fri Nov 7 00:42:41 2008 Subject: FreeBSD-current archives index contains only current month Message-ID: Just glanced over the Mailman archives for -current: there are only threads for the current month, November 2008: http://lists.freebsd.org/pipermail/freebsd-current/ Manually-constructed links like http://lists.freebsd.org/pipermail/freebsd-current/2008-September/thread.html works, but the main index seems to be broken. -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081107/4780a90a/attachment.pgp From aleksey.kashin at gmail.com Fri Nov 7 00:42:51 2008 From: aleksey.kashin at gmail.com (Aleksey K.) Date: Fri Nov 7 00:42:58 2008 Subject: CFT: Realtek 8187L wireless USB driver - urtw(4) Message-ID: <4913FF64.5090500@gmail.com> >Dear all, >This driver supports 8187L which is one of Realtek's 8187x series and >I'm looking for testers who have this device. :-) With lack of H/W I >can't add codes for 8187/8187B devices that AFAIK they can share a lot >of codes and can be supported without modifying many part of codes. > >In my environment the basic features (WEP/WPA and etc ...) are worked >and the driver based on USB1 (not USB2) can be found at as follows: > > http://people.freebsd.org/~weongyo/urtw_20081107.tar.gz > >I think a current problem of urtw(4) is poor RX/TX performance about >8 ~ 10Mbps due to mishandling the rate controlling and I'm not sure it >would easy to fix it without documents but I expect the connection would >be stable. > >Please let me know if you encounter any problems or opinions. Always >patches to improve or enhance features are welcome! > >regards, >Weongyo Jeong Hi. I have netbook MSI Wind U90X with wi-fi module - Realtek 8187SE. You plan to write the driver for this card? I could help with driver testing... Best regards, Kashin Aleksey. From aleksey.kashin at gmail.com Fri Nov 7 00:45:23 2008 From: aleksey.kashin at gmail.com (Aleksey K.) Date: Fri Nov 7 00:45:29 2008 Subject: CFT: Realtek 8187L wireless USB driver - urtw(4) Message-ID: <4913F867.9020301@gmail.com> >Dear all, >This driver supports 8187L which is one of Realtek's 8187x series and >I'm looking for testers who have this device. :-) With lack of H/W I >can't add codes for 8187/8187B devices that AFAIK they can share a lot >of codes and can be supported without modifying many part of codes. > >In my environment the basic features (WEP/WPA and etc ...) are worked >and the driver based on USB1 (not USB2) can be found at as follows: > > http://people.freebsd.org/~weongyo/urtw_20081107.tar.gz > >I think a current problem of urtw(4) is poor RX/TX performance about >8 ~ 10Mbps due to mishandling the rate controlling and I'm not sure it >would easy to fix it without documents but I expect the connection would >be stable. > >Please let me know if you encounter any problems or opinions. Always >patches to improve or enhance features are welcome! > >regards, >Weongyo Jeong Hi. I have netbook MSI Wind U90X with wi-fi module - Realtek 8187SE. You plan to write the driver for this card? I could help with driver testing... Best regards, Kashin Aleksey. From koitsu at FreeBSD.org Fri Nov 7 01:07:22 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Nov 7 01:07:32 2008 Subject: USB4BSD (USB2): Microsoft 4000 keyboard unusable In-Reply-To: <4bSZ78p2klKnbZ/rhiyIIUK0VNE@qm7gbYKMPO53E/nl+D5eD8YyL1A> References: <20081107075232.GA1608@icarus.home.lan> <4bSZ78p2klKnbZ/rhiyIIUK0VNE@qm7gbYKMPO53E/nl+D5eD8YyL1A> Message-ID: <20081107090719.GA1287@icarus.home.lan> On Fri, Nov 07, 2008 at 11:38:49AM +0300, Eygene Ryabinkin wrote: > Thu, Nov 06, 2008 at 11:52:32PM -0800, Jeremy Chadwick wrote: > [...] > > Everything built (csup date: 2008/11/06 ~2200 PST) fine, no issues -- > > until I noticed my USB keyboard didn't function any longer. > > > > During boot0/boot2/loader, the keyboard functions (as expected, re: USB > > Legacy option is enabled in my BIOS), and the keyboard LEDs are lit as > > expected. The kernel loads, some drivers initialise, and the LEDs go > > off. Once the USB2 stack loads, the keyboard LEDs turn back up, but as > > stated, no keypresses are registered. I was forced to hook up a PS/2 > > keyboard. > [...] > > The keyboard in question is a Microsoft Natural Ergonomic 4000. This > > keyboard is known for being a real pain in the ass, since some of the > > multimedia keys, and the infamous F-Lock key, are HID-controlled, while > > alphanumeric are USB keyboard class controlled. > > I used to have this beast. I had simular problems with it, but I had > managed to overcome them by switching the keyboard to the legacy boot > protocol. I am attaching two old patches, one for the stock USB stack > and one for the HPS stack (the old one, more than a year ago). So, they > can be worthless now, but you can give it a shot. > > I had quickly ported my old patch to the current usb20 ukbd2.c, this > patch is attached too, but I have no such keyboard at hand just now, so > I can't test the patches in question. If you will succeed with them -- > please, report back. Eygene, Thanks for providing the patches in question. I applied the third one: > --- sys/dev/usb2/input/ukbd2.c 4 Nov 2008 02:31:03 -0000 1.1 > +++ sys/dev/usb2/input/ukbd2.c 7 Nov 2008 08:32:41 -0000 Sadly it made no difference. I *did not* see any "set protocol failed" messages during boot, so I believe the set worked correctly. Since this box is more or less a server, and I spend very little time at its console (sans recent events :-) ), I think an easier option would be for me to go with a different (simpler) model of USB keyboard, or dig up an old PS/2 Dell keyboard for permanent use. If you'd like me to test any other patches or want me to make code modifications and try things out, I'll be more than happy to test. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From admin at lissyara.su Fri Nov 7 01:23:19 2008 From: admin at lissyara.su (Alex Keda) Date: Fri Nov 7 01:23:27 2008 Subject: Cannot buildworld in CURRENT In-Reply-To: <87bpwsseof.fsf@kobe.laptop> References: <49135844.7010500@lissyara.su> <491358CD.4090601@lissyara.su> <87bpwsseof.fsf@kobe.laptop> Message-ID: <49140904.6080002@lissyara.su> Giorgos Keramidas ?????: > On Thu, 06 Nov 2008 23:51:25 +0300, Alex Keda wrote: > >> Alex Keda ?????: >> >>> ===> usr.bin/du (all) >>> cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall >>> -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes >>> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual >>> -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter >>> -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls >>> -Wno-pointer-sign -c /usr/src/usr.bin/du/du.c >>> cc1: warnings being treated as errors >>> /usr/src/usr.bin/du/du.c: In function 'main': >>> /usr/src/usr.bin/du/du.c:276: warning: format '%jd' expects type >>> intmax_t', but argument 2 has type 'long long int' >>> *** Error code 1 >>> >>> Stop in /usr/src/usr.bin/du. >>> *** Error code 1 >>> ============ >>> updated 2 hour ago >>> >> acer# uname -a >> FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: >> Tue Nov 4 23:23:29 MSK 2008 >> root@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console >> amd64 >> acer# >> > > Oops, this one slipped in because I only built in i386 and not amd64. > > Can you try this patch? > > %%% > diff -r aa58af068624 usr.bin/du/du.c > --- a/usr.bin/du/du.c Thu Nov 06 23:29:46 2008 +0200 > +++ b/usr.bin/du/du.c Thu Nov 06 23:51:48 2008 +0200 > @@ -273,7 +273,8 @@ > (void)printf("\t%s\n", p->fts_path); > } else { > (void)printf("%jd\t%s\n", > - howmany(p->fts_bignum * cblocksize, > + (intmax_t)howmany( > + p->fts_bignum * cblocksize, > blocksize), p->fts_path); > } > } > %%% > another machine. Build success. Updated 2 hour ago... You commit this patch? =) -------------------------------------------------------------- >>> World build completed on Fri Nov 7 11:55:51 MSK 2008 -------------------------------------------------------------- lissyara# uname -a FreeBSD lissyara.moskb.local 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Wed Nov 5 15:44:33 MSK 2008 lissyara@lissyara.moskb.local:/usr/obj/mnt/jabber/DISTR/FreeBSD/src/CURRENT/sys/GENERIC amd64 lissyara# From freebsd-current at dino.sk Fri Nov 7 01:59:12 2008 From: freebsd-current at dino.sk (Milan Obuch) Date: Fri Nov 7 01:59:20 2008 Subject: CFT: Realtek 8187L wireless USB driver - urtw(4) In-Reply-To: <4913FF64.5090500@gmail.com> References: <4913FF64.5090500@gmail.com> Message-ID: <200811071049.04189.freebsd-current@dino.sk> On Friday 07 November 2008 09:42:12 Aleksey K. wrote: > >Dear all, > > > >This driver supports 8187L which is one of Realtek's 8187x series and > >I'm looking for testers who have this device. :-) With lack of H/W I > >can't add codes for 8187/8187B devices that AFAIK they can share a lot > >of codes and can be supported without modifying many part of codes. > > [ snip] > > > >regards, > >Weongyo Jeong > > Hi. I have netbook MSI Wind U90X with wi-fi module - Realtek 8187SE. > You plan to write the driver for this card? I could help with driver > testing... > > Best regards, > Kashin Aleksey. > I have MSI Wind U100 with Realtek 8187SE. From pciconf -lv: none0@pci0:2:0:0: class=0x028000 card=0x68941462 chip=0x819910ec rev=0x22 hdr=0x00 vendor = 'Realtek Semiconductor' class = network Some more details from lspci -vvv: 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Unknown device 8199 (rev 22) Subsystem: Micro-Star International Co., Ltd. Unknown device 6894 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- References: <4913FF64.5090500@gmail.com> Message-ID: <20081107101432.GB23784@freebsd.weongyo.org> On Fri, Nov 07, 2008 at 01:42:12PM +0500, Aleksey K. wrote: > >Dear all, > > >This driver supports 8187L which is one of Realtek's 8187x series and > >I'm looking for testers who have this device. :-) With lack of H/W I > >can't add codes for 8187/8187B devices that AFAIK they can share a lot > >of codes and can be supported without modifying many part of codes. > > > >In my environment the basic features (WEP/WPA and etc ...) are worked > >and the driver based on USB1 (not USB2) can be found at as follows: > > > > http://people.freebsd.org/~weongyo/urtw_20081107.tar.gz > > > >I think a current problem of urtw(4) is poor RX/TX performance about > >8 ~ 10Mbps due to mishandling the rate controlling and I'm not sure it > >would easy to fix it without documents but I expect the connection would > >be stable. > > > >Please let me know if you encounter any problems or opinions. Always > >patches to improve or enhance features are welcome! > > > >regards, > >Weongyo Jeong > > Hi. I have netbook MSI Wind U90X with wi-fi module - Realtek 8187SE. > You plan to write the driver for this card? I could help with driver > testing... Maybe no due to no available H/W. I don't have laptop having Mini-PCI express slot that AFAIK 8187SE is Mini-PCI express. regards, Weongyo Jeong From shoesoft at gmx.net Fri Nov 7 03:01:26 2008 From: shoesoft at gmx.net (Stefan Ehmann) Date: Fri Nov 7 03:01:32 2008 Subject: usb2: scanner no longer working Message-ID: <200811071134.42761.shoesoft@gmx.net> I recompiled sane-backends and linked it against libusb20. The include path needed to be fixed. scanimage -L doesn't detect any scanners. sane-find-scanner correctly detects it on first run: found USB scanner (vendor=0x04a9 [Canon], product=0x221c [CanoScan], chip=GL842) at libusb:/dev/usb:/dev/ugen3.2 on subsequent runs no scanners are found dmesg only says ugen3.2: at usbus3 no ugen detached message even if I unplug the scanner I tried some of the debugging sysctls but I couldn't spot anything useful. ugen seems to work in general as I could access my camera with libgphoto2. Will provide more info as needed. -- Stefan From ed at 80386.nl Fri Nov 7 03:12:03 2008 From: ed at 80386.nl (Ed Schouten) Date: Fri Nov 7 03:12:11 2008 Subject: Request for review: uname(), setdomainname(), getdomainname() cleanups Message-ID: <20081107111201.GH1165@hoeg.nl> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081107/a822179c/attachment.pgp From rdivacky at FreeBSD.org Fri Nov 7 03:16:19 2008 From: rdivacky at FreeBSD.org (Roman Divacky) Date: Fri Nov 7 03:16:27 2008 Subject: Request for review: uname(), setdomainname(), getdomainname() cleanups In-Reply-To: <20081107111201.GH1165@hoeg.nl> References: <20081107111201.GH1165@hoeg.nl> Message-ID: <20081107111305.GA71431@freebsd.org> On Fri, Nov 07, 2008 at 12:12:01PM +0100, Ed Schouten wrote: > Hello all, > > I just wrote this patch and I thought I'd better send it to the lists, > because it affects a lot of random things (Linux emulation, priv(9) > flags, etc). > > Looking at kern_xxx.c, I see we've got a couple of functions there that > actually have to be #ifdef'd with COMPAT_*, while they aren't. Looking > at our CVS repository I can already confirm we don't need to implement > uname(), setdomainname() and getdomainname() on RELENG_5 and later, so I > put them in COMPAT_FREEBSD4. They are implemented as library routines > nowdays. I think they could even be marked as COMPAT_43, but just to be > sure I picked COMPAT_FREEBSD4. > > Below is a list of things of interest: > > - I noticed we have a PRIV_SETDOMAINNAME, but we don't use it inside > sysctl_domainname(). This means that you can bypass PRIV_SETDOMAINNAME > anyway, so remove it. > > - I think it's better if we just implement getdomainname() and > setdomainname() by calling userland_sysctl(). This makes it less > likely to break if we would ever change sysctl_domainname() in > kern_mib.c. > > - To make the linuxolator compile without enabling COMPAT_FREEBSD4, I > added a linux_setdomainname(). I also noticed linux_sethostname() > called userland_sysctl() without holding Giant. > > - It wasn't easy to make uname(), setdomainname() and getdomainname() > work in COMPAT_FREEBSD32, because we would actually need a > "COMPAT4+NOPROTO" option for syscalls.master. Because these system > calls aren't likely to be used, I just disabled them. If it turns out > we really need them, we could reintroduce them. > > Any comments? If not, I'll commit it to SVN in a day or two. Thanks! I just quickly looked at it but I think it's correct and I like the patch. OK from me From keramida at freebsd.org Fri Nov 7 05:16:34 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Fri Nov 7 05:16:41 2008 Subject: Cannot buildworld in CURRENT In-Reply-To: <49140904.6080002@lissyara.su> (Alex Keda's message of "Fri, 07 Nov 2008 12:23:16 +0300") References: <49135844.7010500@lissyara.su> <491358CD.4090601@lissyara.su> <87bpwsseof.fsf@kobe.laptop> <49140904.6080002@lissyara.su> Message-ID: <87k5bfk76s.fsf@kobe.laptop> On Fri, 07 Nov 2008 12:23:16 +0300, Alex Keda wrote: >> Can you try this patch? >> >> %%% >> diff -r aa58af068624 usr.bin/du/du.c >> --- a/usr.bin/du/du.c Thu Nov 06 23:29:46 2008 +0200 >> +++ b/usr.bin/du/du.c Thu Nov 06 23:51:48 2008 +0200 >> @@ -273,7 +273,8 @@ >> (void)printf("\t%s\n", p->fts_path); >> } else { >> (void)printf("%jd\t%s\n", >> - howmany(p->fts_bignum * cblocksize, >> + (intmax_t)howmany( >> + p->fts_bignum * cblocksize, >> blocksize), p->fts_path); >> } >> } >> %%% > > another machine. Build success. Updated 2 hour ago... Thanks :) > You commit this patch? =) Max committed a fix in Subversion change 184742: : r184742 | mlaier | 2008-11-07 01:55:28 +0200 (Fri, 07 Nov 2008) | 2 lines : Changed paths: : M /head/usr.bin/du/du.c : : Restore (intmax_t) casts I lost during the last change & unbreak the build. : If you resync your source tree you will get the fix too :) From nick at van-laarhoven.org Fri Nov 7 05:53:20 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Fri Nov 7 07:29:38 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200811062203.mA6M3ij3048835@lava.sentex.ca> References: <200810092344.10388.nick@van-laarhoven.org> <200811051548.mA5Fmsot040177@lava.sentex.ca> <200811062203.mA6M3ij3048835@lava.sentex.ca> Message-ID: <200811071453.07665.nick@van-laarhoven.org> > For the hardware, I used > http://www.pcengines.ch/alix6b2.htm > with RELENG_7 and nanobsd. The board has dual SIM slots, but there > are no drivers to switch between the two, so just the top one works. If anyone can find information on how to switch SIM slot on the card, I'd be more than happy to include support for it. Would be very useful to have. > at!GSTATUS? > !GSTATUS: > Current Time: 3455 Temperature: 30 > Bootup Time: 3201 Mode: ONLINE > System mode: WCDMA PS state: Not attached > WCDMA band: WCDMA800 GSM band: Unknown > WCDMA channel: 1037 GSM channel: 65535 > GMM (PS) state:DEREGISTERED NO IMSI > MM (CS) state: IDLE NO IMSI > > WCDMA L1 State:L1M_PCH_SLEEP RRC State: DISCONNECTED > RX level (dBm):-87 > > > OK One learns something new every day! > at^SYSINFO > ^SYSINFO: 1,0,1,5,255 Anyone any info on how to decode this? Nick From hselasky at c2i.net Fri Nov 7 08:00:40 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 08:00:54 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071134.42761.shoesoft@gmx.net> References: <200811071134.42761.shoesoft@gmx.net> Message-ID: <200811071702.48123.hselasky@c2i.net> On Friday 07 November 2008, Stefan Ehmann wrote: > I recompiled sane-backends and linked it against libusb20. The include path > needed to be fixed. > > scanimage -L doesn't detect any scanners. > > sane-find-scanner correctly detects it on first run: > found USB scanner (vendor=0x04a9 [Canon], product=0x221c [CanoScan], > chip=GL842) at libusb:/dev/usb:/dev/ugen3.2 > > on subsequent runs no scanners are found > > dmesg only says > ugen3.2: at usbus3 > > no ugen detached message even if I unplug the scanner > > I tried some of the debugging sysctls but I couldn't spot anything useful. > > ugen seems to work in general as I could access my camera with libgphoto2. > > Will provide more info as needed. Hi Stefan, Which version/date is the libusb20 you are using? Does usbconfig list your device? Try changing ownership of the USB devices? Maybe it is a permissions problem. usbconfig -u xx -a xx set_owner xx:yy --HPS From hselasky at c2i.net Fri Nov 7 08:05:40 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 08:05:47 2008 Subject: Kernel panic when copying data to umass device (USB4BSD) In-Reply-To: <20081107082740.GA1334@icarus.home.lan> References: <20081107082740.GA1334@icarus.home.lan> Message-ID: <200811071707.45823.hselasky@c2i.net> On Friday 07 November 2008, Jeremy Chadwick wrote: > http://www.malkavian.com/~jdc/usb2_da0_crash.jpg Hi Jeremy, This issue has already been reported. It has to do with busdma. I will try to verify the busdma path when bounching is enabled. I think I can simulate this on my system by lowering the physical DMA limit. I have not tested on systems with more than 4GB of ram. --HPS From shoesoft at gmx.net Fri Nov 7 08:43:45 2008 From: shoesoft at gmx.net (Stefan Ehmann) Date: Fri Nov 7 08:43:53 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071702.48123.hselasky@c2i.net> References: <200811071134.42761.shoesoft@gmx.net> <200811071702.48123.hselasky@c2i.net> Message-ID: <200811071743.40319.shoesoft@gmx.net> On Friday 07 November 2008 17:02:47 Hans Petter Selasky wrote: > On Friday 07 November 2008, Stefan Ehmann wrote: > > I recompiled sane-backends and linked it against libusb20. The include > > path needed to be fixed. > > > > scanimage -L doesn't detect any scanners. > > > > sane-find-scanner correctly detects it on first run: > > found USB scanner (vendor=0x04a9 [Canon], product=0x221c [CanoScan], > > chip=GL842) at libusb:/dev/usb:/dev/ugen3.2 > > > > on subsequent runs no scanners are found > > > > dmesg only says > > ugen3.2: at usbus3 > > > > no ugen detached message even if I unplug the scanner > > > > I tried some of the debugging sysctls but I couldn't spot anything > > useful. > > > > ugen seems to work in general as I could access my camera with > > libgphoto2. > > > > Will provide more info as needed. > > Hi Stefan, > > Which version/date is the libusb20 you are using? The one commited to current. > Does usbconfig list your device? After I plug it in: ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON After I run scanimage or sane-find-scanner it silently disappears and usbconfig no longer lists it. > Try changing ownership of the USB devices? Maybe it is a permissions > problem. > > usbconfig -u xx -a xx set_owner xx:yy I tried to run as root, so this shouldn't be the problem. From hselasky at c2i.net Fri Nov 7 09:06:58 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 09:07:06 2008 Subject: USB4BSD (USB2): Microsoft 4000 keyboard unusable In-Reply-To: <20081107090719.GA1287@icarus.home.lan> References: <20081107075232.GA1608@icarus.home.lan> <4bSZ78p2klKnbZ/rhiyIIUK0VNE@qm7gbYKMPO53E/nl+D5eD8YyL1A> <20081107090719.GA1287@icarus.home.lan> Message-ID: <200811071809.05617.hselasky@c2i.net> On Friday 07 November 2008, Jeremy Chadwick wrote: > On Fri, Nov 07, 2008 at 11:38:49AM +0300, Eygene Ryabinkin wrote: > > Thu, Nov 06, 2008 at 11:52:32PM -0800, Jeremy Chadwick wrote: > > [...] > > > > > Everything built (csup date: 2008/11/06 ~2200 PST) fine, no issues -- > > > until I noticed my USB keyboard didn't function any longer. > > > > > > During boot0/boot2/loader, the keyboard functions (as expected, re: USB > > > Legacy option is enabled in my BIOS), and the keyboard LEDs are lit as > > > expected. The kernel loads, some drivers initialise, and the LEDs go > > > off. Once the USB2 stack loads, the keyboard LEDs turn back up, but as > > > stated, no keypresses are registered. I was forced to hook up a PS/2 > > > keyboard. > > You are using 64-bit architecture - right? Then you need the following patch to usb2_busdma.c: http://perforce.freebsd.org/chv.cgi?CH=152624 Fix some problems related to busdma: Need to unload DMA maps before re-use! Fix a corner case when loading zero bytes. Affected files ... .. //depot/projects/usb/src/sys/dev/usb2/core/usb2_busdma.c#10 edit Differences ... ==== //depot/projects/usb/src/sys/dev/usb2/core/usb2_busdma.c#10 (text+ko) ==== @@ -597,6 +597,12 @@ uptag = pc->tag_parent; /* + * We have to unload the previous loaded DMA + * pages before trying to load a new one! + */ + bus_dmamap_unload(pc->tag, pc->map); + + /* * Try to load memory into DMA. */ err = bus_dmamap_load( @@ -612,6 +618,12 @@ } else { /* + * We have to unload the previous loaded DMA + * pages before trying to load a new one! + */ + bus_dmamap_unload(pc->tag, pc->map); + + /* * Try to load memory into DMA. The callback * will be called in all cases: */ @@ -639,6 +651,10 @@ void usb2_pc_cpu_invalidate(struct usb2_page_cache *pc) { + if (pc->page_offset_end == pc->page_offset_buf) { + /* nothing has been loaded into this page cache! */ + return; + } bus_dmamap_sync(pc->tag, pc->map, BUS_DMASYNC_POSTWRITE | BUS_DMASYNC_POSTREAD); return; @@ -650,6 +666,10 @@ void usb2_pc_cpu_flush(struct usb2_page_cache *pc) { + if (pc->page_offset_end == pc->page_offset_buf) { + /* nothing has been loaded into this page cache! */ + return; + } bus_dmamap_sync(pc->tag, pc->map, BUS_DMASYNC_PREWRITE | BUS_DMASYNC_PREREAD); return; @@ -953,6 +973,12 @@ if (size > 0) { + /* + * We have to unload the previous loaded DMA + * pages before trying to load a new one! + */ + bus_dmamap_unload(pc->tag, pc->map); + /* try to load memory into DMA using using no wait option */ if (bus_dmamap_load(pc->tag, pc->map, pc->buffer, size, NULL, BUS_DMA_NOWAIT)) { @@ -990,6 +1016,10 @@ len = pc->page_offset_end - pc->page_offset_buf; + if (len == 0) { + /* nothing has been loaded into this page cache */ + return; + } bus_dmamap_sync(pc->tag, pc->map, 0, len, BUS_DMASYNC_POSTWRITE | BUS_DMASYNC_POSTREAD); return; @@ -1005,6 +1035,10 @@ len = pc->page_offset_end - pc->page_offset_buf; + if (len == 0) { + /* nothing has been loaded into this page cache */ + return; + } bus_dmamap_sync(pc->tag, pc->map, 0, len, BUS_DMASYNC_PREWRITE | BUS_DMASYNC_PREREAD); return; Best regards HPS From hselasky at c2i.net Fri Nov 7 09:09:23 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 09:09:30 2008 Subject: Kernel panic when copying data to umass device (USB4BSD) - problem found In-Reply-To: <20081107082740.GA1334@icarus.home.lan> References: <20081107082740.GA1334@icarus.home.lan> Message-ID: <200811071811.27181.hselasky@c2i.net> On Friday 07 November 2008, Jeremy Chadwick wrote: > Not sure if this is caused by problems with USB4BSD or not, as I can > reproduce it on RELENG_7 (but there, the kernel does not panic; it just > "wedges" in a loop/thread somewhere; SSH sessions remain up, but > commands running stop; hitting Ctrl-T shows them in all sorts of > different states, but the states never change; hitting Ctrl-Alt-Esc does > in fact drop me to db>). > Hi Jeremy, I've reproduced the issue with some mods to the usb2_busdma.c on 32-bit arcitecture and have made a fix for this problem. Try the following patch and re-test! Some mem-stick benchmarks would be nice ... My private SVN also has this patch in addition to P4. --HPS http://perforce.freebsd.org/chv.cgi?CH=152624 Fix some problems related to busdma: Need to unload DMA maps before re-use! Fix a corner case when loading zero bytes. Affected files ... .. //depot/projects/usb/src/sys/dev/usb2/core/usb2_busdma.c#10 edit Differences ... ==== //depot/projects/usb/src/sys/dev/usb2/core/usb2_busdma.c#10 (text+ko) ==== @@ -597,6 +597,12 @@ uptag = pc->tag_parent; /* + * We have to unload the previous loaded DMA + * pages before trying to load a new one! + */ + bus_dmamap_unload(pc->tag, pc->map); + + /* * Try to load memory into DMA. */ err = bus_dmamap_load( @@ -612,6 +618,12 @@ } else { /* + * We have to unload the previous loaded DMA + * pages before trying to load a new one! + */ + bus_dmamap_unload(pc->tag, pc->map); + + /* * Try to load memory into DMA. The callback * will be called in all cases: */ @@ -639,6 +651,10 @@ void usb2_pc_cpu_invalidate(struct usb2_page_cache *pc) { + if (pc->page_offset_end == pc->page_offset_buf) { + /* nothing has been loaded into this page cache! */ + return; + } bus_dmamap_sync(pc->tag, pc->map, BUS_DMASYNC_POSTWRITE | BUS_DMASYNC_POSTREAD); return; @@ -650,6 +666,10 @@ void usb2_pc_cpu_flush(struct usb2_page_cache *pc) { + if (pc->page_offset_end == pc->page_offset_buf) { + /* nothing has been loaded into this page cache! */ + return; + } bus_dmamap_sync(pc->tag, pc->map, BUS_DMASYNC_PREWRITE | BUS_DMASYNC_PREREAD); return; @@ -953,6 +973,12 @@ if (size > 0) { + /* + * We have to unload the previous loaded DMA + * pages before trying to load a new one! + */ + bus_dmamap_unload(pc->tag, pc->map); + /* try to load memory into DMA using using no wait option */ if (bus_dmamap_load(pc->tag, pc->map, pc->buffer, size, NULL, BUS_DMA_NOWAIT)) { @@ -990,6 +1016,10 @@ len = pc->page_offset_end - pc->page_offset_buf; + if (len == 0) { + /* nothing has been loaded into this page cache */ + return; + } bus_dmamap_sync(pc->tag, pc->map, 0, len, BUS_DMASYNC_POSTWRITE | BUS_DMASYNC_POSTREAD); return; @@ -1005,6 +1035,10 @@ len = pc->page_offset_end - pc->page_offset_buf; + if (len == 0) { + /* nothing has been loaded into this page cache */ + return; + } bus_dmamap_sync(pc->tag, pc->map, 0, len, BUS_DMASYNC_PREWRITE | BUS_DMASYNC_PREREAD); return; From hselasky at c2i.net Fri Nov 7 09:14:09 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 09:14:16 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071743.40319.shoesoft@gmx.net> References: <200811071134.42761.shoesoft@gmx.net> <200811071702.48123.hselasky@c2i.net> <200811071743.40319.shoesoft@gmx.net> Message-ID: <200811071816.11704.hselasky@c2i.net> On Friday 07 November 2008, Stefan Ehmann wrote: > On Friday 07 November 2008 17:02:47 Hans Petter Selasky wrote: > > On Friday 07 November 2008, Stefan Ehmann wrote: > > > I recompiled sane-backends and linked it against libusb20. The include > > > path needed to be fixed. > > > > > > scanimage -L doesn't detect any scanners. > > > > > > sane-find-scanner correctly detects it on first run: > > > found USB scanner (vendor=0x04a9 [Canon], product=0x221c [CanoScan], > > > chip=GL842) at libusb:/dev/usb:/dev/ugen3.2 > > > > > > on subsequent runs no scanners are found > > > > > > dmesg only says > > > ugen3.2: at usbus3 > > > > > > no ugen detached message even if I unplug the scanner > > > > > > I tried some of the debugging sysctls but I couldn't spot anything > > > useful. > > > > > > ugen seems to work in general as I could access my camera with > > > libgphoto2. > > > > > > Will provide more info as needed. > > > > Hi Stefan, > > > > Which version/date is the libusb20 you are using? > > The one commited to current. > > > Does usbconfig list your device? > > After I plug it in: > ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=ON > > After I run scanimage or sane-find-scanner it silently disappears and > usbconfig no longer lists it. > > > Try changing ownership of the USB devices? Maybe it is a permissions > > problem. > > > > usbconfig -u xx -a xx set_owner xx:yy > Hi, If usbconfig does not list your device, then it is no longer present in the system. Are you running USB2 on a 64-bit architecture? Try again having HUB debugging turned on. sysctl hw.usb2.uhub.debug=15 I suspect that your device: a) had firmware loaded and the scanner driver called the device reset function, which is a little different than on linux. b) USB firmware crashed. Maybe your device needs a quirk? --HPS From gavin at FreeBSD.org Fri Nov 7 09:14:28 2008 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Fri Nov 7 09:14:34 2008 Subject: [PATCH] Quirk for I-Tuner Networks USBLCD4X20 In-Reply-To: <99CD11CA-9AEB-4260-B7C9-44E9B82EA34A@siliconlandmark.com> References: <99CD11CA-9AEB-4260-B7C9-44E9B82EA34A@siliconlandmark.com> Message-ID: <1226076247.69416.12.camel@buffy.york.ac.uk> On Fri, 2008-10-31 at 11:49 -0400, Andre Guibert de Bruet wrote: > Hi, > > The attached patch provides a quirk entry for the I-Tuner Networks' > External USB 4x20 LCD device, so that it does not get attached to by > uhid. I have successfully run lcdproc CVS HEAD with this device on 7.1- > PRERELEASE (If anyone is interested in the configs, please email me > off-list). > > Could this get committed upon review? Hi, You're probably best off putting this into a PR, so that it doesn't get lost. Thanks, Gavin From stas at FreeBSD.org Fri Nov 7 09:18:00 2008 From: stas at FreeBSD.org (Stanislav Sedov) Date: Fri Nov 7 09:18:07 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <20081104015235.GC98154@cdnetworks.co.kr> References: <490F47BE.9080205@janh.de> <20081104015235.GC98154@cdnetworks.co.kr> Message-ID: <20081107200044.77e723d2.stas@FreeBSD.org> On Tue, 4 Nov 2008 10:52:35 +0900 Pyun YongHyeon mentioned: > > This will probably not go into 7.1-RELEASE, will it? > > It was too late to go into 7.1-RELEASE, I guess. I think it's still possible to get this into 7.1 as it's a separate driver and doesn't influence on other subsystems. -- Stanislav Sedov ST4096-RIPE -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081107/acd90103/attachment.pgp From hselasky at c2i.net Fri Nov 7 09:36:09 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 09:36:16 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071743.40319.shoesoft@gmx.net> References: <200811071134.42761.shoesoft@gmx.net> <200811071702.48123.hselasky@c2i.net> <200811071743.40319.shoesoft@gmx.net> Message-ID: <200811071838.16493.hselasky@c2i.net> On Friday 07 November 2008, Stefan Ehmann wrote: > On Friday 07 November 2008 17:02:47 Hans Petter Selasky wrote: > > On Friday 07 November 2008, Stefan Ehmann wrote: > > > I recompiled sane-backends and linked it against libusb20. The include > > > path needed to be fixed. > > > > > > scanimage -L doesn't detect any scanners. > > > > > > sane-find-scanner correctly detects it on first run: > > > found USB scanner (vendor=0x04a9 [Canon], product=0x221c [CanoScan], > > > chip=GL842) at libusb:/dev/usb:/dev/ugen3.2 > > > > > > on subsequent runs no scanners are found > > > > > > dmesg only says > > > ugen3.2: at usbus3 > > > > > > no ugen detached message even if I unplug the scanner > > > > > > I tried some of the debugging sysctls but I couldn't spot anything > > > useful. > > > > > > ugen seems to work in general as I could access my camera with > > > libgphoto2. > > > > > > Will provide more info as needed. > > > > Hi Stefan, > > > > Which version/date is the libusb20 you are using? > > The one commited to current. > > > Does usbconfig list your device? > > After I plug it in: > ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=ON > > After I run scanimage or sane-find-scanner it silently disappears and > usbconfig no longer lists it. > > > Try changing ownership of the USB devices? Maybe it is a permissions > > problem. > > > > usbconfig -u xx -a xx set_owner xx:yy > > I tried to run as root, so this shouldn't be the problem. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Hi, Could you dump the current config descriptor of your scanner? usbconfig -u 3 -a 2 dump_curr_config_desc It can also be a set-config issue. --HPS From hselasky at c2i.net Fri Nov 7 09:40:41 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 09:40:47 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071838.16493.hselasky@c2i.net> References: <200811071134.42761.shoesoft@gmx.net> <200811071743.40319.shoesoft@gmx.net> <200811071838.16493.hselasky@c2i.net> Message-ID: <200811071842.50044.hselasky@c2i.net> On Friday 07 November 2008, Hans Petter Selasky wrote: > Hi, > > Could you dump the current config descriptor of your scanner? > > usbconfig -u 3 -a 2 dump_curr_config_desc > > It can also be a set-config issue. > > --HPS Also get me the device descriptor through: usbconfig -u 3 -a 2 dump_device_desc 3 and 2 are the numbers after ugen, like ugen3.2 --HPS From shoesoft at gmx.net Fri Nov 7 09:51:56 2008 From: shoesoft at gmx.net (Stefan Ehmann) Date: Fri Nov 7 09:52:03 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071842.50044.hselasky@c2i.net> References: <200811071134.42761.shoesoft@gmx.net> <200811071838.16493.hselasky@c2i.net> <200811071842.50044.hselasky@c2i.net> Message-ID: <200811071851.52961.shoesoft@gmx.net> On Friday 07 November 2008 18:42:49 Hans Petter Selasky wrote: > On Friday 07 November 2008, Hans Petter Selasky wrote: > > Hi, > > > > Could you dump the current config descriptor of your scanner? > > > > usbconfig -u 3 -a 2 dump_curr_config_desc # usbconfig -u 3 -a 2 dump_curr_config_desc ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0027 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x00a0 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0003 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 2 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0003 wMaxPacketSize = 0x0001 bInterval = 0x0008 bRefresh = 0x0000 bSynchAddress = 0x0000 > > It can also be a set-config issue. > > > > --HPS > > Also get me the device descriptor through: > > usbconfig -u 3 -a 2 dump_device_desc # usbconfig -u 3 -a 2 dump_device_desc ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00ff bDeviceSubClass = 0x00ff bDeviceProtocol = 0x00ff bMaxPacketSize0 = 0x0040 idVendor = 0x04a9 idProduct = 0x221c bcdDevice = 0x0306 iManufacturer = 0x0001 LangId:0x0409 iProduct = 0x0002 LangId:0x0409 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 > 3 and 2 are the numbers after ugen, like ugen3.2 To your other mail: I'm running i386. HUB debugging didn't output any obvious errors. From hselasky at c2i.net Fri Nov 7 10:33:12 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 10:33:19 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071851.52961.shoesoft@gmx.net> References: <200811071134.42761.shoesoft@gmx.net> <200811071842.50044.hselasky@c2i.net> <200811071851.52961.shoesoft@gmx.net> Message-ID: <200811071935.19412.hselasky@c2i.net> On Friday 07 November 2008, Stefan Ehmann wrote: > On Friday 07 November 2008 18:42:49 Hans Petter Selasky wrote: > > On Friday 07 November 2008, Hans Petter Selasky wrote: > > > Hi, > > > > > > Could you dump the current config descriptor of your scanner? > > > > > > usbconfig -u 3 -a 2 dump_curr_config_desc > > # usbconfig -u 3 -a 2 dump_curr_config_desc > ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=ON > > > Configuration index 0 > > bLength = 0x0009 > bDescriptorType = 0x0002 > wTotalLength = 0x0027 > bNumInterfaces = 0x0001 > bConfigurationValue = 0x0001 > iConfiguration = 0x0000 > bmAttributes = 0x00a0 > bMaxPower = 0x00fa > > Interface 0 > bLength = 0x0009 > bDescriptorType = 0x0004 > bInterfaceNumber = 0x0000 > bAlternateSetting = 0x0000 > bNumEndpoints = 0x0003 > bInterfaceClass = 0x00ff > bInterfaceSubClass = 0x00ff > bInterfaceProtocol = 0x00ff > iInterface = 0x0000 > > Endpoint 0 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0081 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 1 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0002 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 2 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0083 > bmAttributes = 0x0003 > wMaxPacketSize = 0x0001 > bInterval = 0x0008 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > > > It can also be a set-config issue. > > > > > > --HPS > > > > Also get me the device descriptor through: > > > > usbconfig -u 3 -a 2 dump_device_desc > > # usbconfig -u 3 -a 2 dump_device_desc > ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x00ff > bDeviceSubClass = 0x00ff > bDeviceProtocol = 0x00ff > bMaxPacketSize0 = 0x0040 > idVendor = 0x04a9 > idProduct = 0x221c > bcdDevice = 0x0306 > iManufacturer = 0x0001 LangId:0x0409 > iProduct = 0x0002 LangId:0x0409 > iSerialNumber = 0x0000 > bNumConfigurations = 0x0001 > > > 3 and 2 are the numbers after ugen, like ugen3.2 > > To your other mail: > I'm running i386. HUB debugging didn't output any obvious errors. Hi, Try the following patch to libusb20. I suspect that it is the set_configuration call that makes trouble! http://perforce.freebsd.org/chv.cgi?CH=152628 Thanks for reporting. My private SVN repository has also been updated to include this patch if you are using that. --HPS From ed at 80386.nl Fri Nov 7 10:38:03 2008 From: ed at 80386.nl (Ed Schouten) Date: Fri Nov 7 10:38:10 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071702.48123.hselasky@c2i.net> References: <200811071134.42761.shoesoft@gmx.net> <200811071702.48123.hselasky@c2i.net> Message-ID: <20081107183801.GI1165@hoeg.nl> * Hans Petter Selasky wrote: > Try changing ownership of the USB devices? Maybe it is a permissions problem. > > usbconfig -u xx -a xx set_owner xx:yy What's wrong with chmod(1) and chown(1)? -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081107/32d565b3/attachment.pgp From hselasky at c2i.net Fri Nov 7 10:45:02 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 10:45:09 2008 Subject: usb2: scanner no longer working In-Reply-To: <20081107183801.GI1165@hoeg.nl> References: <200811071134.42761.shoesoft@gmx.net> <200811071702.48123.hselasky@c2i.net> <20081107183801.GI1165@hoeg.nl> Message-ID: <200811071947.10612.hselasky@c2i.net> On Friday 07 November 2008, Ed Schouten wrote: > * Hans Petter Selasky wrote: > > Try changing ownership of the USB devices? Maybe it is a permissions > > problem. > > > > usbconfig -u xx -a xx set_owner xx:yy > > What's wrong with chmod(1) and chown(1)? Hi Ed, Basically there is nothing wrong with using chmod and chown. Hence USB has its own directory system which is not part of devfs, it was natural to also have a separate utility to set the permissions and ownership, which might become more complicated than simply a user and group. At EuroBSDcon this year I got some ideas about defining functional permission groups, like permissions for all USB keyboards for example, instead of permissions for individual devices. This pradigm will then break with chmod and chown. --HPS From ed at 80386.nl Fri Nov 7 10:49:30 2008 From: ed at 80386.nl (Ed Schouten) Date: Fri Nov 7 10:49:36 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071947.10612.hselasky@c2i.net> References: <200811071134.42761.shoesoft@gmx.net> <200811071702.48123.hselasky@c2i.net> <20081107183801.GI1165@hoeg.nl> <200811071947.10612.hselasky@c2i.net> Message-ID: <20081107184929.GJ1165@hoeg.nl> Hello Hans, * Hans Petter Selasky wrote: > Basically there is nothing wrong with using chmod and chown. Hence USB > has its own directory system which is not part of devfs, it was > natural to also have a separate utility to set the permissions and > ownership, which might become more complicated than simply a user and > group. At EuroBSDcon this year I got some ideas about defining > functional permission groups, like permissions for all USB keyboards > for example, instead of permissions for individual devices. This > pradigm will then break with chmod and chown. But that's not the right direction. If we really want to do such things, we should add ACL support to devfs, which is already something we eventually want to do. I don't agree that we should create yet another namespace with permissions instead of using the traditional /dev directory. -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081107/8bb48b92/attachment.pgp From rink at FreeBSD.org Fri Nov 7 10:55:20 2008 From: rink at FreeBSD.org (Rink Springer) Date: Fri Nov 7 10:55:28 2008 Subject: usb2: scanner no longer working In-Reply-To: <20081107184929.GJ1165@hoeg.nl> References: <200811071134.42761.shoesoft@gmx.net> <200811071702.48123.hselasky@c2i.net> <20081107183801.GI1165@hoeg.nl> <200811071947.10612.hselasky@c2i.net> <20081107184929.GJ1165@hoeg.nl> Message-ID: <20081107185516.GC39947@rink.nu> On Fri, Nov 07, 2008 at 07:49:29PM +0100, Ed Schouten wrote: > Hello Hans, > > * Hans Petter Selasky wrote: > > Basically there is nothing wrong with using chmod and chown. Hence USB > > has its own directory system which is not part of devfs, it was > > natural to also have a separate utility to set the permissions and > > ownership, which might become more complicated than simply a user and > > group. At EuroBSDcon this year I got some ideas about defining > > functional permission groups, like permissions for all USB keyboards > > for example, instead of permissions for individual devices. This > > pradigm will then break with chmod and chown. > > But that's not the right direction. If we really want to do such things, > we should add ACL support to devfs, which is already something we > eventually want to do. I don't agree that we should create yet another > namespace with permissions instead of using the traditional /dev > directory. I'm working on migrating this to make_dev(9), so USB devices will get created like everything else and thus work properly using devfs et al. -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder From hselasky at c2i.net Fri Nov 7 11:00:10 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 11:00:16 2008 Subject: usb2: scanner no longer working In-Reply-To: <20081107185516.GC39947@rink.nu> References: <200811071134.42761.shoesoft@gmx.net> <20081107184929.GJ1165@hoeg.nl> <20081107185516.GC39947@rink.nu> Message-ID: <200811072002.15868.hselasky@c2i.net> On Friday 07 November 2008, Rink Springer wrote: > On Fri, Nov 07, 2008 at 07:49:29PM +0100, Ed Schouten wrote: > > Hello Hans, > > > > * Hans Petter Selasky wrote: > > > Basically there is nothing wrong with using chmod and chown. Hence USB > > > has its own directory system which is not part of devfs, it was > > > natural to also have a separate utility to set the permissions and > > > ownership, which might become more complicated than simply a user and > > > group. At EuroBSDcon this year I got some ideas about defining > > > functional permission groups, like permissions for all USB keyboards > > > for example, instead of permissions for individual devices. This > > > pradigm will then break with chmod and chown. > > > > But that's not the right direction. If we really want to do such things, > > we should add ACL support to devfs, which is already something we > > eventually want to do. I don't agree that we should create yet another > > namespace with permissions instead of using the traditional /dev > > directory. > > I'm working on migrating this to make_dev(9), so USB devices will get > created like everything else and thus work properly using devfs et al. Hi, How do you plan to integrate this? Do you have any patches? --HPS From shoesoft at gmx.net Fri Nov 7 11:19:14 2008 From: shoesoft at gmx.net (Stefan Ehmann) Date: Fri Nov 7 11:19:23 2008 Subject: usb2: scanner no longer working In-Reply-To: <200811071935.19412.hselasky@c2i.net> References: <200811071134.42761.shoesoft@gmx.net> <200811071851.52961.shoesoft@gmx.net> <200811071935.19412.hselasky@c2i.net> Message-ID: <200811072019.09617.shoesoft@gmx.net> On Friday 07 November 2008 19:35:17 Hans Petter Selasky wrote: > On Friday 07 November 2008, Stefan Ehmann wrote: > > On Friday 07 November 2008 18:42:49 Hans Petter Selasky wrote: > > > On Friday 07 November 2008, Hans Petter Selasky wrote: > > > > Hi, > > > > > > > > Could you dump the current config descriptor of your scanner? > > > > > > > > usbconfig -u 3 -a 2 dump_curr_config_desc > > > > # usbconfig -u 3 -a 2 dump_curr_config_desc > > ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) > > pwr=ON ... > > > 3 and 2 are the numbers after ugen, like ugen3.2 > > > > To your other mail: > > I'm running i386. HUB debugging didn't output any obvious errors. > > Hi, > > Try the following patch to libusb20. I suspect that it is the > set_configuration call that makes trouble! > > http://perforce.freebsd.org/chv.cgi?CH=152628 > > Thanks for reporting. > > My private SVN repository has also been updated to include this patch if > you are using that. The device isn't disappearing any longer. The scanner is basically working now. Thanks for your quick fix. It seems I have another issue now: When I run scanimage the system becomes unresponsive for quite some time before the scanning starts. I'll do more testing tomorrow and try to give more details then. -- Stefan From chuckr at telenix.org Fri Nov 7 11:19:26 2008 From: chuckr at telenix.org (Chuck Robey) Date: Fri Nov 7 11:19:32 2008 Subject: new X11 project Message-ID: <0E1DCF36-07A1-4A7F-8784-477709445C26@telenix.org> [This is my first time running this mail composing tool, tell me if it's doing something evil I don't see, ok?] I just got pointed at a URL, if you haven't, it's most likely worth your time to read this; http://www.phoronix.com/scan.php?page=article&item=xorg_wayland&num=1 It's discussing a new X11 project, going by the name Wayland, a RedHat project. Among it's primary goals is to simplify the server, and since making things simpler (and hence more reliable) has been a lifelong primary goal of mine, I'm listening. My goal here, beyond trying to be helpful in pointing out something clearly important, is to find out of anyone has done any research with a mind towards finding out the ultimate compatibility between FreeBSD and this new Wayland. I'm always worried that a Linux-person is going to "innocently" write something that requires us to become a Linux lookalike. Has anyone got any FreeBSD info on this? Because, if I get s nice loud shot of slicne in answer to this question, I'm going to have to try to fix it. I wonder if it's just something that's going to need porting (my devout wish), or are more extreme measures going to have to be considered? Just being a worry-wart. From shuvaev at physik.uni-wuerzburg.de Fri Nov 7 11:19:32 2008 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Fri Nov 7 11:19:44 2008 Subject: Kernel panic when copying data to umass device (USB4BSD) - problem found In-Reply-To: <200811071811.27181.hselasky@c2i.net> References: <20081107082740.GA1334@icarus.home.lan> <200811071811.27181.hselasky@c2i.net> Message-ID: <20081107191935.GA51170@localhost.my.domain> On Fri, Nov 07, 2008 at 06:11:26PM +0100, Hans Petter Selasky wrote: > > Hi Jeremy, > > I've reproduced the issue with some mods to the usb2_busdma.c on 32-bit > arcitecture and have made a fix for this problem. > > Try the following patch and re-test! > Thanks a lot! I have rebuild the kernel with this patch > > http://perforce.freebsd.org/chv.cgi?CH=152624 > and so far no panics. Indeed, the system I am using is amd64 with 4Gb of RAM. > Some mem-stick benchmarks would be nice ... > What exactly do you mean? I have done: dd if=file_on_one_stick of=/dev/null bs=1m (12.5 Mb/s) dd if=/dev/random of=file_on_the_stick bs=1m count=128 (2.6 Mb/s) and the same tests with USB-microSDHC adapter with 8Gb card (20 MB/s read, 15 Mb/s write). Anything else? Alexey. From rnoland at FreeBSD.org Fri Nov 7 11:33:34 2008 From: rnoland at FreeBSD.org (Robert Noland) Date: Fri Nov 7 11:33:41 2008 Subject: new X11 project In-Reply-To: <0E1DCF36-07A1-4A7F-8784-477709445C26@telenix.org> References: <0E1DCF36-07A1-4A7F-8784-477709445C26@telenix.org> Message-ID: <1226086406.33599.22.camel@squirrel.corp.cox.com> On Fri, 2008-11-07 at 13:52 -0500, Chuck Robey wrote: > [This is my first time running this mail composing tool, tell me if > it's doing something evil I don't see, ok?] > > I just got pointed at a URL, if you haven't, it's most likely worth > your time to read this; > > http://www.phoronix.com/scan.php?page=article&item=xorg_wayland&num=1 > > It's discussing a new X11 project, going by the name Wayland, a RedHat > project. Among it's primary goals is to simplify the server, and > since making things simpler (and hence more reliable) has been a > lifelong primary goal of mine, I'm listening. My goal here, beyond > trying to be helpful in pointing out something clearly important, is > to find out of anyone has done any research with a mind towards > finding out the ultimate compatibility between FreeBSD and this new > Wayland. I'm always worried that a Linux-person is going to > "innocently" write something that requires us to become a Linux > lookalike. I haven't spoken to krh about it, but the userland component likely won't be all that difficult to port. The more complex issue is all the back-end kernel support that will be needed. GEM is on my list to do sooner rather than later, but I haven't gotten it going yet. I still have to scope out kernel modesetting, this may require even more kernel work than gem. Once both of those features exist, it is probably viable to port the code. robert. > Has anyone got any FreeBSD info on this? Because, if I get s nice > loud shot of slicne in answer to this question, I'm going to have to > try to fix it. I wonder if it's just something that's going to need > porting (my devout wish), or are more extreme measures going to have > to be considered? Just being a worry-wart. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081107/983b8b44/attachment.pgp From unixmania at gmail.com Fri Nov 7 11:36:53 2008 From: unixmania at gmail.com (Carlos A. M. dos Santos) Date: Fri Nov 7 11:37:00 2008 Subject: new X11 project In-Reply-To: <0E1DCF36-07A1-4A7F-8784-477709445C26@telenix.org> References: <0E1DCF36-07A1-4A7F-8784-477709445C26@telenix.org> Message-ID: On Fri, Nov 7, 2008 at 4:52 PM, Chuck Robey wrote: > [This is my first time running this mail composing tool, tell me if it's > doing something evil I don't see, ok?] > > I just got pointed at a URL, if you haven't, it's most likely worth your > time to read this; > > http://www.phoronix.com/scan.php?page=article&item=xorg_wayland&num=1 > > It's discussing a new X11 project, going by the name Wayland, a RedHat > project. Among it's primary goals is to simplify the server, and since > making things simpler (and hence more reliable) has been a lifelong primary > goal of mine, I'm listening. My goal here, beyond trying to be helpful in > pointing out something clearly important, is to find out of anyone has done > any research with a mind towards finding out the ultimate compatibility > between FreeBSD and this new Wayland. I'm always worried that a > Linux-person is going to "innocently" write something that requires us to > become a Linux lookalike. OpenBSD folks are working on improvements for X too. You may be interested on this presentation: http://www.openbsd.org/papers/fosdem08-xorg.pdf > Has anyone got any FreeBSD info on this? Because, if I get s nice loud shot > of slicne in answer to this question, I'm going to have to try to fix it. I > wonder if it's just something that's going to need porting (my devout wish), > or are more extreme measures going to have to be considered? Just being a > worry-wart. -- cd /usr/ports/sysutils/life make clean From shuvaev at physik.uni-wuerzburg.de Fri Nov 7 11:48:51 2008 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Fri Nov 7 11:49:01 2008 Subject: Call for testers: fxp(4) WOL In-Reply-To: <20081104014246.GA98154@cdnetworks.co.kr> References: <20081015003745.GG14769@cdnetworks.co.kr> <20081103183556.GA2009@localhost.my.domain> <20081104014246.GA98154@cdnetworks.co.kr> Message-ID: <20081107194844.GA55053@localhost.my.domain> On Tue, Nov 04, 2008 at 10:42:46AM +0900, Pyun YongHyeon wrote: > On Mon, Nov 03, 2008 at 07:35:56PM +0100, Alexey Shuvaev wrote: > > Here are relevant messages from the verbose boot: > > > > fxp0: port 0xdf40-0xdf7f mem 0xfceff000-0xfcefffff irq 11 at device 8.0 on pci2 > > If it's based on ICH controller it would be 82559. > > > fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfceff000 > > fxp0: using memory space register mapping > > fxp0: PCI IDs: 8086 1031 1179 0001 0042 > > fxp0: Dynamic Standby mode is disabled > > miibus0: on fxp0 > > fxp0: XXX: driver didn't set ifq_maxlen > > ^^^ > > Is this something to fix? > > > > fxp(4) didn't set ifq_maxlen and if_attach corrected this with > its default value. Normally network device drivers set this queue > length to number of Tx descriptors but it's completely up to > driver writers and I don't see compeling reason to change that. > Ok, I just was attracted by something with 'XXX'. > > However the system seems to honors only the BIOS settings, if I enable WOL in > > the BIOS the system wakes up from power-down or suspend (to ram) states > > regardless of fxp settings and with disabled WOL in BIOS it never > > wakes up. > > > > Yes that's an expected behaviour. BIOS option should be changed to > enable WOL if you want to wake up your box from power down. If > you don't want to wake up your box regardless of BIOS configuration > you have to disable WOL with ifconfig before shutting down your > box. Likewise even if you enable WOL with ifconfig(8) to wake up > your system, BIOS WOL option also should be enabled to make it > work. > > > The worse thing I have noticed is if I send WOL packet while the system is > > running it reliably hangs. It does not panic and switching virtual > > consoles works (and typing/deleting something in the shell prompt too), > > but the cooler runs at full power and you can't do anything else. > > This is both with patched fxp and that from -CURRENT. > > Hmm, I think that was old bebahviour of stock fxp(4). Previously > fxp(4) was programmed to accept WOL packets regardless of running > state of hardware. With my patch the WOL should be disabled for > normal operation and WOL is enabled again when you shutdown your > box. If sotck fxp(4) also show the same behaviour it's big security > hole. > ATM I have no idea how WOL packets can affect running box. :-( > I have tested more thoroughly and here are the results. FreeBSD-CURRENT (late oktober) without your patch (is it what you call 'stock'?): interface up or down, WOL disabled or enabled in the BIOS - system hangs when receiving WOL packet. Breaking to debugger shows kernel running, namely 3 acpi threads, acpi_task_[0-2]. FreeBSD-CURRENT from 4 Nov 2008 with your patch: again, with WOL enabled in BIOS or not, system hangs with WOL packet, but only if interface is down. With interface (fxp0) up and running, nothing happens. However, I failed to disable WOL with ifconfig, notebook boots always when WOL enabled in the BIOS. Linux-Ubuntu uname: Linux ubuntu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux (booted live from CD) The same results as with FreeBSD-CURRENT with your patch. Disabling wol with ethtool does not produce the desired results. Receiving WOL packet when interface is down does not hang the system, but it (according to top) consumes 70% in system with kacpid process consuming 98.5% of cpu. > Thanks for testing. I'll think again. > By chance can you try Linux on your system and check whether it > works? > So, it seems your patch is making FreeBSD on par with Linux. If you need something more, you are welcome! Alexey. From onemda at gmail.com Fri Nov 7 11:54:58 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Fri Nov 7 11:55:06 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811070036.15816.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <20081106191230.GA47600@wep4035.physik.uni-wuerzburg.de> <20081106210300.GA1595@wep4035.physik.uni-wuerzburg.de> <200811070036.15816.hselasky@c2i.net> Message-ID: <3a142e750811071154y5108f299h60bb7c1060f4567e@mail.gmail.com> On recent CURRENT when attaching rum card, strange bug appear: usb2_alloc_device:1417: set address 2 failed (ignored) usb2_alloc_device:1452: getting device descriptor at addr 2 failed! uhub_reattach_port:401: could not allocate new device! uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling port 5 uhub_reattach_port:370: giving up port reset - device vanished! uhub_reattach_port:370: giving up port reset - device vanished! uhub_reattach_port:370: giving up port reset - device vanished! uhub_reattach_port:370: giving up port reset - device vanished! uhub_reattach_port:370: giving up port reset - device vanished! uhub_reattach_port:370: giving up port reset - device vanished! uhub_reattach_port:370: giving up port reset - device vanished! uhub_reattach_port:370: giving up port reset - device vanished! uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling port 5 uhub_reattach_port:370: giving up port reset - device vanished! usb2_alloc_device:1417: set address 2 failed (ignored) usb2_alloc_device:1452: getting device descriptor at addr 2 failed! uhub_reattach_port:401: could not allocate new device! usb2_alloc_device:1417: set address 2 failed (ignored) usb2_alloc_device:1452: getting device descriptor at addr 2 failed! uhub_reattach_port:401: could not allocate new device! But not so old one from svn was working fine. > kldstat Id Refs Address Size Name 1 155 0xc0400000 51f700 kernel (/boot/kernel/kernel) 2 2 0xc0920000 51bb0 sound.ko (/boot/kernel/sound.ko) 3 1 0xc0972000 1a5e0 snd_hda.ko (/boot/kernel/snd_hda.ko) 4 2 0xc098d000 18170 agp.ko (/boot/kernel/agp.ko) 5 1 0xc09a6000 c3fc random.ko (/boot/kernel/random.ko) 6 2 0xc09b3000 16b14 drm.ko (/boot/kernel/drm.ko) 7 1 0xc09ca000 af9c i915.ko (/boot/kernel/i915.ko) 8 5 0xc09d5000 e3cc ata.ko (/boot/kernel/ata.ko) 9 2 0xc09e4000 5230 ataahci.ko (/boot/kernel/ataahci.ko) 10 3 0xc09ea000 88b0 atapci.ko (/boot/kernel/atapci.ko) 11 1 0xc09f3000 4638 atadisk.ko (/boot/kernel/atadisk.ko) 12 1 0xc09f8000 5834 ataintel.ko (/boot/kernel/ataintel.ko) 13 1 0xc09fe000 be08 cpufreq.ko (/boot/kernel/cpufreq.ko) 14 1 0xc0a0a000 4dc8 sysvmsg.ko (/boot/kernel/sysvmsg.ko) 15 1 0xc0a0f000 5e9c sysvsem.ko (/boot/kernel/sysvsem.ko) 16 1 0xc0a15000 5034 sysvshm.ko (/boot/kernel/sysvshm.ko) 17 1 0xc0a1b000 6b974 acpi.ko (/boot/kernel/acpi.ko) 18 9 0xc462c000 35000 usb2_core.ko (/boot/kernel/usb2_core.ko) 19 4 0xc46eb000 3000 usb2_controller.ko (/boot/kernel/usb2_controller.ko) 20 1 0xc46f8000 a000 usb2_controller_uhci.ko (/boot/kernel/usb2_controller_uhci.ko) 21 1 0xc474e000 c000 usb2_controller_ehci.ko (/boot/kernel/usb2_controller_ehci.ko) 22 1 0xc477b000 a000 usb2_controller_ohci.ko (/boot/kernel/usb2_controller_ohci.ko) 23 1 0xc47a8000 a000 usb2_storage_mass.ko (/boot/kernel/usb2_storage_mass.ko) 24 1 0xc47b2000 43000 cam.ko (/boot/kernel/cam.ko) 25 1 0xc47fe000 2000 usb2_storage.ko (/boot/kernel/usb2_storage.ko) 26 1 0xc4800000 a000 usb2_wlan_rum.ko (/boot/kernel/usb2_wlan_rum.ko) 27 1 0xc480a000 2000 wlan_amrr.ko (/boot/kernel/wlan_amrr.ko) 28 4 0xc480c000 34000 wlan.ko (/boot/kernel/wlan.ko) 29 1 0xc4849000 2000 usb2_wlan.ko (/boot/kernel/usb2_wlan.ko) From onemda at gmail.com Fri Nov 7 12:02:25 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Fri Nov 7 12:02:32 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <3a142e750811071154y5108f299h60bb7c1060f4567e@mail.gmail.com> References: <200810251925.47273.hselasky@c2i.net> <20081106191230.GA47600@wep4035.physik.uni-wuerzburg.de> <20081106210300.GA1595@wep4035.physik.uni-wuerzburg.de> <200811070036.15816.hselasky@c2i.net> <3a142e750811071154y5108f299h60bb7c1060f4567e@mail.gmail.com> Message-ID: <3a142e750811071202h765c64a0g820db4fe54ec9b4f@mail.gmail.com> On 11/7/08, Paul B. Mahol wrote: > On recent CURRENT when attaching rum card, strange bug appear: > > usb2_alloc_device:1417: set address 2 failed (ignored) > usb2_alloc_device:1452: getting device descriptor at addr 2 failed! > uhub_reattach_port:401: could not allocate new device! > > uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT > uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling port 5 > uhub_reattach_port:370: giving up port reset - device vanished! > uhub_reattach_port:370: giving up port reset - device vanished! > uhub_reattach_port:370: giving up port reset - device vanished! > uhub_reattach_port:370: giving up port reset - device vanished! > uhub_reattach_port:370: giving up port reset - device vanished! > uhub_reattach_port:370: giving up port reset - device vanished! > uhub_reattach_port:370: giving up port reset - device vanished! > uhub_reattach_port:370: giving up port reset - device vanished! > uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT > uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling port 5 > uhub_reattach_port:370: giving up port reset - device vanished! > usb2_alloc_device:1417: set address 2 failed (ignored) > usb2_alloc_device:1452: getting device descriptor at addr 2 failed! > uhub_reattach_port:401: could not allocate new device! > > usb2_alloc_device:1417: set address 2 failed (ignored) > usb2_alloc_device:1452: getting device descriptor at addr 2 failed! > uhub_reattach_port:401: could not allocate new device! > > But not so old one from svn was working fine. > >> kldstat > Id Refs Address Size Name > 1 155 0xc0400000 51f700 kernel (/boot/kernel/kernel) > 2 2 0xc0920000 51bb0 sound.ko (/boot/kernel/sound.ko) > 3 1 0xc0972000 1a5e0 snd_hda.ko (/boot/kernel/snd_hda.ko) > 4 2 0xc098d000 18170 agp.ko (/boot/kernel/agp.ko) > 5 1 0xc09a6000 c3fc random.ko (/boot/kernel/random.ko) > 6 2 0xc09b3000 16b14 drm.ko (/boot/kernel/drm.ko) > 7 1 0xc09ca000 af9c i915.ko (/boot/kernel/i915.ko) > 8 5 0xc09d5000 e3cc ata.ko (/boot/kernel/ata.ko) > 9 2 0xc09e4000 5230 ataahci.ko (/boot/kernel/ataahci.ko) > 10 3 0xc09ea000 88b0 atapci.ko (/boot/kernel/atapci.ko) > 11 1 0xc09f3000 4638 atadisk.ko (/boot/kernel/atadisk.ko) > 12 1 0xc09f8000 5834 ataintel.ko (/boot/kernel/ataintel.ko) > 13 1 0xc09fe000 be08 cpufreq.ko (/boot/kernel/cpufreq.ko) > 14 1 0xc0a0a000 4dc8 sysvmsg.ko (/boot/kernel/sysvmsg.ko) > 15 1 0xc0a0f000 5e9c sysvsem.ko (/boot/kernel/sysvsem.ko) > 16 1 0xc0a15000 5034 sysvshm.ko (/boot/kernel/sysvshm.ko) > 17 1 0xc0a1b000 6b974 acpi.ko (/boot/kernel/acpi.ko) > 18 9 0xc462c000 35000 usb2_core.ko (/boot/kernel/usb2_core.ko) > 19 4 0xc46eb000 3000 usb2_controller.ko > (/boot/kernel/usb2_controller.ko) > 20 1 0xc46f8000 a000 usb2_controller_uhci.ko > (/boot/kernel/usb2_controller_uhci.ko) > 21 1 0xc474e000 c000 usb2_controller_ehci.ko > (/boot/kernel/usb2_controller_ehci.ko) > 22 1 0xc477b000 a000 usb2_controller_ohci.ko > (/boot/kernel/usb2_controller_ohci.ko) > 23 1 0xc47a8000 a000 usb2_storage_mass.ko > (/boot/kernel/usb2_storage_mass.ko) > 24 1 0xc47b2000 43000 cam.ko (/boot/kernel/cam.ko) > 25 1 0xc47fe000 2000 usb2_storage.ko (/boot/kernel/usb2_storage.ko) > 26 1 0xc4800000 a000 usb2_wlan_rum.ko (/boot/kernel/usb2_wlan_rum.ko) > 27 1 0xc480a000 2000 wlan_amrr.ko (/boot/kernel/wlan_amrr.ko) > 28 4 0xc480c000 34000 wlan.ko (/boot/kernel/wlan.ko) > 29 1 0xc4849000 2000 usb2_wlan.ko (/boot/kernel/usb2_wlan.ko) > After some time it will appear but will start attaching and dettaching all the time: ugen4.2: at usbus4 rum0: on usbus4 rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 rum0: at ushub4, port 6, addr 2 (disconnected) rum0: detached ugen4.2: at usbus4 rum0: on usbus4 rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 rum0: at ushub4, port 6, addr 2 (disconnected) rum0: detached ugen2.2: at usbus2 rum0: on usbus2 rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 rum0: at ushub2, port 2, addr 2 (disconnected) rum0: detached From onemda at gmail.com Fri Nov 7 12:18:38 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Fri Nov 7 12:18:49 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <3a142e750811071202h765c64a0g820db4fe54ec9b4f@mail.gmail.com> References: <200810251925.47273.hselasky@c2i.net> <20081106191230.GA47600@wep4035.physik.uni-wuerzburg.de> <20081106210300.GA1595@wep4035.physik.uni-wuerzburg.de> <200811070036.15816.hselasky@c2i.net> <3a142e750811071154y5108f299h60bb7c1060f4567e@mail.gmail.com> <3a142e750811071202h765c64a0g820db4fe54ec9b4f@mail.gmail.com> Message-ID: <3a142e750811071218q7c104687j9b55572319ddb5df@mail.gmail.com> On 11/7/08, Paul B. Mahol wrote: > On 11/7/08, Paul B. Mahol wrote: >> On recent CURRENT when attaching rum card, strange bug appear: >> >> usb2_alloc_device:1417: set address 2 failed (ignored) >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! >> uhub_reattach_port:401: could not allocate new device! >> >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling port 5 >> uhub_reattach_port:370: giving up port reset - device vanished! >> uhub_reattach_port:370: giving up port reset - device vanished! >> uhub_reattach_port:370: giving up port reset - device vanished! >> uhub_reattach_port:370: giving up port reset - device vanished! >> uhub_reattach_port:370: giving up port reset - device vanished! >> uhub_reattach_port:370: giving up port reset - device vanished! >> uhub_reattach_port:370: giving up port reset - device vanished! >> uhub_reattach_port:370: giving up port reset - device vanished! >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling port 5 >> uhub_reattach_port:370: giving up port reset - device vanished! >> usb2_alloc_device:1417: set address 2 failed (ignored) >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! >> uhub_reattach_port:401: could not allocate new device! >> >> usb2_alloc_device:1417: set address 2 failed (ignored) >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! >> uhub_reattach_port:401: could not allocate new device! >> >> But not so old one from svn was working fine. >> >>> kldstat >> Id Refs Address Size Name >> 1 155 0xc0400000 51f700 kernel (/boot/kernel/kernel) >> 2 2 0xc0920000 51bb0 sound.ko (/boot/kernel/sound.ko) >> 3 1 0xc0972000 1a5e0 snd_hda.ko (/boot/kernel/snd_hda.ko) >> 4 2 0xc098d000 18170 agp.ko (/boot/kernel/agp.ko) >> 5 1 0xc09a6000 c3fc random.ko (/boot/kernel/random.ko) >> 6 2 0xc09b3000 16b14 drm.ko (/boot/kernel/drm.ko) >> 7 1 0xc09ca000 af9c i915.ko (/boot/kernel/i915.ko) >> 8 5 0xc09d5000 e3cc ata.ko (/boot/kernel/ata.ko) >> 9 2 0xc09e4000 5230 ataahci.ko (/boot/kernel/ataahci.ko) >> 10 3 0xc09ea000 88b0 atapci.ko (/boot/kernel/atapci.ko) >> 11 1 0xc09f3000 4638 atadisk.ko (/boot/kernel/atadisk.ko) >> 12 1 0xc09f8000 5834 ataintel.ko (/boot/kernel/ataintel.ko) >> 13 1 0xc09fe000 be08 cpufreq.ko (/boot/kernel/cpufreq.ko) >> 14 1 0xc0a0a000 4dc8 sysvmsg.ko (/boot/kernel/sysvmsg.ko) >> 15 1 0xc0a0f000 5e9c sysvsem.ko (/boot/kernel/sysvsem.ko) >> 16 1 0xc0a15000 5034 sysvshm.ko (/boot/kernel/sysvshm.ko) >> 17 1 0xc0a1b000 6b974 acpi.ko (/boot/kernel/acpi.ko) >> 18 9 0xc462c000 35000 usb2_core.ko (/boot/kernel/usb2_core.ko) >> 19 4 0xc46eb000 3000 usb2_controller.ko >> (/boot/kernel/usb2_controller.ko) >> 20 1 0xc46f8000 a000 usb2_controller_uhci.ko >> (/boot/kernel/usb2_controller_uhci.ko) >> 21 1 0xc474e000 c000 usb2_controller_ehci.ko >> (/boot/kernel/usb2_controller_ehci.ko) >> 22 1 0xc477b000 a000 usb2_controller_ohci.ko >> (/boot/kernel/usb2_controller_ohci.ko) >> 23 1 0xc47a8000 a000 usb2_storage_mass.ko >> (/boot/kernel/usb2_storage_mass.ko) >> 24 1 0xc47b2000 43000 cam.ko (/boot/kernel/cam.ko) >> 25 1 0xc47fe000 2000 usb2_storage.ko (/boot/kernel/usb2_storage.ko) >> 26 1 0xc4800000 a000 usb2_wlan_rum.ko >> (/boot/kernel/usb2_wlan_rum.ko) >> 27 1 0xc480a000 2000 wlan_amrr.ko (/boot/kernel/wlan_amrr.ko) >> 28 4 0xc480c000 34000 wlan.ko (/boot/kernel/wlan.ko) >> 29 1 0xc4849000 2000 usb2_wlan.ko (/boot/kernel/usb2_wlan.ko) >> > > After some time it will appear but will start attaching and dettaching > all the time: > > ugen4.2: at usbus4 > rum0: on usbus4 > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 > rum0: at ushub4, port 6, addr 2 (disconnected) > rum0: detached > ugen4.2: at usbus4 > rum0: on usbus4 > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 > rum0: at ushub4, port 6, addr 2 (disconnected) > rum0: detached > ugen2.2: at usbus2 > rum0: on usbus2 > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 > rum0: at ushub2, port 2, addr 2 (disconnected) > rum0: detached > Looks like some code is missing because loading only usb2_wlan_rum do not load ehci and uhci usb2 modules. (causing card to not attach) I managed to get card working with usb2_controller_uhci and usb2_controller_ehci loaded. (without ohci) From imp at bsdimp.com Fri Nov 7 12:23:47 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Fri Nov 7 12:23:56 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <3a142e750811071218q7c104687j9b55572319ddb5df@mail.gmail.com> References: <3a142e750811071154y5108f299h60bb7c1060f4567e@mail.gmail.com> <3a142e750811071202h765c64a0g820db4fe54ec9b4f@mail.gmail.com> <3a142e750811071218q7c104687j9b55572319ddb5df@mail.gmail.com> Message-ID: <20081107.132401.1622434515.imp@bsdimp.com> In message: <3a142e750811071218q7c104687j9b55572319ddb5df@mail.gmail.com> "Paul B. Mahol" writes: : On 11/7/08, Paul B. Mahol wrote: : > On 11/7/08, Paul B. Mahol wrote: : >> On recent CURRENT when attaching rum card, strange bug appear: : >> : >> usb2_alloc_device:1417: set address 2 failed (ignored) : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! : >> uhub_reattach_port:401: could not allocate new device! : >> : >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT : >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling port 5 : >> uhub_reattach_port:370: giving up port reset - device vanished! : >> uhub_reattach_port:370: giving up port reset - device vanished! : >> uhub_reattach_port:370: giving up port reset - device vanished! : >> uhub_reattach_port:370: giving up port reset - device vanished! : >> uhub_reattach_port:370: giving up port reset - device vanished! : >> uhub_reattach_port:370: giving up port reset - device vanished! : >> uhub_reattach_port:370: giving up port reset - device vanished! : >> uhub_reattach_port:370: giving up port reset - device vanished! : >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT : >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling port 5 : >> uhub_reattach_port:370: giving up port reset - device vanished! : >> usb2_alloc_device:1417: set address 2 failed (ignored) : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! : >> uhub_reattach_port:401: could not allocate new device! : >> : >> usb2_alloc_device:1417: set address 2 failed (ignored) : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! : >> uhub_reattach_port:401: could not allocate new device! : >> : >> But not so old one from svn was working fine. : >> : >>> kldstat : >> Id Refs Address Size Name : >> 1 155 0xc0400000 51f700 kernel (/boot/kernel/kernel) : >> 2 2 0xc0920000 51bb0 sound.ko (/boot/kernel/sound.ko) : >> 3 1 0xc0972000 1a5e0 snd_hda.ko (/boot/kernel/snd_hda.ko) : >> 4 2 0xc098d000 18170 agp.ko (/boot/kernel/agp.ko) : >> 5 1 0xc09a6000 c3fc random.ko (/boot/kernel/random.ko) : >> 6 2 0xc09b3000 16b14 drm.ko (/boot/kernel/drm.ko) : >> 7 1 0xc09ca000 af9c i915.ko (/boot/kernel/i915.ko) : >> 8 5 0xc09d5000 e3cc ata.ko (/boot/kernel/ata.ko) : >> 9 2 0xc09e4000 5230 ataahci.ko (/boot/kernel/ataahci.ko) : >> 10 3 0xc09ea000 88b0 atapci.ko (/boot/kernel/atapci.ko) : >> 11 1 0xc09f3000 4638 atadisk.ko (/boot/kernel/atadisk.ko) : >> 12 1 0xc09f8000 5834 ataintel.ko (/boot/kernel/ataintel.ko) : >> 13 1 0xc09fe000 be08 cpufreq.ko (/boot/kernel/cpufreq.ko) : >> 14 1 0xc0a0a000 4dc8 sysvmsg.ko (/boot/kernel/sysvmsg.ko) : >> 15 1 0xc0a0f000 5e9c sysvsem.ko (/boot/kernel/sysvsem.ko) : >> 16 1 0xc0a15000 5034 sysvshm.ko (/boot/kernel/sysvshm.ko) : >> 17 1 0xc0a1b000 6b974 acpi.ko (/boot/kernel/acpi.ko) : >> 18 9 0xc462c000 35000 usb2_core.ko (/boot/kernel/usb2_core.ko) : >> 19 4 0xc46eb000 3000 usb2_controller.ko : >> (/boot/kernel/usb2_controller.ko) : >> 20 1 0xc46f8000 a000 usb2_controller_uhci.ko : >> (/boot/kernel/usb2_controller_uhci.ko) : >> 21 1 0xc474e000 c000 usb2_controller_ehci.ko : >> (/boot/kernel/usb2_controller_ehci.ko) : >> 22 1 0xc477b000 a000 usb2_controller_ohci.ko : >> (/boot/kernel/usb2_controller_ohci.ko) : >> 23 1 0xc47a8000 a000 usb2_storage_mass.ko : >> (/boot/kernel/usb2_storage_mass.ko) : >> 24 1 0xc47b2000 43000 cam.ko (/boot/kernel/cam.ko) : >> 25 1 0xc47fe000 2000 usb2_storage.ko (/boot/kernel/usb2_storage.ko) : >> 26 1 0xc4800000 a000 usb2_wlan_rum.ko : >> (/boot/kernel/usb2_wlan_rum.ko) : >> 27 1 0xc480a000 2000 wlan_amrr.ko (/boot/kernel/wlan_amrr.ko) : >> 28 4 0xc480c000 34000 wlan.ko (/boot/kernel/wlan.ko) : >> 29 1 0xc4849000 2000 usb2_wlan.ko (/boot/kernel/usb2_wlan.ko) : >> : > : > After some time it will appear but will start attaching and dettaching : > all the time: : > : > ugen4.2: at usbus4 : > rum0: on usbus4 : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 : > rum0: at ushub4, port 6, addr 2 (disconnected) : > rum0: detached : > ugen4.2: at usbus4 : > rum0: on usbus4 : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 : > rum0: at ushub4, port 6, addr 2 (disconnected) : > rum0: detached : > ugen2.2: at usbus2 : > rum0: on usbus2 : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 : > rum0: at ushub2, port 2, addr 2 (disconnected) : > rum0: detached : > : : Looks like some code is missing because loading only usb2_wlan_rum do : not load ehci and uhci usb2 modules. (causing card to not attach) : : I managed to get card working with usb2_controller_uhci and : usb2_controller_ehci loaded. (without ohci) That's not a bug. Warner From onemda at gmail.com Fri Nov 7 12:29:03 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Fri Nov 7 12:29:15 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <20081107.132401.1622434515.imp@bsdimp.com> References: <3a142e750811071154y5108f299h60bb7c1060f4567e@mail.gmail.com> <3a142e750811071202h765c64a0g820db4fe54ec9b4f@mail.gmail.com> <3a142e750811071218q7c104687j9b55572319ddb5df@mail.gmail.com> <20081107.132401.1622434515.imp@bsdimp.com> Message-ID: <3a142e750811071229r6d452b28t7979ab08e1c90d71@mail.gmail.com> On 11/7/08, M. Warner Losh wrote: > In message: <3a142e750811071218q7c104687j9b55572319ddb5df@mail.gmail.com> > "Paul B. Mahol" writes: > : On 11/7/08, Paul B. Mahol wrote: > : > On 11/7/08, Paul B. Mahol wrote: > : >> On recent CURRENT when attaching rum card, strange bug appear: > : >> > : >> usb2_alloc_device:1417: set address 2 failed (ignored) > : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! > : >> uhub_reattach_port:401: could not allocate new device! > : >> > : >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT > : >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling > port 5 > : >> uhub_reattach_port:370: giving up port reset - device vanished! > : >> uhub_reattach_port:370: giving up port reset - device vanished! > : >> uhub_reattach_port:370: giving up port reset - device vanished! > : >> uhub_reattach_port:370: giving up port reset - device vanished! > : >> uhub_reattach_port:370: giving up port reset - device vanished! > : >> uhub_reattach_port:370: giving up port reset - device vanished! > : >> uhub_reattach_port:370: giving up port reset - device vanished! > : >> uhub_reattach_port:370: giving up port reset - device vanished! > : >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT > : >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling > port 5 > : >> uhub_reattach_port:370: giving up port reset - device vanished! > : >> usb2_alloc_device:1417: set address 2 failed (ignored) > : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! > : >> uhub_reattach_port:401: could not allocate new device! > : >> > : >> usb2_alloc_device:1417: set address 2 failed (ignored) > : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! > : >> uhub_reattach_port:401: could not allocate new device! > : >> > : >> But not so old one from svn was working fine. > : >> > : >>> kldstat > : >> Id Refs Address Size Name > : >> 1 155 0xc0400000 51f700 kernel (/boot/kernel/kernel) > : >> 2 2 0xc0920000 51bb0 sound.ko (/boot/kernel/sound.ko) > : >> 3 1 0xc0972000 1a5e0 snd_hda.ko (/boot/kernel/snd_hda.ko) > : >> 4 2 0xc098d000 18170 agp.ko (/boot/kernel/agp.ko) > : >> 5 1 0xc09a6000 c3fc random.ko (/boot/kernel/random.ko) > : >> 6 2 0xc09b3000 16b14 drm.ko (/boot/kernel/drm.ko) > : >> 7 1 0xc09ca000 af9c i915.ko (/boot/kernel/i915.ko) > : >> 8 5 0xc09d5000 e3cc ata.ko (/boot/kernel/ata.ko) > : >> 9 2 0xc09e4000 5230 ataahci.ko (/boot/kernel/ataahci.ko) > : >> 10 3 0xc09ea000 88b0 atapci.ko (/boot/kernel/atapci.ko) > : >> 11 1 0xc09f3000 4638 atadisk.ko (/boot/kernel/atadisk.ko) > : >> 12 1 0xc09f8000 5834 ataintel.ko (/boot/kernel/ataintel.ko) > : >> 13 1 0xc09fe000 be08 cpufreq.ko (/boot/kernel/cpufreq.ko) > : >> 14 1 0xc0a0a000 4dc8 sysvmsg.ko (/boot/kernel/sysvmsg.ko) > : >> 15 1 0xc0a0f000 5e9c sysvsem.ko (/boot/kernel/sysvsem.ko) > : >> 16 1 0xc0a15000 5034 sysvshm.ko (/boot/kernel/sysvshm.ko) > : >> 17 1 0xc0a1b000 6b974 acpi.ko (/boot/kernel/acpi.ko) > : >> 18 9 0xc462c000 35000 usb2_core.ko (/boot/kernel/usb2_core.ko) > : >> 19 4 0xc46eb000 3000 usb2_controller.ko > : >> (/boot/kernel/usb2_controller.ko) > : >> 20 1 0xc46f8000 a000 usb2_controller_uhci.ko > : >> (/boot/kernel/usb2_controller_uhci.ko) > : >> 21 1 0xc474e000 c000 usb2_controller_ehci.ko > : >> (/boot/kernel/usb2_controller_ehci.ko) > : >> 22 1 0xc477b000 a000 usb2_controller_ohci.ko > : >> (/boot/kernel/usb2_controller_ohci.ko) > : >> 23 1 0xc47a8000 a000 usb2_storage_mass.ko > : >> (/boot/kernel/usb2_storage_mass.ko) > : >> 24 1 0xc47b2000 43000 cam.ko (/boot/kernel/cam.ko) > : >> 25 1 0xc47fe000 2000 usb2_storage.ko > (/boot/kernel/usb2_storage.ko) > : >> 26 1 0xc4800000 a000 usb2_wlan_rum.ko > : >> (/boot/kernel/usb2_wlan_rum.ko) > : >> 27 1 0xc480a000 2000 wlan_amrr.ko (/boot/kernel/wlan_amrr.ko) > : >> 28 4 0xc480c000 34000 wlan.ko (/boot/kernel/wlan.ko) > : >> 29 1 0xc4849000 2000 usb2_wlan.ko (/boot/kernel/usb2_wlan.ko) > : >> > : > > : > After some time it will appear but will start attaching and dettaching > : > all the time: > : > > : > ugen4.2: at usbus4 > : > rum0: on > usbus4 > : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 > : > rum0: at ushub4, port 6, addr 2 (disconnected) > : > rum0: detached > : > ugen4.2: at usbus4 > : > rum0: on > usbus4 > : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 > : > rum0: at ushub4, port 6, addr 2 (disconnected) > : > rum0: detached > : > ugen2.2: at usbus2 > : > rum0: on > usbus2 > : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 > : > rum0: at ushub2, port 2, addr 2 (disconnected) > : > rum0: detached > : > > : > : Looks like some code is missing because loading only usb2_wlan_rum do > : not load ehci and uhci usb2 modules. (causing card to not attach) > : > : I managed to get card working with usb2_controller_uhci and > : usb2_controller_ehci loaded. (without ohci) > > That's not a bug. Really, how then to explain that I cannot make card working properly whan having both uhci2, ehci2 and ohci2 loaded Loading usb2_controller_musb fail, with message: link_elf: symbol usb2_sw_transfer undefined From imp at bsdimp.com Fri Nov 7 12:50:48 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Fri Nov 7 12:51:00 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <3a142e750811071229r6d452b28t7979ab08e1c90d71@mail.gmail.com> References: <3a142e750811071218q7c104687j9b55572319ddb5df@mail.gmail.com> <20081107.132401.1622434515.imp@bsdimp.com> <3a142e750811071229r6d452b28t7979ab08e1c90d71@mail.gmail.com> Message-ID: <20081107.134946.811533952.imp@bsdimp.com> In message: <3a142e750811071229r6d452b28t7979ab08e1c90d71@mail.gmail.com> "Paul B. Mahol" writes: : On 11/7/08, M. Warner Losh wrote: : > In message: <3a142e750811071218q7c104687j9b55572319ddb5df@mail.gmail.com> : > "Paul B. Mahol" writes: : > : On 11/7/08, Paul B. Mahol wrote: : > : > On 11/7/08, Paul B. Mahol wrote: : > : >> On recent CURRENT when attaching rum card, strange bug appear: : > : >> : > : >> usb2_alloc_device:1417: set address 2 failed (ignored) : > : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! : > : >> uhub_reattach_port:401: could not allocate new device! : > : >> : > : >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT : > : >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling : > port 5 : > : >> uhub_reattach_port:370: giving up port reset - device vanished! : > : >> uhub_reattach_port:370: giving up port reset - device vanished! : > : >> uhub_reattach_port:370: giving up port reset - device vanished! : > : >> uhub_reattach_port:370: giving up port reset - device vanished! : > : >> uhub_reattach_port:370: giving up port reset - device vanished! : > : >> uhub_reattach_port:370: giving up port reset - device vanished! : > : >> uhub_reattach_port:370: giving up port reset - device vanished! : > : >> uhub_reattach_port:370: giving up port reset - device vanished! : > : >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT : > : >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling : > port 5 : > : >> uhub_reattach_port:370: giving up port reset - device vanished! : > : >> usb2_alloc_device:1417: set address 2 failed (ignored) : > : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! : > : >> uhub_reattach_port:401: could not allocate new device! : > : >> : > : >> usb2_alloc_device:1417: set address 2 failed (ignored) : > : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! : > : >> uhub_reattach_port:401: could not allocate new device! : > : >> : > : >> But not so old one from svn was working fine. : > : >> : > : >>> kldstat : > : >> Id Refs Address Size Name : > : >> 1 155 0xc0400000 51f700 kernel (/boot/kernel/kernel) : > : >> 2 2 0xc0920000 51bb0 sound.ko (/boot/kernel/sound.ko) : > : >> 3 1 0xc0972000 1a5e0 snd_hda.ko (/boot/kernel/snd_hda.ko) : > : >> 4 2 0xc098d000 18170 agp.ko (/boot/kernel/agp.ko) : > : >> 5 1 0xc09a6000 c3fc random.ko (/boot/kernel/random.ko) : > : >> 6 2 0xc09b3000 16b14 drm.ko (/boot/kernel/drm.ko) : > : >> 7 1 0xc09ca000 af9c i915.ko (/boot/kernel/i915.ko) : > : >> 8 5 0xc09d5000 e3cc ata.ko (/boot/kernel/ata.ko) : > : >> 9 2 0xc09e4000 5230 ataahci.ko (/boot/kernel/ataahci.ko) : > : >> 10 3 0xc09ea000 88b0 atapci.ko (/boot/kernel/atapci.ko) : > : >> 11 1 0xc09f3000 4638 atadisk.ko (/boot/kernel/atadisk.ko) : > : >> 12 1 0xc09f8000 5834 ataintel.ko (/boot/kernel/ataintel.ko) : > : >> 13 1 0xc09fe000 be08 cpufreq.ko (/boot/kernel/cpufreq.ko) : > : >> 14 1 0xc0a0a000 4dc8 sysvmsg.ko (/boot/kernel/sysvmsg.ko) : > : >> 15 1 0xc0a0f000 5e9c sysvsem.ko (/boot/kernel/sysvsem.ko) : > : >> 16 1 0xc0a15000 5034 sysvshm.ko (/boot/kernel/sysvshm.ko) : > : >> 17 1 0xc0a1b000 6b974 acpi.ko (/boot/kernel/acpi.ko) : > : >> 18 9 0xc462c000 35000 usb2_core.ko (/boot/kernel/usb2_core.ko) : > : >> 19 4 0xc46eb000 3000 usb2_controller.ko : > : >> (/boot/kernel/usb2_controller.ko) : > : >> 20 1 0xc46f8000 a000 usb2_controller_uhci.ko : > : >> (/boot/kernel/usb2_controller_uhci.ko) : > : >> 21 1 0xc474e000 c000 usb2_controller_ehci.ko : > : >> (/boot/kernel/usb2_controller_ehci.ko) : > : >> 22 1 0xc477b000 a000 usb2_controller_ohci.ko : > : >> (/boot/kernel/usb2_controller_ohci.ko) : > : >> 23 1 0xc47a8000 a000 usb2_storage_mass.ko : > : >> (/boot/kernel/usb2_storage_mass.ko) : > : >> 24 1 0xc47b2000 43000 cam.ko (/boot/kernel/cam.ko) : > : >> 25 1 0xc47fe000 2000 usb2_storage.ko : > (/boot/kernel/usb2_storage.ko) : > : >> 26 1 0xc4800000 a000 usb2_wlan_rum.ko : > : >> (/boot/kernel/usb2_wlan_rum.ko) : > : >> 27 1 0xc480a000 2000 wlan_amrr.ko (/boot/kernel/wlan_amrr.ko) : > : >> 28 4 0xc480c000 34000 wlan.ko (/boot/kernel/wlan.ko) : > : >> 29 1 0xc4849000 2000 usb2_wlan.ko (/boot/kernel/usb2_wlan.ko) : > : >> : > : > : > : > After some time it will appear but will start attaching and dettaching : > : > all the time: : > : > : > : > ugen4.2: at usbus4 : > : > rum0: on : > usbus4 : > : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 : > : > rum0: at ushub4, port 6, addr 2 (disconnected) : > : > rum0: detached : > : > ugen4.2: at usbus4 : > : > rum0: on : > usbus4 : > : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 : > : > rum0: at ushub4, port 6, addr 2 (disconnected) : > : > rum0: detached : > : > ugen2.2: at usbus2 : > : > rum0: on : > usbus2 : > : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 : > : > rum0: at ushub2, port 2, addr 2 (disconnected) : > : > rum0: detached : > : > : > : : > : Looks like some code is missing because loading only usb2_wlan_rum do : > : not load ehci and uhci usb2 modules. (causing card to not attach) : > : : > : I managed to get card working with usb2_controller_uhci and : > : usb2_controller_ehci loaded. (without ohci) : > : > That's not a bug. : : Really, how then to explain that I cannot make card working properly : whan having both uhci2, ehci2 and ohci2 loaded You are supposed to load them yourself. The leaf modules shouldn't know about the controllers. There may be other bugs here, but not loading the host controllers isn't one of them. Warner From dougb at FreeBSD.org Fri Nov 7 13:06:11 2008 From: dougb at FreeBSD.org (Doug Barton) Date: Fri Nov 7 13:06:23 2008 Subject: Kernel without INET In-Reply-To: <20081106153035.R16105@maildrop.int.zabbadoz.net> References: <20081106153035.R16105@maildrop.int.zabbadoz.net> Message-ID: <4914A782.6030509@FreeBSD.org> Not that I object to this at all, but out of curiosity what is the motivation? I would imagine "embedded devices that run stuff not connected to the 'net" but hoping for something more interesting/exciting. :) Doug -- This .signature sanitized for your protection From hselasky at c2i.net Fri Nov 7 13:21:13 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 13:21:26 2008 Subject: Kernel panic when copying data to umass device (USB4BSD) - problem found In-Reply-To: <20081107191935.GA51170@localhost.my.domain> References: <20081107082740.GA1334@icarus.home.lan> <200811071811.27181.hselasky@c2i.net> <20081107191935.GA51170@localhost.my.domain> Message-ID: <200811072223.20313.hselasky@c2i.net> On Friday 07 November 2008, Alexey Shuvaev wrote: > On Fri, Nov 07, 2008 at 06:11:26PM +0100, Hans Petter Selasky wrote: > > Hi Jeremy, > > > > I've reproduced the issue with some mods to the usb2_busdma.c on 32-bit > > arcitecture and have made a fix for this problem. > > > > Try the following patch and re-test! > > Thanks a lot! I have rebuild the kernel with this patch > > > http://perforce.freebsd.org/chv.cgi?CH=152624 > > and so far no panics. Indeed, the system I am using is amd64 with 4Gb of > RAM. > > > Some mem-stick benchmarks would be nice ... > > What exactly do you mean? > I have done: > dd if=file_on_one_stick of=/dev/null bs=1m (12.5 Mb/s) > dd if=/dev/random of=file_on_the_stick bs=1m count=128 (2.6 Mb/s) > > and the same tests with USB-microSDHC adapter with 8Gb card > (20 MB/s read, 15 Mb/s write). > > Anything else? No, that looks very good. Maybe you could also do a md5 on the transferred data, just to see if there are data errors. BTW: I have forced my 32-bit system to use bounce buffers now, and I have found more problems! Warner: I see that bus-dma is allocating bounce buffers for the EHCI/OHCI/UHCI transfer descriptors and queue heads, even though I use "bus_dmamem_alloc()" with the COHERENT flag and everything. I suspect that the problem is that "bus_dmamem_alloc()" is optimised to use "malloc()" which then automatically will imply a possible bounce buffer. Even if I use PAGE_SIZE byte allocations it goes wrong. Maybe I also need to set the alignment to PAGE_SIZE bytes, to really ensure that "busdma" is not putting the TD's and QH's in the wrong part of the memory from the beginning? This is a big problem, because the busdma API does not allow flushing single fields of these descriptors, which is an absolute mandatory feature during USB operation. On NetBSD this is possible. What should we do? I guess this is the root problem of USB(2) not working reliable on 64-bit architectures. --HPS From hselasky at c2i.net Fri Nov 7 13:31:45 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 13:31:58 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <3a142e750811071229r6d452b28t7979ab08e1c90d71@mail.gmail.com> References: <3a142e750811071154y5108f299h60bb7c1060f4567e@mail.gmail.com> <20081107.132401.1622434515.imp@bsdimp.com> <3a142e750811071229r6d452b28t7979ab08e1c90d71@mail.gmail.com> Message-ID: <200811072233.46558.hselasky@c2i.net> On Friday 07 November 2008, Paul B. Mahol wrote: > On 11/7/08, M. Warner Losh wrote: > > In message: <3a142e750811071218q7c104687j9b55572319ddb5df@mail.gmail.com> > > > > "Paul B. Mahol" writes: > > : On 11/7/08, Paul B. Mahol wrote: > > : > On 11/7/08, Paul B. Mahol wrote: > > : >> On recent CURRENT when attaching rum card, strange bug appear: > > : >> > > : >> usb2_alloc_device:1417: set address 2 failed (ignored) > > : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! > > : >> uhub_reattach_port:401: could not allocate new device! > > : >> > > : >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT > > : >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling > > > > port 5 > > > > : >> uhub_reattach_port:370: giving up port reset - device vanished! > > : >> uhub_reattach_port:370: giving up port reset - device vanished! > > : >> uhub_reattach_port:370: giving up port reset - device vanished! > > : >> uhub_reattach_port:370: giving up port reset - device vanished! > > : >> uhub_reattach_port:370: giving up port reset - device vanished! > > : >> uhub_reattach_port:370: giving up port reset - device vanished! > > : >> uhub_reattach_port:370: giving up port reset - device vanished! > > : >> uhub_reattach_port:370: giving up port reset - device vanished! > > : >> uhub_reattach_port:355: port 5 reset failed, error=USB_ERR_TIMEOUT > > : >> uhub_reattach_port:421: device problem (USB_ERR_TIMEOUT), disabling > > > > port 5 > > > > : >> uhub_reattach_port:370: giving up port reset - device vanished! > > : >> usb2_alloc_device:1417: set address 2 failed (ignored) > > : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! > > : >> uhub_reattach_port:401: could not allocate new device! > > : >> > > : >> usb2_alloc_device:1417: set address 2 failed (ignored) > > : >> usb2_alloc_device:1452: getting device descriptor at addr 2 failed! > > : >> uhub_reattach_port:401: could not allocate new device! > > : >> > > : >> But not so old one from svn was working fine. > > : >> > > : >>> kldstat > > : >> > > : >> Id Refs Address Size Name > > : >> 1 155 0xc0400000 51f700 kernel (/boot/kernel/kernel) > > : >> 2 2 0xc0920000 51bb0 sound.ko (/boot/kernel/sound.ko) > > : >> 3 1 0xc0972000 1a5e0 snd_hda.ko (/boot/kernel/snd_hda.ko) > > : >> 4 2 0xc098d000 18170 agp.ko (/boot/kernel/agp.ko) > > : >> 5 1 0xc09a6000 c3fc random.ko (/boot/kernel/random.ko) > > : >> 6 2 0xc09b3000 16b14 drm.ko (/boot/kernel/drm.ko) > > : >> 7 1 0xc09ca000 af9c i915.ko (/boot/kernel/i915.ko) > > : >> 8 5 0xc09d5000 e3cc ata.ko (/boot/kernel/ata.ko) > > : >> 9 2 0xc09e4000 5230 ataahci.ko (/boot/kernel/ataahci.ko) > > : >> 10 3 0xc09ea000 88b0 atapci.ko (/boot/kernel/atapci.ko) > > : >> 11 1 0xc09f3000 4638 atadisk.ko (/boot/kernel/atadisk.ko) > > : >> 12 1 0xc09f8000 5834 ataintel.ko (/boot/kernel/ataintel.ko) > > : >> 13 1 0xc09fe000 be08 cpufreq.ko (/boot/kernel/cpufreq.ko) > > : >> 14 1 0xc0a0a000 4dc8 sysvmsg.ko (/boot/kernel/sysvmsg.ko) > > : >> 15 1 0xc0a0f000 5e9c sysvsem.ko (/boot/kernel/sysvsem.ko) > > : >> 16 1 0xc0a15000 5034 sysvshm.ko (/boot/kernel/sysvshm.ko) > > : >> 17 1 0xc0a1b000 6b974 acpi.ko (/boot/kernel/acpi.ko) > > : >> 18 9 0xc462c000 35000 usb2_core.ko (/boot/kernel/usb2_core.ko) > > : >> 19 4 0xc46eb000 3000 usb2_controller.ko > > : >> (/boot/kernel/usb2_controller.ko) > > : >> 20 1 0xc46f8000 a000 usb2_controller_uhci.ko > > : >> (/boot/kernel/usb2_controller_uhci.ko) > > : >> 21 1 0xc474e000 c000 usb2_controller_ehci.ko > > : >> (/boot/kernel/usb2_controller_ehci.ko) > > : >> 22 1 0xc477b000 a000 usb2_controller_ohci.ko > > : >> (/boot/kernel/usb2_controller_ohci.ko) > > : >> 23 1 0xc47a8000 a000 usb2_storage_mass.ko > > : >> (/boot/kernel/usb2_storage_mass.ko) > > : >> 24 1 0xc47b2000 43000 cam.ko (/boot/kernel/cam.ko) > > : >> 25 1 0xc47fe000 2000 usb2_storage.ko > > > > (/boot/kernel/usb2_storage.ko) > > > > : >> 26 1 0xc4800000 a000 usb2_wlan_rum.ko > > : >> (/boot/kernel/usb2_wlan_rum.ko) > > : >> 27 1 0xc480a000 2000 wlan_amrr.ko (/boot/kernel/wlan_amrr.ko) > > : >> 28 4 0xc480c000 34000 wlan.ko (/boot/kernel/wlan.ko) > > : >> 29 1 0xc4849000 2000 usb2_wlan.ko (/boot/kernel/usb2_wlan.ko) > > : > > > : > After some time it will appear but will start attaching and > > : > dettaching all the time: > > : > > > : > ugen4.2: at usbus4 > > : > rum0: on > > > > usbus4 > > > > : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 > > : > rum0: at ushub4, port 6, addr 2 (disconnected) > > : > rum0: detached > > : > ugen4.2: at usbus4 > > : > rum0: on > > > > usbus4 > > > > : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 > > : > rum0: at ushub4, port 6, addr 2 (disconnected) > > : > rum0: detached > > : > ugen2.2: at usbus2 > > : > rum0: on > > > > usbus2 > > > > : > rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 > > : > rum0: at ushub2, port 2, addr 2 (disconnected) > > : > rum0: detached > > : > > : Looks like some code is missing because loading only usb2_wlan_rum do > > : not load ehci and uhci usb2 modules. (causing card to not attach) > > : > > : I managed to get card working with usb2_controller_uhci and > > : usb2_controller_ehci loaded. (without ohci) > > > > That's not a bug. It is a new feature :-) > > Really, how then to explain that I cannot make card working properly > whan having both uhci2, ehci2 and ohci2 loaded > > Loading usb2_controller_musb fail, with message: > link_elf: symbol usb2_sw_transfer undefined You cannot load that module, because the bus interface file (musb2_otg_atmelarm.c) only compiles on the FreeBSD ARM target, due to some header file dependencies, which we should fix. Therefore there are some missing KLD dependencies in the module which makes it complain about missing symbols, which is not an error, but thanks for reporting. Maybe I will create a dummy PCI module interface for the driver. Mostly the module is there to ensure that the code compiles. These are the KLD dependancy lines: MODULE_DEPEND(musbotg, usb2_controller, 1, 1, 1); MODULE_DEPEND(musbotg, usb2_core, 1, 1, 1); Which are in "musb2_otg_atmelarm.c" which is not compiled into the module by default. --HPS From hselasky at c2i.net Fri Nov 7 13:34:34 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Fri Nov 7 13:34:46 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <3a142e750811071229r6d452b28t7979ab08e1c90d71@mail.gmail.com> References: <3a142e750811071154y5108f299h60bb7c1060f4567e@mail.gmail.com> <20081107.132401.1622434515.imp@bsdimp.com> <3a142e750811071229r6d452b28t7979ab08e1c90d71@mail.gmail.com> Message-ID: <200811072236.38267.hselasky@c2i.net> On Friday 07 November 2008, Paul B. Mahol wrote: > On 11/7/08, M. Warner Losh wrote: > > : > After some time it will appear but will start attaching and > > : > dettaching all the time: How quick is this happening? There has been some changes to the sys/dev/usb2/core/uhub2.c file recently, which control how HUB is responding to events. Maybe you can get the date of that file from the build where it works and the build where it doesn't work, and I will check the differences. --HPS From Thomas.Sparrevohn at btinternet.com Fri Nov 7 11:46:13 2008 From: Thomas.Sparrevohn at btinternet.com (Thomas Sparrevohn) Date: Fri Nov 7 13:45:58 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811070036.15816.hselasky@c2i.net> References: <200810251925.47273.hselasky@c2i.net> <20081106210300.GA1595@wep4035.physik.uni-wuerzburg.de> <200811070036.15816.hselasky@c2i.net> Message-ID: <200811071946.01269.Thomas.Sparrevohn@btinternet.com> On Thursday 06 November 2008 23:36:14 Hans Petter Selasky wrote: > On Thursday 06 November 2008, Alexey Shuvaev wrote: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > _witness_debugger() at _witness_debugger+0x49 > > witness_checkorder() at witness_checkorder+0x7e6 > > _sx_xlock() at _sx_xlock+0x44 > > vm_map_lookup() at vm_map_lookup+0x47 > > vm_fault() at vm_fault+0xfe > > trap_pfault() at trap_pfault+0x1fa > > trap() at trap+0x201 > > calltrap() at calltrap+0x8 > > --- trap 0xc, rip = 0xffffffff804b2466, rsp = 0xfffffffeba7f8ac0, rbp = > > 0xfffffffeba7f8b00 --- bcopy() at bcopy+0x16 > > usb2_bdma_pre_sync() at usb2_bdma_pre_sync+0x35 > > usb2_bdma_work_loop() at usb2_bdma_work_loop+0x29b > > usb2_command_wrapper() at usb2_command_wrapper+0x76 > > usb2_callback_wrapper() at usb2_callback_wrapper+0xfd > > usb2_command_wrapper() at usb2_command_wrapper+0x76 > > usb2_callback_proc() at usb2_callback_proc+0x68 > > usb2_process() at usb2_process+0xc0 > > Hi Alexey, > > This looks more like a busdma problem to me. "bcopy()" is called from > within "bus_dmamap_sync()". Maybe you can figure out if it is the source or > the destination address that fails? > > Looks like your system has started bouncing data to the 32-bit address range. > I can reproduce an error like it whenever I use DMA on umass device - The error somehow are triggered/created by the multiport patches that was introduced in the ATA framework back in April - For a long time I believed it was an error in the ATA frame work until I discovered that If I disabled the umass device the error disappered I am using ZFS on both devices. If I change to usb2_ata the problem disappers. I think that is because usb2_ata does not use DMA. I believe the problem is related to the DMA handling in the umass see attached fault - In short the problem has been around for a long time but it seems to be related to the USB stack DMA handling - before usb2 it showed up as a DMA error in the ATA driver - but that was because the old umass driver somehow "stole" an active DMA w2fzz0vc03.aah-go-on.com dumped core - see /var/crash/vmcore.42 Thu Oct 16 19:11:48 BST 2008 FreeBSD w2fzz0vc03.aah-go-on.com 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Wed Oct 15 21:39:04 BST 2008 sandbox@w2fzz0vc03.aah-go-on.com:/usr/home/sandbox/newusb/obj/usr/home/sandbox/newusb/src/sys/GENERIC_usb2 amd64 panic: mutex Giant not owned at /usr/home/sandbox/newusb/src/sys/kern/tty_ttydisc.c:1129 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 "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex UMASS lock (UMASS lock) r = 0 (0xffffffff80b67e60) locked @ /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_transfer.c:1795 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x49 witness_warn() at witness_warn+0x232 trap() at trap+0x38f calltrap() at calltrap+0x8 --- trap 0xc, rip = 0xffffffff807b2a46, rsp = 0xfffffffeb7267ac0, rbp = 0xfffffffeb7267b00 --- bcopy() at bcopy+0x16 usb2_bdma_pre_sync() at usb2_bdma_pre_sync+0x59 usb2_bdma_work_loop() at usb2_bdma_work_loop+0x2ac usb2_command_wrapper() at usb2_command_wrapper+0x76 usb2_callback_wrapper() at usb2_callback_wrapper+0x101 usb2_command_wrapper() at usb2_command_wrapper+0x76 usb2_callback_proc() at usb2_callback_proc+0x68 usb2_process() at usb2_process+0xc0 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xfffffffeb7267d40, rbp = 0 --- Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0xfffffffe69a00000 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff807b2a46 stack pointer = 0x10:0xfffffffeb7267ac0 frame pointer = 0x10:0xfffffffeb7267b00 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 139 (USBPROC) lock order reversal: (Giant after non-sleepable) 1st 0xffffffff80b67e60 UMASS lock (UMASS lock) @ /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_transfer.c:1795 2nd 0xffffffff80b6bfe0 Giant (Giant) @ /usr/home/sandbox/newusb/src/sys/dev/kbdmux/kbdmux.c:1044 KDB: stack backtrace: panic: mutex Giant not owned at /usr/home/sandbox/newusb/src/sys/kern/tty_ttydisc.c:1129 cpuid = 3 KDB: stack backtrace: Physical memory: 4078 MB Dumping 1154 MB: 1139 1123 1107 1091 1075 1059 1043 1027 1011 995 979 963 947 931 915 899 883 867 851 835 819 803 787 771 755 739 723 707 691 675 659 643 627 611 595 579 563 547 531 515 499 483 467 451 435 419 403 387 371 355 339 323 307 291 275 259 243 227 211 195 179 163 147 131 115 99 83 67 51 35 19 3 Reading symbols from /boot/kernel/zfs.ko...Reading symbols from /bootdir/boot/kernel/zfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/zfs.ko Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from /bootdir/boot/kernel/opensolaris.ko.symbols...done. done. Loaded symbols for /boot/kernel/opensolaris.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /bootdir/boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/daemon_saver.ko...Reading symbols from /bootdir/boot/kernel/daemon_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/daemon_saver.ko #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:196 #1 0xffffffff801c475c in db_fncall (dummy1=Variable "dummy1" is not available. ) at /usr/home/sandbox/newusb/src/sys/ddb/db_command.c:548 #2 0xffffffff801c4a91 in db_command (last_cmdp=0xffffffff80b384a0, cmd_table=Variable "cmd_table" is not available. ) at /usr/home/sandbox/newusb/src/sys/ddb/db_command.c:445 #3 0xffffffff801c4cd9 in db_command_loop () at /usr/home/sandbox/newusb/src/sys/ddb/db_command.c:498 #4 0xffffffff801c6b37 in db_trap (type=Variable "type" is not available. ) at /usr/home/sandbox/newusb/src/sys/ddb/db_main.c:229 #5 0xffffffff8051deb2 in kdb_trap (type=12, code=0, tf=0xfffffffeb7267a10) at /usr/home/sandbox/newusb/src/sys/kern/subr_kdb.c:534 #6 0xffffffff807b361d in trap_fatal (frame=0xfffffffeb7267a10, eva=Variable "eva" is not available. ) at /usr/home/sandbox/newusb/src/sys/amd64/amd64/trap.c:754 #7 0xffffffff807b4371 in trap (frame=0xfffffffeb7267a10) at /usr/home/sandbox/newusb/src/sys/amd64/amd64/trap.c:289 #8 0xffffffff807973de in calltrap () at /usr/home/sandbox/newusb/src/sys/amd64/amd64/exception.S:217 #9 0xffffffff807b2a46 in bcopy () at /usr/home/sandbox/newusb/src/sys/amd64/amd64/support.S:123 #10 0xffffffff80791ea0 in _bus_dmamap_sync (dmat=0xffffff0004028400, map=Variable "map" is not available. ) at /usr/home/sandbox/newusb/src/sys/amd64/amd64/busdma_machdep.c:922 #11 0xffffffff80426b42 in usb2_bdma_pre_sync (xfer=Variable "xfer" is not available. ) at /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_busdma.c:1360 #12 0xffffffff80426f01 in usb2_bdma_work_loop (pq=0xfffffffe40f84000) at /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_busdma.c:1297 #13 0xffffffff80439b26 in usb2_command_wrapper (pq=0xfffffffe40f84000, xfer=Variable "xfer" is not available. ) at /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_transfer.c:2515 #14 0xffffffff8043c3ed in usb2_callback_wrapper (pq=Variable "pq" is not available. ) at /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_transfer.c:1926 #15 0xffffffff80439b26 in usb2_command_wrapper (pq=0xfffffffe40f84028, xfer=Variable "xfer" is not available. ) at /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_transfer.c:2515 #16 0xffffffff80439c70 in usb2_callback_proc (_pm=Variable "_pm" is not available. ) at /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_transfer.c:1799 #17 0xffffffff804378b4 in usb2_process (arg=Variable "arg" is not available. ) at /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_process.c:139 #18 0xffffffff804d314a in fork_exit ( callout=0xffffffff804377f4 , arg=0xfffffffe40f840f0, frame=0xfffffffeb7267c90) at /usr/home/sandbox/newusb/src/sys/kern/kern_fork.c:810 #19 0xffffffff807977ee in fork_trampoline () at /usr/home/sandbox/newusb/src/sys/amd64/amd64/exception.S:521 #20 0x0000000000000000 in ?? () #21 0x0000000000000000 in ?? () #22 0x0000000000000001 in ?? () #23 0x0000000000000000 in ?? () #24 0x0000000000000000 in ?? () #25 0x0000000000000000 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000000 in ?? () #30 0x0000000000000000 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000000 in ?? () #33 0x0000000000000000 in ?? () #34 0x0000000000000000 in ?? () #35 0x0000000000000000 in ?? () #36 0x0000000000000000 in ?? () #37 0x0000000000000000 in ?? () #38 0x0000000000000000 in ?? () #39 0x0000000000000000 in ?? () #40 0x0000000000000000 in ?? () #41 0x0000000000000000 in ?? () #42 0x0000000000000000 in ?? () #43 0x0000000000000000 in ?? () #44 0x0000000001024000 in ?? () #45 0x0000000000000000 in ?? () #46 0xffffffff80b8dd70 in sleepq_chains () #47 0xffffffff80b756c0 in tdq_cpu () #48 0xffffff00024e96e0 in ?? () #49 0xfffffffeb7267ac0 in ?? () #50 0xfffffffeb7267a78 in ?? () #51 0xffffff0002ddd370 in ?? () #52 0xffffffff80511f90 in sched_switch (td=0xfffffffe40f840f0, newtd=0xffffffff804377f4, flags=Variable "flags" is not available. ) at /usr/home/sandbox/newusb/src/sys/kern/sched_ule.c:1844 Previous frame inner to this frame (corrupt stack?) (kgdb) ------------------------------------------------------------------------ ps -axl UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 0 0 0 -68 0 0 0 - DLs ?? 747427:30.00 [kernel] 0 1 0 0 44 0 2180 0 wait DLs ?? 5472248:30.00 [init] 0 2 0 0 -8 0 0 0 - DL ?? 1887795:30.00 [g_event] 0 3 0 0 -8 0 0 0 - DL ?? 159170669:00.00 [g_up] 0 4 0 0 -8 0 0 0 - DL ?? 80623968:30.00 [g_down] 0 5 0 0 -16 0 0 0 tq->tq DL ?? 0:00.00 [system_tas 0 6 0 0 -16 0 0 0 tq->tq DL ?? 0:00.00 [system_tas 0 7 0 0 -16 0 0 0 tq->tq DL ?? 0:00.00 [system_tas 0 8 0 0 -16 0 0 0 tq->tq DL ?? 0:00.00 [system_tas 0 9 0 0 -16 0 0 0 ccb_sc DL ?? 0:00.00 [xpt_thrd] 0 10 0 0 -16 0 0 0 audit_ DL ?? 5455:30.00 [audit] 0 11 0 0 171 0 0 0 - RL ?? 10883646524:50.00 [idle] 0 12 0 0 -48 0 0 0 - WL ?? 74210281:20.00 [intr] 0 13 0 0 44 0 0 0 - DL ?? 2767776:50.00 [yarrow] 0 14 0 0 -64 0 0 0 WMSG DL ?? 0:00.00 [USBPROC] 0 15 0 0 -64 0 0 0 WMSG DL ?? 17473:30.00 [USBPROC] 0 16 0 0 -16 0 0 0 - DL ?? 0:00.00 [fw0_probe] 0 17 0 0 -16 0 0 0 waitin DL ?? 1154:00.00 [sctp_itera 0 19 0 0 44 0 0 0 d DL ?? 1475436:10.00 [arc_reclai 0 21 0 0 -68 0 0 0 WMSG DL ?? 0:00.00 [USBPROC] 0 22 0 0 -68 0 0 0 WMSG DL ?? 0:00.00 [USBPROC] 0 23 0 0 -64 0 0 0 WMSG DL ?? 0:00.00 [USBPROC] 0 26 0 0 -68 0 0 0 WMSG DL ?? 28989:30.00 [USBPROC] 0 27 0 0 -68 0 0 0 WMSG DL ?? 0:00.00 [USBPROC] 0 28 0 0 -64 0 0 0 WMSG DL ?? 3466420:40.00 [USBPROC] 0 29 0 0 45 0 0 0 psleep DL ?? 13022:40.00 [pagedaemon 0 30 0 0 45 0 0 0 psleep DL ?? 581:40.00 [vmdaemon] 0 31 0 0 76 0 0 0 pgzero DL ?? 665:40.00 [pagezero] 0 32 0 0 45 0 0 0 psleep DL ?? 28784:30.00 [bufdaemon] 0 33 0 0 61 0 0 0 syncer DL ?? 134824082:40.00 [syncer] 0 34 0 0 45 0 0 0 vlruwt DL ?? 68163:10.00 [vnlru] 0 35 0 0 45 0 0 0 sdflus DL ?? 58308:10.00 [softdepflu 0 89 0 0 -68 0 0 0 WMSG DL ?? 10673:10.00 [USBPROC] 0 90 0 0 45 0 0 0 tq->tq DL ?? 226:50.00 [spa_zio_is 0 91 0 0 45 0 0 0 tq->tq DL ?? 206:10.00 [spa_zio_is 0 92 0 0 45 0 0 0 tq->tq DL ?? 408:20.00 [spa_zio_is 0 93 0 0 45 0 0 0 tq->tq DL ?? 346:50.00 [spa_zio_is 0 94 0 0 45 0 0 0 tq->tq DL ?? 271:10.00 [spa_zio_in 0 95 0 0 45 0 0 0 tq->tq DL ?? 310:00.00 [spa_zio_in 0 96 0 0 45 0 0 0 tq->tq DL ?? 191:00.00 [spa_zio_in 0 97 0 0 45 0 0 0 tq->tq DL ?? 342:10.00 [spa_zio_in 0 98 0 0 45 0 0 0 tq->tq DL ?? 692:10.00 [spa_zio_is 0 99 0 0 45 0 0 0 tq->tq DL ?? 561:50.00 [spa_zio_is 0 100 0 0 45 0 0 0 tq->tq DL ?? 407:00.00 [spa_zio_is 0 101 0 0 45 0 0 0 tq->tq DL ?? 384:40.00 [spa_zio_is 0 102 0 0 44 0 0 0 tq->tq DL ?? 3915100:00.00 [spa_zio_in 0 103 0 0 52 0 0 0 tq->tq DL ?? 679657:30.00 [spa_zio_in 0 104 0 0 52 0 0 0 tq->tq DL ?? 724595:40.00 [spa_zio_in 0 105 0 0 44 0 0 0 tq->tq DL ?? 3595602:50.00 [spa_zio_in 0 106 0 0 44 0 0 0 tq->tq DL ?? 161446:00.00 [spa_zio_is 0 107 0 0 44 0 0 0 tq->tq DL ?? 315903:50.00 [spa_zio_is 0 108 0 0 44 0 0 0 tq->tq DL ?? 438196:30.00 [spa_zio_is 0 109 0 0 47 0 0 0 tq->tq DL ?? 68604:10.00 [spa_zio_is 0 110 0 0 44 0 0 0 tq->tq DL ?? 192541000:20.00 [spa_zio_in 0 111 0 0 44 0 0 0 tq->tq DL ?? 183661574:50.00 [spa_zio_in 0 112 0 0 44 0 0 0 tq->tq DL ?? 180367061:20.00 [spa_zio_in 0 113 0 0 48 0 0 0 tq->tq DL ?? 202043190:20.00 [spa_zio_in 0 114 0 0 45 0 0 0 tq->tq DL ?? 683:50.00 [spa_zio_is 0 115 0 0 45 0 0 0 tq->tq DL ?? 595:40.00 [spa_zio_is 0 116 0 0 45 0 0 0 tq->tq DL ?? 486:10.00 [spa_zio_is 0 117 0 0 45 0 0 0 tq->tq DL ?? 226:50.00 [spa_zio_is 0 118 0 0 45 0 0 0 tq->tq DL ?? 386:30.00 [spa_zio_in 0 119 0 0 45 0 0 0 tq->tq DL ?? 790:20.00 [spa_zio_in 0 120 0 0 45 0 0 0 tq->tq DL ?? 419:40.00 [spa_zio_in 0 121 0 0 45 0 0 0 tq->tq DL ?? 173:20.00 [spa_zio_in 0 122 0 0 45 0 0 0 tq->tq DL ?? 771:10.00 [spa_zio_is 0 123 0 0 45 0 0 0 tq->tq DL ?? 746:30.00 [spa_zio_is 0 124 0 0 45 0 0 0 tq->tq DL ?? 525:40.00 [spa_zio_is 0 125 0 0 45 0 0 0 tq->tq DL ?? 736:40.00 [spa_zio_is 0 126 0 0 45 0 0 0 tq->tq DL ?? 528:40.00 [spa_zio_in 0 127 0 0 45 0 0 0 tq->tq DL ?? 309:40.00 [spa_zio_in 0 128 0 0 45 0 0 0 tq->tq DL ?? 246:40.00 [spa_zio_in 0 129 0 0 45 0 0 0 tq->tq DL ?? 531:10.00 [spa_zio_in 0 130 0 0 45 0 0 0 tq->tq DL ?? 3007:50.00 [spa_zio_is 0 131 0 0 45 0 0 0 tq->tq DL ?? 289:40.00 [spa_zio_is 0 132 0 0 45 0 0 0 tq->tq DL ?? 289:20.00 [spa_zio_is 0 133 0 0 45 0 0 0 tq->tq DL ?? 432:40.00 [spa_zio_is 0 134 0 0 45 0 0 0 tq->tq DL ?? 546:50.00 [spa_zio_in 0 135 0 0 45 0 0 0 tq->tq DL ?? 312:00.00 [spa_zio_in 0 136 0 0 45 0 0 0 tq->tq DL ?? 319:40.00 [spa_zio_in 0 137 0 0 45 0 0 0 tq->tq DL ?? 673:40.00 [spa_zio_in 0 138 0 0 44 0 0 0 ffffff000407c910 DL ?? 7618572:50.00 [vdev:worke 0 139 0 0 -68 0 0 0 - RL ?? 907164:40.00 [USBPROC] 0 140 0 0 44 0 0 0 2 DL ?? 7583535:20.00 [vdev:worke 0 141 0 0 44 0 0 0 2 DL ?? 7083820:40.00 [vdev:worke 0 142 0 0 45 0 0 0 tx->tx DL ?? 15303:20.00 [txg_thread 0 143 0 0 44 0 0 0 tx->tx DL ?? 164076779:50.00 [txg_thread 0 144 0 0 45 0 0 0 tx->tx DL ?? 9893:50.00 [txg_thread 0 145 0 0 45 0 0 0 tq->tq DL ?? 746:40.00 [zil_clean] 0 171 0 0 -68 0 0 0 WMSG DL ?? 17984:50.00 [USBPROC] 0 172 0 0 -68 0 0 0 WMSG DL ?? 2636:50.00 [USBPROC] 0 191 0 0 -68 0 0 0 WMSG DL ?? 6680:30.00 [USBPROC] 0 192 0 0 -68 0 0 0 WMSG DL ?? 1121246:10.00 [USBPROC] 0 193 0 0 -68 0 0 0 WMSG DL ?? 1451850:30.00 [USBPROC] 0 194 0 0 -64 0 0 0 WMSG DL ?? 777326:00.00 [USBPROC] 0 195 0 0 -68 0 0 0 WMSG DL ?? 8560:40.00 [USBPROC] 0 196 0 0 -68 0 0 0 WMSG DL ?? 108571:50.00 [USBPROC] 0 265 0 0 45 0 0 0 tq->tq DL ?? 913:20.00 [spa_zio_is 0 266 0 0 45 0 0 0 tq->tq DL ?? 556:20.00 [spa_zio_is 0 267 0 0 45 0 0 0 tq->tq DL ?? 264:20.00 [spa_zio_is 0 268 0 0 45 0 0 0 tq->tq DL ?? 738:20.00 [spa_zio_is 0 269 0 0 45 0 0 0 tq->tq DL ?? 568:00.00 [spa_zio_in 0 270 0 0 45 0 0 0 tq->tq DL ?? 599:30.00 [spa_zio_in 0 271 0 0 45 0 0 0 tq->tq DL ?? 841:00.00 [spa_zio_in 0 272 0 0 45 0 0 0 tq->tq DL ?? 522:30.00 [spa_zio_in 0 273 0 0 45 0 0 0 tq->tq DL ?? 730:00.00 [spa_zio_is 0 274 0 0 45 0 0 0 tq->tq DL ?? 495:10.00 [spa_zio_is 0 275 0 0 45 0 0 0 tq->tq DL ?? 188:10.00 [spa_zio_is 0 276 0 0 45 0 0 0 tq->tq DL ?? 311:00.00 [spa_zio_is 0 277 0 0 45 0 0 0 tq->tq DL ?? 99792:30.00 [spa_zio_in 0 278 0 0 45 0 0 0 tq->tq DL ?? 220438:10.00 [spa_zio_in 0 279 0 0 45 0 0 0 tq->tq DL ?? 99017:10.00 [spa_zio_in 0 280 0 0 45 0 0 0 tq->tq DL ?? 234007:10.00 [spa_zio_in 0 281 0 0 45 0 0 0 tq->tq DL ?? 13354:20.00 [spa_zio_is 0 282 0 0 45 0 0 0 tq->tq DL ?? 13582:50.00 [spa_zio_is 0 283 0 0 45 0 0 0 tq->tq DL ?? 26698:20.00 [spa_zio_is 0 284 0 0 45 0 0 0 tq->tq DL ?? 26920:10.00 [spa_zio_is 0 285 0 0 45 0 0 0 tq->tq DL ?? 168799:10.00 [spa_zio_in 0 286 0 0 45 0 0 0 tq->tq DL ?? 166680:30.00 [spa_zio_in 0 287 0 0 45 0 0 0 tq->tq DL ?? 159190:00.00 [spa_zio_in 0 288 0 0 45 0 0 0 tq->tq DL ?? 157914:20.00 [spa_zio_in 0 289 0 0 45 0 0 0 tq->tq DL ?? 687:20.00 [spa_zio_is 0 290 0 0 45 0 0 0 tq->tq DL ?? 890:00.00 [spa_zio_is 0 291 0 0 45 0 0 0 tq->tq DL ?? 506:30.00 [spa_zio_is 0 292 0 0 45 0 0 0 tq->tq DL ?? 143:20.00 [spa_zio_is 0 293 0 0 45 0 0 0 tq->tq DL ?? 766:30.00 [spa_zio_in 0 294 0 0 45 0 0 0 tq->tq DL ?? 753:10.00 [spa_zio_in 0 295 0 0 45 0 0 0 tq->tq DL ?? 531:00.00 [spa_zio_in 0 296 0 0 45 0 0 0 tq->tq DL ?? 424:20.00 [spa_zio_in 0 297 0 0 45 0 0 0 tq->tq DL ?? 902:40.00 [spa_zio_is 0 298 0 0 45 0 0 0 tq->tq DL ?? 717:30.00 [spa_zio_is 0 299 0 0 45 0 0 0 tq->tq DL ?? 538:30.00 [spa_zio_is 0 300 0 0 45 0 0 0 tq->tq DL ?? 770:40.00 [spa_zio_is 0 301 0 0 45 0 0 0 tq->tq DL ?? 831:10.00 [spa_zio_in 0 302 0 0 45 0 0 0 tq->tq DL ?? 876:00.00 [spa_zio_in 0 303 0 0 45 0 0 0 tq->tq DL ?? 1040:30.00 [spa_zio_in 0 304 0 0 45 0 0 0 tq->tq DL ?? 966:00.00 [spa_zio_in 0 305 0 0 45 0 0 0 tq->tq DL ?? 882:00.00 [spa_zio_is 0 306 0 0 45 0 0 0 tq->tq DL ?? 714:30.00 [spa_zio_is 0 307 0 0 45 0 0 0 tq->tq DL ?? 905:20.00 [spa_zio_is 0 308 0 0 45 0 0 0 tq->tq DL ?? 774:30.00 [spa_zio_is 0 309 0 0 45 0 0 0 tq->tq DL ?? 1262:40.00 [spa_zio_in 0 310 0 0 45 0 0 0 tq->tq DL ?? 732:50.00 [spa_zio_in 0 311 0 0 45 0 0 0 tq->tq DL ?? 624:10.00 [spa_zio_in 0 312 0 0 45 0 0 0 tq->tq DL ?? 769:00.00 [spa_zio_in 0 313 0 0 45 0 0 0 a DL ?? 138498:00.00 [vdev:worke 0 314 0 0 45 0 0 0 tx->tx DL ?? 13274:30.00 [txg_thread 0 315 0 0 45 0 0 0 zio->i DL ?? 592414:00.00 [txg_thread 0 316 0 0 45 0 0 0 tx->tx DL ?? 14080:20.00 [txg_thread 0 369 0 0 45 0 0 0 tq->tq DL ?? 406:20.00 [spa_zio_is 0 370 0 0 45 0 0 0 tq->tq DL ?? 291:50.00 [spa_zio_is 0 371 0 0 45 0 0 0 tq->tq DL ?? 654:30.00 [spa_zio_is 0 372 0 0 45 0 0 0 tq->tq DL ?? 515:10.00 [spa_zio_is 0 373 0 0 45 0 0 0 tq->tq DL ?? 289:50.00 [spa_zio_in 0 374 0 0 45 0 0 0 tq->tq DL ?? 781:10.00 [spa_zio_in 0 375 0 0 45 0 0 0 tq->tq DL ?? 689:40.00 [spa_zio_in 0 376 0 0 45 0 0 0 tq->tq DL ?? 363:40.00 [spa_zio_in 0 377 0 0 45 0 0 0 tq->tq DL ?? 388:50.00 [spa_zio_is 0 378 0 0 45 0 0 0 tq->tq DL ?? 577:50.00 [spa_zio_is 0 379 0 0 45 0 0 0 tq->tq DL ?? 386:20.00 [spa_zio_is 0 380 0 0 45 0 0 0 tq->tq DL ?? 633:00.00 [spa_zio_is 0 381 0 0 45 0 0 0 tq->tq DL ?? 461038:00.00 [spa_zio_in 0 382 0 0 45 0 0 0 tq->tq DL ?? 469792:50.00 [spa_zio_in 0 383 0 0 45 0 0 0 tq->tq DL ?? 452893:40.00 [spa_zio_in 0 384 0 0 76 0 0 0 tq->tq DL ?? 260950:00.00 [spa_zio_in 0 385 0 0 45 0 0 0 tq->tq DL ?? 838:10.00 [spa_zio_is 0 386 0 0 45 0 0 0 tq->tq DL ?? 359:50.00 [spa_zio_is 0 387 0 0 44 0 0 0 tq->tq DL ?? 648:20.00 [spa_zio_is 0 388 0 0 44 0 0 0 tq->tq DL ?? 507:00.00 [spa_zio_is 0 389 0 0 44 0 0 0 tq->tq DL ?? 717:00.00 [spa_zio_in 0 390 0 0 45 0 0 0 tq->tq DL ?? 449:30.00 [spa_zio_in 0 391 0 0 44 0 0 0 tq->tq DL ?? 500:20.00 [spa_zio_in 0 392 0 0 44 0 0 0 tq->tq DL ?? 351:20.00 [spa_zio_in 0 393 0 0 45 0 0 0 tq->tq DL ?? 779:40.00 [spa_zio_is 0 394 0 0 45 0 0 0 tq->tq DL ?? 856:30.00 [spa_zio_is 0 395 0 0 45 0 0 0 tq->tq DL ?? 602:10.00 [spa_zio_is 0 396 0 0 45 0 0 0 tq->tq DL ?? 525:00.00 [spa_zio_is 0 397 0 0 45 0 0 0 tq->tq DL ?? 979:00.00 [spa_zio_in 0 398 0 0 45 0 0 0 tq->tq DL ?? 821:20.00 [spa_zio_in 0 399 0 0 45 0 0 0 tq->tq DL ?? 671:00.00 [spa_zio_in 0 400 0 0 45 0 0 0 tq->tq DL ?? 1013:40.00 [spa_zio_in 0 401 0 0 45 0 0 0 tq->tq DL ?? 595:30.00 [spa_zio_is 0 402 0 0 45 0 0 0 tq->tq DL ?? 363:30.00 [spa_zio_is 0 403 0 0 45 0 0 0 tq->tq DL ?? 444:50.00 [spa_zio_is 0 404 0 0 45 0 0 0 tq->tq DL ?? 749:20.00 [spa_zio_is 0 405 0 0 45 0 0 0 tq->tq DL ?? 942:00.00 [spa_zio_in 0 406 0 0 45 0 0 0 tq->tq DL ?? 379:30.00 [spa_zio_in 0 407 0 0 45 0 0 0 tq->tq DL ?? 583:00.00 [spa_zio_in 0 408 0 0 45 0 0 0 tq->tq DL ?? 553:00.00 [spa_zio_in 0 409 0 0 45 0 0 0 tq->tq DL ?? 570:30.00 [spa_zio_is 0 410 0 0 45 0 0 0 tq->tq DL ?? 344:10.00 [spa_zio_is 0 411 0 0 45 0 0 0 tq->tq DL ?? 527:30.00 [spa_zio_is 0 412 0 0 45 0 0 0 tq->tq DL ?? 449:20.00 [spa_zio_is 0 413 0 0 45 0 0 0 tq->tq DL ?? 505:00.00 [spa_zio_in 0 414 0 0 45 0 0 0 tq->tq DL ?? 685:40.00 [spa_zio_in 0 415 0 0 45 0 0 0 tq->tq DL ?? 467:50.00 [spa_zio_in 0 416 0 0 45 0 0 0 tq->tq DL ?? 535:00.00 [spa_zio_in 0 417 0 0 44 0 0 0 d DL ?? 3205:20.00 [vdev:worke 0 418 0 0 44 0 0 0 d DL ?? 3536:10.00 [vdev:worke 0 419 0 0 44 0 0 0 1 DL ?? 3537:00.00 [vdev:worke 0 420 0 0 44 0 0 0 1 DL ?? 3025:10.00 [vdev:worke 0 421 0 0 45 0 0 0 tx->tx DL ?? 13045:50.00 [txg_thread 0 422 0 0 45 0 0 0 tx->tx DL ?? 24917:00.00 [txg_thread 0 423 0 0 45 0 0 0 tx->tx DL ?? 10366:50.00 [txg_thread 0 433 0 0 45 0 0 0 tq->tq DL ?? 622:20.00 [zil_clean] 0 434 0 0 45 0 0 0 tq->tq DL ?? 4334:00.00 [zil_clean] 0 435 0 0 45 0 0 0 tq->tq DL ?? 214:20.00 [zil_clean] 0 448 0 0 45 0 0 0 tq->tq DL ?? 218:20.00 [zil_clean] 0 455 0 0 45 0 0 0 tq->tq DL ?? 10766862:50.00 [zil_clean] 0 545 1 0 76 0 2600 0 pause Ds ?? 20311:10.00 [adjkerntz] 0 1072 1 0 76 0 2176 0 select Ds ?? 26750:00.00 [devd] 0 1315 1 0 44 0 5724 0 select Ds ?? 2184241:50.00 [syslogd] 0 1370 1 0 76 0 5744 0 auditd Ds ?? 425594:30.00 [auditd] 0 1503 1 0 44 0 5724 0 select Ds ?? 345377:40.00 [powerd] 65534 1558 1 0 44 0 4640 0 select Ds ?? 329227:40.00 [mdnsd] 0 1571 1 0 61 0 21812 0 kqread Ds ?? 1627382:50.00 [cupsd] 1 1580 1 0 44 0 7236 0 select Ds ?? 73565:50.00 [slpd] 0 1612 1 0 76 0 24684 0 select Ds ?? 165899:50.00 [sshd] 0 1617 1 0 44 0 10692 0 select Ds ?? 390314:20.00 [sendmail] 25 1623 1 0 76 0 10692 0 pause Ds ?? 444533:40.00 [sendmail] 0 1629 1 0 44 0 6780 0 nanslp Ds ?? 308518:30.00 [cron] 0 1638 1 0 44 0 5672 0 nanslp Ds ?? 45776:40.00 [uptimed] 0 1650 1 0 76 0 6872 0 select Ds ?? 127881:40.00 [moused] 0 1674 1 0 76 0 7832 0 select Ds ?? 207752:10.00 [inetd] 0 1700 1 0 44 0 20476 0 wait Ds ?? 457620:30.00 [login] 0 1701 1 0 44 0 20476 0 wait Ds ?? 232783:10.00 [login] 0 1702 1 0 76 0 5720 0 tty in Ds+ ?? 195147:40.00 [getty] 0 1703 1 0 76 0 5720 0 tty in Ds+ ?? 190936:00.00 [getty] 0 1704 1 0 76 0 5720 0 tty in Ds+ ?? 374987:20.00 [getty] 0 1705 1 0 76 0 5720 0 tty in Ds+ ?? 611203:40.00 [getty] 0 1706 1 0 76 0 5720 0 tty in Ds+ ?? 224722:50.00 [getty] 0 1707 1 0 76 0 5720 0 tty in Ds+ ?? 203391:00.00 [getty] 0 1708 1 0 76 0 5720 0 tty in Ds+ ?? 313967:20.00 [getty] 0 1709 1 0 76 0 5720 0 tty in Ds+ ?? 205962:50.00 [getty] 0 1710 1 0 76 0 5720 0 tty in Ds+ ?? 244910:10.00 [getty] 0 1714 1700 0 44 0 10132 0 tty in D+ ?? 1077786:20.00 [tcsh] 0 1775 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1777 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1778 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1939 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1940 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1941 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1942 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1943 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1944 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1945 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1946 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1947 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1948 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1949 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1950 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1951 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1952 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1953 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1954 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1955 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1956 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1957 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1958 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1960 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1962 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1964 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1966 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1967 0 0 45 0 0 0 tq->tq DL ?? 0:00.00 [zil_clean] 0 1997 1701 0 44 0 10132 0 pause D ?? 184970:50.00 [tcsh] 0 2001 1997 0 45 0 14452 0 tx->tx D+ ?? 0:00.00 [zpool] ------------------------------------------------------------------------ vmstat -s 0 cpu context switches 0 device interrupts 0 software interrupts 0 traps 0 system calls 0 kernel threads created 0 fork() calls 0 vfork() calls 0 rfork() calls 0 swap pager pageins 0 swap pager pages paged in 0 swap pager pageouts 0 swap pager pages paged out 0 vnode pager pageins 0 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 0 page daemon wakeups 0 pages examined by the page daemon 2934 pages reactivated 0 copy-on-write faults 0 copy-on-write optimized faults 0 zero fill pages zeroed 0 zero fill pages prezeroed 0 intransit blocking page faults 0 total VM faults taken 0 pages affected by kernel thread creation 0 pages affected by fork() 0 pages affected by vfork() 0 pages affected by rfork() 3251 pages cached 0 pages freed 0 pages freed by daemon 83854 pages freed by exiting processes 5662 pages active 2107 pages inactive 109 pages in VM cache 250660 pages wired down 745813 pages free 4096 bytes per page 78523 total name lookups cache hits (86% pos + 3% neg) system 0% per-directory deletions 0%, falsehits 0%, toolong 0% ------------------------------------------------------------------------ vmstat -m Type InUse MemUse HighUse Requests Size(s) ntfs_nthash -1 -511K - 0 pfs_nodes -20 -4K - 0 pfs_vncache -1 0K - 0 fw_xfer 255 0K - 256 16 firewire 4082 -37K - 4096 16,32 GEOM 2301117 -2321K - 2303408 16,32,64,128,256,512,1024,2048,4096,8192 isadev -8 0K - 0 CAM XPT 40167 -58K - 40320 32,64,128,256,512 pci_link -68 -4K - 0 cdev -12 -2K - 0 sbp -96 -12K - 0 ddb_capture -1 -47K - 0 sigio -1 0K - 0 filedesc 890917 -1005K - 892928 16,32,64,128,256,512,1024,2048,4096,8192 kenv -25 -9K - 48 32 kqueue 32226 -32K - 32256 64,128,256 proc-args 42410 -42K - 43168 16,32,64,128,256,512,1024,2048,4096 ithread -77 -11K - 0 prison -1 0K - 0 KTRACE -100 -11K - 0 linker 1355 -160K - 1568 16,32,64,128,512 lockf 418 -2K - 448 64 ip6ndp -6 0K - 0 temp 125335915 -122423K - 125343008 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768 devbuf 361425 -13088K - 367648 16,32,128,256,512,1024,4096 module -431 -52K - 0 mtx_pool -1 -7K - 0 subproc 7141528 -8238K - 7143936 16,32,64,128,256,512,1024,2048,4096,8192 proc -2 -15K - 0 session 608 -3K - 640 16,32 pgrp 5558 -8K - 5632 16,32,128,256 cred 1585026 -1566K - 1591296 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768 uidinfo 184 -1K - 192 16,32 plimit 60926 -63K - 61184 16,32,64,128,256,512,1024 sysctltmp 14679 -13K - 15024 16,32,64,128,512,2048 sysctloid 2500 -217K - 7056 16,32,64,128,256,1024,2048 sysctl 15292 -14K - 15920 32,64,128,256,1024,4096 callout -3 -1535K - 0 umtx -452 -55K - 0 p1003.1b -1 0K - 0 SWAP -8 -8751K - 0 bus-sc 25513187 -25071K - 25516768 16,32,128,256,512,1024,2048,16384,32768 bus 1324171 -1395K - 1330928 16,32,64,128,256,512,1024,2048,4096,8192,65536 clist -54 -5K - 0 devstat -26 -51K - 0 eventhandler -66 -4K - 0 kbdmux -6 -7K - 0 kobj 454261 -1579K - 454656 16,32,64,128,256,1024 rman 54940 -74K - 55552 32,256,512,2048,4096 sbuf 1113064 -1086K - 1113920 16,32,64,128,256,512,1024,2048,4096 stack 510 0K - 512 32 taskqueue -13 0K - 0 Unitno 301 0K - 320 32,64 acpica 3955121 -4083K - 3991088 16,64,256,512,1024,16384,32768,65536,131072,262144 acpitask 63 0K - 64 16 CAM dev queue -4 0K - 0 Witness -1 -127K - 0 iov 217186 -211K - 218080 32,64,128,256,1024,2048,8192 select -20 -1K - 0 ioctlops 6375330 -6235K - 6382160 16,64,128,256,512,1024,2048,32768,65536 msg -4 -29K - 0 sem -4 -6K - 0 shm -1 -15K - 0 tty -21 -20K - 0 mbuf_tag 529 0K - 544 16,32,128 shmfd -1 -7K - 0 CAM queue 2445 -1K - 2560 16,32,64,256,512 pcb 1743 -157K - 1824 16,32,64,128,512 soname 10028 -9K - 10384 16,32,64,128,256,512,1024,2048 vfscache -1 -1023K - 0 vfs_hash -1 -511K - 0 vnodes -2 0K - 0 acpisem -15 0K - 0 vnodemarker 1129310 -1104K - 1131520 32,64,128,256,512,1024,2048,4096,8192,16384 mount 54510 -71K - 56576 32,64,128,512,1024,2048,4096,16384 BPF -6 0K - 0 ether_multi 764 -1K - 816 16,32,64,128 ifaddr 3654 -21K - 3968 64,128,256,512,1024 ifnet -6 -9K - 0 clone -5 -19K - 0 arpcom -2 0K - 0 fw_com -1 0K - 0 ata_generic -6 -5K - 0 ad_driver -4 0K - 0 routetbl 13587 -15K - 13664 16,32,64,256,512 80211vap -1 -3K - 0 80211crypto -4 0K - 0 80211com -1 -7K - 0 80211nodeie 1275 -1K - 1280 16,32 80211node 12286 -23K - 12288 16 80211scan -3 -5K - 0 igmp -1 0K - 0 in_msource 4089 -6K - 4096 64 ip_moptions 1266 -1K - 1280 128 in_multi -4 0K - 0 sctp_iter 510 0K - 512 32 sctp_ifn -2 0K - 0 sctp_ifa -3 0K - 0 sctp_vrf -1 0K - 0 sctp_a_it 30 0K - 32 32 hostcache -1 -27K - 0 ar_driver 69612 -67K - 69632 64,256 syncache -1 -91K - 0 in6_multi -16 0K - 0 acd_driver -2 -3K - 0 nfss_daemon -1 -15K - 0 audit_data 508 0K - 512 16,32 audit_evclass 5750 -21K - 6464 32,128,1024,2048 newblk -1 0K - 0 inodedep -1 -511K - 0 pagedep -1 -127K - 0 ufs_dirhash -3 0K - 0 ufs_mount -3 -5K - 0 UMAHash 19446 -38K - 19456 32,64 vm_pgdata -5 -127K - 0 scsi_da 705 0K - 752 16,32,64,128,256 CAM SIM -4 0K - 0 entropy -1024 -63K - 0 io_apic -1 -1K - 0 CAM periph 3377 -5K - 3408 16,32,64,128 memdesc -1 -3K - 0 acpidev -69 -3K - 0 nexusdev -3 0K - 0 UART -3 0K - 0 atkbddev -2 0K - 0 USBdev 2033 -13K - 2048 32 USB 98263 -251K - 98304 32,64,128 DEVFS1 894 -64K - 1024 32 DEVFS3 623 -35K - 768 16,32 DEVFS -2 0K - 16 16 solaris 9120189812 -9801837K - 9128038272 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536,131072,262144,524288,1048576,2097152,4194304,8388608,16777216,33554432 kstat_data -1 0K - 0 linux -12 0K - 0 ------------------------------------------------------------------------ vmstat -z ITEM SIZE LIMIT USED FREE REQUESTS FAILURES UMA Kegs: 200, 0, 93, 9, 93, 0 UMA Zones: 280, 0, 93, 11, 93, 0 UMA Slabs: 128, 0, 12645, 57, 99014, 0 UMA RCntSlabs: 128, 0, 279, 11, 279, 0 UMA Hash: 256, 0, 6, 9, 8, 0 16 Bucket: 152, 0, 125, 0, 125, 0 32 Bucket: 280, 0, 117, 9, 117, 0 64 Bucket: 536, 0, 147, 0, 147, 658 128 Bucket: 1048, 0, 1126, 2, 1126, 1817 VM OBJECT: 200, 0, 1347, 325, 25494, 0 MAP: 216, 0, 7, 29, 7, 0 KMAP ENTRY: 112, 150216, 528, 462, 240659, 0 MAP ENTRY: 112, 0, 841, 446, 57149, 0 DP fakepg: 112, 0, 0, 0, 0, 0 mt_zone: 2056, 0, 262, 1, 262, 0 16: 16, 0, 3340, 524, 734431, 0 32: 32, 0, 3692, 12266, 3883221, 0 64: 64, 0, 10658, 4798, 1238880, 0 128: 128, 0, 17006, 481, 1301704, 0 256: 256, 0, 930, 90600, 626721, 0 512: 512, 0, 2572, 228, 24619, 0 1024: 1024, 0, 203, 1561, 19987, 0 2048: 2048, 0, 598, 196, 5822, 0 4096: 4096, 0, 756, 395, 13709, 0 Files: 80, 0, 100, 260, 8865, 0 TURNSTILE: 136, 0, 453, 67, 453, 0 umtx pi: 96, 0, 0, 0, 0, 0 PROC: 1072, 0, 265, 131, 2009, 0 THREAD: 872, 0, 421, 31, 421, 0 SLEEPQUEUE: 80, 0, 453, 132, 453, 0 VMSPACE: 376, 0, 30, 90, 1555, 0 cpuset: 72, 0, 2, 98, 2, 0 audit_record: 984, 0, 0, 28, 4, 0 mbuf_packet: 256, 0, 0, 512, 9789, 0 mbuf: 256, 0, 1, 522, 870, 0 mbuf_cluster: 2048, 25600, 512, 46, 512, 0 mbuf_jumbo_page: 4096, 12800, 0, 0, 0, 0 mbuf_jumbo_9k: 9216, 19200, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 12800, 0, 0, 0, 0 mbuf_ext_refcnt: 4, 0, 0, 0, 0, 0 ACL UMA zone: 388, 0, 0, 30, 124, 0 g_bio: 216, 0, 16, 704, 367222, 0 ttyinq: 160, 0, 720, 216, 2520, 0 ttyoutq: 256, 0, 372, 138, 1302, 0 ata_request: 312, 0, 1, 380, 155536, 0 ata_composite: 336, 0, 0, 0, 0, 0 taskq_ent_cache: 64, 0, 1872, 368, 3772, 0 taskq_cache: 288, 0, 71, 46, 157, 0 VNODE: 472, 0, 850, 126, 1512, 0 VNODEPOLL: 104, 0, 0, 0, 0, 0 NAMEI: 1024, 0, 0, 48, 23670, 0 S VFS Cache: 104, 0, 581, 355, 7279, 0 L VFS Cache: 327, 0, 0, 24, 1, 0 DIRHASH: 1024, 0, 13, 7, 13, 0 NFSMOUNT: 640, 0, 0, 0, 0, 0 NFSNODE: 640, 0, 0, 0, 0, 0 pipe: 712, 0, 2, 63, 880, 0 ksiginfo: 112, 0, 376, 680, 376, 0 itimer: 344, 0, 0, 22, 1, 0 KNOTE: 120, 0, 6, 118, 35, 0 socket: 640, 12330, 27, 45, 286, 0 unpcb: 240, 12336, 10, 70, 20, 0 ipq: 56, 819, 0, 0, 0, 0 udpcb: 280, 12334, 7, 63, 251, 0 inpcb: 280, 12334, 9, 33, 13, 0 tcpcb: 728, 12330, 9, 16, 13, 0 tcptw: 88, 2478, 0, 0, 0, 0 syncache: 136, 15372, 0, 0, 0, 0 hostcache: 136, 15372, 0, 0, 0, 0 tcpreass: 40, 1680, 0, 0, 0, 0 sackhole: 32, 0, 0, 0, 0, 0 sctp_ep: 1160, 12330, 0, 0, 0, 0 sctp_asoc: 2152, 40000, 0, 0, 0, 0 sctp_laddr: 48, 80064, 0, 144, 2, 0 sctp_raddr: 584, 80003, 0, 0, 0, 0 sctp_chunk: 136, 400008, 0, 0, 0, 0 sctp_readq: 104, 400032, 0, 0, 0, 0 sctp_stream_msg_out: 88, 400008, 0, 0, 0, 0 sctp_asconf: 40, 400008, 0, 0, 0, 0 sctp_asconf_ack: 48, 400032, 0, 0, 0, 0 ripcb: 280, 12334, 0, 0, 0, 0 rtentry: 232, 0, 9, 39, 9, 0 zio_cache: 672, 0, 5, 10585, 1515161, 0 dmu_buf_impl_t: 224, 0, 8767, 260, 40691, 0 dnode_t: 760, 0, 1578, 97, 2839, 0 arc_buf_hdr_t: 184, 0, 13995, 453, 40842, 0 arc_buf_t: 40, 0, 8746, 494, 41434, 0 zil_lwb_cache: 200, 0, 2, 2164, 3926, 0 zfs_znode_cache: 336, 0, 673, 218, 1276, 0 selfd: 56, 0, 44, 271, 3245, 0 SWAPMETA: 288, 116519, 0, 0, 0, 0 Mountpoints: 800, 0, 37, 43, 88, 0 FFS inode: 176, 0, 7, 56, 7, 0 FFS1 dinode: 128, 0, 0, 0, 0, 0 FFS2 dinode: 256, 0, 7, 38, 7, 0 ------------------------------------------------------------------------ vmstat -i interrupt total rate irq1: atkbd0 3006 4 irq12: psm0 9 0 irq18: fwohci0 3 0 irq20: atapci2 117 0 irq21: ohci0+ 58425 89 irq22: ehci0 19116 29 irq23: atapci1 72123 109 cpu0: timer 1695176 2584 cpu1: timer 1685074 2568 cpu2: timer 1672747 2549 cpu3: timer 1672756 2549 Total 6878552 10485 ------------------------------------------------------------------------ pstat -T 100/12328 files 0M/65535M swap space ------------------------------------------------------------------------ pstat -s Device 1K-blocks Used Avail Capacity /dev/ad4s1b 16777088 0 16777088 0% /dev/ad6s1d 16777088 0 16777088 0% /dev/ad12s1d 16777088 0 16777088 0% /dev/ad14s1b 16777088 0 16777088 0% Total 67108352 0 67108352 0% ------------------------------------------------------------------------ iostat iostat: kvm_read(_tk_nin): invalid address (0x0) iostat: disabling TTY statistics iostat: kvm_getcptime: invalid address (0x0) iostat: disabling CPU time statistics ad4 ad6 ad12 KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s 56.47 62 3.44 46.83 48 2.18 47.01 48 2.18 ------------------------------------------------------------------------ ipcs -a Message Queues: T ID KEY MODE OWNER GROUP CREATOR CGROUP CBYTES QNUM QBYTES LSPID LRPID STIME RTIME CTIME Shared Memory: T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME Semaphores: T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME ------------------------------------------------------------------------ ipcs -T msginfo: msgmax: 16384 (max characters in a message) msgmni: 40 (# of message queues) msgmnb: 2048 (max characters in a message queue) msgtql: 40 (max # of messages in system) msgssz: 8 (size of a message segment) msgseg: 2048 (# of message segments in system) shminfo: shmmax: 33554432 (max shared memory segment size) shmmin: 1 (min shared memory segment size) shmmni: 192 (max number of shared memory identifiers) shmseg: 128 (max shared memory segments per process) shmall: 8192 (max amount of shared memory in pages) seminfo: semmap: 30 (# of entries in semaphore map) semmni: 10 (# of semaphore identifiers) semmns: 60 (# of semaphores in system) semmnu: 30 (# of undo structures in system) semmsl: 60 (max # of semaphores per id) semopm: 100 (max # of operations per semop call) semume: 10 (max # of undo entries per process) semusz: 104 (size in bytes of undo structure) semvmx: 32767 (semaphore maximum value) semaem: 16384 (adjust on exit max value) ------------------------------------------------------------------------ nfsstat Client Info: Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 0 0 0 0 0 0 0 0 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 0 0 0 0 0 0 0 0 Mknod Fsstat Fsinfo PathConf Commit 0 0 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 0 0 0 Cache Info: Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 0 0 0 0 0 0 0 0 BioRLHits Misses BioD Hits Misses DirE Hits Misses 0 0 0 0 0 0 Server Info: Getattr Setattr Lookup Readlink Read Write Create Remove 0 0 0 0 0 0 0 0 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 0 0 0 0 0 0 0 0 Mknod Fsstat Fsinfo PathConf Commit 0 0 0 0 0 Server Ret-Failed 0 Server Faults 0 Server Cache Stats: Inprog Idem Non-idem Misses 0 0 0 0 Server Write Gathering: WriteOps WriteRPC Opsaved 0 0 0 ------------------------------------------------------------------------ netstat -s tcp: 0 packets sent 0 data packets (0 bytes) 0 data packets (0 bytes) retransmitted 0 data packets unnecessarily retransmitted 0 resends initiated by MTU discovery 0 ack-only packets (0 delayed) 0 URG only packets 0 window probe packets 0 window update packets 0 control packets 0 packets received 0 acks (for 0 bytes) 0 duplicate acks 0 acks for unsent data 0 packets (0 bytes) received in-sequence 0 completely duplicate packets (0 bytes) 0 old duplicate packets 0 packets with some dup. data (0 bytes duped) 0 out-of-order packets (0 bytes) 0 packets (0 bytes) of data after window 0 window probes 0 window update packets 0 packets received after close 0 discarded for bad checksums 0 discarded for bad header offset fields 0 discarded because packet too short 0 discarded due to memory problems 0 connection requests 0 connection accepts 0 bad connection attempts 0 listen queue overflows 0 ignored RSTs in the windows 0 connections established (including accepts) 4 connections closed (including 0 drops) 0 connections updated cached RTT on close 0 connections updated cached RTT variance on close 0 connections updated cached ssthresh on close 0 embryonic connections dropped 0 segments updated rtt (of 0 attempts) 0 retransmit timeouts 0 connections dropped by rexmit timeout 0 persist timeouts 0 connections dropped by persist timeout 0 Connections (fin_wait_2) dropped because of timeout 0 keepalive timeouts 0 keepalive probes sent 0 connections dropped by keepalive 0 correct ACK header predictions 0 correct data packet header predictions 0 syncache entries added 0 retransmitted 0 dupsyn 0 dropped 0 completed 0 bucket overflow 0 cache overflow 0 reset 0 stale 0 aborted 0 badack 0 unreach 0 zone failures 0 cookies sent 0 cookies received 0 SACK recovery episodes 0 segment rexmits in SACK recovery episodes 0 byte rexmits in SACK recovery episodes 0 SACK options (SACK blocks) received 0 SACK options (SACK blocks) sent 0 SACK scoreboard overflow 0 packets with ECN CE bit set 0 packets with ECN ECT(0) bit set 0 packets with ECN ECT(1) bit set 0 successful ECN handshakes 0 times ECN reduced the congestion window udp: 132 datagrams received 0 with incomplete header 0 with bad data length field 0 with bad checksum 0 with no checksum 0 dropped due to no socket 24 broadcast/multicast datagrams undelivered 0 dropped due to full socket buffers 0 not for hashed pcb 108 delivered 100 datagrams output 0 times multicast source filter matched ip: 1419 total packets received 0 bad header checksums 0 with size smaller than minimum 0 with data size < data length 0 with ip length > max ip packet size 0 with header length < data size 0 with data length < header length 0 with bad options 0 with incorrect version number 0 fragments received 0 fragments dropped (dup or out of space) 0 fragments dropped after timeout 0 packets reassembled ok 132 packets for this host 30 packets for unknown/unsupported protocol 0 packets forwarded (0 packets fast forwarded) 0 packets not forwardable 1257 packets received for unknown multicast group 0 redirects sent 121 packets sent from this host 0 packets sent with fabricated ip header 0 output packets dropped due to no bufs, etc. 0 output packets discarded due to no route 0 output datagrams fragmented 0 fragments created 0 datagrams that can't be fragmented 0 tunneling packets that can't find gif 0 datagrams with bad address in header icmp: 0 calls to icmp_error 0 errors not generated in response to an icmp message 0 messages with bad code fields 0 messages less than the minimum length 0 messages with bad checksum 0 messages with bad length 0 multicast echo requests ignored 0 multicast timestamp requests ignored 0 message responses generated 0 invalid return addresses 0 no return routes igmp: 30 messages received 0 messages received with too few bytes 0 messages received with bad checksum 14 membership queries received 0 membership queries received with invalid field(s) 16 membership reports received 0 membership reports received with invalid field(s) 16 membership reports received for groups to which we belong 21 membership reports sent ip6: 10 total packets received 0 with size smaller than minimum 0 with data size < data length 0 with bad options 0 with incorrect version number 0 fragments received 0 fragments dropped (dup or out of space) 0 fragments dropped after timeout 0 fragments that exceeded limit 0 packets reassembled ok 0 packets for this host 0 packets forwarded 10 packets not forwardable 0 redirects sent 4 packets sent from this host 0 packets sent with fabricated ip header 0 output packets dropped due to no bufs, etc. 0 output packets discarded due to no route 0 output datagrams fragmented 0 fragments created 0 datagrams that can't be fragmented 0 packets that violated scope rules 10 multicast packets which we don't join Input histogram: UDP: 10 Mbuf statistics: 0 one mbuf 10 one ext mbuf 0 two or more ext mbuf 0 packets whose headers are not continuous 0 tunneling packets that can't find gif 0 packets discarded because of too many headers 0 failures of source address selection 0 forward cache hit 0 forward cache miss Source addresses selection rule applied: 1 first candidate 1 same address icmp6: 0 calls to icmp6_error 0 errors not generated in response to an icmp6 message 0 errors not generated because of rate limitation Output histogram: multicast listener report: 4 0 messages with bad code fields 0 messages < minimum length 0 bad checksums 0 messages with bad length Histogram of error messages to be generated: 0 no route 0 administratively prohibited 0 beyond scope 0 address unreachable 0 port unreachable 0 packet too big 0 time exceed transit 0 time exceed reassembly 0 erroneous header field 0 unrecognized next header 0 unrecognized option 0 redirect 0 unknown 0 message responses generated 0 messages with too many ND options 0 messages with bad ND options 0 bad neighbor solicitation messages 0 bad neighbor advertisement messages 0 bad router solicitation messages 0 bad router advertisement messages 0 bad redirect messages 0 path MTU changes rip6: 0 messages received 0 checksum calcurations on inbound 0 messages with bad checksum 0 messages dropped due to no socket 0 multicast messages dropped due to no socket 0 messages dropped due to full socket buffers 0 delivered 0 datagrams output ------------------------------------------------------------------------ netstat -m 1/1034/1035 mbufs in use (current/cache/total) 0/558/558/25600 mbuf clusters in use (current/cache/total/max) 0/512 mbuf+clusters out of packet secondary zone in use (current/cache) 0/0/0/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/19200 9k jumbo clusters in use (current/cache/total/max) 0/0/0/12800 16k jumbo clusters in use (current/cache/total/max) 18014398509481983K/1374K/1374K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines ------------------------------------------------------------------------ netstat -id Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll Drop fwe0* 1500 82:00:00:00:00:00 0 0 0 0 0 0 fwip0 1500 80:00:00:00:00:00:00:00:0a:02:ff:fe:00:00:00:00 0 0 0 0 0 0 lo0 16384 0 0 0 0 0 0 lo0 16384 fe80:3::1 fe80:3::1 0 - 0 - - - lo0 16384 localhost ::1 0 - 0 - - - lo0 16384 your-net localhost 0 - 0 - - - rum0 2290 00:17:3f:72:40:90 0 0 316 2 0 0 wlan0 1500 00:17:3f:72:40:90 1435 0 122 0 0 0 wlan0 1500 192.168.0.0 w2fzz0vc03 162 - 121 - - - ------------------------------------------------------------------------ netstat -anr Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.0.1 UGS 0 76 wlan0 127.0.0.1 127.0.0.1 UH 0 0 lo0 192.168.0.0/24 link#5 UC 0 0 wlan0 192.168.0.1 00:1c:df:77:6c:f5 UHLW 2 14 wlan0 1251 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#3 UHL lo0 ff01:3::/32 fe80::1%lo0 UC lo0 ff02::%lo0/32 fe80::1%lo0 UC lo0 ------------------------------------------------------------------------ netstat -anA Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr ffffff0004decd20 stream 0 0 ffffff00856fb938 0 0 0 /var/run/cups.sock ffffff0004dedb40 stream 0 0 ffffff0004fa0000 0 0 0 /var/run/mdnsd ffffff0004ded000 stream 0 0 ffffff0004d123b0 0 0 0 /var/run/devd.pipe ffffff00857fa870 dgram 0 0 0 ffffff0004dede10 0 ffffff00859693c0 ffffff00859693c0 dgram 0 0 0 ffffff0004dede10 0 ffffff0004deca50 ffffff0004dec960 dgram 0 0 0 ffffff0004ea5000 0 0 ffffff0004deca50 dgram 0 0 0 ffffff0004dede10 0 ffffff0004dedd20 ffffff0004dedd20 dgram 0 0 0 ffffff0004dede10 0 0 ffffff0004dede10 dgram 0 0 ffffff0004fa3938 0 ffffff00857fa870 0 /var/run/logpriv ffffff0004ea5000 dgram 0 0 ffffff0004fa3b10 0 ffffff0004dec960 0 /var/run/log ------------------------------------------------------------------------ netstat -aL ------------------------------------------------------------------------ fstat USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root zpool 2001 root / 3 drwxr-xr-x 32 r root zpool 2001 wd / 24 drwxr-xr-x 98 r root zpool 2001 text / 1090 -r-xr-xr-x 67152 r root zpool 2001 0 /dev 55 crw------- ttyv1 rw root zpool 2001 1 /dev 55 crw------- ttyv1 rw root zpool 2001 2 /dev 55 crw------- ttyv1 rw root zpool 2001 3 /dev 76 crw-rw---- zfs rw root zpool 2001 4 /dev 31 crw-rw-rw- null r root zpool 2001 5 / 745 -rw-r--r-- 0 r root tcsh 1997 root / 3 drwxr-xr-x 32 r root tcsh 1997 wd / 24 drwxr-xr-x 98 r root tcsh 1997 text / 1008 -r-xr-xr-x 345232 r root tcsh 1997 15 /dev 55 crw------- ttyv1 rw root tcsh 1997 16 /dev 55 crw------- ttyv1 rw root tcsh 1997 17 /dev 55 crw------- ttyv1 rw root tcsh 1997 18 /dev 55 crw------- ttyv1 rw root tcsh 1997 19 /dev 55 crw------- ttyv1 rw root zil_clean 1967 root / 3 drwxr-xr-x 32 r root zil_clean 1967 wd / 3 drwxr-xr-x 32 r root zil_clean 1966 root / 3 drwxr-xr-x 32 r root zil_clean 1966 wd / 3 drwxr-xr-x 32 r root zil_clean 1964 root / 3 drwxr-xr-x 32 r root zil_clean 1964 wd / 3 drwxr-xr-x 32 r root zil_clean 1962 root / 3 drwxr-xr-x 32 r root zil_clean 1962 wd / 3 drwxr-xr-x 32 r root zil_clean 1960 root / 3 drwxr-xr-x 32 r root zil_clean 1960 wd / 3 drwxr-xr-x 32 r root zil_clean 1958 root / 3 drwxr-xr-x 32 r root zil_clean 1958 wd / 3 drwxr-xr-x 32 r root zil_clean 1957 root / 3 drwxr-xr-x 32 r root zil_clean 1957 wd / 3 drwxr-xr-x 32 r root zil_clean 1956 root / 3 drwxr-xr-x 32 r root zil_clean 1956 wd / 3 drwxr-xr-x 32 r root zil_clean 1955 root / 3 drwxr-xr-x 32 r root zil_clean 1955 wd / 3 drwxr-xr-x 32 r root zil_clean 1954 root / 3 drwxr-xr-x 32 r root zil_clean 1954 wd / 3 drwxr-xr-x 32 r root zil_clean 1953 root / 3 drwxr-xr-x 32 r root zil_clean 1953 wd / 3 drwxr-xr-x 32 r root zil_clean 1952 root / 3 drwxr-xr-x 32 r root zil_clean 1952 wd / 3 drwxr-xr-x 32 r root zil_clean 1951 root / 3 drwxr-xr-x 32 r root zil_clean 1951 wd / 3 drwxr-xr-x 32 r root zil_clean 1950 root / 3 drwxr-xr-x 32 r root zil_clean 1950 wd / 3 drwxr-xr-x 32 r root zil_clean 1949 root / 3 drwxr-xr-x 32 r root zil_clean 1949 wd / 3 drwxr-xr-x 32 r root zil_clean 1948 root / 3 drwxr-xr-x 32 r root zil_clean 1948 wd / 3 drwxr-xr-x 32 r root zil_clean 1947 root / 3 drwxr-xr-x 32 r root zil_clean 1947 wd / 3 drwxr-xr-x 32 r root zil_clean 1946 root / 3 drwxr-xr-x 32 r root zil_clean 1946 wd / 3 drwxr-xr-x 32 r root zil_clean 1945 root / 3 drwxr-xr-x 32 r root zil_clean 1945 wd / 3 drwxr-xr-x 32 r root zil_clean 1944 root / 3 drwxr-xr-x 32 r root zil_clean 1944 wd / 3 drwxr-xr-x 32 r root zil_clean 1943 root / 3 drwxr-xr-x 32 r root zil_clean 1943 wd / 3 drwxr-xr-x 32 r root zil_clean 1942 root / 3 drwxr-xr-x 32 r root zil_clean 1942 wd / 3 drwxr-xr-x 32 r root zil_clean 1941 root / 3 drwxr-xr-x 32 r root zil_clean 1941 wd / 3 drwxr-xr-x 32 r root zil_clean 1940 root / 3 drwxr-xr-x 32 r root zil_clean 1940 wd / 3 drwxr-xr-x 32 r root zil_clean 1939 root / 3 drwxr-xr-x 32 r root zil_clean 1939 wd / 3 drwxr-xr-x 32 r root zil_clean 1778 root / 3 drwxr-xr-x 32 r root zil_clean 1778 wd / 3 drwxr-xr-x 32 r root zil_clean 1777 root / 3 drwxr-xr-x 32 r root zil_clean 1777 wd / 3 drwxr-xr-x 32 r root zil_clean 1775 root / 3 drwxr-xr-x 32 r root zil_clean 1775 wd / 3 drwxr-xr-x 32 r root tcsh 1714 root / 3 drwxr-xr-x 32 r root tcsh 1714 wd / 24 drwxr-xr-x 98 r root tcsh 1714 text / 1008 -r-xr-xr-x 345232 r root tcsh 1714 0 /dev 54 crw------- ttyv0 rw root tcsh 1714 1 /dev 54 crw------- ttyv0 rw root tcsh 1714 2 /dev 54 crw------- ttyv0 rw root tcsh 1714 15 /dev 54 crw------- ttyv0 rw root tcsh 1714 16 /dev 54 crw------- ttyv0 rw root tcsh 1714 17 /dev 54 crw------- ttyv0 rw root tcsh 1714 18 /dev 54 crw------- ttyv0 rw root tcsh 1714 19 /dev 54 crw------- ttyv0 rw root getty 1710 root / 3 drwxr-xr-x 32 r root getty 1710 wd / 3 drwxr-xr-x 32 r root getty 1710 text /usr 1227 -r-xr-xr-x 27728 r root getty 1710 0 /dev 64 crw------- ttyva rw root getty 1710 1 /dev 64 crw------- ttyva rw root getty 1710 2 /dev 64 crw------- ttyva rw root getty 1709 root / 3 drwxr-xr-x 32 r root getty 1709 wd / 3 drwxr-xr-x 32 r root getty 1709 text /usr 1227 -r-xr-xr-x 27728 r root getty 1709 0 /dev 63 crw------- ttyv9 rw root getty 1709 1 /dev 63 crw------- ttyv9 rw root getty 1709 2 /dev 63 crw------- ttyv9 rw root getty 1708 root / 3 drwxr-xr-x 32 r root getty 1708 wd / 3 drwxr-xr-x 32 r root getty 1708 text /usr 1227 -r-xr-xr-x 27728 r root getty 1708 0 /dev 62 crw------- ttyv8 rw root getty 1708 1 /dev 62 crw------- ttyv8 rw root getty 1708 2 /dev 62 crw------- ttyv8 rw root getty 1707 root / 3 drwxr-xr-x 32 r root getty 1707 wd / 3 drwxr-xr-x 32 r root getty 1707 text /usr 1227 -r-xr-xr-x 27728 r root getty 1707 0 /dev 61 crw------- ttyv7 rw root getty 1707 1 /dev 61 crw------- ttyv7 rw root getty 1707 2 /dev 61 crw------- ttyv7 rw root getty 1706 root / 3 drwxr-xr-x 32 r root getty 1706 wd / 3 drwxr-xr-x 32 r root getty 1706 text /usr 1227 -r-xr-xr-x 27728 r root getty 1706 0 /dev 60 crw------- ttyv6 rw root getty 1706 1 /dev 60 crw------- ttyv6 rw root getty 1706 2 /dev 60 crw------- ttyv6 rw root getty 1705 root / 3 drwxr-xr-x 32 r root getty 1705 wd / 3 drwxr-xr-x 32 r root getty 1705 text /usr 1227 -r-xr-xr-x 27728 r root getty 1705 0 /dev 59 crw------- ttyv5 rw root getty 1705 1 /dev 59 crw------- ttyv5 rw root getty 1705 2 /dev 59 crw------- ttyv5 rw root getty 1704 root / 3 drwxr-xr-x 32 r root getty 1704 wd / 3 drwxr-xr-x 32 r root getty 1704 text /usr 1227 -r-xr-xr-x 27728 r root getty 1704 0 /dev 58 crw------- ttyv4 rw root getty 1704 1 /dev 58 crw------- ttyv4 rw root getty 1704 2 /dev 58 crw------- ttyv4 rw root getty 1703 root / 3 drwxr-xr-x 32 r root getty 1703 wd / 3 drwxr-xr-x 32 r root getty 1703 text /usr 1227 -r-xr-xr-x 27728 r root getty 1703 0 /dev 57 crw------- ttyv3 rw root getty 1703 1 /dev 57 crw------- ttyv3 rw root getty 1703 2 /dev 57 crw------- ttyv3 rw root getty 1702 root / 3 drwxr-xr-x 32 r root getty 1702 wd / 3 drwxr-xr-x 32 r root getty 1702 text /usr 1227 -r-xr-xr-x 27728 r root getty 1702 0 /dev 56 crw------- ttyv2 rw root getty 1702 1 /dev 56 crw------- ttyv2 rw root getty 1702 2 /dev 56 crw------- ttyv2 rw root login 1701 root / 3 drwxr-xr-x 32 r root login 1701 wd / 24 drwxr-xr-x 98 r root login 1701 text /usr 817 -r-sr-xr-x 25400 r root login 1701 0 /dev 55 crw------- ttyv1 rw root login 1701 1 /dev 55 crw------- ttyv1 rw root login 1701 2 /dev 55 crw------- ttyv1 rw root login 1701 3 / 751 -rw------- 567 r root login 1701 4 / 750 -r--r--r-- 652 r root login 1701 5 / 746 -rw------- 225 r root login 1701 6* local dgram ffffff00857fa870 <-> ffffff0004dede10 root login 1700 root / 3 drwxr-xr-x 32 r root login 1700 wd / 24 drwxr-xr-x 98 r root login 1700 text /usr 817 -r-sr-xr-x 25400 r root login 1700 0 /dev 54 crw------- ttyv0 rw root login 1700 1 /dev 54 crw------- ttyv0 rw root login 1700 2 /dev 54 crw------- ttyv0 rw root login 1700 3 / 751 -rw------- 567 r root login 1700 4 / 750 -r--r--r-- 652 r root login 1700 5 / 746 -rw------- 225 r root login 1700 6* local dgram ffffff00859693c0 <-> ffffff0004dede10 root inetd 1674 root / 3 drwxr-xr-x 32 r root inetd 1674 wd / 3 drwxr-xr-x 32 r root inetd 1674 text /usr 191 -r-xr-xr-x 47296 r root inetd 1674 0 /dev 31 crw-rw-rw- null rw root inetd 1674 1 /dev 31 crw-rw-rw- null rw root inetd 1674 2 /dev 31 crw-rw-rw- null rw root inetd 1674 3 /var 6228 -rw------- 4 w root inetd 1674 4* pipe ffffff0004e71858 <-> ffffff0004e719a8 0 rw root inetd 1674 5* pipe ffffff0004e719a8 <-> ffffff0004e71858 0 rw root moused 1650 root / 3 drwxr-xr-x 32 r root moused 1650 wd / 3 drwxr-xr-x 32 r root moused 1650 text /usr 194 -r-xr-xr-x 40080 r root moused 1650 0 /dev 31 crw-rw-rw- null rw root moused 1650 1 /dev 31 crw-rw-rw- null rw root moused 1650 2 /dev 31 crw-rw-rw- null rw root moused 1650 3 /dev 46 crw-rw-rw- psm0 rw root moused 1650 4 /dev 70 crw------- consolectl rw root moused 1650 5 /var 6227 -rw------- 4 w root uptimed 1638 root / 3 drwxr-xr-x 32 r root uptimed 1638 wd / 3 drwxr-xr-x 32 r root uptimed 1638 text /usr/local 110466 -r-xr-xr-x 15872 r root cron 1629 root / 3 drwxr-xr-x 32 r root cron 1629 wd /var 13 drwxr-x--- 3 r root cron 1629 text /usr 256 -r-xr-xr-x 38608 r root cron 1629 0 /dev 31 crw-rw-rw- null rw root cron 1629 1 /dev 31 crw-rw-rw- null rw root cron 1629 2 /dev 31 crw-rw-rw- null rw root cron 1629 3 /var 6224 -rw------- 4 w smmsp sendmail 1623 root / 3 drwxr-xr-x 32 r smmsp sendmail 1623 wd /var 110 drwxrwx--- 3 r smmsp sendmail 1623 text /usr 1229 -r-xr-sr-x 680072 r smmsp sendmail 1623 0 /dev 31 crw-rw-rw- null r smmsp sendmail 1623 1 /dev 31 crw-rw-rw- null w smmsp sendmail 1623 2 /dev 31 crw-rw-rw- null w smmsp sendmail 1623 3* local dgram ffffff0004dec960 <-> ffffff0004ea5000 root sendmail 1617 root / 3 drwxr-xr-x 32 r root sendmail 1617 wd /var 111 drwxr-xr-x 2 r root sendmail 1617 text /usr 1229 -r-xr-sr-x 680072 r root sendmail 1617 0 /dev 31 crw-rw-rw- null r root sendmail 1617 1 /dev 31 crw-rw-rw- null w root sendmail 1617 2 /dev 31 crw-rw-rw- null w root sendmail 1617 3* local dgram ffffff0004deca50 <-> ffffff0004dede10 root sendmail 1617 4* internet stream tcp ffffff0085608888 root sendmail 1617 5* internet6 stream tcp ffffff00856085b0 root sendmail 1617 6* internet stream tcp ffffff00856082d8 root sendmail 1617 7 /var 6223 -rw------- 44 w root sshd 1612 root / 3 drwxr-xr-x 32 r root sshd 1612 wd / 3 drwxr-xr-x 32 r root sshd 1612 text /usr 210 -r-xr-xr-x 241824 r root sshd 1612 0 /dev 31 crw-rw-rw- null rw root sshd 1612 1 /dev 31 crw-rw-rw- null rw root sshd 1612 2 /dev 31 crw-rw-rw- null rw root sshd 1612 3* internet6 stream tcp ffffff0085703000 root sshd 1612 4* internet stream tcp ffffff0085608b60 daemon slpd 1580 root / 3 drwxr-xr-x 32 r daemon slpd 1580 wd / 3 drwxr-xr-x 32 r daemon slpd 1580 text /usr/local 110501 -r-xr-xr-x 82784 r daemon slpd 1580 3 /var 6120 -rw------- 812302 w daemon slpd 1580 4* internet stream tcp ffffff0004f9d888 daemon slpd 1580 5* internet stream tcp ffffff0004f9d5b0 daemon slpd 1580 6* internet dgram udp ffffff0004d90af0 daemon slpd 1580 7* internet dgram udp ffffff00857cf9d8 root cupsd 1571 root / 3 drwxr-xr-x 32 r root cupsd 1571 wd / 3 drwxr-xr-x 32 r root cupsd 1571 text /usr/local 110523 -rwxr-xr-x 908330 r root cupsd 1571 1 /dev 7 crw-rw-rw- random r root cupsd 1571 2 /var 6215 -rw-r--r-- 1564517 rw root cupsd 1571 3* internet stream tcp ffffff00857035b0 root cupsd 1571 4* internet6 stream tcp ffffff00857032d8 root cupsd 1571 5* local stream ffffff0004decd20 root cupsd 1571 6* internet dgram udp ffffff0004d6faf0 root cupsd 1571 7* pipe ffffff0004472b20 <-> ffffff0004472c70 0 rw root cupsd 1571 8* pipe ffffff0004472c70 <-> ffffff0004472b20 0 rw nobody mdnsd 1558 root / 3 drwxr-xr-x 32 r nobody mdnsd 1558 wd / 3 drwxr-xr-x 32 r nobody mdnsd 1558 text /usr/local 110499 -rwxr-xr-x 189869 r nobody mdnsd 1558 0 /dev 31 crw-rw-rw- null rw nobody mdnsd 1558 1 /dev 31 crw-rw-rw- null rw nobody mdnsd 1558 2 /dev 31 crw-rw-rw- null rw nobody mdnsd 1558 3* internet dgram udp ffffff0004d90578 nobody mdnsd 1558 4* internet dgram udp ffffff0004d909d8 nobody mdnsd 1558 5 / 536 -rw-r--r-- 44 r nobody mdnsd 1558 6* route raw 0 ffffff0004d6e780 nobody mdnsd 1558 7* local stream ffffff0004dedb40 nobody mdnsd 1558 8 / 536 -rw-r--r-- 44 r root powerd 1503 root / 3 drwxr-xr-x 32 r root powerd 1503 wd / 3 drwxr-xr-x 32 r root powerd 1503 text /usr 227 -r-xr-xr-x 13488 r root powerd 1503 0 /dev 31 crw-rw-rw- null rw root powerd 1503 1 /dev 31 crw-rw-rw- null rw root powerd 1503 2 /dev 31 crw-rw-rw- null rw root powerd 1503 3 /var 4542 -rw------- 4 w root auditd 1370 root / 3 drwxr-xr-x 32 r root auditd 1370 wd / 3 drwxr-xr-x 32 r root auditd 1370 text /usr 77 -r-xr-xr-x 20384 r root auditd 1370 0 /dev 31 crw-rw-rw- null rw root auditd 1370 1 /dev 31 crw-rw-rw- null rw root auditd 1370 2 /dev 31 crw-rw-rw- null rw root auditd 1370 3* local dgram ffffff0004dedd20 <-> ffffff0004dede10 root auditd 1370 4 /var 4538 -rw-r--r-- 5 w root auditd 1370 5 /dev 19 crw------- audit r root auditd 1370 6 / 746 -rw------- 225 r root auditd 1370 8 / 750 -r--r--r-- 652 r root syslogd 1315 root / 3 drwxr-xr-x 32 r root syslogd 1315 wd / 3 drwxr-xr-x 32 r root syslogd 1315 text /usr 242 -r-xr-xr-x 38976 r root syslogd 1315 0 /dev 31 crw-rw-rw- null rw root syslogd 1315 1 /dev 31 crw-rw-rw- null rw root syslogd 1315 2 /dev 31 crw-rw-rw- null rw root syslogd 1315 3 /var 46 -rw------- 4 w root syslogd 1315 4* local dgram ffffff0004ea5000 root syslogd 1315 5* local dgram ffffff0004dede10 root syslogd 1315 6* internet6 dgram udp ffffff0004d6fe38 root syslogd 1315 7* internet dgram udp ffffff0004d90000 root syslogd 1315 8 /dev 33 crw------- klog r root syslogd 1315 10 - - bad - root syslogd 1315 11 /var 6284 -rw-r--r-- 26174 w root syslogd 1315 12 /var 6165 -rw------- 3761 w root syslogd 1315 13 /var 6127 -rw------- 51509 w root syslogd 1315 14 /var 6167 -rw-r----- 5487 w root syslogd 1315 15 /var 6199 -rw-r--r-- 82 w root syslogd 1315 16 /var 6119 -rw------- 82 w root syslogd 1315 17 /var 6147 -rw------- 25357 w root syslogd 1315 18 /var 6124 -rw------- 82118 w root syslogd 1315 19 /var 6146 -rw------- 49305 w root syslogd 1315 20 /var 6198 -rw------- 599426 w root syslogd 1315 21 /var 6101 -rw-r----- 82 w root syslogd 1315 22 /var 6104 -rw-r----- 82 w root syslogd 1315 23 /var 6099 -rw-r--r-- 255549441 w root devd 1072 root / 3 drwxr-xr-x 32 r root devd 1072 wd / 3 drwxr-xr-x 32 r root devd 1072 text / 1124 -r-xr-xr-x 401160 r root devd 1072 0 /dev 31 crw-rw-rw- null rw root devd 1072 1 /dev 31 crw-rw-rw- null rw root devd 1072 2 /dev 31 crw-rw-rw- null rw root devd 1072 3 /dev 5 crw------- devctl r root devd 1072 4* local stream ffffff0004ded000 root devd 1072 5 /var 39 -rw------- 4 w root adjkerntz 545 root / 3 drwxr-xr-x 32 r root adjkerntz 545 wd / 3 drwxr-xr-x 32 r root adjkerntz 545 text / 1102 -r-xr-xr-x 9072 r root adjkerntz 545 0 /dev 31 crw-rw-rw- null rw root adjkerntz 545 1 /dev 31 crw-rw-rw- null rw root adjkerntz 545 2 /dev 31 crw-rw-rw- null rw root zil_clean 455 root / 3 drwxr-xr-x 32 r root zil_clean 455 wd / 3 drwxr-xr-x 32 r root zil_clean 448 root / 3 drwxr-xr-x 32 r root zil_clean 448 wd / 3 drwxr-xr-x 32 r root zil_clean 435 root / 3 drwxr-xr-x 32 r root zil_clean 435 wd / 3 drwxr-xr-x 32 r root zil_clean 434 root / 3 drwxr-xr-x 32 r root zil_clean 434 wd / 3 drwxr-xr-x 32 r root zil_clean 433 root / 3 drwxr-xr-x 32 r root zil_clean 433 wd / 3 drwxr-xr-x 32 r root txg_thread_enter 423 root / 3 drwxr-xr-x 32 r root txg_thread_enter 423 wd / 3 drwxr-xr-x 32 r root txg_thread_enter 422 root / 3 drwxr-xr-x 32 r root txg_thread_enter 422 wd / 3 drwxr-xr-x 32 r root txg_thread_enter 421 root / 3 drwxr-xr-x 32 r root txg_thread_enter 421 wd / 3 drwxr-xr-x 32 r root vdev:worker ad14s1 420 root / 3 drwxr-xr-x 32 r root vdev:worker ad14s1 420 wd / 3 drwxr-xr-x 32 r root vdev:worker ad12s1 419 root / 3 drwxr-xr-x 32 r root vdev:worker ad12s1 419 wd / 3 drwxr-xr-x 32 r root vdev:worker ad6s1d 418 root / 3 drwxr-xr-x 32 r root vdev:worker ad6s1d 418 wd / 3 drwxr-xr-x 32 r root vdev:worker ad4s1d 417 root / 3 drwxr-xr-x 32 r root vdev:worker ad4s1d 417 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 416 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 416 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 415 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 415 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 414 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 414 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 413 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 413 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 412 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 412 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 411 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 411 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 410 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 410 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 409 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 409 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 408 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 408 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 407 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 407 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 406 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 406 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 405 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 405 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 404 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 404 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 403 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 403 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 402 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 402 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 401 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 401 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 400 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 400 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 399 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 399 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 398 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 398 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 397 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 397 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 396 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 396 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 395 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 395 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 394 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 394 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 393 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 393 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 392 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 392 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 391 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 391 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 390 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 390 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 389 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 389 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 388 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 388 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 387 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 387 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 386 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 386 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 385 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 385 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 384 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 384 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 383 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 383 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 382 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 382 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 381 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 381 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 380 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 380 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 379 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 379 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 378 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 378 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 377 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 377 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 376 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 376 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 375 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 375 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 374 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 374 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 373 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 373 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 372 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 372 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 371 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 371 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 370 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 370 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 369 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 369 wd / 3 drwxr-xr-x 32 r root txg_thread_enter 316 root / 3 drwxr-xr-x 32 r root txg_thread_enter 316 wd / 3 drwxr-xr-x 32 r root txg_thread_enter 315 root / 3 drwxr-xr-x 32 r root txg_thread_enter 315 wd / 3 drwxr-xr-x 32 r root txg_thread_enter 314 root / 3 drwxr-xr-x 32 r root txg_thread_enter 314 wd / 3 drwxr-xr-x 32 r root vdev:worker da0s2a 313 root / 3 drwxr-xr-x 32 r root vdev:worker da0s2a 313 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 312 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 312 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 311 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 311 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 310 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 310 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 309 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 309 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 308 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 308 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 307 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 307 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 306 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 306 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 305 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 305 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 304 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 304 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 303 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 303 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 302 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 302 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 301 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 301 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 300 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 300 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 299 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 299 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 298 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 298 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 297 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 297 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 296 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 296 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 295 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 295 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 294 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 294 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 293 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 293 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 292 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 292 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 291 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 291 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 290 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 290 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 289 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 289 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 288 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 288 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 287 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 287 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 286 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 286 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 285 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 285 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 284 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 284 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 283 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 283 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 282 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 282 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 281 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 281 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 280 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 280 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 279 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 279 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 278 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 278 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 277 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 277 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 276 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 276 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 275 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 275 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 274 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 274 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 273 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 273 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 272 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 272 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 271 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 271 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 270 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 270 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 269 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 269 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 268 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 268 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 267 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 267 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 266 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 266 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 265 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 265 wd / 3 drwxr-xr-x 32 r root USBPROC 196 root / 3 drwxr-xr-x 32 r root USBPROC 196 wd / 3 drwxr-xr-x 32 r root USBPROC 195 root / 3 drwxr-xr-x 32 r root USBPROC 195 wd / 3 drwxr-xr-x 32 r root USBPROC 194 root / 3 drwxr-xr-x 32 r root USBPROC 194 wd / 3 drwxr-xr-x 32 r root USBPROC 193 root / 3 drwxr-xr-x 32 r root USBPROC 193 wd / 3 drwxr-xr-x 32 r root USBPROC 192 root / 3 drwxr-xr-x 32 r root USBPROC 192 wd / 3 drwxr-xr-x 32 r root USBPROC 191 root / 3 drwxr-xr-x 32 r root USBPROC 191 wd / 3 drwxr-xr-x 32 r root USBPROC 172 root / 3 drwxr-xr-x 32 r root USBPROC 172 wd / 3 drwxr-xr-x 32 r root USBPROC 171 root / 3 drwxr-xr-x 32 r root USBPROC 171 wd / 3 drwxr-xr-x 32 r root zil_clean 145 root / 3 drwxr-xr-x 32 r root zil_clean 145 wd / 3 drwxr-xr-x 32 r root txg_thread_enter 144 root / 3 drwxr-xr-x 32 r root txg_thread_enter 144 wd / 3 drwxr-xr-x 32 r root txg_thread_enter 143 root / 3 drwxr-xr-x 32 r root txg_thread_enter 143 wd / 3 drwxr-xr-x 32 r root txg_thread_enter 142 root / 3 drwxr-xr-x 32 r root txg_thread_enter 142 wd / 3 drwxr-xr-x 32 r root vdev:worker ad14s2 141 root / 3 drwxr-xr-x 32 r root vdev:worker ad14s2 141 wd / 3 drwxr-xr-x 32 r root vdev:worker ad12s2 140 root / 3 drwxr-xr-x 32 r root vdev:worker ad12s2 140 wd / 3 drwxr-xr-x 32 r root USBPROC 139 root / 3 drwxr-xr-x 32 r root USBPROC 139 wd / 3 drwxr-xr-x 32 r root vdev:worker ad6s2 138 root / 3 drwxr-xr-x 32 r root vdev:worker ad6s2 138 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 137 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 137 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 136 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 136 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 135 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 135 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_5 134 root / 3 drwxr-xr-x 32 r root spa_zio_intr_5 134 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 133 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 133 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 132 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 132 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 131 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 131 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_5 130 root / 3 drwxr-xr-x 32 r root spa_zio_issue_5 130 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 129 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 129 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 128 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 128 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 127 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 127 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_4 126 root / 3 drwxr-xr-x 32 r root spa_zio_intr_4 126 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 125 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 125 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 124 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 124 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 123 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 123 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_4 122 root / 3 drwxr-xr-x 32 r root spa_zio_issue_4 122 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 121 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 121 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 120 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 120 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 119 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 119 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_3 118 root / 3 drwxr-xr-x 32 r root spa_zio_intr_3 118 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 117 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 117 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 116 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 116 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 115 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 115 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_3 114 root / 3 drwxr-xr-x 32 r root spa_zio_issue_3 114 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 113 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 113 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 112 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 112 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 111 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 111 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_2 110 root / 3 drwxr-xr-x 32 r root spa_zio_intr_2 110 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 109 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 109 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 108 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 108 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 107 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 107 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_2 106 root / 3 drwxr-xr-x 32 r root spa_zio_issue_2 106 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 105 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 105 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 104 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 104 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 103 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 103 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_1 102 root / 3 drwxr-xr-x 32 r root spa_zio_intr_1 102 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 101 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 101 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 100 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 100 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 99 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 99 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_1 98 root / 3 drwxr-xr-x 32 r root spa_zio_issue_1 98 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 97 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 97 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 96 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 96 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 95 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 95 wd / 3 drwxr-xr-x 32 r root spa_zio_intr_0 94 root / 3 drwxr-xr-x 32 r root spa_zio_intr_0 94 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 93 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 93 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 92 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 92 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 91 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 91 wd / 3 drwxr-xr-x 32 r root spa_zio_issue_0 90 root / 3 drwxr-xr-x 32 r root spa_zio_issue_0 90 wd / 3 drwxr-xr-x 32 r root USBPROC 89 root / 3 drwxr-xr-x 32 r root USBPROC 89 wd / 3 drwxr-xr-x 32 r root init 1 root / 3 drwxr-xr-x 32 r root init 1 wd / 3 drwxr-xr-x 32 r root init 1 text / 1197 -r-xr-xr-x 705696 r root kernel 0 root / 3 drwxr-xr-x 32 r root kernel 0 wd / 3 drwxr-xr-x 32 r ------------------------------------------------------------------------ dmesg Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #1: Wed Oct 15 21:39:04 BST 2008 sandbox@w2fzz0vc03.aah-go-on.com:/usr/home/sandbox/newusb/obj/usr/home/sandbox/newusb/src/sys/GENERIC_usb2 WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Quad CPU @ 2.66GHz (2660.04-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f7 Stepping = 7 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 4 usable memory = 4276260864 (4078 MB) avail memory = 4091035648 (3901 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ ioapic0: Changing APIC ID to 8 ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 ath_hal: 0.10.5.10 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, f00000 (3) failed acpi0: reservation of 1000000, 9edbcc00 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 25000000 Hz quality 900 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 1.0 (no driver attached) pci0: at device 1.1 (no driver attached) pci0: at device 1.2 (no driver attached) pci0: at device 1.3 (no driver attached) pci0: at device 1.4 (no driver attached) pci0: at device 1.5 (no driver attached) pci0: at device 1.6 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 vgapci0: port 0xdc80-0xdcff mem 0xde000000-0xdeffffff,0xa0000000-0xafffffff,0xdc000000-0xddffffff irq 16 at device 0.0 on pci1 pcib2: at device 4.0 on pci0 pci2: on pcib2 pcib3: at device 5.0 on pci0 pci3: on pcib3 pci0: at device 9.0 (no driver attached) isab0: port 0x4f00-0x4fff at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) ohci0: mem 0xdfffc000-0xdfffcfff irq 21 at device 11.0 on pci0 ohci0: [ITHREAD] usbus0: on ohci0 ehci0: mem 0xdfffbf00-0xdfffbfff irq 22 at device 11.1 on pci0 ehci0: [ITHREAD] usbus1: waiting for BIOS to give up control usbus1: EHCI version 1.0 usbus1: on ehci0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xecf0-0xecff at device 13.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf mem 0xdfffd000-0xdfffdfff irq 23 at device 14.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] atapci2: port 0xfe40-0xfe47,0xfe50-0xfe53,0xfe60-0xfe67,0xfe70-0xfe73,0xfed0-0xfedf mem 0xdfffe000-0xdfffefff irq 20 at device 14.1 on pci0 atapci2: [ITHREAD] ata4: on atapci2 ata4: [ITHREAD] ata5: on atapci2 ata5: [ITHREAD] atapci3: port 0xfe80-0xfe87,0xfe90-0xfe93,0xfea0-0xfea7,0xfeb0-0xfeb3,0xfef0-0xfeff mem 0xdffff000-0xdfffffff irq 21 at device 14.2 on pci0 atapci3: [ITHREAD] ata6: on atapci3 ata6: [ITHREAD] ata7: on atapci3 ata7: [ITHREAD] pcib4: at device 15.0 on pci0 pci4: on pcib4 pci4: at device 4.0 (no driver attached) pci4: at device 5.0 (no driver attached) fwohci0: mem 0xdadfb800-0xdadfbfff,0xdadfc000-0xdadfffff irq 18 at device 10.0 on pci4 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 80:00:00:00:00:00:00:00 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x2598000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 82:00:00:00:00:00 fwe0: Ethernet address: 82:00:00:00:00:00 fwip0: on firewire0 fwip0: Firewire address: 80:00:00:00:00:00:00:00 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode pcib5: at device 19.0 on pci0 pci5: on pcib5 pcib6: at device 24.0 on pci0 pci6: on pcib6 vgapci1: port 0xbc80-0xbcff mem 0xd1000000-0xd1ffffff,0xc0000000-0xcfffffff,0xd2000000-0xd3ffffff irq 16 at device 0.0 on pci6 atrtc0: port 0x70-0x7f irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model MouseMan+, device ID 0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr a2a0a2a86000a2a device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr a2a0a2a86000a2a device_attach: est1 attach returned 6 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr a2a0a2a86000a2a device_attach: est2 attach returned 6 p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr a2a0a2a86000a2a device_attach: est3 attach returned 6 p4tcc3: on cpu3 orm0: at iomem 0xc0000-0xcc7ff,0xcc800-0xce7ff,0xce800-0xcffff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ZFS filesystem version 6 ZFS storage pool version 6 ugen0.1: at usbus0 ushub0: on usbus0 ushub0: 10 ports with 10 removable, self powered usbus1: 480Mbps High Speed USB v2.0 ugen1.1: at usbus1 ushub1: on usbus1 ushub1: 10 ports with 10 removable, self powered ad4: 305245MB at ata2-master SATA300 ad6: 305245MB at ata3-master SATA300 acd0: CDRW at ata4-master SATA150 acd1: DVDR at ata5-master SATA150 GEOM_LABEL: Label for provider ad4s2 is ntfs/System. ad12: 305245MB at ata6-master SATA300 ad14: 305245MB at ata7-master SATA300 lapic1: Forcing LINT1 to edge trigger SMP: AP CPU #1 Launched! lapic2: Forcing LINT1 to edge trigger SMP: AP CPU #2 Launched! lapic3: Forcing LINT1 to edge trigger SMP: AP CPU #3 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from zfs:tank lock order reversal: 1st 0xffffff0002d72000 vfslock (vfslock) @ /usr/home/sandbox/newusb/src/sys/kern/vfs_subr.c:372 2nd 0xffffff0002d73448 devfs (devfs) @ /usr/home/sandbox/newusb/src/sys/kern/vfs_lookup.c:428 3rd 0xffffff0002d71c80 vfslock (vfslock) @ /usr/home/sandbox/newusb/src/sys/kern/vfs_subr.c:372 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x49 witness_checkorder() at witness_checkorder+0x7a5 __lockmgr_args() at __lockmgr_args+0xca6 vfs_busy() at vfs_busy+0xd0 vfs_mount_alloc() at vfs_mount_alloc+0x7d vfs_donmount() at vfs_donmount+0xf05 kernel_mount() at kernel_mount+0xa1 kernel_vmount() at kernel_vmount+0xce vfs_mountroot_try() at vfs_mountroot_try+0xf4 vfs_mountroot() at vfs_mountroot+0x3ea start_init() at start_init+0x62 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xfffffffe40023d40, rbp = 0 --- ugen1.2: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0000 lock order reversal: 1st 0xffffff0002c4a7f8 zfs (zfs) @ /usr/home/sandbox/newusb/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1123 2nd 0xffffff0002d72000 vfslock (vfslock) @ /usr/home/sandbox/newusb/src/sys/kern/vfs_subr.c:372 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x49 witness_checkorder() at witness_checkorder+0x7a5 __lockmgr_args() at __lockmgr_args+0xca6 vfs_busy() at vfs_busy+0xd0 lookup() at lookup+0x8c0 namei() at namei+0x454 kern_unlinkat() at kern_unlinkat+0x9d vfs_mountroot_try() at vfs_mountroot_try+0x411 vfs_mountroot() at vfs_mountroot+0x3ea start_init() at start_init+0x62 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xfffffffe40023d40, rbp = 0 --- lock order reversal: 1st 0xffffff00024ee070 user map (user map) @ /usr/home/sandbox/newusb/src/sys/vm/vm_map.c:3115 2nd 0xffffff0002c4a448 zfs (zfs) @ /usr/home/sandbox/newusb/src/sys/kern/vfs_subr.c:2049 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x49 witness_checkorder() at witness_checkorder+0x7a5 __lockmgr_args() at __lockmgr_args+0xca6 vop_stdlock() at vop_stdlock+0x39 VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b _vn_lock() at umass0:1:0:-1: At_tvanc_hleodc kt+o0 xs5c0bu s1 vget() at vget+0x7d vnode_pager_lock() at vnode_pager_lock+0x1d4 vm_fault() at vm_fault+0x22f trap_pfault() at trap_pfault+0x103 trap() at trap+0x51c calltrap() at calltrap+0x8 --- trap 0xc, rip = 0x40014f, rsp = 0x7fffffffee70, rbp = 0x7fffffffee90 --- da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) GEOM_LABEL: Label for provider da0s1 is ntfs/Backup. Entropy harvesting: interrupts ethernet point_to_point ugen1.3: at usbus1 ushub2: on usbus1 kickstart . ushub2: 7 ports with 7 removable, self powered ugen1.4: at usbus1 ugen1.5: at usbus1 rum0: on usbus1 rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528 ugen1.6: at usbus1 umass1: on usbus1 umass1: SCSI over Bulk-Only; quirks = 0x0000 umass1:2:1:-1: Attached to scbus2 da1 at umass-sim1 bus 1 target 0 lun 0 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da2 at umass-sim1 bus 1 target 0 lun 1 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim1 bus 1 target 0 lun 2 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present da4 at umass-sim1 bus 1 target 0 lun 3 da4: Removable Direct Access SCSI-0 device da4: 40.000MB/s transfers da4: Attempt to query device size failed: NOT READY, Medium not present /dev/ad4s1a: 6872 files, 492217 used, 520797 free (3413 frags, 64673 blocks, 0.3% fragmentation) Mismatched versions: File system is version 2 on-disk format, which is incompatible with this software version 1! cannot mount 'backup/20080823-0125': Operation not supported lock order reversal: 1st 0xffffff0004b7d098 syncer (syncer) @ /usr/home/sandbox/newusb/src/sys/kern/vfs_subr.c:1657 2nd 0xffffff0004ba7960 vfslock (vfslock) @ /usr/home/sandbox/newusb/src/sys/kern/vfs_subr.c:372 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x49 witness_checkorder() at witness_checkorder+0x7a5 __lockmgr_args() at __lockmgr_args+0xca6 vfs_busy() at vfs_busy+0xd0 sync_fsync() at sync_fsync+0x9c sync_vnode() at sync_vnode+0x143 sched_sync() at sched_sync+0x1c5 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xfffffffeb4d05d40, rbp = 0 --- wlan0: Ethernet address: 00:17:3f:72:40:90 Starting Network: lo0. add net default: gateway 192.168.0.1 Additional TCP/IP options: tcp extensions=NO . savecore: reboot after panic: mutex Giant not owned at /usr/home/sandbox/newusb/src/sys/kern/tty_ttydisc.c:1129 Oct 16 15:27:09 w2fzz0vc03 savecore: reboot after panic: mutex Giant not owned at /usr/home/sandbox/newusb/src/sys/kern/tty_ttydisc.c:1129 savecore: writing core to vmcore.41 wlan0: link state changed to UP Additional ABI support: linux . Setting date via ntp. 16 Oct 15:28:06 ntpdate[1341]: step time server 192.108.114.23 offset 0.827552 sec Setting NIS domain: aah-go-on.com. pg_ctl: invalid data in PID file "/usr/local/pgsql/data/postmaster.pid" Oct 16 15:28:08 w2fzz0vc03 mDNSResponder (Engineering Build) (Aug 19 2008 18:02:49) [1558]: starting Configuring syscons: keymap font8x16 font8x14 font8x8 blanktime screensaver . Local package initialization: uptimed . Thu Oct 16 15:28:11 BST 2008 Oct 16 15:31:28 w2fzz0vc03 login: ROOT LOGIN (root) ON ttyv0 Oct 16 15:41:04 w2fzz0vc03 login: ROOT LOGIN (root) ON ttyv1 Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex UMASS lock (UMASS lock) r = 0 (0xffffffff80b67e60) locked @ /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_transfer.c:1795 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x49 witness_warn() at witness_warn+0x232 trap() at trap+0x38f calltrap() at calltrap+0x8 --- trap 0xc, rip = 0xffffffff807b2a46, rsp = 0xfffffffeb7267ac0, rbp = 0xfffffffeb7267b00 --- bcopy() at bcopy+0x16 usb2_bdma_pre_sync() at usb2_bdma_pre_sync+0x59 usb2_bdma_work_loop() at usb2_bdma_work_loop+0x2ac usb2_command_wrapper() at usb2_command_wrapper+0x76 usb2_callback_wrapper() at usb2_callback_wrapper+0x101 usb2_command_wrapper() at usb2_command_wrapper+0x76 usb2_callback_proc() at usb2_callback_proc+0x68 usb2_process() at usb2_process+0xc0 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xfffffffeb7267d40, rbp = 0 --- Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0xfffffffe69a00000 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff807b2a46 stack pointer = 0x10:0xfffffffeb7267ac0 frame pointer = 0x10:0xfffffffeb7267b00 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 139 (USBPROC) lock order reversal: (Giant after non-sleepable) 1st 0xffffffff80b67e60 UMASS lock (UMASS lock) @ /usr/home/sandbox/newusb/src/sys/dev/usb2/core/usb2_transfer.c:1795 2nd 0xffffffff80b6bfe0 Giant (Giant) @ /usr/home/sandbox/newusb/src/sys/dev/kbdmux/kbdmux.c:1044 KDB: stack backtrace: panic: mutex Giant not owned at /usr/home/sandbox/newusb/src/sys/kern/tty_ttydisc.c:1129 cpuid = 3 KDB: stack backtrace: Physical memory: 4078 MB Dumping 1154 MB: 1139 1123 1107 1091 1075 1059 1043 1027 1011 995 979 963 947 931 915 899 883 867 851 835 819 803 787 771 755 739 723 707 691 675 659 643 627 611 595 579 563 547 531 515 499 483 467 451 435 419 403 387 371 355 339 323 307 291 275 259 243 227 211 195 179 163 147 131 115 99 83 67 51 35 19 3 ------------------------------------------------------------------------ kernel config config: File /boot/kernel/kernel doesn't contain configuration file. Either unsupported, or not compiled with INCLUDE_CONFIG_FILE -------------- next part -------------- A non-text attachment was scrubbed... Name: core.txt.42 Type: text/x-diff Size: 127988 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20081107/6a0b1af0/core.txt-0001.bin From koitsu at FreeBSD.org Fri Nov 7 14:02:44 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Nov 7 14:02:51 2008 Subject: USB4BSD release candidate number 3 - request for review In-Reply-To: <200811071946.01269.Thomas.Sparrevohn@btinternet.com> References: <200810251925.47273.hselasky@c2i.net> <20081106210300.GA1595@wep4035.physik.uni-wuerzburg.de> <200811070036.15816.hselasky@c2i.net> <200811071946.01269.Thomas.Sparrevohn@btinternet.com> Message-ID: <20081107220242.GA14562@icarus.home.lan> On Fri, Nov 07, 2008 at 07:46:00PM +0000, Thomas Sparrevohn wrote: > On Thursday 06 November 2008 23:36:14 Hans Petter Selasky wrote: > > On Thursday 06 November 2008, Alexey Shuvaev wrote: > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > _witness_debugger() at _witness_debugger+0x49 > > > witness_checkorder() at witness_checkorder+0x7e6 > > > _sx_xlock() at _sx_xlock+0x44 > > > vm_map_lookup() at vm_map_lookup+0x47 > > > vm_fault() at vm_fault+0xfe > > > trap_pfault() at trap_pfault+0x1fa > > > trap() at trap+0x201 > > > calltrap() at calltrap+0x8 > > > --- trap 0xc, rip = 0xffffffff804b2466, rsp = 0xfffffffeba7f8ac0, rbp = > > > 0xfffffffeba7f8b00 --- bcopy() at bcopy+0x16 > > > usb2_bdma_pre_sync() at usb2_bdma_pre_sync+0x35 > > > usb2_bdma_work_loop() at usb2_bdma_work_loop+0x29b > > > usb2_command_wrapper() at usb2_command_wrapper+0x76 > > > usb2_callback_wrapper() at usb2_callback_wrapper+0xfd > > > usb2_command_wrapper() at usb2_command_wrapper+0x76 > > > usb2_callback_proc() at usb2_callback_proc+0x68 > > > usb2_process() at usb2_process+0xc0 > > > > Hi Alexey, > > > > This looks more like a busdma problem to me. "bcopy()" is called from > > within "bus_dmamap_sync()". Maybe you can figure out if it is the source or > > the destination address that fails? > > > > Looks like your system has started bouncing data to the 32-bit address range. > > > > I can reproduce an error like it whenever I use DMA on umass device - The error > somehow are triggered/created by the multiport patches that was introduced > in the ATA framework back in April - For a long time I believed it was an error > in the ATA frame work until I discovered that If I disabled the umass device > the error disappered > > I am using ZFS on both devices. If I change to usb2_ata the problem disappers. > I think that is because usb2_ata does not use DMA. > > I believe the problem is related to the DMA handling in the umass > > see attached fault - In short the problem has been around for a long time > but it seems to be related to the USB stack DMA handling - before usb2 > it showed up as a DMA error in the ATA driver - but that was because > the old umass driver somehow "stole" an active DMA > > {gigantic snip} Check out this thread, which includes patches: http://lists.freebsd.org/pipermail/freebsd-current/2008-November/thread.html#220 http://lists.freebsd.org/pipermail/freebsd-current/2008-November/000220.html -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From keramida at ceid.upatras.gr Fri Nov 7 14:24:07 2008 From: keramida at ceid.upatras.gr (Giorgos Keramidas) Date: Fri Nov 7 14:24:15 2008 Subject: Recent USB mouse regression Message-ID: <8763mz2n0m.fsf@kobe.laptop> A recent 8.0-CURRENT installation _without_ USB2 enabled or loaded from `loader.conf' seems to have regressed a bit from a couple of weeks ago. When I attach an old wired mouse I have at home: ums0: on uhub4 ums0: 3 buttons and Z dir. and run moused in debugging mode I can see mouse clicks being handled, but mouse movement `dies' after a bit of time. Pressing one of the mouse buttons generates moused events like: moused: received char 0x83 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x7f moused: assembled full packet (len 8) 83,0,0,0,0,0,0,7f moused: ts: 3708 752982137 moused: : 3649 133538726 moused: flags:00000001 buttons:00000001 obuttons:00000000 moused: activity : buttons 0x00000001 dx 0 dy 0 dz 0 moused: mstate[0]->count:1 moused: button 1 count 1 moused: received char 0x87 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x7f moused: assembled full packet (len 8) 87,0,0,0,0,0,0,7f moused: ts: 3708 859980149 moused: flags:00000001 buttons:00000000 obuttons:00000001 moused: activity : buttons 0x00000000 dx 0 dy 0 dz 0 moused: mstate[0]->count:1 moused: button 1 count 0 but moving the mouse doesn't show anything in the log of moused, as if the movement event were never delivered by the USB stack to `/dev/ums0'. Some times moused starts receiving movement events for 1-2 seconds and then they are gone again. One of the ways I can reliably get the mouse in a `dead' state is by typing in an xterm window. When xterm hides the mouse pointer of X11, mouse movement is gone for good. A second mouse -- a wireless Microsoft mouse -- attaches as ums0 but never delivers anything to moused: root: Unknown USB device: vendor 0x045e product 0x00e1 bus uhub4 kernel: ums0: on uhub4 kernel: ums0: 5 buttons and Z dir. Both of these used to work a couple of weeks ago, and I'm looking back through history to find out when this started. Is anyone else seeing something like this? From max at love2party.net Fri Nov 7 15:04:13 2008 From: max at love2party.net (Max Laier) Date: Fri Nov 7 15:04:20 2008 Subject: Cannot buildworld in CURRENT In-Reply-To: <49140904.6080002@lissyara.su> References: <49135844.7010500@lissyara.su> <87bpwsseof.fsf@kobe.laptop> <49140904.6080002@lissyara.su> Message-ID: <200811080004.09597.max@love2party.net> On Friday 07 November 2008 10:23:16 Alex Keda wrote: > Giorgos Keramidas ?????: > > On Thu, 06 Nov 2008 23:51:25 +0300, Alex Keda wrote: > >> Alex Keda ?????: > >>> ===> usr.bin/du (all) > >>> cc -O2 -pipe -fstack-protector -Wsystem-headers -Werror -Wall > >>> -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes > >>> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > >>> -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter > >>> -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls > >>> -Wno-pointer-sign -c /usr/src/usr.bin/du/du.c > >>> cc1: warnings being treated as errors > >>> /usr/src/usr.bin/du/du.c: In function 'main': > >>> /usr/src/usr.bin/du/du.c:276: warning: format '%jd' expects type > >>> intmax_t', but argument 2 has type 'long long int' > >>> *** Error code 1 > >>> > >>> Stop in /usr/src/usr.bin/du. > >>> *** Error code 1 > > Oops, this one slipped in because I only built in i386 and not amd64. Not Giorgos' fault ... I did the commit and I should have checked that it builds properly. > another machine. Build success. Updated 2 hour ago... > You commit this patch? =) I committed a fix in r184742. Sorry for the breakage. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From koitsu at FreeBSD.org Fri Nov 7 16:11:30 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Nov 7 16:11:38 2008 Subject: Kernel panic when copying data to umass device (USB4BSD) - problem found In-Reply-To: <200811071811.27181.hselasky@c2i.net> References: <20081107082740.GA1334@icarus.home.lan> <200811071811.27181.hselasky@c2i.net> Message-ID: <20081108001128.GA1437@icarus.home.lan> On Fri, Nov 07, 2008 at 06:11:26PM +0100, Hans Petter Selasky wrote: > On Friday 07 November 2008, Jeremy Chadwick wrote: > > Not sure if this is caused by problems with USB4BSD or not, as I can > > reproduce it on RELENG_7 (but there, the kernel does not panic; it just > > "wedges" in a loop/thread somewhere; SSH sessions remain up, but > > commands running stop; hitting Ctrl-T shows them in all sorts of > > different states, but the states never change; hitting Ctrl-Alt-Esc does > > in fact drop me to db>). > > Hi Jeremy, > > I've reproduced the issue with some mods to the usb2_busdma.c on 32-bit > arcitecture and have made a fix for this problem. > > Try the following patch and re-test! Some mem-stick benchmarks would be > nice ... > > My private SVN also has this patch in addition to P4. Hans, To answer your question in your other mail: yes, this is on an amd64 machine with 4GB of RAM installed. With the patch to usb2_busdma applied, the problem is fixed! Thank you very, very much. As far as benchmarks: I'll keep it simple and try different block sizes. Numbers are compared against a Windows XP machine using the ATTO Benchmarking tool (which uses direct I/O read/writes, not filesystem I/O). Preface facts: - Testing done against SanDisk Cruzer Micro 8GB (SDCZ6-8192RB) - USB 2.0 bus used exclusively on both FreeBSD and Windows - Write caching disabled for USB drives on Windows XP - MD5 tests done against 7.1-BETA2-amd64-disc1.iso (573087744 bytes) - MD5 checksums matched source -- no corruption found on Windows or FreeBSD Software details: - ATTO Disk Benchmark v2.34 - ATTO configuration: Direct I/O, "Neither" type selected (vs. queued/overlapped I/O); data length size = 512MB - All FreeBSD tests done with HPS's busdma patches applied - dd read command: dd if=/dev/zero of=/dev/da0 bs= - dd write command: dd if=/dev/da0 of=/dev/null bs= - md5 command: time md5 7.1-BETA2-amd64-disc1.iso - FreeBSD filesystem: UFS1 (16KB blocks), using da0s1 directly - Windows filesystem: FAT32 (4KB blocks) Read Write --------- --------- Windows ATTO (4KB) 6.87MB/s 1.25MB/s Windows ATTO (8KB) 11.32MB/s 2.38MB/s Windows ATTO (16KB) 17.65MB/s 3.61MB/s Windows ATTO (32KB) 24.24MB/s 4.06MB/s Windows ATTO (64KB) 29.30MB/s 8.17MB/s Windows ATTO (128KB) 29.49MB/s 7.74MB/s Windows md5 2.38 sec n/a --------------------- USB4BSD dd (4KB) 6.72MB/s 1.55MB/s ** USB4BSD dd (8KB) 12.32MB/s 2.44MB/s USB4BSD dd (16KB) 18.45MB/s 3.59MB/s USB4BSD dd (32KB) 23.88MB/s 4.24MB/s USB4BSD dd (64KB) 29.32MB/s 8.90MB/s ** USB4BSD dd (128KB) 29.58MB/s 9.00MB/s ** FreeBSD md5 2.51 sec n/a ** Write speed gradually increased as transfer took place, topping out at the value shown; there was occasionally some variance in the transfer speed, so it wasn't a pure linear ramp-up. Points of interest: - FreeBSD and Windows have about equal read performance, but FreeBSD has slightly higher write performance - Mysterious "gradually increasing speed" with some block sizes - Jump in write performance with 64KB blocks (firmware optimisation?) - Slower write performance on Windows with 128KB blocks (I thought I was going crazy, but I tested this numerous times) To be brutally honest, I was expecting FreeBSD to perform badly during both read and write operations -- I was delightfully surprised to see the above. :-) I have a newer USB flash disk (SanDisk Cruzer Titanium 8GB) arriving early next week, so I can try that one out for comparison. SanDisk is known for tinkering with r/w optimisations in their firmwares. Cheers! -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From keramida at ceid.upatras.gr Fri Nov 7 18:24:42 2008 From: keramida at ceid.upatras.gr (Giorgos Keramidas) Date: Fri Nov 7 18:24:48 2008 Subject: Recent USB mouse regression In-Reply-To: <8763mz2n0m.fsf@kobe.laptop> (Giorgos Keramidas's message of "Sat, 08 Nov 2008 00:23:53 +0200") References: <8763mz2n0m.fsf@kobe.laptop> Message-ID: <87bpwrneeh.fsf@kobe.laptop> Building a kernel & userland just before USB2 from svn change 184609 seems to have fixed this for now. It seems that even when USB2 is not loaded it affects a bit the way ums(4) works. What is the best way of troubleshooting this? On Sat, 08 Nov 2008 00:23:53 +0200, Giorgos Keramidas wrote: > A recent 8.0-CURRENT installation _without_ USB2 enabled or loaded from > `loader.conf' seems to have regressed a bit from a couple of weeks ago. > > When I attach an old wired mouse I have at home: > > ums0: on uhub4 > ums0: 3 buttons and Z dir. > > and run moused in debugging mode I can see mouse clicks being handled, > but mouse movement `dies' after a bit of time. Pressing one of the > mouse buttons generates moused events like: > > moused: received char 0x83 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x7f > moused: assembled full packet (len 8) 83,0,0,0,0,0,0,7f > moused: ts: 3708 752982137 > moused: : 3649 133538726 > moused: flags:00000001 buttons:00000001 obuttons:00000000 > moused: activity : buttons 0x00000001 dx 0 dy 0 dz 0 > moused: mstate[0]->count:1 > moused: button 1 count 1 > moused: received char 0x87 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x0 > moused: received char 0x7f > moused: assembled full packet (len 8) 87,0,0,0,0,0,0,7f > moused: ts: 3708 859980149 > moused: flags:00000001 buttons:00000000 obuttons:00000001 > moused: activity : buttons 0x00000000 dx 0 dy 0 dz 0 > moused: mstate[0]->count:1 > moused: button 1 count 0 > > but moving the mouse doesn't show anything in the log of moused, as if > the movement event were never delivered by the USB stack to `/dev/ums0'. > > Some times moused starts receiving movement events for 1-2 seconds and > then they are gone again. > > One of the ways I can reliably get the mouse in a `dead' state is by > typing in an xterm window. When xterm hides the mouse pointer of X11, > mouse movement is gone for good. > > A second mouse -- a wireless Microsoft mouse -- attaches as ums0 but > never delivers anything to moused: > > root: Unknown USB device: vendor 0x045e product 0x00e1 bus uhub4 > kernel: ums0: on uhub4 > kernel: ums0: 5 buttons and Z dir. > > Both of these used to work a couple of weeks ago, and I'm looking back > through history to find out when this started. > > Is anyone else seeing something like this? From shuvaev at physik.uni-wuerzburg.de Fri Nov 7 18:53:22 2008 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Fri Nov 7 18:53:30 2008 Subject: Recent USB mouse regression In-Reply-To: <87bpwrneeh.fsf@kobe.laptop> References: <8763mz2n0m.fsf@kobe.laptop> <87bpwrneeh.fsf@kobe.laptop> Message-ID: <20081108025317.GA29344@localhost.my.domain> On Sat, Nov 08, 2008 at 04:24:22AM +0200, Giorgos Keramidas wrote: > Building a kernel & userland just before USB2 from svn change 184609 > seems to have fixed this for now. It seems that even when USB2 is not > loaded it affects a bit the way ums(4) works. > > What is the best way of troubleshooting this? > I have seen reversed situation when even with usb2_input_ms kld loaded I am finding ums + usb (old stack) in kldstat after the system goes multiuser. I would check kldstat after each event (today klds are loaded automatically!) and try operate in single user mode first. Could it be that something (moused) is trying to load all klds matching some symbols (provided interfaces)? Just my $0.02, Alexey. > On Sat, 08 Nov 2008 00:23:53 +0200, Giorgos Keramidas wrote: > > A recent 8.0-CURRENT installation _without_ USB2 enabled or loaded from > > `loader.conf' seems to have regressed a bit from a couple of weeks ago. > > > > When I attach an old wired mouse I have at home: > > > > ums0: on uhub4 > > ums0: 3 buttons and Z dir. > > > > and run moused in debugging mode I can see mouse clicks being handled, > > but mouse movement `dies' after a bit of time. Pressing one of the > > mouse buttons generates moused events like: > > > > moused: received char 0x83 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x7f > > moused: assembled full packet (len 8) 83,0,0,0,0,0,0,7f > > moused: ts: 3708 752982137 > > moused: : 3649 133538726 > > moused: flags:00000001 buttons:00000001 obuttons:00000000 > > moused: activity : buttons 0x00000001 dx 0 dy 0 dz 0 > > moused: mstate[0]->count:1 > > moused: button 1 count 1 > > moused: received char 0x87 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x0 > > moused: received char 0x7f > > moused: assembled full packet (len 8) 87,0,0,0,0,0,0,7f > > moused: ts: 3708 859980149 > > moused: flags:00000001 buttons:00000000 obuttons:00000001 > > moused: activity : buttons 0x00000000 dx 0 dy 0 dz 0 > > moused: mstate[0]->count:1 > > moused: button 1 count 0 > > > > but moving the mouse doesn't show anything in the log of moused, as if > > the movement event were never delivered by the USB stack to `/dev/ums0'. > > > > Some times moused starts receiving movement events for 1-2 seconds and > > then they are gone again. > > > > One of the ways I can reliably get the mouse in a `dead' state is by > > typing in an xterm window. When xterm hides the mouse pointer of X11, > > mouse movement is gone for good. > > > > A second mouse -- a wireless Microsoft mouse -- attaches as ums0 but > > never delivers anything to moused: > > > > root: Unknown USB device: vendor 0x045e product 0x00e1 bus uhub4 > > kernel: ums0: on uhub4 > > kernel: ums0: 5 buttons and Z dir. > > > > Both of these used to work a couple of weeks ago, and I'm looking back > > through history to find out when this started. > > > > Is anyone else seeing something like this? > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From keramida at ceid.upatras.gr Fri Nov 7 19:07:13 2008 From: keramida at ceid.upatras.gr (Giorgos Keramidas) Date: Fri Nov 7 19:07:19 2008 Subject: Recent USB mouse regression In-Reply-To: <20081108025317.GA29344@localhost.my.domain> (Alexey Shuvaev's message of "Sat, 8 Nov 2008 03:53:17 +0100") References: <8763mz2n0m.fsf@kobe.laptop> <87bpwrneeh.fsf@kobe.laptop> <20081108025317.GA29344@localhost.my.domain> Message-ID: <87skq2ncfc.fsf@kobe.laptop> On Sat, 8 Nov 2008 03:53:17 +0100, Alexey Shuvaev wrote: > On Sat, Nov 08, 2008 at 04:24:22AM +0200, Giorgos Keramidas wrote: >> Building a kernel & userland just before USB2 from svn change 184609 >> seems to have fixed this for now. It seems that even when USB2 is not >> loaded it affects a bit the way ums(4) works. >> >> What is the best way of troubleshooting this? > > I have seen reversed situation when even with usb2_input_ms kld loaded > I am finding ums + usb (old stack) in kldstat after the system goes > multiuser. I would check kldstat after each event (today klds are > loaded automatically!) and try operate in single user mode first. > Could it be that something (moused) is trying to load all klds > matching some symbols (provided interfaces)? My kernel config file is based on GENERIC, so `ums' is not a module and I don't load any usb2_xxx modules in my `loader.conf' yet. Should I rebuild it as a module? I can try that later... I just started a buildworld with all the changes up the HEAD except for the five commits that are related to usb2, i.e. I have everything else up to svn /head@184743 but I have backed out locally the changes: ------------------------------------------------------------------------ r184610 | alfred | 2008-11-04 04:31:03 +0200 (Tue, 04 Nov 2008) | 123 lines r184612 | alfred | 2008-11-04 05:42:01 +0200 (Tue, 04 Nov 2008) | 2 lines r184658 | rink | 2008-11-04 21:28:19 +0200 (Tue, 04 Nov 2008) | 4 lines r184659 | rink | 2008-11-04 22:57:39 +0200 (Tue, 04 Nov 2008) | 7 lines r184736 | imp | 2008-11-06 19:26:12 +0200 (Thu, 06 Nov 2008) | 4 lines ------------------------------------------------------------------------ These are the commits that I could see affecting sys/usb2 so far, so it may help find out that it is indeed usb2 that causes ums(4) to act oddly. If this fails, I'll remerge the usb2 changes, and try building ums as a module-only. From keramida at ceid.upatras.gr Fri Nov 7 19:10:16 2008 From: keramida at ceid.upatras.gr (Giorgos Keramidas) Date: Fri Nov 7 19:10:23 2008 Subject: Recent USB mouse regression In-Reply-To: <87skq2ncfc.fsf@kobe.laptop> (Giorgos Keramidas's message of "Sat, 08 Nov 2008 05:07:03 +0200") References: <8763mz2n0m.fsf@kobe.laptop> <87bpwrneeh.fsf@kobe.laptop> <20081108025317.GA29344@localhost.my.domain> <87skq2ncfc.fsf@kobe.laptop> Message-ID: <87od0qkj5b.fsf@kobe.laptop> On Sat, 08 Nov 2008 05:07:03 +0200, Giorgos Keramidas wrote: > I just started a buildworld with all the changes up the HEAD except for > the five commits that are related to usb2, i.e. I have everything else > up to svn /head@184743 but I have backed out locally the changes: > > ------------------------------------------------------------------------ > r184610 | alfred | 2008-11-04 04:31:03 +0200 (Tue, 04 Nov 2008) | 123 lines > r184612 | alfred | 2008-11-04 05:42:01 +0200 (Tue, 04 Nov 2008) | 2 lines > r184658 | rink | 2008-11-04 21:28:19 +0200 (Tue, 04 Nov 2008) | 4 lines > r184659 | rink | 2008-11-04 22:57:39 +0200 (Tue, 04 Nov 2008) | 7 lines > r184736 | imp | 2008-11-06 19:26:12 +0200 (Thu, 06 Nov 2008) | 4 lines > ------------------------------------------------------------------------ Nope, that's not it. I just had the same problem with a kernel+world from /head@184607. I'll keep looking for the first time this started happening. For now, I think it's safe to assume it's not USB2 :) From vermaden at interia.pl Fri Nov 7 17:47:13 2008 From: vermaden at interia.pl (vermaden) Date: Fri Nov 7 20:52:41 2008 Subject: sysctl debug.cpufreq.highest Message-ID: <20081108012734.3274F1E3055@f03.poczta.interia.pl> Hi, Currently there is possibility to set lowest speed of cpu for scaling with cpufreq (debug.cpufreq.lowest), it would be good to include also a option to set the highest possible freq to use with cpufreq, some laptops get too hot and/or consume too much power when running on maximum power/speed of cpu. Regards vermaden ---------------------------------------------------------------------- Dzwon taniej na zagraniczne komorki! Sprawdz >> http://link.interia.pl/f1f6a From pyunyh at gmail.com Fri Nov 7 21:25:32 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Fri Nov 7 21:25:40 2008 Subject: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet In-Reply-To: <20081107064724.GA11486@cdnetworks.co.kr> References: <20081030040637.GA78796@cdnetworks.co.kr> <20081030114845.GE78796@cdnetworks.co.kr> <20081031034443.GF82781@cdnetworks.co.kr> <20081107064724.GA11486@cdnetworks.co.kr> Message-ID: <20081108052324.GD14970@cdnetworks.co.kr> On Fri, Nov 07, 2008 at 03:47:24PM +0900, To freebsd-current@FreeBSD.org wrote: > On Fri, Oct 31, 2008 at 12:44:43PM +0900, To freebsd-current@FreeBSD.org wrote: > > On Thu, Oct 30, 2008 at 08:48:45PM +0900, To freebsd-current@FreeBSD.org wrote: > > > On Thu, Oct 30, 2008 at 01:06:37PM +0900, To freebsd-current@FreeBSD.org wrote: > > > > > > > > Hi, > > > > > > > > I had been working on writing a driver for Atheros AR8121(L1E), > > > > AR8113/AR8114(L2E) ethernet controllers since Jeremy Chadwick sent > > > > the hardware to me. I think it's feature complete state and time > > > > for more testing for stability or some edge cases. I guess AR81xx > > > > is commonly found on newer Asus EeePC or P5Q series of Asus > > > > motherboard. If you have AR81xx controller would you give it spin > > > > and let me know how it goes? You can get the latest driver at the > > > > following URL. > > > > http://people.freebsd.org/~yongari/ate/if_ate.c > > > > http://people.freebsd.org/~yongari/ate/if_atereg.h > > > > http://people.freebsd.org/~yongari/ate/if_atevar.h > > > > http://people.freebsd.org/~yongari/ate/Makefile > > > > or > > > > http://people.freebsd.org/~yongari/ate/ate.20081030.tar.gz > > > > The driver should build without problems on CURRENT, stable/7. > > > > > > > > ATM the driver supports the following hardware features. > > > > - TSO > > > > - Rx TCP/UDP/IP checksum offload > > > > - VLAN tag insertion/stripping > > > > - Jumbo frame > > > > - WOL > > > > It seems that hardware supports Tx checksum offload but I couldn't > > > > make it work for TCP segments. Only short TCP segments seem to work > > > > so I disabled Tx checksum offload. > > > > Note, the hardware does not support descriptor based DMA on Rx side > > > > so driver have to copy recevied frames to pass them to upper stack > > > > so it will consume a lot of CPU cycles if you push the hardware to > > > > the limit. > > > > > > > > > > As bruffer pointed out the device name chosen conflicts with other > > > driver in tree so I renamed it to ale(4).The URL for the driver is > > > http://people.freebsd.org/~yongari/ale/if_ale.c > > > http://people.freebsd.org/~yongari/ale/if_alereg.h > > > http://people.freebsd.org/~yongari/ale/if_alevar.h > > > http://people.freebsd.org/~yongari/ale/Makefile > > > or > > > http://people.freebsd.org/~yongari/ale/ale.20081030.tar.gz > > > Sorry for confusion. > > > > > > > FYI: > > There was a typo that keep ale(4) from building on stable/7. It was > > fixed now and I reuploaded related files(URLs are the same as before). > > Finally I've managed to make Tx checksum offload work and added one > more workaround for silicon bug. As usual updated ale(4) can be > found at the following URL. > > http://people.freebsd.org/~yongari/ale/if_ale.c > http://people.freebsd.org/~yongari/ale/if_alereg.h > http://people.freebsd.org/~yongari/ale/if_alevar.h > http://people.freebsd.org/~yongari/ale/Makefile > or > http://people.freebsd.org/~yongari/ale/ale.20081107.tar.gz > > The workaround takes more CPU cycles than previous one but you can > still saturate the link if you have fast CPU. I'll commit this > version within a week unless severe issues are reported. > One user reported non-working NFS over UDP and I disabled Rx checksum offload as AR81xx hardware is not able to handle fragmented IP datagrams correctly. So it's highly recommended to disable Rx checksum offload or use the following updated files. http://people.freebsd.org/~yongari/ale/ale.20081108.tar.gz -- Regards, Pyun YongHyeon From rmgls at free.fr Fri Nov 7 23:28:03 2008 From: rmgls at free.fr (Raoul) Date: Fri Nov 7 23:28:11 2008 Subject: usb2_sound behaviour Message-ID: <20081108070119.170A319758@smtp6-g19.free.fr> Hi all, usb2_sound does not detect an mbox (Digidesign) usb sound box. world and kernel are all from this night. as you can see the box is detected by snd_uaudio, but not by usb2_sound. of course the box does not work at all even well detected by snd_uaudio, perhaps this will come later. i point out the detection problem at this moment. hope this serve best regards Raoul rmgls@free.fr -----------cut----------- usb2_sound_load="YEs" reboot kldstat: Id Refs Address Size Name 1 40 0xc0400000 bff630 kernel (/boot/kernel/kernel) 2 1 0xc1000000 2bdbc linux.ko (/boot/kernel/linux.ko) 3 1 0xc102c000 106dc if_iwi.ko (/boot/kernel/if_iwi.ko) 4 1 0xc103d000 2848 acpi_sony.ko (/boot/kernel/acpi_sony.ko) 5 1 0xc1040000 e15c usb2_sound.ko (/boot/kernel/usb2_sound.ko) 6 3 0xc104f000 52bb0 sound.ko (/boot/kernel/sound.ko) 7 3 0xc10a2000 3be58 usb2_core.ko (/boot/kernel/usb2_core.ko) 8 6 0xc10de000 e9fc netgraph.ko (/boot/kernel/netgraph.ko) 9 1 0xc10ed000 9bd4 ng_ubt.ko (/boot/kernel/ng_ubt.ko) 10 4 0xc53cb000 2000 ng_bluetooth.ko (/boot/kernel/ng_bluetooth.ko) 11 1 0xc53cd000 d000 ng_hci.ko (/boot/kernel/ng_hci.ko) 12 1 0xc545a000 10000 ng_l2cap.ko (/boot/kernel/ng_l2cap.ko) 13 1 0xc546c000 22000 ng_btsocket.ko (/boot/kernel/ng_btsocket.ko) 14 1 0xc5499000 4000 ng_socket.ko (/boot/kernel/ng_socket.ko) mbox2 connected in the usb port: ugen0: on uhub1 kldunload usb2_sound kldunload usb2_core kldunload sound kldload snd_uaudio Id Refs Address Size Name ... 15 1 0xc6232000 a000 snd_uaudio.ko (/boot/kernel/snd_uaudio.ko) 16 1 0xc623c000 47000 sound.ko (/boot/kernel/sound.ko) mbox insertion => dmesg: uaudio0: on uhub1 uaudio0: ignored audio interface with 2 endpoints uaudio0: ignored audio interface with 2 endpoints uaudio0: ignored audio interface with 2 endpoints uaudio0: ignored audio interface with 2 endpoints uaudio0: ignored setting with type 8193 format uaudio0: audio rev 1.00 uaudio0: 0 mixer controls pcm0: on uaudio0 pcm0: USB Audio: vendor=0x0dba, product=0x3000, release=0x0138 pcm0: using a default buffer size of 16384 pcm0: Mixer "vol" -> "none": child=0x00000010 pcm0: Mixer "pcm": parent="vol" pcm0: Soft PCM mixer ENABLED uaudio0: uaudio_query_formats: found a native record channel (stereo) continous min 8000 max 48000 24bit 3bytes/subframe X 2 channels = 6 bytes per sample uaudio0: uaudio_query_formats: found a native record channel (stereo) continous min 8000 max 48000 24bit 3bytes/subframe X 2 channels = 6 bytes per sample uaudio0: uaudio_query_formats: found a native record channel (stereo) continous min 8000 max 48000 24bit 3bytes/subframe X 2 channels = 6 bytes per sample uaudio0: uaudio_query_formats: found a native record channel (stereo) continous min 8000 max 48000 24bit 3bytes/subframe X 2 channels = 6 bytes per sample pcm0: clone manager: deadline=750ms flags=0x8000001e uaudio0: rec buf 0xc6294000 ----------cut---------- From pyunyh at gmail.com Sat Nov 8 00:01:44 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Sat Nov 8 00:01:51 2008 Subject: Call for testers: fxp(4) WOL In-Reply-To: <20081107194844.GA55053@localhost.my.domain> References: <20081015003745.GG14769@cdnetworks.co.kr> <20081103183556.GA2009@localhost.my.domain> <20081104014246.GA98154@cdnetworks.co.kr> <20081107194844.GA55053@localhost.my.domain> Message-ID: <20081108075929.GE14970@cdnetworks.co.kr> On Fri, Nov 07, 2008 at 08:48:44PM +0100, Alexey Shuvaev wrote: > On Tue, Nov 04, 2008 at 10:42:46AM +0900, Pyun YongHyeon wrote: > > On Mon, Nov 03, 2008 at 07:35:56PM +0100, Alexey Shuvaev wrote: > > > Here are relevant messages from the verbose boot: > > > > > > fxp0: port 0xdf40-0xdf7f mem 0xfceff000-0xfcefffff irq 11 at device 8.0 on pci2 > > > > If it's based on ICH controller it would be 82559. > > > > > fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfceff000 > > > fxp0: using memory space register mapping > > > fxp0: PCI IDs: 8086 1031 1179 0001 0042 > > > fxp0: Dynamic Standby mode is disabled > > > miibus0: on fxp0 > > > fxp0: XXX: driver didn't set ifq_maxlen > > > ^^^ > > > Is this something to fix? > > > > > > > fxp(4) didn't set ifq_maxlen and if_attach corrected this with > > its default value. Normally network device drivers set this queue > > length to number of Tx descriptors but it's completely up to > > driver writers and I don't see compeling reason to change that. > > > Ok, I just was attracted by something with 'XXX'. > > > > However the system seems to honors only the BIOS settings, if I enable WOL in > > > the BIOS the system wakes up from power-down or suspend (to ram) states > > > regardless of fxp settings and with disabled WOL in BIOS it never > > > wakes up. > > > > > > > Yes that's an expected behaviour. BIOS option should be changed to > > enable WOL if you want to wake up your box from power down. If > > you don't want to wake up your box regardless of BIOS configuration > > you have to disable WOL with ifconfig before shutting down your > > box. Likewise even if you enable WOL with ifconfig(8) to wake up > > your system, BIOS WOL option also should be enabled to make it > > work. > > > > > The worse thing I have noticed is if I send WOL packet while the system is > > > running it reliably hangs. It does not panic and switching virtual > > > consoles works (and typing/deleting something in the shell prompt too), > > > but the cooler runs at full power and you can't do anything else. > > > This is both with patched fxp and that from -CURRENT. > > > > Hmm, I think that was old bebahviour of stock fxp(4). Previously > > fxp(4) was programmed to accept WOL packets regardless of running > > state of hardware. With my patch the WOL should be disabled for > > normal operation and WOL is enabled again when you shutdown your > > box. If sotck fxp(4) also show the same behaviour it's big security > > hole. > > ATM I have no idea how WOL packets can affect running box. :-( > > > I have tested more thoroughly and here are the results. > > FreeBSD-CURRENT (late oktober) without your patch > (is it what you call 'stock'?): Yes. > interface up or down, WOL disabled or enabled in the BIOS - > system hangs when receiving WOL packet. > Breaking to debugger shows kernel running, namely 3 acpi threads, > acpi_task_[0-2]. This is critical issue, your box is vulnerable to WOL attack. > FreeBSD-CURRENT from 4 Nov 2008 with your patch: > again, with WOL enabled in BIOS or not, system hangs with WOL packet, > but only if interface is down. > With interface (fxp0) up and running, nothing happens. > However, I failed to disable WOL with ifconfig, notebook boots > always when WOL enabled in the BIOS. Maybe BIOS doesn't honor preprogrammed PCI configuration data? Or the reset command in fxp_stop() might cleared some important configuration data. > Linux-Ubuntu uname: Linux ubuntu 2.6.22-14-generic #1 SMP > Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux (booted live from CD) > The same results as with FreeBSD-CURRENT with your patch. > Disabling wol with ethtool does not produce the desired results. > Receiving WOL packet when interface is down does not hang the system, > but it (according to top) consumes 70% in system with > kacpid process consuming 98.5% of cpu. > Thanks a lot for your testing! > > Thanks for testing. I'll think again. > > By chance can you try Linux on your system and check whether it > > works? > > > So, it seems your patch is making FreeBSD on par with Linux. > If you need something more, you are welcome! I still have no clue yet but would you try attached one after backing out previous patch? -- Regards, Pyun YongHyeon -------------- next part -------------- Index: sys/dev/fxp/if_fxp.c =================================================================== --- sys/dev/fxp/if_fxp.c (revision 184742) +++ sys/dev/fxp/if_fxp.c (working copy) @@ -402,7 +402,7 @@ uint32_t val; uint16_t data, myea[ETHER_ADDR_LEN / 2]; u_char eaddr[ETHER_ADDR_LEN]; - int i, prefer_iomap; + int i, pmc, prefer_iomap; int error; error = 0; @@ -480,6 +480,16 @@ sc->revision = pci_get_revid(dev); /* + * Check availability of WOL. + */ + if (sc->revision >= FXP_REV_82558_A4) { + fxp_read_eeprom(sc, &data, 10, 1); + if ((data & 0x20) != 0 && + pci_find_extcap(sc->dev, PCIY_PMG, &pmc) == 0) + sc->flags |= FXP_FLAG_WOLCAP; + } + + /* * Determine whether we must use the 503 serial interface. */ fxp_read_eeprom(sc, &data, 6, 1); @@ -778,6 +788,11 @@ ifp->if_capenable |= IFCAP_HWCSUM; } + if (sc->flags & FXP_FLAG_WOLCAP) { + ifp->if_capabilities |= IFCAP_WOL_MAGIC; + ifp->if_capenable |= IFCAP_WOL_MAGIC; + } + #ifdef DEVICE_POLLING /* Inform the world we support polling. */ ifp->if_capabilities |= IFCAP_POLLING; @@ -938,17 +953,13 @@ static int fxp_shutdown(device_t dev) { - struct fxp_softc *sc = device_get_softc(dev); /* * Make sure that DMA is disabled prior to reboot. Not doing * do could allow DMA to corrupt kernel memory during the * reboot before the driver initializes. */ - FXP_LOCK(sc); - fxp_stop(sc); - FXP_UNLOCK(sc); - return (0); + return (fxp_suspend(dev)); } /* @@ -960,11 +971,27 @@ fxp_suspend(device_t dev) { struct fxp_softc *sc = device_get_softc(dev); + struct ifnet *ifp; + int pmc; + uint16_t pmstat; FXP_LOCK(sc); + ifp = sc->ifp; + if (pci_find_extcap(sc->dev, PCIY_PMG, &pmc) == 0) { + pmstat = pci_read_config(sc->dev, pmc + PCIR_POWER_STATUS, 2); + pmstat &= ~(PCIM_PSTAT_PME | PCIM_PSTAT_PMEENABLE); + if ((ifp->if_capenable & IFCAP_WOL_MAGIC) != 0) { + /* Request PME. */ + pmstat |= PCIM_PSTAT_PME | PCIM_PSTAT_PMEENABLE; + sc->flags |= FXP_FLAG_WOL; + /* Reconfigure hardware to accept magic frames. */ + fxp_init_body(sc); + } + pci_write_config(sc->dev, pmc + PCIR_POWER_STATUS, pmstat, 2); + } fxp_stop(sc); - + sc->suspended = 1; FXP_UNLOCK(sc); @@ -980,9 +1007,23 @@ { struct fxp_softc *sc = device_get_softc(dev); struct ifnet *ifp = sc->ifp; + int pmc; + uint16_t pmstat; FXP_LOCK(sc); + if (pci_find_extcap(sc->dev, PCIY_PMG, &pmc) == 0) { + sc->flags &= ~FXP_FLAG_WOL; + pmstat = pci_read_config(sc->dev, pmc + PCIR_POWER_STATUS, 2); + /* Disable PME and clear PME status. */ + pmstat &= ~PCIM_PSTAT_PMEENABLE; + pci_write_config(sc->dev, pmc + PCIR_POWER_STATUS, pmstat, 2); + if ((sc->flags & FXP_FLAG_WOL) != 0) { + /* Clear wakeup events. */ + CSR_READ_1(sc, FXP_CSR_PMDR); + } + } + CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SELECTIVE_RESET); DELAY(10); @@ -1848,11 +1889,13 @@ callout_stop(&sc->stat_ch); /* - * Issue software reset, which also unloads the microcode. + * Preserve PCI configuration, configure, IA/multicast + * setup and put RU and CU into idle state. */ - sc->flags &= ~FXP_FLAG_UCODE; - CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SOFTWARE_RESET); + CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SELECTIVE_RESET); DELAY(50); + /* Disable interrupts. */ + CSR_WRITE_1(sc, FXP_CSR_SCB_INTRCNTL, FXP_SCB_INTR_DISABLE); /* * Release any xmit buffers. @@ -1932,6 +1975,13 @@ */ fxp_stop(sc); + /* + * Issue software reset, which also unloads the microcode. + */ + sc->flags &= ~FXP_FLAG_UCODE; + CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SOFTWARE_RESET); + DELAY(50); + prm = (ifp->if_flags & IFF_PROMISC) ? 1 : 0; /* @@ -2047,8 +2097,7 @@ cbp->rcv_crc_xfer = 0; /* (don't) xfer CRC to host */ cbp->long_rx_en = sc->flags & FXP_FLAG_LONG_PKT_EN ? 1 : 0; cbp->ia_wake_en = 0; /* (don't) wake up on address match */ - cbp->magic_pkt_dis = 0; /* (don't) disable magic packet */ - /* must set wake_en in PMCSR also */ + cbp->magic_pkt_dis = sc->flags & FXP_FLAG_WOL ? 0 : 1; cbp->force_fdx = 0; /* (don't) force full duplex */ cbp->fdx_pin_en = 1; /* (enable) FDX# pin */ cbp->multi_ia = 0; /* (don't) accept multiple IAs */ @@ -2458,6 +2507,10 @@ } } #endif + if ((mask & IFCAP_WOL_MAGIC) != 0 && + (ifp->if_capabilities & IFCAP_WOL_MAGIC) != 0) + ifp->if_capenable ^= IFCAP_WOL_MAGIC; + if (mask & IFCAP_VLAN_MTU) { FXP_LOCK(sc); ifp->if_capenable ^= IFCAP_VLAN_MTU; Index: sys/dev/fxp/if_fxpreg.h =================================================================== --- sys/dev/fxp/if_fxpreg.h (revision 184742) +++ sys/dev/fxp/if_fxpreg.h (working copy) @@ -46,6 +46,7 @@ #define FXP_CSR_EEPROMCONTROL 14 /* eeprom control (2 bytes) */ #define FXP_CSR_MDICONTROL 16 /* mdi control (4 bytes) */ #define FXP_CSR_FLOWCONTROL 0x19 /* flow control (2 bytes) */ +#define FXP_CSR_PMDR 0x1B /* power management driver (1 byte) */ #define FXP_CSR_GENCONTROL 0x1C /* general control (1 byte) */ /* Index: sys/dev/fxp/if_fxpvar.h =================================================================== --- sys/dev/fxp/if_fxpvar.h (revision 184742) +++ sys/dev/fxp/if_fxpvar.h (working copy) @@ -193,6 +193,8 @@ #define FXP_FLAG_DEFERRED_RNR 0x0200 /* DEVICE_POLLING deferred RNR */ #define FXP_FLAG_EXT_RFA 0x0400 /* extended RFDs for csum offload */ #define FXP_FLAG_SAVE_BAD 0x0800 /* save bad pkts: bad size, CRC, etc */ +#define FXP_FLAG_WOLCAP 0x1000