[Bug 2061929] Re: Python docker package does not import, crashes due to urllib3 upgrade

[A. Karl Kornel]

Looking around, I found an upstream (Debian) bug report related to this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065926

Debian hasn't switched their default Python to 3.12 yet, but it looks
like that's in work, and so this issue will appear there.

I'll email the Debian bug, letting them know about the issue here.

Jonas, you're right that moving to a newer usptream is probably the
best.  Unfortunately I don't know the policies here: Maybe the MOTU
folks will want Debian to move first?

** Bug watch added: Debian Bug tracker #1065926
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065926

** Also affects: debbugs via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065926
   Importance: Unknown
   Status: Unknown

** No longer affects: debbugs

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker package does not import, crashes due to urllib3 upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061929] Re: Python docker package does not import, crashes due to urllib3 upgrade

[A. Karl Kornel]

** Description changed:

- This is on a fresh install of the 20.04 beta that was released on April
+ This is on a fresh install of the 24.04 beta that was released on April
  12.  I used the Desktop installer, into a VMware Fusion VM, on amd64.
  
  Other than the defaults for a fresh Ubuntu Desktop install, all I ran
  was `apt install -y docker.io python3-docker`.
  
  I ran `python3`, tried to execute `import docker`, and got this:
  
  Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import docker
  Traceback (most recent call last):
-   File "", line 1, in 
-   File "/usr/lib/python3/dist-packages/docker/__init__.py", line 2, in 

- from .api import APIClient
-   File "/usr/lib/python3/dist-packages/docker/api/__init__.py", line 2, in 

- from .client import APIClient
-   File "/usr/lib/python3/dist-packages/docker/api/client.py", line 10, in 

- from .. import auth
-   File "/usr/lib/python3/dist-packages/docker/auth.py", line 5, in 
- from . import credentials
-   File "/usr/lib/python3/dist-packages/docker/credentials/__init__.py", line 
2, in 
- from .store import Store
-   File "/usr/lib/python3/dist-packages/docker/credentials/store.py", line 7, 
in 
- from .utils import create_environment_dict
-   File "/usr/lib/python3/dist-packages/docker/credentials/utils.py", line 1, 
in 
- import distutils.spawn
+   File "", line 1, in 
+   File "/usr/lib/python3/dist-packages/docker/__init__.py", line 2, in 

+ from .api import APIClient
+   File "/usr/lib/python3/dist-packages/docker/api/__init__.py", line 2, in 

+ from .client import APIClient
+   File "/usr/lib/python3/dist-packages/docker/api/client.py", line 10, in 

+ from .. import auth
+   File "/usr/lib/python3/dist-packages/docker/auth.py", line 5, in 
+ from . import credentials
+   File "/usr/lib/python3/dist-packages/docker/credentials/__init__.py", line 
2, in 
+ from .store import Store
+   File "/usr/lib/python3/dist-packages/docker/credentials/store.py", line 7, 
in 
+ from .utils import create_environment_dict
+   File "/usr/lib/python3/dist-packages/docker/credentials/utils.py", line 1, 
in 
+ import distutils.spawn
  ModuleNotFoundError: No module named 'distutils'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: python3-docker 5.0.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 16:35:20 2024
  InstallationDate: Installed on 2024-04-16 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  PackageArchitecture: all
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: python-docker
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker package does not import, crashes due to urllib3 upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061929] Re: Python docker package does not import, crashes due to urllib3 upgrade

[A. Karl Kornel]

** Patch added: "Remove the calls to distutils, so that the package no longer 
relies on python3-distutils or python3-setuptools"
   
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+attachment/5766881/+files/no-distutils.patch

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker package does not import, crashes due to urllib3 upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061929] Re: Python docker package does not import, crashes due to urllib3 upgrade

[A. Karl Kornel]

** Patch added: "Update use of requests & urllib3 to work with urllib3 2.0"
   
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+attachment/5766882/+files/requests-urllib3-updates.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker package does not import, crashes due to urllib3 upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061929] Re: Python docker package does not import, crashes due to urllib3 upgrade

[A. Karl Kornel]

It looks like https://github.com/docker/docker-py/pull/3116 is the pull
request which fixes this issue.

I've only just started using this Python package, so I'm not able to do
a full test, but I'm at least able to take a pass at making a patch.
I'll provide a patch for both issues: The reliance on setuptools code,
and the urllib3 2.0 incompatibility.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker package does not import, crashes due to urllib3 upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061929] Re: Python docker package does not import: No module named 'distutils'

[A. Karl Kornel]

It looks like things are worse than I thought.

Once I install python3-setuptools, even though the `docker` module now
imports successfully, running `docker.from_env()` fails with the
following:


Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import docker
>>> docker.from_env()
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/docker/api/client.py", line 214, in 
_retrieve_server_version
return self.version(api_version=False)["ApiVersion"]
   ^^^
  File "/usr/lib/python3/dist-packages/docker/api/daemon.py", line 181, in 
version
return self._result(self._get(url), json=True)
^^
  File "/usr/lib/python3/dist-packages/docker/utils/decorators.py", line 46, in 
inner
return f(self, *args, **kwargs)
   
  File "/usr/lib/python3/dist-packages/docker/api/client.py", line 237, in _get
return self.get(url, **self._set_request_timeout(kwargs))
   ^^
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 602, in get
return self.request("GET", url, **kwargs)
   ^^
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 589, in 
request
resp = self.send(prep, **send_kwargs)
   ^^
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 703, in send
r = adapter.send(request, **kwargs)
^^^
  File "/usr/lib/python3/dist-packages/requests/adapters.py", line 486, in send
resp = conn.urlopen(
   ^
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 791, in 
urlopen
response = self._make_request(
   ^^^
  File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 497, in 
_make_request
conn.request(
TypeError: HTTPConnection.request() got an unexpected keyword argument 'chunked'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/docker/client.py", line 96, in from_env
return cls(
   
  File "/usr/lib/python3/dist-packages/docker/client.py", line 45, in __init__
self.api = APIClient(*args, **kwargs)
   ^^
  File "/usr/lib/python3/dist-packages/docker/api/client.py", line 197, in 
__init__
self._version = self._retrieve_server_version()
^^^
  File "/usr/lib/python3/dist-packages/docker/api/client.py", line 221, in 
_retrieve_server_version
raise DockerException(
docker.errors.DockerException: Error while fetching server API version: 
HTTPConnection.request() got an unexpected keyword argument 'chunked'


This is https://github.com/docker/docker-py/issues/3113, an issue reported 
about a year ago.  Per the urllib3 maintainer, who commented on the bug:

> I can confirm however that docker-py is not compatible with urllib3
2.0. Since requests will soon allow it, docker-py should modify setup.py
to use urllib3 >= 1.26.0, < 2.0.0 or fix the bug.

So, simply installing python3-setuptools won't be enough.  The module
code itself either needs patches, or it needs upgrading to a new
upstream version.  Per https://github.com/docker/docker-
py/issues/3113#issuecomment-1536476705, the issue was fixed upstream
starting with version 6.1.0.

** Bug watch added: github.com/docker/docker-py/issues #3113
   https://github.com/docker/docker-py/issues/3113

** Summary changed:

- Python docker package does not import: No module named 'distutils'
+ Python docker package does not import, crashes due to urllib3 upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker package does not import, crashes due to urllib3 upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061929] Re: Python docker package does not import: No module named 'distutils'

[A. Karl Kornel]

** Summary changed:

- Python docker page does not import: No module named 'distutils'
+ Python docker package does not import: No module named 'distutils'

** Tags removed: wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker package does not import: No module named 'distutils'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061929] Re: Python docker page does not import: No module named 'distutils'

[A. Karl Kornel]

I've been doing some checking, and it looks like this is because Python
3.12 (the default python3) no longer includes distutils.  See
https://docs.python.org/3.12/whatsnew/3.12.html (the first paragraph
under the heading "Summary – Release highlights"), as well as PEP-0632
(https://peps.python.org/pep-0632/).

I figured this out when I tried downgrading the package to the version
in Mantic (5.0.3-1ubuntu1): `dpkg` complained that it depends on
`python3-distutils`.  That led me to searching for the package in Noble,
and getting to this point.

(Adding the `regression-release` tag.  Apologies if this is the wrong
regression tag to apply!)

BTW, this isn't affecting Debian 12 because they're using Python 3.11,
the last Python version to include distutils in the standard library.
Debian sid is currently on Python 3.11.8, so they haven't hit this issue
yet.

As for upstream, looking at PyPi
(https://pypi.org/project/docker/#history), 5.0.3 was the last of the
5.x series.  Their latest versions are 6.1.3 and 7.0.0.  Their changelog
page (https://docker-py.readthedocs.io/en/stable/change-log.html) does
not explicitly say when they moved away from distutils, but from Git
commits it looks like the removal happened in
https://github.com/docker/docker-
py/commit/42789818bed5d86b487a030e2e60b02bf0cfa284, which was included
in the 6.0.0 and later releases.

So, what to do in the meantime?  According to PEP-0632, Setuptools
adopted distutils, and this started to happen in Setuptools 48
(https://github.com/pypa/setuptools/issues/417#issuecomment-653593796).
Since the python3-setuptools package in Noble is newer
(68.1.2-2ubuntu1), probably the best workaround is for `python3-docker`
to depend on `python3-setuptools`.

== Regression details ==
Discovered in version:5.0.3-1ubuntu1
Last known good version:5.0.3-1

** Bug watch added: github.com/pypa/setuptools/issues #417
   https://github.com/pypa/setuptools/issues/417

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker package does not import: No module named 'distutils'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061929] Re: Python docker page does not import: No module named 'distutils'

[A. Karl Kornel]

** Tags added: regression-release

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker page does not import: No module named 'distutils'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061929] [NEW] Python docker page does not import: No module named 'distutils'

[A. Karl Kornel]

Public bug reported:

This is on a fresh install of the 20.04 beta that was released on April
12.  I used the Desktop installer, into a VMware Fusion VM, on amd64.

Other than the defaults for a fresh Ubuntu Desktop install, all I ran
was `apt install -y docker.io python3-docker`.

I ran `python3`, tried to execute `import docker`, and got this:

Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import docker
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/docker/__init__.py", line 2, in 
from .api import APIClient
  File "/usr/lib/python3/dist-packages/docker/api/__init__.py", line 2, in 

from .client import APIClient
  File "/usr/lib/python3/dist-packages/docker/api/client.py", line 10, in 

from .. import auth
  File "/usr/lib/python3/dist-packages/docker/auth.py", line 5, in 
from . import credentials
  File "/usr/lib/python3/dist-packages/docker/credentials/__init__.py", line 2, 
in 
from .store import Store
  File "/usr/lib/python3/dist-packages/docker/credentials/store.py", line 7, in 

from .utils import create_environment_dict
  File "/usr/lib/python3/dist-packages/docker/credentials/utils.py", line 1, in 

import distutils.spawn
ModuleNotFoundError: No module named 'distutils'

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: python3-docker 5.0.3-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 16:35:20 2024
InstallationDate: Installed on 2024-04-16 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: python-docker
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-docker (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061929

Title:
  Python docker page does not import: No module named 'distutils'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2061929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument

[A. Karl Kornel]

Hello!

I just wanted to chime in: My co-worker and I ran into this exact
problem.  The `traceroute6` command was giving us "sendto: Invalid
argument", and we did not have the `traceroute` package installed.  It
was only by finding this Launchpad bug that we became aware of the
problem, after about half an hour of confusion and web-searching.

One other note: In addition to installing the `traceroute` package, we
also had to use `update-alternatives`, so that running traceroute (or
traceroute6) would go to the executable provided by the traceroute
package.

This was really confusing, so I would like to suggest that some sort of
action be taken upstream: Maybe a Release Notes item, or some other way
to let sysadmins know that the `traceroute6` executable in the iputils
package has an important bug (as per the Debian bug entry), and that the
workaround is to install the traceroute package, and then use `update-
alternatives` to set traceroute's traceroute6 as the preferred
traceroute6.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798313

Title:
  traceoute6 gives error sendto: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/1798313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1773100] Re: Bionic Server ISO soft lockup on Dell C6420 in swapper - Xenial appears OK

[A. Karl Kornel]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773100

Title:
  Bionic Server ISO soft lockup on Dell C6420 in swapper - Xenial
  appears OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773100/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1773100] [NEW] Bionic Server ISO soft lockup on Dell C6420 in swapper - Xenial appears OK

[A. Karl Kornel]

Public bug reported:

Hello!

We are experiencing a soft lockup when booting the Bionic Server
installer amd64 ISO (kernel 4.15.0-20).  The installer seems to hang on
boot: After GRUB, nothing ever appears on the display, and we only
managed to get kernel logs through Serial-Over-LAN.  The 16.04.4 Server
installer ISO (kernel 4.4.0-16) does not seem to have this problem.

Our hardware is a Dell C6420.  The C6420 is one node in a four-node, 2 U
chassis (the C6400 chassis).  The node's hardware is two Intel Xeon Gold
6134 CPUs (8 cores @ 3.2 GHz/core).  RAM is 96 GB, as twelve 8 GB DIMMs.
We have tested with Hyperthreading on and off, and with UFEI and BIOS
boot modes, and we get the same results in both cases.

Right now, we have Hyperthreading on, and we are booting in UEFI mode.
If you need us to change that for testing, let us know!

Here are the first 25 lines of the soft lockup:

[   40.544002] watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [swapper/0:1]
[   40.628002] Modules linked in:
[   40.664000] CPU: 24 PID: 1 Comm: swapper/0 Not tainted 4.15.0-20-generic 
#21-Ubuntu
[   40.756002] Hardware name: Dell Inc. PowerEdge C6420/0K2TT6, BIOS 1.3.7 
02/09/2018
[   40.844002] RIP: 0010:smp_call_function_many+0x229/0x250
[   40.908002] RSP: :aa61000eb868 EFLAGS: 0202 ORIG_RAX: 
ff11
[   41.00] RAX: 0004 RBX: 8eba9f5238c0 RCX: 0001
[   41.084002] RDX: 8eba9f2a8f60 RSI:  RDI: 8eba96754de0
[   41.168002] RBP: aa61000eb8a0 R08: fff0 R09: feff
[   41.252003] R10: ecb61f56b380 R11: 0004 R12: 0100
[   41.340002] R13: 00023880 R14: b4035030 R15: 
[   41.424002] FS:  () GS:8eba9f50() 
knlGS:
[   41.520002] CS:  0010 DS:  ES:  CR0: 80050033
[   41.588002] CR2:  CR3: 00018c00a001 CR4: 007606e0
[   41.676002] DR0:  DR1:  DR2: 
[   41.760004] DR3:  DR6: fffe0ff0 DR7: 0400
[   41.844002] PKRU: 
[   41.876002] Call Trace:
[   41.908002]  ? nsio_rw_bytes+0xd9/0x250
[   41.952002]  ? cpumask_weight+0x20/0x20
[   42.02]  ? nsio_rw_bytes+0xda/0x250
[   42.044003]  ? quirk_intel_brickland_xeon_ras_cap+0x60/0x60
[   42.112002]  on_each_cpu+0x2d/0x60
[   42.152000]  ? nsio_rw_bytes+0xd9/0x250
[   42.196003]  text_poke_bp+0x6a/0xf0

The full output is attached as "kernel 4.15.0-20 boot.txt".  We used the
following kernel command line:

BOOT_IMAGE=/install/vmlinuz file=/cdrom/preseed/ubuntu-server.seed
console=tty0 console=ttyS0 console=ttyS1 debug ---

As I mentioned up top, we have started installing the Ubuntu Server
16.04.4 Server ISO, and this far the kernel is booting, and we have
gotten through to the text-based installer.

I'm sorry that I couldn't use the normal kernel bug-reporting process,
but since we're hitting this problem in the installer, I'm not sure what
else we can do.

I also apologize that I don't have any more info, since it's after
Midnight local time, but I wanted to make sure I got this information
through to you ASAP.

At this point, we're probably going to move forward with the 16.04.4
Server installer for now, but we do have an identical C6420 node (in a
different chassis), and we will probably be able to use that for testing
for at least a little while!  For example, we were thinking of trying
the 16.04 HWE kernel, as an additional data point.

So, please let us know what additional information you would like, and
what else we can try.  Thanks very much!

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-bug

** Attachment added: "Serial console output from the Bionic Server installer, 
with "debug" active"
   
https://bugs.launchpad.net/bugs/1773100/+attachment/5143673/+files/kernel%204.15.0-20%20boot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773100

Title:
  Bionic Server ISO soft lockup on Dell C6420 in swapper - Xenial
  appears OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1773100/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 517270] Re: cupsd crashed with SIGSEGV in com_right()

[A. Karl Kornel]

OK, now that I see the appport data that's been attached, I think this
is a duplicate of another problem I'm seeing, which I've already
submitted in Bug 414359.

** Visibility changed to: Public

-- 
cupsd crashed with SIGSEGV in com_right()
https://bugs.launchpad.net/bugs/517270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 514456] [NEW] Browser entries pane greys out on keypress under OU

[A. Karl Kornel]

Public bug reported:

Binary package hint: luma

Hello!  I am having problems with the Browser plugin in Luma.  When I
press a key on the keyboard, the Entries pane (which lists all of the
servers, and their entries) greys out, and Luma essentially becomes
unusable.  This is luma 2.3-1.1

Here are my steps to reproduce:

1) Launch Luma
2) Click on the Browser plugin
3) Expand the entry for one of the already-configured LDAP servers
4) Click on one of the "o=" entries that appear
5) Press a letter key on the keyboard

When I execute Step 5, I expect Luma to either do nothing, or
(preferably) to start going to the item whose name matches what I am
typing.  Instead, the Entries pane in the browser greys out, a bomb icon
appears in the lower-right corner.  After clicking on the bomb icon, the
following error message appears:

An unhandled exception occured. This is most likely a bug 
in the programming of Luma. In order to fix this, send an email with the 
following text and a detailed description of what you were doing to
luma-us...@lists.sourceforge.net.
  File "/usr/lib/luma/base/utils/gui/BrowserWidget.py", line 876, in 
keyPressEvent
if keyTex == tmpString[0].lower():
Reason:  global name 'keyTex' is not defined

The only way to resolve the issue is to quit and re-launch Luma.

** Affects: luma (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Browser entries pane greys out on keypress under OU
https://bugs.launchpad.net/bugs/514456
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] Re: Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

Hello again!

I've got another twist on this bug!  Last night, I tried logging into a
machine that is showing this problem.  I was logging in using SSH, using
the PuTTY Windows SSH client.  At the time I made the connection, I
entered the wrong username by mistake, but I did not catch my mistake
until I had finished entering my password.  After entering the password,
PuTTY just sat for a while, waiting, and then reported that the remote
side had closed the connection.

Once I got back into work, I did a test with this on my workstation
(also running Ubuntu Hardy, fully up-to-date), and I discovered the
following:  If you have PAM configured to use Heimdal's pam_krb5.so
module, and you try to log in with an invalid username, openssh-server's
sshd will crash in the same place as dovecot-imapd.

Since I did the verification on my Linux workstation, I had apport
running, and it grabbed a crash report.  I processed the crash report
with `appport-cli -c` and saved the report, so it has the core dump AND
all of the information that is derived from the core dump.  I really
hope this extra info helps!

** Attachment added: "usr_sbin_sshd.0.crash"
   http://launchpadlibrarian.net/35196951/usr_sbin_sshd.0.crash

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] Re: Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

Hello!

When I got the machine, I installed Ubuntu 6.06.1 LTS.  From time to
time, I installed additional packages, including Dovecot.  Also from
time to time, I'd do `apt-get update` followed by `apt-get upgrade`.
Then, on 6 August, I ran:

apt-get update
apt-get install update-manager-core
do-release-upgrade

(I already had the dapper-updates repository in my APT sources.list when
I did this)

I ran those commands based on the instructions at
.

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 445028] Re: Intermittent segfault in var_hrswrun

[A. Karl Kornel]

Hello!

Sure, I can install it & let it run until it hopefully does not die!

I just checked your PPA, and I'm really sorry, I should've said that I'm
running on the amd64 platform!

-- 
Intermittent segfault in var_hrswrun
https://bugs.launchpad.net/bugs/445028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 445028] Re: Intermittent segfault in var_hrswrun

[A. Karl Kornel]

** Attachment added: "snmpd.conf"
   http://launchpadlibrarian.net/33285009/snmpd.conf

-- 
Intermittent segfault in var_hrswrun
https://bugs.launchpad.net/bugs/445028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 445028] [NEW] Intermittent segfault in var_hrswrun

[A. Karl Kornel]

Public bug reported:

I am running Ubuntu 8.04.3 LTS, upgraded from 6.06 LTS.  At intermittent
times, snmpd dies with a segfault.  Once I restart it, snmpd behaves
normally, but will eventually die again.  The interval between starting
snmpd and having it die by segfault can be as small as an hour and as
large as 3 weeks.  I have a backtrace from the most recent segfault,
which I am attaching.  The version of snmpd and libsnmp15 used to
generate the backtrace is 5.4.1~dfsg-4ubuntu4.3, which is currently in
hardy-proposed.

I originally thought that this was part of bug #200614, as I was seeing
the same problem.  That is why I am using the hardy-proposed version of
snmpd, is because I thought it would fix the segfaults.  However, the
fix for bug #200614 does not fix this segfault problem for me; when I
brought it up in the bug (bug #200614 comment 18), I was told that it
was probably not related (bug #200614 comment 19), and that I should
submit a new bug, which I am doing now!

** Affects: net-snmp (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Intermittent segfault in var_hrswrun
https://bugs.launchpad.net/bugs/445028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 445028] Re: Intermittent segfault in var_hrswrun

[A. Karl Kornel]

** Attachment added: "gdb-snmpd.txt"
   http://launchpadlibrarian.net/33188509/gdb-snmpd.txt

-- 
Intermittent segfault in var_hrswrun
https://bugs.launchpad.net/bugs/445028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 200614] Re: segfault and warnings from net-snmp 5.4.x

[A. Karl Kornel]

Hello, I'm back with some bad news...

On Saturday, snmpd segfaulted again.  This was on the same machine which
I had said was running OK after installing the hardy-proposed packages.

I re-started snmpd under gdb Saturday; it crashed again today, and
here's the backtrace info from the crash.

** Attachment added: "gdb-snmpd.txt"
   http://launchpadlibrarian.net/33001676/gdb-snmpd.txt

-- 
segfault and warnings from net-snmp 5.4.x
https://bugs.launchpad.net/bugs/200614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 200614] Re: segfault and warnings from net-snmp 5.4.x

[A. Karl Kornel]

Hello!  Since it's been a week I'm reporting back.  Everything is still
working fine!

-- 
segfault and warnings from net-snmp 5.4.x
https://bugs.launchpad.net/bugs/200614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] Re: Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

** Changed in: dovecot (Ubuntu)
   Status: Incomplete => New

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 200614] Re: segfault and warnings from net-snmp 5.4.x

[A. Karl Kornel]

Hello!  Well, with the weekend gone by, I'm happy to say that my SNMP
daemon is still up and running!

-- 
segfault and warnings from net-snmp 5.4.x
https://bugs.launchpad.net/bugs/200614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 200614] Re: segfault and warnings from net-snmp 5.4.x

[A. Karl Kornel]

I've installed the updated snmp, snmpd, libsnmp15, libsnmp-base,
libsnmp-dev, and libsnmp-perl packages onto one of my Hardy servers.
After an hour, things have been running OK, with no assertions or other
weird log entries, although I do see one new log entry:

Sep 24 15:27:09 npbnagb snmptrapd[16645]: Warning: no access control
information configured. This receiver will *NOT* accept any incoming
notifications.

If everything continues to go OK I'll report back in 1 day, and then (if
the package hasn't been released yet) in 1 week!

-- 
segfault and warnings from net-snmp 5.4.x
https://bugs.launchpad.net/bugs/200614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] Re: Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

H, looks like I needed a couple more debug packages.  Here's the GDB
file again after installing libcomerr2-dbgsym, libpam-heimdal-dbgsym,
and libkrb5-22-heimdal-dbgsym.

** Attachment added: "gdb-dovecot.txt"
   http://launchpadlibrarian.net/32407763/gdb-dovecot.txt

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] Re: Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

Hi Chuck,

I have done backtraces before, but this one was a little more unusual
for me.  The last time I needed a backtrace, I was able to capture the
daemon's full command line, then run it through GDB.  In this case, I'm
thinking the offending program is located at /usr/lib/dovecot/dovecot-
auth, it is run by the dovecot daemon as needed, and then exits with a
result (or, in this case, a crash) shortly after starting.

In this case, I stopped dovecot, sudo-ed into root, ran `ulimit -c
unlimited`, ran dovecot manually, and had my IMAP client try a login.
That caused dovecot-auth to die again (as expected), and dropped a core
file in /var/run/dovecot.  I installed both dovecot-common-dbgsym and
libpam0g-dbgsym packages, ran `gdb /usr/lib/dovecot/dovecot-auth core`,
and then ran the 5 GDB commands requested in
https://wiki.ubuntu.com/Backtrace.  Attached are the results!

** Attachment added: "gdb-dovecot.txt"
   http://launchpadlibrarian.net/32407551/gdb-dovecot.txt

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] Re: Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

** Attachment added: "/etc/pam.d/common-account"
   http://launchpadlibrarian.net/30383648/common-account

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] Re: Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

** Attachment added: "/etc/pam.d/common-auth"
   http://launchpadlibrarian.net/30383646/common-auth

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] Re: Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

** Attachment added: "/etc/pam.d/common-session"
   http://launchpadlibrarian.net/30383657/common-session

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] Re: Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

** Attachment added: "dovecot.conf"
   http://launchpadlibrarian.net/30383634/dovecot.conf

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414359] [NEW] Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash

[A. Karl Kornel]

Public bug reported:

The two servers showing this behavior were previously running an up-to-
date Ubuntu 6.06, which was then upgraded to an up-to-date Ubuntu 8.04
install.

The IMAP client I'm using (Opera) reports "Temporary authentication
failure".  The following entries appear in syslog, when I have
'auth_verbose' and 'auth_debug' set to "yes":

Aug 16 00:41:56 npbnagb dovecot: auth(default): new auth connection: pid=31751
Aug 16 00:41:56 npbnagb dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservi
ce=IMAP^Isecured^Ilip=10.1.16.85^Irip=192.168.235.121
Aug 16 00:41:56 npbnagb dovecot: auth(default): client out: CONT^I1^I
Aug 16 00:41:56 npbnagb dovecot: auth(default): client in: CONT
Aug 16 00:41:56 npbnagb dovecot: auth(default): pam(nagios,192.168.235.121): 
lookup service=dovecot
Aug 16 00:41:57 npbnagb kernel: [12214.451803] dovecot-auth[31752] general 
protection rip:7ffa8c7b57f6 rsp:7fff956f9b98 error:0
Aug 16 00:41:57 npbnagb dovecot: auth(default): pam(nagios,192.168.235.121): 
Child process died
Aug 16 00:41:57 npbnagb dovecot: auth(default): PAM: Child 31752 died with 
signal 11
Aug 16 00:41:57 npbnagb dovecot: auth(default): client out: 
FAIL^I1^Iuser=nagios^Itemp
Aug 16 00:41:57 npbnagb dovecot: imap-login: Disconnected: user=, 
method=PLAIN, rip=192.168.235.121, lip=10.1.16.85, TLS

The nagios account is a local account.

I also have another account on each server, for which I also have Opera
checking mail.  For this other account, I log in using my Kerberos
username and password, and things work fine.

** Affects: dovecot (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash
https://bugs.launchpad.net/bugs/414359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade on Sun X4200 M2

[A. Karl Kornel]

This is the last info I can provide.  I looked through some other bug
reports, and I decided to see what some combinations of boot options
could do:

* acpi_skip_timer_override: I didn't see any change.
* enable_8254_timer: I didn't see any change.
* disable_8254_timer: Kernel panic - not syncing: Attempted to kill init!
* noapic: The system was able to boot, and I didn't see the bug message.  I 
did, however, see "spurious 8259A interrupt: IRQ7." when I looked through the 
dmesg output.
* noapic nolapic: I saw all of the messages/changes that I saw when just 
'noapic' was set.
* acpi=off: I didn't see any of the ACPI information at boot, and the CPU 
frequency scaling module didn't load ("powernow-k8: MP systems not supported by 
PSB BIOS structure").  I didn't see any indication of the HPETs being used 
("time.c: Using PIT/TSC based timekeeping."), but I did see the line "testing 
NMI watchdog ... OK.".
* acpi=off noapic: I saw all of the messages/changes that I saw when just 
'acpi=off' and 'noapic' were set.  There were also some PCI errors ("PCI: IRQ 0 
for device :83:00.0 doesn't match PIRQ mask - try pci=usepirqmask" and 
"PCI: No IRQ known for interrupt pin A of device :83:00.0. Please try using 
pci=biosirq.").
* acpi=off noapic nolapic: I saw all of the messages/changes that I saw when 
just 'acpi=off' was set, and when 'acpi=off' and 'noapic' were set.

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade on Sun X4200 M2
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade on Sun X4200 M2

[A. Karl Kornel]

Here is the output from the `dmesg` command, when I boot the OS with
just the 'root' and 'ro' options.

So far, I have compromised by normally adding 'nmi_watchdog=0' to the
boot options, to suppress the NMI watchdog warnings.

** Attachment added: "badBIOS_dmesg.log"
   
http://launchpadlibrarian.net/16719043/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CbadBIOS_dmesg.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade on Sun X4200 M2
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade on Sun X4200 M2

[A. Karl Kornel]

I just noticed the KernelTeamBugPolicies Wiki entry suggests including
the hardware in the title.  My apologies for leaving this out before!

** Summary changed:

- "8254 timer not connected to IO-APIC" after BIOS upgrade
+ "8254 timer not connected to IO-APIC" after BIOS upgrade on Sun X4200 M2

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade on Sun X4200 M2
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

My apologies, I forgot the uname -a results from the "control" server!

** Attachment added: "goodBIOS_uname-a.log"
   
http://launchpadlibrarian.net/16717350/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CgoodBIOS_uname-a.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

** Attachment added: "badBIOS_uname-a.log"
   
http://launchpadlibrarian.net/16717265/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CbadBIOS_uname-a.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

** Attachment added: "badBIOS_dmidecode.log"
   
http://launchpadlibrarian.net/16717238/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CbadBIOS_dmidecode.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

** Attachment added: "badBIOS_version.log"
   
http://launchpadlibrarian.net/16717200/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CbadBIOS_version.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

** Attachment added: "badBIOS_lspci-vvnn.log"
   
http://launchpadlibrarian.net/16717162/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CbadBIOS_lspci-vvnn.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

I'm using "badBIOS" as an identifier for the problem machine.

** Attachment added: "badBIOS_lsb_release-rd.log"
   
http://launchpadlibrarian.net/16717135/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CbadBIOS_lsb_release-rd.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

This is the result of the `dmesg` command on the "control" server,
executed about 3 minutes after boot.  Some notes on the boot command
line:

* My boot partition is on an LVM2 logical volume
* The server's DB9 serial port is connected to a Cyclades serial server, hence 
the two 'console' lines

** Attachment added: "goodBIOS_dmesg.log"
   
http://launchpadlibrarian.net/16717089/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CgoodBIOS_dmesg.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

** Attachment added: "goodBIOS_dmidecode.log"
   
http://launchpadlibrarian.net/16717035/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CgoodBIOS_dmidecode.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

** Attachment added: "C:\Documents and 
Settings\kornelak\Desktop\attachments\goodBIOS_lspci-vvnn.log"
   
http://launchpadlibrarian.net/16717023/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CgoodBIOS_lspci-vvnn.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

** Attachment added: "goodBIOS_version.log"
   
http://launchpadlibrarian.net/16717031/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CgoodBIOS_version.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] Re: "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

** Attachment added: "Output of the `lsb_release -rd` command on the "control" 
server"
   
http://launchpadlibrarian.net/16717022/C%3A%5CDocuments%20and%20Settings%5Ckornelak%5CDesktop%5Cattachments%5CgoodBIOS_lsb_release-rd.log

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 257157] [NEW] "8254 timer not connected to IO-APIC" after BIOS upgrade

[A. Karl Kornel]

Public bug reported:

Hello!

I recently upgraded the BIOS on one of my severs, which run Dapper
(amd64 build), before rolling it out to the others.  After the BIOS
update, I have noticed some new, not-very-nice-looking messages in the
dmesg output during boot.  One of the messages is also apparently
important enough to be displayed on screen even when the 'quiet'
parameter is set.  I have confirmed that all packages are up-to-date.

The server was originally running BIOS version 44 (0ABJX044).  I
upgraded the BIOS to version 79 (0ABJX079).  Now, at boot, I see the
following message:

..MP-BIOS bug: 8254 timer not connected to IO-APIC

Looking through dmesg after boot, I see some additional messages that
are new:

..MP-BIOS bug: 8254 timer not connected to IO-APIC
 failed.
timer doesn't work through the IO-APIC - disabling NMI Watchdog!
Uhhuh. NMI received for unknown reason 3c.
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?

The hardware is a Sun Fire X4200 M2 server, running 2 dual-core AMD
Opterons.  Attached PCI devices include 2 QLogic QLE2460 single-port 4
GBps Fibre Channel cards, an LSI SAS controller that hosts the two
internal hard drives (hardware RAID is not configured), a PCI Express
card containing two serial ports (those are the 2 Oxford devices you'll
see in the lspci output), and an Intel PRO/1000 dual-port Gigabit
Ethernet PCI Express card.

My servers do have support from the VAR; when I called them and provided
details (Applied Computer Solutions, Huntington Beach, CA, ticket
#4384), they opened a support case with Sun (Sun Case #66043616).
To quote Sun support, "The issue we are seeing is in the Kernel and not
a hardware issue."

I would like to help as much as I can.  It helps that this server is
part of a two-server active/passive cluster, which is how I was able to
get all the upcoming data quickly.  The other node in the cluster has
not had its BIOS upgraded, so I can give you its log files as a sort of
"control".  For those who will ask, upgrading to Hardy is not an option
at this time, as I have software that is not compatible with MySQL 5
right now (so I need to continue using MySQL 4).

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 84821] Re: "attempt to access beyond end of device" when creating LVM snapshot

[A. Karl Kornel]

And, finally, an example of the problem:

[EMAIL PROTECTED]:/var/lib/mysql/main$ dmesg|tail
[17180786.72] EXT3-fs: mounted filesystem with ordered data mode.
[17180799.652000] kjournald starting.  Commit interval 5 seconds
[17180799.656000] EXT3 FS on dm-41, internal journal
[17180799.656000] EXT3-fs: recovery complete.
[17180799.656000] EXT3-fs: mounted filesystem with ordered data mode.
[17203415.252000] ibm_acpi: ec object not found
[17808026.704000] ibm_acpi: ec object not found
[18412815.972000] ibm_acpi: ec object not found
[19017364.116000] ibm_acpi: ec object not found
[19622027.484000] ibm_acpi: ec object not found
[EMAIL PROTECTED]:/var/lib/mysql/main$ sudo lvs
   LV   VG Attr   LSize  Origin  Snap%  
Move Log Copy%
  Database_LogsVolGroup00 -wi-ao 10.00G 
  Database_MainVolGroup00 -wi-ao  5.00G 
  Database_Stage_31743 VolGroup00 swi-a-  5.00G Database_Stage_Orig   0.00 
  Database_Stage_32781 VolGroup00 swi-a-  5.00G Database_Stage_Orig   0.00 
  Database_Stage_34352 VolGroup00 swi-a-  5.00G Database_Stage_Orig   0.00 
  Database_Stage_Orig  VolGroup00 owi-ao 35.00G 
  Database_Transition  VolGroup00 -wi-ao 80.00G 
  Home VolGroup00 -wi-a-  3.00G 
  Live VolGroup00 -wi-ao 94.00G 
  Root VolGroup00 -wi-a- 10.00G 
  Stage_31743  VolGroup00 swi-a-  5.00G Stage_Orig0.00 
  Stage_32781  VolGroup00 swi-a-  5.00G Stage_Orig0.00 
  Stage_34352  VolGroup00 swi-a-  5.00G Stage_Orig0.00 
  Stage_Orig   VolGroup00 owi-ao 76.00G 
  Swap VolGroup00 -wi-ao  2.00G 
  root VolGroup00 -wi-ao 15.00G 
[EMAIL PROTECTED]:/var/lib/mysql/main$ sudo lvcreate --verbose --snapshot 
--size 5G --name Database_Stage_35780 VolGroup00/Database_Stage_Orig
Setting chunksize to 16 sectors.
Finding volume group "VolGroup00"
Archiving volume group "VolGroup00" metadata (seqno 485).
Creating logical volume Database_Stage_35780
Creating volume group backup "/etc/lvm/backup/VolGroup00" (seqno 486).
Found volume group "VolGroup00"
Creating VolGroup00-Database_Stage_35780
Loading VolGroup00-Database_Stage_35780 table
Resuming VolGroup00-Database_Stage_35780 (254:42)
Zeroing start of logical volume "Database_Stage_35780"
Found volume group "VolGroup00"
Removing VolGroup00-Database_Stage_35780 (254:42)
Found volume group "VolGroup00"
Found volume group "VolGroup00"
Found volume group "VolGroup00"
Loading VolGroup00-Database_Stage_Orig-real table
Suppressed VolGroup00-Database_Stage_Orig-real identical table reload.
Loading VolGroup00-Database_Stage_Orig table
Suppressed VolGroup00-Database_Stage_Orig identical table reload.
Loading VolGroup00-Database_Stage_31743-cow table
Suppressed VolGroup00-Database_Stage_31743-cow identical table reload.
Loading VolGroup00-Database_Stage_31743 table
Suppressed VolGroup00-Database_Stage_31743 identical table reload.
Loading VolGroup00-Database_Stage_32781-cow table
Suppressed VolGroup00-Database_Stage_32781-cow identical table reload.
Loading VolGroup00-Database_Stage_32781 table
Suppressed VolGroup00-Database_Stage_32781 identical table reload.
Loading VolGroup00-Database_Stage_34352-cow table
Suppressed VolGroup00-Database_Stage_34352-cow identical table reload.
Loading VolGroup00-Database_Stage_34352 table
Suppressed VolGroup00-Database_Stage_34352 identical table reload.
Creating VolGroup00-Database_Stage_35780-cow
Loading VolGroup00-Database_Stage_35780-cow table
Resuming  (254:42)
Creating VolGroup00-Database_Stage_35780
Loading VolGroup00-Database_Stage_35780 table
Suspending VolGroup00-Database_Stage_Orig (254:9) with filesystem sync.
Suspending VolGroup00-Database_Stage_31743 (254:33) with filesystem sync.
Suspending VolGroup00-Database_Stage_32781 (254:35) with filesystem sync.
Suspending VolGroup00-Database_Stage_34352 (254:41) with filesystem sync.
Suspending VolGroup00-Database_Stage_Orig-real (254:31) with filesystem 
sync.
Suspending VolGroup00-Database_Stage_31743-cow (254:32) with filesystem 
sync.
Suspending VolGroup00-Database_Stage_Orig-real (254:31) with filesystem 
sync.
Suspending VolGroup00-Database_Stage_32781-cow (254:34) with filesystem 
sync.
Suspending VolGroup00-Database_Stage_Orig-real (254:31) with filesystem 
sync.
Suspending VolGroup00-Database_Stage_34352-cow (254:40) with filesystem 
sync.
Suspending VolGroup00-Database_Stage_Orig-real (254:31) with filesystem 
sync.
Found volume group "VolGroup00"
Loading VolGroup00-Database_Stage_Orig-real table
Suppressed VolGroup00-Database_Stage_Orig-real identical table reload.
Resuming VolGroup00-Database_Stage_Orig-real (254:31)
Loading VolGroup00-Database_Stage_Orig table
Suppressed VolGroup00-Database_Stage_Orig id

[Bug 84821] Re: "attempt to access beyond end of device" when creating LVM snapshot

[A. Karl Kornel]

Here's a control example, showing the output of lvcreate when there are
no problems reported:

[EMAIL PROTECTED]:/home/bugzilla/stage$ dmesg|tail
[17180786.72] EXT3-fs: mounted filesystem with ordered data mode.
[17180799.652000] kjournald starting.  Commit interval 5 seconds
[17180799.656000] EXT3 FS on dm-41, internal journal
[17180799.656000] EXT3-fs: recovery complete.
[17180799.656000] EXT3-fs: mounted filesystem with ordered data mode.
[17203415.252000] ibm_acpi: ec object not found
[17808026.704000] ibm_acpi: ec object not found
[18412815.972000] ibm_acpi: ec object not found
[19017364.116000] ibm_acpi: ec object not found
[19622027.484000] ibm_acpi: ec object not found
[EMAIL PROTECTED]:/home/bugzilla/stage$ cd /var/lib/mysql/main
[EMAIL PROTECTED]:/var/lib/mysql/main$ sudo lvs
  LV  VG Attr   LSize  Origin Snap%  Move Log Copy%
  Database_Logs   VolGroup00 -wi-ao 10.00G
  Database_Main   VolGroup00 -wi-ao  5.00G
  Database_Stage_Orig VolGroup00 -wi-ao 35.00G
  Database_Transition VolGroup00 -wi-ao 80.00G
  HomeVolGroup00 -wi-a-  3.00G
  LiveVolGroup00 -wi-ao 94.00G
  RootVolGroup00 -wi-a- 10.00G
  Stage_Orig  VolGroup00 -wi-ao 76.00G
  SwapVolGroup00 -wi-ao  2.00G
  rootVolGroup00 -wi-ao 15.00G
[EMAIL PROTECTED]:/var/lib/mysql/main$ sudo lvcreate --verbose --snapshot 
--size 5G --name Stage_31743 VolGroup00/Stage_Orig
Setting chunksize to 16 sectors.
Finding volume group "VolGroup00"
Archiving volume group "VolGroup00" metadata (seqno 473).
Creating logical volume Stage_31743
Creating volume group backup "/etc/lvm/backup/VolGroup00" (seqno 474).
Found volume group "VolGroup00"
Creating VolGroup00-Stage_31743
Loading VolGroup00-Stage_31743 table
Resuming VolGroup00-Stage_31743 (254:4)
Zeroing start of logical volume "Stage_31743"
Found volume group "VolGroup00"
Removing VolGroup00-Stage_31743 (254:4)
Found volume group "VolGroup00"
Found volume group "VolGroup00"
Found volume group "VolGroup00"
Creating VolGroup00-Stage_Orig-real
Loading VolGroup00-Stage_Orig-real table
Resuming  (254:4)
Loading VolGroup00-Stage_Orig table
Creating VolGroup00-Stage_31743-cow
Loading VolGroup00-Stage_31743-cow table
Resuming  (254:8)
Creating VolGroup00-Stage_31743
Loading VolGroup00-Stage_31743 table
Suspending VolGroup00-Stage_Orig (254:5)
Suspending VolGroup00-Stage_Orig-real (254:4)
Found volume group "VolGroup00"
Loading VolGroup00-Stage_Orig-real table
Suppressed VolGroup00-Stage_Orig-real identical table reload.
Resuming VolGroup00-Stage_Orig-real (254:4)
Loading VolGroup00-Stage_31743-cow table
Suppressed VolGroup00-Stage_31743-cow identical table reload.
Resuming VolGroup00-Stage_31743 (254:30)
Resuming VolGroup00-Stage_Orig (254:5)
Creating volume group backup "/etc/lvm/backup/VolGroup00" (seqno 475).
  Logical volume "Stage_31743" created
[EMAIL PROTECTED]:/var/lib/mysql/main$ dmesg|tail
[17180786.72] EXT3-fs: mounted filesystem with ordered data mode.
[17180799.652000] kjournald starting.  Commit interval 5 seconds
[17180799.656000] EXT3 FS on dm-41, internal journal
[17180799.656000] EXT3-fs: recovery complete.
[17180799.656000] EXT3-fs: mounted filesystem with ordered data mode.
[17203415.252000] ibm_acpi: ec object not found
[17808026.704000] ibm_acpi: ec object not found
[18412815.972000] ibm_acpi: ec object not found
[19017364.116000] ibm_acpi: ec object not found
[19622027.484000] ibm_acpi: ec object not found
[EMAIL PROTECTED]:/var/lib/mysql/main$ sudo lvs
  LV  VG Attr   LSize  Origin Snap%  Move Log Copy%
  Database_Logs   VolGroup00 -wi-ao 10.00G
  Database_Main   VolGroup00 -wi-ao  5.00G
  Database_Stage_Orig VolGroup00 -wi-ao 35.00G
  Database_Transition VolGroup00 -wi-ao 80.00G
  HomeVolGroup00 -wi-a-  3.00G
  LiveVolGroup00 -wi-ao 94.00G
  RootVolGroup00 -wi-a- 10.00G
  Stage_31743 VolGroup00 swi-a-  5.00G Stage_Orig   0.00
  Stage_Orig  VolGroup00 owi-ao 76.00G
  SwapVolGroup00 -wi-ao  2.00G
  rootVolGroup00 -wi-ao 15.00G
[EMAIL PROTECTED]:/var/lib/mysql/main$

-- 
"attempt to access beyond end of device" when creating LVM snapshot
https://bugs.launchpad.net/bugs/84821
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 84821] Re: "attempt to access beyond end of device" when creating LVM snapshot

[A. Karl Kornel]

Hello!  I don't know if this helps, but I'm experiencing the same
problem, with ext3 filesystems.

I'm running the latest version of Dapper.  That is, if I run `apt-get
update` and then `apt-get upgrade`, I do not see any packages listed.

`uname -a` returns "Linux npbbz 2.6.15-29-686 #1 SMP PREEMPT Mon Sep 24 
17:24:47 UTC 2007 i686 GNU/Linux".
The file at '/proc/version' contains "Linux version 2.6.15-29-686 ([EMAIL 
PROTECTED]) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 SMP PREEMPT Mon Sep 
24 17:24:47 UTC 2007".
The file at '/proc/cmdline' contains "root=/dev/mapper/VolGroup00-root ro".

The file at '/proc/cpuinfo' contains:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 15
model   : 2
model name  : Intel(R) Xeon(TM) MP CPU 2.70GHz
stepping: 8
cpu MHz : 2694.761
cache size  : 2048 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr
bogomips: 5403.05

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 15
model   : 2
model name  : Intel(R) Xeon(TM) MP CPU 2.70GHz
stepping: 8
cpu MHz : 2694.761
cache size  : 2048 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr
bogomips: 5392.65


Package versions are:
  - linux-image-2.6.15-29-686: 2.6.15-29.60
  - libc6: 2.3.6-0ubuntu20.5
  - libdevmapper1.02: 1.02.05-1ubuntu1
  - dmsetup: 1.02.05-1ubuntu1
  - lvm-common: 1.5.20ubuntu4
  - lvm2: 2.02.02-1ubuntu1.5

I'll post my dmesg output soon!

-- 
"attempt to access beyond end of device" when creating LVM snapshot
https://bugs.launchpad.net/bugs/84821
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 131714] Re: glibc corrupted double-linked list error when updatedb runs

[A. Karl Kornel]

Got three more:

2007-08-16 08:00:26:
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08055988 ***
/etc/cron.daily/slocate: line 12: 20647 Aborted 
/usr/bin/updatedb

2007-08-17 08:00:47:
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08055988 ***
/etc/cron.daily/slocate: line 12: 13568 Aborted 
/usr/bin/updatedb

2007-08-21 08:00:53:
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08055988 ***
/etc/cron.daily/slocate: line 12: 16413 Aborted 
/usr/bin/updatedb

-- 
glibc corrupted double-linked list error when updatedb runs
https://bugs.launchpad.net/bugs/131714
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 131737] Re: network device (nVidia MCP55, forcedeth) stops sending packets

[A. Karl Kornel]

As a stopgap measure, I've installed an Intel PRO/1000 dual-port PCI
Express card, giving me two Ethernet ports to supplant the ones that are
malfunctioning.

-- 
network device (nVidia MCP55, forcedeth) stops sending packets
https://bugs.launchpad.net/bugs/131737
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 131737] Re: network device (nVidia MCP55, forcedeth) stops sending packets

[A. Karl Kornel]

Update:  I've had the problem reappear two more times in the last 4
hours.  The first time, I was `apt-get`ing about 50 packages; the
network link (eth1) died partway through the download.  The second time,
I wasn't transferring much data, but I did have lots of connections open
to various places.

When the network links did fail (again, eth0 and eth1 failed at the same
time), eth1 recorded a number of error packets (36) immediately.
Shortly afterwards, both eth0 and eth1 started racking up dropped
packets until I shut the machine down.  Five minutes of the power cord
out, and it was good to go again!

-- 
network device (nVidia MCP55, forcedeth) stops sending packets
https://bugs.launchpad.net/bugs/131737
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 131737] Re: network device (nVidia MCP55, forcedeth) stops sending packets

[A. Karl Kornel]

BTW, I've got an identical Sun Fire X2200 M2, which is not showing this
problem.  At least, I think they're identical:  I purchased them and
configured them at exactly the same time.  As they are the members of a
two-node cluster, I've always kept their configurations essentially
identical.

-- 
network device (nVidia MCP55, forcedeth) stops sending packets
https://bugs.launchpad.net/bugs/131737
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 131737] network device (nVidia MCP55, forcedeth) stops sending packets

[A. Karl Kornel]

Public bug reported:

Binary package hint: linux-source-2.6.15

The Sun Fire X2200 M2 (BIOS version S39_3B16, running Dapper and kernel
2.6.15-28-amd64-generic) has four built-in network interfaces.  Two
network interfaces (eth0 and eth1) are nVidia MCP55 devices, and two
(eth2 and eth3) are Broadcom devices.  eth0 and eth1 are connected to
Cisco switches, each on a different VLAN (although the interfaces don't
know that, as VLAN tagging is not in use).  eth3 is unused by the OS (it
is active as the interface to the remote access system), and eth2 is
directly connected to another machine (via crossover cable).  eth1 is
the primary interface, where most of the traffic flows.

eth0 and eth1 have been working well until a few weeks ago, when their
network connections were moved.  They originally started out connected
to gigabit ports on a blade of a Cisco switch.  The problem began when
they were moved to a 10/100 blade on the same switch.  The switch ports
are hard-coded to 100MBps full-duplex, but the `ethtool` command reports
that the network interface is running at 100Mbps half-duplex.  Also,
during certain circumstances, eth0 and eth1 can stop functioning.  When
eth0 and eth1 stop working, no outgoing traffic is actually sent, and
incoming traffic can only be received on eth1.  The problem always
affects both interfaces at the same time, never just eth0 or eth1,
always both eth0 and eth1.  I have not experienced any problems (so far)
with eth2 and eth3 (although the OS doesn't use eth3).

I have found two ways at present to trigger the problem.  The first
method is to flood the interface with a large amount of data.  For
example, downloading many large files at once will eventually expose the
problem.  Most recently, the problem appeared during a reinstallation of
Ubuntu:  I had installed the OS from DVD, and was in the process of
upgrading/installing about 100 packages.

Another method is to attempt to change the network configuration.  The
network devices, as I said, seem to run at 100MBps half-duplex, even
though the switch ports are set to run at 100MBps full-duplex.  If I run
the command `ethtool -s eth1 autoneg off speed 100 duplex full` to force
the interface to 100MBps full-duplex, the connection on eth1 is lost.
Restarting autonegotiation does nothing.

This problem was noticed several weeks ago, when the machine's network
connections were switched from gigabit ports to 10/100 ports on the
Cisco switch.  The diagnosis was temporarily delayed by a hard drive
failure (see Sun Online Support Center SR#65605769).

In an attempt to fix the problem, thinking that the Cisco blade may be
at fault, I have had the malfunctioning network interfaces moved to a
different 10/100 blade on our Cisco switch.  The problem is still
present after the move; the network devices show the same problems
regardless of which 10/100 blade they are on.  Unfortunately, all the
gigabit ports have been taken since the move, so I am unable to move
eth0 and eth1 back to gigabit ports to see if this fixes the problem.

To get the network interfaces working agin, besides moving network
connections, I have tried four different things.  First, I tried
executing the command `/etc/init.d/networking restart`, which is
supposed to deactivate and then reactivate the network devices, but that
didn't work.  I then tried executing the commands
`/etc/init.d/networking stop`, `rmmod forcedeth`, `modprobe forcedeth`,
and `/etc/init.d/networking start`.  The commands should deactivate the
network devices, unload and then reload the driver for eth0 and eth1,
and then restart networking.  This also didn't work.  I eventually just
tried shutting down the machine (using the command `shutdown -h now`)
and restarting it, but that also did not work!  Eventually, the only way
to get eth0 and eth1 working again was to shut down the system and
actually unplug it for approximately five minutes.  That fixed the
problem temporarily.

Examining the /var/log/messages file, which records pretty much
everything reported to syslog, I found a number of messages relating to
eth0 and eth1:

[Boot time]
Aug  8 15:15:12 npbnagb kernel: [   54.426790] forcedeth.c: Reverse Engineered 
nForce ethernet driver. Version 0.54.
Aug  8 15:15:12 npbnagb kernel: [   54.686201] forcedeth: using HIGHDMA
Aug  8 15:15:12 npbnagb kernel: [   55.204363] eth0: forcedeth.c: subsystem: 
0108e:534b bound to :00:08.0
Aug  8 15:15:12 npbnagb kernel: [   55.204811] forcedeth: using HIGHDMA
Aug  8 15:15:12 npbnagb kernel: [   55.723467] eth1: forcedeth.c: subsystem: 
0108e:534b bound to :00:09.0

[When both network devices stop working]
Aug  8 16:42:24 npbnagb kernel: [ 5307.159987] NETDEV WATCHDOG: eth0: transmit 
timed out
Aug  8 16:42:24 npbnagb kernel: [ 5307.159992] eth0: Got tx_timeout. irq: 

Aug  8 16:42:24 npbnagb kernel: [ 5307.159995] eth0: Ring at 7e30: next 
2090 nic 1834
Aug  8 16:42:24 npbnagb kernel: [ 5307.159997] eth0: Dumping tx registers
Aug  8 16:42:2

[Bug 131737] Re: network device (nVidia MCP55, forcedeth) stops sending packets

[A. Karl Kornel]

FYI, I also opened an SR with Sun.  It's Sun Online Support Center
SR#65611163.  I'll relay reports as appropriate!

-- 
network device (nVidia MCP55, forcedeth) stops sending packets
https://bugs.launchpad.net/bugs/131737
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 131713] glibc double free or corruption error when updatedb runs

[A. Karl Kornel]

Public bug reported:

Binary package hint: slocate

Since installing Ubuntu 6.06 LTS at the end of March, which included
slocate, there have been 8 cases of "double free or corruption" errors
being reported when `updatedb` runs as part of the cron.daily set of
jobs.

The system has a fairly large number (5-20, from then to now) of local
filesystems (LVM), and one NFS-mounted filesystem.

Here are the dates & times of the errors, along with the error messages:

2007-03-05 08:00:52
/etc/cron.daily/slocate:
*** glibc detected *** double free or corruption (!prev): 0x080553c0 ***
/etc/cron.daily/slocate: line 12: 32023 Aborted 
/usr/bin/updatedb

2007-04-07 08:00:53
/etc/cron.daily/slocate:
*** glibc detected *** double free or corruption (!prev): 0x080564c0 ***
/etc/cron.daily/slocate: line 12: 26736 Aborted 
/usr/bin/updatedb

2007-04-14 08:00:51
/etc/cron.daily/slocate:
*** glibc detected *** double free or corruption (!prev): 0x08052d68 ***
/etc/cron.daily/slocate: line 12: 12349 Aborted 
/usr/bin/updatedb

2007-04-15 08:00:58
/etc/cron.daily/slocate:
*** glibc detected *** double free or corruption (!prev): 0x08052dc0 ***
/etc/cron.daily/slocate: line 12: 32688 Aborted 
/usr/bin/updatedb

2007-04-21 08:00:58
/etc/cron.daily/slocate:
*** glibc detected *** double free or corruption (!prev): 0x08055bc0 ***
/etc/cron.daily/slocate: line 12: 20379 Aborted 
/usr/bin/updatedb

2007-04-23 08:00:40
/etc/cron.daily/slocate:
*** glibc detected *** double free or corruption (!prev): 0x08052fd8 ***
/etc/cron.daily/slocate: line 12: 23704 Aborted 
/usr/bin/updatedb

2007-05-14 08:00:38
/etc/cron.daily/slocate:
*** glibc detected *** double free or corruption (!prev): 0x08052fd8 ***
/etc/cron.daily/slocate: line 12: 24606 Aborted 
/usr/bin/updatedb

2007-08-02 08:00:50
/etc/cron.daily/slocate:
*** glibc detected *** double free or corruption (!prev): 0x08055b90 ***
/etc/cron.daily/slocate: line 12:  7392 Aborted 
/usr/bin/updatedb

** Affects: slocate (Ubuntu)
 Importance: Undecided
 Status: New

-- 
glibc double free or corruption error when updatedb runs
https://bugs.launchpad.net/bugs/131713
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 131714] glibc corrupted double-linked list error when updatedb runs

[A. Karl Kornel]

Public bug reported:

Binary package hint: slocate

Since installing Ubuntu 6.06 LTS at the end of March, which included
slocate, there have been 15 cases of "corrupted double-linked list"
errors being reported when `updatedb` runs as part of the cron.daily set
of jobs.

The system has a fairly large number (5-20, from then to now) of local
filesystems (LVM), and one NFS-mounted filesystem.

Here are the dates & times of the errors, along with the error messages:

2007-04-08 08:01:15
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08056b40 ***
/etc/cron.daily/slocate: line 12: 14847 Aborted 
/usr/bin/updatedb

2007-04-17 08:00:45
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08052e50 ***
/etc/cron.daily/slocate: line 12:  7977 Aborted 
/usr/bin/updatedb

2007-04-24 08:01:14
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08057108 ***
/etc/cron.daily/slocate: line 12:  9219 Aborted 
/usr/bin/updatedb

2007-04-25 08:00:37
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08055ab0 ***
/etc/cron.daily/slocate: line 12: 27003 Aborted 
/usr/bin/updatedb

2007-04-27 08:00:58
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08055b30 ***
/etc/cron.daily/slocate: line 12: 30888 Aborted 
/usr/bin/updatedb

2007-04-28 08:01:00
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08056e48 ***
/etc/cron.daily/slocate: line 12: 16425 Aborted 
/usr/bin/updatedb

2007-04-30 08:00:33
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08055ab0 ***
/etc/cron.daily/slocate: line 12: 20467 Aborted 
/usr/bin/updatedb

2007-05-03 08:01:04
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08057478 ***
/etc/cron.daily/slocate: line 12: 12802 Aborted 
/usr/bin/updatedb

2007-05-06 08:00:56
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08056ce0 ***
/etc/cron.daily/slocate: line 12:  2645 Aborted 
/usr/bin/updatedb

2007-05-15 08:00:56
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08052e50 ***
/etc/cron.daily/slocate: line 12: 11283 Aborted 
/usr/bin/updatedb

2007-05-20 08:01:03
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08057338 ***
/etc/cron.daily/slocate: line 12: 26360 Aborted 
/usr/bin/updatedb

2007-05-21 08:01:05
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08057478 ***
/etc/cron.daily/slocate: line 12: 15706 Aborted 
/usr/bin/updatedb

2007-05-27 08:00:56
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08056e48 ***
/etc/cron.daily/slocate: line 12: 29431 Aborted 
/usr/bin/updatedb

2007-06-03 08:00:54
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x080573f0 ***
/etc/cron.daily/slocate: line 12:  8564 Aborted 
/usr/bin/updatedb

2007-06-08 08:00:51
/etc/cron.daily/slocate:
*** glibc detected *** corrupted double-linked list: 0x08055f48 ***
/etc/cron.daily/slocate: line 12: 20049 Aborted 
/usr/bin/updatedb

** Affects: slocate (Ubuntu)
 Importance: Undecided
 Status: New

-- 
glibc corrupted double-linked list error when updatedb runs
https://bugs.launchpad.net/bugs/131714
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 25093] Applying fix to Dapper?

[A. Karl Kornel]

It appears, from bug 57972, that this bug also affects Dapper.  I was
preparing to set up a server where several 500GB disks are made into a
2TB RAID array, so I'm guessing that this is going to affect me.  I'm
using Dapper for the longer-term support.  Is it possible to get this
fix applied to Dapper?

-- 
mdrun is generating a bad eval statement
https://launchpad.net/bugs/25093

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 80364] AssertionError when cancelling invite

[A. Karl Kornel]

Public bug reported:

Binary package hint: mailman

I invited a user to join a mailing list that I recently created.  The
user went to the URL in the invitation email, and was prompted to enter
their name (entered), use or not use digests (not used), select a
language (English (USA)), and either cancel the request or subscribe.
The user chose to cancel, and was told that "we hit a bug!"

I tried to reproduce this error on another list, and was successful.  By
the way, the user was still able to accept the invitation, even after
trying to cancel it.

I have the bug information, from the error logs, here:

admin(12492): [- Mailman Version: 2.1.5 -]
admin(12492): [- Traceback --]
admin(12492): Traceback (most recent call last):
admin(12492):   File "/var/lib/mailman/scripts/driver", line 110, in run_main
admin(12492): main()
admin(12492):   File "/usr/lib/mailman/Mailman/Cgi/confirm.py", line 114, in 
main
admin(12492): subscription_cancel(mlist, doc, cookie)
admin(12492):   File "/usr/lib/mailman/Mailman/Cgi/confirm.py", line 312, in 
subscription_cancel
admin(12492): userdesc = mlist.pend_confirm(cookie)[1]
admin(12492):   File "/usr/lib/mailman/Mailman/Pending.py", line 141, in 
pend_confirm
admin(12492): assert self.Locked()
admin(12492): AssertionError
admin(12492): [- Python Information -]
admin(12492): sys.version =   2.4.3 (#2, Oct  6 2006, 07:52:30)
[GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5)]
admin(12492): sys.executable  =   /usr/bin/python
admin(12492): sys.prefix  =   /usr
admin(12492): sys.exec_prefix =   /usr
admin(12492): sys.path=   /usr
admin(12492): sys.platform=   linux2
admin(12492): [- Environment Variables -]
admin(12492):   force_response_1_0: 1
admin(12492):   HTTP_REFERER: 
https://npbrepo.inet.mindspeed.local/mailman/confirm/nagios_config/d2ee4634c12e10b86dd32a64e85457e170bacee8
admin(12492):   SERVER_SOFTWARE: Apache/2.0.55 (Ubuntu) DAV/2 SVN/1.3.1 
PHP/5.1.2 mod_ssl/2.0.55 OpenSSL/0.9.8a mod_perl/2.0.2 Perl/v5.8.7
admin(12492):   SCRIPT_NAME: /mailman/confirm
admin(12492):   SERVER_SIGNATURE: Apache/2.0.55 (Ubuntu) DAV/2 
SVN/1.3.1 PHP/5.1.2 mod_ssl/2.0.55 OpenSSL/0.9.8a mod_perl/2.0.2 Perl/v5.8.7 
Server at npbrepo.inet.mindspeed.local Port 443
admin(12492):
admin(12492):   REQUEST_METHOD: POST
admin(12492):   PATH_INFO: /nagios_config
admin(12492):   SERVER_PROTOCOL: HTTP/1.1
admin(12492):   QUERY_STRING:
admin(12492):   CONTENT_LENGTH: 131
admin(12492):   HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 
5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
admin(12492):   HTTP_CONNECTION: Keep-Alive
admin(12492):   SERVER_NAME: npbrepo.inet.mindspeed.local
admin(12492):   REMOTE_ADDR: 10.1.49.145
admin(12492):   PATH_TRANSLATED: /repoweb/nagios_config
admin(12492):   SERVER_PORT: 443
admin(12492):   SERVER_ADDR: 10.1.16.68
admin(12492):   DOCUMENT_ROOT: /repoweb
admin(12492):   PYTHONPATH: /var/lib/mailman
admin(12492):   SCRIPT_FILENAME: /var/lib/mailman/cgi-bin/confirm
admin(12492):   SERVER_ADMIN: [EMAIL PROTECTED]
admin(12492):   HTTP_HOST: npbrepo.inet.mindspeed.local
admin(12492):   HTTPS: on
admin(12492):   HTTP_UA_CPU: x86
admin(12492):   HTTP_CACHE_CONTROL: no-cache
admin(12492):   REQUEST_URI: /mailman/confirm/nagios_config
admin(12492):   HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, 
image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, 
application/vnd.ms-powerpoint, application/msword, */*
admin(12492):   nokeepalive: 1
admin(12492):   GATEWAY_INTERFACE: CGI/1.1
admin(12492):   REMOTE_PORT: 4801
admin(12492):   HTTP_ACCEPT_LANGUAGE: en-us
admin(12492):   downgrade_1_0: 1
admin(12492):   ssl_unclean_shutdown: 1
admin(12492):   CONTENT_TYPE: application/x-www-form-urlencoded
admin(12492):   HTTP_ACCEPT_ENCODING: gzip, deflate

** Affects: mailman (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
AssertionError when cancelling invite
https://launchpad.net/bugs/80364

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 67868] Watchdog intermittently returns "Host Unreachable" errors on should-be-OK pings

[A. Karl Kornel]

Public bug reported:

I have watchdog configured to ping 10.1.16.1 (the gateway address), and
to check for traffic on eth0.  I have the watchdog init script set to
run watchdog with the '-q' and '-v' switches, so I can see what's going
on without my machine being forcibly restarted.

Anywhere from %30 to %50 of the time, watchdog's pings come back as
"Host unreachable".  Howevever, this information seems to be inaccurate:
If I run the `ping` command in a separate window, I can see 0% packet
loss on pings to 10.1.16.1, even while watchdog is reporting problems.

** Affects: watchdog (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed
** Affects: watchdog (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #32547
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=32547

** Also affects: watchdog (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=32547
   Importance: Unknown
   Status: Unknown

-- 
Watchdog intermittently returns "Host Unreachable" errors on should-be-OK pings
https://launchpad.net/bugs/67868

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 67853] Watchdog sees self-generated ICMP packets as good ping results

[A. Karl Kornel]

Public bug reported:

Binary package hint: watchdog

I just installed the 'watchdog' package to monitor & shutdown my system
if any one of the following takes place:

a) No traffic comes in on eth0
b) 10.1.16.85 (the machine's IP) doesn't respond to pings
c) 10.1.16.1 (the subnet's router) doesn't respond to pings

To test it, I modified the init script, changing $watchdog_options from
"" (empty string) to "-q -v", so I can watch /var/log/syslog to see
what's going on.  Every 15 seconds, I get the messages "device eth0
received  bytes", "got answer from target 10.1.16.85", and "got
answer from 10.1.16.1"; everything looked OK.

The actual test came when I unplugged the network cable and waited.  The
first message changed to "device eth0 did not receive anything since
last check", which I expected.  However, watchdog continued to say "got
answer from target {10.1.16.85, 10.1.16.1}", even though the network
cable was disconnected.

Anyway, I tried pinging both 10.1.16.85 and 10.1.16.1.  10.1.16.85
responded to pings, but 10.1.16.1 kept on coming back with the ICMP
message "Destination Host Unreachable".  I had expected watchdog to
differentiate between an ICMP error and an actual ping.

Another piece of interesting information:  In watchdog.conf, I had three
lines:

ping = 10.1.16.85
ping = 10.1.16.1
interface = eth0

When I commented out the first line, and restarted watchdog, it started
to recognize the host unreachable message as what it was; when I removed
the '-q' from the watchdog options, and restarted watchdog, the system
was restarted (as expected).

** Affects: watchdog (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
Watchdog sees self-generated ICMP packets as good ping results
https://launchpad.net/bugs/67853

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs