Bug#1050588: bookworm-pu: package nsis/3.08-3+deb12u1
Jonathan Wiltshire wrote: ... Thanks. The bug #1050288 isn't fixed in unstable according to the BTS, which is a requirement. What's the status? The problem described in #1050288 does not longer occur since NSIS 3.09. The problem appeared in Debian 12 because the Mingw-w64 toolchain now enables ASLR (and therefore emits relocation information) by default but NSIS does not support relocation information. NSIS upstream addressed this in the build recipes of 3.09. I could confirm that this has the desired effect: In the smartmontools project, we use a Debian 12 based docker image for reproducible CI builds (https://builds.smartmontools.org/). After forcibly upgrading NSIS to 3.09 from Debian trixie, the problem disappeared. Here the related commit: https://github.com/smartmontools/docker-build/commit/9b231f0 Therefore I guess that #1050288 is also fixed in unstable. -- Regards, Christian
Bug#1050288: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)
On Sat, 26 Aug 2023 14:23, Thomas Gaugler wrote: Therefore I would appreciate if you create a "bookworm proposed updates request" by issuing the "reportbug release.debian.org" command on a Debian system. I did, but obviously it was incomplete. Unfortunately the immediate error report didn't reach my mailbox: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050588 Could you possibly complete this as I'm (obviously) unfamiliar with the Debian release process & policies. Thanks, Christian smartmontools.org
Bug#1041745: Device: /dev/nvme0, number of Error Log entries increased from … to …
This should no longer happen with smartd 7.4, see https://www.smartmontools.org/ticket/1222 Regards, Christian smartmontools.org
Bug#1050588: bookworm-pu: package nsis/nsis 3.08-3
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: n...@packages.debian.org, christian.fra...@t-online.de Control: affects -1 + src:nsis Please update nsis 3.08-3 to 3.09. [ Reason ] Generated installers contain invalid relocation information, see Bug#1050288. This is a regression introduced by a changed behavior of the MinGW-w64 toolchain. nsis 3.06.1-1 on bullseye is not affected because an older version of the toolchain is used. nsis-3.09-1 on trixie is not affected because NSIS upstream addressed this problem in release 3.09. This update also fixes security vulnerability CVE-2023-37378, see Bug#1040880. [ Impact ] Large installers may work on Windows, but small installers do not. Even if an installer works, warning messages from security scanners may be triggered because the file is considered corrupt. [ Tests ] Create a small installer with makensis. The problem is fixed if 'objdump -p' does no longer complain "BFD: error: FILE.exe(.reloc) is too large" and the size of the '.reloc' section is 0. See Bug#1050288 for details. [ Risks ] NSIS 3.09 is the official upstream release proven to work for some time now.
Bug#1050288: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)
A manual download of nsis{-common}-3.09-1 from debian testing and 'dpgk
--install --force-all' succeeded and makensis works then. With this
version, the problem does not occur.
A backport of this version to bookworm should fix the problem.
Bug#1050288: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)
Severity of this bug promoted to 'grave' because further tests show that generated installers may not work at all: Testcase: $ cat /etc/debian_version 12.1 $ makensis -VERSION v3.08-3 $ cat test.nsi RequestExecutionLevel user Section "Test" MessageBox MB_OK "Hello, World!" SectionEnd $ makensis test.nsi ... $ objdump -p test-debian.exe >/dev/null BFD: error: test-debian.exe(.reloc) is too large (0x8e4 bytes) If test.exe is started on a Windows machine, CreateProcess() fails with GetLastError()==193 (ERROR_BAD_EXE_FORMAT). The same installer built with upstream NSIS 3.09 on Windows is much smaller and works: -rwxr-xr-x 1 ... 94699 Aug 24 09:45 test.exe -rwxr-xr-x 1 ... 38886 Aug 24 09:43 test-built-on-windows.exe
Bug#1050288: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)
Control: severity -1 grave
Bug#1050288: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)
Package: nsis Version: 3.08-3 Severity: important makensis 3.08-3 on bookworm creates installers with a non-empty relocation section which contains garbage. The installers work, but trigger false positive warnings from security scanners, likely due to exe file corruption. Testcase: $ dpkg --list nsis nsis-common ... ii nsis 3.08-3 amd64 ... ii nsis-common 3.08-3 all ... $ cat test.nsi Section "Empty" SectionEnd $ makensis test.nsi ... $ objdump -p test.exe >/dev/null objdump: error: test.exe(.reloc) is too large (0x8e4 bytes) $ objdump -p test.exe 2>/dev/null ... Entry 5 00047000 08e4 Base Relocation Directory [.reloc] ... $ objdump -p /usr/share/nsis/Stubs/zlib-x86-unicode ... Entry 5 00047000 08e4 Base Relocation Directory [.reloc] ... PE File Base Relocations (interpreted .reloc section contents) Virtual Address: 1000 Chunk size 196 (0xc4) Number of fixups 94 reloc 0 offset 2b [102b] HIGHLOW reloc 1 offset 40 [1040] HIGHLOW ... Virtual Address: c000 Chunk size 216 (0xd8) Number of fixups 104 reloc 1 offset 8 [c008] HIGHLOW reloc 2 offset c [c00c] HIGHLOW ... reloc 102 offset 8f8 [c8f8] HIGHLOW reloc 103 offset 8fc [c8fc] HIGHLOW All the stubs apparently have a non-empty relocation section with garbage. This is not the case for the stubs from nsis-common-3.06.1-1 (bullseye) and nsis-common-3.09-1 (sid). This is also not the case with the upstream 3.08 and 3.09 builds for windows which are available at https://sourceforge.net/projects/nsis/files/NSIS%203/ Related: https://sourceforge.net/p/nsis/bugs/1299/ -- Regards Christian Franke smartmontools.org
Bug#1041295: smartd.conf.5: some remarks and editorial fixes for the manual
Hi Bjarni, this bug Split a punctuation from a single argument, if a two-font macro is meant 64:.B /etc/smartd.conf. and minor mandoc / groff warnings are now fixed upstream: https://www.smartmontools.org/changeset/5506 https://www.smartmontools.org/changeset/5520 The remaining suggestions will be addressed after smartmontools 7.4 release. Change '-' (\-) to '\(en' (en-dash) for a numeric range. BTW, tests with groff show that, unlike '\-', the '\(en' does not look "nice" for numerical ranges because it is vertically aligned for lowercase letters. This is the case with the default serif font T(imes) and also the with sans-serif font H(elvetica). ... smartd.conf.5:173:# Start short self\-tests daily between 1\-2, 2\-3, and smartd.conf.5:174:# 3\-4 am. ... Note that using '\(en' in the above text has no visible effect because this section is always rendered with monospaced (.ft CW) font. The amount of space between sentences in the output can then be controlled with the ".ss" request. Where should .ss be used? I didn't find any example in your patch on other man pages. -- Regards, Christian
Bug#1041295: [smartmontools-devel] Bug#1041295: smartd.conf.5: some remarks and editorial fixes for the manual
Thanks for the suggestions. Possibly too late for upcoming smartmontools 7.4, but will be addressed later. In general, non-trivial syntax changes require tests with several formatting tools including those used on Free/Net/OpenBSD. Changes shall also work with older tool versions still used by LTS distributions. Using \(en may make sense and is already used elsewhere in the man page source files. This is IMO a minor issue. The visible difference with "groff -man -Tpdf" is small. The \& are not needed because we always format these files manually and review plaintext and pdf formatted versions afterwards. Please note that the patch itself could not be used because it only fixes the generated Debian specific version of this page. This file hides the info specific to other platforms in comments. See the long MAN_FILTER macro in Makefile.am for the details. The patch only addresses a single file. Such general changes should be done for all four *.[58].in files from the sourcecode with a single commit. Regards, Christian
Bug#1029210: smartmontools.service fails since bookworm
Fixed upstream: https://www.smartmontools.org/changeset/5475
Bug#1029210: smartmontools.service fails since bookworm
Alban Browaeys wrote: Why is smartd of type notify? Does it send notification to systemd via sd_notify? Yes, otherwise this would not appear in systemctl status output: Status: "No devices to monitor" See 'man smartd' for details. Unfortunately it does not properly work in conjunction with '-q nodev0' because 'READY=1' is not notified before 'exit(0)' then. Systemd reports "failed (Result: protocol)" in this case. This will be fixed in the next release of smartmontools. Regards, Christian
Bug#1029210: smartmontools.service fails since bookworm
Possible fix for the package: Add '-q nodev0' or '-q never' to ExecStart in smartmontools.service. Workaround for users: Add one of these to smartd_opts in /etc/default/smartmontools. Option '-q nodev0' is available since smartmontools 7.3. Then smartd will exit with status 0 instead of 17 (default '-q nodev') if there are no devices to monitor. Systemd should no longer report this as a failed service. With '-q never', smartd will keep running and does nothing. This was the default for '-q' in some previous versions of (only!) the Debian package. This Debian-specific patch was reverted later, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006630 Regards, Christian smartmontools.org
Bug#1032469: smartmontools: startup takes too long for systemd
A note for upcoming smartmontools release 7.4: It NOTIFY_SOCKET is set in environment, smartd 7.4 will sd_notify "EXTEND_TIMEOUT_USEC=2000" for each disk during device registration and then for each disk during first device checks.No such calls will occur after "READY=1" has been notified. Regards, Christian smartmontools.org
Bug#1024237: drop meaningless EMails
What is the idea behind these emails? The drive reports bad sectors pending for reallocation (HDD) or retirement (SSD). What is the recommended way to turn them off? Run a long self-test (smartctl -t long ...). Also check Device Statistics and Pending Defects log (smartctl -l devstat -l pending ...). If no bad LBA is reported, disable the emails by '-C 197+ -U 198+' in smartd.conf. See "man smartd.conf" for details. Otherwise fix the bad sectors by overwriting. -- Regards, Christian smartmontools.org
Bug#1006630: smartmontools: Please do not change the upstream default of the 'smartd -q' option
Package: smartmontools Version: 7.2-1 The "default_never-quit.patch" changes the default of the 'smartd -q' option from '-q nodev' to '-q never'. It should be at least mentioned on the man page that this change is Debian (and possibly Ubuntu) specific. The change of the default is not required as the following setting in the service file has the same effect: ExecStart=/usr/sbin/smartd -n -q never $smartd_opts The '-q' option could then still be overridden via $smartd_opts. Note that the new 7.3 version of smartmontools adds `-q *nodev0*` option variants which change the 'no devices' exit code from 17 to 0. The service should be no longer reported as failed then. "No devices to monitor" is reported via sd_notify() if configured. Regards, Christian Franke smartmontools.org
Bug#997840: mailutils: [security] mail(1) processes command escapes also if used non-interactively
Package: mailutils Version: 1:3.10-3 Steps to reproduce: $ printf 'test:\n~! echo ALERT\nbye!\n' | mail TO_SOME_ADDRESS Observed: "ALERT" is printed to standard output. Expected: String "~! echo ALERT" shall be send as second line of the mail. Command escapes should only be processed if used interactively. Related security issues: https://security-tracker.debian.org/tracker/CVE-2021-32749 https://www.smartmontools.org/ticket/1535 Fixed in mailutils 3.13, see https://savannah.gnu.org/bugs/?60937 If possible, please backport the fix to (old)stable. Regards, Christian Franke smartmontools.org
Bug#947803: smartmontools: smartctl -l error causes Micron 2200S NVME to fail
Please test recent build from https://builds.smartmontools.org/
Bug#947803: smartmontools: smartctl -l error causes Micron 2200S NVME to fail
Possibly related report for Micron_2200_MTFDHBA1T0TCK with firmware P1MU003: https://www.smartmontools.org/ticket/1404
Bug#974755: smartd: Problematic memory activity (triggers oom-killer)
smartd.conf file ? If DEVICESCAN is used: How many devices are detected ? Triggering self-tests should not require any additional memory as the actual tests are handled by drive firmware. Regards, Christian smartmontools.org
Bug#969048: smartmontools: Update systemd unit file (StandardOutput=syslog)
Fixed upstream in r5077: https://www.smartmontools.org/changeset/5077 BTW: https://www.smartmontools.org/changeset/5078
Bug#964032: smartmontools: Samsung S1 Mini 200GB: Unknown USB bridge [0x04e8:0x2f06 (0x000)]
Added upstream in r5084, r5087: https://www.smartmontools.org/changeset/5084 https://www.smartmontools.org/changeset/5087 Please update the drive database.
Bug#918535: smartmontools: New upstream release (7.0)
Dear Maintainer (or NMUploader),
if possible, please also include the attached patch to a
smartmontools-7.0 package.
Details: https://www.smartmontools.org/ticket/1154
Thanks,
Christian
smartmontools.org
Index: ataprint.cpp
===
--- ataprint.cpp(revision 4883)
+++ ataprint.cpp(revision 4889)
@@ -704,7 +704,8 @@
else
jout("Form Factor: Unknown (0x%04x)\n", word168);
jglb["form_factor"]["ata_value"] = word168;
-jglb["form_factor"]["name"] = form_factor;
+if (form_factor)
+ jglb["form_factor"]["name"] = form_factor;
}
// See if drive is recognized
Bug#924892: smartmontools: fails on nvme/Optane: NVMe Status 0x4002
> Read NVMe SMART/Health Information failed: NVMe Status 0x4002 Which device name did you use for smartctl 6.6 ? If it was '/dev/nvme0n1', please retry with '/dev/nvme0' or '/dev/nvme0n1,0x'. Smartctl 6.6 uses selected namespace to read SMART/Health and Error logs. Smartctl 7.0 always uses broadcast namespace. Christian smartmontools.org
Bug#804299: smartmontools: update-smart-drivedb currently risky
Marc Haber wrote: On Thu, Jan 10, 2019 at 03:47:24PM +0100, Christoph Anton Mitterer wrote: ... Plus it automatically imports the shipped public key into the keyring of the executing user… which is IMO also unacceptable. Agreed, the script should use its own keyring. The script creates a temporary gpg homedir, imports the key, verifies the file and then removes the gpg homedir. See function gpg_verify(). So it actually uses its own keyring and does not touch user's ~/.gnupg :-) Cheers, Christian
Bug#804299: smartmontools: update-smart-drivedb currently risky
Christoph Anton Mitterer wrote: ... I've just hat a quick glance at current upstream: https://svn.code.sf.net/p/smartmontools/code/trunk/smartmontools/update-smart-drivedb.in Comments are welcome. It seems it now contains some code verification, both X.509 CA based and/or OpenPGP based. I think the X.509 CA / TLS based one can be just tossed (because X.509 PKI is inherently flawed and insecure - just take the ~150 CAs Mozilla ships, many of them already completely untrustworthy, with even more sub-CAs (that are even more untrustworthy). Agree. OpenPGP would be in principle ok. However, I haven't really checked the implementation of it (i.e. how the code downloading, verification is done... on a first glance, I'd say it allows at least for replay attacks. Could you possibly describe an attack scenario? Plus it automatically imports the shipped public key into the keyring of the executing user… which is IMO also unacceptable. Of course this would be unacceptable. I'm at least somewhat sure that I didn't implement it that way :-) Cheers, Christian smartmontools.org
Bug#865912: smartd: please start with Type=forking to wait for successful initialisation
BTW: smartmontools 7.0 supports Type=notify. https://www.smartmontools.org/browser/tags/RELEASE_7_0/smartmontools/NEWS
Bug#911280: smartmontools: DEVICESCAN pattern doesn't match /dev/nvme*
smartmontools 7.0 enables '-with-nvme-devicescan' by default on Linux. https://www.smartmontools.org/browser/tags/RELEASE_7_0/smartmontools/NEWS
Bug#900244: smartmontools: NVM error information log entry count increase not an error
Please provide two differing "smartctl -i -l error /dev/nvmeX" outputs of an affected device. The error log may be filled with "Invalid Field in Command" or a similar "Generic Command" (0x0) errors. Smartd should possibly limit the error count to entries with Status Code Type "Media and Data Integrity Errors" (0x2).
Bug#911280: smartmontools: DEVICESCAN pattern doesn't match /dev/nvme*
This means that the package maintainer did not override the upstream decision to exclude NVMe devices from default DEVICESCAN. Here the related message printed by ./configure if no '--with*-nvme-devicescan' option is specified: " configure: WARNING: This version of smartmontools provides NVMe support which is still EXPERIMENTAL. NVMe devices are not yet included in smartd.conf 'DEVICESCAN' and 'smartctl --scan' unless '-d nvme' is specified. Use option '--with-nvme-devicescan' to include NVMe devices. Use option '--without-nvme-devicescan' to suppress this warning. " Workaround: DEVICESCAN -d sat -d nvme ... Test with: smartctl --scan -d sat -d nvme
Bug#907736: smartmontools: smartd starts on every boot, ignoring /etc/default/smartmontools
The file /etc/default/smartmontools has no effect if systemd is used. Simply disable the service with: # systemctl disable smartd
Bug#865912: smartd: please start with Type=forking to wait for successful initialisation
See also upstream tickets: https://www.smartmontools.org/ticket/1080 https://www.smartmontools.org/ticket/1081
Bug#874085: smartmontools: [smartd.conf] UNRECOGNIZED OPTION: U
There is no smartd command line option -U (see 'smartd -h' or 'man smartd') but a smartd.conf directive -U (see 'smartd -D' or 'man smartd.conf'). Conclusion: Place '-U 198+' in the file /etc/smartd.conf instead.
Bug#679035: Useless warning about disconnected USB device: Device: /dev/sdb [SAT], unable to open device
Please upgrade to smartmontools-6.6 and add '-d removable' to smartd.conf (see Bug#770872).
Bug#889033: smartmontools: New version (6.6) is available
For a smartmontools-6.6+ package, please reconsider the decision to remove the update-smart-drivedb script (Bug#804299) as it now validates the downloaded file. See https://www.smartmontools.org/ticket/751 for details. Related: Bug#824795
Bug#770872: smartmontools: smartd sends FailedOpenDevice warnings even for devices marked as removable
Fixed upstream since r4399. https://www.smartmontools.org/changeset/4399 Fix is included in new smartmontools-6.6 release.
Bug#824795: smartmontools: remove obsolete /usr/share/man/man8/update-smart-drivedb.8.gz man page
The update-smart-drivedb script now validates the downloaded file with GnuPG. The assumptions which resulted in the removal of the update script (Bug#804299) are possibly no longer true. See https://www.smartmontools.org/ticket/751 for details.
Bug#824795: smartmontools: remove obsolete /usr/share/man/man8/update-smart-drivedb.8.gz man page
Smartmontools 6.5 provides a new ./configure option '--without-update-smart-drivedb'. It removes the update script, its man page and all references from the other man pages. See: https://www.smartmontools.org/changeset/4299 Please consider to provide drivedb.h updates as a separate package which is updated more frequently. Christian smartmontools.org
Bug#804299: smartmontools: update-smart-drivedb currently risky
Christoph Anton Mitterer wrote: - Removing "-F nologdir" option from Intel 320/710 SSD entries may result in drive a firmware crash if Log Directory is read. - Setting a bogus USB "-d TYPE" option may result in disconnected USB devices or more serious problems. I think in the past there were several reports of hardware including disks, that, when you queried something wrong, may have ended up severely damaged. Most of these problems were unrelated to any influence the drive database file has on smartmontools operation. For example: Buggy RAID controller firmware doing interesting things if specific (SAT) pass-through commands are issued. Or my favorite: Samsung F4 disks discarding write cache if ATA IDENTIFY is issued. Cheers, Christian
Bug#804299: smartmontools: update-smart-drivedb currently risky
Christoph Anton Mitterer wrote: Even if it would be properly secured with some key that upstream has, it would allow them to selectively inject code into Debian systems. Then anything we could do upstream (e.g. provide a drivedb.h.asc file, check it in update-smart-drivedb) won't help. Some volunteer maintainer might provide drivedb.h (below /usr, not /var) as a separate arch independent package and update it more frequently than smartmontools. Such a package only needs a "suggests" dependency because the built-in database is used if the external file is missing. In the short term it should probably be disabled or at least prompt the user to manually verify a checksum or something. ./configure --without-drivedbdir This keeps the built-in database and optional /etc/smartd_drivedb.h intact. If done, please add a dummy update-smart-drivedb script which explains why this functionality was removed. Possible risks from a bogus drivedb.h: - The typical worst case: A hidden bug in the parser allows to run arbitrary code as root. (BTW: Thanks for any review of the parser in knowndrives.cpp) - Removing "-F nologdir" option from Intel 320/710 SSD entries may result in drive a firmware crash if Log Directory is read. - Setting a bogus USB "-d TYPE" option may result in disconnected USB devices or more serious problems. - More ? (IMO no). Thanks, Christian smartmontools.org
Bug#804168: The temperature values in the systemlog not Celcuis but Fahrenheit
Please provide info about affected drive models and sample temperature outputs from smartd and smartctl. Note that a ATA/SATA devices may have various sources for current temperature: SMART Attributes (190, 194, ...), SCT Status and Device Statistics. Smartctl could read all, but smartd only checks the attributes.
Bug#293060: Bug#598537: UUID is not enough. Gather all the information possible.
Jon Bendtsen wrote: UUID is not enough. I would rather that the emails like the one quoted below would include as much information as possible or maybe configureable. smartctl -i /dev/sds fdisk -l /dev/sds ... sg_inq /dev/sds This could be done by a custom script run via '-M exec' directive. ... The following warning/error was logged by the smartd daemon: Device: /dev/sds [SAT], Self-Test Log error count increased from 2 to 3 For details see host's SYSLOG. This sample output is outdated. Starting with smartmontools 6.0 (October 2012), the warning mails include device identify info (Model, S/N, WWN, FW, Size).
Bug#788243: quagga: suboptimal default pager settings for vtysh
Package: quagga Version: 0.99.23.1-1 Severity: minor Hello Chris, doing a standard Debian installation and then installing Quagga, it will use less as a pager for vtysh. While less might be a neat pager for vtysh with more configuration, the less with default configuration is a usability hurdle. On my installation, I observe the following two inconvenient behaviours: - less prompts the user to explicitly close it, after each command - the output from less will be cleared after less is closed, inhibiting the option to use output from show ... commands for configuration commands While I understand the intention to make vtysh match up with Debians global pager settings, would it maybe be possible and sensible to implement a more usable default? -Christian -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages quagga depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii iproute2 3.16.0-2 ii libc6 2.19-18 ii libcap21:2.24-8 ii libpam0g 1.1.8-3.1 ii libreadline6 6.3-8+b3 ii libtinfo5 5.9+20140913-1+b1 ii logrotate 3.8.7-1+b1 quagga recommends no packages. Versions of packages quagga suggests: pn snmpd none -- Configuration Files: /etc/quagga/daemons changed [not included] /etc/quagga/debian.conf changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782568: smartmontools: Default MTA 'mail' not available in any Debian packages
For that the package recommends two MTAs: 'mailx' or 'mailutils'. Both of these packages do not provide a 'mail' binary or script nor neither does any other standard Debian package (e.g. do 'apt-file search bin/mail') This test is not valid to check for missing commands. The /usr/bin/mail command will NEVER appear as an actual file in any package. If the path exists, it is a symlink finally leading to some executable compatible with traditional 'mail'. Such symlinks are created by update-alternatives(8) which is typically run by the 'postinst' script of the selected mailer alternative. For example, if 'mailutils' package is the only installed alternative, the created symlinks are: /usr/bin/mail - /etc/alternatives/mail - /usr/bin/mail.mailutils Try 'update-alternatives --display mailx' for current selection. If none, (re)install or reconfigure the mailer package of choice. Further it is not possible do simply specify another MTA like '-M exec sendmail' Using the 'mail' interface instead of 'sendmail' for smartd emails is a very old upstream design decision. There are no plans to change this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783317: Missing upstream version of update-smart-drivedb man page
Package: smartmontools Version: 6.3+svn4002-2 Severity: minor The original update-smart-drivedb man page was provided for the Debian package (Bug #708433) . This man page was added 2014-06-26 to upstream smartmontools (r3929). An slightly updated version was included in smartmontools upstream release 6.3 (r3976). The Debian package build from smartmontools r4002 still provides the original version. No problem for this package, but future versions of the upstream man page might contain significant changes. Thanks, Christian Franke smartmontools.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777710: smartmontools: strange LBA numbers in reports
There is random garbage in the upper bytes of the 48-bit LBA field: 00312581807 = 0x12A19EAF (Max possible LBA) 00020399756 = 0x0137468C (Self-test Log #10/#11) 138688809354892 = 0x7E230137468C (Extended Self-test Log #10) 244890465683084 = 0xDEBA0137468C (Extended Self-test Log #11) Possibly a drive firmware issue: 4 byte LBA value from old self-test log copied to 6 byte field of extended self-test log entry without zeroing the upper bytes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781112: grub-common: grub-probe fails with 'Unknown filesystem' for JFS2
Package: grub-common
Version: 2.02~beta2-21
Severity: important
Dear Maintainer,
I just tried to install Debian Jessie using the current debian-installer for
Jessie.
I went through the installation and created a partition layout like this:
/dev/vda1 2GiB Swap
/dev/vda2 40GiB JFS2
I have other installations with Debian Wheezy that work fine with this and
installation
progressed normally. However, finishing up the installation and trying to
install grub
to /dev/vda, I got a fatal error unknown filesystem.
Entering the newly installed system from the chroot, the issue seems to be that
update-grub
fails because the call 'grub-probe --target=fs -d /dev/vda2' fails with
'Unknown filesystem'
instead of returning the correct value.
# file -Ls /dev/vda2
/dev/vda2: JFS2 filesystem image, 79713504 blocks, blocksize 4096
# grub-probe --target=fs -d /dev/vda2
grub-probe: error: unknown filesystem.
I would have expected to be able to just install grub with the JFS as root
device, as it did
quite a few times before.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/vda2 / jfs rw,noatime 0 0
/dev/vda2 /dev/.static/dev jfs rw,noatime 0 0
/dev/sr0 /cdrom iso9660 ro,relatime 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ ${next_entry} ] ; then
set default=${next_entry}
set next_entry=
save_env next_entry
set boot_once=true
else
set default=0
fi
if [ x${feature_menuentry_id} = xy ]; then
menuentry_id_option=--id
else
menuentry_id_option=
fi
export menuentry_id_option
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if loadfont unicode ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
if [ ${recordfail} = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload=${1}
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option 'gnulinux-simple-/dev/vda2' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
echo'Loading Linux 3.16.0-4-amd64 ...'
linux /boot/vmlinuz-3.16.0-4-amd64 root=/dev/vda2 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option
'gnulinux-advanced-/dev/vda2' {
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64' --class debian
--class gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-3.16.0-4-amd64-advanced-/dev/vda2' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio;
fi
insmod part_msdos
echo'Loading Linux 3.16.0-4-amd64 ...'
linux /boot/vmlinuz-3.16.0-4-amd64 root=/dev/vda2 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode)'
--class debian --class gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-3.16.0-4-amd64-recovery-/dev/vda2' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio;
fi
insmod part_msdos
echo'Loading Linux 3.16.0-4-amd64 ...'
linux /boot/vmlinuz-3.16.0-4-amd64 root=/dev/vda2 ro single
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.16.0-4-amd64
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END
Bug#636601: [Patch] posh does not glob words partially quoted
Found the same issue during testing of the autoconf script from
smartmontools with various shells. With posh, the script returned a few
bogus results.
The problem occurs when a quote string precedes the wildcard. The
wildcard is also interpreted as quoted then:
$ posh -c 'case foo in fo*) echo OK;; *) echo FAIL; esac'
FAIL
$ posh -c 'case fo* in fo*) echo OK;; *) echo FAIL; esac'
OK
$ posh -c 'case foo in *oo) echo OK;; *) echo FAIL; esac'
OK
$ posh -c 'case foo in fo*) echo OK;; *) echo FAIL; esac'
OK
Examining the source, I found
case CQUOTE:
quote = st-quote;/* XXX correct? */
continue;
Actually this isn't correct, because st-quote may refer to
st_head.quote which is not initialized. The attached patch fixes the
issue for the above cases. It may be necessary to also init other fields
of std_head. There may also be a nesting problem with the 'st' chain.
Regards,
Christian
2014-07-07 Christian Franke fra...@computer.org
* eval.c (expand): Fix missing initialization of st_head.quote.
(Closes #636601 ?)
diff -rup posh-0.12.3.orig/eval.c posh-0.12.3/eval.c
--- posh-0.12.3.orig/eval.c 2012-11-01 15:33:25.0 +0100
+++ posh-0.12.3/eval.c 2014-07-07 21:16:41.012243600 +0200
@@ -201,6 +201,7 @@ expand(const char *cp, /* input word */
make_magic = 0;
word = (fDOBLANK) ? IFS_WS : IFS_WORD;
st_head.next = NULL;
+ st_head.quote = 0;
st = st_head;
while (1) {
Bug#710815: Please move smartd_warning.sh out of /etc
I added ./configure options --with-smartdscriptdir and
--with-smartdplugindir to upstream smartmontools.
Defaults are unchanged:
--with-smartdscriptdir=${sysconfdir}
--with-smartdplugindir=${smartdscriptdir}/smartd_warning.d
Thanks,
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734395: smartmontools: [drivedb] Support for TOSHIBA STOR.E Plus 2 TB (0x0480:0xa00a)
Added to upstream drivedb.h r3908. Please run /usr/sbin/update-smart-drivedb to test. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717567: smartmontools: FTBFS[kfreebsd]: error: 'ARCMSR_IOCTL_READ_RQBUFFER' was not declared in this scope
Fixed upstream in r3854. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705404: ikiwiki: broken relative links from CGI pages
Package: ikiwiki Version: 3.20130212 Severity: important The following bug has been observed with testing, an upgrade to unstable did not bring an improvement. Setup: I have an ikiwiki at https://sublab.org/wiki/ which supports editing via CGI. It is served by an Apache which has Alias /wiki/ /the/wiki/dir configured. It has the ikiwiki.cgi accessible at .../wiki/ikiwiki.cgi and .../wiki/auth/ikiwiki.cgi, the latter using Apaches' HTTP authentication features as described in Ikiwiki's documentation. The setup file is available at https://git.sublab.org/ikiwiki/tree/wiki.setup?id=a52915d Problem: On pages generated by the CGI, most URLs generated by ikiwiki are off and trigger 404. While debugging the issue I found that this seems to happen for relative urls only. The issue seems to be that ikiwiki assumes the wrong base for the links. E.g. when you are at .../wiki/ikiwiki/formatting and edit the page, you will get to to .../wiki/ikiwiki.cgi?do=edit but all links on that site will be generated relative to .../wiki/ikiwiki/formatting. This concerns e.g. the links to the formatting help and the breadcrumbs navigation built by parentlinks. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (600, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages ikiwiki depends on: ii libhtml-parser-perl 3.69-2 ii libhtml-scrubber-perl 0.09-1 ii libhtml-template-perl 2.91-1 ii libjson-perl2.53-1 ii libtext-markdown-discount-perl 0.02-1 ii liburi-perl 1.60-1 ii libyaml-libyaml-perl0.38-3 ii perl5.14.2-20 Versions of packages ikiwiki recommends: ii gcc [c-compiler] 4:4.7.2-1 ii gcc-4.4 [c-compiler] 4.4.7-2 ii gcc-4.5 [c-compiler] 4.5.3-12 ii gcc-4.6 [c-compiler] 4.6.3-14 ii gcc-4.7 [c-compiler] 4.7.2-5 ii git [git-core] 1:1.7.10.4-1+wheezy1 ii libauthen-passphrase-perl0.008-1 ii libc6-dev [libc-dev] 2.13-38 ii libcgi-formbuilder-perl 3.08-1 ii libcgi-session-perl 4.46-1 ii libcrypt-ssleay-perl 0.58-1 ii libgravatar-url-perl 1.06-1 ii liblwpx-paranoidagent-perl 1.07-1 ii libmail-sendmail-perl0.79.16-1 ii libnet-openid-consumer-perl 1.13-1 ii librpc-xml-perl 0.76-3 ii libterm-readline-gnu-perl1.20-2+b1 ii libtimedate-perl 1.2000-1 ii libxml-simple-perl 2.20-1 Versions of packages ikiwiki suggests: pn dvipng none ii file5.11-2 ii gettext 0.18.1.1-9 pn graphviznone ii libfile-mimeinfo-perl 0.16-1 pn libhighlight-perl none ii libhtml-tree-perl 5.02-1 ii liblocale-gettext-perl 1.05-7+b1 ii libmailtools-perl 2.09-1 pn libnet-amazon-s3-perl none pn libnet-inet6glue-perl none pn libsearch-xapian-perl none pn libsort-naturally-perl none pn libsparkline-phpnone pn libtext-csv-perlnone pn libtext-multimarkdown-perl none pn libtext-textile-perlnone pn libtext-typography-perl none pn libtext-wikicreole-perl none pn libtext-wikiformat-perl none pn libxml-feed-perlnone pn libxml-writer-perl none ii perlmagick 8:6.7.7.10-5 pn po4anone pn polygen none ii python 2.7.3-4 pn python-docutils none ii texlive 2012.20120611-5 pn tidynone pn viewvc | gitweb | viewcvs none pn xapian-omeganone -- 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#705404: Acknowledgement (ikiwiki: broken relative links from CGI pages)
Just to avoid confusion: At the given URL, I hot-wired the parentlinks plugin so that it will not generate relative links, so the described behaviour is not observable there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690108: INVALID ARGUMENT TO -t: select,cont+35651584
Fix is included in upstream smartmontools-6.1.tar.gz. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694315: smartmontools: Short-self test sometimes never ends (6+ hours) on high IO
Such a long test duration is actually uncommon for the short SMART self-test. This is a drive firmware bug which cannot be fixed by smartmontools. All SMART self-tests are controlled by drive firmware. Smartctl and smartd only issue the ATA command to start the test. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636078: smartmontools: offline data collection was aborted by an interrupting command from host
Bob Proulx wrote: Christian Franke wrote: This is logged as LOG_INFO and no sign of trouble. Tracking of self-test and offline data collection status was added in 5.40 and 5.41 and is enabled by default (-l selftest, -a). I don't understand. The log message says that the action was suspended and aborted by an interrupting command. The report in such a way certainly makes it appear as if an error is occurring. The message texts are aligned with ATA standards, see T13 documents. I think you are saying that this has always been happening but is simply being reported in this version when it wasn't being reported before. Is that right? Yes. But it still seems like an error, right? No. This message is logged as LOG_INFO. Please note that smartd uses LOG_CRIT level to indicate possible disk problems. This would only be the case for the offline data collection was aborted by the device with a fatal error state. Smartmontools 5.42 adds new directives -l selfteststs (included in -a) and -l offlinests (not included in -a) to control this separately. Sorry but I don't understand what you are trying to tell me about using those options. I think you are suggesting that I should add one of those options to avoid the default of '-l selftest -a'. Is that right? Old (5.41) behavior: '-l selftest' also reports changes of self-test and offline data collection status. '-a' includes '-l selftest'. New (5.42) behavior: '-l selfteststs' reports changes of self-test execution status. '-l offlinests' reports changes of offline data collection status. '-l selftest' does no include the above. '-a' includes '-l selftest -l selfteststs' but not '-l offlinests'. See smartd.conf man page. Conclusion: This bug could be set to fixed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690108: INVALID ARGUMENT TO -t: select,cont+35651584
Could not reproduce this with the same package. But there is actually a very old bug in the option parser: errno is not cleared before strtoull(). Now fixed upstream in r3661. Possible workarounds for this package: - Enabling debug messages first with -r ioctl,1 clears errno, -t select,cont+SIZE should work then. - Don't use +SIZE, rely on size of last span tested. Thanks, Christian smartmontools-support at lists.sourceforge.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683051: smartmontools: Release 5.43 finally supports areca 1680
The Areca SAS patch adds the Enclosure Parameter to '-d areca' option. This was added upstream in r3540 and therefore should be already included in Debian package 5.42+svn3561-X. Please note that this requires upcoming 1.51 Areca firmware or a recent beta version. Firmware versions = 1.50 do not support ATA pass-through on SAS controllers. Thanks, Christian smartmontools-support at lists.sourceforge.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636078: smartmontools: offline data collection was aborted by an interrupting command from host
This should be fixed in Debian package 5.42+svn3539-1. Offline data collection status is no longer tracked unless '-l offlinests' is specified. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661801: smartmontools: typo in man page: QUIT instead of INT in the description of
Fixed upstream in r3529. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598537: smartmontools: Use UUID instead /dev/sdX
Using /dev/disk/by-id/... as a device name should work for non-RAID volumes since 5.41 r3269. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563256: smartmontools: SMART errors upon resuming from suspend
Some pass-through I/O-controls may fail if called immediately after resume from suspend. There is a fix in upstream smartd r3424 (included in 5.42). Some extra sleep() time is added if resume from suspend is detected. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643928: Add USB bridge to known IDs
Added to upstream drivedb.h r3471. Please run /usr/sbin/update-smart-drivedb to test. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636078: smartmontools: offline data collection was aborted by an interrupting command from host
This is logged as LOG_INFO and no sign of trouble. Tracking of self-test and offline data collection status was added in 5.40 and 5.41 and is enabled by default (-l selftest, -a). Smartmontools 5.42 adds new directives -l selfteststs (included in -a) and -l offlinests (not included in -a) to control this separately. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632758: (False?) warning about problematic Seagate drives
I changed the warning message accordingly (drivedb.h r3456). Run /usr/sbin/update-smart-drivedb to test. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634181: linux-image-2.6.39-2-amd64: br_netfilter nat pagefault
On Sun, 17 Jul 2011 17:51:14 +0200, Christian Franke wrote: This fault now also occured with version 2.6.39-3 of the linux-image-2.6.39-2-amd64 package. On Fri, 22 Jul 2011 01:19:33 +0200, Ben Hutchings wrote: I think this bug was fixed in 2.6.39-3 along with bug #629932. Let us know if it occurs again. As I see it (upper quote), this bug also occurs in the 2.6.39-3 version. It do however lack understanding of the package naming and versioning here - the package has the name linux-image-2.6.39-2-amd64, however its version is 2.6.39-3, an aptitude update search also does not show a package with name 2.6.39-3 here. Attached, there is a dump of the complete kernel log on 2.6.39-3, I hope this makes it into the bugtracker. :/ Best Regards, Christian Franke [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.39-2-amd64 (Debian 2.6.39-3) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-6) ) #1 SMP Tue Jul 5 02:51:22 UTC 2011 [0.00] Command line: root=/dev/mapper/storage-root ro intel_iommu=on console=ttyS0,115200 console=tty0 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: 0100 - 0009e800 (usable) [0.00] BIOS-e820: 0009e800 - 000a (reserved) [0.00] BIOS-e820: 000e4000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - bf77 (usable) [0.00] BIOS-e820: bf77e000 - bf78 (reserved) [0.00] BIOS-e820: bf78 - bf78e000 (ACPI data) [0.00] BIOS-e820: bf78e000 - bf7dc000 (ACPI NVS) [0.00] BIOS-e820: bf7dc000 - c000 (reserved) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ffe0 - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00034000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI 2.6 present. [0.00] No AGP bridge found [0.00] last_pfn = 0x34 max_arch_pfn = 0x4 [0.00] x86 PAT enabled: cpu 0, old 0x7010600070106, new 0x7010600070106 [0.00] last_pfn = 0xbf770 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [880ff780] ff780 [0.00] init_memory_mapping: -bf77 [0.00] init_memory_mapping: 0001-00034000 [0.00] RAMDISK: 7f492000 - 7fff4000 [0.00] ACPI: RSDP 000fb6a0 00024 (v02 ACPIAM) [0.00] ACPI: XSDT bf780100 0007C (v01 092410 XSDT1014 20100924 MSFT 0097) [0.00] ACPI: FACP bf780290 000F4 (v03 092410 FACP1014 20100924 MSFT 0097) [0.00] ACPI: DSDT bf7804b0 05814 (v01 S0093 S0093501 0501 INTL 20060113) [0.00] ACPI: FACS bf78e000 00040 [0.00] ACPI: APIC bf780390 000D2 (v01 092410 APIC1014 20100924 MSFT 0097) [0.00] ACPI: MCFG bf780470 0003C (v01 092410 OEMMCFG 20100924 MSFT 0097) [0.00] ACPI: OEMB bf78e040 00072 (v01 092410 OEMB1014 20100924 MSFT 0097) [0.00] ACPI: HPET bf78a4b0 00038 (v01 092410 OEMHPET 20100924 MSFT 0097) [0.00] ACPI: DMAR bf78e0c0 00090 (v01AMI OEMDMAR 0001 MSFT 0097) [0.00] ACPI: SSDT bf78fba0 00363 (v01 DpgPmmCpuPm 0012 INTL 20060113) [0.00] ACPI: EINJ bf78a4f0 00130 (v01 AMIER AMI_EINJ 20100924 MSFT 0097) [0.00] ACPI: BERT bf78a680 00030 (v01 AMIER AMI_BERT 20100924 MSFT 0097) [0.00] ACPI: ERST bf78a6b0 001B0 (v01 AMIER AMI_ERST 20100924 MSFT 0097) [0.00] ACPI: HEST bf78a860 000A8 (v01 AMIER ABC_HEST 20100924 MSFT 0097) [0.00] No NUMA configuration found [0.00] Faking a node at -00034000 [0.00] Initmem setup node 0 -00034000 [0.00] NODE_DATA [00033fffb000 - 00033fff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 - 0x1000 [0.00] DMA320x1000 - 0x0010 [0.00] Normal 0x0010 - 0x0034 [0.00] Movable zone start PFN for each node [0.00] early_node_map[3] active PFN ranges [0.00] 0: 0x0010 - 0x009e [0.00] 0: 0x0100 - 0x000bf770 [0.00] 0: 0x0010 - 0x0034 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x05] enabled) [0.00] ACPI: LAPIC (acpi_id
Bug#634181: linux-image-2.6.39-2-amd64: br_netfilter nat pagefault
Package: linux-2.6 Version: 2.6.39-3 Severity: normal Tags: wheezy Unfortunately I have not found a way to reproduce this problem yet. So the only thing I can give is a describtion what I did. The box has some ethernet interfaces, among them eth0 and eth1. eth0 is part of a bridge, which is created by /etc/network/interfaces. ---/etc/network/interfaces cutout--- auto eth0 iface eth0 inet manual auto br0 iface br0 inet dhcp bridge_ports eth0 ---eof--- The box obtains 172.22.92.28/27 as IP on that bridge via DHCP and gets a default route via 172.22.92.1 via that bridge. On that bridge there are also various tap devices in use by VMs. After bootup, there are no iptables or ebtables rules, and eth1 is down. I use eth1 as something like a test-interface, so I usually configure it manually to fit my needs. What I did before the crash was: # ip link set eth1 up # ip addr add 192.168.1.5/24 dev eth1 # iptables -t nat -I POSTROUTING -o br0 -j MASQUERADE # echo 1 /proc/sys/net/ipv4/ip_forward This did not immediately cause the crash, judging from the backtrace, the crash is later caused by some network traffic, however as I read the backtrace, the crash could not have happened without the nat stuff being loaded. Unfortunately, I do not have a dump of network traffic at that time, on top of that I am not even sure on the path of the traffic which caused the crash in the first place. (routed from eth1 to br0? Originating on that host with default via br0?) To avoid any mixups, it should also be noted that at the time of running reportbug, linux-image-2.6.39-2-amd64 version 2.6.39-3 was running, while the crash occured on linux-image-2.6.39-2-amd64 version 2.6.39-2. -- Package-specific info: ** Version: Linux version 2.6.39-2-amd64 (Debian 2.6.39-2) ** Command line: root=/dev/mapper/storage-root ro intel_iommu=on console=ttyS0,115200 console=tty0 ** Not tainted ** Kernel log: [291476.322390] e1000e: eth1 NIC Link is Up 10 Mbps Half Duplex, Flow Control: None [291476.329865] e1000e :05:00.0: eth1: Autonegotiated half duplex but link partner cannot autoneg. Try forcing full duplex if link gets many collisions. [291476.343738] e1000e :05:00.0: eth1: 10/100 speed: disabling TSO [292453.071471] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [292708.909247] BUG: unable to handle kernel paging request at 88032ef51ffe [292708.916328] IP: [a03626ff] br_nf_pre_routing_finish_bridge+0x66/0xb5 [bridge] [292708.924450] PGD 1604063 PUD 33fffa067 PMD 32ef66063 PTE 80032ef51161 [292708.931305] Oops: 0003 [#1] SMP [292708.934659] last sysfs file: /sys/devices/system/cpu/cpu3/topology/thread_siblings [292708.942316] CPU 0 [292708.944246] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 tun ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables acpi_cpufreq mperf cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave parport_pc ppdev lp parport rfcomm bnep bluetooth rfkill binfmt_misc fuse nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc bridge stp jfs kvm_intel w83627ehf hwmon_vid kvm loop ftdi_sio cdc_ether usbnet usbserial mii i2c_i801 processor thermal_sys i2c_core ghes button pcspkr evdev hed ext4 mbcache jbd2 crc16 dm_snapshot sha256_generic aesni_intel cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod raid456 md_mod async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx sd_mod usb_storage usbhid crc_t10dif hid uas ahci libahci libata ehci_hcd scsi_mod acenic usbcore e1000e [last unloaded: scsi_wait_scan] [292709.025588] [292709.027176] Pid: 2919, comm: kvm Not tainted 2.6.39-2-amd64 #1 System manufacturer System Product Name/P7F-M [292709.037143] RIP: 0010:[a03626ff] [a03626ff] br_nf_pre_routing_finish_bridge+0x66/0xb5 [bridge] [292709.047689] RSP: 0018:88033fc03c68 EFLAGS: 00010246 [292709.053091] RAX: RBX: 8801cbd8d180 RCX: 8801fbbe3700 [292709.060311] RDX: 88032d506c80 RSI: 88032d506cd8 RDI: 8801cbd8d180 [292709.067530] RBP: 8801fbbe3700 R08: 88032d506cd0 R09: 88032ef5200e [292709.074749] R10: 2a9c07540800 R11: R12: 88032ef5200e [292709.081969] R13: 880321d22000 R14: 8803205b5000 R15: [292709.089189] FS: 7ff7b5ff8760() GS:88033fc0() knlGS: [292709.097364] CS: 0010 DS: ES: CR0: 8005003b [292709.103197] CR2: 88032ef51ffe CR3: 000327449000 CR4: 26e0 [292709.110415] DR0: DR1: DR2: [292709.117637] DR3: DR6: 0ff0 DR7: 0400 [292709.124857] Process kvm (pid: 2919, threadinfo 88032745a000, task 880328c2d7e0) [292709.132941] Stack: [292709.135045] 8801fbbe3700 a0362e87 88010001 81686a20 [292709.142587]
Bug#634181: also happens with linux-image-2.6.39-2-amd64 (2.6.39-3)
This fault now also occured with version 2.6.39-3 of the linux-image-2.6.39-2-amd64 package. At the time of the fault there was definetly no traffic on eth1. Most traffic at that time was NFS from a box attached to the network at eth0 to an NFS server in a VM attached to br0, though there might have been other traffic on that bridge too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633724: smartmontools: Support for WD MyBook Essential 0x1058:0x0910 (0x106)
Added to upstream drivedb.h r3404. Please run /usr/sbin/update-smart-drivedb to test. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632758: (False?) warning about problematic Seagate drives
According to http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951 the ST31000340AS with firmware SD15 is affected and should be updated to SD1A. Did Seagate actually fix this serious bug without changing the reported firmware version number? If this is the case the only thing we could do is to mention this fact in the warning text, see the SAMSUNG SpinPoint F4 EG drivedb entry for an example. You could add a local entry in /etc/smart_drivedb.h to suppress the warning. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614325: smartmontools: Please add SAMSUNG HM250HI to database
Added 2010-07-21 to upstream drivedb.h r3126 (USB 0x0411:0x0181) and r3127 (SAMSUNG HM250HI). This is included in Debian wheezy smartmontools-5.40+svn3296-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621411: smartmontools: Please add support for Seagate Expansion Desk external (usb) disks
Added to upstream drivedb.h r3321. Please run /usr/sbin/update-smart-drivedb to test. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619208: smartmontools: FTBFS on hurd-i386: missing #include in os_generic.cpp
The os_generic.cpp is a dummy OS interface module which is selected by configure for platforms not yet supported by smartmontools. I would suggest to remove the smartmontools package from hurd-i386. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581996: errors on Intel X25-M V2 SSD
The new Intel X25-M firmware 2CV102M3 fixes possible drive hangs when reading SMART self-test log. http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=18363 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608586: mplayer segfaults in demux_open for specific input file
Package: mplayer Version: 2:1.0~rc3++final.dfsg1-1 Severity: important Tags: squeeze nihi...@menelaos:~$ wget http://ftp.ccc.de/congress/27C3/mp4-h264-HQ/4018-en-frozencache.mp4 [...] nihi...@menelaos:~$ mplayer 4018-en-frozencache.mp4 MPlayer 1.0rc3-4.4.4 (C) 2000-2009 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing 4018-en-frozencache.mp4. libavformat file format detected. MPlayer interrupted by signal 11 in module: demux_open - MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash. - MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and won't help unless you provide this information when reporting a possible bug. [ This binary of MPlayer in Debian is currently compiled with '--enable-debug'; the debugging symbols are in the package 'mplayer-dbg'.] (gdb) backtrace #0 0x70c37e6e in mov_read_hdlr (c=0xb34be0, pb=0xb269c0, atom=...) at /build/buildd-ffmpeg_0.5.2-6-amd64-tx9WBV/ffmpeg-0.5.2/libavformat/mov.c:316 #1 0x70c36b9b in mov_read_default (c=value optimized out, pb=0xb269c0, atom=...) at /build/buildd-ffmpeg_0.5.2-6-amd64-tx9WBV/ffmpeg-0.5.2/libavformat/mov.c:221 #2 0x70c36b9b in mov_read_default (c=value optimized out, pb=0xb269c0, atom=...) at /build/buildd-ffmpeg_0.5.2-6-amd64-tx9WBV/ffmpeg-0.5.2/libavformat/mov.c:221 #3 0x70c36b9b in mov_read_default (c=value optimized out, pb=0xb269c0, atom=...) at /build/buildd-ffmpeg_0.5.2-6-amd64-tx9WBV/ffmpeg-0.5.2/libavformat/mov.c:221 #4 0x70c3705a in mov_read_moov (c=0xb269c0, pb=0xb269c0, atom=...) at /build/buildd-ffmpeg_0.5.2-6-amd64-tx9WBV/ffmpeg-0.5.2/libavformat/mov.c:494 #5 0x70c36b9b in mov_read_default (c=value optimized out, pb=0xb269c0, atom=...) at /build/buildd-ffmpeg_0.5.2-6-amd64-tx9WBV/ffmpeg-0.5.2/libavformat/mov.c:221 #6 0x70c39b28 in mov_read_header (s=0xb33bb0, ap=value optimized out) at /build/buildd-ffmpeg_0.5.2-6-amd64-tx9WBV/ffmpeg-0.5.2/libavformat/mov.c:2010 #7 0x70c0482d in av_open_input_stream (ic_ptr=0x7fffd088, pb=0xb269c0, filename=0x7fffcf50 mp:4018-en-frozencache.mp4, fmt=0x70e8b980, ap=0x7fffd050) at /build/buildd-ffmpeg_0.5.2-6-amd64-tx9WBV/ffmpeg-0.5.2/libavformat/utils.c:441 #8 0x005d1ba3 in demux_open_lavf (demuxer=0xb296d0) at libmpdemux/demux_lavf.c:467 #9 0x0052b8c8 in demux_open_stream (stream=value optimized out, file_format=value optimized out, force=value optimized out, audio_id=value optimized out, video_id=value optimized out, dvdsub_id=-2, filename=0xb045d0 4018-en-frozencache.mp4) at libmpdemux/demuxer.c:821 #10 0x0052ba91 in demux_open (vs=value optimized out, file_format=value optimized out, audio_id=1919706216, video_id=value optimized out, dvdsub_id=11710344, filename=0xb045d0 4018-en-frozencache.mp4) at libmpdemux/demuxer.c:1000 #11 0x004557b3 in main (argc=value optimized out, argv=value optimized out) at mplayer.c:3202 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mplayer depends on: ii libaa1 1.4p5-38 ascii art library ii libasound2 1.0.23-2.1 shared library for ALSA applicatio ii libaudio2 1.9.2-4 Network Audio System - shared libr ii libavcodec524:0.5.2-6ffmpeg codec library ii libavformat52 4:0.5.2-6ffmpeg file format library ii libavutil49 4:0.5.2-6ffmpeg utility library ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcaca00.99.beta17-1colour ASCII art library ii libcdparanoia0 3.10.2+debian-9 audio extraction tool for sampling ii libdirectfb-1.2-9 1.2.10.0-4 direct frame buffer graphics - sha ii libdvdread4 4.1.3-10 library for reading DVDs ii libenca01.13-3 Extremely Naive Charset Analyser - ii libesd0 0.2.41-8 Enlightened Sound Daemon - Shared ii libfontconfig1 2.8.0-2.1generic font configuration library ii libfreetype62.4.2-2.1FreeType 2 font engine, shared lib ii libfribidi0 0.19.2-1 Free Implementation of the Unicode ii libgcc1 1:4.4.5-8
Bug#601258: Bug #601258: SandForce SSD errors
The WARNING messages appear because the threshold of attribute 177 is missing in the SMART threshold data reported by SandForce based SSDs. Updating drivedb.h would fix the attribute names but won't suppress the warning messages. New smartmontools release 5.40 handles missing attributes and prints attributes of SandForce based SSDs correctly. -- Christian Franke smartmontools-supp...@lists.sourceforge.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593502: Please compile smartmontools with --enable-drivedb to allow updates of drivedb.h at runtime
The ./configure option --enable-drivedb is not required for new releases. It is set by default since SVN trunk r3139. New or updated database entries could also be added via /etc/smart_drivedb.h, regardless of the --enable-drivedb setting. See -B option on smartctl man page for further info. -- Christian Franke smartmontools-supp...@lists.sourceforge.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570892: smartctl does not warn about SMART Attribute Autosave disabled
We cannot fix this. A note was added to man page in r3097. Please set this bug to wontfix. -- Christian Franke smartmontools-supp...@lists.sourceforge.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570892: smartctl does not warn about SMART Attribute Autosave disabled
It is not possible to print such a warning for ATA/SATA devices. The ATA standard does not specify a method to check whether Attribute Autosave is enabled. I will add a note to the man page. -- Christian Franke smartmontools-supp...@lists.sourceforge.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564876: smartd: internal error in MailWarning(): cfg.mailwarn-emailfreq=0
This bug exists - but only in the Debian version of smartd. It is a regression introduced by the change for the '--capabilities' option (#ifdef HAVE_LIBCAP_NG). This option does not exist in the upstream version yet. The patch accidentally removes the warning mail enabled check at the beginning of MailWarning(), see lines 2849-51 of: http://ftp.de.debian.org/debian/pool/main/s/smartmontools/smartmontools_5.39-3.diff.gz Please reopen this bug. Cheers, Christian -- Christian Franke smartmontools-supp...@lists.sourceforge.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545808: bind9: Binding to specific Ipv6 address does not work with chroot (-t)
Package: bind9
Version: 1:9.5.1.dfsg.P3-1
Severity: important
I need the named to bind on a specific address, let's say 2001:123:1234::1.
I specify: listen-on-v6 { 2001:123:1234::1/128; }; in the named.conf.options.
When starting named with /etc/init.d/bind9, it does not listen on IPv6.
The init script starts it with the option -t /var/lib/bind.
Starting it without -t .. makes named bind on the address.
This is a very unexpected behaviour and should not happen.
The logs with -t and without -t have the line
listening on IPv6 interface lo, 2001:123:1234::1#53
as only difference. There is no error message to be seen.
Binding on IPv6 works with -t ... if listen-on-v6 { any; }; is specified,
however I can't use any and any shouldn't be used in the most cases anyway.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.20-xen-r6 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bind9 depends on:
ii adduser 3.110add and remove users and groups
ii bind9utils 1:9.5.1.dfsg.P3-1Utilities for BIND
ii debconf [debcon 1.5.24 Debian configuration management sy
ii libbind9-40 1:9.5.1.dfsg.P3-1BIND9 Shared Library used by BIND
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libcap2 2.11-2 support for getting/setting POSIX.
ii libdb4.64.6.21-11Berkeley v4.6 Database Libraries [
ii libdns451:9.5.1.dfsg.P3-1DNS Shared Library used by BIND
ii libisc451:9.5.1.dfsg.P3-1ISC Shared Library used by BIND
ii libisccc40 1:9.5.1.dfsg.P3-1Command Channel Library used by BI
ii libisccfg40 1:9.5.1.dfsg.P3-1Config File Handling Library used
ii libkrb531.6.dfsg.4~beta1-5lenny1 MIT Kerberos runtime libraries
ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries
ii liblwres40 1:9.5.1.dfsg.P3-1Lightweight Resolver Library used
ii libssl0.9.8 0.9.8g-15+lenny3 SSL shared libraries
ii libxml2 2.6.32.dfsg-5+lenny1 GNOME XML library
ii lsb-base3.2-20 Linux Standard Base 3.2 init scrip
ii net-tools 1.60-22 The NET-3 networking toolkit
ii netbase 4.34 Basic TCP/IP networking system
bind9 recommends no packages.
Versions of packages bind9 suggests:
pn bind9-doc none(no description available)
ii dnsutils 1:9.5.1.dfsg.P3-1 Clients provided with BIND
pn resolvconf none(no description available)
pn ufwnone(no description available)
-- debconf information:
bind9/different-configuration-file:
bind9/run-resolvconf: true
bind9/start-as-user: bind
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
