Re: msdosfs mask?
On Mon, 6 Oct 2003, Bruce Evans wrote: > On Sun, 5 Oct 2003, Nate Lawson wrote: > > In the past, msdosfs has taken its permissions from the mountpoint. > > Recently I noticed that this still works for files in the root directory > > but subdirectories are all chmod 000. Has anyone else seen this? Adding > > the -m=755 flag for instance does work for the files in the top of the > > mountpoint (i.e. command.com) but not subdirectories, which are still 000. > > What's going on? > > Perhaps your mount_msdosfs binary is out of date. Rev.1.25 of > mount_msdosfs.c is required to keep up with corresponding kernel > changes. It passes a separate mask for directories. Thanks! That was it. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cannot create partition entries for /dev/ad3
In message <[EMAIL PROTECTED]>, ecsd writes: >with MAKEDEV gone, the mystery is how to use devfs. >In /dev I have ad3, but I cannot "disklabel -e /dev/ad3s1d", >nor can I "disklabel -e /dev/ad3", and I can't determine >what minor device numbers to assign for mknod to create >the partition entries. Try bsdlabel -w /dev/ad3 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cannot create partition entries for /dev/ad3
with MAKEDEV gone, the mystery is how to use devfs. In /dev I have ad3, but I cannot "disklabel -e /dev/ad3s1d", nor can I "disklabel -e /dev/ad3", and I can't determine what minor device numbers to assign for mknod to create the partition entries. So how does one use devfs to do what MAKEDEV used to do? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
savecore: first and last dump headers disagree on /dev/ad0b
Hello. -CURRENT as of yesterday can't save kernel dump: savecore: first and last dump headers disagree on /dev/ad0b savecore: unsaved dumps found but not saved Is this a known issue? I need to be able to dump to this device because I've seen reliably reproducible panics to be reported, and saving kernel dumps is not supported by ips(4). /dev/ad0 is an IDE hard disk capable of UDMA33 and dedicated to saving kernel dumps, and is not used as a swap device, so I think misc/55933 is not relavant. How can I force it to save the kernel dump; I've tried -f optition, but it didn't work. I've seen no odd messages while it's dumping, just the numbers counted up from 16 to 512. The hardware is IBM NetFinity 6000R, and it has ServerWorks ROSB4 UDMA33 controller, to which the IDE disk is attached. The size of the IDE hard disk is 4Gbytes, and the size of the kernel dump and physical memory both fits in that size. Please tell me if I missed any information you need. Regards. -- YONETANI Tomokazu / Ergo-Brains Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Debugging CURRENT kernels using remote gdb on STABLE does not work ?
On Mon, Oct 06, 2003 at 10:34:50PM +0400, Vladimir B. Grebenschikov wrote: > > Hi > > Debugging CURRENT kernels using remote gdb on STABLE does not work ? That's probably to be expected - trying to debug a 5.x crashdump with 4.x's gdb also doesn't work, because gdb needs to know details of the kernel which are not the same between the two versions. Kris pgp0.pgp Description: PGP signature
Re: D-Link DWL-520+
Hi there. If you want a very stable Freebsd Access Point, use a PCMCIA card with chipset prism II and freebsd 5.0 release I 've got one working for 6 month with more than 40 customers (never crash!!) if you want to use a PCI card try with a Netgear is prism 2.5 (I testing one these now and looks fine but slower than PCMCIA prism II) . you have to use the firmware 1.4.9 or 1.5.6, I trust more in 1.4.9 Don't use freebsd 5.1 is half speed less! cheers! Marcos tokza wrote: On Monday 06 October 2003 05:22, Marcos Biscaysaqu wrote: Ok.! Anyway don't use the Dlink 520 as Access Point has a bug, and crash very often. :( No problem if you use it like client :) Hm, sounds wery useful for me, thanks a lot. Building wireless Host AP on freebsd using PCI wi-fi card is exact the one thing I want to do. So would you mind to reccommend good PCI card for building Host AP? I know, it should be wi-based card, but what's the best? Or maybe building host AP with PCI card is a bad idea in mind and it's better to buy hardware AP? -- Marcos Biscaysaqu Systems Administrator ThePacific.Net Ltd. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cardbus code still broken in current
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstric t-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma t-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contri b/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/u sr/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common - finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings -mpreferred-st ack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/cardbus/cardbus_cis.c /usr/src/sys/dev/cardbus/cardbus_cis.c:80: warning: `decode_tuple_copy' declared `static' but never defined *** Error code 1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: D-Link DWL-520+
On Monday 06 October 2003 05:22, Marcos Biscaysaqu wrote: > Ok.! > Anyway don't use the Dlink 520 as Access Point has a bug, and crash very > often. :( > No problem if you use it like client :) Hm, sounds wery useful for me, thanks a lot. Building wireless Host AP on freebsd using PCI wi-fi card is exact the one thing I want to do. So would you mind to reccommend good PCI card for building Host AP? I know, it should be wi-based card, but what's the best? Or maybe building host AP with PCI card is a bad idea in mind and it's better to buy hardware AP? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb digital camera failure
Matt wrote: [EMAIL PROTECTED] root]# mdconfig -a -t vnode -f /root/blah md0 [EMAIL PROTECTED] root]# mount_msdosfs /dev/md0 /mnt [EMAIL PROTECTED] root]# ls /mnt dcim [EMAIL PROTECTED] root]# cd /mnt/dcim/100_fuji/ [EMAIL PROTECTED] 100_fuji]# ls dscf0001.jpg dscf0006.jpg dscf0011.jpg dscf0016.jpg dscf0021.jpg dscf0002.jpg dscf0007.jpg dscf0012.jpg dscf0017.jpg dscf0022.jpg dscf0003.jpg dscf0008.jpg dscf0013.jpg dscf0018.jpg dscf0023.jpg dscf0004.jpg dscf0009.jpg dscf0014.jpg dscf0019.jpg dscf0024.jpg dscf0005.jpg dscf0010.jpg dscf0015.jpg dscf0020.jpg dscf0025.jpg [EMAIL PROTECTED] 100_fuji]# cp * ~ [EMAIL PROTECTED] 100_fuji]# Sorry. I've just got home from work. Forgot about msdosfs :) Ok so that seems to work. Matt. Sorry I forgot to answer your other question. "Recently" was June 22nd. Where this camera worked perfectly on -current. I normally buildworld on a saturday morning so I guess that would have been a kernel/world of June the 21st. Anyway bottom line is the dd and mdconfig mount worked fine. I've copied all the pictures off. So the problem I am now currently seeing is the OHCI driver issue people know about already. Thanks for your help! Regards, Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAng doesn't boot on my notebook - panic
Hi Soren, please help. I can't boot kernel after ATAng. It founds one extra ATA device (I have no ata1-slave attached) and then panics. All details in PR kern/57156. In short: ad0: setting UDMA33 on Intel PIIX4 chip GEOM: create disk ad0 dp=0xc1d00970 ad0: ATA-5 disk at ata0-master ad0: 38154MB (78140160 sectors), 77520 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA33 GEOM: new disk ad0 [0] f:00 typ:6 s(CHS):0/1/1 e(CHS):969/239/63 s:63 l:14666337 [1] f:00 typ:160 s(CHS):970/0/1 e(CHS):996/239/63 s:14666400 l:408240 [2] f:80 typ:165 s(CHS):997/0/1 e(CHS):1023/239/63 s:15074640 l:41942880 [3] f:00 typ:165 s(CHS):1023/0/1 e(CHS):1023/239/63 s:57017520 l:21122640 GEOM: Configure ad0s1, start 32256 length 7509164544 end 7509196799 GEOM: Configure ad0s2, start 7509196800 length 209018880 end 7718215679 GEOM: Configure ad0s3, start 7718215680 length 21474754560 end 9192970239 GEOM: Configure ad0s4, start 29192970240 length 10814791680 end 40007761919 GEOM: Configure ad0s3a, start 0 length 134217728 end 134217727 GEOM: Configure ad0s3b, start 134217728 length 268435456 end 402653183 GEOM: Configure ad0s3c, start 0 length 21474754560 end 21474754559 GEOM: Configure ad0s3e, start 402653184 length 6442450944 end 6845104127 GEOM: Configure ad0s3f, start 6845104128 length 14629650432 end 1474754559 GEOM: Configure ad0s4c, start 0 length 10814791680 end 10814791679 GEOM: Configure ad0s4e, start 0 length 134217728 end 134217727 GEOM: Configure ad0s4f, start 134217728 length 8915517440 end 9049735167 ata1-slave: pio=0x08 wdma=0x udma=0x cable=40pin ata1-master: pio=0x09 wdma=0x udma=0x cable=40pin ad1: FAILURE - SETFEATURES status=51 error=4 ad1: FAILURE - SETFEATURES status=51 error=4 ad1: FAILURE - SETFEATURES status=51 error=4 ad1: FAILURE setting PIO1 on Intel PIIX4 chip GEOM: create disk ad1 dp=0xc1d4b770 ad1: ATA-0 disk at ata1-master ad1: 3MB (7904 sectors), 247 C, 2 H, 16 S, 512 B ad1: 1 secs/int, 1 depth queue, BIOSPIO GEOM: new disk ad1 ad2: WARNING - SETFEATURES recovered from missing interrupt [0] f:80 typ:1 s(CHS):0/1/12 e(CHS):245/1/16 s:27 l:7845 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad1s1, start 13824 length 4016640 end 4030463 ad2: WARNING - SETFEATURES recovered from missing interrupt ad2: WARNING - SETFEATURES recovered from missing interrupt ad2: setting PIO0 on Intel PIIX4 chip GEOM: create disk ad2 dp=0xc1d4b970 ad2: ATA-0 disk at ata1-slave Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc03fa088 stack pointer = 0x10:0xc05c5c54 frame pointer = 0x10:0xc05c5cd0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) kernel: type 18 trap, code=0 Stopped at __qdivrem+0x38: divl%ecx,%eax db> tra __qdivrem(0,0,0,0,0) at __qdivrem+0x38 __udivdi3(0,0,0,0,0) at __udivdi3+0x2e ad_attach(c1c712d4,1,c0ac6c50,c0445310,c05c5d74) at ad_attach+0x4aa ata_boot_attach(0,c02392d6,c046392c,0,c0445310) at ata_boot_attach+0x6f run_interrupt_driven_config_hooks(0,0,c0ac46f8,c0ac46f8,5c2c00) at run_interrupt_driven_config_hooks+0x2b mi_startup() at mi_startup+0xa1 begin() at begin+0x2c db> Any solution or workaround ? -- Vladimir B. Grebenschikov <[EMAIL PROTECTED]> SWsoft Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb digital camera failure
Bernd Walter wrote: On Mon, Oct 06, 2003 at 07:26:34PM +0100, Matt wrote: [EMAIL PROTECTED] root]# dd if=/dev/da0s1 of=/root/blah bs=512 dd: /dev/da0s1: Input/output error 63646+0 records in 63646+0 records out 32586752 bytes transferred in 812.878115 secs (40088 bytes/sec) [EMAIL PROTECTED] root]# mdconfig -a -t vnode -f /root/blah md0 [EMAIL PROTECTED] root]# mount /dev/md0 /mnt mount: /dev/md0 on /mnt: incorrect super block you want -t msdosfs [EMAIL PROTECTED] root]# ls -al blah -rw-r--r-- 1 root wheel 32586752 Oct 6 19:22 blah The dd took a good 10 minutes and was transferring lots of data over the link before it gave that i/o error. So not sure. Is this the problem you have seen before or a new problem? Could be the well known problem, but the IO error doesn't fit. This camera DID used to work perfectly on freebsd 4.x and -current up until recently. Do you have an idea when "recently" was? [EMAIL PROTECTED] root]# mdconfig -a -t vnode -f /root/blah md0 [EMAIL PROTECTED] root]# mount_msdosfs /dev/md0 /mnt [EMAIL PROTECTED] root]# ls /mnt dcim [EMAIL PROTECTED] root]# cd /mnt/dcim/100_fuji/ [EMAIL PROTECTED] 100_fuji]# ls dscf0001.jpg dscf0006.jpg dscf0011.jpg dscf0016.jpg dscf0021.jpg dscf0002.jpg dscf0007.jpg dscf0012.jpg dscf0017.jpg dscf0022.jpg dscf0003.jpg dscf0008.jpg dscf0013.jpg dscf0018.jpg dscf0023.jpg dscf0004.jpg dscf0009.jpg dscf0014.jpg dscf0019.jpg dscf0024.jpg dscf0005.jpg dscf0010.jpg dscf0015.jpg dscf0020.jpg dscf0025.jpg [EMAIL PROTECTED] 100_fuji]# cp * ~ [EMAIL PROTECTED] 100_fuji]# Sorry. I've just got home from work. Forgot about msdosfs :) Ok so that seems to work. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Debugging CURRENT kernels using remote gdb on STABLE does not work ?
Hi Debugging CURRENT kernels using remote gdb on STABLE does not work ? /ext/current/src# uname -r 4.9-PRERELEASE /ext/current/src# gdb -k /usr/obj/ext/current/src/sys/VBOOK/kernel.debug GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called at /ext/releng4/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dwarf2read.c line 3049 in dwarf2_read_section Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. (kgdb) -- Vladimir B. Grebenschikov <[EMAIL PROTECTED]> SWsoft Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb digital camera failure
On Mon, Oct 06, 2003 at 07:26:34PM +0100, Matt wrote: > [EMAIL PROTECTED] root]# dd if=/dev/da0s1 of=/root/blah bs=512 > dd: /dev/da0s1: Input/output error > 63646+0 records in > 63646+0 records out > 32586752 bytes transferred in 812.878115 secs (40088 bytes/sec) > [EMAIL PROTECTED] root]# mdconfig -a -t vnode -f /root/blah > md0 > [EMAIL PROTECTED] root]# mount /dev/md0 /mnt > mount: /dev/md0 on /mnt: incorrect super block you want -t msdosfs > [EMAIL PROTECTED] root]# ls -al blah > -rw-r--r-- 1 root wheel 32586752 Oct 6 19:22 blah > > The dd took a good 10 minutes and was transferring lots of data over the > link before it gave that i/o error. > > So not sure. Is this the problem you have seen before or a new problem? Could be the well known problem, but the IO error doesn't fit. > This camera DID used to work perfectly on freebsd 4.x and -current up > until recently. Do you have an idea when "recently" was? -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb digital camera failure
Bernd Walter wrote: On Sun, Oct 05, 2003 at 10:39:14PM -0700, Doug White wrote: On Sun, 5 Oct 2003, Matt wrote: I have a fuji digital camera which has always previously worked with -current no problems. However I have not tried to copy images from it for a couple of months now. [...] Oct 5 23:02:58 heather kernel: umass0: Fuji Photo Film USB Mass Storage, rev 1.10/10.00, addr 3 Oct 5 23:02:59 heather kernel: GEOM: create disk da0 dp=0xc40abc50 Oct 5 23:02:59 heather kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Oct 5 23:02:59 heather kernel: da0: Removable Direct Access SCSI-0 device Oct 5 23:02:59 heather kernel: da0: 1.000MB/s transfers Oct 5 23:02:59 heather kernel: da0: 62MB (128000 512 byte sectors: 64H 32S/T 62C) Which USB controller? There are known issues with the ohci driver at current. Could you please test to copy the disk with dd and bs=512? The resulting file can be made mountable using mdconfig. If this is the same problem then the dd copy should work, otherwise we have another problem. [EMAIL PROTECTED] root]# dd if=/dev/da0s1 of=/root/blah bs=512 dd: /dev/da0s1: Input/output error 63646+0 records in 63646+0 records out 32586752 bytes transferred in 812.878115 secs (40088 bytes/sec) [EMAIL PROTECTED] root]# mdconfig -a -t vnode -f /root/blah md0 [EMAIL PROTECTED] root]# mount /dev/md0 /mnt mount: /dev/md0 on /mnt: incorrect super block [EMAIL PROTECTED] root]# ls -al blah -rw-r--r-- 1 root wheel 32586752 Oct 6 19:22 blah The dd took a good 10 minutes and was transferring lots of data over the link before it gave that i/o error. So not sure. Is this the problem you have seen before or a new problem? This camera DID used to work perfectly on freebsd 4.x and -current up until recently. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: make buildkernel failure in cardbus.c
On 2003-10-06 at 19:21:34 M. Warner Losh wrote: > My bad. I've fixed it. Builds fine now, thanks for the fast fix. :) pgp0.pgp Description: PGP signature
Re: CDROM / UDMA problem on -current (2 hours old)
Le 2003-10-06, Jan Stocker écrivait : > But here some stuff when booting in "safe mode" (maybe it boots because > DMA support for atapi is off, have to check) Probably so. The messages you quote look perfectly normal. Thomas. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
? warning used static ldt allocation
#dmesg|tail -n 2 Warning: pid 474 used static ldt allocation. See the i386_set_ldt man page for more info What does it means? It was apearring for aprox. 15days. What I have to do? Maybe it was asked before... Could anybody refetch that message or answer? :( -- freebsd the power to serve ---Publicidad Únete a los miles de sin pareja en Meetic... ¡te vas a enamorar! http://www.iespana.es/_reloc/email.meetic ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: make buildkernel failure in cardbus.c
In message: <[EMAIL PROTECTED]> Arjan van Leeuwen <[EMAIL PROTECTED]> writes: : While trying to do a make buildkernel, cvsupped two hours ago: My bad. I've fixed it. I'd had the changes in my local tree for months, but somehow missed committing the cardbus parts. :-( Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDROM / UDMA problem on -current (2 hours old)
On Mon, 2003-10-06 at 17:23, Thomas Quinot wrote: > Le 2003-10-06, Jan Stocker écrivait : > > > I would give you more info... but as i wrote... thats an endless loop. > > You might be able to interrupt the loop by breaking into DDB with > Crtl+Alt+Esc, which then allows you to get a backtrace. Yep, if you've that enabled... my workstation hasn't.. but will have tomorrow you'll get some bt from me. > > > interesting to know whether the enclosed patch changes anything to your > > > situation. > > Will try it. Pls give me some mins (~30) Okay doesnt help But here some stuff when booting in "safe mode" (maybe it boots because DMA support for atapi is off, have to check) Oct 6 19:04:53 Twoflower kernel: acd0: CDROM at ata1-master PIO4 Oct 6 19:04:53 Twoflower kernel: acd1: CDRW at ata1-slave PIO4 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): Invalid field in CDB Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): Invalid field in CDB Oct 6 19:04:53 Twoflower kernel: GEOM: create disk cd0 dp=0xcbbe4e00 Oct 6 19:04:53 Twoflower kernel: GEOM: create disk cd1 dp=0xcbbe4600 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): NOT READY asc:3a,0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Medium not present Oct 6 19:04:53 Twoflower kernel: cd0 at ata1 bus 0 target 0 lun 0 Oct 6 19:04:53 Twoflower kernel: cd0: Removable CD-ROM SCSI-0 device Oct 6 19:04:53 Twoflower kernel: cd0: 16.000MB/s transfers Oct 6 19:04:53 Twoflower kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): NOT READY asc:3a,0 Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): Medium not present Oct 6 19:04:53 Twoflower kernel: cd1 at ata1 bus 0 target 1 lun 0 Oct 6 19:04:53 Twoflower kernel: cd1: Removable CD-ROM SCSI-0 device Oct 6 19:04:53 Twoflower kernel: cd1: 16.000MB/s transfers Oct 6 19:04:53 Twoflower kernel: cd1: Attempt to query device size failed: NOT READY, Medium not present Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): NOT READY asc:3a,0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Medium not present Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): NOT READY asc:3a,0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Medium not present Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): Recovered Sense Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): CAM Status: SCSI Status Error Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): SCSI Status: Check Condition Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): NOT READY asc:3a,0 Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): Medium not present Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): Recovered Sens
Re: ptmx, /dev/pts support for 5.x
On Sun, Oct 05, 2003 at 09:25:53PM -0400, Robert Watson wrote: > Last week, I did a bit of experimentation to look at privilege issues in > the allocation of ptys on FreeBSD. Right now, to safely allocate a > pty/tty pair, you basically need privilege (otherwise you can't > chown/chmod the slave node). I took a look at some of the approaches used > by other systems (specifically Linux, Solaris) and implemented basic ptmx > support for FreeBSD: > http://www.watson.org/~robert/freebsd/pts/ > I took the existing tty_pty.c driver code and remunged most of the dev_t > and clone handling, as well as open/close of both master and slave. It's > far from perfect -- more of an experiment really, but it has some notable > benefits, including allowing programs like window, xterm, etc, to allocate > ptys safely without privilege (although utmp still requires privilege if > you're into that sort of thing). pts/ttys are also GC'd to reset > ownership/permissions/flags in a race-free manner. The current implementation could also be changed to make it safe. It relies on an (ugly) setuid root helper /usr/libexec/pt_chown to chown the slave device. A revoke() call on the slave should be added somewhere after that in grantpt(), or in unlockpt(). A problem is that forking may confuse SIGCHLD handlers. grantpt() in FreeBSD blocks SIGCHLD, but I don't know whether that's enough. POSIX.1-2001 says that calling grantpt() with a SIGCHLD handler produces undefined results. With openpty() programs may not expect that. By the way, in System V the slave device is locked (cannot be opened) when the master is opened. The unlockpt() call unlocks it, so it can be opened, giving the user program time to chown and chmod the slave device. So unlockpt() has little to do with STREAMS, and it should be said in the manpage that this functionality is handled differently (namely, revoke(2)) in FreeBSD, as the deeper purpose of avoiding the race condition is as relevant in FreeBSD as in System V. Jilles Tjoelker ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
IPv6 panic page fault nd6_cache_lladdr/nd6_ns_input
Hello,
After upgrading a system to -CURRENT of yesterday night, making IPv6
connections to another host in the same subnet does not work (remains in
[connec] state). Some messing about with routes solved that, but it
panicked quickly thereafter. After a reboot it panicked again with a
similar panic. I'm running an older kernel now.
The machine is a dual Athlon MP 2000+, 1GB RAM.
Relevant lines from /etc/rc.conf:
ipv6_enable="YES"
ipv6_ifconfig_xl1='2001:610:1108:5012::2 prefixlen 64'
ipv6_network_interfaces="auto"
ipv6_static_routes="nfsrtfix"
ipv6_route_nfsrtfix="2001:610:1108:5012::/64 -iface xl1"
ipv6_firewall_enable="YES"
ipv6_firewall_type="/etc/ip6fw.rules"
The IPv6 firewall rules are very simple (no stateful stuff in there).
Also we do in /etc/rc.local:
sysctl net.inet6.ip6.accept_rtadv=1
rtsol xl0
Results from gdb (first panic, second is very similar, except that it
has softupdate trouble after getting the initial page fault):
Script started on Mon Oct 6 15:21:34 2003
# gdb -k kernel.debug.9 vmcore.9
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-undermydesk-freebsd"...
panic: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 0100
fault virtual address = 0xac
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc0599601
stack pointer = 0x10:0xe0084a8c
frame pointer = 0x10:0xe0084ad8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 15 (swi1: net)
trap number = 12
panic: page fault
cpuid = 0; lapic.id = 0100
boot() called on cpu#0
syncing disks, buffers remaining... 2384 2384 2384 2384 2384 2384 2384 2384 2384 2384
2384 2384 2384 2384 2384 2384 2384 2384 2384 2384
giving up on 809 buffers
Uptime: 11m17s
Dumping 1023 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368
384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704
720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008
---
Reading symbols from
/usr/obj/usr/src/sys/TURTLE/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/TURTLE/modules/usr/src/sys/modules/acpi/acpi.ko.debug
Reading symbols from
/usr/obj/usr/src/sys/TURTLE/modules/usr/src/sys/modules/fdescfs/fdescfs.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/TURTLE/modules/usr/src/sys/modules/fdescfs/fdescfs.ko.debug
Reading symbols from
/usr/obj/usr/src/sys/TURTLE/modules/usr/src/sys/modules/linux/linux.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/TURTLE/modules/usr/src/sys/modules/linux/linux.ko.debug
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc04d6ff1 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc04d7448 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc0655cd6 in trap_fatal (frame=0xe0084a4c, eva=0)
at /usr/src/sys/i386/i386/trap.c:819
#4 0xc0655952 in trap_pfault (frame=0xe0084a4c, usermode=0, eva=172)
at /usr/src/sys/i386/i386/trap.c:733
#5 0xc06554ad in trap (frame=
{tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 1, tf_esi = -536327200, tf_ebp =
-536327464, tf_isp = -536327560, tf_ebx = 0, tf_edx = -1034105584, tf_ecx = 4, tf_eax
= -1034105584, tf_trapno = 12, tf_err = 2, tf_eip = -1067870719, tf_cs = 8, tf_eflags
= 66050, tf_esp = -950171904, tf_ss = 1})
at /usr/src/sys/i386/i386/trap.c:418
#6 0xc063d678 in calltrap () at {standard input}:103
#7 0xc059a774 in nd6_cache_lladdr (ifp=0xc6544000, from=0x0,
lladdr=0xc3275852 "", lladdrlen=8, type=135, code=0)
at /usr/src/sys/netinet6/nd6.c:1654
#8 0xc059ba3d in nd6_ns_input (m=0xc25ef100, off=40, icmp6len=-965550080)
at /usr/src/sys/netinet6/nd6_nbr.c:306
#9 0xc058072b in icmp6_input (mp=0x0, offp=0xe0084c68, proto=58)
at /usr/src/sys/netinet6/icmp6.c:790
#10 0xc0591e1b in ip6_input (m=0xc25eef00)
at /usr/src/sys/netinet6/ip6_input.c:825
#11 0xc0554b59 in netisr_processqueue (ni=0xc06e7538)
---Type to continue, or q to quit---
at /usr/src/sys/net/netisr.c:140
#12 0xc0555048 in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:246
#13 0xc04c0d88 in ithread_loop (arg=0xc25c9c00)
at /usr/src/sys/kern/kern_intr.c:534
#14 0xc04bf9c1 in fork_exit (callout=0xc04c0bb0 , arg=0x0,
frame=0x0) at /usr/src/sys/kern/kern_fork.c:796
(kgdb) frame 7
#7 0xc059a774 in nd6_cac
Re: CDROM / UDMA problem on -current (2 hours old)
Le 2003-10-06, Jan Stocker écrivait : > I would give you more info... but as i wrote... thats an endless loop. You might be able to interrupt the loop by breaking into DDB with Crtl+Alt+Esc, which then allows you to get a backtrace. > > interesting to know whether the enclosed patch changes anything to your > > situation. > Will try it. Pls give me some mins (~30) Thanks! Thomas. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel build breaks in dev/cardbus
In message: <[EMAIL PROTECTED]> Lukas Ertl <[EMAIL PROTECTED]> writes: : a buildkernel from a fresh cvsup breaks with these errors: working on it. my bad. warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDROM / UDMA problem on -current (2 hours old)
> are printed so fast i cant really read but it must be something > > like that: > > acd1: WARNING - REQUEST_UDMA (error request) > > acd1: WARNING - INQUIRE_SENSE (retrying request) > > Little can be said without complete and accurate error messages, > preferrably including a complete kernel backtrace, but still it would be I would give you more info... but as i wrote... thats an endless loop. > interesting to know whether the enclosed patch changes anything to your > situation. Will try it. Pls give me some mins (~30) > > /usr/local/bin/cdrecord: Permission denied. Cannot send SCSI cmd via ioctl > > Check perms on your /dev nodes. cdrecord runs suid root should be enough rights... > it's an atapicam problem... > > That we do not know so far. Recent problems reported by ATAPI/CAM users > were mostly ATA and CAM bugs. Please do not make such hasty statements > until a complete analysis of the problem has been made. Okay... you're right... shame on me and i try to see more in the depth of the kernel in the future ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ld not sucking in /usr/lib/crt1.o - or is it me?
On Mon, 6 Oct 2003 20:52:23 +1100 "Chris Knight" <[EMAIL PROTECTED]> wrote: > > If I add /usr/lib/crt1.o to the file list it works OK. Any reason > why ld isn't pulling this in automatically? Feel free to correct > me if I'm missing the obvious and if there's a better way of > resolving this. Thanks. > ld is not supposed to pull in anything except what was given to it on the command line. Why your build tries to use LD where it should be using CC is a separate question though... -- Alexander Kabaev ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't build kernel without overriding -Werror
Anybody expecting this: /usr/src# make buildkernel ... cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I 17:33:15 [] flashone: . -I/ext/current/src/sys -I/ext/current/src/sys/contrib/dev/acpica -I/ext/current/src/sys/contrib/ipfilter -I/ext/current/src/sys/contrib/dev/ath -I/ext/current/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -O3 -mcpu=pentiumpro -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /ext/current/src/sys/kern/kern_descrip.c /ext/current/src/sys/kern/kern_descrip.c:1894: warning: inlining failed in call to `_fgetvp' /ext/current/src/sys/kern/kern_descrip.c:1915: warning: called from here /ext/current/src/sys/kern/kern_descrip.c:1894: warning: inlining failed in call to `_fgetvp' /ext/current/src/sys/kern/kern_descrip.c:1922: warning: called from here /ext/current/src/sys/kern/kern_descrip.c:1894: warning: inlining failed in call to `_fgetvp' /ext/current/src/sys/kern/kern_descrip.c:1929: warning: called from here *** Error code 1 Stop in /usr/obj/ext/current/src/sys/VBOOK. *** Error code 1 Stop in /ext/current/src. *** Error code 1 Stop in /ext/current/src. /usr/src# Suggestions ? -- Vladimir B. Grebenschikov <[EMAIL PROTECTED]> SWsoft Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb keyboard not working in single user mode
On Sun, Oct 05, 2003 at 09:17:37PM -0700, Doug White wrote: > On Fri, 3 Oct 2003, Ken McKittrick wrote: > > I've got 5.1-current running on an IBM BladeCenter HS20. This thing has > > a USB KVM built-in. It's working in multi-user mode. Problem is when I > > boot to single user, can't do anything. > Check that atkbd is using flags 0x1. That should cause atkbd not to > attach and allow ukbd to take over. If your system happens to emulate a > atkbd even when one is not attached, you will have to modify the start > scripts to run kbdcontrol even in the single-user case (if thats even > possible). No /etc/rc* scripts are run in single-user mode. You would have to put it in /.profile, with a test such as [ $(/bin/ps -o ppid= -p $$) = 1 ]. Jilles Tjoelker ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
make buildkernel failure in cardbus.c
While trying to do a make buildkernel, cvsupped two hours ago: /usr/local/bin/gcc -c -O -pipe -march=athlon-xp -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/ usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/cardbus/cardbus.c /usr/src/sys/dev/cardbus/cardbus.c:380: error: `card_cis_read_desc' undeclared here (not in a function) /usr/src/sys/dev/cardbus/cardbus.c:380: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:380: error: (near initialization for `cardbus_methods[27].desc') /usr/src/sys/dev/cardbus/cardbus.c:380: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:380: error: (near initialization for `cardbus_methods[27]') /usr/src/sys/dev/cardbus/cardbus.c:381: error: `card_cis_free_desc' undeclared here (not in a function) /usr/src/sys/dev/cardbus/cardbus.c:381: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:381: error: (near initialization for `cardbus_methods[28].desc') /usr/src/sys/dev/cardbus/cardbus.c:381: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:381: error: (near initialization for `cardbus_methods[28]') /usr/src/sys/dev/cardbus/cardbus.c:384: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:384: error: (near initialization for `cardbus_methods[29]') /usr/src/sys/dev/cardbus/cardbus.c:385: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:385: error: (near initialization for `cardbus_methods[30]') /usr/src/sys/dev/cardbus/cardbus.c:386: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:386: error: (near initialization for `cardbus_methods[31]') /usr/src/sys/dev/cardbus/cardbus.c:387: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:387: error: (near initialization for `cardbus_methods[32]') /usr/src/sys/dev/cardbus/cardbus.c:388: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:388: error: (near initialization for `cardbus_methods[33]') /usr/src/sys/dev/cardbus/cardbus.c:389: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:389: error: (near initialization for `cardbus_methods[34]') /usr/src/sys/dev/cardbus/cardbus.c:390: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:390: error: (near initialization for `cardbus_methods[35]') /usr/src/sys/dev/cardbus/cardbus.c:391: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:391: error: (near initialization for `cardbus_methods[36]') /usr/src/sys/dev/cardbus/cardbus.c:392: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:392: error: (near initialization for `cardbus_methods[37]') /usr/src/sys/dev/cardbus/cardbus.c:394: error: initializer element is not constant /usr/src/sys/dev/cardbus/cardbus.c:394: error: (near initialization for `cardbus_methods[38]') *** Error code 1 Stop in /usr/obj/usr/src/sys/AMD760. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ld not sucking in /usr/lib/crt1.o - or is it me?
Howdy, I installed 5.1 on my laptop, then synced up to -current as of 8 hours ago. I'm trying to build the 1.5 branch of Firebird (the DBMS), but run into the following error: ld ../temp/static.gpre/gpre/cmd.o ../temp/static.gpre/gpre/cme.o ../temp/static.gpre/gpre/cmp.o ../temp/static.gpre/gpre/c_cxx.o ../temp/static.gpre/gpre/exp.o ../temp/static.gpre/gpre/gpre.o ../temp/static.gpre/gpre/hsh.o ../temp/static.gpre/gpre/int.o ../temp/static.gpre/gpre/int_cxx.o ../temp/static.gpre/gpre/jrdmet.o ../temp/static.gpre/gpre/movg.o ../temp/static.gpre/gpre/msc.o ../temp/static.gpre/gpre/par.o ../temp/static.gpre/gpre/pat.o ../temp/static.gpre/gpre/sqe.o ../temp/static.gpre/gpre/sql.o ../temp/static.gpre/gpre/noform.o ../temp/static.gpre/gpre/gpre_meta.o -o ../gen/firebird/bin/gpre_static -L../gen/firebird/lib -lfbstatic -lfbcom mon -lstdc++ -lcurses -lcrypt -lm -lc -leditline ld: warning: cannot find entry symbol _start; defaulting to 0804dc70 /usr/lib/libc.so: undefined reference to `environ' /usr/lib/libc.so: undefined reference to `__progname' gmake[3]: *** [../gen/firebird/bin/gpre_static] Error 1 gmake[3]: Leaving directory `/u1/scratch/firebird-devel/work/firebird2/src' gmake[2]: *** [gpre_static] Error 2 gmake[2]: Leaving directory `/u1/scratch/firebird-devel/work/firebird2/src' gmake[1]: *** [../gen/firebird/bin/gpre_static] Error 2 gmake[1]: Leaving directory `/u1/scratch/firebird-devel/work/firebird2/src' gmake: *** [firebird] Error 2 *** Error code 2 If I add /usr/lib/crt1.o to the file list it works OK. Any reason why ld isn't pulling this in automatically? Feel free to correct me if I'm missing the obvious and if there's a better way of resolving this. Thanks. Regards, Chris Knight Systems Administrator E-Easy Tel: +61 3 6334 9995 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.e-easy.com.au ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb digital camera failure
On Sun, Oct 05, 2003 at 10:39:14PM -0700, Doug White wrote: > On Sun, 5 Oct 2003, Matt wrote: > > > I have a fuji digital camera which has always previously worked with > > -current no problems. However I have not tried to copy images from it > > for a couple of months now. > > [...] > > > Oct 5 23:02:58 heather kernel: umass0: Fuji Photo Film USB Mass > > Storage, rev 1.10/10.00, addr 3 > > Oct 5 23:02:59 heather kernel: GEOM: create disk da0 dp=0xc40abc50 > > Oct 5 23:02:59 heather kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > > Oct 5 23:02:59 heather kernel: da0: > > Removable Direct Access SCSI-0 device > > Oct 5 23:02:59 heather kernel: da0: 1.000MB/s transfers > > Oct 5 23:02:59 heather kernel: da0: 62MB (128000 512 byte sectors: 64H > > 32S/T 62C) > > Which USB controller? There are known issues with the ohci driver at > current. Could you please test to copy the disk with dd and bs=512? The resulting file can be made mountable using mdconfig. If this is the same problem then the dd copy should work, otherwise we have another problem. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic: mutex vm object not owned at ../../../vm/vm_page.c:762
I got this upon attempting to burn a CD with cdrecord on my
freshly-updated current machine:
panic: mutex vm object not owned at ../../../vm/vm_page.c:762
syncing disks, buffers remaining... 3842 3842 3842 3842 3842 3842 3842 3842 3842 3842
3842 3842 3842 3842 3842 3842 3842 3842 3842 3842
giving up on 218 buffers
Uptime: 16m51s
Dumping 511 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368
384 400 416 432 448 464 480 496
---
Reading symbols from /boot/kernel/nvidia.ko...done.
Loaded symbols for /boot/kernel/nvidia.ko
#0 doadump () at ../../../kern/kern_shutdown.c:240
240 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:240
#1 0xc054a32d in boot (howto=256) at ../../../kern/kern_shutdown.c:372
#2 0xc054a6b7 in panic () at ../../../kern/kern_shutdown.c:550
#3 0xc05410cc in _mtx_assert (m=0xc4ea4c24, what=0, file=0xc06f8518
"../../../vm/vm_page.c", line=762)
at ../../../kern/kern_mutex.c:855
#4 0xc065c03c in vm_page_alloc (object=0xc4ea4c24, pindex=0, req=0) at
../../../vm/vm_page.c:762
#5 0xc064e68b in vm_fault_copy_entry (dst_map=0xc4f527e0, src_map=0xc4d653f0,
dst_entry=0xc537fd5c,
src_entry=0x0) at ../../../vm/vm_fault.c:1167
#6 0xc0654e81 in vm_map_copy_entry (src_map=0xc4d653f0, dst_map=0xc4f527e0,
src_entry=0xc537f834,
dst_entry=0xc537fd5c) at ../../../vm/vm_map.c:2379
#7 0xc06551c6 in vmspace_fork (vm1=0xc4d653f0) at ../../../vm/vm_map.c:2494
#8 0xc064fcce in vm_forkproc (td=0xc4ebe130, p2=0xc53855ac, td2=0xc4ebeab0, flags=20)
at ../../../vm/vm_glue.c:624
#9 0xc05353f5 in fork1 (td=0xc4ebe130, flags=20, pages=0, procp=0xd9d38cd8) at
../../../kern/kern_fork.c:654
#10 0xc053441b in fork (td=0xc4ebe130, uap=0xd9d38d10) at ../../../kern/kern_fork.c:102
#11 0xc06a4d93 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 4096, tf_esi = 65536, tf_ebp =
-1077948008, tf_isp = -640447116, tf_ebx = 64, tf_edx = 1307, tf_ecx = 672806144,
tf_eax = 2, tf_trapno = 0, tf_err = 2, tf_eip = 672202079, tf_cs = 31, tf_eflags =
582, tf_esp = -1077948052, tf_ss = 47}) at ../../../i386/i386/trap.c:1006
#12 0xc069505d in Xint0x80_syscall () at {standard input}:144
---Can't read userspace from dump, or kernel process---
(kgdb)
The annoying thing was that something apparently overwrote the
partition table on the disk holding the swap partition - I had to
recreate it by hand before I could bring the system back up, although
it then came back up without further problems.
Kris
pgp0.pgp
Description: PGP signature
Re: msdosfs mask?
On Sun, 5 Oct 2003, Nate Lawson wrote: > In the past, msdosfs has taken its permissions from the mountpoint. > Recently I noticed that this still works for files in the root directory > but subdirectories are all chmod 000. Has anyone else seen this? Adding > the -m=755 flag for instance does work for the files in the top of the > mountpoint (i.e. command.com) but not subdirectories, which are still 000. > What's going on? This still works for me. Perhaps your mount_msdosfs binary is out of date. Rev.1.25 of mount_msdosfs.c is required to keep up with corresponding kernel changes. It passes a separate mask for directories. Old versions of mount_msdosfs don't understand the new field for the directory mask in the args struct so they don't pass anything. More precisely, it happens that the new field fits in unnamed padding in the old args struct, so adding it didn't completely break binary compatibility with old mount_msdosfs binaries; all version fill memset the struct to 0 so they set unnamed padding to 0, so old versions do the equivalent of the new version when the latter is invoked with "-M 0". But a mask of 0 is rarely what is wanted. The compatibility problems can be fixed easily since the new field is in spare space and there is already a magic number and flags for version control. See also PR bin/57401 which has a quick fix for amd. The fix is wrong since it is under a wrong ifdef, and it shouldn't be necessary -- amd should work like an old mount_msdosfs binary and simply not pass a dirmask (by not setting a flag which that it passes one). amd could also use flags for saying that it doesn't pass a file mask or uid or gid... either. It always passes 0777 for the file mask and 0 for the ids instead of the attributes inherited from the mount point. Perhaps more of the logical for this should be in the kernel since applications get it wrong. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb digital camera failure
Doug White wrote: On Sun, 5 Oct 2003, Matt wrote: I have a fuji digital camera which has always previously worked with -current no problems. However I have not tried to copy images from it for a couple of months now. [...] Oct 5 23:02:58 heather kernel: umass0: Fuji Photo Film USB Mass Storage, rev 1.10/10.00, addr 3 Oct 5 23:02:59 heather kernel: GEOM: create disk da0 dp=0xc40abc50 Oct 5 23:02:59 heather kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Oct 5 23:02:59 heather kernel: da0: Removable Direct Access SCSI-0 device Oct 5 23:02:59 heather kernel: da0: 1.000MB/s transfers Oct 5 23:02:59 heather kernel: da0: 62MB (128000 512 byte sectors: 64H 32S/T 62C) Which USB controller? There are known issues with the ohci driver at current. Yes it is OHCI. Ok if it's a known fault and people are working on it then that's cool. I just thought I would mention it. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mgetty fails in -current
I don't know if it is a problem with 5.1 or with my ASUS P4SX (sio on board, Sis chipset) or with the Devolo Fun II (ELSA Microlink) modem. Anyway, I spent the sunday afternoon sending log files into the mgetty+sendfax list (Gert Doering, the maintainer and author of mgetty) was so king to help and analyze the problem. He came to the conclusion that while mgetty should stay in a select() waiting loop it gets unexpected input on the descriptor and thinks a RING would come in. Instead the input comes from previous chat with the modem and it looks if characters are not coming not fast enough or delayed from the preceeding chat dialog. I'm appending a piece of log: 10/05 16:47:11 aa0got:[0d][0a]ERROR[0d] 10/05 16:47:11 aa0 mdm_command: string 'ERROR' -> ERROR 10/05 16:47:11 aa0 no class 2/2.0 faxmodem, no faxing available 10/05 16:47:11 aa0 waiting for line to clear (select), read: 10/05 16:47:12 aa0select returned 0 10/05 16:47:12 aa0 removing lock file 10/05 16:47:12 aa0 waiting... 10/05 16:47:12 aa0 checking lockfiles, locking the line 10/05 16:47:12 aa0 makelock(cuaa0) called 10/05 16:47:12 aa0 do_makelock: lock='/var/spool/lock/LCK..cuaa0' 10/05 16:47:12 aa0 lock made 10/05 16:47:12 aa0 wfr: waiting for ``RING'' 10/05 16:47:12 aa0 got: [0a] 10/05 16:47:22 aa0 mdm_read_byte: read returned -1: Interrupted system call 10/05 16:47:22 aa0 wfr: timeout waiting for RING 10/05 16:47:22 aa0 wfr: rc=-1, drn=0 10/05 16:47:22 aa0 huh? Junk on the line? 10/05 16:47:22 aa0 >>> could be a dial-out program without proper locking - check this! 10/05 16:47:22 aa0 removing lock file -- 10/05 16:47:22 aa0 mgetty: experimental test release 1.1.30-Dec16 10/05 16:47:22 aa0 mgetty.c compiled at Oct 5 2003, 16:16:48 10/05 16:47:22 aa0 user id: 0, pid: 29530, parent pid: 1 10/05 16:47:22 aa0 reading configuration data for port 'cuaa0' 10/05 16:47:22 aa0 reading /usr/local/etc/mgetty+sendfax/mgetty.config... 10/05 16:47:22 aa0 conf lib: read: 'port cuaa0' 10/05 16:47:22 aa0 section: port cuaa0, **found** 10/05 16:47:22 aa0 conf lib: read: 'debug 4' 10/05 16:47:22 aa0 conf lib: read: 'fax-id 49 2405 x' 10/05 16:47:22 aa0 conf lib: read: 'speed 38400' 10/05 16:47:22 aa0 conf lib: read: 'direct NO' 10/05 16:47:22 aa0 conf lib: read: 'blocking YES' 10/05 16:47:22 aa0 conf lib: read: 'port-owner uucp' 10/05 16:47:22 aa0 conf lib: read: 'port-group uucp' -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SiI3112 SATA controller problems - status
It seems Derek Ragona wrote: > The SATA seems better, but is still not working. I tried the Oct 5 > snapshot, doing a clean install. I CVSup'd and did > make buildworld > make buildkernel KERNCONF=GENERIC > make installkernel KERNCONF=GENERIC > reboot to single user > mount -a > swapon -a > mergemaster -p > make installworld > > System has the same DMA write problems. In this recent case it was > installing termcap. I tried the Oct 1 snapshot and it was the same, it > errored in installworld installing tar. > > The SATA is stabler as I can buildworld, but not stable enough to handle > the installworld copies. > > Here is what I copied from the console after it went into the debugger: > spec_getpages I/O Read failure(error=5) > vm_fault: pager read error > panic: initiate_write_inodeblock_ufs2: already started Thanks for the info, and no I havn't found the problem yet, sorry... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
