Bug#1051161: postfix: Postfix does not start with default configuration
Package: postfix Version: 3.7.6-0+deb12u2 Severity: important Dear Maintainer, On a fresh Debian 12 Bookworm installation, the Postfix package was installed and configured as "Internet site". The service does not start. "systemctl start postfix" shows as "started (exited)". journalctl for the service just says that "A start job for unit postfix.service has finished successfully." but no processes are running. It is possible to start Postfix with the command "postfix start", then it runs as expected. But I would expect the systemd configuration to do this. Regards, Henrik Stoerner -- System Information: Debian Release: 12.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages postfix depends on: ii adduser3.134 ii cpio 2.13+dfsg-7.1 ii debconf [debconf-2.0] 1.5.82 ii dpkg 1.21.22 ii e2fsprogs 1.47.0-2 ii init-system-helpers1.65.2 ii libc6 2.36-9+deb12u1 ii libdb5.3 5.3.28+dfsg2-1 ii libicu72 72.1-3 ii libnsl21.3.0-2 ii libsasl2-2 2.1.28+dfsg-10 ii libssl33.0.9-1 ii netbase6.4 ii ssl-cert 1.1.2 Versions of packages postfix recommends: ii ca-certificates 20230311 ii python3 3.11.2-1+b1 Versions of packages postfix suggests: ii dovecot-core [dovecot-common] 1:2.3.19.1+dfsg1-2.1 ii libsasl2-modules 2.1.28+dfsg-10 ii mutt [mail-reader] 2.2.9-1+b1 ii postfix-cdb3.7.6-0+deb12u2 ii postfix-doc3.7.6-0+deb12u2 pn postfix-ldap pn postfix-lmdb pn postfix-mta-sts-resolver ii postfix-mysql 3.7.6-0+deb12u2 ii postfix-pcre 3.7.6-0+deb12u2 pn postfix-pgsql ii postfix-sqlite 3.7.6-0+deb12u2 pn procmail pn resolvconf ii ufw0.36.2-1 -- debconf information: postfix/not_configured: postfix/newaliases: false postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128 postfix/destinations: $myhostname, vmail2.vservers, localhost.vservers, , localhost postfix/bad_recipient_delimiter: postfix/relayhost: * postfix/main_mailer_type: Internet Site postfix/rfc1035_violation: false postfix/procmail: false postfix/root_address: postfix/mailbox_limit: 0 postfix/chattr: false * postfix/mailname: mx2.hswn.dk postfix/recipient_delim: + postfix/protocols: all
Bug#981921: dovecot-imapd: imapd crashes with "Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0)"
Package: dovecot-imapd
Version: 1:2.3.4.1-5+deb10u5
Severity: normal
Dear Maintainer,
since late january I have seen a couple of crashes of imapd in the logs. The
error message logged is
Panic: file message-parser.c: line 174 (message_part_finish): assertion failed:
(ctx->nested_parts_count > 0)
And a backtrace:
imap(usern...@domain.dk)<26983>: Error: Raw
backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb6fb) [0x7ff4f72486fb] ->
/usr/lib/dovecot/libdovecot.so.0(+0xdb791) [0x7ff4f7248791] ->
/usr/lib/dovecot/libdovecot.so.0(+0x4a171) [0x7ff4f71b7171] ->
/usr/lib/dovecot/libdovecot.so.0(+0x474d4) [0x7ff4f71b44d4] ->
/usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x104)
[0x7ff4f7230914] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa8)
[0x7ff4f7232ec8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcf89e)
[0x7ff4f73cb89e] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45)
[0x7ff4f734d445] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd0774)
[0x7ff4f73cc774] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd1a68)
[0x7ff4f73cda68] ->
/usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x61)
[0x7ff4f73ce0e1] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28)
[0x7ff4f7356e58] -> dovecot/imap(+0x2695f) [0x55a389c4295f] ->
dovecot/imap(command_exec+0x70) [0x55a389c3bdc0] -> dovecot/imap(+0x25f12)
[0x55a389c41f12] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x111)
[0x7ff4f725e9c1] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd0)
[0x7ff4f7260140] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c)
[0x7ff4f725ec4c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40)
[0x7ff4f725edb0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
[0x7ff4f71df103] -> dovecot/imap(main+0x325) [0x55a389c2cbf5] ->
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7ff4f6fc809b] ->
dovecot/imap(_start+0x2a) [0x55a389c2cd8a]
-- Package-specific info:
dovecot configuration
-
# 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.4 ()
# OS: Linux 4.19.0-14-amd64 x86_64 Debian 10.7 xfs
# Hostname: vmail.vservers
protocol lda {
info_log_path = /var/log/dovecot-lda/dovecot-lda-info.log
log_path = /var/log/dovecot-lda/dovecot-lda-errors.log
mail_plugins = " sieve"
}
protocol imap {
mail_max_userip_connections = 20
}
-- System Information:
Debian Release: 10.7
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-14-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dovecot-imapd depends on:
ii dovecot-core 1:2.3.4.1-5+deb10u5
ii libbz2-1.01.0.6-9.2~deb10u1
ii libc6 2.28-10
ii liblz4-1 1.8.3-1
ii liblzma5 5.2.4-1
ii ucf 3.0038+nmu1
ii zlib1g1:1.2.11.dfsg-1
dovecot-imapd recommends no packages.
Versions of packages dovecot-imapd suggests:
ii ufw 0.36-1
Versions of packages dovecot-imapd is related to:
ii dovecot-core [dovecot-common] 1:2.3.4.1-5+deb10u5
pn dovecot-dev
pn dovecot-gssapi
ii dovecot-imapd 1:2.3.4.1-5+deb10u5
pn dovecot-ldap
pn dovecot-lmtpd
ii dovecot-managesieved 1:2.3.4.1-5+deb10u5
ii dovecot-mysql 1:2.3.4.1-5+deb10u5
pn dovecot-pgsql
ii dovecot-pop3d 1:2.3.4.1-5+deb10u5
ii dovecot-sieve 1:2.3.4.1-5+deb10u5
pn dovecot-sqlite
-- no debconf information
Bug#856733: linux-image-3.16.0-4-amd64: Xen guest has multiple stack dumps, ending with spontaneous reboot
Package: src:linux Version: 3.16.39-1+deb8u1 Severity: important Dear Maintainer, after installing the latest linux-image update, one of my Xen guests suddenly logged multiple kernel stacktraces. The initial one was this: Mar 4 03:05:14 saltmaster kernel: [798533.537459] WARNING: CPU: 1 PID: 9901 at /build/linux-NAZ6Cx/linux-3.16.39/arch/x86/xen/multicalls.c:129 __xen_mc_entry+0x110/0x180() Mar 4 03:05:14 saltmaster kernel: [798533.537463] Modules linked in: x86_pkg_temp_thermal thermal_sys intel_rapl coretemp crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper evdev cryptd pcspkr autofs4 ext4 crc16 mbcache jbd2 xen_netfront crct10di f_pclmul crct10dif_common xen_blkfront crc32c_intel Mar 4 03:05:14 saltmaster kernel: [798533.537483] CPU: 1 PID: 9901 Comm: salt-master Not tainted 3.16.0-4-amd64 #1 Debian 3.16.39-1+deb8u1 Mar 4 03:05:14 saltmaster kernel: [798533.537486] 81514c41 0009 Mar 4 03:05:14 saltmaster kernel: [798533.537490] 81068867 01ff 88007adcbd00 Mar 4 03:05:14 saltmaster kernel: [798533.537496] 0001 0150 81005150 01ff Mar 4 03:05:14 saltmaster kernel: [798533.537501] Call Trace: Mar 4 03:05:14 saltmaster kernel: [798533.537507] [] ? dump_stack+0x5d/0x78 Mar 4 03:05:14 saltmaster kernel: [798533.537513] [] ? warn_slowpath_common+0x77/0x90 Mar 4 03:05:14 saltmaster kernel: [798533.537517] [] ? __xen_mc_entry+0x110/0x180 Mar 4 03:05:14 saltmaster kernel: [798533.537521] [] ? xen_pin_page+0x58/0x160 Mar 4 03:05:14 saltmaster kernel: [798533.537524] [] ? xen_do_pin+0x50/0x50 Mar 4 03:05:14 saltmaster kernel: [798533.537527] [] ? __xen_pgd_walk+0x2e4/0x310 Mar 4 03:05:14 saltmaster kernel: [798533.537529] [] ? xen_do_pin+0x50/0x50 Mar 4 03:05:14 saltmaster kernel: [798533.537532] [] ? __xen_pgd_pin+0x5b/0x340 Mar 4 03:05:14 saltmaster kernel: [798533.537535] [] ? xen_dup_mmap+0x1e/0x30 Mar 4 03:05:14 saltmaster kernel: [798533.537539] [] ? copy_process.part.25+0x1781/0x1c50 Mar 4 03:05:14 saltmaster kernel: [798533.537543] [] ? do_fork+0xe0/0x3d0 Mar 4 03:05:14 saltmaster kernel: [798533.537547] [] ? __alloc_fd+0x7c/0x120 Mar 4 03:05:14 saltmaster kernel: [798533.537550] [] ? stub_clone+0x69/0x90 Mar 4 03:05:14 saltmaster kernel: [798533.537554] [] ? system_call_fast_compare_end+0x10/0x15 Mar 4 03:05:14 saltmaster kernel: [798533.537556] ---[ end trace ef0d5e3cd38fc131 ]--- immediately followed by this: Mar 4 03:05:14 saltmaster kernel: [798533.538577] WARNING: CPU: 1 PID: 9901 at /build/linux-NAZ6Cx/linux-3.16.39/arch/x86/xen/multicalls.c:129 __xen_pgd_pin+0x103/0x340() Mar 4 03:05:14 saltmaster kernel: [798533.538580] Modules linked in: x86_pkg_temp_thermal thermal_sys intel_rapl coretemp crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper evdev cryptd pcspkr autofs4 ext4 crc16 mbcache jbd2 xen_netfront crct10di f_pclmul crct10dif_common xen_blkfront crc32c_intel Mar 4 03:05:14 saltmaster kernel: [798533.538597] CPU: 1 PID: 9901 Comm: salt-master Tainted: GW 3.16.0-4-amd64 #1 Debian 3.16.39-1+deb8u1 Mar 4 03:05:14 saltmaster kernel: [798533.538600] 81514c41 0009 Mar 4 03:05:14 saltmaster kernel: [798533.538604] 81068867 000edf90 8800fa16 88007bfb1800 Mar 4 03:05:14 saltmaster kernel: [798533.538608] 8800843fe000 77ff8000 81009ad3 88007bfb1800 Mar 4 03:05:14 saltmaster kernel: [798533.538611] Call Trace: Mar 4 03:05:14 saltmaster kernel: [798533.538614] [] ? dump_stack+0x5d/0x78 Mar 4 03:05:14 saltmaster kernel: [798533.538617] [] ? warn_slowpath_common+0x77/0x90 Mar 4 03:05:14 saltmaster kernel: [798533.538621] [] ? __xen_pgd_pin+0x103/0x340 Mar 4 03:05:14 saltmaster kernel: [798533.538624] [] ? xen_dup_mmap+0x1e/0x30 Mar 4 03:05:14 saltmaster kernel: [798533.538627] [] ? copy_process.part.25+0x1781/0x1c50 Mar 4 03:05:14 saltmaster kernel: [798533.538630] [] ? do_fork+0xe0/0x3d0 Mar 4 03:05:14 saltmaster kernel: [798533.538634] [] ? __alloc_fd+0x7c/0x120 Mar 4 03:05:14 saltmaster kernel: [798533.538637] [] ? stub_clone+0x69/0x90 Mar 4 03:05:14 saltmaster kernel: [798533.538641] [] ? system_call_fast_compare_end+0x10/0x15 Mar 4 03:05:14 saltmaster kernel: [798533.538643] ---[ end trace ef0d5e3cd38fc132 ]--- After this, multiple stacktraces were logged without much call trace info: Mar 4 03:05:14 saltmaster kernel: [798533.538726] WARNING: CPU: 0 PID: 0 at /build/linux-NAZ6Cx/linux-3.16.39/arch/x86/xen/multicalls.c:129 xen_end_context_switch+0xe/0x20() Mar 4 03:05:14 saltmaster kernel: [798533.538732] Modules linked in: x86_pkg_temp_thermal thermal_sys intel_rapl coretemp crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper evdev cryptd pcspkr autofs4 ext4 crc16
Bug#759809: linux-image-3.2.0-4-amd64: USB 3 devices fail, logging "xHCI xhci_drop_endpoint called with disabled ep ffff8802165db0c0"
Package: src:linux Version: 3.2.60-1+deb7u3 Severity: normal Dear Maintainer, Yesterday morning I rebooted a machine running Wheezy (stable) after installing kernel upgrade 3.2.60-1+deb7u3. Upon reboot, the machine hung while detecting two USB-3 attached harddisks. After unplugging the two harddisks, boot continued. Re-connecting them caused the same errors to appear in the log. The kernel log below shows this after 35 seconds. Connecting the two disks to USB-2 ports worked without problems, and they worked fine on previous kernel - which was either 3.2.60-1+deb7u2 or u1 (not entirely sure which, but probably u2). I have tried connecting another device (an APC UPS device) to the USB-3 port, and this is detected by the kernel but talking to the device fails. Please note that the USB device listing in the bugreport is from the current boot, so the devices have been changed to other connections to avoid using the USB-3 ports. The problem is reproducible, I see the same behaviour on an identical system (same motherboard, different USB devices). -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u3 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=61d5a246-0740-4e6e-8745-f69c986ec68d ro irqpoll ip=192.168.1.1::192.168.1.254:255.255.255.0::eth1:off ** Not tainted ** Kernel log: Aug 29 08:01:09 blixen kernel: imklog 5.8.11, log source = /proc/kmsg started. Aug 29 08:01:09 blixen kernel: [0.00] Initializing cgroup subsys cpuset Aug 29 08:01:09 blixen kernel: [0.00] Initializing cgroup subsys cpu Aug 29 08:01:09 blixen kernel: [0.00] Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u3 Aug 29 08:01:09 blixen kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=61d5a246-0740-4e6e-8745-f69c986ec68d ro irqpoll ip=192.168.1.1::192.168.1.254:255.255.255.0::eth1:off Aug 29 08:01:09 blixen kernel: [0.00] BIOS-provided physical RAM map: Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: - 0009c000 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 0009c000 - 000a (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 000e - 0010 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 0010 - 2000 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 2000 - 2020 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 2020 - 4000 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 4000 - 4020 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 4020 - da38d000 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: da38d000 - da93e000 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: da93e000 - dab9 (ACPI NVS) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dab9 - dab9e000 (ACPI data) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dab9e000 - dabbe000 (ACPI NVS) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dabbe000 - dabc3000 (ACPI data) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dabc3000 - dac06000 (ACPI NVS) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dac06000 - db00 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: db80 - dfa0 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: f800 - fc00 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: fec0 - fec01000 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: fed0 - fed04000 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: fed1c000 - fed2 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: fee0 - fee01000 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: ff00 - 0001 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 0001 - 00021f60 (usable) Aug 29 08:01:09 blixen kernel: [0.00] NX (Execute Disable) protection: active Aug 29 08:01:09 blixen kernel: [0.00] SMBIOS 2.6 present. Aug 29 08:01:09 blixen kernel: [0.00] DMI: System manufacturer System Product Name/P8H67-M PRO, BIOS 3604 02/23/2012 Aug 29 08:01:09 blixen kernel: [0.00] e820 update range: - 0001 (usable) ==> (reserved) Aug 29 08:01:
Bug#741989: linux-image-3.2.0-4-amd64: Regression bug #741989 also in Stable kernel 3.2.60-1+deb7u3 Followup-For: Bug #741989 Package: src:linux Version: 3.2.60-1+deb7u3
Dear Maintainer, This morning I rebooted a machine runnig Wheezy (stable) after installing kernel upgrade 3.2.60-1+deb7u3. Upon reboot, the machine hung while detecting two USB-3 attached harddisks. After unplugging the two harddisks, boot continued. Re-connecting them caused the same errors to appear in the log. The kernel log below shows this after 35 seconds. Connecting the two disks to a USB-2 port worked without problems, and they worked fine on previous kernel - which was either 3.2.60-1+deb7u2 or u1 (not entirely sure which, but probably u2). I have tried connecting another device (an APC UPS device) to the USB-3 port, and this is detected by the kernel but talking to the device fails. Please note that the USB device listing in the bugreport is from the current boot, and the devices have been changed to other connections to avoid using the USB-3 ports. The problem is reproducible. The behaviour is identical to the bug report I am filing this with, but since this is the 3.2.0 stable kernel I am not sure if it is the same bug. -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u3 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=61d5a246-0740-4e6e-8745-f69c986ec68d ro irqpoll ip=192.168.1.1::192.168.1.254:255.255.255.0::eth1:off ** Not tainted ** Kernel log: Aug 29 08:01:09 blixen kernel: imklog 5.8.11, log source = /proc/kmsg started. Aug 29 08:01:09 blixen kernel: [0.00] Initializing cgroup subsys cpuset Aug 29 08:01:09 blixen kernel: [0.00] Initializing cgroup subsys cpu Aug 29 08:01:09 blixen kernel: [0.00] Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u3 Aug 29 08:01:09 blixen kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=61d5a246-0740-4e6e-8745-f69c986ec68d ro irqpoll ip=192.168.1.1::192.168.1.254:255.255.255.0::eth1:off Aug 29 08:01:09 blixen kernel: [0.00] BIOS-provided physical RAM map: Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: - 0009c000 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 0009c000 - 000a (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 000e - 0010 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 0010 - 2000 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 2000 - 2020 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 2020 - 4000 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 4000 - 4020 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 4020 - da38d000 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: da38d000 - da93e000 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: da93e000 - dab9 (ACPI NVS) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dab9 - dab9e000 (ACPI data) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dab9e000 - dabbe000 (ACPI NVS) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dabbe000 - dabc3000 (ACPI data) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dabc3000 - dac06000 (ACPI NVS) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: dac06000 - db00 (usable) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: db80 - dfa0 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: f800 - fc00 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: fec0 - fec01000 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: fed0 - fed04000 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: fed1c000 - fed2 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: fee0 - fee01000 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: ff00 - 0001 (reserved) Aug 29 08:01:09 blixen kernel: [0.00] BIOS-e820: 0001 - 00021f60 (usable) Aug 29 08:01:09 blixen kernel: [0.00] NX (Execute Disable) protection: active Aug 29 08:01:09 blixen kernel: [0.00] SMBIOS 2.6 present. Aug 29 08:01:09 blixen kernel: [0.00] DMI: System manufacturer System Product Name/P8H67-M PRO, BIOS 3604 02/23/2012 Aug 29 08:01:09 blixen kernel: [0.00] e820 update range: - 0001 (usable) ==> (reserved) Aug 29 08:01:09 blixen
Bug#708183: linux-image-3.2.0-4-amd64: File access via symlink on tmpfs filesystem gives "permission denied"
Package: src:linux Version: 3.2.41-2 Severity: important Dear Maintainer, on the 3.2.0-4 kernel, access to a directory via a symlink on a tmpfs filesystem gives "permission denied" - if the tmpfs filesystem mountpoint is not owned by root. The same setup on a 2.6.32-5 (Squeeze) system works fine. Apparently, access via a symlink on a tmpfs filesystem fails if the mountpoint is not owned either by "root" or by the user attempting to use the symlink. This is my test setup: * Two user accounts, "henrik" and "dummy" * Create directories /test/fsdir and /test/memdir * Mount a tmpfs filesystem on /test/memdir * In /test/fsdir: ln -s ../../home/henrik . * In /test/memdir: create the same link * Change owner of tmpfs mountpoint: chown dummy:dummy /test/memdir Now, try this as user "henrik": cd /test/fsdir/henrik --> works cd /test/memdir/henrik --> fails Here are the commands used: << run these as root >> adduser henrik adduser dummy mkdir /test /test/fsdir /test/memdir mount -t tmpfs tmpfs /test/memdir cd /test/fsdir; ln -s ../../home/henrik . cd /test/memdir; ln -s ../../home/henrik . chown dummy:dummy /test/memdir << run these as user henrik >> # This works: cd /test/fsdir/henrik # This fails: cd /test/memdir/henrik Tested on clean installs of Wheezy and Squeeze in a Virtualbox setup, but originally found on a physical server upgraded from Squeeze to Wheezy. -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=0741f671-0f50-4b20-993f-6be28b07d50e ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [1.384269] usb usb1: Manufacturer: Linux 3.2.0-4-amd64 ohci_hcd [1.384270] usb usb1: SerialNumber: :00:06.0 [1.384341] hub 1-0:1.0: USB hub found [1.384353] hub 1-0:1.0: 8 ports detected [1.384671] ahci :00:0d.0: version 3.0 [1.384802] ahci: SSS flag set, parallel bus scan disabled [1.384934] ahci :00:0d.0: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode [1.384937] ahci :00:0d.0: flags: 64bit ncq stag only ccc [1.386052] scsi0 : ahci [1.386160] ata1: SATA max UDMA/133 abar m8192@0xf0806000 port 0xf0806100 irq 21 [1.386363] ata_piix :00:01.1: version 2.13 [1.388085] scsi1 : ata_piix [1.389502] scsi2 : ata_piix [1.389569] ata2: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xd000 irq 14 [1.389572] ata3: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xd008 irq 15 [1.544990] ata3.00: ATAPI: VBOX CD-ROM, 1.0, max UDMA/133 [1.545812] ata3.00: configured for UDMA/33 [1.708334] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [1.708475] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133 [1.708479] ata1.00: 41943040 sectors, multi 128: LBA48 NCQ (depth 31/32) [1.708674] ata1.00: configured for UDMA/133 [1.708816] scsi 0:0:0:0: Direct-Access ATA VBOX HARDDISK1.0 PQ: 0 ANSI: 5 [1.709916] scsi 2:0:0:0: CD-ROMVBOX CD-ROM 1.0 PQ: 0 ANSI: 5 [1.719128] sd 0:0:0:0: [sda] 41943040 512-byte logical blocks: (21.4 GB/20.0 GiB) [1.719153] sd 0:0:0:0: [sda] Write Protect is off [1.719154] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.719164] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.745840] sda: sda1 sda2 < sda5 > [1.746065] sd 0:0:0:0: [sda] Attached SCSI disk [1.747304] sr0: scsi3-mmc drive: 32x/32x xa/form2 tray [1.747306] cdrom: Uniform CD-ROM driver Revision: 3.20 [1.747506] sr 2:0:0:0: Attached scsi CD-ROM sr0 [1.749104] sd 0:0:0:0: Attached scsi generic sg0 type 0 [1.749148] sr 2:0:0:0: Attached scsi generic sg1 type 5 [1.792308] usb 1-1: new full-speed USB device number 2 using ohci_hcd [1.952087] PM: Starting manual resume from disk [1.952090] PM: Hibernation image partition 8:5 present [1.952091] PM: Looking for hibernation image. [1.952418] PM: Image not found (code -22) [1.952419] PM: Hibernation image not present or could not be loaded. [1.973394] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [2.040074] usb 1-1: New USB device found, idVendor=80ee, idProduct=0021 [2.040077] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [2.040078] usb 1-1: Product: USB Tablet [2.040087] usb 1-1: Manufacturer: VirtualBox [2.348442] Switching to clocksource tsc [3.086456] udevd[277]: starting version 175 [3.258308] input: Unspecified device as /devices/virtual/input/input1 [3.259412] vboxguest: major 0, IRQ 20, I/O port d020, MMIO at f040 (size 0x40) [3.259417] vboxguest: Successfully loaded version 4.1.18_Debian (interface 0x00010004) [3.271326] input: PC Speaker as /devices/platform/pcspkr/input/input2 [3.301639] input: Power Button
Bug#651205: tumgreyspf: Please include upstream fix for accepting mail when SPF record has an error
Package: tumgreyspf
Version: 1.35-7
Severity: wishlist
tumgreyspf 1.35 (current version in Debian) causes mail to be rejected, if the
sender-domain has an invalid SPF record (SPF check returns a "Permerror").
This can cause valid mail to be rejected.
In version 1.36, released a couple of weeks ago, this was changed so it is
now configurable what tumgreyspf should do in the case of invalid SPF records,
and the default was set to accept mail when that is the case.
I would suggest this change be included in a future Debian release, and
hopefully
as an update to Squeeze. The attached patch is taken directly from a diff
between
version 1.35 and the new 1.36, and will implement this change.
-- System Information:
Debian Release: 6.0.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages tumgreyspf depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii passwd 1:4.1.4.2+svn3283-2+squeeze1 change and administer password and
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-spf 2.0.5-2 sender policy framework (SPF) modu
ii spfquery1.2.9-4 query SPF (Sender Policy Framework
tumgreyspf recommends no packages.
tumgreyspf suggests no packages.
-- Configuration Files:
/etc/cron.daily/tumgreyspf changed [not included]
-- no debconf information
diff -ur ../tumgreyspf-1.35//tumgreyspf ./tumgreyspf
--- ../tumgreyspf-1.35//tumgreyspf 2009-07-24 01:59:00.0 +0200
+++ ./tumgreyspf 2011-11-24 15:14:38.0 +0100
@@ -119,11 +119,16 @@
))
syslog.syslog('%s: %s; %s' % ( spfReason, queue_id, spfDetail ))
- if spfResult == 'Fail' or spfResult == 'Permerror':
+ if spfResult == 'Fail':
+ return(( 'reject', '%s SPF Reports: %s' % ( queue_id, spfReason )))
+
+ spfAcceptOnPermError = configGlobal.get('spfAcceptOnPermError', 1)
+ if spfResult == 'Permerror' and not spfAcceptOnPermError:
return(( 'reject', '%s SPF Reports: %s' % ( queue_id, spfReason )))
if spfResult == 'Temperror':
return(( 'defer', '%s SPF Reports: %s' % ( queue_id, spfReason )))
+
header = ('Received-SPF: '+ spfResult + ' (' + spfReason
+ ') ' + spfDetail)
diff -ur ../tumgreyspf-1.35//tumgreyspf.conf ./tumgreyspf.conf
--- ../tumgreyspf-1.35//tumgreyspf.conf 2009-07-24 01:59:00.0 +0200
+++ ./tumgreyspf.conf 2011-11-24 15:14:38.0 +0100
@@ -42,3 +42,11 @@
# originating machine, not by IP, sender address, and reciever address
# as is the default. This option honors the 'ingoreLastByte' option.
greylistByIPOnly = 1
+
+# If set to zero, permanent spf errors will reject the message.
+# If set to one, permanent spf errors do not reject the message.
+# Permanent errors are user errors in the domains SPF record
+# that cause SPF processing to fail: for example typos, recursive
+# inclusion, having two spf records for a domain, etc.
+# Default is 1
+spfAcceptOnPermError = 1
Bug#615589: installation-reports: Partitioning completes without creating bios_boot partition required by GRUB
Package: installation-reports Severity: minor Tags: d-i During manual partitioning - at least on 2 TB+ harddisks - the Debian installer creates a GUID partition table (GPT). This type of partitioning requires a small "BIOS boot" partition to be set aside for use by GRUB. However, this is not checked during partitioning. Failing to create this partition causes GRUB installation to fail later in the installation. Unfortunately, this happens AFTER all of the packages have been downloaded and installed, so going back to the partitioning to correct the problem results in the entire installation having to be re-done. The partitioning tool should enforce the creation of a "BIOS boot" partition during partitioning, in the same manner that it forces a partition to be assigned for the root filesystem, and it warns if you do not create a swap partition. It could also suggest a reasonable size for this partition, since there doesn't seem to be any information in the installation documentation about how large this partition should be. The GRUB docs suggest 64 kB or 128 kB http://grub.enbug.org/BIOS_Boot_Partition . -- Package-specific info: Boot method: CD Image version: Debian GNU/Linux 6.0.0 _Squeeze_ - Official amd64 NETINST Binary-1 20110205-14:31 Date: Machine: Homebuilt. Intel motherboard w/ Atom CPU, dual 2 TB SATA harddisks Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[ ] Comments/Problems: -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="6.0 (squeeze) - installer build 20110106+b1" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux jorn 2.6.32-5-amd64 #1 SMP Fri Dec 10 15:35:08 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: nVidia Corporation MCP79 Host Bridge [10de:0a82] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:00.1 RAM memory [0500]: nVidia Corporation MCP79 Memory Controller [10de:0a88] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.0 ISA bridge [0601]: nVidia Corporation MCP79 LPC Bridge [10de:0aad] (rev b2) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.1 RAM memory [0500]: nVidia Corporation MCP79 Memory Controller [10de:0aa4] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.2 SMBus [0c05]: nVidia Corporation MCP79 SMBus [10de:0aa2] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.3 RAM memory [0500]: nVidia Corporation MCP79 Memory Controller [10de:0a89] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.5 Co-processor [0b40]: nVidia Corporation MCP79 Co-processor [10de:0aa3] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:04.0 USB Controller [0c03]: nVidia Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa5] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:04.1 USB Controller [0c03]: nVidia Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa6] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:06.0 USB Controller [0c03]: nVidia Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa7] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:06.1 USB Controller [0c03]: nVidia Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa9] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:08.0 Audio device [0403]: nVidia Corporation MCP79 High Definition Audio [10de:0ac0] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f7] lspci -knn: 00:09.0 PCI bridge [0604]: nVidia Corporation MCP79 PCI Bridge [10de:0aab] (rev b1) lspci -knn: 00:0b.0 SA
Bug#615215: installation-reports: Boot failure after install w/ GPT partitioning on Intel motherboard(s)
Package: installation-reports Severity: grave Tags: d-i Justification: renders package unusable During installation, the partitioning creates a GPT (GUID partition table) on disk, i.e. the old-style "MBR" partition only has a single type 0xEE partition listed. The 0xEE partition is created without the "bootable" flag set. Motherboards with Intel BIOS requires at least one partition to be flagged as bootable, so after installing reboot fails with the BIOS reporting that there is no bootable device present. From some reports on the net, this appears to be a common problem on Intel motherboards. Upgrading to the latest BIOS release from Intel did not solve the problem. Workaround is to run the plain "fdisk" utility from a secondary console during installation, and use the "a" command to toggle the GPT partition to "bootable". -- Package-specific info: Boot method: CD Image version: Debian GNU/Linux 6.0.0 _Squeeze_ - Official amd64 NETINST Binary-1 20110205-14:31 Date: Machine: Homebuilt. Intel DCL945GCF2 motherboard, Western Digital WDC WD20EARS 2 TB SATA disk Partitions: Model: ATA WDC WD20EARS-00M (scsi) Disk /dev/sda: 2000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End SizeFile system NameFlags 1 17,4kB 10,0MB 10,0MB bios_grub 2 10,0MB 1010MB 1000MB linux-swap(v1) 3 1010MB 51,0GB 50,0GB md_root raid 4 51,0GB 151GB 100GB md_var raid 5 151GB 1151GB 1000GB md_home raid 6 1151GB 2000GB 849GB md_netdisk raid Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="6.0 (squeeze) - installer build 20110106+b1" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux jorn 2.6.32-5-amd64 #1 SMP Fri Dec 10 15:35:08 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: nVidia Corporation MCP79 Host Bridge [10de:0a82] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:00.1 RAM memory [0500]: nVidia Corporation MCP79 Memory Controller [10de:0a88] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.0 ISA bridge [0601]: nVidia Corporation MCP79 LPC Bridge [10de:0aad] (rev b2) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.1 RAM memory [0500]: nVidia Corporation MCP79 Memory Controller [10de:0aa4] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.2 SMBus [0c05]: nVidia Corporation MCP79 SMBus [10de:0aa2] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.3 RAM memory [0500]: nVidia Corporation MCP79 Memory Controller [10de:0a89] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:03.5 Co-processor [0b40]: nVidia Corporation MCP79 Co-processor [10de:0aa3] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: 00:04.0 USB Controller [0c03]: nVidia Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa5] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:04.1 USB Controller [0c03]: nVidia Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa6] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:06.0 USB Controller [0c03]: nVidia Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa7] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:06.1 USB Controller [0c03]: nVidia Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa9] (rev b1) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:83f9] lspci -knn: Kernel driver in use: ehci_hcd l
Bug#516571: gdb on SPARC fails with ""regcache.c:175: internal-error: register_size:" assertion failure
Package: gdb Version: 6.4.90.dfsg-1 Severity: normal While trying to debug a program on Debian/SPARC I loaded the binary and a core-dump into gdb. A simple "bt" then caused the following error (after displaying part of the backtrace, but not all of it): /build/buildd/gdb-6.4.90.dfsg/gdb/regcache.c:175: internal-error: register_size: Assertion `regnum >= 0 && regnum < (NUM_REGS + NUM_PSEUDO_REGS)' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) I have seen this happen with different binaries and core-files. A sample set of input files can be provided. -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-sparc64 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gdb depends on: ii libc6 2.3.6.ds1-13etch9 GNU C Library: Shared libraries ii libncurses55.5-5 Shared libraries for terminal hand ii libreadline5 5.2-2 GNU readline and history libraries gdb recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#422324: Acknowledgement (linux-image-2.6.18-4-footbridge: System spontaneously reboots, logs "NWFPE: ntpd[1694] takes exception 00000001")
Hi Martin, I'm sorry, but I no longer have access to this hardware so I cannot tell if the problem has been resolved. Regards, Henrik On Tue, Jun 10, 2008 at 11:16:25AM +0200, Martin Michlmayr wrote: > * Henrik Stoerner <[EMAIL PROTECTED]> [2007-05-05 11:02]: > > I checked the kernel logs looking for this error message. The system > > was upgraded to Etch on April 10, and there are NO entries of the > > NWFPE log until after the DSA-1286-1 security update is installed. > > So it looks like this might be related to the changes introduced with > > this update. > > Henrik, do you still see this problem? > > -- > Martin Michlmayr > http://www.cyrius.com/ -- Henrik Storner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422324: Acknowledgement (linux-image-2.6.18-4-footbridge: System spontaneously reboots, logs "NWFPE: ntpd[1694] takes exception 00000001")
I checked the kernel logs looking for this error message. The system was upgraded to Etch on April 10, and there are NO entries of the NWFPE log until after the DSA-1286-1 security update is installed. So it looks like this might be related to the changes introduced with this update. Going through the System.map file, it appears that the exception occurs in the "PerformFIX" routine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#422324: linux-image-2.6.18-4-footbridge: System spontaneously reboots, logs "NWFPE: ntpd[1694] takes exception 00000001"
Package: linux-image-2.6.18-4-footbridge Version: 2.6.18.dfsg.1-12etch1 Severity: grave Justification: causes non-serious data loss After updating to the kernel version released with DSA-1286-1, the system has begun to spontaneously reboot. This is a small Netwinder system, which has been running stable for 3 years now on Debian Sarge. It also logs this message in the kernel log: NWFPE: ntpd[1694] takes exception 0001 at c003118c from 0002d644 although this does not trigger the reboot (there is one such entry in the "dmesg" output now, and the system is still running). I'm attaching the dmesg output. The system runs ntpd, dhcpd, nutups, and the dnscache+tinydns utilities (not in Debian). The system gets power through a UPS, so there hasn't been a power outage. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: arm (armv4l) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-footbridge Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.18-4-footbridge depends on: ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85g tools for generating an initramfs ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo linux-image-2.6.18-4-footbridge recommends no packages. -- debconf information: linux-image-2.6.18-4-footbridge/postinst/depmod-error-2.6.18-4-footbridge: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-footbridge/prerm/would-invalidate-boot-loader-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-footbridge/prerm/removing-running-kernel-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/postinst/old-initrd-link-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/postinst/old-dir-initrd-link-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/preinst/abort-overwrite-2.6.18-4-footbridge: linux-image-2.6.18-4-footbridge/preinst/failed-to-move-modules-2.6.18-4-footbridge: * linux-image-2.6.18-4-footbridge/preinst/already-running-this-2.6.18-4-footbridge: linux-image-2.6.18-4-footbridge/preinst/abort-install-2.6.18-4-footbridge: linux-image-2.6.18-4-footbridge/postinst/depmod-error-initrd-2.6.18-4-footbridge: false linux-image-2.6.18-4-footbridge/preinst/lilo-initrd-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/postinst/create-kimage-link-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/postinst/bootloader-error-2.6.18-4-footbridge: linux-image-2.6.18-4-footbridge/preinst/elilo-initrd-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/postinst/old-system-map-link-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/preinst/overwriting-modules-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/preinst/bootloader-initrd-2.6.18-4-footbridge: true linux-image-2.6.18-4-footbridge/postinst/kimage-is-a-directory: linux-image-2.6.18-4-footbridge/preinst/initrd-2.6.18-4-footbridge: linux-image-2.6.18-4-footbridge/postinst/bootloader-test-error-2.6.18-4-footbridge: Linux version 2.6.18-4-footbridge (Debian 2.6.18.dfsg.1-12etch1) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Sun Apr 15 11:11:12 UTC 2007 CPU: StrongARM-110 [4401a104] revision 4 (ARMv4), cr=517f Machine: Rebel-NetWinder Converting old-style param struct to taglist ATAG_INITRD is deprecated; please update your bootloader. Memory policy: ECC disabled, Data cache writeback On node 0 totalpages: 16384 DMA zone: 16384 pages, LIFO batch:3 Built 1 zonelists. Total pages: 16384 Kernel command line: ide0=autotune noinitrd root=/dev/hda2 console=tty0 netconfig_eth0=disk netconfig_eth1=disk ide_setup: ide0=autotune -- OBSOLETE OPTION, WILL BE REMOVED SOON! PID hash table entries: 512 (order: 9, 2048 bytes) start_kernel(): bug: interrupts were enabled early Console: colour dummy device 80x30 Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 64MB = 64MB total Memory: 60208KB available (2512K code, 563K data, 116K init) Calibrating delay loop... 185.54 BogoMIPS (lpj=927744) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: failed, enabling work-around checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd Freeing initrd memory: 1458K NET: Registered protocol family 16 PCI: DC21285 footbridge, revision 03, in central function mode PCI: bus0: Fast back to back transfers disabled PCI: Ignore bogus resource 1 [3f6:3f6] of :00:0c.1 PCI: Ignore bogus resource 3 [376:376] of :00:0c.1 Linux Plug and Play Support v0.97 (c)
Bug#327083: dhcping: Loops indefinitely while parsing commandline options
Package: dhcping
Version: 1.2-2
Severity: grave
Tags: patch
Justification: renders package unusable
dhcping uses getopt(3) to parse commandline options. In doing
this, it goes into an infinite loop while parsing the command
"dhcping -c 172.16.10.3 -s 172.16.10.2 -h 00:10:57:C0:1B:E6"
The code in question is
char ch;
...
while ((ch = getopt(argc,argv,"c:g:h:iqrs:t:vV"))>0) {
getopt() returns -1 at the end of the options, but when assigned to a
"char" variable this becomes the value 255. Hence the test is always
true, and the while... loops indefinitely.
The simple patch (attached) changes the variable from a char to an int.
-- System Information:
Debian Release: 3.1
Architecture: arm (armv4l)
Kernel: Linux 2.4.27-netwinder
Locale: LANG=da_DK, LC_CTYPE=da_DK (charmap=ISO-8859-1)
Versions of packages dhcping depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
-- no debconf information
--- dhcping.c.orig 2002-01-27 03:18:58.0 +0100
+++ dhcping.c 2005-09-07 15:20:18.0 +0200
@@ -70,7 +70,7 @@
int maxwait=3;
void doargs(int argc,char **argv) {
-char ch;
+int ch;
inform=request=verbose=VERBOSE=quiet=0;
ci=gi=server="0.0.0.0";
Bug#315549: kernel-image-2.6.8-2-sparc64: Fails to recognize and start md2 during boot
Package: kernel-image-2.6.8-2-sparc64 Version: 2.6.8-15 Severity: normal This kernel fails to recognize all LVM RAID-1 devices. It will automatically detect md0 and md1, but fails to detect md2. During bootup it therefore fails to mount the filesystem on this partition and drops to a console prompt. Running mdadm --assemble /dev/md2 /dev/sda5 /dev/sdb5 correctly recognizes and starts the md2 device, and I can bootup normally. All partitions are flagged as "Linux raid autodetect" and a 2.4 kernel picks them up automatically. Included "dmesg.txt" with the dmesg output; also "fdisk.txt" lists the disk partitions on the sda and sdb devices (identical). -- System Information: Debian Release: 3.1 Architecture: sparc (sparc64) Kernel: Linux 2.6.8-2-sparc64 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-image-2.6.8-2-sparc64 depends on: ii initrd-tools 0.1.81.1 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information PROMLIB: Sun IEEE Boot Prom 3.23.1 1999/07/16 12:08 Linux version 2.6.8-2-sparc64 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #1 Wed Mar 23 04:23:37 EST 2005 ARCH: SUN4U Ethernet address: 08:00:20:e1:b2:3e On node 0 totalpages: 130171 DMA zone: 130171 pages, LIFO batch:8 Normal zone: 0 pages, LIFO batch:1 HighMem zone: 0 pages, LIFO batch:1 Built 1 zonelists Kernel command line: root=/dev/md0 PID hash table entries: 4096 (order 12: 65536 bytes) Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 6, 524288 bytes) Memory: 1032000k available (1992k kernel code, 600k data, 152k init) [f800,bff1e000] Calibrating delay loop... 897.02 BogoMIPS Mount-cache hash table entries: 512 (order: 0, 8192 bytes) checking if image is initramfs...it isn't (ungzip failed); looks like an initrd Freeing initrd memory: 3128k freed NET: Registered protocol family 16 PCI: Probing for controllers. PCI: Found PSYCHO, control regs at 01fe PSYCHO: Shared PCI config space at 01fe0100 PCI-IRQ: Routing bus[ 0] slot[ 1] map[0] to INO[21] PCI-IRQ: Routing bus[ 0] slot[ 3] map[0] to INO[20] PCI-IRQ: Routing bus[ 0] slot[ 3] map[0] to INO[26] PCI0(PBMB): Bus running at 33MHz PCI-IRQ: Routing bus[81] slot[ 0] map[1] to INO[01] PCI-IRQ: Routing bus[81] slot[ 1] map[1] to INO[02] PCI-IRQ: Routing bus[81] slot[ 2] map[1] to INO[03] PCI-IRQ: Routing bus[81] slot[ 3] map[1] to INO[00] PCI0(PBMA): Bus running at 33MHz ebus0: [auxio] [power] [SUNW,pll] [sc] [se] [su] [su] [ecpp] [fdthree] [eeprom] [flashprom] power: Control reg at 01fff1724000 ... not using powerd. usbcore: registered new driver usbfs usbcore: registered new driver hub VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 8192 bytes) devfs: 2004-01-31 Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x0 Initializing Cryptographic API Console: switching to mono PROM 80x34 rtc_init: no PC rtc found su0 at 0x01fff13062f8 (irq = 4,7ea) is a 16550A su1 at 0x01fff13083f8 (irq = 9,7e9) is a 16550A ttyS0 at MMIO 0x1fff140 (irq = 7125984) is a SAB82532 V3.2 ttyS1 at MMIO 0x1fff1400040 (irq = 7125984) is a SAB82532 V3.2 Console: ttyS0 (SAB82532) Using anticipatory io scheduler RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize loop: loaded (max 8 devices) Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver mice: PS/2 mouse device common for all mice input: Sun Mouse on su/serio0 NET: Registered protocol family 2 IP: routing cache hash table of 16384 buckets, 128Kbytes TCP: Hash tables configured (established 131072 bind 65536) NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 3128 blocks [1 disk] into ram disk... |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\done. VFS: Mounted root (cramfs filesystem) readonly. md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: raid1 personality registered as nr 3 SCSI subsystem initialized sym0: <875> rev 0x14 at pci 0001:00:03.0 irq 4,7e0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym0: SCSI BUS has been reset. scsi0 : sym-2.1.18j Vendor: FUJITSU Model: MAN3184M SUN18G Rev: 1502 Type: Direct-Access ANSI SCSI revision: 02 sym0:0:0: tagged command queuing ena
