headers
martin f krafft | 5 Dec 15:54
Favicon
Gravatar

Bug#506419: kernel trace during IPv6 ssh output

also sprach martin f krafft <madduck <at> debian.org> [2008.12.04.1551 +0100]:
> I cannot reproduce the same bug anymore, which may be due to the
> fact that I am using a proto-41 IPv6 tunnel at the new location
> (and thus lower transmission rates).

I can reproduce it now that the machine is back in a native IPV6
network.

> So the bug is kinda horrid: the NIC that provides eth0 also
> connects to the IPMI card, and when I cause a whole lot of IPv6
> traffic (incoming, e.g. downloading ISOs from switch.ch via IPv6),
> the NIC locks up to the point where the IPMI card also becomes
> unreachable. A soft-reboot fixes the problem. There is nothing in
> the logs.

Of course I can no longer reproduce this one at home, even with
a proto-41 tunnel to my gateway, and bridging and iptables.

JOY!

--

-- 
 .''`.   martin f. krafft <madduck <at> debian.org>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems
Permalink | Reply | 0 comments |
headers
Ivan Savcic | 4 Dec 14:02

Bug#507785: xen-linux-system: Xen domU clock frozen on dom0 boot

Package: xen-linux-system-2.6.26-1-xen-686
Version: 2.6.26-10
Severity: important
File: xen-linux-system

When dom0 boots up, all restored domUs (2 x etch and 1 x lenny) have their clocks set to the time when they were
restored and their 
clocks are "frozen" in that time, with following error appearing in all domUs' dmesg:

clocksource/0: Time went backwards: ret=b01d2985eb delta=-929476120446 shadow=b00552031d offset=17d7f610

(ret, delta, shadow and offset vary over time)

"xm destroy domU && xm create domU.cfg" seems to fix the problem, but only until I reboot/shutdown dom0 again.

Manual "/etc/init.d/xendomains restart" doesn't fix the problem, but it doesn't reintroduce it either
once the domUs have been manually 
recreated with xm destroy/create.

This happens on every dom0 boot.

domU.cfg (Created with xen-tools, other domUs have pretty much similar config. "virtual" is the name of
LVM VG.):

kernel      = '/boot/vmlinuz-2.6.26-1-xen-686'
ramdisk     = '/boot/initrd.img-2.6.26-1-xen-686'
memory      = '256'
root        = '/dev/sda2 ro'
disk        = [ 'phy:virtual/vm2-swap,sda1,w', 'phy:virtual/vm2-root,sda2,w', ]
name        = 'domU'
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jayen Ashar | 4 Dec 02:36

packaging e1000e from intel

Hi,

I've found that the e1000e driver isn't up-to-date for some new hardware 
our school has received.  I'm trying to package it [properly], but I'm 
having trouble finding instructions on packaging a kernel module.  If 
someone could look at what I tried (below) and tell me what I'm doing 
wrong, that would be appreciated.  Thanks.

* lspci to find hardware id (0x10de)
* google search to find hardware name (intel 82567LM-3)
* intel download search to find driver
* 
http://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/15817/eng/e1000e-0.5.8.2.tar.gz&agr=&ProductID=3003&DwnldId=15817&strOSs=&OSFullName=&lang=eng
  tar -zxvf e1000e-0.5.8.2.tar.gz
  cd e1000e-0.5.8.2/
  cat > Makefile << end
  default:
  	$(MAKE) -C src default
  install:
  	$(MAKE) -C src install
  end
  dh_make -e jayen <at> science.unsw.edu.au -f ../e1000e-0.5.8.2.tar.gz -s -p 
e1000e
  sed -i s/INSTALL_MOD_PATH/DESTDIR/ src/Makefile
  fakeroot debian/rules binary

  sudo dpkg --force-overwrite -i e1000e_0.5.8.2-1_i386.deb

The main thing I'm uncomfortable with is the --force-overwrite, but I'm 
also worried I'm using -s (single binary) instead of -k (kernel module)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Moritz Muehlenhoff | 3 Dec 23:40
Favicon

Bug#506964: linux-image-2.6.26-1-686: radeonfb suspend/resume for Acer Travelmate 29X

On Wed, Nov 26, 2008 at 03:00:56PM +0100, Wolfgang Kroener wrote:
> Package: linux-image-2.6.26-1-686
> Version: 2.6.26-10
> Severity: normal
> Tags: patch
> 
> Hi,
> I have a ATI Mobility Radeon RV350 and similar problems with radeonfb
> described in http://kernel.org/doc/Documentation/power/s2ram.txt
> Adding the device to radeon_workaround_list solves the Problem.
> 
> I wrote a patch, sent it to the lkml and got a positive response, but
> the patch wasn't merged.
> Please see the thread with the (trivial) patch at
> http://lkml.org/lkml/2008/9/30/203

If you haven't received a reply from upstream, please resend and keep
the maintainer and the specific development list in CC, it's probably
been overseen in the enourmous amount of l-k traffic: 
Benjamin Herrenschmidt <benh <at> kernel.crashing.org> and
linux-fbdev-devel <at> lists.sourceforge.net

Also, please add a Signed-off-by: line as described in
Documentation/SubmittingPatches

Cheers,
        Moritz
Permalink | Reply | 0 comments |
headers
salonh | 3 Dec 21:28

Bug#507712: Followup-For: Bug #502375- seem to be a problem with version notation change


Package: virtualbox-ose-modules-2.6.26-1-686
Version: 1.6.6-dfsg-3+2.6.26-10

*** Please type your report below this line ***
version notation changed from  2.6.26+1.6.2-dfsg-4 to 1.6.6-dfsg-3+2.6.26-10
apparantly causing update-manager to consider the former as latest.
solved locally by locking version in synaptic after doing the proposed a-i.
should be fixed by reformatting version number of new (or old) package

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages virtualbox-ose-modules-2.6.26-1-686 depends on:
ii  linux-image-2.6.26-1-686 [lin 2.6.26-10  Linux 2.6.26 image on PPro/Celeron

Versions of packages virtualbox-ose-modules-2.6.26-1-686 recommends:
ii  virtualbox-ose              1.6.6-dfsg-3 x86 virtualization solution - bina

virtualbox-ose-modules-2.6.26-1-686 suggests no packages.

-- no debconf information
(Continue reading)

Permalink | Reply | 1 comment |
headers
Peter | 3 Dec 21:24
Favicon

Bug#507710: linux-image-2.6.26-1-amd64: CPU overload, Sound server fatal error.

Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-10
Severity: critical
Justification: breaks the whole system

-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (10, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-1-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.24     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92j      tools for generating an initramfs
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo

linux-image-2.6.26-1-amd64 recommends no packages.

Versions of packages linux-image-2.6.26-1-amd64 suggests:
pn  grub | lilo                   <none>     (no description available)
pn  linux-doc-2.6.26              <none>     (no description available)

-- debconf information excluded
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bernhard Kleine | 3 Dec 17:30

Bug#507676: initramfs-tools: does not wait for usb disks in

Am Wed, 03 Dec 2008 16:30:30 +0100 schrieb hugo vanwoerkom:

> Package: initramfs-tools
> Version: 0.92l
> Severity: normal
> 
> Booting linux-image-2.6.26-1-686 initramfs does not wait for the 2 USB
> disks that are in /etc/fstab to show up, causing the boot to fail.

I had a similar problem 2 days ago, one usb partition as /dev/sda1, boot 
stopped with an error, I do not remember but related to a missing device. 
Rebooting solved the problem.

Bernhard
Permalink | Reply | 1 comment |
headers
George B. | 3 Dec 10:45

Bug#387460: linux-image-2.6.17-2-686: kernel panic when trying to add vlan to a slave bonded interface

2008/11/29 Moritz Muehlenhoff <jmm <at> inutil.org>:
> George, did you report that bug upstream?

Hi Mortiz,

I don't think I submitted a bug upstream (I think I may have had some
problems, but I can't remember now). Since then, I've changed jobs
twice, so I no longer have access to that hardware.

I tried reproducing the problem on a Lenny VirtualBox VM, but could
not. Feel free to close this bug - I'll re-open it if I manage to
reproduce it (I should have some spare real servers available for that
in our lab at some point in future).

Thanks.

George.
Permalink | Reply | 0 comments |
headers
Florian Lohoff | 3 Dec 10:14

Bug#429011: Fwd: + drivers-char-cycladesc-cy_pci_probe-fix-error-path.patch added to -mm tree


Hi,
this fast there was a patch ...

----- Forwarded message from akpm <at> linux-foundation.org -----

Subject: + drivers-char-cycladesc-cy_pci_probe-fix-error-path.patch added to -mm tree
To: mm-commits <at> vger.kernel.org
Cc: akpm <at> linux-foundation.org, alan <at> lxorguk.ukuu.org.uk, flo <at> rfc822.org,
	jirislaby <at> gmail.com, stable <at> kernel.org
From: akpm <at> linux-foundation.org
Date: Wed, 03 Dec 2008 00:10:54 -0800
X-Spam-Status: No, hits=-2.9 required=5 tests=AWL,BAYES_00
X-Bogosity: Unsure, tests=bogofilter, spamicity=0.500003, version=1.1.3

The patch titled
     drivers/char/cyclades.c: cy_pci_probe(): fix error path
has been added to the -mm tree.  Its filename is
     drivers-char-cycladesc-cy_pci_probe-fix-error-path.patch

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
(Continue reading)

Permalink | Reply | 0 comments |
headers
Debian Bug Tracking System | 3 Dec 09:03

Bug#507629: marked as done (linux-image-2.6.26-1-686: kernel & gcc incompatible: vmware install headache)


Your message dated Wed, 3 Dec 2008 08:59:18 +0100
with message-id <20081203075918.GA24409 <at> wavehammer.waldi.eu.org>
and subject line Re: Bug#507629: linux-image-2.6.26-1-686: kernel & gcc incompatible: vmware install headache
has caused the Debian Bug report #507629,
regarding linux-image-2.6.26-1-686: kernel & gcc incompatible: vmware install headache
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner <at> bugs.debian.org
immediately.)

--

-- 
507629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507629
Debian Bug Tracking System
Contact owner <at> bugs.debian.org with problems
From: clayton <ckoeni <at> gmail.com>
Subject: linux-image-2.6.26-1-686: kernel & gcc incompatible: vmware install headache
Date: 2008-12-03 04:35:05 GMT
(Continue reading)






Permalink
| Reply
| 0 comments  
| 



  

  

  





headers


Jindřich Vrba
 | 
2 Dec 19:44





Bug#506799: linux-image-2.6-amd64: deadlock when removing qdisc on multiprocessor systems


Hello Moritz,

I can confirm in Linux kernel 2.6.24 from Debian stable is everything 
working fine.

Thanks for help! Cheers,
Jindrich Vrba







Permalink
| Reply
| 0 comments  
| 



  

  

  

  


  





    



Gmane