Re: warnings while kernel build
, 23.10.2003, 02:13, Doug White : On Wed, 22 Oct 2003, Vladimir B. Grebenschikov wrote: While build kernel on RELENG_4 machine I have following warnings (they prevent success build unless -Werror disabled) Is there some reason you're trying to compile RELENG_4 with gcc 3.3, which won't work? I am trying to compile -CURRENT code on RELENG_4 machine, with native RELENG_4 gcc: % gcc -v Using builtin specs. gcc version 2.95.4 20020320 [FreeBSD] % which gcc /usr/bin/gcc % pkg_glob gcc\* % /ext/current/src# make -j8 buildkernel ... /ext/current/src/sys/kern/kern_descrip.c:1914: warning: inlining failed in call to `_fgetvp' makeoptions CONF_CFLAGS=-O3 -mcpu=pentiumpro This is an unsupported option. Do not compile the kernel with any optimization beyond -O. This might be the other reason why you are getting these inlining warnings. Ok, But it works for me from 5.0 branching (or about). gcc -v? 2.95.4 20020320 [FreeBSD] -- 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: usbd doesn't get DEVICE_DETACH? (plus patch for typo in usbd.c)
, 24.10.2003, 00:01, Vladimir B. Grebenschikov : , 21.10.2003, 10:45, Johny Mattsson : Hi all, Me too ! kern/46488 I will check your patch. Yes, patch works, Thanx, please commit and close PR. Now I can get rid of hack in usbd.conf: --- # hack to workaround no keyboard detach event device HUB devname uhub[0-9]+ detach /usr/sbin/kbdcontrol -k /dev/kbd0 /dev/console --- BACKGROUND: After a recent purchase of a Palm Tungsten W, I've been spending a few hours getting the synchronization working in FreeBSD (which hasn't been an easy task). I've almost got it all up and running, by using a PPP over Serial over USB setup, but I have a small problem remaining. THE PROBLEM: Basically, what's happening is this: When I initiate the sync on the Palm, it lights up the USB port and a /dev/ucom0 is created for me. My usbd then launches a ppp instance for that port, as well as the service daemon for the Palm device. This is all well and wonderful. However, when the sync is complete, the Palm closes down the USB port (to be expected), and /dev/ucom0 is removed. The problem is that the usbd only sees a DRIVER_DETACH, not a DEVICE_DETACH message, and because of that, it doesn't execute the detach statement for ucom0 (in my case, to shut down ppp and the service daemon). The net effect is that I get a ppp hanging around and getting in the way for the next sync. SPECIFIC QUESTION: What I'd like to know is whether usbd should pick up on the implicit device detach in the DRIVER_DETACH event (probably won't work if there's more than one device hanging off the driver detaching), or if there should indeed be a DEVICE_DETACH arriving before the DRIVER_DETACH? If I read usb.c correctly, it appears that when a detach event is posted, any events in the queue with the same cookie will be discarded. Is this intended behaviour, or should DEVICE_DETACH messages be left in the queue for normal processing? For me it would make more sense if they were kept, but I don't have any previous exposure to this code, so I'm not an authoritative voice exactly. As can be see in the trace below, the DRIVER_DETACH event does contain the device name, so it would be easy to modify usbd to handle this scenario as well. It doesn't feel like a very elegant way to do things, though, and as I mentioned above, it probably can't deal with the case where there's more than one device handing off the detaching driver. If someone points out what would be the preferred way of resolving this, I'm happy to get a patch happening. Trace showing that there's no device-detach picked up by usbd: usbd: processing event queue on /dev/usb usbd: driver-attach event cookie=3217029324 devname=ucom0 USB_EVENT_DRIVER_ATTACH usbd: processing event queue on /dev/usb usbd: device-attach event at 1066715435.318666000, Palm Handheld, Palm, Inc.: vndr=0x0830 prdct=0x0031 rlse=0x0100 clss=0x subclss=0x prtcl=0x device names: ucom0 usbd: ucom0 matches ucom0 usbd: Found action 'Palm Tungsten W' for Palm Handheld, Palm, Inc. at ucom0 usbd: action 0: Palm Tungsten W vndr=0x0830 prdct=0x0031 devname: ucom0 attach='/usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0' detach='killall ppp; killall pi-csd' usbd: Setting DEVNAME='ucom0' usbd: Executing '/usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0' Working in auto mode Using interface: tun0 /usr/local/bin/pi-csd(50923): Connection Service Daemon for Palm Computing(tm) device active. /usr/local/bin/pi-csd(50923): Accepting connection requests for 'sarah' at 192.168.2.3 with mask 255.255.255.0. /usr/local/bin/pi-csd(50923): Connection from [192.168.2.253], req 'sarah', 192.168.2.3, 255.255.255.0 = accept. /usr/local/bin/pi-csd(50923): Connection from [192.168.2.253], req 'sarah', 192.168.2.3, 255.255.255.0 = accept. /usr/local/bin/pi-csd(50923): Connection from [192.168.2.253], req 'sarah', 192.168.2.3, 255.255.255.0 = accept. Terminated usbd: '/usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0' returned 143 usbd: driver-detach event cookie=3217029324 devname=ucom0 USB_EVENT_DRIVER_DETACH usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 Oh, and there's a typo in usbd.c too, it's printing DETACH when the event is ATTACH. One-line patch to fix this is ATTACHed (pun intended). Cheers, /Johny -- 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: warnings while kernel build
, 23.10.2003, 22:33, David O'Brien : On Thu, Oct 23, 2003 at 02:41:58PM +0400, Vladimir B. Grebenschikov wrote: ? ??, 23.10.2003, ? 02:13, Doug White ?: On Wed, 22 Oct 2003, Vladimir B. Grebenschikov wrote: While build kernel on RELENG_4 machine I have following warnings (they prevent success build unless -Werror disabled) Is there some reason you're trying to compile RELENG_4 with gcc 3.3, which won't work? I am trying to compile -CURRENT code on RELENG_4 machine, with native RELENG_4 gcc: % gcc -v Using builtin specs. gcc version 2.95.4 20020320 [FreeBSD] % which gcc /usr/bin/gcc Install the GCC 3.3 port on your 4.x system and use CC=gcc33 make when building the 5-CURRENT kernel sources. Looks like bad idea, with native gcc I can simple ignore warnings, but with gcc33 it fails on depend stage: # env CC=/usr/local/bin/gcc33 make KERNCONF=VBOOK buildkernel | tee ~/build.report33 ... if [ -f .depend ]; then mv .depend .olddep; fi /usr/obj/ext/current/src/make.i386/make _kernel-depend /usr/local/bin/gcc33 -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. -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 -finline-limit=15000 -fno-strict-aliasing -O -mcpu=pentiumpro -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wno-inline /ext/current/src/sys/i386/i386/genassym.c cc1: error: invalid option `no-align-long-strings' *** Error code 1 Stop in /usr/obj/ext/current/src/sys/VBOOK. *** 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. # -- 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: usbd doesn't get DEVICE_DETACH? (plus patch for typo in usbd.c)
, 21.10.2003, 10:45, Johny Mattsson : Hi all, Me too ! kern/46488 I will check your patch. BACKGROUND: After a recent purchase of a Palm Tungsten W, I've been spending a few hours getting the synchronization working in FreeBSD (which hasn't been an easy task). I've almost got it all up and running, by using a PPP over Serial over USB setup, but I have a small problem remaining. THE PROBLEM: Basically, what's happening is this: When I initiate the sync on the Palm, it lights up the USB port and a /dev/ucom0 is created for me. My usbd then launches a ppp instance for that port, as well as the service daemon for the Palm device. This is all well and wonderful. However, when the sync is complete, the Palm closes down the USB port (to be expected), and /dev/ucom0 is removed. The problem is that the usbd only sees a DRIVER_DETACH, not a DEVICE_DETACH message, and because of that, it doesn't execute the detach statement for ucom0 (in my case, to shut down ppp and the service daemon). The net effect is that I get a ppp hanging around and getting in the way for the next sync. SPECIFIC QUESTION: What I'd like to know is whether usbd should pick up on the implicit device detach in the DRIVER_DETACH event (probably won't work if there's more than one device hanging off the driver detaching), or if there should indeed be a DEVICE_DETACH arriving before the DRIVER_DETACH? If I read usb.c correctly, it appears that when a detach event is posted, any events in the queue with the same cookie will be discarded. Is this intended behaviour, or should DEVICE_DETACH messages be left in the queue for normal processing? For me it would make more sense if they were kept, but I don't have any previous exposure to this code, so I'm not an authoritative voice exactly. As can be see in the trace below, the DRIVER_DETACH event does contain the device name, so it would be easy to modify usbd to handle this scenario as well. It doesn't feel like a very elegant way to do things, though, and as I mentioned above, it probably can't deal with the case where there's more than one device handing off the detaching driver. If someone points out what would be the preferred way of resolving this, I'm happy to get a patch happening. Trace showing that there's no device-detach picked up by usbd: usbd: processing event queue on /dev/usb usbd: driver-attach event cookie=3217029324 devname=ucom0 USB_EVENT_DRIVER_ATTACH usbd: processing event queue on /dev/usb usbd: device-attach event at 1066715435.318666000, Palm Handheld, Palm, Inc.: vndr=0x0830 prdct=0x0031 rlse=0x0100 clss=0x subclss=0x prtcl=0x device names: ucom0 usbd: ucom0 matches ucom0 usbd: Found action 'Palm Tungsten W' for Palm Handheld, Palm, Inc. at ucom0 usbd: action 0: Palm Tungsten W vndr=0x0830 prdct=0x0031 devname: ucom0 attach='/usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0' detach='killall ppp; killall pi-csd' usbd: Setting DEVNAME='ucom0' usbd: Executing '/usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0' Working in auto mode Using interface: tun0 /usr/local/bin/pi-csd(50923): Connection Service Daemon for Palm Computing(tm) device active. /usr/local/bin/pi-csd(50923): Accepting connection requests for 'sarah' at 192.168.2.3 with mask 255.255.255.0. /usr/local/bin/pi-csd(50923): Connection from [192.168.2.253], req 'sarah', 192.168.2.3, 255.255.255.0 = accept. /usr/local/bin/pi-csd(50923): Connection from [192.168.2.253], req 'sarah', 192.168.2.3, 255.255.255.0 = accept. /usr/local/bin/pi-csd(50923): Connection from [192.168.2.253], req 'sarah', 192.168.2.3, 255.255.255.0 = accept. Terminated usbd: '/usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0' returned 143 usbd: driver-detach event cookie=3217029324 devname=ucom0 USB_EVENT_DRIVER_DETACH usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 Oh, and there's a typo in usbd.c too, it's printing DETACH when the event is ATTACH. One-line patch to fix this is ATTACHed (pun intended). Cheers, /Johny -- 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]
warnings while kernel build
ugen #device uhid #device ukbd #device ulpt #device umass #device ums #device firewire #device fwohci #device sbp # prevent memory corruption (?) options DISABLE_PSE options DISABLE_PG_G == -- 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]
fsck_ufs -B lockup any writes on filesystem
Hi After unclean shutdown, system boots and work properly. After some time any processes triing to write was blocked in suspfs state. fsck_ufs process was blocked in suspwt state. Killing blocked processes does not helps. # ps alx | fgrep fsck_ufs 0 917 736 0 75 0 676 268 suspwt D ??0:00.91 fsck_ufs -p -B /dev/ad0s3f # strace -p 917 mount(0x80af3d3, 0x80cb44c, 0x1211000, 0xbfbffcc0^C unfinished ... ^C # ps alx | fgrep suspfs 0 559 1 0 75 0 7076 1588 suspfs Is??0:01.92 /usr/local/sbin/cupsd 207 611 609 0 75 0 8832 2396 suspfs I ??0:00.11 /usr/X11R6/bin/gdm-binary 207 836 1 0 75 0 18000 9108 suspfs I ??0:02.33 /usr/X11R6/libexec/stickynotes_applet 207 865 1 2 75 0 55932 41028 suspfs I ??1:59.49 evolution-1.4 207 867 1 0 75 0 32296 16000 suspfs I ??0:22.15 /usr/X11R6/share/opera/bin/opera --bi 207 942 1 0 75 0 4120 2068 suspfs I p0- 0:00.04 licq I can cure situation only be running fsck -y in single-user mode. PR: kern/58060 -- 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: fsck_ufs -B lockup any writes on filesystem
, 15.10.2003, 17:31, Robert Watson : On Wed, 15 Oct 2003, Vladimir B. Grebenschikov wrote: After unclean shutdown, system boots and work properly. After some time any processes triing to write was blocked in suspfs state. fsck_ufs process was blocked in suspwt state. I reported an identical set of symptoms over the weekend to Kirk and Jeff, and a fix was committed as src/sys/kerne/vfs_bio.c:1.412. A missing write lock release in buffer cache locking work would leave the disk suspended for writes, and the result is a file system deadlock just as you describe. Could you check and see which version of vfs_bio.c you're running with -- if it's the earlier version, try updating? If it's the newer version, please let me know. Here's the commit message: Date: Mon, 13 Oct 2003 17:38:35 -0700 (PDT) From: Jeff Roberson [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/sys/kern vfs_bio.c jeff2003/10/13 17:38:35 PDT FreeBSD src repository Modified files: sys/kern vfs_bio.c Log: - Add a mising vn_finished_write() Pointy hat: jeff Found by: robert Obtained from: kirk Revision ChangesPath 1.412 +1 -0 src/sys/kern/vfs_bio.c I have old version 1.409. % cvs status sys/kern/vfs_bio.c === File: vfs_bio.c Status: Needs Patch Working revision: 1.409Mon Oct 6 11:35:04 2003 Repository revision: 1.412 /ext/ncvs/src/sys/kern/vfs_bio.c,v I will upgrade. -- 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: ATAng doesn't boot on my notebook - panic
, 08.10.2003, 12:04, Soren Schmidt : Does not help, another panic in ad_attach: ARGH, try this instead: Yes, it helps, thank you. -Sren -- 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: ATAng doesn't boot on my notebook - panic
, 07.10.2003, 23:26, Soren Schmidt : It seems Vladimir B. Grebenschikov wrote: Any solution or workaround ? Try this patch please: diff -u -r1.191 ata-all.c Does not help, another panic in ad_attach: ... GEOM: create disk ad1 dp=0xc2358a70 ad1: MEMORYSTICK 4M 8K/SONY1.00 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 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x6 fault code = supervisor read, page not present instruction pointer = 0x8:0xc047d801 stack pointer = 0x10:0xc0c21cf4 frame pointer = 0x10:0xc0c21d3c 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 12 trap, code=0 Stopped at ad_attach+0x61: movzbl 0x6(%edi),%ecx db tra ad_attach(c227d2d4,1,c1122c50,c074a990,c0c21d74) at ad_attach+0x61 ata_boot_attach(0,c0539736,c0768fec,0,c074a990) at ata_boot_attach+0x6f run_interrupt_driven_config_hooks(0,0,c1120708,c1120708,c1ec00) at run_interrupt_driven_config_hooks+0x2b mi_startup() at mi_startup+0xa1 begin() at begin+0x2c db full boot -v: OK boot -v /boot/kernel.soren/acpi.ko text=0x3b43c data=0x16cc+0xee0 syms=[0x4+0x6480+0x4+0x7fb5] SMAP type=01 base= len=0009f800 SMAP type=02 base=0009f800 len=0800 SMAP type=02 base=000e7800 len=00018800 SMAP type=01 base=0010 len=0bef SMAP type=03 base=0bff len=f800 SMAP type=04 base=0bfff800 len=0800 SMAP type=02 base=fffe7800 len=00018800 Copyright (c) 1992-2003 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 5.1-CURRENT #11: Wed Oct 8 03:00:25 MSD 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VBOOK Preloaded elf kernel /boot/kernel.soren/kernel at 0xc08a8000. Preloaded elf module /boot/kernel.soren/ums.ko at 0xc08a8208. Preloaded elf module /boot/kernel.soren/usb.ko at 0xc08a82b8. Preloaded elf module /boot/kernel.soren/ukbd.ko at 0xc08a8368. Preloaded elf module /boot/kernel.soren/snd_neomagic.ko at 0xc08a8418. Preloaded elf module /boot/kernel.soren/snd_pcm.ko at 0xc08a84d0. Preloaded elf module /boot/kernel.soren/acpi.ko at 0xc08a8584. Calibrating clock(s) ... i8254 clock: 1193111 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 331580921 Hz CPU: Pentium II/Pentium II Xeon/Celeron (331.58-MHz 686-class CPU) Origin = GenuineIntel Id = 0x66a Stepping = 10 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 201261056 (191 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c26000 - 0x0bc69fff, 184827904 bytes (45124 pages) avail memory = 185966592 (177 MB) bios32: Found BIOS32 Service Directory header at 0xc00f6c50 bios32: Entry = 0xfd7c0 (c00fd7c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd7c0+0x214 pnpbios: Found PnP BIOS data at 0xc00f6c80 pnpbios: Entry = f:b5d4 Rev = 1.0 Other BIOS signatures found: random: entropy source mem: memory I/O Pentium Pro MTRR support enabled null: null device, zero device npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: SONY Z0 on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x80003b54 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71928086) pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fdf50 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded01A 0x60 9 embedded01B 0x61 9 embedded01C 0x62 9 embedded01D 0x63 9 embedded07D 0x63 9 embedded08A 0x60 9 embedded08B 0x61 9 embedded09A 0x62 9 embedded0 10A 0x61 9 embedded0 11A 0x60 9 embedded06A 0x60 9 AcpiOsDerivePciId: bus 0 dev 7 func 2 AcpiOsDerivePciId: bus 0 dev 10 func 0 AcpiOsDerivePciId: bus 0 dev 7 func 0 acpi0: Power Button (fixed) ACPI timer looks BAD min = 2, max = 8, width = 6 ACPI timer looks BAD min = 2, max = 8, width = 6 ACPI timer looks BAD min = 2, max = 8, width = 6 ACPI timer looks BAD min = 3, max = 16777202, width = 16777199 ACPI timer looks BAD min = 3, max = 8, width = 5 ACPI timer looks BAD min = 3, max = 9, width = 6 ACPI timer looks BAD min = 2, max = 8, width = 6 ACPI timer looks BAD min = 0, max = 8, width = 8 ACPI timer looks BAD
Re: ATAng doesn't boot on my notebook - panic
, 06.10.2003, 22:48, Vladimir B. Grebenschikov :
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.
I have workarounded problem by disabling slave ATA devices
(I have no slaves so it is acceptable for me):
RCS file: /ext/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.190
diff -u -r1.190 ata-all.c
--- sys/dev/ata/ata-all.c 27 Sep 2003 12:00:58 - 1.190
+++ sys/dev/ata/ata-all.c 6 Oct 2003 19:00:14 -
@@ -577,11 +577,12 @@
ata_identify_devices(struct ata_channel *ch)
{
if (ch-devices ATA_ATA_SLAVE) {
- if (ata_getparam(ch-device[SLAVE], ATA_ATA_IDENTIFY))
+/* if (ata_getparam(ch-device[SLAVE], ATA_ATA_IDENTIFY)) */
ch-devices = ~ATA_ATA_SLAVE;
#ifdef DEV_ATADISK
- else
- ch-device[SLAVE].attach = ad_attach;
+/* else
+ ch-device[SLAVE].attach = ad_attach;
+*/
#endif
}
if (ch-devices ATA_ATAPI_SLAVE) {
In short:
ad0: setting UDMA33 on Intel PIIX4 chip
GEOM: create disk ad0 dp=0xc1d00970
ad0: TOSHIBA MK4019GAX/FA002D 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=51READY,DSC,ERROR error=4ABORTED
ad1: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED
ad1: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED
ad1: FAILURE setting PIO1 on Intel PIIX4 chip
GEOM: create disk ad1 dp=0xc1d4b770
ad1: MEMORYSTICK 4M 8K/SONY1.00 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]
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]
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]
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: TOSHIBA MK4019GAX/FA002D 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=51READY,DSC,ERROR error=4ABORTED ad1: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED ad1: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED ad1: FAILURE setting PIO1 on Intel PIIX4 chip GEOM: create disk ad1 dp=0xc1d4b770 ad1: MEMORYSTICK 4M 8K/SONY1.00 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]
gkrellm and libthr
Hi Just tried run gnome-2.4 desktop with: % cat /etc/libmap.conf libc_r.so.5 libthr.so.1 libc_r.solibthr.so All seems smooth so far, but gkrellm. First it works right (creates some threads) Then system time consumed became all available CPU power (by systat -vm) When I have kill gkrellm all returns to normal operation. It is reproducible effect. -- 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]
GEOM-related problem sysutils/diskcheckd does not work
Submitter-Id: current-users Originator:Vladimir B. Grebenschikov Organization: SWsoft Confidential: no Synopsis: GEOM-related problem sysutils/diskcheckd does not work Severity: non-critical Priority: low Category: ports Class: sw-bug Release: FreeBSD 5.0-CURRENT i386 Environment: System: FreeBSD vbook.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #12: Wed Nov 27 16:18:57 MSK 2002 [EMAIL PROTECTED]:/usr/obj/usr/local/src/sys/VBOOK i386 # pkg_info -I diskcheckd\* diskcheckd-20010823_3 Daemon to check for disk read errors # Description: It seem there are some problems with accessing HDD through GEOM: # egrep -v \^# /usr/local/etc/diskcheckd.conf /dev/ad0* 28 * # diskcheckd # tail /var/log/messages ... Dec 2 12:46:50 vbook diskcheckd[1444]: DIOCGDINFO on /dev/ad0 failed: Operation not supported by device # strace /usr/local/sbin/diskcheckd -d ... open(/dev/ad0, O_RDONLY) = 3 ioctl(3, DIOCGDINFO, 0xbfbff250)= -1 ENODEV (Operation not supported by device) ... When I have change /dev/ad0 in config file to /dev/ad0s2c it work. But I want to check integrity of all drive, not only FreeBSD part. How-To-Repeat: Just run diskcheckd on post-GEOM CURRENT. Fix: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
short uid/gid
Hi
I have found that SysVIPC functions uses structure with short uid/gid types.
What is valid solution ?
Change types to uid_t/gid_t (but this will broke binary compatibility)
Change syscalls to old_* and add new with right structures,
or something else ?
struct ipc_perm {
ushort cuid; /* creator user id */
ushort cgid; /* creator group id */
ushort uid;/* user id */
ushort gid;/* group id */
ushort mode; /* r/w permission */
ushort seq;/* sequence # (to generate unique msg/sem/shm id) */
key_t key;/* user specified msg/sem/shm key */
};
--
Vladimir B. Grebenschikov
[EMAIL PROTECTED], SWsoft, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Have random panic somewhere near console driver on fresh current
Submitter-Id: [EMAIL PROTECTED] Originator:Vladimir B. Grebenschikov Organization: SWsoft Confidential: no Synopsis: Have random panic somewhere near console driver on fresh current Severity: critical Priority: high Category: kern Class: sw-bug Release: FreeBSD 5.0-CURRENT i386 Environment: System: FreeBSD vbook.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Wed Jun 5 17:36:46 MSD 2002 [EMAIL PROTECTED]:/usr/local/src/sys/i386/compile/VBOOK i386 gdm runned from /etc/ttys by init gnome environment xconsole runned both by gdm on login screen and by gnome-session after login dmesg.boot: Copyright (c) 1992-2002 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 5.0-CURRENT #2: Wed Jun 5 17:36:46 MSD 2002 [EMAIL PROTECTED]:/usr/local/src/sys/i386/compile/VBOOK Preloaded elf kernel /boot/kernel/kernel at 0xc0468000. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04680b4. Preloaded elf module /boot/kernel/snd_neomagic.ko at 0xc0468160. Preloaded elf module /boot/kernel/ukbd.ko at 0xc0468214. Preloaded elf module /boot/kernel/usb.ko at 0xc04682c0. Preloaded elf module /boot/kernel/ums.ko at 0xc0468368. Preloaded elf module /boot/kernel/acpi.ko at 0xc0468410. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 331580917 Hz CPU: Pentium II/Pentium II Xeon/Celeron (331.58-MHz 686-class CPU) Origin = GenuineIntel Id = 0x66a Stepping = 10 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 201261056 (196544K bytes) avail memory = 190615552 (186148K bytes) Pentium Pro MTRR support enabled Using $PIR table, 7 entries at 0xc00fdf50 npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_button0: Power Button on acpi0 acpi_pcib0: Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 pci0: network, ethernet at device 6.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xfca0-0xfcbf irq 9 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 4 ports with 4 removable, self powered ums0: Microsoft Microsoft IntelliMouse\M-. Explorer, rev 1.10/1.14, addr 3, iclass 3/1 ums0: 5 buttons and Z dir. ukbd0: Behavior Tech. Computer Keyboard with mouse port, rev 1.00/1.00, addr 4, iclass 3/1 kbd1 at ukbd0 ums1: Behavior Tech. Computer Keyboard with mouse port, rev 1.00/1.00, addr 4, iclass 3/1 ums1: 3 buttons intpm0: Intel 82371AB Power management controller port 0x2180-0x218f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 2180 intpm0: intr IRQ 9 enabled revision 0 smbus0: System Management Bus on intsmb0 smb0: SMBus generic I/O on smbus0 intpm0: PM I/O mapped 8000 pci0: display, VGA at device 8.0 (no driver attached) pcm0: NeoMagic 256AV mem 0xfea0-0xfeaf,0xfe00-0xfe3f irq 9 at device 8.1 on pci0 pci0: serial bus, FireWire at device 9.0 (no driver attached) acpi_pcib0: device is routed to IRQ 9 pcic0: Ricoh RL5C475 PCI-CardBus Bridge irq 9 at device 10.0 on pci0 pcic0: PCI Memory allocated: 0x4400 pccard0: PC Card bus (classic) on pcic0 pci0: simple comms at device 11.0 (no driver attached) atspeaker0 port 0x61 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console sio1 port 0x140-0x147,0x3e8-0x3ef irq 10 drq 0 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 acpi_cmbat0: Control method Battery on acpi0 acpi_acad0: AC adapter on acpi0 orm0: Option ROMs at iomem 0xdc000-0xd,0xc-0xcbfff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec IP packet filtering
gdb do not work with gcc-3.1
Submitter-Id: current-users
Originator:Vladimir B. Grebenschikov
Organization: SWsoft
Confidential: no
Synopsis: gdb do not work with gcc-3.1
Severity: serious
Priority: high
Category: bin
Class: sw-bug
Release: FreeBSD 5.0-CURRENT i386
Environment:
System: FreeBSD vbook.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri May 17
13:42:09 MSD 2002 [EMAIL PROTECTED]:/usr/obj/usr/local/src/sys/VBOOK i386
make world done at May 16.
Description:
GDB do not work with strange diagnostic:
Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.
How-To-Repeat:
vbook:/home/vova/src 164_ cat aa.c
#include stdio.h
main()
{
printf(hello world\n);
}
^D
vbook:/home/vova/src 165_ gcc -g aa.c
vbook:/home/vova/src 166_ gdb a.out
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...
Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.
(gdb) b main
No symbol table is loaded. Use the file command.
(gdb) r
Starting program:
/usr/local/home/vova/src/a.out
hello world
(no debugging symbols found)...(no debugging symbols found)...
Program exited with code 015.
(gdb) q
vbook:/home/vova/src 167_ gdb --version
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.
vbook:/home/vova/src 168_ gcc --version
gcc (GCC) 3.1 [FreeBSD] 20020509 (prerelease)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Fix:
Get GCC before 3.1
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
libpng port makes bad dynamic library on -CURRENT
Submitter-Id: current-users
Originator:Vladimir B. Grebenschikov
Organization: SWsoft
Confidential: no
Synopsis: libpng port makes bad dynamic library on -CURRENT
Severity: non-critical
Priority: medium
Category: ports
Class: sw-bug
Release: FreeBSD 5.0-CURRENT i386
Environment:
System: FreeBSD vbook.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #42: Wed Feb 13
14:57:29 MSK 2002 [EMAIL PROTECTED]:/usr/obj/ext/current/src/sys/VBOOK i386
Todays current:
% date
Wed Feb 13 14:32:09 GMT 2002
% pkg_info -I png\*
png-1.2.1 Library for manipulating PNG images
%
Description:
Programm linked against libpng.so on -CURRNET causes SIGBUS on startup
How-To-Repeat:
% cat trypng.c
#include stdio.h
main(int ac, char ** av)
{
printf(Hello World\n);
}
^D
% gcc -o trypng trypng.c -L/usr/local/lib -lpng
% ./trypng
Bus error (core dumped)
% ldd ./trypng
./trypng:
libpng.so.5 = lib/xx/libpng.so.5 (0x28068000)
libc.so.5 = /usr/lib/libc.so.5 (0x2808a000)
libz.so.2 = /usr/lib/libz.so.2 (0x2813d000)
libm.so.2 = /usr/lib/libm.so.2 (0x2814a000)
% gdb ./trypng
GNU gdb 4.18
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...
(no debugging symbols found)...
(gdb) r
Starting program: ./trypng
Program received signal SIGBUS, Bus error.
0x280500e2 in ?? ()
(gdb) bt
#0 0x280500e2 in ?? ()
#1 0x2804db7c in ?? ()
#2 0x2804c6af in ?? ()
(gdb)
Fix:
Workaround - build libpng on 4.5-RELEASE system and install package on
5.0-CURRENT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
[SUGGESTION] - disallowing shutdown after su(1)
Hiten Pandya writes: hi all, correct me if i am wrong.. but.. do you think, if we denied a shutdown after an su(1) to root from a non-privileged user would be good... i tried this same thing at home.. i builded it and installed it.. works fine for me... the patch below will allow a shutdown only be logging into root itself and not by issuing an su(1) command to root. this would be very good, i think if someone broke into a normal user and was able to gain access into root using su... (without a password..) i am submitting a tar.gz file, which has the patch for the shutdown.8 manpage, and shutdown.c located at.. src/sbin/shutdown.c... I think this idea have no any sence because beeing root you CAN shutdown machine not depending on how you became root. few examples: # kill -USR2 (see init(8) - halt) build fresh shutdown halt -q so ... thanks... = regards, Hiten Pandya [EMAIL PROTECTED] http://geocities.com/hitmaster2k Guys!... stay away from Einstein Junior! __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vmware fails on -current
Hellmuth Michaelis writes: Today i got it to compile and run: - apply the patch from Munehiro Matsuda to hostif.c, this makes the vmware2 port compile under -current as of today - as described above, use /dev/vmnet1 instead of /compat/linux/dev/vmnet1 in /usr/local/etc/rc.d/vmware.sh - replace /compat/linux/dev/vmnet1 with a symlink to /dev/vmnet1 (perhaps the previous step would be unnecessary by this one) After this, vmware comes up and then complains about not able to use /dev/rtc (/dev/rtc is present in /compat/linux and is kld-loaded) but then continues to start up and runs. One thing which looks funny to me is this that the vmnet1 device files have different minor numbers: ROOT@bert/root ll /usr/compat/linux/dev/vmnet1-BAK /dev/vmnet1 crw--- 1 root wheel 149, 0x0081 Nov 20 18:50 /dev/vmnet1 crw-rw-rw- 1 root wheel 149, 0x00010001 Nov 20 18:42 /usr/compat/linux/dev/vmnet1-BAK (where /usr/compat/linux/dev/vmnet1-BAK is from the vmware2 port install and moved from vmnet1 to vmnet1-BAK before the new symlink was made). After all, after block disk devices was removed wmvare stops support plain disks :(. Do anybody have solution for it ? hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Need help with 5.0-CURRENT on Sony VAIO Z505s
Warner Losh writes: In message [EMAIL PROTECTED] Vladimir B. Grebenschikov writes: : - pccard: : : Only way to use any pccard device is to insert it before poweron : If I try to insert or eject card on the fly system completely freezes. : : If I've power-up with card inserted some device (two different ATA : CDROMs) I have significant (20-40s) freeze while booting (after : pccardd starts) but after it device is detected and works without : problem. (This problem not related to my Orinco WaveLan card) : : it work right on 4.3 OLDCARD or NEWCARD? kernel config: machine i386 ident VBOOK maxusers256 options INCLUDE_CONFIG_FILE # Include this file in kernel cpu I486_CPU cpu I586_CPU # aka Pentium(tm) cpu I686_CPU # aka Pentium Pro(tm) options COMPAT_43 makeoptions CONF_CFLAGS=-O3 -mpentiumpro #makeoptions CONF_CFLAGS=-fno-builtin #Don't allow use of memcmp, etc. #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols #makeoptionsKERNEL=foo #Build kernel foo and install /foo options SYSVSHM options SYSVSEM options SYSVMSG options UCONSOLE #optionsUSERCONFIG #boot -c editor #optionsVISUAL_USERCONFIG #visual boot -c editor options INET#Internet communications protocols device ether #Generic Ethernet device loop#Network loopback device device bpf 4 #Berkeley packet filter #device vlan4 device snp 4 #Snoop device - to look at pty/vty/etc.. options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) options MROUTING# Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support #optionsIPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPDIVERT#divert sockets options DUMMYNET options FFS #Fast filesystem options NFSSERVER #Network File System - server options NFSCLIENT #Network File System - client # options NFS_NOSERVER#Disable the NFS-server code. options PROCFS #Process filesystem options SOFTUPDATES # Allow this many swap-devices. device scbus #base SCSI code device da #SCSI direct access devices (aka disks) device sa #SCSI tapes device cd #SCSI CD-ROMs device pass#CAM passthrough driver options SCSI_DELAY=2000 device pty 32 #Pseudo ttys - can go as high as 256 device speaker #Play IBM BASIC-style noises out your speaker device gzip#Exec gzipped a.out's device md # Memory disks device isa device atkbdc device atkbd 1 device psm device vga device sc options MAXCONS=16 # number of virtual consoles options SC_DFLT_FONT# compile font in makeoptions SC_DFLT_FONT=cp866-vio options SC_HISTORY_SIZE=1024# number of history buffer lines #optionsSC_DISABLE_REBOOT # disable reboot key sequence device npx device aha device ata device atadisk# ATA disk drives device atapicd# ATAPI CDROM drives device atapifd# ATAPI floppy drives device atapist# ATAPI tape drives #optionsATA_STATIC_ID #Static dev number like old wd driver #optionsIDE_DELAY=2000 # Be optimistic about Joe IDE device device fdc device sio device apm device pci device smbus device intpm device smb device iicbus device iicbb device ic device iic device iicsmb device ppbus device vpo device lpt device plip device ppi #device pps device lpbb device ppc #optionsCOMPAT_LINUX options EXT2FS options KTRACE #kernel tracing options DDB device pcic device card device wi device random options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L #device acpica #options ACPI_DEBUG options KBD_INSTALL_CDEV
Re: Need help with 5.0-CURRENT on Sony VAIO Z505s
Juriy Goloveshkin writes: On Sat, Nov 10, 2001 at 12:12:25AM +0300, Vladimir B. Grebenschikov wrote: Content-Description: message body text If you want to have suspend/wakeup, you should disable acpi-stuff(it is buggy for all time I've tried to use it). echo hint.acpi.0.disable=1 /boot/device.hints reboot maybe it will work. It not helps, acpi now turned off, but after resume box completle freezed :( After upgrade to -CURRENT I start experience following problems: - pccard: Only way to use any pccard device is to insert it before poweron If I try to insert or eject card on the fly system completely freezes. If I've power-up with card inserted some device (two different ATA CDROMs) I have significant (20-40s) freeze while booting (after pccardd starts) but after it device is detected and works without problem. (This problem not related to my Orinco WaveLan card) it work right on 4.3 - reboot or Ctrl-Alt-Del shutdowns OS but after it notebook not reboots it remains completely freezes and not react on power key hold 10sec, so I need plug off AC power and battery to reboot notebook. it work right on 4.3 - shutdown -p does not work (I have both acpi and apm enabled) but pressing power key work perfect. shutdown -p work right on 4.3 - acpi: acpiconf -sX where X - 3/4/4b/5 turn off system without any shutdown at all - suspend and suspend to disk works both but after awake system shows right picture but seems completely freeze on 4.3 suspend to disk always work right and suspend sometimes broke some timer (CPU load 100% after resume) but works too my dmesg.boot: Content-Description: message body text my acpidump result Content-Description: message body text from my rc.conf: pccard_enable=YES pccardd_flags=-i 11 pccard_mem=0xd4000 pccard_conf=/etc/pccard.conf # pccardd(8) config file apm_enable=YES# Set to YES to enable APM BIOS functions (or NO). apmd_enable=YES # Run apmd to handle APM event from userland. apmd_flags= # Flags to apmd (if enabled). my sysctl hw: Content-Description: message body text # fgrep -v \# /etc/pccard.conf | head -n 5 io 0x240-0x360 irq 3 10 11 memory 0xd4000 96k Any help/comments will be very helpful, thank you. -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] -- bye Juriy Goloveshkin -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Firewire driver is updated
Katsushi Kobayashi writes: Hello, I have made a quick hack for SBP-2 (known as SCSI over firewire) for my driver code. I know this code is testted on my limited environment (only verified fat32 file system), and also lacks a lot of function, e.g. device detach and reconnect after busreset. However, I would like to use my effort to A/V functions of the firewire. So,I release the SBP-2 code for the start point of somebody who would loves storage on the firewire. The URL of the latest code is: ftp://ftp.uec.ac.jp/pub/firewire/beta/firewire-freebsd-5.0-20010918 Can't build fresh -CURRENT kernel with this patch: vbook#/usr/src.local/sys/i386/compile/VBOOK 168_ make kernel cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I/usr/include -D_KERNEL -include opt_global.h -elf -O3 -mpentiumpro -mpreferred-stack-boundary=2 ../../../dev/firewire/firewire.c ../../../dev/firewire/firewire.c:133: warning: initialization makes pointer from integer without a cast ../../../dev/firewire/firewire.c:142: conflicting types for `fw_open' ../../../dev/firewire/firewire.c:85: previous declaration of `fw_open' ../../../dev/firewire/firewire.c:170: conflicting types for `fw_close' ../../../dev/firewire/firewire.c:86: previous declaration of `fw_close' ../../../dev/firewire/firewire.c:698: conflicting types for `fw_ioctl' ../../../dev/firewire/firewire.c:87: previous declaration of `fw_ioctl' ../../../dev/firewire/firewire.c: In function `fw_rcv': ../../../dev/firewire/firewire.c:2129: warning: long unsigned int format, __uint32_t arg (arg 3) ../../../dev/firewire/firewire.c: In function `fw_vmaccess': ../../../dev/firewire/firewire.c:2247: warning: long unsigned int format, __uint32_t arg (arg 5) ../../../dev/firewire/firewire.c:2247: warning: long unsigned int format, __uint32_t arg (arg 6) ../../../dev/firewire/firewire.c:2247: warning: long unsigned int format, __uint32_t arg (arg 7) ../../../dev/firewire/firewire.c:2247: warning: long unsigned int format, __uint32_t arg (arg 8) ../../../dev/firewire/firewire.c:2248: warning: long unsigned int format, __uint32_t arg (arg 2) ../../../dev/firewire/firewire.c:2248: warning: long unsigned int format, __uint32_t arg (arg 3) ../../../dev/firewire/firewire.c:2248: warning: long unsigned int format, __uint32_t arg (arg 4) ../../../dev/firewire/firewire.c:2248: warning: long unsigned int format, __uint32_t arg (arg 5) *** Error code 1 Stop in /usr/src.local/sys/i386/compile/VBOOK. Any suggestions ? Will my Sony Firewire controller (in VAIO Z505S) work with these drivers ? # dmesg | grep FireWire pci0: serial bus, FireWire at device 9.0 (no driver attached) # sudo pciconf -l | grep pci0:9 none1@pci0:9:0: class=0x0c card=0x8054104d chip=0x8009104d rev=0x01 hdr=0x00 # -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
My Recommended Development/Testing environment for -current
Matt Dillon writes:
* On my -STABLE box I build the -current world. I usually
try to build it -DNOCLEAN but if that fails I just rebuild it from
scratch. NOTE!!! DO NOT ACCIDENTLY TRY TO INSTALL THE -CURRENT WORLD
ON YOUR STABLE BOX!!!
stable cd /FreeBSD/FreeBSD-current/src
stable make -DNOCLEAN -j 10 buildworld
* On my -STABLE box I build the -current kernel. Again I try to use
-DNOCLEAN to reduce [re]compilation times, but just build it from
scratch too some times. NOTE!!! DO NOT ACCIDENTLY TRY TO INSTALL
THE -CURRENT KERNEL ON YOUR STABLE BOX!!!
One problem - in such testing you newer see problems building world on
-CURRENT, so without below patch world not builds on my -CURRENT
--- src/gnu/usr.bin/perl/Makefile.inc.orig Thu May 31 15:04:52 2001
+++ src/gnu/usr.bin/perl/Makefile.inc Fri Sep 7 13:22:09 2001
@@ -41,7 +41,7 @@
done ;\
for i in `cd ${PERL5SRC}; find $${d} -type f | grep -v CVS` ;\
do \
- ln -s ${PERL5SRC}/$${i} $${i} ;\
+ ln -sf ${PERL5SRC}/$${i} $${i} ;\
done ;\
done
@ln -sf ${PERL5SRC}/ext/File/Glob/Glob.pm lib/File/Glob.pm
Sometime I am use a bit different scheme, on my -STABLE box I have cvsup and
source tree, it mounted through NFS to -CURRENT box read-only, and above it
mounted unionfs tree for building and changing sources.
-Matt
--
TSB Russian Express, Moscow
Vladimir B. Grebenschikov, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
non-present sched_yield
I have message kernel: cmd soffice.bin pid 4690 tried to use non-present sched_yield in logs triing to run staroffice on -CURRENT. But staroffice run fine, what about plans on implementing sched_yield() in kernel trhreads ? # uname -r 5.0-CURRENT # Aug 22 17:30:03 vbook /boot/kernel/kernel: cmd soffice.bin pid 4690 tried to use non-present sched_yield Aug 22 17:30:34 vbook last message repeated 1975 times Aug 22 17:31:14 vbook last message repeated 2036 times -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI on Sony VAIO z505s on fresh -CURRENT
Hi
Anybody tried subj ?
It compiles in, and seems to work:
Aug 17 14:16:58 vbook /boot/kernel/kernel: ACPI debug layer 0x0 debug level 0x0
Aug 17 14:16:59 vbook /boot/kernel/kernel: acpi0: PTLTDRSDT on motherboard
Aug 17 14:16:59 vbook /boot/kernel/kernel: acpi0: power button is handled as a fixed
feature programming model.
Aug 17 14:16:59 vbook /boot/kernel/kernel: Timecounter ACPI frequency 3579545 Hz
Aug 17 14:16:59 vbook /boot/kernel/kernel: acpi_cpu0: CPU on acpi0
Aug 17 14:16:59 vbook /boot/kernel/kernel: acpi_tz0: thermal zone on acpi0
Aug 17 14:16:59 vbook /boot/kernel/kernel: acpi_button0: Power Button on acpi0
Aug 17 14:16:59 vbook /boot/kernel/kernel: acpi_pcib0: Host-PCI bridge on acpi0
Aug 17 14:16:59 vbook /boot/kernel/kernel: pci0: PCI bus on acpi_pcib0
Aug 17 14:17:00 vbook /boot/kernel/kernel: acpi_pcib0: matched entry for 0.10.INTA
(source \_SB_.LNKB)
Aug 17 14:17:00 vbook /boot/kernel/kernel: acpi_pcib0: device is routed to IRQ 9
Aug 17 14:17:00 vbook /boot/kernel/kernel: acpi_cmbat0: Control method Battery on
acpi0
Aug 17 14:17:00 vbook /boot/kernel/kernel: acpi_acad0: AC adapter on acpi0
Aug 17 14:17:00 vbook /boot/kernel/kernel: acpi_timer0: 24-bit timer at 3.579545MHz
port 0x8008-0x800b on acpi0
Aug 17 14:17:01 vbook /boot/kernel/kernel: acpi_cpu0: set speed to 100.0%
Aug 17 14:17:01 vbook /boot/kernel/kernel: acpi_cpu: CPU throttling enabled, 8 steps
from 100% to 12.5%
acpidump - dumps a lot of information
But there are some problems with using acpi:
1st: it seems that acpi not emulates apm interface (/dev/{apm,apmctl}) so
apm-based utilites don't work (apmd, zzz, monitors and so)
Is it planned to have apm interface through acpi or not ?
If I compile both in kernel - apm code not works.
2nd: Where I can get more info about acpimodes, from man acpiconf(8):
-s type
Enters the specified sleep mode. Recognized types are 1, 2, 3,
4, and 5.
in man acpiconf(8) there are no mention about mode 4b
I have tried some:
1,2 - do nothing
5 - turn off machine without proper shutdown
3rd: I have tried couple utilites from http://people.freebsd.org/~jhb/acpi/
batt.c- works after patching, but if no battary present on laptop
shows 1 battary with unrealistic numbers
health.c - I can't make it work - it seems it lacks of defines in kernel
May be there are some other utilites for acpi ?
--
TSB Russian Express, Moscow
Vladimir B. Grebenschikov, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Interrupt messages from usb0 on CURRENT
Ollivier Robert writes: I just upgraded to the latest sources (two hours ago) on my VAIO laptop and I'm now getting dozens of messages: Aug 22 15:00:07 sidhe /boot/kernel/kernel: usb0: interrupt, but not for us Aug 22 15:00:51 sidhe last message repeated 8 times Aug 22 15:03:02 sidhe last message repeated 19 times Aug 22 15:12:59 sidhe last message repeated 92 times Have same problem on VAIO, on fresh sources. Any idea? I also got an error where pccardd tried to attach my pcmcia card two times -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
problem not single open() of '/dev/mixer' in -CURRENT
After ubgrade to -CURRENT I have found that it is not possible open mixer device twice and more. Second open gets EBUSY. It is usual practice that on there is more than one program on desktop opening mixer - for me it wmmixer, wmtune (both WindowMaker applets) and xmms or xmcd. Under RELENG_4 - there was no problem with it. Is it principial or conceptual problem ? I've fix it with small patch, but I want to understand why it so in -CURRENT ? -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
is 'suspend' broken in CURRENT?
Juriy Goloveshkin writes: I have sony vaio z505hs. I have latest cvs-tree. suspend worked 1-2 weeks ago but now when I want to resume from suspend-mode I see the same screen I saw before suspend but keyboard doesn't work and harddisk doesn't spin. Have same problem on: FreeBSD vbook.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Sat Aug 18 00:12:19 MSD 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/VBOOK i386 When I was running RELENG_4 my vaio z505s allways successful awake from hibernation, and with probability about 30% freezes after awake from suspend. Now (with -CURRENT) it always freezes after awake from suspend, and often freezes after awake from hibernation. bye Juriy Goloveshkin -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
