Possible Workaround for 2.6.x kernels is to blacklist r8169, so r8168 can be
used, see my comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/864750/comments/34
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
see my comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/864750/comments/34
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/784335
Title:
Heavy network utilization with r8169 leads to kerne
AFAIS it is a kernel driver problem.
The NIC is detected as
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 03)
The problem was not present with 2.6.35-32-server (r8169 was used) and
appeared on the system (natty) upon switc
** Also affects: ltsp
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925165
Title:
in ltsp, initramfs-tools/scripts/ltsp_nbd does not respect the
paramet
Public bug reported:
Package: ltsp-server
Version: 5.2.16-0ubuntu7
Maintainer: Stephane Graber
Release: 11.10 (oneiric)
AFAIU, (/opt/ltsp/.../usr/share/) initramfs-tools/scripts/ltsp_nbd
should respect the "nbdserver" parameter -
the relevant part of the function mountroot() should be amended to
I was just thinking that these problems might be due to misconfiguration
or suboptimal configuration of the controller, or even suboptimal
configuration of and/or conflicts with other devices in the system.
So it might be a driver problem, but also a driver problem of some other
device (other cont
** Description changed:
- vmware-checkvm and (at least vmware-toolbox-cmd) do not detect the VM,
+ vmware-checkvm and vmware-toolbox-cmd (at least) do not detect the VM,
running as guest on VMware Server 2.0.2 build 203138
-
# vmware-checkvm
** Message: HOSTINFO: CPUID hypervisor bit is
Public bug reported:
vmware-checkvm and vmware-toolbox-cmd (at least) do not detect the VM,
running as guest on VMware Server 2.0.2 build 203138
# vmware-checkvm
** Message: HOSTINFO: CPUID hypervisor bit is set, but no hypervisor vendor
signature is present
** (process:5549): DEBUG: VmCheck_Is
** Bug watch added: Debian Bug tracker #626752
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626752
** Also affects: lockfile-progs (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626752
Importance: Unknown
Status: Unknown
--
You received this bug notification be
Hiello Clint,
thank you for responding and corrections.
I've just installed the packages using aptitude -
it happens on the (first) run of ntpdate, while starting services.
I've noticed there is some code trying to address this
problem, it seems logical at first sight
I do not see why it is not
** Also affects: upstart
Importance: Undecided
Status: New
** Also affects: dovecot
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/718188
Title:
** Description changed:
Binary package hint: upstart
Due to ntpdate (installed with ubuntu-minimal), the time was corrected
backwards during boot, obviously after starting dovecot, causing
dovecot: Fatal: Time just moved backwards by 90 seconds. This might
cause a lot of problems,
Public bug reported:
Binary package hint: upstart
Due to ntpdate (installed with ubuntu-minimal), the time was corrected
backwards during boot, obviously after starting dovecot, causing
dovecot: Fatal: Time just moved backwards by 90 seconds. This might
cause a lot of problems, so I'll just kill
In the end, it seems that this bug is related to
- HDD problems like unreadable blocks / sectors
- possibly changes in how HDDs act in such situations
- some controllers like the one in AMD SB700
- kernel / libata changes after 2.6.24 (?)
I worry that maybe
- HDD manufacturers are changing the way
Public bug reported:
Binary package hint: libc-bin
Following appears in the system log while using iconv with possibly invalid
characters in the input:
[392035.500277] iconv[3813]: segfault at 0 ip 7f26384aaee4 sp
7a35b1a0 error 4 in libc-2.11.1.so[7f2638442000+17a000]
[392035.52424
It is for sure some sort of kernel bug and/or deficiency, because
- a process should not get blocked for several minutes or more because
of an SCSI/ATA controller or HDD I/O error, no matter what the
controller or HDD does (or doesn't do), it should get I/O error /
timeout
- md RAID other than le
I also had the "ata ... frozen" symptom on system with AMD SB700/SB800 controler
with 2.6.26, 2.6.30 and 2.6.32. Comparing on similar systems, it seems (could
be)
that it occurs more often with distinct hard drives or under distinct
circumstances (?).
You may want to try some of following (step
** Summary changed:
- IOCStatus(0x004b): SCSI IOC Terminated
+ IOCStatus(0x004b): SCSI IOC Terminated, mptscsih task abort
--
IOCStatus(0x004b): SCSI IOC Terminated, mptscsih task abort
https://bugs.launchpad.net/bugs/140032
You received this bug notification because you are a member of Ubuntu
B
Reproduced in Lucid.
Possible workaround: convert vmware disks to IDE.
It could be that it is a kernel driver (mptscsih) problem that affects some
real hardware as well,
(searched for "mptscsih: ioc0: attempting task abort!") -
perhaps the driver times out to soon for specific operations or some
19 matches
Mail list logo
