Bug#401916: Bug #401916 - any progress?

2007-02-23 Thread David Härdeman
maks...any progress on this bug?

A new package which exports ROOTDELAY would be nice, then the rest can be
fixed in udev...

-- 
David Härdeman



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



[patch 00/06] ti_usb, usb-serial: firmware in userspace, new setup/configuration, small cleanup

2007-02-23 Thread Oleg Verych
Thankfully to Al, who have some time to test this, i'm pleased to send
this patch proposition.

Debian. This update eliminates need of udev/sysfs reconfiguration,
thus no udev package patches needed. Firmware files from standard
driver package from TI must be copied or symlinked to /lib/firmware.

Patchset was posted to usb-devel (but not yet appeared) and to
maintainers. Debian's kernel's ready patch set can be sent to you.

Thanks.

,-*- dmesg -*-
|usbcore: registered new driver ti_usb_3410_5052
|/mnt/work/root-fs/usr/src/linux-source-2.6.18/drivers/usb/serial/ti_usb_3410_5052.c:
|TI USB 3410/5052 Serial Driver v0.92
|ti_usb_3410_5052 3-2:1.0: device disconnected
|usb 3-2: new full speed USB device using ohci_hcd and address 3
|usb 3-2: configuration #1 chosen from 2 choices
|ti_usb_3410_5052 3-2:1.0: TI USB 3410 1 port adapter converter detected
|ti_usb_3410_5052 3-2:1.0: device disconnected
|ti_usb_3410_5052 3-2:2.0: TI USB 3410 1 port adapter converter detected
|usb 3-2: TI USB 3410 1 port adapter converter now attached to ttyUSB0
`-*-

--
-o--=O`C  info emacs : not found
 #oo'L O  info make  : not found
___=E M  man gcc: not found


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processing of linux-modules-extra-2.6_2.6.18-7_i386.changes

2007-02-23 Thread Archive Administrator
linux-modules-extra-2.6_2.6.18-7_i386.changes uploaded successfully to localhost
along with the files:
  linux-modules-extra-2.6_2.6.18-7.dsc
  linux-modules-extra-2.6_2.6.18-7.tar.gz
  gspca-modules-2.6.18-4-486_2.6.18+01.00.12-7_i386.deb
  gspca-modules-2.6-486_2.6.18-7_i386.deb
  redhat-cluster-modules-2.6.18-4-486_2.6.18+1.03.00-7_i386.deb
  redhat-cluster-modules-2.6-486_2.6.18-7_i386.deb
  squashfs-modules-2.6.18-4-486_2.6.18+3.1r2-7_i386.deb
  squashfs-modules-2.6-486_2.6.18-7_i386.deb
  unionfs-modules-2.6.18-4-486_2.6.18+1.4+debian-7_i386.deb
  unionfs-modules-2.6-486_2.6.18-7_i386.deb
  gspca-modules-2.6.18-4-686_2.6.18+01.00.12-7_i386.deb
  gspca-modules-2.6-686_2.6.18-7_i386.deb
  redhat-cluster-modules-2.6.18-4-686_2.6.18+1.03.00-7_i386.deb
  redhat-cluster-modules-2.6-686_2.6.18-7_i386.deb
  squashfs-modules-2.6.18-4-686_2.6.18+3.1r2-7_i386.deb
  squashfs-modules-2.6-686_2.6.18-7_i386.deb
  unionfs-modules-2.6.18-4-686_2.6.18+1.4+debian-7_i386.deb
  unionfs-modules-2.6-686_2.6.18-7_i386.deb
  gspca-modules-2.6.18-4-k7_2.6.18+01.00.12-7_i386.deb
  gspca-modules-2.6-k7_2.6.18-7_i386.deb
  redhat-cluster-modules-2.6.18-4-k7_2.6.18+1.03.00-7_i386.deb
  redhat-cluster-modules-2.6-k7_2.6.18-7_i386.deb
  squashfs-modules-2.6.18-4-k7_2.6.18+3.1r2-7_i386.deb
  squashfs-modules-2.6-k7_2.6.18-7_i386.deb
  unionfs-modules-2.6.18-4-k7_2.6.18+1.4+debian-7_i386.deb
  unionfs-modules-2.6-k7_2.6.18-7_i386.deb
  gspca-modules-2.6.18-4-686-bigmem_2.6.18+01.00.12-7_i386.deb
  gspca-modules-2.6-686-bigmem_2.6.18-7_i386.deb
  redhat-cluster-modules-2.6.18-4-686-bigmem_2.6.18+1.03.00-7_i386.deb
  redhat-cluster-modules-2.6-686-bigmem_2.6.18-7_i386.deb
  squashfs-modules-2.6.18-4-686-bigmem_2.6.18+3.1r2-7_i386.deb
  squashfs-modules-2.6-686-bigmem_2.6.18-7_i386.deb
  unionfs-modules-2.6.18-4-686-bigmem_2.6.18+1.4+debian-7_i386.deb
  unionfs-modules-2.6-686-bigmem_2.6.18-7_i386.deb
  gspca-modules-2.6.18-4-amd64_2.6.18+01.00.12-7_i386.deb
  gspca-modules-2.6-amd64_2.6.18-7_i386.deb
  redhat-cluster-modules-2.6.18-4-amd64_2.6.18+1.03.00-7_i386.deb
  redhat-cluster-modules-2.6-amd64_2.6.18-7_i386.deb
  squashfs-modules-2.6.18-4-amd64_2.6.18+3.1r2-7_i386.deb
  squashfs-modules-2.6-amd64_2.6.18-7_i386.deb
  unionfs-modules-2.6.18-4-amd64_2.6.18+1.4+debian-7_i386.deb
  unionfs-modules-2.6-amd64_2.6.18-7_i386.deb
  gspca-modules-2.6.18-4-vserver-686_2.6.18+01.00.12-7_i386.deb
  gspca-modules-2.6-vserver-686_2.6.18-7_i386.deb
  redhat-cluster-modules-2.6.18-4-vserver-686_2.6.18+1.03.00-7_i386.deb
  redhat-cluster-modules-2.6-vserver-686_2.6.18-7_i386.deb
  squashfs-modules-2.6.18-4-vserver-686_2.6.18+3.1r2-7_i386.deb
  squashfs-modules-2.6-vserver-686_2.6.18-7_i386.deb
  gspca-modules-2.6.18-4-vserver-k7_2.6.18+01.00.12-7_i386.deb
  gspca-modules-2.6-vserver-k7_2.6.18-7_i386.deb
  redhat-cluster-modules-2.6.18-4-vserver-k7_2.6.18+1.03.00-7_i386.deb
  redhat-cluster-modules-2.6-vserver-k7_2.6.18-7_i386.deb
  squashfs-modules-2.6.18-4-vserver-k7_2.6.18+3.1r2-7_i386.deb
  squashfs-modules-2.6-vserver-k7_2.6.18-7_i386.deb
  gspca-modules-2.6.18-4-xen-686_2.6.18+01.00.12-7_i386.deb
  gspca-modules-2.6-xen-686_2.6.18-7_i386.deb
  redhat-cluster-modules-2.6.18-4-xen-686_2.6.18+1.03.00-7_i386.deb
  redhat-cluster-modules-2.6-xen-686_2.6.18-7_i386.deb
  squashfs-modules-2.6.18-4-xen-686_2.6.18+3.1r2-7_i386.deb
  squashfs-modules-2.6-xen-686_2.6.18-7_i386.deb
  gspca-modules-2.6.18-4-xen-vserver-686_2.6.18+01.00.12-7_i386.deb
  gspca-modules-2.6-xen-vserver-686_2.6.18-7_i386.deb
  redhat-cluster-modules-2.6.18-4-xen-vserver-686_2.6.18+1.03.00-7_i386.deb
  redhat-cluster-modules-2.6-xen-vserver-686_2.6.18-7_i386.deb
  squashfs-modules-2.6.18-4-xen-vserver-686_2.6.18+3.1r2-7_i386.deb
  squashfs-modules-2.6-xen-vserver-686_2.6.18-7_i386.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



linux-modules-extra-2.6 override disparity

2007-02-23 Thread Debian Installer
There are disparities between your recently accepted upload and the
override file for the following file(s):

unionfs-modules-2.6-486_2.6.18-7_i386.deb: package says section is admin, 
override says misc.
unionfs-modules-2.6-686_2.6.18-7_i386.deb: package says section is admin, 
override says misc.
unionfs-modules-2.6-k7_2.6.18-7_i386.deb: package says section is admin, 
override says misc.

Either the package or the override file is incorrect.  If you think
the override is correct and the package wrong please fix the package
so that this disparity is fixed in the next upload.  If you feel the
override is incorrect then please reply to this mail and explain why.

[NB: this is an automatically generated mail; if you replied to one
like it before and have not received a response yet, please ignore
this mail.  Your reply needs to be processed by a human and will be in
due course, but until then the installer will send these automated
mails; sorry.]

--
Debian distribution maintenance software

(This message was generated automatically; if you believe that there
is a problem with it please contact the archive administrators by
mailing [EMAIL PROTECTED])


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



linux-modules-extra-2.6_2.6.18-7_i386.changes ACCEPTED

2007-02-23 Thread Debian Installer

Accepted:
gspca-modules-2.6-486_2.6.18-7_i386.deb
  to pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6-486_2.6.18-7_i386.deb
gspca-modules-2.6-686-bigmem_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6-686-bigmem_2.6.18-7_i386.deb
gspca-modules-2.6-686_2.6.18-7_i386.deb
  to pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6-686_2.6.18-7_i386.deb
gspca-modules-2.6-amd64_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6-amd64_2.6.18-7_i386.deb
gspca-modules-2.6-k7_2.6.18-7_i386.deb
  to pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6-k7_2.6.18-7_i386.deb
gspca-modules-2.6-vserver-686_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6-vserver-686_2.6.18-7_i386.deb
gspca-modules-2.6-vserver-k7_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6-vserver-k7_2.6.18-7_i386.deb
gspca-modules-2.6-xen-686_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6-xen-686_2.6.18-7_i386.deb
gspca-modules-2.6-xen-vserver-686_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6-xen-vserver-686_2.6.18-7_i386.deb
gspca-modules-2.6.18-4-486_2.6.18+01.00.12-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6.18-4-486_2.6.18+01.00.12-7_i386.deb
gspca-modules-2.6.18-4-686-bigmem_2.6.18+01.00.12-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6.18-4-686-bigmem_2.6.18+01.00.12-7_i386.deb
gspca-modules-2.6.18-4-686_2.6.18+01.00.12-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6.18-4-686_2.6.18+01.00.12-7_i386.deb
gspca-modules-2.6.18-4-amd64_2.6.18+01.00.12-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6.18-4-amd64_2.6.18+01.00.12-7_i386.deb
gspca-modules-2.6.18-4-k7_2.6.18+01.00.12-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6.18-4-k7_2.6.18+01.00.12-7_i386.deb
gspca-modules-2.6.18-4-vserver-686_2.6.18+01.00.12-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6.18-4-vserver-686_2.6.18+01.00.12-7_i386.deb
gspca-modules-2.6.18-4-vserver-k7_2.6.18+01.00.12-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6.18-4-vserver-k7_2.6.18+01.00.12-7_i386.deb
gspca-modules-2.6.18-4-xen-686_2.6.18+01.00.12-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6.18-4-xen-686_2.6.18+01.00.12-7_i386.deb
gspca-modules-2.6.18-4-xen-vserver-686_2.6.18+01.00.12-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/gspca-modules-2.6.18-4-xen-vserver-686_2.6.18+01.00.12-7_i386.deb
linux-modules-extra-2.6_2.6.18-7.dsc
  to pool/main/l/linux-modules-extra-2.6/linux-modules-extra-2.6_2.6.18-7.dsc
linux-modules-extra-2.6_2.6.18-7.tar.gz
  to pool/main/l/linux-modules-extra-2.6/linux-modules-extra-2.6_2.6.18-7.tar.gz
redhat-cluster-modules-2.6-486_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-486_2.6.18-7_i386.deb
redhat-cluster-modules-2.6-686-bigmem_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-686-bigmem_2.6.18-7_i386.deb
redhat-cluster-modules-2.6-686_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-686_2.6.18-7_i386.deb
redhat-cluster-modules-2.6-amd64_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-amd64_2.6.18-7_i386.deb
redhat-cluster-modules-2.6-k7_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-k7_2.6.18-7_i386.deb
redhat-cluster-modules-2.6-vserver-686_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-vserver-686_2.6.18-7_i386.deb
redhat-cluster-modules-2.6-vserver-k7_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-vserver-k7_2.6.18-7_i386.deb
redhat-cluster-modules-2.6-xen-686_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-xen-686_2.6.18-7_i386.deb
redhat-cluster-modules-2.6-xen-vserver-686_2.6.18-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-xen-vserver-686_2.6.18-7_i386.deb
redhat-cluster-modules-2.6.18-4-486_2.6.18+1.03.00-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.18-4-486_2.6.18+1.03.00-7_i386.deb
redhat-cluster-modules-2.6.18-4-686-bigmem_2.6.18+1.03.00-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.18-4-686-bigmem_2.6.18+1.03.00-7_i386.deb
redhat-cluster-modules-2.6.18-4-686_2.6.18+1.03.00-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.18-4-686_2.6.18+1.03.00-7_i386.deb
redhat-cluster-modules-2.6.18-4-amd64_2.6.18+1.03.00-7_i386.deb
  to 
pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6.18-4-amd64_2.6.18+1.03.00-7_i386.deb
redhat-cluster-modules-2.6.18-4-k7_2.6.18+1.03.00-7_i386.deb
  to 

Bug#410039: No /usr/lib/xen folder so it's confusing other packages

2007-02-23 Thread Goswin von Brederlow
Thomas Goirand [EMAIL PROTECTED] writes:

 Goswin von Brederlow wrote:
 The problem is that multiple xen versions (3.0-unstable, 3.0.3, 3.0.4)
 can be installed and they are incompatible with each other. If each
 one contained /usr/lib/python/xen then the packages would have to
 conflict.

 I understood that, for sure!

 What you need is a common package that contains wrapper scripts in
 /usr/lib/python/xen that will pick the right
 /usr/lib/xen-VERSION/lib/python subdir applicable to the running xen
 version.
 
 Maybe xen-utils-common is what you should be using?

 Maybe a script run at startup could check for the xen version that is
 running and make the appropriate symlink? Sure that could be in a
 xen-common package, for example... Is that what xen-utils-common does?

 Thomas

/usr is (potentially) read-only. You can only write there during
install time which is not enough. You would have to put a static link
to /var/lib/xen and then have a dynamic link there or something.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: initrd udev/devfs problem

2007-02-23 Thread maximilian attems
On Wed, 21 Feb 2007, [EMAIL PROTECTED] wrote:

 On (02/21/07 18:20), maximilian attems wrote:
  use mkinitramfs from initramfs-tools
  
  regards
 
 Hi,
 
 Thanks for the reply, I will try this out. This leads me to
 another question, is there any way to integrate initrmfs-tools 
 with make-kpkg?
 
 -Sergei

it will pick it up automaticaly if you compile with initrd.
and have the do_initrd = yes setting in /etc/kernel-img.conf


-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#411663: linux-image-2.6.18-4-amd64: iptables do not work correctly with amd64 kernel

2007-02-23 Thread Goswin von Brederlow
[EMAIL PROTECTED] writes:

 Package: linux-image-2.6.18-4-amd64
 Version: 2.6.18.dfsg.1-10
 Severity: normal


 It seems that the 32bit iptables package do not work correctly together
 with the (i386) amd64 kernel. After installing this kernel, shorewall do
 not start anymore.

 Here you can see snippets of the logs:

 snippet of /var/log/shorewall-init.log:
 ...
 Processing /etc/shorewall/continue ...
 ip6tables v1.3.6: can't initialize ip6tables table `filter': Invalid
 argument Perhaps ip6tables or your kernel needs to be upgraded.
 ip6tables v1.3.6: can't initialize ip6tables table `filter': Bad file
 descriptor Perhaps ip6tables or your kernel needs to be upgraded.
 ...
 Setting up TC Rules...
 iptables: Invalid argument
ERROR: Command /sbin/iptables -t mangle -A tcpre -s 0.0.0.0/0 -d
 0.0.0.0/0 -p icmp --icmp-type echo-request -j MARK --set-mark 1 Failed
 ...

Wow, another one of those alignment changes.

For now there is a patch in the BTS to build an iptables64 package on
i386 that you can use or you can install the amd64 iptables with
--force-architecture along with amd64-libs.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#411115: sky2 module

2007-02-23 Thread maximilian attems
On Wed, 21 Feb 2007, Renato S. Yamane wrote:

 Patchs available to 2.6.20 stable Kernel comment by Stephen is attached.
 
  sky2-pause-flush.patch
  sky2-tx-timeout-deadlock.patch
 Subject: sky2: don't flush good pause frames
 

thanks that's a first help :)
but i guess they won't apply to 2.6.18,
plus there were also some other important sky2 patches
from 2.6.18 to 2.6.20

regards

--
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401916: Bug #401916 - any progress?

2007-02-23 Thread maximilian attems
On Fri, 23 Feb 2007, David Härdeman wrote:

 maks...any progress on this bug?

no.
latest initramfs-tools is on mentors without any #401916 yet.
 
 A new package which exports ROOTDELAY would be nice, then the rest can be
 fixed in udev...

well i don't feel that is enough.
mika's case is general enough, it affects lilo on almost any
root beside ide and quick sata controller 
and grub for lvm2, evms and mdadm on those too.

all the other distribution add some bandaid aka stupid sleep
for the case of usb, ..
and for a quick glance over those initramfs generators
this would be done on mkinitramfs time.
right?


sorry, really busy on a physics workshop so no code right now.
but happy about your ping!

salutations amicales
 
-- 
maks



Bug#412075: no files bigger than 1GB possible on udf-Filesystems

2007-02-23 Thread Thomas Geyer

Package: kernel-image-2.6-k7
Version: 101sarge1   2.6.18+5
Severity: wishlist

Since http://www.debian.org/security/2006/dsa-1184
it is not possible to write files larger than 1GB on udf-Filesystems,
both on sarge and etch.

(  udf-deadlock.dpatch
  [SECURITY] Fix possible UDF deadlock and memory corruption
  See CVE-2006-4145 )

This decreases the funktionality of udf-media especially for backup issues.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401916: Bug #401916 - any progress?

2007-02-23 Thread David Härdeman
On Fri, February 23, 2007 12:11, maximilian attems said:
 On Fri, 23 Feb 2007, David Härdeman wrote:

 maks...any progress on this bug?

 no.
 latest initramfs-tools is on mentors without any #401916 yet.

 A new package which exports ROOTDELAY would be nice, then the rest can
 be fixed in udev...

 well i don't feel that is enough.

That what is enough? Just having a sleep boot arg?

 mika's case is general enough, it affects lilo on almost any
 root beside ide and quick sata controller
 and grub for lvm2, evms and mdadm on those too.

Sorry, I don't follow, what does lilo and grub have to do with waiting in
the initramfs for the root blockdev to appear? Was that a reference to bug
 409820?

 all the other distribution add some bandaid aka stupid sleep
 for the case of usb, ..
 and for a quick glance over those initramfs generators
 this would be done on mkinitramfs time.
 right?

Yes, initramfs-based fixed sleep for a couple of seconds (which may still
break in some scenarios) or a hardcoded root device (which allows the
initramfs script to wait until that root device node appears) are the two
solution I've seen from a quick survey.

I still think a user-configurable sleep (and/or a user configurable device
node to wait for) would be the best option at this point followed by a
more complete solution later.

 sorry, really busy on a physics workshop so no code right now.
 but happy about your ping!

Good luck with your workshop

 salutations amicales

Med vänliga hälsningar.

-- 
David Härdeman



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#412086: kernel-image-2.6.8-3-686: Masquerading problem with dynamic IP interfac

2007-02-23 Thread Oliver Seufer
Subject: kernel-image-2.6.8-3-686: Masquerading problem with dynamic IP 
interfaces
Package: kernel-image-2.6.8-3-686
Version: 2.6.8-16sarge6
Severity: important
Tags: patch

*** Please type your report below this line ***
When using Debian Sarge with kernel-image-2.6.8-3-686 as a nat gateway
with a dynamic IP interfaces like pppoe and you have OpenVPN clients or other
udp based programms behind the gateway, you have the following problem
after a reconnect of the pppoe interface you get a new address, but the state
entry in /proc/net/ip_conntrack will stay with the old address for the
udp connection. 

Without the attached patch the OpenVPN tunnel is not usable anymore,
because the packages are send out on the pppoe interface with the wrong
ip address. 

This bug is also mentioned here:
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=329

I took the patch from
http://www.linuxarkivet.se/mlists/netfilter-devel/0411/msg00154.html
and modified it for the debian kernel. 

This is fixed in newer kernel versions.

Regards,

Oliver Seufer

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-image-2.6.8-3-686 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  initrd-tools  0.1.81.1   tools to create initrd image for p
ii  module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo

-- no debconf information
--- net/ipv4/netfilter/ipt_MASQUERADE.c 2004-08-14 07:37:15.0 +0200
+++ net/ipv4/netfilter/ipt_MASQUERADE.c.patched 2007-02-23 13:30:29.709425676 
+0100
@@ -141,35 +141,58 @@
 }
 
 static inline int
-device_cmp(const struct ip_conntrack *i, void *_ina)
+device_cmp(const struct ip_conntrack *i, void *ifindex)
 {
-   int ret = 0;
-   struct in_ifaddr *ina = _ina;
+   int ret;
 
READ_LOCK(masq_lock);
-   /* If it's masquerading out this interface with a different address,
-  or we don't know the new address of this interface. */
-   if (i-nat.masq_index == ina-ifa_dev-dev-ifindex
-i-tuplehash[IP_CT_DIR_REPLY].tuple.dst.ip != ina-ifa_address)
-   ret = 1;
+   ret = (i-nat.masq_index == (int)(long)ifindex);
READ_UNLOCK(masq_lock);
 
return ret;
 }
 
+static int masq_device_event(struct notifier_block *this,
+   unsigned long event,
+   void *ptr)
+{
+   struct net_device *dev = ptr;
+
+   if (event == NETDEV_DOWN) {
+   /* Device was downed.  Search entire table for
+  conntracks which were associated with that device,
+  and forget them. */
+   IP_NF_ASSERT(dev-ifindex != 0);
+
+   ip_ct_selective_cleanup(device_cmp, (void *)(long)dev-ifindex);
+   }
+
+   return NOTIFY_DONE;
+}
+
 static int masq_inet_event(struct notifier_block *this,
   unsigned long event,
   void *ptr)
 {
-   /* For some configurations, interfaces often come back with
-* the same address.  If not, clean up old conntrack
-* entries. */
-   if (event == NETDEV_UP)
-   ip_ct_selective_cleanup(device_cmp, ptr);
+   struct net_device *dev = ((struct in_ifaddr *)ptr)-ifa_dev-dev;
+
+   if (event == NETDEV_DOWN) {
+   /* IP address was deleted.  Search entire table for
+  conntracks which were associated with that device,
+  and forget them. */
+   IP_NF_ASSERT(dev-ifindex != 0);
+
+   ip_ct_selective_cleanup(device_cmp, (void *)(long)dev-ifindex);
+
+   }
 
return NOTIFY_DONE;
 }
 
+static struct notifier_block masq_dev_notifier = {
+   .notifier_call  = masq_device_event,
+};
+
 static struct notifier_block masq_inet_notifier = {
.notifier_call  = masq_inet_event,
 };
@@ -187,9 +210,12 @@
 
ret = ipt_register_target(masquerade);
 
-   if (ret == 0)
+   if (ret == 0) {
+   /* Register for device down reports */
+   register_netdevice_notifier(masq_dev_notifier);
/* Register IP address change reports */
register_inetaddr_notifier(masq_inet_notifier);
+   }
 
return ret;
 }
@@ -197,6 +223,7 @@
 static void __exit fini(void)
 {
ipt_unregister_target(masquerade);
+   unregister_netdevice_notifier(masq_dev_notifier);
unregister_inetaddr_notifier(masq_inet_notifier);  
 }
 


Bug#401916: Bug #401916 - any progress?

2007-02-23 Thread maximilian attems
On Fri, Feb 23, 2007 at 01:46:08PM +0100, David Härdeman wrote:
 On Fri, February 23, 2007 12:11, maximilian attems said:
  On Fri, 23 Feb 2007, David Härdeman wrote:
snipp 
  mika's case is general enough, it affects lilo on almost any
  root beside ide and quick sata controller
  and grub for lvm2, evms and mdadm on those too.
 
 Sorry, I don't follow, what does lilo and grub have to do with waiting in
 the initramfs for the root blockdev to appear? Was that a reference to bug
  409820?

for grub we can wait for the root dev to appear,
for lilo we create it by hand, so it's always there
and you fall into the rescue shell for async root drivers.

so this is the topic of this particular bug and afaik
the grml-2hd test case is precisely done on an usb stick
with lilo bootloader.
 
  all the other distribution add some bandaid aka stupid sleep
  for the case of usb, ..
  and for a quick glance over those initramfs generators
  this would be done on mkinitramfs time.
  right?
 
 Yes, initramfs-based fixed sleep for a couple of seconds (which may still
 break in some scenarios) or a hardcoded root device (which allows the
 initramfs script to wait until that root device node appears) are the two
 solution I've seen from a quick survey.
 
 I still think a user-configurable sleep (and/or a user configurable device
 node to wait for) would be the best option at this point followed by a
 more complete solution later.

yes the user configured sleep should override the stupid bandaid sleep.
and i would like that band aid sleep only for the known trouble
cases like usb-storage and ieee1394.
we don't have too _many_ complaints, so we aren't doing that badly.
 
  sorry, really busy on a physics workshop so no code right now.
  but happy about your ping!
 
 Good luck with your workshop

thanks, pretty intersting but lots of work..
 
  salutations amicales
 
 Med vänliga hälsningar.

zut babelfish lacks danish features.
switching back ;)

happy greetings
maks 



Bug#401916: Bug #401916 - any progress?

2007-02-23 Thread David Härdeman
On Fri, February 23, 2007 14:16, maximilian attems said:
 On Fri, Feb 23, 2007 at 01:46:08PM +0100, David Härdeman wrote:
 On Fri, February 23, 2007 12:11, maximilian attems said:
  On Fri, 23 Feb 2007, David Härdeman wrote:
 snipp
  mika's case is general enough, it affects lilo on almost any
  root beside ide and quick sata controller
  and grub for lvm2, evms and mdadm on those too.

 Sorry, I don't follow, what does lilo and grub have to do with waiting
 in
 the initramfs for the root blockdev to appear? Was that a reference to
 bug
  409820?

 for grub we can wait for the root dev to appear,
 for lilo we create it by hand, so it's always there
 and you fall into the rescue shell for async root drivers.

Ah yes, now I follow, with lilo we get a numeric root dev which is passed
to parse_numeric() and used for /dev/root.

 so this is the topic of this particular bug and afaik
 the grml-2hd test case is precisely done on an usb stick
 with lilo bootloader.

  all the other distribution add some bandaid aka stupid sleep
  for the case of usb, ..
  and for a quick glance over those initramfs generators
  this would be done on mkinitramfs time.
  right?

 Yes, initramfs-based fixed sleep for a couple of seconds (which may
 still
 break in some scenarios) or a hardcoded root device (which allows the
 initramfs script to wait until that root device node appears) are the
 two
 solution I've seen from a quick survey.

 I still think a user-configurable sleep (and/or a user configurable
 device
 node to wait for) would be the best option at this point followed by a
 more complete solution later.

 yes the user configured sleep should override the stupid bandaid sleep.
 and i would like that band aid sleep only for the known trouble
 cases like usb-storage and ieee1394.
 we don't have too _many_ complaints, so we aren't doing that badly.

Exactly, considering the low amount of complaints, I'd say there's a tiny
minority that is actually affected by this bug.

Secondly, there is no way to have the bandaid-wait for usb-storage users
only, instead it would hit every computer with usb port (i.e. the vast
majority).

That's why I think it would be enough to: not include the bandaid at all,
implement the rootwait parameter and let the small minority who are
affected use it.

 sorry, really busy on a physics workshop so no code right now.
 but happy about your ping!

 Good luck with your workshop

 thanks, pretty intersting but lots of work..

Since you're busy, I'll do another patch which implements the rootwait
parameter during the weekend. Question is, should I completely remove the
wait from the premount stage (where it is now) and move it to the udev
stage, or should it be duplicated?

  salutations amicales

 Med vänliga hälsningar.

 zut babelfish lacks danish features.

Swedish

 switching back ;)

Mit freundlichen Grüßen :)

-- 
David Härdeman



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#412092: [Patch] bug in gdth.c crashing machine

2007-02-23 Thread Joerg Dorchain
Package: linux-image-2.6.18-3-686
Version: 2.6.18-7
Tags: upstream,patch
Severity: important

Hello,

there is a bug in the gdth driver causing crashes and potential data
losses when using tape. The bug is also described and confirmed on the lklm
on 13 Oct 2006
Message-ID: [EMAIL PROTECTED]

The included patch is derived directly from that mail.

Please consider including it until it has made it upstream, as it
endangers machines doing tape backups.

Bye,

Joerg


--- gdth.c.orig 2007-02-23 12:48:56.0 +0100
+++ gdth.c  2007-02-23 12:51:44.0 +0100
@@ -3092,6 +3092,7 @@
 cmdp-u.raw64.direction  = 
 gdth_direction_tab[scp-cmnd[0]]==DOU ? 
GDTH_DATA_OUT:GDTH_DATA_IN;
 memcpy(cmdp-u.raw64.cmd,scp-cmnd,16);
+cmdp-u.raw64.sg_ranz= 0;
 } else {
 cmdp-u.raw.reserved   = 0;
 cmdp-u.raw.mdisc_time = 0;
@@ -3108,6 +3109,7 @@
 cmdp-u.raw.direction  = 
 gdth_direction_tab[scp-cmnd[0]]==DOU ? 
GDTH_DATA_OUT:GDTH_DATA_IN;
 memcpy(cmdp-u.raw.cmd,scp-cmnd,12);
+cmdp-u.raw.sg_ranz= 0;
 }
 
 if (scp-use_sg) {


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401916: Bug #401916 - any progress?

2007-02-23 Thread maximilian attems
On Fri, Feb 23, 2007 at 03:05:44PM +0100, David Härdeman wrote:
 
 Exactly, considering the low amount of complaints, I'd say there's a tiny
 minority that is actually affected by this bug.
 
 Secondly, there is no way to have the bandaid-wait for usb-storage users
 only, instead it would hit every computer with usb port (i.e. the vast
 majority).

hmm i thought there was just from looking at the init scripts
you or mikap posted..
 
 Since you're busy, I'll do another patch which implements the rootwait
 parameter during the weekend. Question is, should I completely remove the
 wait from the premount stage (where it is now) and move it to the udev
 stage, or should it be duplicated?

don't remove it as the udev rootdelay is optional as bootparam.
we want a small diff too ;)
 
uups always confusing the .nu domain to the language,
bad geoip matching :-P

cya maks



Bug#401916: Bug #401916 - any progress?

2007-02-23 Thread David Härdeman
On Fri, February 23, 2007 16:28, maximilian attems said:
 On Fri, Feb 23, 2007 at 03:05:44PM +0100, David Härdeman wrote:
 Exactly, considering the low amount of complaints, I'd say there's a
 tiny minority that is actually affected by this bug.

 Secondly, there is no way to have the bandaid-wait for usb-storage users
 only, instead it would hit every computer with usb port (i.e. the vast
 majority).

 hmm i thought there was just from looking at the init scripts
 you or mikap posted..

No, unfortunately it seems that the times between loading the usb host
controller, loading usb-storage and spawning the usb-storage-scan thread
are all asynchronous. So we can't really know how long time we need to
wait for any of those stages.

 Since you're busy, I'll do another patch which implements the rootwait
 parameter during the weekend. Question is, should I completely remove
 the
 wait from the premount stage (where it is now) and move it to the udev
 stage, or should it be duplicated?

 don't remove it as the udev rootdelay is optional as bootparam.
 we want a small diff too ;)

So just to make sure: you want the use of the rootdelay parameter to be
added to the udev script and kept in the initramfs script (i.e. used
twice)?

In that case if you specify rootdelay=5, the boot will pause in the udev
stage and then again after the premount stage (before the actual mount).

The dual wait is probably no big deal of course...since it adds a few
seconds to some exotic boot scenarios only. I'll start working on this...

-- 
David Härdeman



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401916: Bug #401916 - any progress?

2007-02-23 Thread maximilian attems
On Fri, Feb 23, 2007 at 04:39:52PM +0100, David Härdeman wrote:
 On Fri, February 23, 2007 16:28, maximilian attems said:
 
 No, unfortunately it seems that the times between loading the usb host
 controller, loading usb-storage and spawning the usb-storage-scan thread
 are all asynchronous. So we can't really know how long time we need to
 wait for any of those stages.

zut they were only pasted to irc it seems,
no you had the mandrake one posted, so this one might not
been on the radar yet
http://david.woodhou.se/olpc-init.txt

my current statement is that other distribution add some stupid
sleep inside on the case of some async drivers.
afair that the heuristic for the choice is done on build time.
 
 So just to make sure: you want the use of the rootdelay parameter to be
 added to the udev script and kept in the initramfs script (i.e. used
 twice)?
 
 In that case if you specify rootdelay=5, the boot will pause in the udev
 stage and then again after the premount stage (before the actual mount).
 
 The dual wait is probably no big deal of course...since it adds a few
 seconds to some exotic boot scenarios only. I'll start working on this...

the dual wait only comes to play if your root doesn't show off yet
after the first round. see scripts/local:
if [ ! -e ${ROOT} ]; then


--
maks



Processed: reassign 412075 to kernel-source-2.6.8, tagging 412075, cloning 412075, reassign -1 to linux-2.6

2007-02-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.27
 reassign 412075 kernel-source-2.6.8
Bug#412075: no files bigger than 1GB possible on udf-Filesystems
Bug reassigned from package `kernel-image-2.6-k7' to `kernel-source-2.6.8'.

 tags 412075 + upstream
Bug#412075: no files bigger than 1GB possible on udf-Filesystems
There were no tags set.
Tags added: upstream

 clone 412075 -1
Bug#412075: no files bigger than 1GB possible on udf-Filesystems
Bug 412075 cloned as bug 412098.

 reassign -1 linux-2.6
Bug#412098: no files bigger than 1GB possible on udf-Filesystems
Bug reassigned from package `kernel-source-2.6.8' to `linux-2.6'.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: reassign 412086 to kernel-source-2.6.8

2007-02-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.27
 reassign 412086 kernel-source-2.6.8
Bug#412086: kernel-image-2.6.8-3-686: Masquerading problem with dynamic IP 
interfac
Bug reassigned from package `kernel-image-2.6.8-3-686' to `kernel-source-2.6.8'.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Question about config of Debian/unstable kernel

2007-02-23 Thread Patrick Vervoorn

Hello there,

I'm running the following Debian-unstable kernel:

Linux morannon 2.6.18-4-686 #1 SMP Wed Feb 21 16:06:54 UTC 2007 i686 GNU/Linux

Aptitude says:

  --\ Versions
i2.6.18.dfsg.1-11

Is this kernel compiled/generated with the Large Block Devices enabled? 
Reason, I've mounted a 3.0TB filesystem via samba, but am seeing only 
2.0TB of it via, for instance, df.


If this is not enabled, is there an easy way to do enable it in this 
binary kernel image, or do I have to generate my own kernel?


Thanks in advance,

Patrick.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processing of linux-2.6_2.6.18.dfsg.1-11_m68k.changes

2007-02-23 Thread Archive Administrator
linux-headers-2.6.18-4_2.6.18.dfsg.1-11_m68k.deb has incorrect size; deleting it
Due to the errors above, the .changes file couldn't be processed.
Please fix the problems for the upload to happen.

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processing of linux-2.6_2.6.18.dfsg.1-11_m68k.changes

2007-02-23 Thread Archive Administrator
linux-2.6_2.6.18.dfsg.1-11_m68k.changes uploaded successfully to localhost
along with the files:
  linux-headers-2.6.18-4-all_2.6.18.dfsg.1-11_m68k.deb
  linux-headers-2.6.18-4-all-m68k_2.6.18.dfsg.1-11_m68k.deb
  linux-headers-2.6.18-4_2.6.18.dfsg.1-11_m68k.deb
  linux-image-2.6.18-4-amiga_2.6.18.dfsg.1-11_m68k.deb
  linux-headers-2.6.18-4-amiga_2.6.18.dfsg.1-11_m68k.deb
  linux-image-2.6.18-4-atari_2.6.18.dfsg.1-11_m68k.deb
  linux-headers-2.6.18-4-atari_2.6.18.dfsg.1-11_m68k.deb
  linux-image-2.6.18-4-mac_2.6.18.dfsg.1-11_m68k.deb
  linux-headers-2.6.18-4-mac_2.6.18.dfsg.1-11_m68k.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



linux-2.6_2.6.18.dfsg.1-11_m68k.changes ACCEPTED

2007-02-23 Thread Debian Installer

Accepted:
linux-headers-2.6.18-4-all-m68k_2.6.18.dfsg.1-11_m68k.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-4-all-m68k_2.6.18.dfsg.1-11_m68k.deb
linux-headers-2.6.18-4-all_2.6.18.dfsg.1-11_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.18-4-all_2.6.18.dfsg.1-11_m68k.deb
linux-headers-2.6.18-4-amiga_2.6.18.dfsg.1-11_m68k.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-4-amiga_2.6.18.dfsg.1-11_m68k.deb
linux-headers-2.6.18-4-atari_2.6.18.dfsg.1-11_m68k.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.18-4-atari_2.6.18.dfsg.1-11_m68k.deb
linux-headers-2.6.18-4-mac_2.6.18.dfsg.1-11_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.18-4-mac_2.6.18.dfsg.1-11_m68k.deb
linux-headers-2.6.18-4_2.6.18.dfsg.1-11_m68k.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.18-4_2.6.18.dfsg.1-11_m68k.deb
linux-image-2.6.18-4-amiga_2.6.18.dfsg.1-11_m68k.deb
  to pool/main/l/linux-2.6/linux-image-2.6.18-4-amiga_2.6.18.dfsg.1-11_m68k.deb
linux-image-2.6.18-4-atari_2.6.18.dfsg.1-11_m68k.deb
  to pool/main/l/linux-2.6/linux-image-2.6.18-4-atari_2.6.18.dfsg.1-11_m68k.deb
linux-image-2.6.18-4-mac_2.6.18.dfsg.1-11_m68k.deb
  to pool/main/l/linux-2.6/linux-image-2.6.18-4-mac_2.6.18.dfsg.1-11_m68k.deb


Override entries for your package:
linux-headers-2.6.18-4-all-m68k_2.6.18.dfsg.1-11_m68k.deb - optional devel
linux-headers-2.6.18-4-all_2.6.18.dfsg.1-11_m68k.deb - optional devel
linux-headers-2.6.18-4-amiga_2.6.18.dfsg.1-11_m68k.deb - optional devel
linux-headers-2.6.18-4-atari_2.6.18.dfsg.1-11_m68k.deb - optional devel
linux-headers-2.6.18-4-mac_2.6.18.dfsg.1-11_m68k.deb - optional devel
linux-headers-2.6.18-4_2.6.18.dfsg.1-11_m68k.deb - optional devel
linux-image-2.6.18-4-amiga_2.6.18.dfsg.1-11_m68k.deb - optional admin
linux-image-2.6.18-4-atari_2.6.18.dfsg.1-11_m68k.deb - optional admin
linux-image-2.6.18-4-mac_2.6.18.dfsg.1-11_m68k.deb - optional admin



Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#412122: network adapter (BCM 5704s) not working with kernel 2.6.8-12

2007-02-23 Thread Olivier RICHE

Package: kernel-image-2.6.8-12-amd64-k8-smp
Severity: grave

distribution : sarge (3.1) kernel 2.6.8-12 on AMD64

hardware : Fujitsu Primergy BX630 
(http://developer.novell.com/yes/84281.htm)


Hi,

I installed sarge on new server using the net install cd (i386) and 
under the 2.4.27-3-386 kernel, the network adapter works fine.


After upgrading to kernel 2.6.8-12-amd64-k8-smp, the network adapter 
(BCM 5704s Gigabit Ethernet Controlle) does not work any more.  There 
are strange error messages about tg3.ko and the network adapter goes down.


extract from /var/log/messages :

Feb 23 18:16:48 samsara kernel: tg3.c:v3.10 (September 14, 2004)
Feb 23 18:16:48 samsara kernel: ACPI: PCI interrupt :03:04.0[A] - 
GSI 28 (level, low) - IRQ 28
Feb 23 18:16:48 samsara kernel: tg3: tg3_request_firmware (eth%%d): 
Couldn't get firmware tg3/tso-1.4.0.
Feb 23 18:16:48 samsara kernel: tg3: eth%%d: Firmware tg3/tso-1.4.0 
not loaded; continuing without TSO.
Feb 23 18:16:48 samsara kernel: eth0: Tigon3 [partno(BCM95704A41) rev 
2100 PHY(serdes)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 
00:30:05:71:d7:e6
Feb 23 18:16:48 samsara kernel: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] Split[0] WireSpeed[1] TSOcap[0]
Feb 23 18:16:48 samsara kernel: ACPI: PCI interrupt :03:04.1[B] - 
GSI 29 (level, low) - IRQ 29
Feb 23 18:16:48 samsara kernel: tg3: tg3_request_firmware (eth%%d): 
Couldn't get firmware tg3/tso-1.4.0.
Feb 23 18:16:48 samsara kernel: tg3: eth%%d: Firmware tg3/tso-1.4.0 
not loaded; continuing without TSO.
Feb 23 18:16:48 samsara kernel: eth1: Tigon3 [partno(BCM95704A41) rev 
2100 PHY(serdes)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 
00:30:05:71:d7:e7
Feb 23 18:16:48 samsara kernel: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] Split[0] WireSpeed[1] TSOcap[0]
Feb 23 18:16:48 samsara kernel: ACPI: PCI interrupt :01:00.0[D] - 
GSI 19 (level, low) - IRQ 19
Feb 23 18:16:48 samsara kernel: ohci_hcd :01:00.0: Advanced Micro 
Devices [AMD] AMD-8111 USB
Feb 23 18:16:48 samsara kernel: ohci_hcd :01:00.0: irq 19, pci mem 
ff19
Feb 23 18:16:48 samsara kernel: ohci_hcd :01:00.0: new USB bus 
registered, assigned bus number 1

Feb 23 18:16:48 samsara kernel: hub 1-0:1.0: USB hub found
Feb 23 18:16:48 samsara kernel: hub 1-0:1.0: 3 ports detected
Feb 23 18:16:48 samsara kernel: ACPI: PCI interrupt :01:00.1[D] - 
GSI 19 (level, low) - IRQ 19
Feb 23 18:16:48 samsara kernel: ohci_hcd :01:00.1: Advanced Micro 
Devices [AMD] AMD-8111 USB (#2)
Feb 23 18:16:48 samsara kernel: ohci_hcd :01:00.1: irq 19, pci mem 
ff192000
Feb 23 18:16:48 samsara kernel: ohci_hcd :01:00.1: new USB bus 
registered, assigned bus number 2

Feb 23 18:16:48 samsara kernel: hub 2-0:1.0: USB hub found
Feb 23 18:16:48 samsara kernel: hub 2-0:1.0: 3 ports detected
Feb 23 18:16:48 samsara kernel: hw_random: AMD768 system management I/O 
registers at 0xC000.

Feb 23 18:16:48 samsara kernel: hw_random hardware driver 1.0.0 loaded
Feb 23 18:16:48 samsara kernel: tg3: eth0: Link is up at 1000 Mbps, full 
duplex.
Feb 23 18:16:48 samsara kernel: tg3: eth0: Flow control is off for TX 
and off for RX.

Feb 23 18:16:49 samsara kernel: tg3: eth0: Link is down.
Feb 23 18:16:50 samsara lpd[2037]: restarted
Feb 23 18:16:50 samsara kernel: NET: Registered protocol family 10
Feb 23 18:16:50 samsara kernel: Disabled Privacy Extensions on device 
80357480(lo)

Feb 23 18:16:50 samsara kernel: IPv6 over IPv4 tunneling driver
Feb 23 18:16:51 samsara kernel: tg3: eth0: Link is up at 1000 Mbps, full 
duplex.
Feb 23 18:16:51 samsara kernel: tg3: eth0: Flow control is off for TX 
and off for RX.

Feb 23 18:16:52 samsara kernel: tg3: eth0: Link is down.
Feb 23 18:16:54 samsara kernel: tg3: eth0: Link is up at 1000 Mbps, full 
duplex.
Feb 23 18:16:54 samsara kernel: tg3: eth0: Flow control is off for TX 
and off for RX.

...
then the link is up and down, and up and down, 

Any help appreciated

Regards

Olivier


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#410853: linux-2.6: please add support for armel architecture

2007-02-23 Thread Lennert Buytenhek
Attached is a new patch that:
* Drops both footbridge and rpc from the armel flavour list.
  (Martin Michlmayr.)
* Adds CONFIG_AEABI=y/CONFIG_OABI_COMPAT=y to config.iop32x and
  config.ixp4xx as well, since they seem to override the main
  config.  (Joey Hess)

Apply as follows:

cp -a debian/arch/arm debian/arch/armel
rm debian/arch/armel/*footbridge*
rm debian/arch/armel/*rpc*
patch -p0  armel3.patch
debian/rules debian/control
diff -urN debian/arch/armel/config.orig debian/arch/armel/config
--- debian/arch/armel/config.orig   2007-02-23 00:55:58.0 +
+++ debian/arch/armel/config2007-02-23 00:56:23.0 +
@@ -19,4 +19,5 @@
 CONFIG_JBD=y
 # CONFIG_ARCH_REALVIEW is not set
 CONFIG_TMPFS=y
-# CONFIG_AEABI is not set
+CONFIG_AEABI=y
+CONFIG_OABI_COMPAT=y
diff -urN debian/arch/armel/config.iop32x.orig debian/arch/armel/config.iop32x
--- debian/arch/armel/config.iop32x.orig2007-02-23 00:55:58.0 
+
+++ debian/arch/armel/config.iop32x 2007-02-23 01:01:58.0 +
@@ -136,7 +136,8 @@
 #
 # CONFIG_PREEMPT is not set
 # CONFIG_NO_IDLE_HZ is not set
-# CONFIG_AEABI is not set
+CONFIG_AEABI=y
+CONFIG_OABI_COMPAT=y
 # CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
 CONFIG_SELECT_MEMORY_MODEL=y
 CONFIG_FLATMEM_MANUAL=y
diff -urN debian/arch/armel/config.ixp4xx.orig debian/arch/armel/config.ixp4xx
--- debian/arch/armel/config.ixp4xx.orig2007-02-23 00:55:58.0 
+
+++ debian/arch/armel/config.ixp4xx 2007-02-23 01:02:07.0 +
@@ -139,7 +139,8 @@
 #
 # CONFIG_PREEMPT is not set
 # CONFIG_NO_IDLE_HZ is not set
-# CONFIG_AEABI is not set
+CONFIG_AEABI=y
+CONFIG_OABI_COMPAT=y
 # CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
 CONFIG_SELECT_MEMORY_MODEL=y
 CONFIG_FLATMEM_MANUAL=y
diff -urN debian/arch/armel/config.versatile.orig 
debian/arch/armel/config.versatile
--- debian/arch/armel/config.versatile.orig 2007-02-23 00:55:58.0 
+
+++ debian/arch/armel/config.versatile  2007-02-23 00:56:23.0 +
@@ -147,7 +147,8 @@
 #
 # CONFIG_PREEMPT is not set
 # CONFIG_NO_IDLE_HZ is not set
-# CONFIG_AEABI is not set
+CONFIG_AEABI=y
+CONFIG_OABI_COMPAT=y
 # CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
 CONFIG_SELECT_MEMORY_MODEL=y
 CONFIG_FLATMEM_MANUAL=y
diff -urN debian/arch/armel/defines.orig debian/arch/armel/defines
--- debian/arch/armel/defines.orig  2007-02-23 00:55:58.0 +
+++ debian/arch/armel/defines   2007-02-23 00:58:33.0 +
@@ -1,23 +1,15 @@
 [base]
 flavours:
- footbridge
  iop32x
  ixp4xx
- rpc
  s3c2410
+ versatile
 kernel-arch: arm
 kernel-header-dirs: arm
 
 [image]
 suggests: fdutils
 
-[footbridge_image]
-suggests: nwutil
-
-[footbridge]
-class: Footbridge based
-longclass: Footbridge (CATS, Netwinder)
-
 [iop32x]
 class: IOP32x
 longclass: IOP32x based (Thecus N2100, etc)
@@ -26,10 +18,6 @@
 class: IXP4xx
 longclass: IXP4xx based (Linksys NSLU2, etc)
 
-[rpc]
-class: RiscPC
-longclass: Arcon RiscPC
-
 [s3c2410]
 class: Samsung S3C2410
 longclass: Samsung S3C2410 based (BAST, IPAQ 1940, etc)
diff -urN debian/arch/defines.orig debian/arch/defines
--- debian/arch/defines.orig2007-02-23 10:31:12.0 +
+++ debian/arch/defines 2007-02-23 00:56:23.0 +
@@ -6,6 +6,7 @@
  alpha
  amd64
  arm
+ armel
  hppa
  i386
  ia64


Bug#412132: cacct interface misscalced about 100 TB

2007-02-23 Thread Patrick Matthäi

Package: linux-image-2.6.18-4-vserver-amd64
Version: 2.6.18.dfsg.1-9
Severity: serious

Hello,

I think I've found a serious bug in the vserver image for amd64.
We're running a daemon, which is logging the traffic of all 
hostmachines. Now I've found a very big mistake in the 
/proc/virtual/id/cacct interface.


The daemon gets the informations of this cacct interface and will calc 
the caused traffic, here's the debug of my daemon:


|Fri Feb 23 15:42:01 2007 - cacct: 1472700147 o.cacct 1472517504 logged: 1495189052 now: 1495371695 method: 1 


Fri Feb 23 16:00:01 2007 - cacct: 18446744072641133818 o.cacct 3222831651 
logged: 3178567909 now: 18446744072596870076 method: 1

|The cacct variable is the value of all incoming / outcoming IPv4 and 
IPv6 traffic in bytes.
This debug would mean, that one customer has caused traffic more as 100 
TB in 20 minutes ( and that only with one ventrilo server! ).
First I thought, it's a bug in my daemon software, but that wasn't the 
problem, how this information will show:


|hostname:~/control# cat /proc/virtual/2/cacct
UNSPEC:0/0 0/0 0/0 

UNIX: 305586/28642976 267311/28642976  1/30 

INET:9058790/1149688302  9889025/18446744071736090069  47323/18446744072430740975 

INET6: 0/0 0/0 0/0 

OTHER: 0/0 0/0 0/0 


forks:  0|
|
|It seems as the kernel misscalced or overflowed after a cacct value 
over |1472700147.


It's the first and only example of this bug, because this is the first 
customer, with such a lot traffic.


Regards,
Patrick Matthäi
|



Bug#412132:

2007-02-23 Thread Patrick Matthäi

Hi again,

I'm very sorry, I pasted the wrong debug lines:

Fri Feb 23 15:42:01 2007 - cacct: 39375996 o.cacct 39375996 logged: 
39375996 now: 39375996 method: 1
Fri Feb 23 16:00:01 2007 - cacct: 18446744072641133818 o.cacct 
3222831651 logged: 3178567909 now: 18446744072596870076 method: 1


This would be the right one, which would mean, that this error will 
cause maybe about 39375996 bytes ( ~ 4gb ).


Regards,
Patrick Matthäi




Bug#412139: linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root

2007-02-23 Thread Michael Rasmussen
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-11
Severity: grave
Justification: renders package unusable

After latest upgrade of 2.6.18-4-686 my machine stops booting when reasing to 
the message: Waiting for root.

The disk is found but just before finding disk on system I see this error 
message from udev: udevd[411]: Illegal subsystem (or something like that). Then 
complains of an error in /etc/udev/rules.d/udev.rules on line 61

I have tried to run update-initramfs -u -t -k 2.6.18-4-686 without any luck.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.18-4-686 depends on:
ii  coreutils 5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85e  tools for generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-18  Yet Another mkInitRD

Versions of packages linux-image-2.6.18-4-686 recommends:
ii  libc6-i686  2.3.6.ds1-13 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true
  linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true
  linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false
  linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false
  linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/bootloader-initrd-2.6.18-4-686: true
* linux-image-2.6.18-4-686/preinst/already-running-this-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/old-dir-initrd-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/kimage-is-a-directory:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/initrd-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#412132: Patch

2007-02-23 Thread Patrick Matthäi

And hello again ;)

I talked about that problem with the people of linux-vserver.org. It's a 
known upstream bug, which is already fixed.


Here's the patch:
http://people.linux-vserver.org/~dhozac/p/k/delta-longatomic-fix01.diff

The counter overflows like I said at 4 GB ( like on a 32 bit system ).

I hope you can apply this patch fast, it's very important for us.

Thanks and regards,
Patrick Matthäi



Bug#412132: cacct interface misscalced about 100 TB

2007-02-23 Thread Bastian Blank
severity 412132 important
user debian-kernel@lists.debian.org
usertag dkt-waiting-etch-update
tags 412132 +patch
thanks

On Fri, Feb 23, 2007 at 11:19:57PM +0100, Patrick Matthäi wrote:
 I think I've found a serious bug in the vserver image for amd64.
 We're running a daemon, which is logging the traffic of all 
 hostmachines. Now I've found a very big mistake in the 
 /proc/virtual/id/cacct interface.

Known. Can be fixed with the first stable update, not security relevant.

Available patch, needs to be fixed to avoid abi change (use atomic_t and crop
at the printf):

diff -Nurp linux-2.6.19.2-vs2.2.0-rc9/include/linux/vserver/cacct_def.h 
linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vserver/cacct_def.h
--- linux-2.6.19.2-vs2.2.0-rc9/include/linux/vserver/cacct_def.h
2007-01-11 18:10:53.0 +0100
+++ linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vserver/cacct_def.h 
2007-02-02 18:17:38.0 +0100
@@ -6,8 +6,8 @@
 
 
 struct _vx_sock_acc {
-   atomic_t count;
-   atomic_t total;
+   atomic_long_t count;
+   atomic_long_t total;
 };
 
 /* context sub struct */
@@ -30,9 +30,9 @@ static inline void __dump_vx_cacct(struc
 
printk(\t [%d] =, i);
for (j=0; j3; j++) {
-   printk( [%d] = %8d, %8d, j,
-   atomic_read(ptr[j].count),
-   atomic_read(ptr[j].total));
+   printk( [%d] = %8ld, %8ld, j,
+   atomic_long_read(ptr[j].count),
+   atomic_long_read(ptr[j].total));
}
printk(\n);
}
diff -Nurp linux-2.6.19.2-vs2.2.0-rc9/include/linux/vs_socket.h 
linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vs_socket.h
--- linux-2.6.19.2-vs2.2.0-rc9/include/linux/vs_socket.h2007-01-11 
18:10:52.0 +0100
+++ linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vs_socket.h 
2007-02-02 18:18:14.0 +0100
@@ -38,8 +38,8 @@ static inline void __vx_acc_sock(struct 
if (vxi) {
int type = vx_sock_type(family);
 
-   atomic_inc(vxi-cacct.sock[type][pos].count);
-   atomic_add(size, vxi-cacct.sock[type][pos].total);
+   atomic_long_inc(vxi-cacct.sock[type][pos].count);
+   atomic_long_add(size, vxi-cacct.sock[type][pos].total);
}
 }
 
Bastian

-- 
Without freedom of choice there is no creativity.
-- Kirk, The return of the Archons, stardate 3157.4



Processed (with 1 errors): Re: Bug#412132: cacct interface misscalced about 100 TB

2007-02-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 412132 important
Bug#412132: cacct interface misscalced about 100 TB
Severity set to `important' from `serious'

 user debian-kernel@lists.debian.org
Setting user to debian-kernel@lists.debian.org (was [EMAIL PROTECTED]).
 usertag dkt-waiting-etch-update
Unknown command or malformed arguments to command.

 tags 412132 +patch
Bug#412132: cacct interface misscalced about 100 TB
There were no tags set.
Tags added: patch

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#412139: linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root

2007-02-23 Thread Bastian Blank
severity 412139 important
tags 412139 moreinfo
thanks

On Sat, Feb 24, 2007 at 12:08:26AM +0100, Michael Rasmussen wrote:
 After latest upgrade of 2.6.18-4-686 my machine stops booting when reasing to 
 the message: Waiting for root.

Which kernel worked?

 The disk is found but just before finding disk on system I see this error 
 message from udev: udevd[411]: Illegal subsystem (or something like that). 
 Then complains of an error in /etc/udev/rules.d/udev.rules on line 61

This line shows in my udev version:
| KERNEL==umad*,NAME=infiniband/%k

Which udev version do you use?

Bastian

-- 
A princess should not be afraid -- not with a brave knight to protect her.
-- McCoy, Shore Leave, stardate 3025.3


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: Re: Bug#412139: linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root

2007-02-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 412139 important
Bug#412139: linux-image-2.6.18-4-686: Not booting. Hangs with message waiting 
for root
Severity set to `important' from `grave'

 tags 412139 moreinfo
Bug#412139: linux-image-2.6.18-4-686: Not booting. Hangs with message waiting 
for root
There were no tags set.
Tags added: moreinfo

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#326602: marked as done (linux-image-2.6.12-1-powerpc: [powerpc] ramdomly switches off)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 00:42:40 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#326602
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-image-2.6.12-1-powerpc
Version: 2.6.12-5
Severity: important

There seems to be a serious bug (might be related to pmu) in 2.6.12.

Reports in debian-powerpc mailing list mention that the problem did not exist
in previous versions of the kernel (2.6.8/2.6.9) but it is present in 2.6.12

The machine (ibook g4 12) randomly switches off forcing a restart of the
system and loosing any data of the open application.

Seems to be related to pmu since when powered on the date shows back to 1904
(if i remember right).

Today it happened when i unplugged the computer from the power suply and went
on battery. I noticed that the framebuffer did not answer to raise the bright
level (fn-f2) key, and few seconds after it died on me.

If more info is needed, please, request.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-powerpc
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.12-1-powerpc depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  initrd-tools  0.1.82 tools to create initrd image for p
ii  mkvmlinuz 13 create a kernel to boot a PowerPC 
ii  module-init-tools 3.2-pre8-1 tools for managing Linux kernel mo

linux-image-2.6.12-1-powerpc recommends no packages.

-- no debconf information

-- 
Jesus Climent  info:www.pumuki.org
Unix SysAdm|Linux User #66350|Debian Developer|2.6.12|Helsinki Finland
GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429  7E18 66FC 1D7F 8694 6D69


---End Message---
---BeginMessage---
No response from submitter, closing.

Bastian

-- 
Earth -- mother of the most beautiful women in the universe.
-- Apollo, Who Mourns for Adonais? stardate 3468.1
---End Message---


Bug#412143: linux-2.6 - vserver patch allows renice of processes in different context

2007-02-23 Thread Bastian Blank
Package: linux-2.6
Version: 2.6.18.dfsg.1-11
Severity: serious
Tags: security patch
User: debian-kernel@lists.debian.org
Usertags: dkt-waiting-etch-security-update

The included version of the vserver patch allows contexts to renice
processes in other contexts. See patch.

diff -NurpP linux-2.6.19.3-vs2.2.0-rc13.3/kernel/pid.c 
linux-2.6.19.3-vs2.2.0-rc13.4/kernel/pid.c
--- linux-2.6.19.3-vs2.2.0-rc13.3/kernel/pid.c  2006-12-04 01:47:02 +0100
+++ linux-2.6.19.3-vs2.2.0-rc13.4/kernel/pid.c  2007-02-23 00:30:28 +0100
@@ -286,6 +286,9 @@ void fastcall transfer_pid(struct task_s
 struct task_struct * fastcall pid_task(struct pid *pid, enum pid_type type)
 {
struct task_struct *result = NULL;
+
+   if (type == PIDTYPE_REALPID)
+   type = PIDTYPE_PID;
if (pid) {
struct hlist_node *first;
first = rcu_dereference(pid-tasks[type].first);
@@ -300,11 +303,17 @@ struct task_struct * fastcall pid_task(s
  */
 struct task_struct *find_task_by_pid_type(int type, int nr)
 {
+   struct task_struct *task;
+
if (type == PIDTYPE_PID)
nr = vx_rmap_pid(nr);
-   else if (type == PIDTYPE_REALPID)
-   type = PIDTYPE_PID;
-   return pid_task(find_pid(nr), type);
+
+   task = pid_task(find_pid(nr), type);
+   if (task  (type != PIDTYPE_REALPID) 
+   /* maybe VS_WATCH_P in the future? */
+   !vx_check(task-xid, VS_WATCH|VS_IDENT))
+   return NULL;
+   return task;
 }
 
 EXPORT_SYMBOL(find_task_by_pid_type);
diff -NurpP linux-2.6.19.3-vs2.2.0-rc13.3.1/include/linux/pid.h 
linux-2.6.19.3-vs2.2.0-rc13.4/include/linux/pid.h
--- linux-2.6.19.3-vs2.2.0-rc13.3.1/include/linux/pid.h 2006-11-08 04:57:52 
+0100
+++ linux-2.6.19.3-vs2.2.0-rc13.4/include/linux/pid.h   2007-02-22 18:09:39 
+0100
@@ -105,7 +105,8 @@ static inline pid_t pid_nr(struct pid *p
struct pid *pid___ = find_pid(who); \
if (pid___ != NULL) \
hlist_for_each_entry_rcu((task), pos___,\
-   pid___-tasks[type], pids[type].node) {
+   pid___-tasks[type], pids[type].node)  \
+   if (vx_check((task)-xid, VS_WATCH_P|VS_IDENT)) {
 
 #define while_each_task_pid(who, type, task)   \
}   \
@@ -124,7 +124,8 @@ static inline pid_t pid_nr(struct pid *p
struct hlist_node *pos___;  \
if (pid != NULL)\
hlist_for_each_entry_rcu((task), pos___,\
-   pid-tasks[type], pids[type].node) {
+   pid-tasks[type], pids[type].node) \
+   if (vx_check((task)-xid, VS_WATCH_P|VS_IDENT)) {
 
 #define while_each_pid_task(pid, type, task)   \
}   \

Bastian

-- 
Power is danger.
-- The Centurion, Balance of Terror, stardate 1709.2


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#403479: marked as done (linux-image-2.6.18-3-k7 lacks the tda9887.ko module)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 00:41:14 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#403479
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-image
Version: 2.6.18-3-k7

The package don't have the tda9887.ko module. There is no advice in any 
changelog from that package and in previous versions of the package the 
module was there.


-- 
By

---End Message---
---BeginMessage---
tda9887 is no seperate module in 2.6.18. It is included into tuner.ko.

Bastian

-- 
The heart is not a logical organ.
-- Dr. Janet Wallace, The Deadly Years, stardate 3479.4
---End Message---


Bug#337974: marked as done (linux-image-2.6.12-1-k7: i2o controller probe failed err -110)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 00:44:50 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#337974
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---

Package: linux-image-2.6.12-1-k7
Version: 2.6.12-10
Severity: critical
Justification: breaks the whole system


Kernel hangs at boot after failing to init iop0:

...
iop0: get status timeout
iop0: reset rejected trying to clear
iop0: unable to clear (status=0xbe)
i2o controller probe failed err -110
[hang]

The very same system boots fine under 2.6.8, where it uses dpti instead
of iop.  The dpti driver on 2.6.12 looks like it issues the same messages
as it does under 2.6.8 (suggests that it is working properly), but
apparently iop steps in shortly thereafter and tries (unsuccessfully) to
take over.

My dmesg from 2.6.8:

...
Loading Adaptec I2O RAID: Version 2.4 Build 5go
Detecting Adaptec I2O RAID controllers...
ACPI: PCI interrupt :00:0b.1[A] - GSI 19 (level, low) - IRQ 185
Adaptec I2O RAID controller 0 at f887f000 size=10 irq=185
dpti: If you have a lot of devices this could take a few minutes.
dpti0: Reading the hardware resource table.
TID 008  Vendor: ADAPTEC  Device: AIC-7899 Rev: 0001
TID 009  Vendor: ADAPTEC  Device: AIC-7899 Rev: 0001
TID 010  Vendor: ADAPTEC  Device: AIC-7899 Rev: 0001
TID 011  Vendor: ADAPTEC  Device: AIC-7899 Rev: 0001
TID 518  Vendor: IBM  Device: DDYS-T18350N Rev: SA2A
TID 523  Vendor: ADAPTEC  Device: RAID-5   Rev: 370F
scsi2 : Vendor: Adaptec  Model: 3410SFW:370F
Vendor: IBM   Model: DDYS-T18350N  Rev: SA2A
Type:   Direct-Access  ANSI SCSI revision: 03
Vendor: ADAPTEC   Model: RAID-5Rev: 370F
Type:   Direct-Access  ANSI SCSI revision: 02

A grep for iop0 in my 2.6.8 dmesg produces no results.

I don't have a dmesg for 2.6.12, since the system won't boot.   :) 




-- System Information:
Debian Release: testing/unstable
 APT prefers testing
 APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.12-1-k7 depends on:
ii  coreutils [fileutils] 5.2.1-2.1  The GNU core utilities
ii  initrd-tools  0.1.84 tools to create initrd image for p
ii  module-init-tools 3.2-pre9-2 tools for managing Linux kernel mo

linux-image-2.6.12-1-k7 recommends no packages.

-- no debconf information


---End Message---
---BeginMessage---
No further informations provided by submitter, closing.

Please reopen with new informations if appropriate.

Bastian

-- 
No one wants war.
-- Kirk, Errand of Mercy, stardate 3201.7
---End Message---


Bug#314678: marked as done (chattr: Function not implemented)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 00:50:20 +0100
with message-id [EMAIL PROTECTED]
and subject line #314678: fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---

Package: kernel-patch-vserver
Version: 1.9.5.3
Severity: important

'chattr' causes the error message 'Function not implemented', which 
makes it impossible to 'vserver xx build' without workaround (i.e. 
turning of 'namespace').


cel600:/# uname -a
Linux cel600 2.6.8+vserver #1 Wed Jun 15 01:44:04 CEST 2005 i686 GNU/Linux

cel600:/# touch /home/helmut/test-attr
cel600:/# chattr -i /home/helmut/test-attr
chattr: Function not implemented while setting flags on 
/home/helmut/test-attr


cel600:# getpcaps 1
Capabilities for `1': =ep cap_setpcap-e

cel600:/# cat /boot/config-2.6.8+vserver | grep 'FS_XATTR'
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_REISERFS_FS_XATTR is not set
CONFIG_DEVPTS_FS_XATTR=y
# CONFIG_CIFS_XATTR is not set

cel600:/# cat /etc/mtab
/dev/hda7 / ext3 rw,user_xattr,errors=remount-ro 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs rw 0 0
/dev/hda8 /save ext3 rw,errors=remount-ro 0 0
usbfs /proc/bus/usb usbfs rw 0 0
tmpfs /dev tmpfs rw,size=10M,mode=0755 0 0
/dev/drbd0 /var/lib/vservers ext3 rw 0 0


The same on an unpatched kernel (stock Debian too):

xp2400:/# uname -a
Linux xp2400 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux

xp2400:/# lsattr /home/helmut/test-attr
- /home/helmut/test-attr
xp2400:/# chattr +i /home/helmut/test-attr
xp2400:/# lsattr /home/helmut/test-attr
i /home/helmut/test-attr

xp2400:/# getpcaps 1
Capabilities for `1': =ep cap_setpcap-e

xp2400:/boot# cat /boot/config-2.6.8-1-386 | grep 'FS_XATTR'
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_REISERFS_FS_XATTR is not set
CONFIG_DEVPTS_FS_XATTR=y
# CONFIG_CIFS_XATTR is not set

Helmut Wollmersdorfer



---End Message---
---BeginMessage---
This bug does not show up with current kernels.

Bastian

-- 
Is truth not truth for all?
-- Natira, For the World is Hollow and I have Touched
   the Sky, stardate 5476.4.
---End Message---


Bug#293195: marked as done (concurrent usage of snd_cmipci and sk98lin freezes system)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 00:45:50 +0100
with message-id [EMAIL PROTECTED]
and subject line #293195
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: kernel-image-2.6.10-1-k7
Version: 2.6.10-4
Severity: grave
Justification: causes non-serious data loss

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I have a Terratec Aureon 5.1 PCI sound card, and an on-board 3Com 3c940
gigabit ethernet controller (the board is an Asus A7V600). The sound
card uses the cmipci module, and the ethernet card the sk98lin module.

Playing sound and using the network at the same time freezes the sytem
after a short time (generally 15-30 seconds); nothing is logged or
displayed (I checked syslog, kern.log and /var/log/messages), it just
freezes everything, forcing a reset of the machine (and after the
subsequent reboot my mouse isn't recognized any more, but I don't think
that matters).

I did a memtest, but my memory seems to be ok.

This happens both with kernel-image-2.6.10-1-k7-4 and
kernel-image-2.6.9-2-k7-5; it does NOT happen with
kernel-image-2.6.8-2-k7-13.

Steps to reproduce (console, no X11 loaded):

alsaplayer -i text SOME MP3

(other console)

ncftp and download something.

I'm sorry I can't provide any more useful information, but I just have
no idea how to debug a frozen system :-(

Greetings,
Aaron

[EMAIL PROTECTED]:~# lsmod
Module  Size  Used by
nvidia   3464988  12
ipv6  262912  12
lp 11368  0
af_packet  22408  2
snd_cmipci 33440  3
snd_pcm_oss53668  0
snd_mixer_oss  20096  3 snd_pcm_oss
snd_pcm97224  2 snd_cmipci,snd_pcm_oss
snd_page_alloc  9924  1 snd_pcm
snd_opl3_lib   11200  1 snd_cmipci
snd_timer  25668  2 snd_pcm,snd_opl3_lib
snd_hwdep   9540  1 snd_opl3_lib
gameport4544  1 snd_cmipci
snd_mpu401_uart 7872  1 snd_cmipci
snd_rawmidi25120  1 snd_mpu401_uart
snd_seq_device  8716  2 snd_opl3_lib,snd_rawmidi
snd57188  12 
snd_cmipci,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore  10272  3 snd
pci_hotplug34160  0
via_agp 9472  1
agpgart34408  2 via_agp
tsdev   7616  0
mousedev   11480  2
psmouse21832  0
parport_pc 37828  1
parport37576  2 lp,parport_pc
floppy 60048  0
pcspkr  3560  0
rtc12664  0
evdev   9472  0
ehci_hcd   33028  0
uhci_hcd   33552  0
usbcore   121656  3 ehci_hcd,uhci_hcd
sk98lin   170984  1
capability  4680  0
commoncap   7808  1 capability
vsxxxaa 6464  0
it87   23268  0
eeprom  7576  0
i2c_sensor  3584  2 it87,eeprom
i2c_isa 1920  0
i2c_viapro  7500  0
i2c_core   22736  5 it87,eeprom,i2c_sensor,i2c_isa,i2c_viapro
ide_generic 1216  0 [permanent]
ide_cd 42564  0
cdrom  41116  1 ide_cd
via82cxxx  13468  0 [permanent]
ide_core  132236  3 ide_generic,ide_cd,via82cxxx
ext3  139528  2
jbd61336  1 ext3
mbcache 8516  1 ext3
sd_mod 18000  5
aic7xxx   212504  0
sata_via7300  3
libata 46596  1 sata_via
scsi_mod  129600  3 sd_mod,aic7xxx,libata
unix   28724  714
fbcon  38336  0
font8256  1 fbcon
bitblit 5568  1 fbcon
vesafb  7768  0
cfbcopyarea 3904  1 vesafb
cfbimgblt   2944  1 vesafb
cfbfillrect 3520  1 vesafb


[EMAIL PROTECTED]:~# lspci -
:00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host 
Bridge (rev 80)
Subsystem: Asustek Computer, Inc. A7V8X motherboard
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR-
Latency: 0
Region 0: Memory at f000 (32-bit, prefetchable) [size=128M]
Capabilities: [80] AGP version 3.5
Status: 

Bug#412132: cacct interface misscalced about 100 TB

2007-02-23 Thread Patrick Matthäi

Hi,

I'm sorry, normaly it shouldn't be a very important bug, but please 
think about these ones, who have to log the caused traffic, that's very 
terrible. So could you please add it to the next upload?


Regards, Patrick Matthäi


Bastian Blank schrieb:

severity 412132 important
user debian-kernel@lists.debian.org
usertag dkt-waiting-etch-update
tags 412132 +patch
thanks

On Fri, Feb 23, 2007 at 11:19:57PM +0100, Patrick Matthäi wrote:
  

I think I've found a serious bug in the vserver image for amd64.
We're running a daemon, which is logging the traffic of all 
hostmachines. Now I've found a very big mistake in the 
/proc/virtual/id/cacct interface.



Known. Can be fixed with the first stable update, not security relevant.

Available patch, needs to be fixed to avoid abi change (use atomic_t and crop
at the printf):

diff -Nurp linux-2.6.19.2-vs2.2.0-rc9/include/linux/vserver/cacct_def.h 
linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vserver/cacct_def.h
--- linux-2.6.19.2-vs2.2.0-rc9/include/linux/vserver/cacct_def.h
2007-01-11 18:10:53.0 +0100
+++ linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vserver/cacct_def.h 
2007-02-02 18:17:38.0 +0100
@@ -6,8 +6,8 @@
 
 
 struct _vx_sock_acc {

-   atomic_t count;
-   atomic_t total;
+   atomic_long_t count;
+   atomic_long_t total;
 };
 
 /* context sub struct */

@@ -30,9 +30,9 @@ static inline void __dump_vx_cacct(struc
 
 		printk(\t [%d] =, i);

for (j=0; j3; j++) {
-   printk( [%d] = %8d, %8d, j,
-   atomic_read(ptr[j].count),
-   atomic_read(ptr[j].total));
+   printk( [%d] = %8ld, %8ld, j,
+   atomic_long_read(ptr[j].count),
+   atomic_long_read(ptr[j].total));
}
printk(\n);
}
diff -Nurp linux-2.6.19.2-vs2.2.0-rc9/include/linux/vs_socket.h 
linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vs_socket.h
--- linux-2.6.19.2-vs2.2.0-rc9/include/linux/vs_socket.h2007-01-11 
18:10:52.0 +0100
+++ linux-2.6.19.2-vs2.2.0-rc9.longatomic/include/linux/vs_socket.h 
2007-02-02 18:18:14.0 +0100
@@ -38,8 +38,8 @@ static inline void __vx_acc_sock(struct 
 	if (vxi) {

int type = vx_sock_type(family);
 
-		atomic_inc(vxi-cacct.sock[type][pos].count);

-   atomic_add(size, vxi-cacct.sock[type][pos].total);
+   atomic_long_inc(vxi-cacct.sock[type][pos].count);
+   atomic_long_add(size, vxi-cacct.sock[type][pos].total);
}
 }
 
Bastian


  





Bug#365560: marked as done (linux-image-2.6.16-1-amd64-k8: Spontaneous reboots when playing audio)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 00:48:16 +0100
with message-id [EMAIL PROTECTED]
and subject line #365560
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-image-2.6.16-1-amd64-k8
Version: 2.6.16-10
Severity: important


The subject line says it all Spontaneous reboots when playing audio

I see no errors or logs, and it isn't reliably reproduceable.

This system is a Debian Sid up to date system, that doesn't run any programs 
not from the Debian archive

I've been seeing this problem for a long time, but I never could figure out 
what was the common factor

I'm not sure what information I need to give, but here is the output of 
/dev/sndstat

$ cat /dev/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.11rc2 emulation code)
Kernel: Linux TheMachine 2.6.16-1-amd64-k8 #2 Tue Apr 25 20:36:29 UTC 2006 
x86_64
Config options: 0

Installed drivers:
Type 10: ALSA emulation

Card config:
ALi M5455 with ALC850 at 0x0, irq 201
MPU-401 UART at 0x330, irq 5

Audio devices:
0: ALi M5455 (DUPLEX)

Synth devices: NOT ENABLED IN CONFIG

Midi devices:
1: MPU-401 UART MIDI

Timers:
7: system timer

Mixers:
0: Realtek ALC850 rev 0
1: mixer10




-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-amd64-k8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-image-2.6.16-1-amd64-k8 depends on:
ii  e2fsprogs 1.38+1.39-WIP-2006.04.09-1 ext2 file system utilities and lib
ii  initramfs-too 0.60   tools for generating an initramfs
ii  module-init-t 3.2.2-2tools for managing Linux kernel mo

linux-image-2.6.16-1-amd64-k8 recommends no packages.

-- debconf information:
  linux-image-2.6.16-1-amd64-k8/postinst/old-dir-initrd-link-2.6.16-1-amd64-k8: 
true
  linux-image-2.6.16-1-amd64-k8/preinst/elilo-initrd-2.6.16-1-amd64-k8: true
  linux-image-2.6.16-1-amd64-k8/preinst/lilo-has-ramdisk:
  linux-image-2.6.16-1-amd64-k8/preinst/abort-install-2.6.16-1-amd64-k8:
  linux-image-2.6.16-1-amd64-k8/postinst/depmod-error-2.6.16-1-amd64-k8: false
  linux-image-2.6.16-1-amd64-k8/postinst/depmod-error-initrd-2.6.16-1-amd64-k8: 
false
  linux-image-2.6.16-1-amd64-k8/preinst/abort-overwrite-2.6.16-1-amd64-k8:
* linux-image-2.6.16-1-amd64-k8/preinst/already-running-this-2.6.16-1-amd64-k8:
  linux-image-2.6.16-1-amd64-k8/postinst/old-system-map-link-2.6.16-1-amd64-k8: 
true
  linux-image-2.6.16-1-amd64-k8/preinst/initrd-2.6.16-1-amd64-k8:
  linux-image-2.6.16-1-amd64-k8/preinst/bootloader-initrd-2.6.16-1-amd64-k8: 
true
  linux-image-2.6.16-1-amd64-k8/postinst/create-kimage-link-2.6.16-1-amd64-k8: 
true
  linux-image-2.6.16-1-amd64-k8/postinst/kimage-is-a-directory:
  linux-image-2.6.16-1-amd64-k8/postinst/bootloader-error-2.6.16-1-amd64-k8:
  
linux-image-2.6.16-1-amd64-k8/prerm/removing-running-kernel-2.6.16-1-amd64-k8: 
true
  
linux-image-2.6.16-1-amd64-k8/prerm/would-invalidate-boot-loader-2.6.16-1-amd64-k8:
 true
  linux-image-2.6.16-1-amd64-k8/preinst/overwriting-modules-2.6.16-1-amd64-k8: 
true
  
linux-image-2.6.16-1-amd64-k8/preinst/failed-to-move-modules-2.6.16-1-amd64-k8:
  linux-image-2.6.16-1-amd64-k8/postinst/old-initrd-link-2.6.16-1-amd64-k8: true
  linux-image-2.6.16-1-amd64-k8/preinst/lilo-initrd-2.6.16-1-amd64-k8: true
  
linux-image-2.6.16-1-amd64-k8/postinst/bootloader-test-error-2.6.16-1-amd64-k8:

---End Message---
---BeginMessage---
Close as unreproduced and no new informations.

Bastian

-- 
She won' go Warp 7, Cap'n!  The batteries are dead!
---End Message---


Processed: severity of 412122 is important

2007-02-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.27
 severity 412122 important
Bug#412122: network adapter (BCM 5704s) not working with kernel 2.6.8-12 
Severity set to `important' from `grave'


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#412132: cacct interface misscalced about 100 TB

2007-02-23 Thread Bastian Blank
On Sat, Feb 24, 2007 at 12:48:20AM +0100, Patrick Matthäi wrote:
 I'm sorry, normaly it shouldn't be a very important bug, but please 
 think about these ones, who have to log the caused traffic, that's very 
 terrible. So could you please add it to the next upload?

I do, but I have to prioritize them.

Bastian

-- 
Kirk to Enterprise -- beam down yeoman Rand and a six-pack.



Bug#412139: linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root

2007-02-23 Thread Michael Rasmussen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, 24 Feb 2007 00:27:25 +0100
Bastian Blank [EMAIL PROTECTED] wrote:

 tags 412139 moreinfo
I don't know if this is important, but the 2.6.18-3 kernel apparently
probes the ide interface in a different order that 2.6.18-4.dsfg-11

2.6.18-3:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ICH2: IDE controller at PCI slot :00:1f.1
ICH2: chipset revision 18
ICH2: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x2480-0x2487, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x2488-0x248f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
not related
usbcore: registered new driver usbfs
usbcore: registered new driver hub
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
USB Universal Host Controller Interface driver v3.0
/not related
hda: WDC WD200BB-60CVB0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: LITE-ON DVDRW SOHW-1213S, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15

2.6.18-4:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
below not seen
ICH2: IDE controller at PCI slot :00:1f.1
ICH2: chipset revision 18
ICH2: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x2480-0x2487, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x2488-0x248f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
usbcore: registered new driver usbfs
usbcore: registered new driver hub
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
USB Universal Host Controller Interface driver v3.0
/below not seen
below the order has changed
hda: WDC WD200BB-60CVB0, ATA DISK drive
hdc: LITE-ON DVDRW SOHW-1213S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
/below the order has changed
below not seen
Probing IDE interface ide1...
/below not seen


- -- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael at rasmussen dot cc
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xD3C9A00E
mir at datanom dot net
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE501F51C
mir at miras dot org
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE3E80917
- --
Bubba Blue: You ever been on a real SHRIMP boat? 
Forrest Gump: No - but I been on a real BIG boat 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF34KBQQOPluUB9RwRAlyAAKDEua4NC0WgP0XTDT8aYWd5BKnN/wCgsFae
XjDnQ2h+ZPG0JA6RJpmR4og=
=rTJA
-END PGP SIGNATURE-


Bug#412139: Fw: Bug#412139: linux-image-2.6.18-4-686: Not booting. Hangs with message waiting for root

2007-02-23 Thread Michael Rasmussen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Begin forwarded message:

Date: Sat, 24 Feb 2007 00:41:26 +0100
From: Michael Rasmussen [EMAIL PROTECTED]
To: Bastian Blank [EMAIL PROTECTED]
Subject: Re: Bug#412139: linux-image-2.6.18-4-686: Not booting. Hangs
with message waiting for root


- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, 24 Feb 2007 00:27:25 +0100
Bastian Blank [EMAIL PROTECTED] wrote:

 
 On Sat, Feb 24, 2007 at 12:08:26AM +0100, Michael Rasmussen wrote:
  After latest upgrade of 2.6.18-4-686 my machine stops booting when
  reasing to the message: Waiting for root.
 
 Which kernel worked?
Running this version before: linux-2.6 2.6.18.dfsg.1-10
which worked.
Now running backup kernel:
$ dpkg -s linux-image-2.6.18-3-686
Package: linux-image-2.6.18-3-686
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 49592
Maintainer: Debian Kernel Team debian-kernel@lists.debian.org
Architecture: i386
Source: linux-2.6
Version: 2.6.18-8

 
  The disk is found but just before finding disk on system I see this
  error message from udev: udevd[411]: Illegal subsystem (or
  something like that). Then complains of an error
  in /etc/udev/rules.d/udev.rules on line 61
 
 This line shows in my udev version:
 | KERNEL==umad*,NAME=infiniband/%k
 
My udev contains the same.

 Which udev version do you use?
 
$ dpkg -s udev
Package: udev
Status: install ok installed
Priority: important
Section: admin
Installed-Size: 892
Maintainer: Marco d'Itri [EMAIL PROTECTED]
Architecture: i386
Version: 0.105-1

- - -- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael at rasmussen dot cc
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xD3C9A00E
mir at datanom dot net
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE501F51C
mir at miras dot org
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE3E80917
- - --
THIS time it really is fixed. I mean, how many times can we
 get it wrong? At some point, we just have to run out of really 
 bad ideas..

- Linus Torvalds
- -BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF33uqQQOPluUB9RwRAn4CAKCucfHCtkEbqMJJ3F6O6i7x/z4biACg2L82
HaTOUdfJJ8nUFvF1tzMHP8I=
=hxsP
- -END PGP SIGNATURE-


- -- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael at rasmussen dot cc
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xD3C9A00E
mir at datanom dot net
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE501F51C
mir at miras dot org
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE3E80917
- --
Q:  Why did the programmer call his mother long distance?
A:  Because that was her name.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF34KUQQOPluUB9RwRArlWAKDOlIAuCS7+H5eItORC/3/FtcIllACfaRDr
Ww1xMwDlY7/TCoUfKIkJ5tE=
=CB8Q
-END PGP SIGNATURE-


Processed: Re: #406915

2007-02-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 406915 important
Bug#406915: access to large RAID arrays on Adaptec 2400A RAID controller with 
dpt_i2o module causes system hang
Severity set to `important' from `critical'

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#406915: #406915

2007-02-23 Thread Bastian Blank
severity 406915 important
thanks

The i2o subsystem seems to be mostly dead. Only interface changes was
propagated.

Bastian

-- 
You can't evaluate a man by logic alone.
-- McCoy, I, Mudd, stardate 4513.3


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#378449: marked as done (linux-image-2.6.16-2-amd64-generic: amd64 package should be build for arch i386 too)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:19:23 +0100
with message-id [EMAIL PROTECTED]
and subject line fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-image-2.6.16-2-amd64-generic
Version: 2.6.16-16
Severity: wishlist

Hello,


it would be nice to have all the amd64 packages on arch i386 too for
installations with 64 bit kernel and 32 bit userland.


Regards,
Torsten

---End Message---
---BeginMessage---
Version: 2.6.18.dfsg.1-10

Fixed.

-- 
A little suffering is good for the soul.
-- Kirk, The Corbomite Maneuver, stardate 1514.0
---End Message---


Bug#405187: marked as done (Please provide xen-vserver flavour for k7)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:15:05 +0100
with message-id [EMAIL PROTECTED]
and subject line #405187
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-2.6
Severity: wishlist

Please provide a flavour -xen-vserver-k7.

Greetings
Martin

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (1003, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

---End Message---
---BeginMessage---
No k7 flavour for xen anymore. Closing.

Bastian

-- 
No one wants war.
-- Kirk, Errand of Mercy, stardate 3201.7
---End Message---


Bug#372726: marked as done (Please make linux-image-2.6-xen-vserver-k7)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:20:07 +0100
with message-id [EMAIL PROTECTED]
and subject line no xen k7
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-2.6
Version: 2.6.16-14
Severity: wishlist

Hi there, thanks for your work.

I see 
linux-image-2.6-xen-686
linux-image-2.6-xen-k7
linux-image-2.6-xen-vserver-686
but no linux-image-2.6-xen-vserver-k7

Is there any problem with linux+xen+vserver optimized for k7?
If no, please build it for k7 too %)

Regards, Alexander.


-- System Information:
Debian Release: 3.1
  APT prefers proposed-updates
  APT policy: (670, 'proposed-updates'), (670, 'stable'), (620, 
'testing-proposed-updates'), (620, 'testing'), (600, 'unstable'), (550, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-2-vserver-k7
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages linux-image-2.6.16-2-vserver-k7 depends on:
ii  initramfs-tools [linux-initra 0.60   tools for generating an initramfs
ii  module-init-tools 3.2.2-3tools for managing Linux kernel mo

Versions of packages linux-image-2.6.16-2-vserver-k7 recommends:
ii  libc6-i6862.3.6-13   GNU C Library: Shared libraries [i

-- debconf information:
  
linux-image-2.6.16-2-vserver-k7/prerm/would-invalidate-boot-loader-2.6.16-2-vserver-k7:
 true
  linux-image-2.6.16-2-vserver-k7/preinst/initrd-2.6.16-2-vserver-k7:
  linux-image-2.6.16-2-vserver-k7/postinst/kimage-is-a-directory:
  linux-image-2.6.16-2-vserver-k7/preinst/abort-overwrite-2.6.16-2-vserver-k7:
  
linux-image-2.6.16-2-vserver-k7/preinst/failed-to-move-modules-2.6.16-2-vserver-k7:
  linux-image-2.6.16-2-vserver-k7/preinst/lilo-initrd-2.6.16-2-vserver-k7: true
  linux-image-2.6.16-2-vserver-k7/preinst/abort-install-2.6.16-2-vserver-k7:
  linux-image-2.6.16-2-vserver-k7/postinst/depmod-error-2.6.16-2-vserver-k7: 
false
  
linux-image-2.6.16-2-vserver-k7/preinst/already-running-this-2.6.16-2-vserver-k7:
  
linux-image-2.6.16-2-vserver-k7/postinst/depmod-error-initrd-2.6.16-2-vserver-k7:
 false
  
linux-image-2.6.16-2-vserver-k7/postinst/old-dir-initrd-link-2.6.16-2-vserver-k7:
 true
  
linux-image-2.6.16-2-vserver-k7/preinst/overwriting-modules-2.6.16-2-vserver-k7:
 true
  linux-image-2.6.16-2-vserver-k7/preinst/elilo-initrd-2.6.16-2-vserver-k7: true
  
linux-image-2.6.16-2-vserver-k7/preinst/bootloader-initrd-2.6.16-2-vserver-k7: 
true
  linux-image-2.6.16-2-vserver-k7/postinst/bootloader-error-2.6.16-2-vserver-k7:
  linux-image-2.6.16-2-vserver-k7/postinst/old-initrd-link-2.6.16-2-vserver-k7: 
true
  
linux-image-2.6.16-2-vserver-k7/prerm/removing-running-kernel-2.6.16-2-vserver-k7:
 true
  
linux-image-2.6.16-2-vserver-k7/postinst/bootloader-test-error-2.6.16-2-vserver-k7:
  linux-image-2.6.16-2-vserver-k7/preinst/lilo-has-ramdisk:
  
linux-image-2.6.16-2-vserver-k7/postinst/old-system-map-link-2.6.16-2-vserver-k7:
 true
  
linux-image-2.6.16-2-vserver-k7/postinst/create-kimage-link-2.6.16-2-vserver-k7:
 true

---End Message---
---BeginMessage---
There are no xen k7 variants anymore.

-- 
Pain is a thing of the mind.  The mind can be controlled.
-- Spock, Operation -- Annihilate! stardate 3287.2
---End Message---


Bug#347468: marked as done (ipw2200 in linux-image-2.6.15-1-686 lacks monitor mode)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:25:59 +0100
with message-id [EMAIL PROTECTED]
and subject line fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-image-2.6.15-1-686
Version: 2.6.15-1

I upgraded to linux-image-2.6.15-1-686 and found that kismet no longer
worked.  Neither could I set the card into monitor mode via iwconfig or
airmon.  It's an ipw2915, which has worked more or less with various
ipw2200 drivers until today.

A quick check revealed that the ipw2200 driver had not been compiled
with Monitor mode support...it looks like this is set as an option in
the config file.  No idea why it didn't result in a module with monitor
mode support ...but I was able to get monitor mode by installing the
ipw2200-source package, editing ipw2200.c and putting
#define CONFIG_IPW2200_MONITOR
at the top and using module-assistant to make a new module.  Which is
probably not the brightest thing in the world but it works again.

Debian unstable.

---End Message---
---BeginMessage---
Monitor mode is enabled since some time.

-- 
Women professionals do tend to over-compensate.
-- Dr. Elizabeth Dehaver, Where No Man Has Gone Before,
   stardate 1312.9.
---End Message---


Bug#358617: marked as done (linux-image-2.6.16-1-686: please enable CONFIG_IPW2200_MONITOR=y)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:23:41 +0100
with message-id [EMAIL PROTECTED]
and subject line fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-image-2.6.16-1-686
Version: 2.6.16-2
Severity: wishlist

Hello,

the ipw2200 module in the kernel doesn't have the monitor mode enabled.
It should be enabled like the one for ipw2100 but trying to enable it via
menuconfig on a vanilla .16 kernel doesn't allow this option.
But it is in the code

linux-2.6.16/drivers/net/wireless/ipw2200.c


#ifdef CONFIG_IPW2200_MONITOR
case IW_MODE_MONITOR:
rc = ipw_get_fw(priv, ucode,
IPW_FW_NAME(sniffer_ucode));


Is it a upstream bug?

Thank you.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.16-1-686 depends on:
ii  module-init-tools 3.2.2-2tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-8   Yet Another mkInitRD

Versions of packages linux-image-2.6.16-1-686 recommends:
ii  libc6-i6862.3.6-4GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.16-1-686/preinst/initrd-2.6.16-1-686:
  linux-image-2.6.16-1-686/postinst/create-kimage-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.16-1-686/prerm/removing-running-kernel-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/old-dir-initrd-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/depmod-error-initrd-2.6.16-1-686: false
  linux-image-2.6.16-1-686/preinst/lilo-initrd-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/old-system-map-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.16-1-686/preinst/bootloader-initrd-2.6.16-1-686: true
  linux-image-2.6.16-1-686/preinst/already-running-this-2.6.16-1-686:
* linux-image-2.6.16-1-686/preinst/overwriting-modules-2.6.16-1-686: false
  linux-image-2.6.16-1-686/postinst/old-initrd-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/preinst/abort-overwrite-2.6.16-1-686:
  linux-image-2.6.16-1-686/postinst/depmod-error-2.6.16-1-686: false
  linux-image-2.6.16-1-686/preinst/failed-to-move-modules-2.6.16-1-686:
  linux-image-2.6.16-1-686/preinst/elilo-initrd-2.6.16-1-686: true
  linux-image-2.6.16-1-686/prerm/would-invalidate-boot-loader-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/bootloader-error-2.6.16-1-686:
  linux-image-2.6.16-1-686/preinst/abort-install-2.6.16-1-686:
  linux-image-2.6.16-1-686/postinst/bootloader-test-error-2.6.16-1-686:

---End Message---
---BeginMessage---
This bug was fixed.

-- 
There are always alternatives.
-- Spock, The Galileo Seven, stardate 2822.3
---End Message---


Bug#296808: marked as done (kernel-source-2.6.10: Please consider enabling reiserfs extended attributes(posix acls))

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:27:18 +0100
with message-id [EMAIL PROTECTED]
and subject line fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: kernel-source-2.6.10
Version: 2.6.10-5
Severity: wishlist

Enabling the reiserfs extended attributes would be greatly appreciated, i see 
that this has been enabled on ext2/3. I do not know if this can break anything, 
but please consider it.

Thank You,
Jonathan

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-k7
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)

Versions of packages kernel-source-2.6.10 depends on:
ii  binutils  2.15-5 The GNU assembler, linker and bina
ii  bzip2 1.0.2-5high-quality block-sorting file co
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities

-- no debconf information

---End Message---
---BeginMessage---
reiserfs extended attribute and posix acl support is enabled since some
time.

-- 
We'll pivot at warp 2 and bring all tubes to bear, Mr. Sulu!
---End Message---


Bug#304507: marked as done (kernel-source-2.6.11: please apply the evms bd-claim patch to debian kernel sources)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:32:26 +0100
with message-id [EMAIL PROTECTED]
and subject line supported
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: kernel-source-2.6.11
Severity: wishlist
Tags: patch

In kernel 2.6, a patch was added to the system to allow a block device
driver to claim an entire device as its own.  That well meaning change
has been a bane to everyone trying to migrate from hard partition support
to using the device mapper with lvm2 or evms.  If you're trying to bring
up a system that has /dev/hda1 mounted, you can't create any logical
volumes in the free space.

Unfortunately, since we can't do native EVMS yet in the debian installer
(the udeb is there, but there's no d-i support), the only way to bring
up EVMS on a new machine is to install a small debian partition, bring
up a new kernel  evms, and then patch things in.  The biggest pain in
that is having to bring in a patched up-to-date kernel so we can be
running on /dev/hda1 while formatting the rest of the bloody system.

Please consider my plea, I've been stuck playing this game 4 times in
the past year and it's getting seriously un-fun.  I don't care if you
want to put it on a kernel command-line switch so only people in the
know run the risk of shooting themselves in the foot.. but frankly, we
lived with the old behavior up until 2.6, so it's clearly not all that
critical.

Thanks,

Paul







-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
bd-claim

A patch was merged between 2.6.0-test3 and -test4 that breaks EVMS on many
systems by not allowing Device-Mapper to activate DM devices on top of disks
that also contain mounted partitions.

More specifically, the kernel has its own partitioning code that runs when the
kernel boots, and provides the traditional partition devices (e.g. /dev/hda1).
When a filesystem mounts one of these partitions, the filesystem claims that
partition and no one else can claim it. When this happens, the kernel's
partitioning code (not the filesystem code) also claims the underlying disk,
meaning that disk is only available for use by the kernel's built-in
partitions on that disk. Other filesystems may mount other partitions on that
disk, but the disk itself is owned by the partitioning code.

However, in order to allow easy management of partitions, EVMS does its own
partition detection, and creates devices to represent those partitions using
Device-Mapper (not the kernel's built-in partitioning code). When DM creates a
device, it also attempts to claim the underlying devices (in this case the
disk that holds the partition). But, if the user has already mounted one of
the kernel's built-in partitions on that same disk, then the disk will already
have been claimed. DM will be unable to claim it, and the DM device activation
will fail.

The end result is that a single disk cannot be used both for EVMS and for
mounting the kernel's built-in partitions. 

There are three solutions to this problem.

1. Switch to using EVMS for *all* your volumes and partitions. If none of the
   kernel's built-in partitions are mounted, then there won't be any conflicts
   when DM tries to claim the disks. This is, of course, the preferred
   solution, but also requires some extra work on your part to convert to
   mounting your root filesystem using an EVMS volume. Please see
   http://evms.sf.net/install/root.html and http://evms.sf.net/convert.html
   for more details on this option.

2. Tell EVMS to exclude any disks that contain partitions that you are going
   to mount using the kernel's built-in partitions. You can do this by adding
   the names of these disks to the sysfs_devices.exclude line in your
   /etc/evms.conf file. If you choose this option, EVMS will completely ignore
   the specified disks and not discover any of the partitions or volumes on
   those disks.

3. Apply this patch, which will is a reversal of the patch that prevents
   Device-Mapper and the kernel's built-in partitions from using the same disk
   at the same time. This patch is not supported by the kernel community, and
   in fact removes functionality that they specifically added. However, it
   will allow you to share your disks between EVMS and the kernel's built-in
   partitioning code, if that's the choice you wish to make for your system.

   cd /usr/src/linux-2.6.10/
   

Bug#304507: wontfix

2007-02-23 Thread Bastian Blank
tags 304507 wontfix
thanks

The bd_claim patch was never accepted upstream.

Bastian

-- 
In the strict scientific sense we all feed on death -- even vegetarians.
-- Spock, Wolf in the Fold, stardate 3615.4


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: wontfix

2007-02-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tags 304507 wontfix
Bug#304507: kernel-source-2.6.11: please apply the evms bd-claim patch to 
debian kernel sources
Tags were: patch
Tags added: wontfix

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#329047: marked as done (linux-image-2.6.12-1-k7: please enable CONFIG_REISERFS_FS_XATTR (and inotify))

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:27:55 +0100
with message-id [EMAIL PROTECTED]
and subject line fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-image-2.6.12-1-k7
Version: 2.6.12-6
Severity: wishlist

I would like CONFIG_REISERFS_FS_XATTR to be enabled so that the beagle
desktop search and indexing daemon is faster. Also, when 2.6.13 is
uploaded, be sure to enable inotify support, at least on i486.

See here for details of why:
http://beaglewiki.org/Enabling_Extended_Attributes
http://beaglewiki.org/Inotify_Kernel

-- System Information:
Debian Release: unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.12-1-k7 depends on:
ii  coreutils [fileutils] 5.2.1-2.1  The GNU core utilities
ii  initrd-tools  0.1.82 tools to create initrd image for p
ii  module-init-tools 3.2-pre8-1 tools for managing Linux kernel mo

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
---End Message---
---BeginMessage---
This was fixes some time ago.

-- 
Insults are effective only where emotion is present.
-- Spock, Who Mourns for Adonais?  stardate 3468.1
---End Message---


Bug#348392: marked as done ([wishlist] Support for 16 CPUs and 8GB of RAM)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:25:18 +0100
with message-id [EMAIL PROTECTED]
and subject line fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: linux-image-2.6.15-1-686-smp
Severity: wishlist

Hello

I have a Quad-Dualcore-Hyperthreading Dell 6850 Server with 8GB RAM and
even the latest Sid kernel image only supports only half of the CPU and
the RAM. Are these options really so expensive that one should use them
by default? At the time where Etch gets released 8GB RAM probably isn't
Science Fiction any more :)

  /boot/config-2.6.15-1-686-smp
CONFIG_NR_CPUS=8
CONFIG_HIGHMEM4G=y

bye,

-christian-

---End Message---
---BeginMessage---
We provide a PAE version since some time. So this is fixed.

Bastian

-- 
Not one hundred percent efficient, of course ... but nothing ever is.
-- Kirk, Metamorphosis, stardate 3219.8
---End Message---


Processed: tagging 303490

2007-02-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.26
 tags 303490 moreinfo
Bug#303490: tulip driver doesn't open loop on Apple 100BaseT ethernet card
There were no tags set.
Tags added: moreinfo


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#303490: marked as done (tulip driver doesn't open loop on Apple 100BaseT ethernet card)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:42:13 +0100
with message-id [EMAIL PROTECTED]
and subject line no bug
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: kernel-image-2.6.10-powerpc
Version: 2.6.10-2
Severity: important

The tulip driver should open the loopback on the Apple 100BaseT ethernet
card when bringing up the interface. Otherwise the interface is unusable
for normal traffic. This can be done by writing 0x10f and 0x3 to CSR12.
It's probably wise to check for the apple OUI first as other cards might
use the GPIO pins for other purposes. The apple OUI is 00:05:02.
Additionally you can check for the chip type being 21140, as apple
never made cards with other tulip family chips.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.9-ans
Locale: LANG=C, LC_CTYPE=C

Versions of packages kernel-image-2.6.10-powerpc depends on:
ii  initrd-tools  0.1.77 tools to create initrd image for p
ii  mkvmlinuz 12 create a kernel to boot a PowerPC 
ii  module-init-tools 3.0-pre5-1 tools for managing Linux kernel mo

-- no debconf information

---End Message---
---BeginMessage---
It is no bug in the kernel to now provide a given optional interface per
default.

Bastian

-- 
There are always alternatives.
-- Spock, The Galileo Seven, stardate 2822.3
---End Message---


Bug#303491: marked as done (MACE not detected by kernel/initrd)

2007-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2007 01:39:41 +0100
with message-id [EMAIL PROTECTED]
and subject line no response
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: kernel-image-2.6.10-powerpc
Version: 2.6.10-2
Severity: important

The onboard MACE ethernet MAC of the ANS is not detected by the
kernel/initrd. As a result the MACE driver module is not loaded. The
MACE ethernet MAC is part of the grand central ASIC and lives at address 
0xf3008200 - 0xf30083ff and 0xf3011000-0xf3011fff. It uses IRQ 14 and
IRQ 2 and 3 for TX and RX DMA.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.9-ans
Locale: LANG=C, LC_CTYPE=C

Versions of packages kernel-image-2.6.10-powerpc depends on:
ii  initrd-tools  0.1.77 tools to create initrd image for p
ii  mkvmlinuz 12 create a kernel to boot a PowerPC 
ii  module-init-tools 3.0-pre5-1 tools for managing Linux kernel mo

-- no debconf information

---End Message---
---BeginMessage---
No response from submitter, closing.

Please reopen with the requested informations if appropritate.

-- 
You!  What PLANET is this!
-- McCoy, The City on the Edge of Forever, stardate 3134.0
---End Message---


Processed: tagging 357533

2007-02-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.26
 tags 357533 moreinfo
Bug#357533: linux-image-2.6.15-1-k7: nforce4 driver (network, sata, usb2 ) 
don't work with 2.6.15-k7-4
There were no tags set.
Tags added: moreinfo


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#412139: downgrading to 1-10 not working

2007-02-23 Thread Michael Rasmussen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I tried downgrading to 1-10 but now it shows the same behaviour as
1-11. Maybe something related to creating the initrd.img has changed
since the time 1-10 was released. My guess is udev.

- -- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael at rasmussen dot cc
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xD3C9A00E
mir at datanom dot net
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE501F51C
mir at miras dot org
http://keyserver.veridis.com:11371/pks/lookup?op=getsearch=0xE3E80917
- --
BOFH excuse #318:

Your EMAIL is now being delivered by the USPS.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF349JVErYVePoCRcRAhOMAJ4keAcUUTi0tdKPpGv8prgJrpbAGQCcDOUU
hqLwXeDFzZ9XDIh0H1L6uBg=
=GUiF
-END PGP SIGNATURE-


Bug#412153: linux-image-2.6.18-4-686: WPA fails on SMP systems under heavy load

2007-02-23 Thread Erich Schubert
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-11
Severity: normal

I was having problems with WPA-encrypted networks in heavy load
conditions, e.g. when transferring files from a local server.
Every minute I would be disconnected with the error messages
---
TKIP: ICV error detected: STA=...
N/A: Michael MIC verification failed for MSDU from ... keyidx=0
wifi0: MSDU decryption/MIC verification failed (SA=... keyidx=0)
TKIP: received packet without ExtIV flag from ...
---
And after about 1 minute, the wireless reconnected again.

After googling a while, I found this page:
http://www.tuxyturvy.com/blog/index.php?/archives/23-Using-the-IPW3945-with-Linux,-WPA,-and-the-SMP-Kernel.html

That is exactly my setup, and my error. I don't know which ieee80211
version is included with the 2.6.18 kernel, but I'm experiencing this
problem, and there is one more comment mentioning 2.6.18

Apparently, this is the same bug in Ubuntu:
https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/56894

I had a quick look at the 2.6.20 changelog, and it contains
---
commit 4d1feabcbf41f875447a392015acd0796f57baf6
Author: Ulrich Kunitz [EMAIL PROTECTED]
Date:   Sun Dec 10 11:13:12 2006 -0800

[PATCH] zd1211rw: Call ieee80211_rx in tasklet

The driver called ieee80211_rx in hardware interrupt context.  This has
been against the intention of the ieee80211_rx function.  It caused a bug
in the crypto routines used by WPA.  This patch calls ieee80211_rx in a
tasklet.

Signed-off-by: Ulrich Kunitz [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
Signed-off-by: John W. Linville [EMAIL PROTECTED]
---
That could be the relevant changeset, I don't know. There are some more 80211
related patches that could be relevant.
Anyway, not having reliable networking is a bigger issue for me...

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-4-686 depends on:
ii  coreutils 5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85e  tools for generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-18  Yet Another mkInitRD

Versions of packages linux-image-2.6.18-4-686 recommends:
ii  libc6-i6862.5-0exp3  GNU C Library: Shared libraries [i

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#304507: closed by Bastian Blank [EMAIL PROTECTED] (supported)

2007-02-23 Thread Paul Traina

You closed the wrong bug.

On Feb 23, 2007, at 4:33 PM, Debian Bug Tracking System wrote:


This is an automatic notification regarding your Bug report
#304507: kernel-source-2.6.11: please apply the evms bd-claim patch  
to debian kernel sources,

which was filed against the linux-2.6 package.

It has been closed by Bastian Blank [EMAIL PROTECTED].

Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact Bastian Blank [EMAIL PROTECTED] by  
replying

to this email.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


From: Bastian Blank [EMAIL PROTECTED]
Date: February 23, 2007 4:32:26 PM PST
To: [EMAIL PROTECTED]
Subject: supported


The given pci id is supported in the current version.

--
We have the right to survive!
Not by killing others.
-- Deela and Kirk, Wink of An Eye, stardate 5710.5






Bug#412161: linux-image-2.6.18-4-686: Upgrade from linux-image-2.6.18-3-686 fails on Sid

2007-02-23 Thread laur-olb1
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-10
Severity: important

*** Please type your report below this line ***
Upgrade from linux-image-2.6.18-3-686 fails on Sid, fails in the
configuration step.

# dpkg --configure linux-image-2.6.18-4-686
Setting up linux-image-2.6.18-4-686 (2.6.18.dfsg.1-10) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Running postinst hook script /usr/sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/boot/grub
Searching for default file ... Generating /boot/boot/grub/default file
and setting the default boot entry to 0
No GRUB directory found under /
User postinst hook script [/usr/sbin/update-grub] exited with value 1
dpkg: error processing linux-image-2.6.18-4-686 (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-2.6.18-4-686


-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-image-2.6.18-4-686 depends on:
ii  coreutils 5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85e  tools for generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-4-686 recommends:
ii  libc6-i686  2.3.6.ds1-13 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true
  linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true
  linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false
  linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false
  linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/bootloader-initrd-2.6.18-4-686: true
  linux-image-2.6.18-4-686/preinst/already-running-this-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/old-dir-initrd-link-2.6.18-4-686: true
  linux-image-2.6.18-4-686/postinst/kimage-is-a-directory:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686:
  linux-image-2.6.18-4-686/preinst/initrd-2.6.18-4-686:
  linux-image-2.6.18-4-686/postinst/create-kimage-link-2.6.18-4-686: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]