Bug#564587: linux-image-2.6.32-trunk-amd64: Silent NVidia HDMI audio in 2.6.32

2010-01-10 Thread Tony Houghton
Package: linux-2.6
Version: 2.6.32-4
Severity: normal

*** Please type your report below this line ***

When using 2.6.32 I get no sound from my integrated NVidia HDMI audio.
Everything appears to work properly ie no errors from audio players, and those
that block while playing block for the normal period, but the TV remains silent.
Analogue audio does work. I've checked all the mixer settings etc and I'm sure
they're correct. Reverting to kernel 2.6.31 without changing anything else
restores sound.

-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-4) (b...@decadent.org.uk) (gcc 
version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Thu Jan 7 17:44:12 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 
root=UUID=395dfad6-4ae1-422f-8365-599ceed5944b ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[2.047041] usb 3-3: Product: 2.4G USB RF KeyBoard
[2.047118] usb 3-3: configuration #1 chosen from 1 choice
[2.065155] usbcore: registered new interface driver hiddev
[2.072294] input: 2.4G USB RF KeyBoard as 
/devices/pci:00/:00:02.0/usb3/3-3/3-3:1.0/input/input4
[2.072347] generic-usb 0003:05AF:0408.0001: input,hidraw0: USB HID v1.10 
Keyboard [2.4G USB RF KeyBoard] on usb-:00:02.0-3/input0
[2.080314] input: 2.4G USB RF KeyBoard as 
/devices/pci:00/:00:02.0/usb3/3-3/3-3:1.1/input/input5
[2.080362] generic-usb 0003:05AF:0408.0002: input,hidraw1: USB HID v1.10 
Mouse [2.4G USB RF KeyBoard] on usb-:00:02.0-3/input1
[2.096105] input: 2.4G USB RF KeyBoard as 
/devices/pci:00/:00:02.0/usb3/3-3/3-3:1.2/input/input6
[2.096264] generic-usb 0003:05AF:0408.0003: input,hiddev96,hidraw2: USB HID 
v1.10 Device [2.4G USB RF KeyBoard] on usb-:00:02.0-3/input2
[2.096292] usbcore: registered new interface driver usbhid
[2.096295] usbhid: v2.6:USB HID core driver
[2.217550] PM: Starting manual resume from disk
[2.247302] kjournald starting.  Commit interval 5 seconds
[2.247312] EXT3-fs: mounted filesystem with ordered data mode.
[3.673276] udev: starting version 150
[4.359986] processor LNXCPU:00: registered as cooling_device0
[4.360072] processor LNXCPU:01: registered as cooling_device1
[4.363567] ACPI: WMI: Mapper loaded
[4.366430] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[4.405747] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[4.432190] parport_pc 00:05: reported by Plug and Play ACPI
[4.432240] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[4.477507] k8temp :00:18.3: Temperature readouts might be wrong - check 
erratum #141
[4.540293] EDAC MC: Ver: 2.1.0 Jan  7 2010
[4.568376] EDAC amd64_edac:  Ver: 3.2.0 Jan  7 2010
[4.568462] EDAC amd64: ECC is enabled by BIOS.
[4.568500] EDAC MC: Rev F or later detected
[4.568546] EDAC MC0: Giving out device to 'amd64_edac' 'RevF': DEV 
:00:18.2
[4.568577] EDAC PCI0: Giving out device to module 'amd64_edac' controller 
'EDAC PCI controller': DEV ':00:18.2' (POLLED)
[4.601000] i2c i2c-0: nForce2 SMBus adapter at 0x600
[4.601006] ACPI: I/O resource nForce2_smbus [0x700-0x73f] conflicts with 
ACPI region SM00 [0x700-0x73f]
[4.601079] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[4.601082] nForce2_smbus :00:01.1: Error probing SMB2.
[4.784577] saa7146: register extension 'budget_ci dvb'.
[4.785427] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 17
[4.785435]   alloc irq_desc for 17 on node 0
[4.785437]   alloc kstat_irqs on node 0
[4.785449] budget_ci dvb :01:06.0: PCI INT A - Link[LNKA] - GSI 17 
(level, low) - IRQ 17
[4.785472] IRQ 17/: IRQF_DISABLED is not guaranteed on shared IRQs
[4.785502] saa7146: found saa7146 @ mem c90010ff2c00 (revision 1, irq 
17) (0x13c2,0x100f).
[4.785509] saa7146 (0): dma buffer size 192512
[4.785512] DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI)
[4.821274] adapter has MAC addr = 00:d0:5c:20:d6:b2
[4.822260] input: Budget-CI dvb ir receiver saa7146 (0) as 
/devices/pci:00/:00:08.0/:01:06.0/input/input7
[5.136215] DVB: registering adapter 0 frontend 0 (ST STV0299 DVB-S)...
[5.136786] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 16
[5.136792]   alloc irq_desc for 16 on node 0
[5.136795]   alloc kstat_irqs on node 0
[5.136807] budget_ci dvb :01:07.0: PCI INT A - Link[LNKB] - GSI 16 
(level, low) - IRQ 16
[5.136843] IRQ 16/: IRQF_DISABLED is not guaranteed on shared IRQs
[5.136871] saa7146: found saa7146 @ mem c900111e2800 (revision 1, irq 
16) (0x13c2,0x1011).
[5.136878] saa7146 (1): dma buffer size 192512
[5.136880] DVB: registering new adapter (TT-Budget/WinTV-NOVA-T  PCI)
[5.177954] adapter has MAC addr = 00:d0:5c:23:e4:a3
[5.178325] input: Budget-CI dvb ir receiver saa7146 (1) as 

Bug#564587: linux-image-2.6.32-trunk-amd64: Silent NVidia HDMI audio in 2.6.32

2010-01-10 Thread Ben Hutchings
On Sun, 2010-01-10 at 14:13 +, Tony Houghton wrote:
 Package: linux-2.6
 Version: 2.6.32-4
 Severity: normal
 
 *** Please type your report below this line ***
 
 When using 2.6.32 I get no sound from my integrated NVidia HDMI audio.
 Everything appears to work properly ie no errors from audio players, and those
 that block while playing block for the normal period, but the TV remains 
 silent.
 Analogue audio does work. I've checked all the mixer settings etc and I'm sure
 they're correct. Reverting to kernel 2.6.31 without changing anything else
 restores sound.

Is the HDMI audio output part of the video card?

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


signature.asc
Description: This is a digitally signed message part


Bug#564587: linux-image-2.6.32-trunk-amd64: Silent NVidia HDMI audio in 2.6.32

2010-01-10 Thread Ben Hutchings
 Forwarded Message 
From: Tony Houghton h...@realh.co.uk
To: Ben Hutchings b...@decadent.org.uk
Subject: Re: Bug#564587: linux-image-2.6.32-trunk-amd64: Silent NVidia HDMI 
audio in 2.6.32
Date: Sun, 10 Jan 2010 15:09:44 +

On Sun, 10 Jan 2010 14:41:49 +
Ben Hutchings b...@decadent.org.uk wrote:

 Is the HDMI audio output part of the video card?

I think it would be correct to say so; it's an Asus M3N78-VM motherboard
which has an NVidia 8200 (MCP78S) IGP.

I've found a thread about a similar problem:
http://www.nvnews.net/vbulletin/showthread.php?t=140999page=3 but
they seem to be blaming NVidia's blob and I can't really tell whether
everybody affected is using kernel 2.6.32 and/or alsa 1.0.21. I suppose
I'd better see if I can get a 185 series NVidia driver installed on
it...




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#564587: linux-image-2.6.32-trunk-amd64: Silent NVidia HDMI audio in 2.6.32

2010-01-10 Thread Ben Hutchings
On Sun, 2010-01-10 at 15:09 +, Tony Houghton wrote:
 On Sun, 10 Jan 2010 14:41:49 +
 Ben Hutchings b...@decadent.org.uk wrote:
 
  Is the HDMI audio output part of the video card?
 
 I think it would be correct to say so; it's an Asus M3N78-VM motherboard
 which has an NVidia 8200 (MCP78S) IGP.
 
 I've found a thread about a similar problem:
 http://www.nvnews.net/vbulletin/showthread.php?t=140999page=3 but
 they seem to be blaming NVidia's blob and I can't really tell whether
 everybody affected is using kernel 2.6.32 and/or alsa 1.0.21. I suppose
 I'd better see if I can get a 185 series NVidia driver installed on
 it...

Our answer will be the same - if the Nvidia proprietary driver is
involved then only Nvidia can investigate and fix this.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


signature.asc
Description: This is a digitally signed message part


Incomplete upload found in Debian upload queue

2010-01-10 Thread Archive Administrator
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
  linux-2.6_2.6.32-5.diff.gz
  linux-2.6_2.6.32-5.dsc
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.

If no .changes file arrives within 23:22:29, the files will be deleted.

If you didn't upload those files, please just ignore this message.

Greetings,

Your Debian queue daemon (running on host ries.debian.org)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#564010: linux-image-2.6.32-trunk-686: fails to boot

2010-01-10 Thread Ben Hutchings
On Thu, 2010-01-07 at 11:35 +0800, Brice Rebsamen wrote:
 OK, shame on me: after I wrote this bug report I decided to try to
 read the kernel message in details to understand more about it and
 while I was doing so the kernel booted. The explanation is that since
 the realtek firmware are missing, the kernel fails to turn on the
 ethernet link, and hangs there for some time, then gives up and carry
 on with the boot process.

That is not the true explanation.  The kernel sends requests for
firmware as device events, which are normally handled by udev.  If
firmware is missing, it can immediately cancel the request.  The problem
is that udev is not running, so the kernel keeps on waiting for a
response up to the time limit (60 seconds).

This is a known bug in initramfs-tools, which I think will be fixed
soon.

 So this is no longer a critical bug. Sorry about the false alarm.
 
 However, there is still a problem with the packaging: where are the
 firmwares required?

Not clearly distributable.  I will contact Realtek again to request
clear licencing.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


signature.asc
Description: This is a digitally signed message part


Bug#564628: Add Realtek RTL8168D firmware

2010-01-10 Thread Ben Hutchings
Package: firmware-linux-nonfree
Version: 0.22
Severity: wishlist

I need to request a suitable licence to redistribute the RTL8168D
firmware patches which are removed from Linux kernel packages.
Currently the only licence for drivers/net/r8169.c is GPLv2, which is
not suitable for sourceless firmware.

Ben.

-- System Information:
Debian Release: squeeze/sid
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-linux-nonfree depends on no packages.

firmware-linux-nonfree recommends no packages.

Versions of packages firmware-linux-nonfree suggests:
ii  initramfs-tools   0.93.4 tools for generating an initramfs
ii  linux-image-2.6.26-2-686 [lin 2.6.26-20  Linux 2.6.26 image on PPro/Celeron
ii  linux-image-2.6.32-trunk-686  2.6.32-5   Linux 2.6.32 for modern PCs
ii  linux-image-2.6.32-trunk-amd6 2.6.32-5   Linux 2.6.32 for 64-bit PCs

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: reassign 545112 to linux-2.6

2010-01-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # bug seems to be in compat_ioctl code
 reassign 545112 linux-2.6 2.6.32-5
Bug #545112 [dvgrab] dvgrab: does not work properly with Juju firewire stack
Bug reassigned from package 'dvgrab' to 'linux-2.6'.
Bug #545112 [linux-2.6] dvgrab: does not work properly with Juju firewire stack
There is no source info for the package 'linux-2.6' at version '2.6.32-5' with 
architecture ''
Unable to make a source version for version '2.6.32-5'
Bug Marked as found in versions 2.6.32-5.

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 debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processing of linux-2.6_2.6.32-5_multi.changes

2010-01-10 Thread Archive Administrator
linux-image-2.6.32-trunk-amd64_2.6.32-5_i386.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 (running on host ries.debian.org)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#545112: dvgrab: does not work properly with Juju firewire stack

2010-01-10 Thread Ben Hutchings
On Sun, 2010-01-10 at 19:12 +, Ben Hutchings wrote:
 On Wed, 2010-01-06 at 22:12 +0100, Erik Schanze wrote: 
  tags 545112 moreinfo
  thanks
  
  Hi Ben,
  
  I have no problem with dvgrab and new firewire stack anymore, so I wonder 
  what
  the problem is in your case. Currently I use unstable Linux kernel 
  2.6.32-trunk-686.
  Did you already try it?
 
 I do test what I upload. :-)  Only I use 2.6.32-trunk-amd64 with i386
 userland.  Hmm...
 
 Right, dvgrab seems to be fine on 2.6.32-trunk-686.  That implies that
 this *is* a kernel bug but it's in ioctl translation, not the main
 firewire code.  Thanks for the hint; I'll reassign this and investigate
 further within the kernel.

...and now I can't reproduce this problem with either the -686 or -amd64
flavour.  I don't believe it has been fixed but I think there may be
some oddity of my specific camera involved.  If I can get it into this
state again then I'll try to track down what dvgrab is doing that fails
while my simple grabber doesn't.  (It is certainly sending requests to
the device, which the simple grabber doesn't bother with.)

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


signature.asc
Description: This is a digitally signed message part


Processed: retitle 545112 to Firewire stack gets into a state where it cannot send to some devices ...

2010-01-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 retitle 545112 Firewire stack gets into a state where it cannot send to some 
 devices
Bug #545112 [linux-2.6] dvgrab: does not work properly with Juju firewire stack
Changed Bug title to 'Firewire stack gets into a state where it cannot send to 
some devices' from 'dvgrab: does not work properly with Juju firewire stack'
 tags 545112 unreproducible moreinfo
Bug #545112 [linux-2.6] Firewire stack gets into a state where it cannot send 
to some devices
Added tag(s) unreproducible.

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 debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: loading kernel mode setting drivers

2010-01-10 Thread Ben Hutchings
On Thu, 2009-12-31 at 18:24 +, Julien Cristau wrote:
[...]
 One possible way to fix this, I guess, would be to replace this
 blacklist entry with a list of blacklisted fb drivers, to allow i915
 (and later radeon and nouveau) being loaded automatically on boot.  Is
 this feasible?  Are there other/better solutions?

That sounds like it might be a problem to maintain.  Would it be
feasible for each X video driver to blacklist the conflicting fb
driver(s), in the same way that KMS-capable X video drivers set module
parameters to enable KMS?

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


signature.asc
Description: This is a digitally signed message part


Processing of linux-2.6_2.6.32-5_multi.changes

2010-01-10 Thread Archive Administrator
linux-2.6_2.6.32-5_multi.changes uploaded successfully to localhost
along with the files:
  linux-2.6_2.6.32-5.dsc
  linux-2.6_2.6.32-5.diff.gz
  linux-support-2.6.32-trunk_2.6.32-5_all.deb
  linux-patch-debian-2.6.32_2.6.32-5_all.deb
  firmware-linux-free_2.6.32-5_all.deb
  linux-source-2.6.32_2.6.32-5_all.deb
  linux-doc-2.6.32_2.6.32-5_all.deb
  linux-manual-2.6.32_2.6.32-5_all.deb
  linux-headers-2.6.32-trunk-486_2.6.32-5_i386.deb
  linux-image-2.6.32-trunk-486_2.6.32-5_i386.deb
  linux-headers-2.6.32-trunk-686_2.6.32-5_i386.deb
  linux-image-2.6.32-trunk-686_2.6.32-5_i386.deb
  linux-headers-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
  linux-image-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
  linux-headers-2.6.32-trunk-amd64_2.6.32-5_i386.deb
  linux-image-2.6.32-trunk-amd64_2.6.32-5_i386.deb
  linux-headers-2.6.32-trunk-common_2.6.32-5_i386.deb
  linux-headers-2.6.32-trunk-all_2.6.32-5_i386.deb
  linux-headers-2.6.32-trunk-all-i386_2.6.32-5_i386.deb
  linux-libc-dev_2.6.32-5_i386.deb
  linux-headers-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
  linux-image-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
  linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
  linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
  linux-headers-2.6.32-trunk-common-vserver_2.6.32-5_i386.deb

Greetings,

Your Debian queue daemon (running on host ries.debian.org)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: found 534324 in 2.6.30-1

2010-01-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 found 534324 2.6.30-1
Bug #534324 [linux-2.6] linux-image-2.6.30-1-686: USB disk fails to show up at 
initramfs
There is no source info for the package 'linux-2.6' at version '2.6.30-1' with 
architecture ''
Unable to make a source version for version '2.6.30-1'
Bug Marked as found in versions 2.6.30-1.

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 debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



linux-2.6_2.6.32-5_multi.changes ACCEPTED

2010-01-10 Thread Archive Administrator



Accepted:
firmware-linux-free_2.6.32-5_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-5_all.deb
linux-2.6_2.6.32-5.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-5.diff.gz
linux-2.6_2.6.32-5.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-5.dsc
linux-doc-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-5_all.deb
linux-headers-2.6.32-trunk-486_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-all-i386_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-all_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-all_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-amd64_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-amd64_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-common-vserver_2.6.32-5_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-trunk-common-vserver_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-common_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-common_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-486_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-486_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-686_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-amd64_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-amd64_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
  to 
main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
linux-libc-dev_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-5_i386.deb
linux-manual-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-5_all.deb
linux-patch-debian-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-5_all.deb
linux-source-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-5_all.deb
linux-support-2.6.32-trunk_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-trunk_2.6.32-5_all.deb


Override entries for your package:
firmware-linux-free_2.6.32-5_all.deb - optional kernel
linux-2.6_2.6.32-5.dsc - source devel
linux-doc-2.6.32_2.6.32-5_all.deb - optional doc
linux-headers-2.6.32-trunk-486_2.6.32-5_i386.deb - optional kernel
linux-headers-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb - optional kernel
linux-headers-2.6.32-trunk-686_2.6.32-5_i386.deb - optional kernel
linux-headers-2.6.32-trunk-all-i386_2.6.32-5_i386.deb - optional kernel
linux-headers-2.6.32-trunk-all_2.6.32-5_i386.deb - optional kernel
linux-headers-2.6.32-trunk-amd64_2.6.32-5_i386.deb - optional kernel
linux-headers-2.6.32-trunk-common-vserver_2.6.32-5_i386.deb - optional kernel
linux-headers-2.6.32-trunk-common_2.6.32-5_i386.deb - optional kernel
linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb - optional 
kernel
linux-headers-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb - optional kernel
linux-image-2.6.32-trunk-486_2.6.32-5_i386.deb - optional kernel
linux-image-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb - optional kernel
linux-image-2.6.32-trunk-686_2.6.32-5_i386.deb - optional kernel
linux-image-2.6.32-trunk-amd64_2.6.32-5_i386.deb - optional kernel
linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb - optional kernel
linux-image-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb - optional kernel
linux-libc-dev_2.6.32-5_i386.deb - optional devel
linux-manual-2.6.32_2.6.32-5_all.deb - optional doc
linux-patch-debian-2.6.32_2.6.32-5_all.deb - optional kernel
linux-source-2.6.32_2.6.32-5_all.deb - optional kernel
linux-support-2.6.32-trunk_2.6.32-5_all.deb - optional devel

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 560040 563136 564156 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#564156: marked as done (FTBFS on armel: isp1362-hcd was written for some other kernel version)

2010-01-10 Thread Debian Bug Tracking System
Your message dated Sun, 10 Jan 2010 21:31:36 +
with message-id e1nu5no-0008li...@ries.debian.org
and subject line Bug#564156: fixed in linux-2.6 2.6.32-5
has caused the Debian Bug report #564156,
regarding FTBFS on armel: isp1362-hcd was written for some other kernel version
to be marked as done.

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

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


-- 
564156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-4
Justification: fails to build from source
Severity: important
Tags: patch

It seems the submitter of this driver was only pretending to work
with mainline, because this code won't compile on anything after
2.6.26:

#ifdef CONFIG_ARM
if (isp1362_hcd-board)
set_irq_type(irq, isp1362_hcd-board-int_act_high ? 
IRQT_RISING : IRQT_FALLING);
#endif

It looks like this can easily be fixed, but as this is a platform
device driver and none of our kernel flavours appears to use it I see
no reason to build it at all.

Ben.

-- System Information:
Debian Release: squeeze/sid
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Ben Hutchings
To err is human; to really foul things up requires a computer.


signature.asc
Description: This is a digitally signed message part
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.32-5

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-5_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-5_all.deb
linux-2.6_2.6.32-5.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-5.diff.gz
linux-2.6_2.6.32-5.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-5.dsc
linux-doc-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-5_all.deb
linux-headers-2.6.32-trunk-486_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-all-i386_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-all_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-all_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-amd64_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-amd64_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-common-vserver_2.6.32-5_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-trunk-common-vserver_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-common_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-common_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-486_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-486_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-686_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-amd64_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-amd64_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
  to 
main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
linux-libc-dev_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-5_i386.deb
linux-manual-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-5_all.deb
linux-patch-debian-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-5_all.deb
linux-source-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-5_all.deb

Bug#560040: marked as done (please enable CONFIG_DEVTMPFS)

2010-01-10 Thread Debian Bug Tracking System
Your message dated Sun, 10 Jan 2010 21:31:36 +
with message-id e1nu5no-0008ly...@ries.debian.org
and subject line Bug#560040: fixed in linux-2.6 2.6.32-5
has caused the Debian Bug report #560040,
regarding please enable CONFIG_DEVTMPFS
to be marked as done.

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

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


-- 
560040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32
Severity: normal

-- 
ciao,
Marco


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.32-5

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-5_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-5_all.deb
linux-2.6_2.6.32-5.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-5.diff.gz
linux-2.6_2.6.32-5.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-5.dsc
linux-doc-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-5_all.deb
linux-headers-2.6.32-trunk-486_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-all-i386_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-all_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-all_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-amd64_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-amd64_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-common-vserver_2.6.32-5_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-trunk-common-vserver_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-common_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-common_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
linux-headers-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-486_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-486_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-686-bigmem_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-686_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-amd64_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-amd64_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
  to 
main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-5_i386.deb
linux-image-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686_2.6.32-5_i386.deb
linux-libc-dev_2.6.32-5_i386.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-5_i386.deb
linux-manual-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-5_all.deb
linux-patch-debian-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-5_all.deb
linux-source-2.6.32_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-5_all.deb
linux-support-2.6.32-trunk_2.6.32-5_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-trunk_2.6.32-5_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 560...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Jan 2010 03:22:23 +
Source: linux-2.6
Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 
linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-trunk 
linux-base linux-libc-dev linux-headers-2.6.32-trunk-all 
linux-headers-2.6.32-trunk-all-alpha 

Processed: tagging 534324

2010-01-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 534324 moreinfo
Bug #534324 [linux-2.6] linux-image-2.6.30-1-686: USB disk fails to show up at 
initramfs
Added tag(s) 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 debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: found 562815 in 2.6.26-19lenny2

2010-01-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # assumed, as this was the current stable-security version
 found 562815 2.6.26-19lenny2
Bug #562815 [linux-2.6] Bug in kernel audit code makes system crash
There is no source info for the package 'linux-2.6' at version 
'2.6.26-19lenny2' with architecture ''
Unable to make a source version for version '2.6.26-19lenny2'
Bug Marked as found in versions 2.6.26-19lenny2.

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 debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#534324: linux-image-2.6.30-1-686: USB disk fails to show up at initramfs

2010-01-10 Thread Ben Hutchings
Good log:
[1.401460] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[1.401462] Warning! ehci_hcd should always be loaded before uhci_hcd and 
ohci_hcd, not after
...
[2.835643] usb 1-2.4: new full speed USB device using uhci_hcd and address 4
[2.938835] usb 1-2.4: configuration #1 chosen from 1 choice
[2.954087] Initializing USB Mass Storage driver...
[2.954234] scsi0 : SCSI emulation for USB Mass Storage devices
[2.954406] usbcore: registered new interface driver usb-storage
[2.954410] USB Mass Storage support registered.
[2.954822] usb-storage: device found at 4
[2.954824] usb-storage: waiting for device to settle before scanning
[3.008640] usb 1-2.7: new full speed USB device using uhci_hcd and address 5
...
[3.122843] usb 1-2.7: configuration #1 chosen from 1 choice
...
[3.134049] scsi1 : SCSI emulation for USB Mass Storage devices
[3.136678] usb-storage: device found at 5
[3.136681] usb-storage: waiting for device to settle before scanning
...
[6.736725] usb 5-2.4: new high speed USB device using ehci_hcd and address 6
[6.824221] usb 5-2.4: configuration #1 chosen from 1 choice
[6.825452] scsi4 : SCSI emulation for USB Mass Storage devices
[6.826671] usb-storage: device found at 6
[6.826675] usb-storage: waiting for device to settle before scanning
[6.888622] usb 5-2.7: new high speed USB device using ehci_hcd and address 7
[6.966814] usb 5-2.7: configuration #1 chosen from 1 choice
[6.971604] scsi5 : SCSI emulation for USB Mass Storage devices
[6.972162] usb-storage: device found at 7
[6.972165] usb-storage: waiting for device to settle before scanning

This is actually kind of broken in that the devices are enumerated
twice: first through the OHCI, then through the EHCI.  Still, the
usb-storage driver binds to them both.

Bad log:
[4.172086] usb 5-2.4: new high speed USB device using ehci_hcd and address 6
...
[4.266207] usb 5-2.4: New USB device found, idVendor=04b4, idProduct=6830
[4.266211] usb 5-2.4: New USB device strings: Mfr=0, Product=80, 
SerialNumber=63
[4.266214] usb 5-2.4: Product: Cypress AT2LP RC42
[4.266217] usb 5-2.4: SerialNumber: 50006779
[4.266320] usb 5-2.4: configuration #1 chosen from 1 choice
...
[4.298711] Initializing USB Mass Storage driver...
[4.298802] usbcore: registered new interface driver usb-storage
[4.298905] USB Mass Storage support registered.
...
[4.435101] usb 5-2.7: New USB device found, idVendor=0928, idProduct=0002
[4.435107] usb 5-2.7: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[4.435110] usb 5-2.7: Product: OXSEMI Mass Storage
[4.435113] usb 5-2.7: Manufacturer: Oxford Semiconductor Ltd.
[4.435116] usb 5-2.7: SerialNumber: 5BCDEF61
[4.435218] usb 5-2.7: configuration #1 chosen from 1 choice
[4.444062] scsi2 : SCSI emulation for USB Mass Storage devices
[4.444382] usb-storage: device found at 7
[4.444385] usb-storage: waiting for device to settle before scanning

Here the USB mass storage driver is loaded as expected but for some
reason it doesn't bind to the storage device that was already found;
only to the next device found.

The working config has:
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set

whereas our config has:
CONFIG_USB_STORAGE_CYPRESS_ATACB=m

Maybe the main usb-storage driver is ignoring this device because it
should be handled by the ums-cypress sub-driver, but that is missing
from the initramfs.

Can you try this:
1. Add 'ums-cypress' to /etc/modules
2. Run 'update-initramfs -u 2.6.30-1-686' (or any kernel version that
shows this problem)
3. Reboot into that kernel
?

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


signature.asc
Description: This is a digitally signed message part


Bug#563466: marked as done (reloading ath5k module and bringing link up freezes machine)

2010-01-10 Thread Debian Bug Tracking System
Your message dated Mon, 11 Jan 2010 12:34:46 +1300
with message-id 20100110233446.ga4...@lapse.rw.madduck.net
and subject line Re: Bug#563466: reloading ath5k module and bringing link up 
freezes machine
has caused the Debian Bug report #563466,
regarding reloading ath5k module and bringing link up freezes machine
to be marked as done.

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

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


-- 
563466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-3
Severity: normal

If I rmmod and modprobe ath5k and then bring the link up, the
machine repeatably hard-locks. I have no idea how to obtain
additional information about this, so if you need anything, please
advise.

-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-686 (Debian 2.6.32-3) (b...@decadent.org.uk) (gcc 
version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Thu Dec 24 05:52:30 UTC 2009

** Command line:
BOOT_IMAGE=//vmlinuz-2.6.32-trunk-686 root=/dev/mapper/lapse-root ro hpet=force

** Not tainted

** Kernel log:
[   14.896764] mmc0: SDHCI controller on PCI [:02:00.1] using PIO
[   15.027085] yenta_cardbus :02:00.0: CardBus bridge found [1014:0555]
[   15.152934] yenta_cardbus :02:00.0: ISA IRQ mask 0x0cb0, PCI irq 16
[   15.152984] yenta_cardbus :02:00.0: Socket status: 3006
[   15.153033] yenta_cardbus :02:00.0: pcmcia: parent PCI bridge I/O 
window: 0x3000 - 0x7fff
[   15.153096] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3000-0x7fff: 
clean.
[   15.154769] yenta_cardbus :02:00.0: pcmcia: parent PCI bridge Memory 
window: 0xd020 - 0xdfff
[   15.154833] yenta_cardbus :02:00.0: pcmcia: parent PCI bridge Memory 
window: 0xf000 - 0xf7ff
[   15.360546] hda: UDMA/100 mode selected
[   15.373959] hda: cache flushes supported
[   15.634746] ath5k :02:02.0: PCI INT A - GSI 21 (level, low) - IRQ 21
[   15.634836] ath5k :02:02.0: registered as 'phy0'
[   16.105576] ath: EEPROM regdomain: 0x62
[   16.105579] ath: EEPROM indicates we should expect a direct regpair map
[   16.105585] ath: Country alpha2 being used: 00
[   16.105588] ath: Regpair used: 0x62
[   16.121146] Intel ICH Modem :00:1f.6: PCI INT B - GSI 17 (level, low) 
- IRQ 17
[   16.121223] Intel ICH Modem :00:1f.6: setting latency timer to 64
[   16.193200] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: 
clean.
[   16.194126] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: 
excluding 0x4d0-0x4d7
[   16.194621] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: 
clean.
[   16.195836] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: 
clean.
[   16.197029] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: 
clean.
[   16.200798] phy0: Selected rate control algorithm 'minstrel'
[   16.201767] Registered led device: ath5k-phy0::rx
[   16.201829] Registered led device: ath5k-phy0::tx
[   16.201871] ath5k phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43)
[   16.201916] ath5k phy0: RF5112B multiband radio found (0x36)
[   16.208052] udev: renamed network interface wlan0 to wifi
[   16.224075] MC'97 1 converters and GPIO not ready (0xff00)
[   16.224880] Intel ICH :00:1f.5: PCI INT B - GSI 17 (level, low) - IRQ 
17
[   16.224984] Intel ICH :00:1f.5: setting latency timer to 64
[   17.148022] intel8x0_measure_ac97_clock: measured 55332 usecs (2666 samples)
[   17.148075] intel8x0: clocking to 48000
[   17.496162] hda: UDMA/100 mode selected
[   17.496727] hda: cache flushes supported
[   17.673142] Adding 1572856k swap on /dev/mapper/lapse-swap.  Priority:-1 
extents:1 across:1572856k 
[   17.836226] EXT3 FS on dm-2, internal journal
[   23.605159] kjournald starting.  Commit interval 5 seconds
[   23.605453] EXT3 FS on hda1, internal journal
[   23.605514] EXT3-fs: mounted filesystem with ordered data mode.
[   23.676603] kjournald starting.  Commit interval 5 seconds
[   23.677039] EXT3 FS on dm-6, internal journal
[   23.677107] EXT3-fs: mounted filesystem with ordered data mode.
[   23.810615] kjournald starting.  Commit interval 5 seconds
[   23.811271] EXT3 FS on dm-5, internal journal
[   23.811331] EXT3-fs: mounted filesystem with ordered data mode.
[   23.866409] kjournald starting.  Commit interval 5 seconds
[   23.866784] EXT3 FS on dm-3, internal journal
[   23.866844] EXT3-fs: mounted filesystem with ordered data mode.
[   23.956405] kjournald starting.  Commit interval 5 seconds
[   23.956788] EXT3 FS on dm-4, internal journal
[   23.956848] EXT3-fs: mounted filesystem with