kernel panic athn0
kernel panic athn0 when I do
`sudo ifconfig athn0 scan`
or
`sudo ifconfig athn0 inet 192.168.10.1 255.255.255.0 mediaopt hostap nwid
mynwid wpakey 1qaz1qaz up`
or
`sudo ifconfig athn0 up`
ifconfig
athn0: flags=28802BROADCAST,SIMPLEX,MULTICAST,NOINET6 mtu 1500
lladdr 00:00:ef:be:ad:de
priority: 4
groups: wlan
media: IEEE802.11 autoselect
status: no network
ieee80211: nwid
pcidump
Domain
/dev/pci0:
[1/47]
0:0:0: AMD AMD64 14h Host
0:1:0: ATI Radeon HD 6320
0:1:1: ATI Radeon HD 6310 HD Audio
0:4:0: AMD AMD64 14h PCIE
0:17:0: ATI SBx00 SATA
0:18:0: ATI SB700 USB
0:18:2: ATI SB700 USB2
0:19:0: ATI SB700 USB
0:19:2: ATI SB700 USB2
0:20:0: ATI SBx00 SMBus
0:20:2: ATI SBx00 HD Audio
0:20:3: ATI SB700 ISA
0:20:4: ATI SB600 PCI
0:20:5: ATI SB700 USB
0:21:0: ATI SB800 PCIE
0:21:1: ATI SB800 PCIE
0:21:2: ATI SB800 PCIE
0:21:3: ATI SB800 PCIE
0:22:0: ATI SB700 USB
0:22:2: ATI SB700 USB2
0:24:0: AMD AMD64 14h Link Cfg
0:24:1: AMD AMD64 14h Address Map
0:24:2: AMD AMD64 14h DRAM Cfg
0:24:3: AMD AMD64 14h Misc Cfg
0:24:4: AMD AMD64 14h CPU Power
0:24:5: AMD AMD64 14h Reserved
0:24:6: AMD AMD64 14h NB Power
0:24:7: AMD AMD64 14h Reserved
3:0:0: Atheros AR9300
4:0:0: Realtek 8168
5:0:0: ASMedia ASM1083/1085 PCIE-PCI
6:1:0: Realtek 8169
6:2:0: VIA VT6306 FireWire
7:0:0: ASMedia ASM1042 xHCI
OpenBSD/amd64 (router.local.lan) (tty00)
login: panic: kernel diagnostic assertion pin sc-ngpiopins failed:
file ../../../../dev/ic/ar9003.c, line 512
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{0} trace
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
ar9003_gpio_write() at ar9003_gpio_write+0x9d
athn_init() at athn_init+0xfb
athn_ioctl() at athn_ioctl+0x1e6
in_ifinit() at in_ifinit+0xee
in_control() at in_control+0x574
ifioctl() at ifioctl+0x201
sys_ioctl() at sys_ioctl+0x169
syscall() at syscall+0x297
--- syscall (number 54) ---
end of kernel
end trace frame: 0x53bb20, count: -11
acpi_pdirpa+0x3fc50a:
ddb{0} ps
PID PPID PGRPUID S FLAGS WAIT COMMAND
* 1313 22629 1313 0 7 0x3ifconfig
22629 1819 22629 1000 30x8b pause ksh
19651 23472 6931 1000 30x83 ttyin more
23472 6931 6931 1000 30x8b pause sh
6931 12554 6931 1000 30x83 wait man
12554 1819 12554 1000 30x8b pause ksh
1819 1 1819 1000 30x80 kqreadtmux
28809 5207 28809 1000 30x83 kqreadtmux
5207 27936 5207 1000 30x8b pause ksh
27936 13045 13045 1000 30x90 selectsshd
13045 25024 13045 0 30x92 poll sshd
2078 1 2078 0 30x83 ttyin getty
17304 1 17304 0 30x83 ttyin getty
2330 1 2330 0 30x83 ttyin getty
24689 1 24689 0 30x83 ttyin getty
26914 1 26914 0 30x83 ttyin getty
16989 1 16989 0 30x83 ttyin getty
14046 1 14046 0 30x80 selectcron
10830 1 10830 0 30x80 nanosleep sensorsd
5153 1 5153 0 30x80 kqreadapmd
27414 1 27414 99 30x90 poll sndiod
26709 7533 7533 95 30x90 kqreadsmtpd
17924 7533 7533 95 30x90 kqreadsmtpd
17176 7533 7533 95 30x90 kqreadsmtpd
15696 7533 7533 95 30x90 kqreadsmtpd
27629 7533 7533 95 30x90 kqreadsmtpd
9046 7533 7533103 30x90 kqreadsmtpd
7533 1 7533 0 30x80 kqreadsmtpd
4849 1 4849 77 30x90 poll dhcpd
25024 1 25024 0 30x80 selectsshd
29737 21956 28576 83 30x90 poll ntpd
21956 28576 28576 83 30x90 poll ntpd
28576 1 28576 0 30x80 poll ntpd
19213 19275 19275 70 30x90 selectnamed
19275 1 19275 0 30x90 netio named
10253 2257 2257 74 30x90 bpf pflogd
2257 1 2257 0 30x80 netio pflogd
5672 12619 12619 73 30x90 poll syslogd
12619 1 12619 0 30x80 netio syslogd
8519 1 8519 77 30x90 poll dhclient
7102 1 7102 0 30x80 poll dhclient
28382 0 0 0 3 0x14200 bored
Re: kernel panic athn0
Sorry, in first message ddb only for one processor. This is fresh for both:
# ifconfig athn0 up
panic: kernel diagnostic assertion pin sc-ngpiopins failed: file
../../../../dev/ic/ar9003.c, line 512
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{1} trace
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
ar9003_gpio_write() at ar9003_gpio_write+0x9d
athn_init() at athn_init+0xfb
athn_ioctl() at athn_ioctl+0x1e6
ifioctl() at ifioctl+0xb18
sys_ioctl() at sys_ioctl+0x169
syscall() at syscall+0x297
--- syscall (number 54) ---
end of kernel
end trace frame: 0x7f7bcca0, count: -9
acpi_pdirpa+0x3fc50a:
ddb{1} mach ddbcpu 0
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{0} trace
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x64
Xresume_lapic_ipi() at Xresume_lapic_ipi+0x1b
--- interrupt ---
Bad frame pointer: 0x80001ce45c08
end trace frame: 0x80001ce45c08, count: -3
__mp_lock+0x42:
ddb{0} ps
PID PPID PGRPUID S FLAGS WAIT COMMAND
19450 13014 19450 0 7 0x3ifconfig
13014 1 13014 0 30x8b pause ksh
25598 1 25598 0 30x83 ttyin getty
18456 1 18456 0 30x83 ttyin getty
11661 1 11661 0 30x83 ttyin getty
916 1916 0 30x83 ttyin getty
6800 1 6800 0 30x83 ttyin getty
26728 1 26728 0 30x80 selectcron
3038 1 3038 0 30x80 nanosleep sensorsd
19379 1 19379 0 30x80 kqreadapmd
12318 1 12318 99 30x90 poll sndiod
10631 30214 30214 95 30x90 kqreadsmtpd
9723 30214 30214 95 30x90 kqreadsmtpd
20447 30214 30214 95 30x90 kqreadsmtpd
32443 30214 30214 95 30x90 kqreadsmtpd
10158 30214 30214 95 30x90 kqreadsmtpd
26620 30214 30214103 30x90 kqreadsmtpd
30214 1 30214 0 30x80 kqreadsmtpd
25074 1 25074 77 30x90 poll dhcpd
5058 1 5058 0 30x80 selectsshd
13567 28172 22 83 30x90 poll ntpd
28172 22 22 83 30x90 poll ntpd
22 1 22 0 30x80 poll ntpd
12313 17356 17356 70 30x90 selectnamed
17356 1 17356 0 30x90 netio named
13591 11643 11643 74 30x90 bpf pflogd
11643 1 11643 0 30x80 netio pflogd
22160 30463 30463 73 30x90 poll syslogd
30463 1 30463 0 30x80 netio syslogd
*16977 1 16977 77 70x90dhclient
26597 1 26597 0 30x80 poll dhclient
27019 0 0 0 3 0x14200 bored ttm_swap
27833 0 0 0 3 0x14200 aiodoned aiodoned
13860 0 0 0 3 0x14200 syncerupdate
12987 0 0 0 3 0x14200 cleaner cleaner
29718 0 0 0 3 0x14200 reaperreaper
9873 0 0 0 3 0x14200 pgdaemon pagedaemon
30462 0 0 0 3 0x14200 bored crypto
2 0 0 0 3 0x14200 pftm pfpurge
31001 0 0 0 3 0x14200 bored sensors
14441 0 0 0 3 0x14200 usbtskusbtask
13312 0 0 0 3 0x14200 usbatsk usbatsk
16136 0 0 0 3 0x40014200 acpi0 acpi0
27548 0 0 0 3 0x40014200idle1
20115 0 0 0 3 0x14200 bored systqmp
11558 0 0 0 3 0x14200 bored systq
14960 0 0 0 3 0x14200 bored syswq
14541 0 0 0 3 0x40014200idle0
1 0 1 0 30x82 wait init
0 -1 0 0 3 0x10200 scheduler swapper
ddb{0}
Re: kernel panic athn0
On Tue, Nov 11, 2014 at 01:44:57PM +0200, Alexey Kurinnij wrote:
Sorry, in first message ddb only for one processor. This is fresh for both:
athn0 at pci3 dev 0 function 0 Atheros AR9300 rev 0x01: apic 0 int 16
Sorry, this chip isn't supported. See the man page -- it's not listed.
Damien committed untested code for this chip years ago and made the
driver use that code (see r1.1 in CVS log for dev/ic/ar9003.c).
There have been various crashes as a result, some already fixed,
some not fixed.
Since this problem keeps coming up, and ar9003 cards are known to be
broken, and nobody is working on fixing them I believe we should
simply stop the kernel from attaching them for now.
Index: if_athn_pci.c
===
RCS file: /cvs/src/sys/dev/pci/if_athn_pci.c,v
retrieving revision 1.16
diff -u -p -r1.16 if_athn_pci.c
--- if_athn_pci.c 8 Jul 2014 08:55:33 - 1.16
+++ if_athn_pci.c 11 Nov 2014 11:58:33 -
@@ -97,8 +97,7 @@ static const struct pci_matchid athn_pci
{ PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9285 },
{ PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR2427 },
{ PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9227 },
- { PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9287 },
- { PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9300 }
+ { PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9287 }
};
int
# ifconfig athn0 up
panic: kernel diagnostic assertion pin sc-ngpiopins failed: file
../../../../dev/ic/ar9003.c, line 512
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{1} trace
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
ar9003_gpio_write() at ar9003_gpio_write+0x9d
athn_init() at athn_init+0xfb
athn_ioctl() at athn_ioctl+0x1e6
ifioctl() at ifioctl+0xb18
sys_ioctl() at sys_ioctl+0x169
syscall() at syscall+0x297
--- syscall (number 54) ---
end of kernel
end trace frame: 0x7f7bcca0, count: -9
acpi_pdirpa+0x3fc50a:
ddb{1} mach ddbcpu 0
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{0} trace
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x64
Xresume_lapic_ipi() at Xresume_lapic_ipi+0x1b
--- interrupt ---
Bad frame pointer: 0x80001ce45c08
end trace frame: 0x80001ce45c08, count: -3
__mp_lock+0x42:
ddb{0} ps
PID PPID PGRPUID S FLAGS WAIT COMMAND
19450 13014 19450 0 7 0x3ifconfig
13014 1 13014 0 30x8b pause ksh
25598 1 25598 0 30x83 ttyin getty
18456 1 18456 0 30x83 ttyin getty
11661 1 11661 0 30x83 ttyin getty
916 1916 0 30x83 ttyin getty
6800 1 6800 0 30x83 ttyin getty
26728 1 26728 0 30x80 selectcron
3038 1 3038 0 30x80 nanosleep sensorsd
19379 1 19379 0 30x80 kqreadapmd
12318 1 12318 99 30x90 poll sndiod
10631 30214 30214 95 30x90 kqreadsmtpd
9723 30214 30214 95 30x90 kqreadsmtpd
20447 30214 30214 95 30x90 kqreadsmtpd
32443 30214 30214 95 30x90 kqreadsmtpd
10158 30214 30214 95 30x90 kqreadsmtpd
26620 30214 30214103 30x90 kqreadsmtpd
30214 1 30214 0 30x80 kqreadsmtpd
25074 1 25074 77 30x90 poll dhcpd
5058 1 5058 0 30x80 selectsshd
13567 28172 22 83 30x90 poll ntpd
28172 22 22 83 30x90 poll ntpd
22 1 22 0 30x80 poll ntpd
12313 17356 17356 70 30x90 selectnamed
17356 1 17356 0 30x90 netio named
13591 11643 11643 74 30x90 bpf pflogd
11643 1 11643 0 30x80 netio pflogd
22160 30463 30463 73 30x90 poll syslogd
30463 1 30463 0 30x80 netio syslogd
*16977 1 16977 77 70x90dhclient
26597 1 26597 0 30x80 poll dhclient
27019 0 0 0 3 0x14200 bored ttm_swap
27833 0 0 0 3 0x14200 aiodoned aiodoned
Re: kernel panic athn0
On Tue, Nov 11, 2014 at 1:04 PM, Stefan Sperling s...@stsp.name wrote:
On Tue, Nov 11, 2014 at 01:44:57PM +0200, Alexey Kurinnij wrote:
Sorry, in first message ddb only for one processor. This is fresh for both:
athn0 at pci3 dev 0 function 0 Atheros AR9300 rev 0x01: apic 0 int 16
Sorry, this chip isn't supported. See the man page -- it's not listed.
Damien committed untested code for this chip years ago and made the
driver use that code (see r1.1 in CVS log for dev/ic/ar9003.c).
There have been various crashes as a result, some already fixed,
some not fixed.
Since this problem keeps coming up, and ar9003 cards are known to be
broken, and nobody is working on fixing them I believe we should
simply stop the kernel from attaching them for now.
Indeed.
ok with me.
Ciao,
David
Index: if_athn_pci.c
===
RCS file: /cvs/src/sys/dev/pci/if_athn_pci.c,v
retrieving revision 1.16
diff -u -p -r1.16 if_athn_pci.c
--- if_athn_pci.c 8 Jul 2014 08:55:33 - 1.16
+++ if_athn_pci.c 11 Nov 2014 11:58:33 -
@@ -97,8 +97,7 @@ static const struct pci_matchid athn_pci
{ PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9285 },
{ PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR2427 },
{ PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9227 },
- { PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9287 },
- { PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9300 }
+ { PCI_VENDOR_ATHEROS, PCI_PRODUCT_ATHEROS_AR9287 }
};
int
# ifconfig athn0 up
panic: kernel diagnostic assertion pin sc-ngpiopins failed: file
../../../../dev/ic/ar9003.c, line 512
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{1} trace
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
ar9003_gpio_write() at ar9003_gpio_write+0x9d
athn_init() at athn_init+0xfb
athn_ioctl() at athn_ioctl+0x1e6
ifioctl() at ifioctl+0xb18
sys_ioctl() at sys_ioctl+0x169
syscall() at syscall+0x297
--- syscall (number 54) ---
end of kernel
end trace frame: 0x7f7bcca0, count: -9
acpi_pdirpa+0x3fc50a:
ddb{1} mach ddbcpu 0
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb{0} trace
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x64
Xresume_lapic_ipi() at Xresume_lapic_ipi+0x1b
--- interrupt ---
Bad frame pointer: 0x80001ce45c08
end trace frame: 0x80001ce45c08, count: -3
__mp_lock+0x42:
ddb{0} ps
PID PPID PGRPUID S FLAGS WAIT COMMAND
19450 13014 19450 0 7 0x3ifconfig
13014 1 13014 0 30x8b pause ksh
25598 1 25598 0 30x83 ttyin getty
18456 1 18456 0 30x83 ttyin getty
11661 1 11661 0 30x83 ttyin getty
916 1916 0 30x83 ttyin getty
6800 1 6800 0 30x83 ttyin getty
26728 1 26728 0 30x80 selectcron
3038 1 3038 0 30x80 nanosleep sensorsd
19379 1 19379 0 30x80 kqreadapmd
12318 1 12318 99 30x90 poll sndiod
10631 30214 30214 95 30x90 kqreadsmtpd
9723 30214 30214 95 30x90 kqreadsmtpd
20447 30214 30214 95 30x90 kqreadsmtpd
32443 30214 30214 95 30x90 kqreadsmtpd
10158 30214 30214 95 30x90 kqreadsmtpd
26620 30214 30214103 30x90 kqreadsmtpd
30214 1 30214 0 30x80 kqreadsmtpd
25074 1 25074 77 30x90 poll dhcpd
5058 1 5058 0 30x80 selectsshd
13567 28172 22 83 30x90 poll ntpd
28172 22 22 83 30x90 poll ntpd
22 1 22 0 30x80 poll ntpd
12313 17356 17356 70 30x90 selectnamed
17356 1 17356 0 30x90 netio named
13591 11643 11643 74 30x90 bpf pflogd
11643 1 11643 0 30x80 netio pflogd
22160 30463 30463 73 30x90 poll syslogd
30463 1 30463 0 30x80 netio syslogd
*16977 1 16977 77 70x90dhclient
26597 1 26597 0 30x80 poll dhclient
Re: Sun/Cassini Quad Gigabit Card Not Detected
In my experience, cas(4) is slow and not very stable on sparc64. I used it in a Blade 150 firewall. On Sun, Nov 09, 2014 at 11:31:37AM -0500, Jeff wrote: Hi, I've installed OpenBSD 5.6 (i386) on a dual processor XEON box which has a 4 port Sun (Sun# 501-6738-10) Gigabit NIC card. dmesg doesn't have any indication that the card is installed. Booting Linux shows the card as Sun/Cassini which I believe should be handled by the cas driver. pcidump shows the following (I think that the NS Saturn is the NIC card): Domain /dev/pci0: 0:0:0: Intel E7505 Host 0:0:1: Intel E7505 Error Reporting 0:1:0: Intel E7505 AGP 0:2:0: Intel E7505 PCI 0:2:1: Intel E7505 PCI 0:30:0: Intel 82801BA Hub-to-PCI 0:31:0: Intel 82801DB LPC 0:31:1: Intel 82801DB IDE 0:31:3: Intel 82801DB SMBus 1:0:0: NVIDIA Riva TNT2 2:28:0: Intel 82870P2 IOxAPIC 2:29:0: Intel 82870P2 PCIX-PCIX 2:30:0: Intel 82870P2 IOxAPIC 2:31:0: Intel 82870P2 PCIX-PCIX 3:1:0: Broadcom BCM5703X 3:2:0: Intel unknown 4:0:0: NS Saturn 4:1:0: NS Saturn 4:2:0: NS Saturn 4:3:0: NS Saturn 6:1:0: TI TSB43AB22 FireWire Any ideas on how to get OpenBSD to recognise this card? Thanks! Jeff Any ideas on how to get OpenBSD to recognise this card? Thanks! Jeff
Re: httpd slowcgi notes
Hi,
server local-fastcgi {
listen on egress port 80
fastcgi
}
have you tried specifying the fastcgi socket ?
kernel page fault trap after growfs
Hello all,
I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I
can reproduce it in older versions too).
I've created an OpenBSD installation in Linux through kvm on a 1GB hard
disk with just a root partition (a), by booting the install56.iso cdrom
with a command like this:
# kvm -smp 1 -m 2048 -boot d -drive \
file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom
/tmp/install56.iso -vnc :0
The system boots fine with a command like this:
# kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio
If I then copy it into a 100GB volume:
# dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M
And try to boot it, it still boots fine. I then boot into the VM's
rescue disk:
boot bsd.rd
and press S to get a shell
I mount the root partition and grab growfs program:
# mount /dev/sd0a /mnt
# cp /mnt/sbin/growfs .
# umount /mnt
Fix the MBR to use the entire disk:
# fdisk -i wd0
And change the disklabel:
# disklabel -E sd0
Change the OpenBSD boundaries to cover the whole disk:
b
Starting sector: [64]
Size ('*' for entire disk):[] *
and then grow the root partition to make it 100GB log:
c
partition to change size: [] a
Then grow the underlying FFS file system:
# growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs bug?
Thank you in advance,
Nikos Skalkotos
Re: kernel page fault trap after growfs
On Tue, Nov 11, 2014 at 04:10:48PM +0200, Nikos Skalkotos wrote:
Hello all,
I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I
can reproduce it in older versions too).
I've created an OpenBSD installation in Linux through kvm on a 1GB hard
disk with just a root partition (a), by booting the install56.iso cdrom
with a command like this:
# kvm -smp 1 -m 2048 -boot d -drive \
file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom
/tmp/install56.iso -vnc :0
The system boots fine with a command like this:
# kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio
If I then copy it into a 100GB volume:
# dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M
And try to boot it, it still boots fine. I then boot into the VM's
rescue disk:
boot bsd.rd
and press S to get a shell
I mount the root partition and grab growfs program:
# mount /dev/sd0a /mnt
# cp /mnt/sbin/growfs .
# umount /mnt
Fix the MBR to use the entire disk:
# fdisk -i wd0
I assume that wd0 should be sd0?
And change the disklabel:
# disklabel -E sd0
Change the OpenBSD boundaries to cover the whole disk:
b
Starting sector: [64]
Size ('*' for entire disk):[] *
and then grow the root partition to make it 100GB log:
c
partition to change size: [] a
Then grow the underlying FFS file system:
# growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs bug?
Thank you in advance,
Nikos Skalkotos
What does fsck say after you have grown the fs?
Yoy probably need to force fsck, see BUGS section of growfs(8).
-Otto
Re: kernel page fault trap after growfs
Hello Otto,
First of all, thank you for the quick reply.
On 11 November 2014 16:25, Otto Moerbeek o...@drijf.net wrote:
On Tue, Nov 11, 2014 at 04:10:48PM +0200, Nikos Skalkotos wrote:
Hello all,
I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I
can reproduce it in older versions too).
I've created an OpenBSD installation in Linux through kvm on a 1GB hard
disk with just a root partition (a), by booting the install56.iso cdrom
with a command like this:
# kvm -smp 1 -m 2048 -boot d -drive \
file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom
/tmp/install56.iso -vnc :0
The system boots fine with a command like this:
# kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio
If I then copy it into a 100GB volume:
# dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M
And try to boot it, it still boots fine. I then boot into the VM's
rescue disk:
boot bsd.rd
and press S to get a shell
I mount the root partition and grab growfs program:
# mount /dev/sd0a /mnt
# cp /mnt/sbin/growfs .
# umount /mnt
Fix the MBR to use the entire disk:
# fdisk -i wd0
I assume that wd0 should be sd0?
Yes this was a typo
And change the disklabel:
# disklabel -E sd0
Change the OpenBSD boundaries to cover the whole disk:
b
Starting sector: [64]
Size ('*' for entire disk):[] *
and then grow the root partition to make it 100GB log:
c
partition to change size: [] a
Then grow the underlying FFS file system:
# growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs bug?
Thank you in advance,
Nikos Skalkotos
What does fsck say after you have grown the fs?
Yoy probably need to force fsck, see BUGS section of growfs(8).
I tried it and it justs asks if I want to mark the file system as
clean and states that the filesystem has been modified in the end.
But still, the file system seems to be corrupted. I can reproduce this
for big filesystems (50G or 100G). I tried to use ide, instead of
virtio but I still get errors. It's 100% reproducible for big
filesystems :-(
-Otto
Does anybody have enough space to try it out?
The funny thing is that if I directly install the OpenBSD system on
the 100G drive, and just create a 1G root partition and enlarge it
afterwards it works. But If I install it in a small volume and then do
the aforementioned procedure it always crashes. I don't thing this is
a hardware issue from my side.
Nikos
Re: foomatic-rip 'f' exited (retcode=9)
Predrag Punosevac punosevac72 at gmail.com writes: It appears that I can print spool-lessly with foomatic-rip -P HP-PhotoSmart_C5200 --ppd HP-PhotoSmart_C5200.ppd /dev/ulpt0 Any fix for this yet (same problem with an Epson Stylus Office BX300F)?
kernel page fault trap
Hello all,
I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I
can reproduce it in older versions too).
I've created an OpenBSD installation in Linux through kvm on a 1GB hard
disk with just a root partition (a), by booting the install56.iso cdrom
with a command like this:
kvm -smp 1 -m 2048 -boot d -drive \
file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom
/tmp/install56.iso -vnc :0
The system boots fine with a command like this:
kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio
If I then copy it into a 100GB volume:
dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M
And try to boot it, it still boots fine. I then boot into the VM's
rescue disk:
boot bsd.rd
and press S to get a shell
I mount the root partition and grab growfs program:
# mount /dev/sd0a /mnt
# cp /mnt/sbin/growfs .
# umount /mnt
Fix the MBR to use the entire disk:
# fdisk -i wd0
And change the disklabel:
disklabel -E sd0
Change the OpenBSD boundaries to cover the whole disk:
b
Starting sector: [64]
Size ('*' for entire disk):[] *
and then grow the root partition to make it 100GB log:
c
partition to change size: [] a
Then grow the underlying FFS file system:
growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs bug?
Nikos Skalkotos
kernel page fault trap
Hello all,
I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I
can reproduce it in older versions too).
I've created an OpenBSD installation in Linux through kvm on a 1GB hard
disk with just a root partition (a), by booting the install56.iso cdrom
with a command like this:
kvm -smp 1 -m 2048 -boot d -drive \
file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom
/tmp/install56.iso -vnc :0
The system boots fine with a command like this:
kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio
If I then copy it into a 100GB volume:
dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M
And try to boot it, it still boots fine. I then boot into the VM's
rescue disk:
boot bsd.rd
and press S to get a shell
I mount the root partition and grab growfs program:
# mount /dev/sd0a /mnt
# cp /mnt/sbin/growfs .
# umount /mnt
Fix the MBR to use the entire disk:
# fdisk -i wd0
And change the disklabel:
disklabel -E sd0
Change the OpenBSD boundaries to cover the whole disk:
b
Starting sector: [64]
Size ('*' for entire disk):[] *
and then grow the root partition to make it 100GB log:
c
partition to change size: [] a
Then grow the underlying FFS file system:
growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs bug?
Thank you in advance,
Nikos Skalkotos
Advice requested -- how best to copy a disk
My apologies for what seems to be a rather simple and not really OpenBSD specific question, but searching hasn't found any good answers. I've got an old PC running i386 OpenBSD which is dying; the disk seems to be good, but I need to replace the rest of the hardware. Usually I'd just move the disk to the new system, but the old system is EIDE and the new one is SATA -- so I need to copy the old disk (which I can put in an external enclosure and connect to the new system via USB) to the new one (which is a different size and probably a different geometry, so the new and old partitions probably won't be exactly the same sizes). It's clearly possible to boot the new system from an install CD (or, if necessary, a USB stick with a full install on it) then fdisk and disklabel the new disk and newfs / dump|restore the partitions one by one, followed up by installboot, editing the duids in /etc/fstab, and fixing up /etc/hostname.*, but I'm hoping that there's a better way. Thanks in advance for any suggestions (or confirmations that there is no better way). Dave -- Dave Anderson d...@daveanderson.com
Re: Advice requested -- how best to copy a disk
On 2014-11-11 14:23, Dave Anderson wrote: My apologies for what seems to be a rather simple and not really OpenBSD specific question, but searching hasn't found any good answers. I've got an old PC running i386 OpenBSD which is dying; the disk seems to be good, but I need to replace the rest of the hardware. Usually I'd just move the disk to the new system, but the old system is EIDE and the new one is SATA -- so I need to copy the old disk (which I can put in an external enclosure and connect to the new system via USB) to the new one (which is a different size and probably a different geometry, so the new and old partitions probably won't be exactly the same sizes). It's clearly possible to boot the new system from an install CD (or, if necessary, a USB stick with a full install on it) then fdisk and disklabel the new disk and newfs / dump|restore the partitions one by one, followed up by installboot, editing the duids in /etc/fstab, and fixing up /etc/hostname.*, but I'm hoping that there's a better way. Thanks in advance for any suggestions (or confirmations that there is no better way). The RAMDISK kernel doesn't include dump(8), but it does have restore(8). If you physically move the disk, you can boot it, if the new hardware permits booting from the alternate disk. Use single-user mode (boot -s) and you have access to the full set of partitions with only root mounted read/only. If I recall correctly, dump(8) and restore(8) are both in /sbin, you will need a read/write /tmp directory in order to use restore. After dump/restore of all partitions, you can then run installboot(8) and update /etc/fstab.
Re: kernel page fault trap
I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I
can reproduce it in older versions too).
I've created an OpenBSD installation in Linux through kvm on a 1GB hard
disk with just a root partition (a), by booting the install56.iso cdrom
with a command like this:
kvm -smp 1 -m 2048 -boot d -drive \
file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom
/tmp/install56.iso -vnc :0
The system boots fine with a command like this:
kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio
If I then copy it into a 100GB volume:
dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M
And try to boot it, it still boots fine. I then boot into the VM's
rescue disk:
boot bsd.rd
and press S to get a shell
I mount the root partition and grab growfs program:
# mount /dev/sd0a /mnt
# cp /mnt/sbin/growfs .
# umount /mnt
Fix the MBR to use the entire disk:
# fdisk -i wd0
And change the disklabel:
disklabel -E sd0
Change the OpenBSD boundaries to cover the whole disk:
b
Starting sector: [64]
Size ('*' for entire disk):[] *
and then grow the root partition to make it 100GB log:
c
partition to change size: [] a
Then grow the underlying FFS file system:
growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs bug?
Didn't you read the manual page?
Currently growfs can only enlarge unmounted file systems. Do not try
enlarging a mounted file system - your system may panic and you will not
be able to use the file system any longer. Most of the newfs(8) options
cannot be changed by growfs. In fact, you can only increase the size of
the file system. Use tunefs(8) for other changes.
Re: kernel page fault trap
Hello,
Sorry, what do you mean by mounted file system? The file system was
not mounted when I tried to enlarge it. I booted with bsd.rd, mounted
the file system just to copy the growfs utility, unmounted the
filesystem and then tried to enlarge it.
Nikos
P.S. This post was sent by 2 mail accounts (skalk...@grnet.gr and
skalk...@gmail.com). For some strange reason the mails from
skalk...@grnet.gr did not reach the list for hours and I tried the
other account. Sorry about this.
On 11 November 2014 21:56, Theo de Raadt dera...@cvs.openbsd.org wrote:
I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I
can reproduce it in older versions too).
I've created an OpenBSD installation in Linux through kvm on a 1GB hard
disk with just a root partition (a), by booting the install56.iso cdrom
with a command like this:
kvm -smp 1 -m 2048 -boot d -drive \
file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom
/tmp/install56.iso -vnc :0
The system boots fine with a command like this:
kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio
If I then copy it into a 100GB volume:
dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M
And try to boot it, it still boots fine. I then boot into the VM's
rescue disk:
boot bsd.rd
and press S to get a shell
I mount the root partition and grab growfs program:
# mount /dev/sd0a /mnt
# cp /mnt/sbin/growfs .
# umount /mnt
Fix the MBR to use the entire disk:
# fdisk -i wd0
And change the disklabel:
disklabel -E sd0
Change the OpenBSD boundaries to cover the whole disk:
b
Starting sector: [64]
Size ('*' for entire disk):[] *
and then grow the root partition to make it 100GB log:
c
partition to change size: [] a
Then grow the underlying FFS file system:
growfs /dev/sd0a
If I then reboot, the ffs driver crashes with errors like this:
uvm_fault(0x81dcddc0, 0xc68, 0, 2) - e
kernel: page fault trap, code=0
Stopped at ffs_vget+0x115: addb%al, 0(%rcx,%rax,1)
ddb
Am I missing something or is this a kernel/growfs bug?
Didn't you read the manual page?
Currently growfs can only enlarge unmounted file systems. Do not try
enlarging a mounted file system - your system may panic and you will not
be able to use the file system any longer. Most of the newfs(8) options
cannot be changed by growfs. In fact, you can only increase the size of
the file system. Use tunefs(8) for other changes.
Re: kernel page fault trap
On Tue, Nov 11, 2014 at 5:43 AM, Nikos Skalkotos skalk...@grnet.gr wrote: I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I can reproduce it in older versions too). I've created an OpenBSD installation in Linux through kvm on a 1GB hard disk with just a root partition (a), by booting the install56.iso cdrom with a command like this: kvm -smp 1 -m 2048 -boot d -drive \ file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom /tmp/install56.iso -vnc :0 The system boots fine with a command like this: kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio If I then copy it into a 100GB volume: dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M And try to boot it, it still boots fine. I then boot into the VM's rescue disk: ... Fix the MBR to use the entire disk: # fdisk -i wd0 And change the disklabel: disklabel -E sd0 ... To make it easier to analyze and reproduce this, can you provide the output of fdisk and disklabel both before changing anything and then again afterwards? Hmm, and how about the output of dumpfs /dev/rsd0a | head -23 before and after too? Philip Guenther
Re: Advice requested -- how best to copy a disk
On 14-11-11 01:23 PM, Dave Anderson wrote: My apologies for what seems to be a rather simple and not really OpenBSD specific question, but searching hasn't found any good answers. I've got an old PC running i386 OpenBSD which is dying; the disk seems to be good, but I need to replace the rest of the hardware. Usually I'd just move the disk to the new system, but the old system is EIDE and the new one is SATA -- so I need to copy the old disk (which I can put in an external enclosure and connect to the new system via USB) to the new one (which is a different size and probably a different geometry, so the new and old partitions probably won't be exactly the same sizes). It's clearly possible to boot the new system from an install CD (or, if necessary, a USB stick with a full install on it) then fdisk and disklabel the new disk and newfs / dump|restore the partitions one by one, followed up by installboot, editing the duids in /etc/fstab, and fixing up /etc/hostname.*, but I'm hoping that there's a better way. Thanks in advance for any suggestions (or confirmations that there is no better way). I think you've already figured out the optimal way to do it... I would do a fresh minimal install on the target disk, then restore(8) over top of it, to avoid having to fiddle too much with installboot(8) etc. An easier way might be to just use an IDE-to-SATA adapter for now and move the disk as-is into the new system. I've used these (http://www.startech.com/HDD/Adapters/Bi-Directional-SATA-IDE-Adapter-Converter~PATA2SATA3) in production before, Startech has a few others with more convenient form factors (click on Related Products). -- -Adam Thompson athom...@athompso.net
Re: kernel page fault trap
Hello, Is there a way to output the rescue disk console on a serial port? It will help for the copy-paste because I don't have physical access to the server I'm running the VM's and I'm using VNC to grab the console. On 11 November 2014 22:21, Philip Guenther guent...@gmail.com wrote: On Tue, Nov 11, 2014 at 5:43 AM, Nikos Skalkotos skalk...@grnet.gr wrote: I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I can reproduce it in older versions too). I've created an OpenBSD installation in Linux through kvm on a 1GB hard disk with just a root partition (a), by booting the install56.iso cdrom with a command like this: kvm -smp 1 -m 2048 -boot d -drive \ file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom /tmp/install56.iso -vnc :0 The system boots fine with a command like this: kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio If I then copy it into a 100GB volume: dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M And try to boot it, it still boots fine. I then boot into the VM's rescue disk: ... Fix the MBR to use the entire disk: # fdisk -i wd0 And change the disklabel: disklabel -E sd0 ... To make it easier to analyze and reproduce this, can you provide the output of fdisk and disklabel both before changing anything and then again afterwards? Hmm, and how about the output of dumpfs /dev/rsd0a | head -23 before and after too? Philip Guenther
[patches for the website] last release for platforms is 5.6
Hi, In each platforms pages, at the end there is a paragraph about the last supported release, which is not anymore 5.5 (unless for armv7 because there isn't any 5.6). As there are 17 patches, I don't inline them but here's an archive : http://iota.chown.me/plat.diff.tar.gz Cheers, Daniel
Re: symon: mbuf() failed (508)
On 2014-11-10, Atanas Vladimirov vl...@bsdbg.net wrote: Hi, After the upgrade to the recent snapshot I got many symon: mbuf() failed (508) in /var/log/messages. I've just committed a fix to ports for this.
Postfix compilation error.
Hi at all, I try to compile postfix on OpenBSD 5.6 with command # env FLAVOR=mysql sasl2 make install for install it with mysql and sasl2 support. I have compiled it in OpenBSD 5.5 and 5.4 without problem. My system is upgrated from 5.4 to 5.5 and to 5.6 The compiler show: /usr/local/lib/mysql -lmysqlclient -L/usr/local/lib -Wl,-R/usr/local/lib -lpcre /usr/local/lib/libmysqlclient.so.23.0: warning: stpcpy() is dangerous; do not use it ../../lib/libutil.a(concatenate.o)(.text+0x77): In function `concatenate': : warning: strcpy() is almost always misused, please use strlcpy() ../../lib/libutil.a(concatenate.o)(.text+0x88): In function `concatenate': : warning: strcat() is almost always misused, please use strlcat() ../../lib/libglobal.a(mail_conf_time.o)(.text+0x46): In function `set_mail_conf_time_int': : warning: sprintf() is often misused, please use snprintf() /usr/bin/ld: warning: libcrypto.so.23.0, needed by /usr/local/lib/libsasl2.so.3.0, may conflict with libcrypto.so.30.0 /usr/bin/ld: warning: libroken.so.1.0, needed by /usr/local/lib/libsasl2.so.3.0, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libssl.so.20.0, needed by /usr/local/lib/libmysqlclient.so.23.0, may conflict with libssl.so.27.0 /usr/lib/libgssapi.so.7.1: undefined reference to `ct_memcmp' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_cloexec_dir' /usr/lib/libasn1.so.20.0: undefined reference to `rk_strpoolcollect' /usr/lib/libasn1.so.20.0: undefined reference to `rk_hex_encode' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_strupr' /usr/lib/libkrb5.so.20.0: undefined reference to `net_write' /usr/lib/libasn1.so.20.0: undefined reference to `rk_hex_decode' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_bswap16' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_bswap32' /usr/lib/libgssapi.so.7.1: undefined reference to `rk_cloexec_file' /usr/lib/libasn1.so.20.0: undefined reference to `rk_strpoolprintf' /usr/lib/libkrb5.so.20.0: undefined reference to `arg_printusage' /usr/lib/libkrb5.so.20.0: undefined reference to `roken_gethostby_setup' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_estrdup' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_dns_free_data' /usr/lib/libkrb5.so.20.0: undefined reference to `base64_encode' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_socket_sockaddr_size' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_dns_lookup' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_socket_get_port' /usr/lib/libkrb5.so.20.0: undefined reference to `net_read' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_strlwr' /usr/lib/libgssapi.so.7.1: undefined reference to `issuid' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_cloexec' /usr/lib/libkrb5.so.20.0: undefined reference to `roken_gethostbyname' /usr/lib/libkrb5.so.20.0: undefined reference to `getarg' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_strsep_copy' /usr/lib/libkrb5.so.20.0: undefined reference to `parse_time' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_dns_srv_order' collect2: ld returned 1 exit status *** Error 1 in src/master (Makefile:72 'master') *** Error 1 in /usr/ports/pobj/postfix-2.12.20140701-sasl2-mysql/postfix-2.12-20140701 (Makefile:83 'update') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2727 '/usr/ports/pobj/postfix-2.12.20140701-sasl2-mysql/.build_done') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1922 '/usr/ports/packages/i386/all/postfix-2.12.20140701-sasl2-mysql.tgz') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2475 '_internal-package') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2455 'package') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1939 '/var/db/pkg/postfix-2.12.20140701-sasl2-mysql/+CONTENTS') *** Error 1 in /usr/ports/mail/postfix/snapshot (/usr/ports/infrastructure/mk/bsd.port.mk:2455 'install') What is the problem? Has been lost something? Thanks. -- Isaia Luciano -- Le informazioni contenute nella presente e-mail e nei documenti/files eventualmente allegati sono confidenziali. Essi sono riservati esclusivamente al destinatario della stessa. La loro eventuale comunicazione, diffusione o, comunque, rivelazione a terzi, nonche' la copiatura e/o conservazione e' vietata. Se avete ricevuto questa e-mail per errore, Vi preghiamo cortesemente di informare immediatamente il mittente della stessa e di distruggerla o, comunque, cancellarla dal Vostro sistema. This e-mail contains confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorised communication, diffusion, disclosure and copy of the material in this e-mail is strictly forbidden. --
Re: Basic question about following current
On 2014-11-09, Theodore Wynnychenko t...@uchicago.edu wrote: Hello I am thinking of taking the plunge and following current. It all seems straightforward. I have looked at the FAQ's and other sources. I understand that it goes like this (simplistically): Get a new snapshot from mirror Sysmerge etc/xetc There are no more etc/xetc sets, they are included as tar files inside base*.tgz / xbase*.tgz files. Cp bsd.rd to / Boot into bsd.rd Follow upgrade Reboot Sysmerge again to be sure Update packages (pkg_add -ui) So far, got it. But, I am confused about ports. If I have something build from ports, I would want to update that as well, right? pkg_add -u using the snapshot packages. If it doesn't work, wait a few days and try again. There's usually very little reason to do a bulk update of packages via the ports tree. I see that there is a ports.tar.gz in the snapshot directory. But, in the FAQ it says: You must make sure your kernel, 'userland' (the supporting utilities and files) and ports tree are all in sync. There is no src, sys, or xenocara in the snapshot directory (I saw the explanation in the FAQ or somewhere, and it makes total sense). Therefore, my question is: if I am trying to update a port (using make update from a local ports tree), should I use the ports.tar.gz that is in the snapshot directory by uncompressing it over the top of the ports tree I already have? Or, should I download the current source and ports trees using anoncvs, and do the make update from the most current ports tree in anoncvs? Or, is either choice ok? I guess this comes down to a fundamental not understanding of exactly whether or not the local ports tree needs access to the current source tree or not, when trying to build or update a port. If you need something urgently and packages are out of sync with snaps, update trees from anoncvs and build the individual ports. (If you need to do bulk updates and things are out of sync, dpb(1) with -R -u flags might help, though there are some problem areas building packages on a system with already-installed packages, waiting and trying again later is usually easier.)
Re: Postfix compilation error.
On 11/11/14 15:51, giacomo wrote: Hi at all, I try to compile postfix on OpenBSD 5.6 with command # env FLAVOR=mysql sasl2 make install for install it with mysql and sasl2 support. I have compiled it in OpenBSD 5.5 and 5.4 without problem. My system is upgrated from 5.4 to 5.5 and to 5.6 The compiler show: While upgrading your system you haven't followed the upgrade guide to clean out old unused cruft from your system.. http://www.openbsd.org/faq/upgrade55.html http://www.openbsd.org/faq/upgrade56.html The Files to delete and move section. /usr/local/lib/mysql -lmysqlclient -L/usr/local/lib -Wl,-R/usr/local/lib -lpcre /usr/local/lib/libmysqlclient.so.23.0: warning: stpcpy() is dangerous; do not use it ../../lib/libutil.a(concatenate.o)(.text+0x77): In function `concatenate': : warning: strcpy() is almost always misused, please use strlcpy() ../../lib/libutil.a(concatenate.o)(.text+0x88): In function `concatenate': : warning: strcat() is almost always misused, please use strlcat() ../../lib/libglobal.a(mail_conf_time.o)(.text+0x46): In function `set_mail_conf_time_int': : warning: sprintf() is often misused, please use snprintf() /usr/bin/ld: warning: libcrypto.so.23.0, needed by /usr/local/lib/libsasl2.so.3.0, may conflict with libcrypto.so.30.0 /usr/bin/ld: warning: libroken.so.1.0, needed by /usr/local/lib/libsasl2.so.3.0, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libssl.so.20.0, needed by /usr/local/lib/libmysqlclient.so.23.0, may conflict with libssl.so.27.0 /usr/lib/libgssapi.so.7.1: undefined reference to `ct_memcmp' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_cloexec_dir' /usr/lib/libasn1.so.20.0: undefined reference to `rk_strpoolcollect' /usr/lib/libasn1.so.20.0: undefined reference to `rk_hex_encode' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_strupr' /usr/lib/libkrb5.so.20.0: undefined reference to `net_write' /usr/lib/libasn1.so.20.0: undefined reference to `rk_hex_decode' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_bswap16' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_bswap32' /usr/lib/libgssapi.so.7.1: undefined reference to `rk_cloexec_file' /usr/lib/libasn1.so.20.0: undefined reference to `rk_strpoolprintf' /usr/lib/libkrb5.so.20.0: undefined reference to `arg_printusage' /usr/lib/libkrb5.so.20.0: undefined reference to `roken_gethostby_setup' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_estrdup' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_dns_free_data' /usr/lib/libkrb5.so.20.0: undefined reference to `base64_encode' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_socket_sockaddr_size' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_dns_lookup' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_socket_get_port' /usr/lib/libkrb5.so.20.0: undefined reference to `net_read' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_strlwr' /usr/lib/libgssapi.so.7.1: undefined reference to `issuid' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_cloexec' /usr/lib/libkrb5.so.20.0: undefined reference to `roken_gethostbyname' /usr/lib/libkrb5.so.20.0: undefined reference to `getarg' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_strsep_copy' /usr/lib/libkrb5.so.20.0: undefined reference to `parse_time' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_dns_srv_order' collect2: ld returned 1 exit status *** Error 1 in src/master (Makefile:72 'master') *** Error 1 in /usr/ports/pobj/postfix-2.12.20140701-sasl2-mysql/postfix-2.12-20140701 (Makefile:83 'update') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2727 '/usr/ports/pobj/postfix-2.12.20140701-sasl2-mysql/.build_done') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1922 '/usr/ports/packages/i386/all/postfix-2.12.20140701-sasl2-mysql.tgz') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2475 '_internal-package') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2455 'package') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1939 '/var/db/pkg/postfix-2.12.20140701-sasl2-mysql/+CONTENTS') *** Error 1 in /usr/ports/mail/postfix/snapshot (/usr/ports/infrastructure/mk/bsd.port.mk:2455 'install') What is the problem? Has been lost something? Thanks. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: Basic question about following current
Re: Postfix compilation error.
On 11/11/14 20:51, giacomo wrote: Hi at all, I try to compile postfix on OpenBSD 5.6 with command # env FLAVOR=mysql sasl2 make install for install it with mysql and sasl2 support. I have compiled it in OpenBSD 5.5 and 5.4 without problem. My system is upgrated from 5.4 to 5.5 and to 5.6 The compiler show: /usr/local/lib/mysql -lmysqlclient -L/usr/local/lib -Wl,-R/usr/local/lib -lpcre /usr/local/lib/libmysqlclient.so.23.0: warning: stpcpy() is dangerous; do not use it ../../lib/libutil.a(concatenate.o)(.text+0x77): In function `concatenate': : warning: strcpy() is almost always misused, please use strlcpy() ../../lib/libutil.a(concatenate.o)(.text+0x88): In function `concatenate': : warning: strcat() is almost always misused, please use strlcat() ../../lib/libglobal.a(mail_conf_time.o)(.text+0x46): In function `set_mail_conf_time_int': : warning: sprintf() is often misused, please use snprintf() /usr/bin/ld: warning: libcrypto.so.23.0, needed by /usr/local/lib/libsasl2.so.3.0, may conflict with libcrypto.so.30.0 /usr/bin/ld: warning: libroken.so.1.0, needed by /usr/local/lib/libsasl2.so.3.0, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libssl.so.20.0, needed by /usr/local/lib/libmysqlclient.so.23.0, may conflict with libssl.so.27.0 /usr/lib/libgssapi.so.7.1: undefined reference to `ct_memcmp' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_cloexec_dir' /usr/lib/libasn1.so.20.0: undefined reference to `rk_strpoolcollect' /usr/lib/libasn1.so.20.0: undefined reference to `rk_hex_encode' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_strupr' /usr/lib/libkrb5.so.20.0: undefined reference to `net_write' /usr/lib/libasn1.so.20.0: undefined reference to `rk_hex_decode' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_bswap16' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_bswap32' /usr/lib/libgssapi.so.7.1: undefined reference to `rk_cloexec_file' /usr/lib/libasn1.so.20.0: undefined reference to `rk_strpoolprintf' /usr/lib/libkrb5.so.20.0: undefined reference to `arg_printusage' /usr/lib/libkrb5.so.20.0: undefined reference to `roken_gethostby_setup' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_estrdup' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_dns_free_data' /usr/lib/libkrb5.so.20.0: undefined reference to `base64_encode' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_socket_sockaddr_size' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_dns_lookup' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_socket_get_port' /usr/lib/libkrb5.so.20.0: undefined reference to `net_read' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_strlwr' /usr/lib/libgssapi.so.7.1: undefined reference to `issuid' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_cloexec' /usr/lib/libkrb5.so.20.0: undefined reference to `roken_gethostbyname' /usr/lib/libkrb5.so.20.0: undefined reference to `getarg' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_strsep_copy' /usr/lib/libkrb5.so.20.0: undefined reference to `parse_time' /usr/lib/libkrb5.so.20.0: undefined reference to `rk_dns_srv_order' collect2: ld returned 1 exit status *** Error 1 in src/master (Makefile:72 'master') *** Error 1 in /usr/ports/pobj/postfix-2.12.20140701-sasl2-mysql/postfix-2.12-20140701 (Makefile:83 'update') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2727 '/usr/ports/pobj/postfix-2.12.20140701-sasl2-mysql/.build_done') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1922 '/usr/ports/packages/i386/all/postfix-2.12.20140701-sasl2-mysql.tgz') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2475 '_internal-package') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2455 'package') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1939 '/var/db/pkg/postfix-2.12.20140701-sasl2-mysql/+CONTENTS') *** Error 1 in /usr/ports/mail/postfix/snapshot (/usr/ports/infrastructure/mk/bsd.port.mk:2455 'install') What is the problem? Has been lost something? Thanks. Kerberos was removed, upgrading needed to remove old libraries. See the final steps of the upgrade.. http://www.openbsd.org/faq/upgrade56.html#final The port for Kerberos is here.. security/heimdal
hplip cups
I'm trying to set up a print server using Openbsd 5.6 and hplip-cups. This is what the logs are showing me: D [11/Nov/2014:16:32:53 -0600] [Job 13] HP_Photosmart_C4200_series: can't load library 'libfontconfig.so.9.1' D [11/Nov/2014:16:32:53 -0600] [Job 13] HP_Photosmart_C4200_series:/usr/lib/libstdc++.so.57.0: /usr/local/lib/libestdc++ .so.16.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program D [11/Nov/2014:16:32:53 -0600] [Job 13] PID 17335 (/usr/local/libexec/cups/filter/pdftopdf) stopped with status 1. D [11/Nov/2014:16:32:53 -0600] [Job 13] Hint: Try setting the LogLevel to debug to find out more. D [11/Nov/2014:16:32:53 -0600] [Job 13] prnt/hpcups/HPCupsFilter.cpp 530: cupsRasterOpen failed, fd = 0 D [11/Nov/2014:16:32:53 -0600] [Job 13] PID 26937 (/usr/local/libexec/cups/filter/gstoraster) stopped with status 1. D [11/Nov/2014:16:32:53 -0600] [Job 13] Hint: Try setting the LogLevel to debug to find out more. D [11/Nov/2014:16:32:53 -0600] [Job 13] prnt/backend/hp.c 902: ERROR: null print job total=0 D [11/Nov/2014:16:32:53 -0600] [Job 13] PID 341 (/usr/local/libexec/cups/filter/hpcups) stopped with status 1. libfontconfig.so.9.1 exists at /usr/X11R6/lib/libfontconfig.so.9.1 I'm not sure what to think about the size mismatch error, and setting LogLevel to debug is an insane amount of logging that didn't show anything else useful to me. If it will help someone else to diagnose the issue I'll gladly post it. Thanks in advance, Edgar
Re: Question about /etc/mail post 5.6 upgrade
On Mon, Nov 10, 2014 at 8:30 AM, Scott Vanderbilt li...@datagenic.com wrote: These changes came after 5.6 was RTM, and are reflected in -current as of 15 September or so. See http://www.openbsd.org/faq/current.html. Removing sendmail as outlined above will make things like 'make release' break. I upgraded to 5.6 and decided to remove sendmail. I needed to add it back because I couldn't make a release.
Re: Advice requested -- how best to copy a disk
On 11/11/14 14:23, Dave Anderson wrote: My apologies for what seems to be a rather simple and not really OpenBSD specific question, but searching hasn't found any good answers. I've got an old PC running i386 OpenBSD which is dying; the disk seems to be good, but I need to replace the rest of the hardware. Usually I'd just move the disk to the new system, but the old system is EIDE and the new one is SATA -- so I need to copy the old disk (which I can put in an external enclosure and connect to the new system via USB) to the new one (which is a different size and probably a different geometry, so the new and old partitions probably won't be exactly the same sizes). It's clearly possible to boot the new system from an install CD (or, if necessary, a USB stick with a full install on it) then fdisk and disklabel the new disk and newfs / dump|restore the partitions one by one, followed up by installboot, editing the duids in /etc/fstab, and fixing up /etc/hostname.*, but I'm hoping that there's a better way. Thanks in advance for any suggestions (or confirmations that there is no better way). Dave Personally, I'd probably just do a pkg_info to see all the installed packages, build out a new machine EXACTLY as I want it on the new disk, install the same packages, copy over the config files and any other data files. Done. Save the old machine (or the disk in a usb enclosure) in case you find something missing. In cases where I was copying over multi-boot systems including OSs that are not so portable, I've put the old disk in an external enclosure, used dd to copy the entire disk image from the old disk to the new disk, and then fluffed things out on the new disk...but it's hard to justify with OpenBSD, as the reconfig of a new system is usually pretty easy. Nick.
syweb nginx
I am running amd 5.6 and playing little bit with sysutils/symon Thinks are looking good and I have close to 100 MB of data in /var/www/symon/rrds/localhost I am trying to plot the data using syweb. I am sure that my installation of php_fpm and nginx is works correctly as I am nfsen working properly. Pointing browser http://localhost/syweb/configtest.php Gives Testing rrdtool: apache or php setup faulty: cannot execute /bin/rrdtool However I did copy rrdtool binaries to /var/www/bin/ and they have correct permission. I am just wondering if syweb works with Nginx or require Apache as the setup.inc indicates. Thanks, Predrag P.S. I also found phpSymon http://ryanflannery.net/hacking/phpsymon/ which looks dormant. Any other alternatives?
Re: syweb nginx
On Wed Nov 12 2014 05:04:02 GMT+0100 (CET), Predrag Punosevac wrote: I am running amd 5.6 and playing little bit with sysutils/symon Thinks are looking good and I have close to 100 MB of data in /var/www/symon/rrds/localhost I am trying to plot the data using syweb. I am sure that my installation of php_fpm and nginx is works correctly as I am nfsen working properly. Pointing browser http://localhost/syweb/configtest.php Gives Testing rrdtool: apache or php setup faulty: cannot execute /bin/rrdtool Note here the path '/bin/rrdtool' not '/var/www/...' However I did copy rrdtool binaries to /var/www/bin/ and they have correct permission. Right, but how do you know that's what is being used. Have you tried a symlink from bin...? I assume it is a webapp script that calls rrdtool, does it have a conf to say where to find it? HTH, george I am just wondering if syweb works with Nginx or require Apache as the setup.inc indicates. Thanks, Predrag P.S. I also found phpSymon http://ryanflannery.net/hacking/phpsymon/ which looks dormant. Any other alternatives? --
Re: Question about /etc/mail post 5.6 upgrade
On Tue, 11 Nov 2014 15:31:27 -0800 Joe S js.li...@gmail.com wrote: On Mon, Nov 10, 2014 at 8:30 AM, Scott Vanderbilt li...@datagenic.com wrote: These changes came after 5.6 was RTM, and are reflected in -current as of 15 September or so. See http://www.openbsd.org/faq/current.html. Removing sendmail as outlined above will make things like 'make release' break. I upgraded to 5.6 and decided to remove sendmail. I needed to add it back because I couldn't make a release. what error messages are you getting? i've been following -current for a while, and deleted sendmail when that page was updated, but have not had any problems (did 'make release' last night). my situation is not exactly the same as yours though, since i did a fresh install from a snapshot before following -current. just as an aside, i usually pipe the output thru 'tee' to save a copy for later checking eg if i get errors.
Re: kernel page fault trap
Can't you make the kvm run the console as a serial and then telnet or something to get that serial output from the guest? 2014-11-11 22:12 GMT+01:00 Nikos Skalkotos skalk...@gmail.com: Hello, Is there a way to output the rescue disk console on a serial port? It will help for the copy-paste because I don't have physical access to the server I'm running the VM's and I'm using VNC to grab the console. On 11 November 2014 22:21, Philip Guenther guent...@gmail.com wrote: On Tue, Nov 11, 2014 at 5:43 AM, Nikos Skalkotos skalk...@grnet.gr wrote: I have a kernel page fault in OpenBSD 5.6 100% reproducible (I think I can reproduce it in older versions too). I've created an OpenBSD installation in Linux through kvm on a 1GB hard disk with just a root partition (a), by booting the install56.iso cdrom with a command like this: kvm -smp 1 -m 2048 -boot d -drive \ file=/dev/images/openbsd-5.6,format=raw,cache=none,if=virtio -cdrom /tmp/install56.iso -vnc :0 The system boots fine with a command like this: kvm -m 2048 -drive file=/dev/images/openbsd,format=raw,cache=none,if=virtio If I then copy it into a 100GB volume: dd if=/dev/images/openbsd of=/dev/images/tmp1 bs=4M And try to boot it, it still boots fine. I then boot into the VM's rescue disk: ... Fix the MBR to use the entire disk: # fdisk -i wd0 And change the disklabel: disklabel -E sd0 ... To make it easier to analyze and reproduce this, can you provide the output of fdisk and disklabel both before changing anything and then again afterwards? Hmm, and how about the output of dumpfs /dev/rsd0a | head -23 before and after too? Philip Guenther -- May the most significant bit of your life be positive.
