Re: fusefs-kmod does not work on 8-STABLE?
On 2013-04-16 08:14, Alexey Dokuchaev wrote: On Mon, Apr 15, 2013 at 10:41:36PM -0400, Ryan Stone wrote: On Fri, Apr 12, 2013 at 10:28 AM, Alexey Dokuchaev wrote: I've found the culprit: the problem is in this command of the build: ld -Bshareable -d -warn-common -o hello.ko.debug hello.kld I had put /usr/local/bin in my $PATH before /usr/bin for a reason I don't currently recall, and have binutils-2.23.1 installed. As a result, ld(1) in the quoted line above was called from /usr/local/bin/ld, [...] Is this for i386? When compiling modules with newer versions of ld I had to add the following flags to the ld invocation to get the module to work: Yes, this is for i386. -u __start_set_sysinit_set -u __start_set_sysuninit_set \ -u __start_set_sysctl_set -u __start_set_modmetadata_set \ -u __stop_set_sysinit_set -u __stop_set_sysuninit_set \ -u __stop_set_sysctl_set -u __stop_set_modmetadata_set Hmm. Adding these does help, indeed. How did you come up with this list? Is it documented anywhere, or just the result of careful readelf/objdump examination? Thanks! These are module start/stop symbols, which get optimized away by newer versions of binutils. We fixed it in head when binutils 2.17.50 was imported, here: http://svn.freebsd.org/changeset/base/215137 This fix could probably also be used for stable/8. It is most likely too late to get into 8.4, though. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: fusefs-kmod does not work on 8-STABLE?
On Tue, Apr 16, 2013 at 01:21:32PM +0200, Dimitry Andric wrote: > On 2013-04-16 08:14, Alexey Dokuchaev wrote: > >>-u __start_set_sysinit_set -u __start_set_sysuninit_set \ > >>-u __start_set_sysctl_set -u __start_set_modmetadata_set \ > >>-u __stop_set_sysinit_set -u __stop_set_sysuninit_set \ > >>-u __stop_set_sysctl_set -u __stop_set_modmetadata_set > > These are module start/stop symbols, which get optimized away by newer > versions of binutils. We fixed it in head when binutils 2.17.50 was > imported, here: > > http://svn.freebsd.org/changeset/base/215137 > > This fix could probably also be used for stable/8. It is most likely > too late to get into 8.4, though. Personally I do not care for 8.4 (or any release), but would definitely appreciate if you could merge it to stable/8, thanks! ./danfe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: EuroBSDcon 2013: Call for Proposals, Conference on September 28+29 2013
On 15.04.2013 05:32, Julian Elischer wrote: On 4/11/13 5:18 PM, Andre Oppermann wrote: Excuse me for being slightly spammy but I've received feedback that we haven't spread this information widely enough outside the inner circles and interested people missed the announcement. EuroBSDcon 2013: September 28-29 in Malta = EuroBSDcon is the European technical conference for users and developers of BSD-based systems. The conference will take place Saturday and Sunday 28-29 September at the Hilton Conference Centre in St. Julian's, Malta (tutorials and FreeBSD Developer Summit on preceding Thursday and Friday, talks on Saturday and Sunday). [Yes, very nice weather at that time of year, about 26/19C sunny no rain, Social event on Saturday evening is going to be a sunset beach BBQ] The web page suggest I bring my wife AND my spouse.. what if they don't > know about each other? Well, you have poorly managed your relationships then. ;) This web page is a place holder and will be updated with the all important details on venue/travel/hotels/schedule really soon now. -- Andre ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: EuroBSDcon 2013: Call for Proposals, Conference on September 28+29 2013
On 4/16/13 10:59 AM, Andre Oppermann wrote: On 15.04.2013 05:32, Julian Elischer wrote: On 4/11/13 5:18 PM, Andre Oppermann wrote: Excuse me for being slightly spammy but I've received feedback that we haven't spread this information widely enough outside the inner circles and interested people missed the announcement. EuroBSDcon 2013: September 28-29 in Malta = EuroBSDcon is the European technical conference for users and developers of BSD-based systems. The conference will take place Saturday and Sunday 28-29 September at the Hilton Conference Centre in St. Julian's, Malta (tutorials and FreeBSD Developer Summit on preceding Thursday and Friday, talks on Saturday and Sunday). [Yes, very nice weather at that time of year, about 26/19C sunny no rain, Social event on Saturday evening is going to be a sunset beach BBQ] The web page suggest I bring my wife AND my spouse.. what if they don't > know about each other? Well, you have poorly managed your relationships then. ;) This web page is a place holder and will be updated with the all important details on venue/travel/hotels/schedule really soon now. Tweeted: BSDTV: EuroBSDcon 2013: September 28-29 in Malta : 2013.eurobsdcon.org Your family will actually want to travel with you! #BSD P ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kern/165903: mbuf leak
On Tue, Apr 16, 2013 at 04:43:49PM +, Chris Forgeron wrote: > Thanks, I've applied it, and am rebuilding now. I should know tonight/tomorrow > > I take it this proves that I don't have the latest source with cvsup, or is > this work in progress? > > Thanks again. The patch Gleb provided is not committed anywhere (not even HEAD/current) -- it's a patch for you to test. :-) The sources you have via csup/cvsup seem to be recent enough (all I can go off of is your legacy em(4) driver version being 1.0.5). -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Lost CDROM on 9.1 with ATA_CAM on Promise controller
I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00) after going from 7.4 to 9.1 when using ATA_CAM. It is attached to a Promise PDC20268 UDMA100 controller. A standard harddisk drive attached to this controller works well. Cables, controller and drive where replaced already. Kernel gives me: atapci1: port 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f mem 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0 ata2: at channel 0 on atapci1 ata3: at channel 1 on atapci1 ... ada0 at ata2 bus 0 scbus2 target 0 lun 0 ada0: ATA-7 device ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C) ... (cd2:ata3:0:0:0): got CAM status 0x50 (cd2:ata3:0:0:0): fatal error, failed to attach to device (cd2:ata3:0:0:0): lost device, 4 refs (cd2:ata3:0:0:0): removing device entry ... Attaching the CDROM drive to the controller that is integrated on the mainboard (Intel PIIX4 UDMA33 controller) does not show this problem (but here I don't have UDMA66). It also works when not using ATA_CAM: ... acd0: DVDR at ata3-master UDMA66 ... So this semes to be a problem with the Promise controller and ATA_CAM. Any ideas? Or should I file PR? Thanks, -Andre ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lost CDROM on 9.1 with ATA_CAM on Promise controller
On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote: > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00) > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to > a Promise PDC20268 UDMA100 controller. A standard harddisk drive > attached to this controller works well. Cables, controller and drive > where replaced already. > > Kernel gives me: > > atapci1: port > 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f mem > 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0 > ata2: at channel 0 on atapci1 > ata3: at channel 1 on atapci1 > ... > ada0 at ata2 bus 0 scbus2 target 0 lun 0 > ada0: ATA-7 device > ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) > ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C) > ... > (cd2:ata3:0:0:0): got CAM status 0x50 > (cd2:ata3:0:0:0): fatal error, failed to attach to device > (cd2:ata3:0:0:0): lost device, 4 refs > (cd2:ata3:0:0:0): removing device entry > ... > > Attaching the CDROM drive to the controller that is integrated on > the mainboard (Intel PIIX4 UDMA33 controller) does not show this > problem (but here I don't have UDMA66). > > It also works when not using ATA_CAM: > > ... > acd0: DVDR at ata3-master UDMA66 > ... > > So this semes to be a problem with the Promise controller and ATA_CAM. > > Any ideas? Or should I file PR? The controller in question is a Promise Ultra100 TX2. The error message comes from sys/cam/scsi/scsi_cd.c, in function cddone(). The logic is a little hard for me to follow (I understand about 70% of it). Look at lines 1724 to 1877 for stable/9. 1. Can you provide full output from a verbose boot when the CD/DVD drive is attached to the Promise controller? 2. What firmware version the card is using? The PDC20268 had many, many firmware problems relating to ATAPI devices. 3. I wouldn't worry about ATA66 vs. ATA33; this drive can only support up to about 22MBytes/second so ATA66 isn't going to get you anything, so as a workaround, using the PIIX4 for it would not hurt you. 4. ONLY if this turns out to be a "controller thing": I'm not sure how much effort should be spent trying to make this work, as the PDC20268 is legacy/deprecated hardware (made/released 13 years ago). -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lost CDROM on 9.1 with ATA_CAM on Promise controller
On Tue, 16-Apr-2013 at 21:38:22 +0200, Jeremy Chadwick wrote: > On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote: > > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00) > > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to > > a Promise PDC20268 UDMA100 controller. A standard harddisk drive > > attached to this controller works well. Cables, controller and drive > > where replaced already. > > > > Kernel gives me: > > > > atapci1: port > > 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f mem > > 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0 > > ata2: at channel 0 on atapci1 > > ata3: at channel 1 on atapci1 > > ... > > ada0 at ata2 bus 0 scbus2 target 0 lun 0 > > ada0: ATA-7 device > > ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) > > ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C) > > ... > > (cd2:ata3:0:0:0): got CAM status 0x50 > > (cd2:ata3:0:0:0): fatal error, failed to attach to device > > (cd2:ata3:0:0:0): lost device, 4 refs > > (cd2:ata3:0:0:0): removing device entry > > ... > > > > Attaching the CDROM drive to the controller that is integrated on > > the mainboard (Intel PIIX4 UDMA33 controller) does not show this > > problem (but here I don't have UDMA66). > > > > It also works when not using ATA_CAM: > > > > ... > > acd0: DVDR at ata3-master UDMA66 > > ... > > > > So this semes to be a problem with the Promise controller and ATA_CAM. > > > > Any ideas? Or should I file PR? > > The controller in question is a Promise Ultra100 TX2. Right. Tried with an Ultra133, same effect. > > The error message comes from sys/cam/scsi/scsi_cd.c, in function > cddone(). The logic is a little hard for me to follow (I understand > about 70% of it). Look at lines 1724 to 1877 for stable/9. > > 1. Can you provide full output from a verbose boot when the CD/DVD drive > is attached to the Promise controller? Attached below. I have just filtered out some ahc cruft... Later I will try to boot a -current kernel -- just to see how this behaves... > > 2. What firmware version the card is using? The PDC20268 had many, many > firmware problems relating to ATAPI devices. It is the latest BIOS: 2.20.0.15. > > 3. I wouldn't worry about ATA66 vs. ATA33; this drive can only support > up to about 22MBytes/second so ATA66 isn't going to get you anything, > so as a workaround, using the PIIX4 for it would not hurt you. Probably. But I already had cdrecord complain when it came to the funky DMA speed test it is doing. It went away when using the UDMA66 port. And on the other hand I sometimes use the PIIX4 port for other stuff and I do not want to attach the cdrom to the slave port. > > 4. ONLY if this turns out to be a "controller thing": I'm not sure how > much effort should be spent trying to make this work, as the PDC20268 is > legacy/deprecated hardware (made/released 13 years ago). The whole box is more than 13 years old (good old Asus BX board) ;-) But since it worked in 7.4-STABLE I feel that this is some kind of regression. I do not want to waste anyone's resources in fixing it -- just if someone is curious and/or has an idea how to fix it... And here is the dmesg: Copyright (c) 1992-2013 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 9.1-STABLE #6: Wed Apr 17 07:56:57 CEST 2013 r...@server.ofw.tld:/usr/obj/src/src-9/sys/bratfix i386 gcc version 4.2.1 20070831 patched [FreeBSD] Preloaded elf kernel "/boot/kernel/kernel" at 0xc097d000. Calibrating TSC clock ... TSC clock: 1405298309 Hz CPU: Intel(R) Celeron(TM) CPU1400MHz (1405.30-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Family = 0x6 Model = 0xb Stepping = 1 Features=0x383f9ff Instruction TLB: 4 KB pages, 4-way set associative, 32 entries Instruction TLB: 4 MB pages, fully associative, 2 entries Data TLB: 4 KB pages, 4-way set associative, 64 entries 2nd-level cache: 256 KB, 8-way set associative, 32 byte line size 1st-level instruction cache: 16 KB, 4-way set associative, 32 byte line size Data TLB: 4 MB Pages, 4-way set associative, 8 entries 1st-level data cache: 16 KB, 4-way set associative, 32 byte line size real memory = 268435456 (256 MB) Physical memory chunk(s): 0x1000 - 0x0009dfff, 643072 bytes (157 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c26000 - 0x0fb18fff, 250556416 bytes (61171 pages) avail memory = 253022208 (241 MB) bios32: Found BIOS32 Service Directory header at 0xc00f92a0 bios32: Entry = 0xf06c0 (c00f06c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0x8c0 pnpbios: Found PnP BIOS data at 0xc00fc240 pnpbios: Entry = f:c270 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ULE: setup cpu 0 random: cpuctl:
