Supporting 2.6.27 in Lenny? - Long term support

2008-10-19 Thread Kushal Koolwal

I posted this message on debian-devel and I was asked to post on  
debian-kernel. So here it is:

First of all I apologize if this has been brought up somewhere else.
 
It seems that on LKML it was announced that 2.6.27 will be a long term support 
kernel:
http://lkml.org/lkml/2008/10/11/235
 
Since we haven't released Lenny yet (freeze state I believe), wouldn't it be a 
good idea to include 2.6.27 as the default Lenny kernel instead of 2.6.26?
 
Most of the newer release of other distributions like  Fedora, Ubuntu, and 
openSUSE are going to be based on 2.6.27
http://lkml.org/lkml/2008/10/14/322
 
Also I am not a DD so I might not be aware 100% of the freeze policy as I ask 
this question.
 
Thanks
 
Kushal Koolwal
 
I do blog at http://blogs.koolwal.net/
 
_
When your life is on the go—take your life with you.
http://clk.atdmt.com/MRT/go/115298558/direct/01/

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



Re: Firmware removal progress

2008-10-19 Thread Holger Levsen
Hi Ben,

On Sunday 19 October 2008 04:11, Ben Hutchings wrote:
 Here's an updated overview; I think this now covers all sourceless
 firmware/microcode left in linux-2.6:

You're a rockstar! :-)

Thanks a lot for all your work on this!


regards,
Holger, very happy to see this mess tackled


pgpz6NcQA63YS.pgp
Description: PGP signature


Bug#493479: linux-image-2.6.26-1-amd64: 2.6.26-8 still locks up

2008-10-19 Thread Marek Michalkiewicz
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-8
Followup-For: Bug #493479

I've just tried the latest, recently updated kernel from testing.
I'd like to report that this bug is still present - the machine still 
freezes after NET: Registered protocol family 2, as before.
GA-MA69VM-S2 motherboard, Athlon LE-1620 CPU.
The 2.6.25 kernel listed below is the last working one.

-- Package-specific info:

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

Kernel: Linux 2.6.25-2-amd64 (SMP w/1 CPU core)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=locale: Cannot set LC_CTYPE to 
default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

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

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

Versions of packages linux-image-2.6.26-1-amd64 suggests:
ii  grub-pc [grub]  1.96+20080724-10 GRand Unified Bootloader, version 
pn  linux-doc-2.6.26none   (no description available)

-- debconf-show failed



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



Bug#502733: firehol: Doesn't allow connection with OpenVPN since upgrade of linux-image-2.6.26-1-686

2008-10-19 Thread Yannick Palanque
Package: firehol
Version: 1.256-4
Severity: important

Hello,

Since an upgrade from linux-image-2.6.26-1-686 2.6.26-8 to 2.6.26-9, when 
Firehol is activated, I cannot connect to an OpenVPN network anymore. Here is 
what says syslog when I launch Openvpn, Firehol started:

Oct 19 15:42:30 baudelaire ovpn-myvpn[11762]: Control Channel Authentication: 
using 'user/my.key' as a OpenVPN static key file
Oct 19 15:42:30 baudelaire ovpn-myvpn[11762]: Outgoing Control Channel 
Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Oct 19 15:42:30 baudelaire ovpn-myvpn[11762]: Incoming Control Channel 
Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Oct 19 15:42:30 baudelaire ovpn-myvpn[11762]: Control Channel MTU parms [ 
L:1591 D:168 EF:68 EB:0 ET:0 EL:0 ]
Oct 19 15:42:30 baudelaire ovpn-myvpn[11762]: Data Channel MTU parms [ L:1591 
D:1450 EF:59 EB:4 ET:32 EL:0 ]
Oct 19 15:42:30 baudelaire ovpn-myvpn[11762]: Local Options hash (VER=V4): 
'b8d42479'
Oct 19 15:42:30 baudelaire ovpn-myvpn[11762]: Expected Remote Options hash 
(VER=V4): '173d8fc4'
Oct 19 15:42:30 baudelaire ovpn-myvpn[11764]: NOTE: UID/GID downgrade will be 
delayed because of --client, --pull, or --up-delay
Oct 19 15:42:30 baudelaire ovpn-myvpn[11764]: Attempting to establish TCP 
connection with 42.42.42.42: [nonblock]
Oct 19 15:42:33 baudelaire ovpn-myvpn[11764]: TCP: connect to 42.42.42.42: 
failed, will try again in 5 seconds: Connection refused
Oct 19 15:42:41 baudelaire ovpn-myvpn[11764]: TCP: connect to 42.42.42.42: 
failed, will try again in 5 seconds: Connection refused
Oct 19 15:42:49 baudelaire ovpn-myvpn[11764]: TCP: connect to 42.42.42.42: 
failed, will try again in 5 seconds: Connection refused


My firehol.conf is simple and looks like this:

 begin of firehol.conf 
version 5

FIREHOL_LOG_MODE=ULOG

interface eth0 interface_eth0
## Doesn't work even if this two lines are commented.
   protection strong
   policy reject

   server icmp accept
   client all accept

interface tap0 myvpn
## Doesn't work even if this two lines are commented.
   protection strong
   policy reject

   server icmp accep
   client all accept

 end of firehol.conf 


Here is the output of iptables -L:




Chain INPUT (policy DROP)
target prot opt source   destination 
ACCEPT all  --  anywhere anywhere
in_interface_eth0  all  --  anywhere anywhere
in_myvpn  all  --  anywhere anywhere
ACCEPT all  --  anywhere anywherestate RELATED 
ULOG   all  --  anywhere anywherelimit: avg 1/sec 
burst 5 ULOG copy_range 0 nlgroup 1 prefix `'IN-unknown:'' queue_threshold 1 
DROP   all  --  anywhere anywhere

Chain FORWARD (policy DROP)
target prot opt source   destination 
ACCEPT all  --  anywhere anywherestate RELATED 
ULOG   all  --  anywhere anywherelimit: avg 1/sec 
burst 5 ULOG copy_range 0 nlgroup 1 prefix `'PASS-unknown:'' queue_threshold 1 
DROP   all  --  anywhere anywhere

Chain OUTPUT (policy DROP)
target prot opt source   destination 
ACCEPT all  --  anywhere anywhere
out_interface_eth0  all  --  anywhere anywhere
out_myvpn  all  --  anywhere anywhere
ACCEPT all  --  anywhere anywherestate RELATED 
ULOG   all  --  anywhere anywherelimit: avg 1/sec 
burst 5 ULOG copy_range 0 nlgroup 1 prefix `'OUT-unknown:'' queue_threshold 1 
DROP   all  --  anywhere anywhere

Chain in_myvpn (1 references)
target prot opt source   destination 
in_myvpn_icmp_s1  all  --  anywhere anywhere
in_myvpn_all_c2  all  --  anywhere anywhere
in_myvpn_irc_c3  all  --  anywhere anywhere
in_myvpn_ftp_c4  all  --  anywhere anywhere
ACCEPT all  --  anywhere anywherestate RELATED 
ULOG   all  --  anywhere anywherelimit: avg 1/sec 
burst 5 ULOG copy_range 0 nlgroup 1 prefix `''IN-myvpn':'' queue_threshold 1 
DROP   all  --  anywhere anywhere

Chain in_myvpn_all_c2 (1 references)
target prot opt source   destination 
ACCEPT all  --  anywhere anywherestate ESTABLISHED 

Chain in_myvpn_ftp_c4 (1 references)
target prot opt source   destination 
ACCEPT tcp  --  anywhere anywheretcp spt:ftp 
dpts:32768:61000 state ESTABLISHED 
ACCEPT tcp  --  anywhere anywheretcp spt:ftp-data 
dpts:32768:61000 state 

Processed: post-lenny bugs

2008-10-19 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 tags 494007 + lenny-ignore
Bug#494007: binary firmware in drivers/char/drm/r128_cce.c
Tags were: patch help
Tags added: lenny-ignore

 tags 494009 + lenny-ignore
Bug#494009: binary firmware in drivers/char/drm/radeon_microcode.h
Tags were: patch help
Tags added: lenny-ignore

 tags 494010 + lenny-ignore
Bug#494010: binary firmware in drivers/char/dsp56k.c
Tags were: patch fixed-upstream help
Tags added: lenny-ignore

 tags 494308 + lenny-ignore
Bug#494308: binary firmware in drivers/net/e100.c
Tags were: patch help
Tags added: lenny-ignore

 tags 498631 + lenny-ignore
Bug#498631: binary firmware in drivers/net/cassini.h
Tags were: help
Tags added: lenny-ignore

 tags 501152 + lenny-ignore
Bug#501152: binary firmware in drivers/net/starfire_firmware.h
Tags were: patch
Tags added: lenny-ignore

 tags 501153 + lenny-ignore
Bug#501153: binary firmware in drivers/net/tehuti_fw.h
There were no tags set.
Tags added: lenny-ignore

 tags 502663 + lenny-ignore
Bug#502663: linux-2.6: Binary firmware in dabusb driver
There were no tags set.
Tags added: lenny-ignore

 tags 502665 + lenny-ignore
Bug#502665: Binary firmware in kaweth driver
There were no tags set.
Tags added: lenny-ignore

 tags 502666 + lenny-ignore
Bug#502666: Binary firmware in mga driver
There were no tags set.
Tags added: lenny-ignore

 tags 502667 + lenny-ignore
Bug#502667: Binary firmware in qla1280 driver
There were no tags set.
Tags added: lenny-ignore

 tags 502668 + lenny-ignore
Bug#502668: Binary firmware in whiteheat driver
There were no tags set.
Tags added: lenny-ignore

 tags 502669 + lenny-ignore
Bug#502669: Binary firmware in typhoon driver
There were no tags set.
Tags added: lenny-ignore


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#498702: additional comment: PATA HD not detected

2008-10-19 Thread Michel Briand
Quote from #495273:

  I've crossposted this to every relevant debian bug I could find with:

  http://www.google.com/search?q=site:bugs.debian.org+marvell+88se6121

  I believe the bug to be caused by the regression under discussion in
  this thread:

  http://www.gossamer-threads.com/lists/linux/kernel/968813

  It looks like Alan Cox's patch will be in 2.6.27, and in the meantime
  you can achieve a work around by rebuilding your initrd to load
  pata_marvell before ahci.

  I hope this helps everyone who's been affected by this problem!

  --alex



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



Processed: found 502663 in 2.6.26-8, found 502665 in 2.6.26-8, found 502666 in 2.6.26-8 ...

2008-10-19 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # These bugs are not new
 found 502663 2.6.26-8
Bug#502663: linux-2.6: Binary firmware in dabusb driver
Bug marked as found in version 2.6.26-8.

 found 502665 2.6.26-8
Bug#502665: Binary firmware in kaweth driver
Bug marked as found in version 2.6.26-8.

 found 502666 2.6.26-8
Bug#502666: Binary firmware in mga driver
Bug marked as found in version 2.6.26-8.

 found 502667 2.6.26-8
Bug#502667: Binary firmware in qla1280 driver
Bug marked as found in version 2.6.26-8.

 found 502668 2.6.26-8
Bug#502668: Binary firmware in whiteheat driver
Bug marked as found in version 2.6.26-8.

 found 502669 2.6.26-8
Bug#502669: Binary firmware in typhoon driver
Bug marked as found in version 2.6.26-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]



Bug#502792: initramfs-tools: mkinitramfs-kpkg ignores UMASK setting

2008-10-19 Thread Mario 'BitKoenig' Holbe
Package: initramfs-tools
Version: 0.92l

Hello,

upgrading kernels always produces 0644 initrd.imgs while upgrading
initramfs-tools as well as manual update-initramfs calls produce 0600
initrd.imgs. The only difference I found is that kernel postinst scripts
use mkinitramfs-kpkg instead of update-initramfs, so I guess this is the
guilty party.

I have loop-aes-utils installed which sets UMASK=0077 in
/usr/share/initramfs-tools/conf.d/loopaes. This seems to be respected by
update-initramfs but not by mkinitramfs-kpkg.


regards
   Mario
-- 
To err is human. To really foul things up requires a computer.


signature.asc
Description: Digital signature


Bug#502816: cannot suspend

2008-10-19 Thread Joe Nahmias
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-9
Severity: normal

Hello,

I am unable to suspend my T61 thinkpad when using an amd64 kernel.
However, if I use linux-image-2.6.26-1-686 it works fine.  Here's some
additional info on the failure:


$ uname -srmvo
Linux 2.6.26-1-amd64 #1 SMP Sat Oct 18 17:55:00 UTC 2008 x86_64 GNU/Linux

$ swapon -s
FilenameTypeSizeUsedPriority
/dev/mapper/diskvg-swap partition   524280  0   -1

$ sudo s2disk
[  105.778948] ioctl32(s2disk:4852): Unknown cmd fd(4) 
cmd(400c330d){t:'3';sz:12} arg(ff88413c) on /dev/snapshot
[  105.779219] ioctl32(s2disk:4852): Unknown cmd fd(4) 
cmd(4004330a){t:'3';sz:4} arg(fe00) on /dev/snapshot
s2disk: Could not use the resume device (try swapon -a). Reason: Invalid 
argument

$ cat /var/log/pm-suspend.log
Initial commandline parameters: --quirk-s3-bios
--quirk-s3-mode
Fri Oct 17 00:11:20 EDT 2008: Running hooks for hibernate.
/usr/lib/pm-utils/sleep.d/00clear hibernate: disabled.
/usr/lib/pm-utils/sleep.d/05led hibernate: success.
/usr/lib/pm-utils/sleep.d/10NetworkManager hibernate: success.
/usr/lib/pm-utils/sleep.d/49bluetooth hibernate: success.
/usr/lib/pm-utils/sleep.d/50modules hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/90clock hibernate: success.
/usr/lib/pm-utils/sleep.d/94cpufreq hibernate: success.
/usr/lib/pm-utils/sleep.d/95led hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video hibernate: success.
/usr/lib/pm-utils/sleep.d/99video hibernate: disabled.
Fri Oct 17 00:11:21 EDT 2008: performing hibernate
s2disk: Could not use the resume device (try swapon -a). Reason: Invalid 
argument
Fri Oct 17 00:11:22 EDT 2008: Awake.
Fri Oct 17 00:11:22 EDT 2008: Running hooks for thaw
/usr/lib/pm-utils/sleep.d/99video thaw: disabled.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video thaw: success.
/usr/lib/pm-utils/sleep.d/95led thaw: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq thaw: success.
/usr/lib/pm-utils/sleep.d/90clock thaw: success.
/usr/lib/pm-utils/sleep.d/50modules thaw: success.
/usr/lib/pm-utils/sleep.d/49bluetooth thaw: success.
/usr/lib/pm-utils/sleep.d/10NetworkManager thaw: success.
/usr/lib/pm-utils/sleep.d/05led thaw: success.
/usr/lib/pm-utils/sleep.d/00clear thaw: disabled.
Fri Oct 17 00:11:22 EDT 2008: Finished.


-- Package-specific info:

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

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

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

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

Versions of packages linux-image-2.6.26-1-amd64 suggests:
ii  grub  0.97-47GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.26  none (no description available)

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



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