Bug#620608: uninitialized value in string eq at postinst:1280

2011-04-26 Thread Jörg Sommer
Ben Hutchings hat am Tue 26. Apr, 04:47 (+0100) geschrieben:
 On Mon, 2011-04-25 at 23:35 +0200, Jörg Sommer wrote:
  Jörg Sommer hat am Mon 25. Apr, 23:21 (+0200) geschrieben:
   Ben Hutchings hat am Sun 03. Apr, 03:06 (+0100) geschrieben:
/sbin/blkid -o device | while read device; do
echo $device:
/sbin/blkid -o udev -s LABEL -s UUID -s TYPE $device
done
   
   /dev/sda1
   ID_FS_UUID=a59a6be1-01ac-2c7a-12ab-c8dc8e4c3255
   ID_FS_UUID_ENC=a59a6be1-01ac-2c7a-12ab-c8dc8e4c3255
   ID_FS_LABEL=_grml_:0
   ID_FS_LABEL_ENC=\x27grml\x27:0
   ID_FS_TYPE=linux_raid_member
   /dev/sda2
   ID_FS_LABEL=Linux_Var
   ID_FS_LABEL_ENC=Linux_Var
   ID_FS_UUID=60342ce9-209a-4b60-97b5-7d9309751202
   ID_FS_UUID_ENC=60342ce9-209a-4b60-97b5-7d9309751202
   ID_FS_TYPE=ext4
  
  That's strange. sda2 is a RAID member. I don't know why blkid thinks it's
  a standalone filesystem.
 
 Yes, that's weird.
 
 But now that I look over the code again, I think the bug you found is
 not related to this information.  Does the /etc/mdadm.conf file on this
 system use a device name wildcard?

No. That's the contents:

cat /etc/mdadm/mdadm.conf 
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST jupiter

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2 
UUID=a59a6be1:01ac2c7a:12abc8dc:8e4c3255
ARRAY /dev/md1 level=raid1 num-devices=2 
UUID=2e95c5a4:d658a167:cf89181d:5e6e3dc4

# This file was auto-generated on Mon, 04 Jan 2010 22:46:50 +0100
# by mkconf $Id$

Schöne Grüße, Jörg.
-- 
A valid expression in Java: x = new A().new B();


signature.asc
Description: Digital signature http://en.wikipedia.org/wiki/OpenPGP


Bug#587686: Squeeze partially helps

2011-04-26 Thread Oleg Broytman
Hello. Upgrading to squeeze partially helped - squeeze's kernel works
better than lenny's. But still kernels compiled by me exhibit even better
disk performance. So it seems I'm stuck with recompiling my kernel
myself.

Oleg.
-- 
 Oleg Broytmanhttp://phdru.name/p...@phdru.name
   Programmers don't die, they just GOSUB without RETURN.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110426080502.gb21...@iskra.aviel.ru



Bug#624185: linux-image-2.6.38-2-686: fuse module does not load

2011-04-26 Thread Benjamin Gufler
Package: linux-2.6
Version: 2.6.38-4
Severity: important
Tags: sid

The fuse module cannot be loaded due to unknown symbol _kstrtoul.

-- Package-specific info:
** Version:
Linux version 2.6.38-2-686 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 05:24:21 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.38-2-686 root=UUID=fd22fa0f-d09c-4828-8f01-e87d21e05601 
ro vga=791 quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[   28.497639] XFS mounting filesystem dm-0
[   28.632602] Ending clean XFS mount for filesystem: dm-0
[   28.713611] XFS mounting filesystem dm-1
[   28.900230] Ending clean XFS mount for filesystem: dm-1
[   30.214824] fuse init (API version 7.16)
[   31.110147] tun: Universal TUN/TAP device driver, 1.6
[   31.110150] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com
[   32.601145] input: ACPI Virtual Keyboard Device as 
/devices/virtual/input/input14
[   36.49] lp: driver loaded but no devices found
[   36.948641] ppdev: user-space parallel port driver
[   38.111441] tg3 :09:00.0: irq 48 for MSI/MSI-X
[   38.146445] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   41.239778] tg3 :09:00.0: eth0: Link is up at 1000 Mbps, full duplex
[   41.239781] tg3 :09:00.0: eth0: Flow control is on for TX and on for RX
[   41.239916] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   50.943445] Disabling lock debugging due to kernel taint
[   50.943453] nvidia: module license 'NVIDIA' taints kernel.
[   51.915612] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[   51.915623] nvidia :01:00.0: setting latency timer to 64
[   51.915629] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   51.915775] NVRM: loading NVIDIA UNIX x86 Kernel Module  260.19.44  Sun Feb 
27 21:30:31 PST 2011
[   53.257393] ip_tables: (C) 2000-2006 Netfilter Core Team
[  410.663886] keyboard: can't emulate rawmode for keycode 240
[  410.663914] keyboard: can't emulate rawmode for keycode 240
[  411.104246] usb 3-2: new full speed USB device using uhci_hcd and address 2
[  411.286271] usb 3-2: New USB device found, idVendor=413c, idProduct=8140
[  411.286280] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  411.349336] Bluetooth: Core ver 2.15
[  411.349359] NET: Registered protocol family 31
[  411.349361] Bluetooth: HCI device and connection manager initialized
[  411.349363] Bluetooth: HCI socket layer initialized
[  411.434565] Bluetooth: Generic Bluetooth USB driver ver 0.6
[  411.436792] usbcore: registered new interface driver btusb
[  412.047407] iwl3945 :0c:00.0: loaded firmware version 15.32.2.9
[  412.120502] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  414.748120] iwl3945 :0c:00.0: Card state received: HW:Kill SW:On
[  414.748241] iwl3945 :0c:00.0: Not sending command - RF KILL
[  414.748251] iwl3945 :0c:00.0: Error sending REPLY_RXON: enqueue_hcmd 
failed: -5
[  414.748260] iwl3945 :0c:00.0: Error setting new configuration (-5).
[  414.748272] iwl3945 :0c:00.0: Not sending command - RF KILL
[  414.748281] iwl3945 :0c:00.0: Error sending REPLY_RXON: enqueue_hcmd 
failed: -5
[  414.748287] iwl3945 :0c:00.0: Error setting new configuration (-5).
[  414.748684] keyboard: can't emulate rawmode for keycode 240
[  414.748709] keyboard: can't emulate rawmode for keycode 240
[  414.762321] iwl3945 :0c:00.0: Not sending command - RF KILL
[  414.762332] iwl3945 :0c:00.0: Error sending REPLY_RXON: enqueue_hcmd 
failed: -5
[  414.762342] iwl3945 :0c:00.0: Error setting new configuration (-5).
[  414.766297] iwl3945 :0c:00.0: MAC is in deep sleep!.  CSR_GP_CNTRL = 
0x040003DD
[  414.824104] usb 3-2: USB disconnect, address 2
[  415.441003] keyboard: can't emulate rawmode for keycode 240
[  415.441028] keyboard: can't emulate rawmode for keycode 240
[  416.056166] usb 3-2: new full speed USB device using uhci_hcd and address 3
[  416.234505] usb 3-2: New USB device found, idVendor=413c, idProduct=8140
[  416.234515] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  417.066726] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  422.389988] wlan0: authenticate with 00:03:52:ad:25:84 (try 1)
[  422.395332] wlan0: authenticated
[  422.396549] wlan0: associate with 00:03:52:ad:25:84 (try 1)
[  422.399022] wlan0: RX AssocResp from 00:03:52:ad:25:84 (capab=0xc31 status=0 
aid=2)
[  422.399029] wlan0: associated
[  422.400909] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  424.397760] iwl3945 :0c:00.0: Card state received: HW:Kill SW:On
[  424.397882] iwl3945 :0c:00.0: Not sending command - RF KILL
[  424.397890] iwl3945 :0c:00.0: Error sending REPLY_QOS_PARAM: 
enqueue_hcmd failed: -5
[  424.397907] iwl3945 :0c:00.0: Not sending command - RF KILL
[  424.397914] iwl3945 :0c:00.0: Error sending REPLY_RXON: enqueue_hcmd 

Bug#611301: patch applied in 2.6.38.4

2011-04-26 Thread Michal Suchanek
close 611301
thanks

The patch fixing this was applied in 2.6.38.4 so this should be fixed
in Debian 2.8.38-4.

Thanks

Michal



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTikPy3G6uZUc97s=3cai6zx0_hq...@mail.gmail.com



Processed: patch applied in 2.6.38.4

2011-04-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 close 611301
Bug#611301: linux-image-2.6.37-trunk-amd64: uswsusp does not work on linux 
2.6.37
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Michal Suchanek 
hramr...@centrum.cz

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
611301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13038124998210.transcr...@bugs.debian.org



Bug#624185: marked as done (linux-image-2.6.38-2-686: fuse module does not load)

2011-04-26 Thread Debian Bug Tracking System
Your message dated Tue, 26 Apr 2011 12:37:42 +0200
with message-id 4db6a076.5000...@cs.tum.edu
and subject line Re: Bug#624185: Acknowledgement (linux-image-2.6.38-2-686: 
fuse module does not load)
has caused the Debian Bug report #624185,
regarding linux-image-2.6.38-2-686: fuse module does not load
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.)


-- 
624185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.38-4
Severity: important
Tags: sid

The fuse module cannot be loaded due to unknown symbol _kstrtoul.

-- Package-specific info:
** Version:
Linux version 2.6.38-2-686 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 05:24:21 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.38-2-686 root=UUID=fd22fa0f-d09c-4828-8f01-e87d21e05601 
ro vga=791 quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[   28.497639] XFS mounting filesystem dm-0
[   28.632602] Ending clean XFS mount for filesystem: dm-0
[   28.713611] XFS mounting filesystem dm-1
[   28.900230] Ending clean XFS mount for filesystem: dm-1
[   30.214824] fuse init (API version 7.16)
[   31.110147] tun: Universal TUN/TAP device driver, 1.6
[   31.110150] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com
[   32.601145] input: ACPI Virtual Keyboard Device as 
/devices/virtual/input/input14
[   36.49] lp: driver loaded but no devices found
[   36.948641] ppdev: user-space parallel port driver
[   38.111441] tg3 :09:00.0: irq 48 for MSI/MSI-X
[   38.146445] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   41.239778] tg3 :09:00.0: eth0: Link is up at 1000 Mbps, full duplex
[   41.239781] tg3 :09:00.0: eth0: Flow control is on for TX and on for RX
[   41.239916] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   50.943445] Disabling lock debugging due to kernel taint
[   50.943453] nvidia: module license 'NVIDIA' taints kernel.
[   51.915612] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[   51.915623] nvidia :01:00.0: setting latency timer to 64
[   51.915629] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   51.915775] NVRM: loading NVIDIA UNIX x86 Kernel Module  260.19.44  Sun Feb 
27 21:30:31 PST 2011
[   53.257393] ip_tables: (C) 2000-2006 Netfilter Core Team
[  410.663886] keyboard: can't emulate rawmode for keycode 240
[  410.663914] keyboard: can't emulate rawmode for keycode 240
[  411.104246] usb 3-2: new full speed USB device using uhci_hcd and address 2
[  411.286271] usb 3-2: New USB device found, idVendor=413c, idProduct=8140
[  411.286280] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  411.349336] Bluetooth: Core ver 2.15
[  411.349359] NET: Registered protocol family 31
[  411.349361] Bluetooth: HCI device and connection manager initialized
[  411.349363] Bluetooth: HCI socket layer initialized
[  411.434565] Bluetooth: Generic Bluetooth USB driver ver 0.6
[  411.436792] usbcore: registered new interface driver btusb
[  412.047407] iwl3945 :0c:00.0: loaded firmware version 15.32.2.9
[  412.120502] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  414.748120] iwl3945 :0c:00.0: Card state received: HW:Kill SW:On
[  414.748241] iwl3945 :0c:00.0: Not sending command - RF KILL
[  414.748251] iwl3945 :0c:00.0: Error sending REPLY_RXON: enqueue_hcmd 
failed: -5
[  414.748260] iwl3945 :0c:00.0: Error setting new configuration (-5).
[  414.748272] iwl3945 :0c:00.0: Not sending command - RF KILL
[  414.748281] iwl3945 :0c:00.0: Error sending REPLY_RXON: enqueue_hcmd 
failed: -5
[  414.748287] iwl3945 :0c:00.0: Error setting new configuration (-5).
[  414.748684] keyboard: can't emulate rawmode for keycode 240
[  414.748709] keyboard: can't emulate rawmode for keycode 240
[  414.762321] iwl3945 :0c:00.0: Not sending command - RF KILL
[  414.762332] iwl3945 :0c:00.0: Error sending REPLY_RXON: enqueue_hcmd 
failed: -5
[  414.762342] iwl3945 :0c:00.0: Error setting new configuration (-5).
[  414.766297] iwl3945 :0c:00.0: MAC is in deep sleep!.  CSR_GP_CNTRL = 
0x040003DD
[  414.824104] usb 3-2: USB disconnect, address 2
[  415.441003] keyboard: can't emulate rawmode for keycode 240
[  415.441028] keyboard: can't emulate rawmode for keycode 240
[  416.056166] usb 3-2: new full speed USB device using uhci_hcd and address 3
[  416.234505] usb 3-2: New USB device found, 

Bug#621803: Add support for /run directory

2011-04-26 Thread rleigh
block 623174 by 621803
thanks

On Fri, Apr 22, 2011 at 08:14:47PM +0100, Roger Leigh wrote:
 On Mon, Apr 18, 2011 at 07:38:41PM +0100, Roger Leigh wrote:
  By the way, could you consider adding this patch to your branch:
 
 diff --git a/init b/init
 index 38c8a5d..cdbfe50 100755
 --- a/init
 +++ b/init
 @@ -25,7 +25,7 @@ if ! mount -t devtmpfs -o mode=0755 none /dev; then
  fi
  mkdir /dev/pts
  mount -t devpts -o noexec,nosuid,gid=5,mode=0620 none /dev/pts || true
 -mount -t tmpfs -o nodev,noexec,nosuid,mode=0755 none /run
 +mount -t tmpfs -o nosuid,size=20%,mode=0755 tmpfs /run
  mkdir /run/initramfs
  
  # Export the dpkg architecture
 
 Slightly simpler than the previous patch, but does the same job.
 Please note that I've now patched initscripts
 (http://paste.debian.net/114826/ and
 http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/2011-April/004990.html)
  so that the filesystems mounted in the initramfs and later moved
 over to the root filesystem are remounted with the mount options
 specified in /etc/fstab (or /etc/default/tmpfs if no fstab entry
 exists).  In consequence, it's no longer critical that the mount
 option defaults in the initramfs match the real root filesystem
 defaults, because they will always be applied by mountkernfs/
 mountdevsubfs.  So if you choose not to apply this, that's fine--it's
 just a nice to have addition; the patch as it stands without the
 above change is equally acceptable.
 
 Thanks for doing this.  Do we have any ETA on an upload?

The updated initscripts should be uploaded to experimental later today.
This includes all the changes listed above.

I've added the block above because we can't make an upload of sysvinit/
initscripts to unstable until we have an updated initramfs-tools in
unstable, or else udev will break.  Therefore in order to have a smooth
transition we need initramfs-tools uploading first, followed by
initscripts.

Marco, have you tested this upgrade path?  That is /run in the
initramfs and no /run on the rootfs?  Is udev checking for that and
not using /run in this scenario (or moving the files from /run to
/dev/.udev)?  We will need to cope with this for a brief transitional
period when initramfs-tools is updated and initscripts is not.


Thanks,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.


signature.asc
Description: Digital signature


Processed: Re: Bug#621803: Add support for /run directory

2011-04-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 block 623174 by 621803
Bug #623174 [initscripts] /run must exist in the initramfs and be moved to the 
root filesystem
Was not blocked by any bugs.
Added blocking bug(s) of 623174: 621803
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
623174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.130381598517807.transcr...@bugs.debian.org



Bug#598893: marked as done (linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052))

2011-04-26 Thread Debian Bug Tracking System
Your message dated Tue, 26 Apr 2011 10:57:42 + (UTC)
with message-id pine.bsm.4.64l.1104261057180.4...@herc.mirbsd.org
and subject line linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)
has caused the Debian Bug report #598893,
regarding linux-2.6 [m68k]: please work around gcc-4.3 ICE bug (37052)
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.)


-- 
598893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: linux-2.6
Version: 2.6.32-24
Severity: wishlist
Tags: sid

Please see to that -fno-omit-frame-pointer is used during compilation
of a Debian m68k kernel as long as it is built with gcc-4.3 (I think
defining CONFIG_FRAME_POINTER should be enough, I have yet to build
any kernel at all though and have not tested this).

Details: http://wiki.debian.org/M68k/Gcc#iceinfindreloads

Triggered during btrfs compilation, out of all things…

-- System Information:
Debian Release: squeeze/sid
  APT prefers etch-m68k
..oO(why?)
  APT policy: (500, 'etch-m68k')
Architecture: m68k

Kernel: Linux 2.6.26-1-atari
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static


---End Message---
---BeginMessage---
src:linux-2.6 now uses gcc-4.4 so this is done.

---End Message---


Bug#623059: Data corruption when sendfile is used on atl1c Atheros NIC.

2011-04-26 Thread Artur R. Czechowski
On Mon, Apr 25, 2011 at 05:58:12AM +0100, Ben Hutchings wrote:
 Your test program is broken; this function is missing a return
 statement:
[cut
 It might be that the variable 'cfd' ends up in the return value anyway.
 But you should fix this (and use compiler options -Wall and -Wextra).
Thanks for noticing it.

 The extra data at the start of 'apache.dat' and 'sendfile.dat' looks
 like the packet headers, so for some reason they have been duplicated.
 Please can you test the attached patch, following the instructions at
 http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official?
Unfortunately I'll be able to test it after May 10th. So, if you already have
a report that the issue has been fixed, that's fine be me.

Best regards
Artur



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110426111713.gs13...@blabluga.hell.pl



can't grep start_rodata in /proc/kallsyms

2011-04-26 Thread Zongliang Li
Hi,

I'm using Debian squeeze 6.0.1a.

I tried to grep `start_rodata' in /proc/kallsyms but no output. But can
succeed with System.map.

root@debian:/boot# uname -a
Linux debian 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux
root@debian:/boot# grep _start_rodata /proc/kallsyms
root@debian:/boot# grep _start_rodata /boot/System.map-2.6.32-5-686
c1273000 R __start_rodata
root@debian:/boot#

How can I know where went wrong?

BR,


Bug#590105: Buffalo LS-CHL not supported yet

2011-04-26 Thread Martin Michlmayr
* Antonios Galanopoulos an...@goto10.org [2011-04-16 19:05]:
 It's supported in the kernel now.  It's not supported in the installer
 yet (there are open bugs for this already).
 
 Can you point me to those bugs so I can follow their progress please? I 
 really like to get my last year
 Christmas present working before upcoming Christmas! :) 

Which device are you interested in?  Buffalo Linkstation Live (LS-CHL)
or Buffalo Linkstation Mini (LS-WSGL)?

-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110426065905.gh2...@jirafa.cyrius.com



Re: can't grep start_rodata in /proc/kallsyms

2011-04-26 Thread Ben Hutchings
On Tue, 2011-04-26 at 19:34 +0800, Zongliang Li wrote:
 Hi,
 
 I'm using Debian squeeze 6.0.1a.
 
 I tried to grep `start_rodata' in /proc/kallsyms but no output. But
 can succeed with System.map. 
 
 root@debian:/boot# uname -a
 Linux debian 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686
 GNU/Linux
 root@debian:/boot# grep _start_rodata /proc/kallsyms
 root@debian:/boot# grep _start_rodata /boot/System.map-2.6.32-5-686
 c1273000 R __start_rodata
 root@debian:/boot#
 
 How can I know where went wrong? 

I don't think there's anything wrong here.  /proc/kallsyms only contains
text (function) symbols.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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


Processing of kernel-handbook_1.0.10_i386.changes

2011-04-26 Thread Debian FTP Masters
kernel-handbook_1.0.10_i386.changes uploaded successfully to localhost
along with the files:
  kernel-handbook_1.0.10.dsc
  kernel-handbook_1.0.10.tar.gz
  debian-kernel-handbook_1.0.10_all.deb

Greetings,

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1qeivi-0004qi...@franck.debian.org



kernel-handbook_1.0.10_i386.changes ACCEPTED into unstable

2011-04-26 Thread Debian FTP Masters



Accepted:
debian-kernel-handbook_1.0.10_all.deb
  to main/k/kernel-handbook/debian-kernel-handbook_1.0.10_all.deb
kernel-handbook_1.0.10.dsc
  to main/k/kernel-handbook/kernel-handbook_1.0.10.dsc
kernel-handbook_1.0.10.tar.gz
  to main/k/kernel-handbook/kernel-handbook_1.0.10.tar.gz


Override entries for your package:
debian-kernel-handbook_1.0.10_all.deb - extra doc
kernel-handbook_1.0.10.dsc - source doc

Announcing to debian-devel-chan...@lists.debian.org


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
Archive: http://lists.debian.org/e1qejye-0004g9...@franck.debian.org



Bug#621803: Add support for /run directory

2011-04-26 Thread Marco d'Itri
On Apr 26, rleigh rle...@codelibre.net wrote:

  -mount -t tmpfs -o nodev,noexec,nosuid,mode=0755 none /run
  +mount -t tmpfs -o nosuid,size=20%,mode=0755 tmpfs /run
Why does /run should not be noexec?

 I've added the block above because we can't make an upload of sysvinit/
 initscripts to unstable until we have an updated initramfs-tools in
 unstable, or else udev will break.  Therefore in order to have a smooth
Yes, if /run exists in the initramfs then it needs to be moved to the
root filesystem.

 Marco, have you tested this upgrade path?  That is /run in the
 initramfs and no /run on the rootfs?  Is udev checking for that and
No, but if the database is not copied to the initramfs then LVM will be
annoyed.

 not using /run in this scenario (or moving the files from /run to
 /dev/.udev)?  We will need to cope with this for a brief transitional
 period when initramfs-tools is updated and initscripts is not.
The udev initscript cannot know if there was a /run/udev in the
initramfs and it was lost.
Right now I can't see how to work around this.
If there is no /run in the initramfs then /dev/.udev/ will be used, and
since udev 167-3 the udev init script will move it to /run/udev/ (as
long as /run is a mount point, check the init script).

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#621803: Add support for /run directory

2011-04-26 Thread rleigh
On Tue, Apr 26, 2011 at 12:06:14PM +0100, Roger Leigh wrote:
 block 623174 by 621803
 thanks
 
 On Fri, Apr 22, 2011 at 08:14:47PM +0100, Roger Leigh wrote:
  On Mon, Apr 18, 2011 at 07:38:41PM +0100, Roger Leigh wrote:
   By the way, could you consider adding this patch to your branch:
  
  diff --git a/init b/init
  index 38c8a5d..cdbfe50 100755
  --- a/init
  +++ b/init
  @@ -25,7 +25,7 @@ if ! mount -t devtmpfs -o mode=0755 none /dev; then
   fi
   mkdir /dev/pts
   mount -t devpts -o noexec,nosuid,gid=5,mode=0620 none /dev/pts || true
  -mount -t tmpfs -o nodev,noexec,nosuid,mode=0755 none /run
  +mount -t tmpfs -o nosuid,size=20%,mode=0755 tmpfs /run
   mkdir /run/initramfs
   
   # Export the dpkg architecture
  
  Slightly simpler than the previous patch, but does the same job.
  Please note that I've now patched initscripts
  (http://paste.debian.net/114826/ and
  http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/2011-April/004990.html)
   so that the filesystems mounted in the initramfs and later moved
  over to the root filesystem are remounted with the mount options
  specified in /etc/fstab (or /etc/default/tmpfs if no fstab entry
  exists).  In consequence, it's no longer critical that the mount
  option defaults in the initramfs match the real root filesystem
  defaults, because they will always be applied by mountkernfs/
  mountdevsubfs.  So if you choose not to apply this, that's fine--it's
  just a nice to have addition; the patch as it stands without the
  above change is equally acceptable.
  
  Thanks for doing this.  Do we have any ETA on an upload?
 
 The updated initscripts should be uploaded to experimental later today.
 This includes all the changes listed above.
 
 I've added the block above because we can't make an upload of sysvinit/
 initscripts to unstable until we have an updated initramfs-tools in
 unstable, or else udev will break.  Therefore in order to have a smooth
 transition we need initramfs-tools uploading first, followed by
 initscripts.
 
 Marco, have you tested this upgrade path?  That is /run in the
 initramfs and no /run on the rootfs?  Is udev checking for that and
 not using /run in this scenario (or moving the files from /run to
 /dev/.udev)?  We will need to cope with this for a brief transitional
 period when initramfs-tools is updated and initscripts is not.

Testing with initramfs-tools (maks/run) with current unstable shows
udev appearing to work correctly with it using /dev/.udev when /run
is not present on the host system.  And also with /run present on
the host system in addition.  In the former case, it uses /run in
the initramfs and moved it to /dev/.udev on the host.  In the latter
it uses /run in the initramfs and on the host as well.  So from the
udev side, it does appear to be working correctly in all cases.  So
from this POV, the maks/run branch is working just fine.


In a kvm VM, I do see some errors from udev at startup:

--
Loading Linux 2.6.38-2-amd64 ...
Loading initial ramdisk ...
Loading, please wait...
udevd[125]: exec of program 'net.agent' failed

udevd[126]: exec of program 'net.agent' failed

udevd[137]: exec of program 'cdrom_id --export /dev/sr0' failed

udevd[142]: exec of program 'cdrom_id --export /dev/sr0' failed

INIT: version 2.88 booting
Using makefile-style concurrent boot in runlevel S.
Starting the hotplug events dispatcher: udevd
--

This is with udev 168-1.  However, I see the above without any changes
to initramfs-tools or initscripts, and this doesn't changes with /run
present in the initramfs or both the initramfs and rootfs, so it's a
separate issue, and so far specific to the VM image.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.


signature.asc
Description: Digital signature


Bug#621803: Add support for /run directory

2011-04-26 Thread rleigh
On Tue, Apr 26, 2011 at 05:12:49PM +0200, Marco d'Itri wrote:
 On Apr 26, rleigh rle...@codelibre.net wrote:
 
   -mount -t tmpfs -o nodev,noexec,nosuid,mode=0755 none /run
   +mount -t tmpfs -o nosuid,size=20%,mode=0755 tmpfs /run
 Why does /run should not be noexec?

If /run/shm is also on /run (not a separate mount), it needs to be
executable.  If they are separate mounts, it does add the noexec
option back:

[mountkernfs.sh]
# If /run/shm is separately mounted, /run can be safely mounted noexec.
RUNEXEC=
if [ yes = $RAMSHM ] || read_fstab_entry /run/shm tmpfs; then
RUNEXEC=',noexec'
fi
# TODO: Add -onodev once checkroot no longer creates a device node.
domount $MNTMODE tmpfs shmfs /run tmpfs -onosuid$RUNEXEC$RUN_OPT

  I've added the block above because we can't make an upload of sysvinit/
  initscripts to unstable until we have an updated initramfs-tools in
  unstable, or else udev will break.  Therefore in order to have a smooth
 Yes, if /run exists in the initramfs then it needs to be moved to the
 root filesystem.

This is being done by initramfs-tools, and it's working nicely AFAICT.

  Marco, have you tested this upgrade path?  That is /run in the
  initramfs and no /run on the rootfs?  Is udev checking for that and
 No, but if the database is not copied to the initramfs then LVM will be
 annoyed.

Which database is this?  Is this something that the LVM scripts need
updating to handle?

  not using /run in this scenario (or moving the files from /run to
  /dev/.udev)?  We will need to cope with this for a brief transitional
  period when initramfs-tools is updated and initscripts is not.
 The udev initscript cannot know if there was a /run/udev in the
 initramfs and it was lost.
 Right now I can't see how to work around this.
 If there is no /run in the initramfs then /dev/.udev/ will be used, and
 since udev 167-3 the udev init script will move it to /run/udev/ (as
 long as /run is a mount point, check the init script).

I just sent a separate mail after doing some testing.  The current logic
in 168-1 does appear to move /run/udev (initramfs) to /dev/.udev when
/run is not present on the host.  Looks good to me.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.


signature.asc
Description: Digital signature


Bug#621803: Add support for /run directory

2011-04-26 Thread Marco d'Itri
On Apr 26, rleigh rle...@codelibre.net wrote:

 Testing with initramfs-tools (maks/run) with current unstable shows
 udev appearing to work correctly with it using /dev/.udev when /run
 is not present on the host system.  And also with /run present on
Did you check with LVM and that all its persistent symlinks are still
there?

 In a kvm VM, I do see some errors from udev at startup:
These are unrelated and harmless (the errors are old, only the message
is new).

  Why does /run should not be noexec?
 If /run/shm is also on /run (not a separate mount), it needs to be
 executable.
Why do we need it executable?


   Marco, have you tested this upgrade path?  That is /run in the
   initramfs and no /run on the rootfs?  Is udev checking for that and
  No, but if the database is not copied to the initramfs then LVM will be
  annoyed.
 Which database is this?  Is this something that the LVM scripts need
 updating to handle?
It is /dev/.udev/ or /run/udev/. I do not know exactly how LVM interacts
with it, just that it must be preserved.

 I just sent a separate mail after doing some testing.  The current logic
 in 168-1 does appear to move /run/udev (initramfs) to /dev/.udev when
 /run is not present on the host.  Looks good to me.
No, there is no such code in the udev package. What you are seeing is
/run/udev/ being lost when the initramfs is destroyed and a new
/dev/.udev/.

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#607301: I think I misunderstood The SiI 3114 User Manual Page 5. HDDs Function Normally When Not in RAID Sets.

2011-04-26 Thread techy techtech
Jump to the last 5 paragraphs in this post, at my tag date 21.04.2011 .
I believe I have made a mistake with my configuration set up.

13.04.2011.  Otherwise:
The error symptom persists using grub-pc 1.99~rc1-12 on same pc:
AMD K6-2 cpu, Aladdin V chipset system with only one SATA Non raid,
hard disk attached to the SiI 3114 Raid controller.
In the bios:-
1st boot device set to SCSI.
2nd Boot device set to CDROM
With the cdrom empty. The error symptom persists:

SiI 3114 SATARaid BIOS Version 5.3.14
Silicon Image, Inc.
Press Ctrl+S or F4 to enter RAID utility
0  ST3160815AS   149GB

No valid device! Press any key to continue...
or)
Press Ctrl+S or F4 to enter RAID utility

Searching for Boot Record from SCSI..Not Found
Searching for Boot Record from CDROM..Not Found

Boot Failure
Reboot and Select proper Boot device
or insert Boot Media in selected Boot device
Press any key when ready  

---

# less /boot/grub/device.map
(hd0)  /dev/disk/by-id/ata-ST3160815AS_9...A

---
When trying to start the already installed system on /sda1
via the rescue disk in the cdrom drive, using
grub-rescue-cdrom 1.99~rc1-12 from grub-rescue-pc 1.99~rc1-12
The rescue cdrom itself successfully boots on the same machine.

Editing the rescue disk 'GNU/Linux, boot command list'
to experiment only, to help identify where the error messages
are coming from.
I have no intention to boot the system with this experiment edit.

GNU GRUB version 1.99~rc1-12

echo 1 set root=(hd0,1)
set root=(hd0,1)
echo 2
echo 3
echo 4 linux /vmlinuz root=/dev/sda1
/vmlinuz root=/dev/sda1
echo 5
echo 6 end.

Then booting with F10 followed by a quick press of
the Pause/Break key on the keyboard to stop the
screen output timing out and disappearing, gave:

Booting a command list

1 set root=(hd0,1)
2
3
4 Linuz /vmlinuz root=/dev/sda1
error: hd0 cannot get C/H/S values.
5
6 end.

Press any key to continue...
--

21.04.2011.
It looks like I have made, at least, another mistake.
Reviewing my issue yet again, I decided to check out
when booting up, the Silicon Image Bios message :-
 No valid device! Press any key to continue... 
Yes,  the first error message encountered.
I know to follow the first error indication.

I have been searching on the net and discovered
that there are TWO basic types of firmware for the card.
1.) With RAID( SATARaid )
2.) WithOUT RAID ( SATALink )
Going back and rereading my SATA/Raid card documentation,
along with the internet entries I have since found,
without realising, I had assumed, there would be no change in firmware.
To date, I have not touched the firmware.
I have not loaded the non raid firmware when I started
using a single sata attached hard disk drive.
I thought it would make fault finding easier,
by making things less complex, with just one hard disk.

I will have to rethink the SATARaid User's Manual page 5.
 HDDs Function Normally When Not in RAID Sets. 
copyright 2003 Silicon Image Inc.

I thought the  No valid device!  message meant no valid raid array.
I now believe it means;
that there is no valid Direct Access Storage Device (DASD), that
the BIOS can communicate with.  If so, I need to either :-
1.) Install a second disk to make a valid RAID array, or
2.) Change the SiI 3114 to (non raid) SATALink firmware.

For what it's worth,
grub-rescue-cdrom 1.99~rc1-12 and rc1-13 has the same symptoms.
Although this post started life as an Installation Report.
It is now what may probably be a user error (mine).
So with hindsight, I should not be posting on this mailing list.
For politeness and completeness, I will attempt to take this
issue to it's conclusion, elsewhere if need be,
then update a final posting here.  I'm learning.

Regards,  McTech.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktino022_594fygjrep3zd8zdmg6...@mail.gmail.com



Bug#622850: linux-2.6: Please enable Hyper-V drivers

2011-04-26 Thread Steinar H. Gunderson
On Fri, Apr 15, 2011 at 03:06:40PM +0200, Steinar H. Gunderson wrote:
 hv_netvsc. I'll see if the patch I linked to actually fixes the issue
 (Microsoft seems to claim it does):

After a few days and some relatively high load, I can confirm 2.6.38 + that
patch (hand-adjusted) works fine.

/* Steinar */
-- 
Homepage: http://www.sesse.net/



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110426182850.ga13...@uio.no



Re: Introduction and greetings

2011-04-26 Thread Moritz Mühlenhoff
Jeremiah Foster jerem...@jeremiahfoster.com schrieb:

 On Apr 24, 2011, at 18:30, Moritz Mühlenhoff wrote:

 Jeremiah C. Foster jerem...@jeremiahfoster.com schrieb:

 So the start might be to look through the BTS, find kernel bugs that were 
 forwarded and if it looks like they are dormant, see if they can be brought 
 to life?

Yes, and it there's no reaction from the submitter they can also be closed
(in Debian and upstream), no need to keep old bugs cluttering the BTSes.

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnirebfd.2qp@inutil.org



Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38

2011-04-26 Thread Moritz Mühlenhoff
On Mon, Apr 25, 2011 at 11:29:13AM +1000, Jason White wrote:
 Laptop-mode appears to be the cause; can you reproduce the bug by enabling it
 on your X200?

How did you activate the laptop mode on your system?

If I install laptop-mode-tools, the system still powers down just fine.
laptop-mode is deactivated as part of the shutdown sequence, though.

Cheers,
Moritz



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110426214732.GA2980@pisco.westfalen.local



Bug#624261: Patch for statd.8 and nfsiostat.8 man syntax errors

2011-04-26 Thread Simon Paillard
Package: nfs-common
Version: 1:1.2.3-2
Tags: patch 
Severity: minor

Hi,

During update of manpages-fr-extra, po4a complained about syntax issues with
two manpages from nfs-utils.

It's not only nitpicking for po4a, as it prevents as well some part of the
manpages from being displayed by the pager.

Already spotted by lintian (the 3rd one is not a problem for po4a nor pager):
http://lintian.debian.org/maintainer/debian-ker...@lists.debian.org.html#nfs-utils
 )

Here are two tiny patches for this (against upstream branch from your git).

-- 
Simon Paillard
From eb0f1c1ccb60ebed6c959088467f5bf8bfcaedc9 Mon Sep 17 00:00:00 2001
From: Simon Paillard spaill...@debian.org
Date: Wed, 27 Apr 2011 00:15:49 +0200
Subject: [PATCH] Fix statd.8 manpage syntax 'visible'

---
 utils/statd/statd.man |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/utils/statd/statd.man b/utils/statd/statd.man
index ca00e24..3209a50 100644
--- a/utils/statd/statd.man
+++ b/utils/statd/statd.man
@@ -347,8 +347,8 @@ of the requesting lock manager.
 TI-RPC is a pre-requisite for supporting NFS on IPv6.
 If TI-RPC support is built into
 .BR rpc.statd ,
-it attempts to start listeners on network transports marked
-'visible' in
+it attempts to start listeners on network transports marked 'visible'
+in
 .IR /etc/netconfig .
 As long as at least one network transport listener starts successfully,
 .B rpc.statd
-- 
1.7.2.5

From 00a47ffac69bd0a9331f899cdc04728fb567519d Mon Sep 17 00:00:00 2001
From: Simon Paillard spaill...@debian.org
Date: Wed, 27 Apr 2011 00:22:45 +0200
Subject: [PATCH 2/2] Fix nfsiostat.8 manpage syntax missing .I

---
 tools/nfs-iostat/nfsiostat.man |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/tools/nfs-iostat/nfsiostat.man b/tools/nfs-iostat/nfsiostat.man
index 99e04fb..3ec245d 100644
--- a/tools/nfs-iostat/nfsiostat.man
+++ b/tools/nfs-iostat/nfsiostat.man
@@ -24,7 +24,7 @@ parameter is
 specified, the value of 
 .I count 
 determines the number of reports generated at
-. interval 
+.I interval 
 seconds apart. if the interval parameter is 
 specified without the
 .I count 
-- 
1.7.2.5



Bug#590105: Buffalo LS-CHL not supported yet

2011-04-26 Thread Antonios Galanopoulos
Hi, 

Martin Michlmayr said :

 Which device are you interested in?  Buffalo Linkstation Live (LS-CHL)
 or Buffalo Linkstation Mini (LS-WSGL)?

Its a Linkstation Pro Duo. (LS-WTGL/R1)


Thanks!
 
 -- 
 Martin Michlmayr
 http://www.cyrius.com/
 

-- 
|
|'`'.   .''...
|'.''..`  '.
|-`..'--- '.  
|   '..'   `.'
|`..'   
|
http://agagag.goto10.org



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110426230428.GE3261@xbeetroot



Bug#624266: linux-image-2.6.38-2-686: Upgrading from 2.6.38-3 to 2.6.38-4 breaks fuse.ko

2011-04-26 Thread Sebastian Schmidt
Package: linux-2.6
Version: 2.6.38-4
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hi,

after upgrading from 2.6.38-3 to -4 fuse.ko doesn't load anymore:

[212281.279079] fuse: Unknown symbol _kstrtoul (err 0)
[212291.332634] fuse: Unknown symbol _kstrtoul (err 0)

After booting the newly installed kernel fuse loads fine.

Sebastian

- -- Package-specific info:
** Version:
Linux version 2.6.38-2-686 (Debian 2.6.38-4) (b...@decadent.org.uk) (gcc 
version 4.4.6 (Debian 4.4.6-2) ) #1 SMP Sat Apr 23 19:04:20 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.38-2-686 root=/dev/mapper/sda3_crypt ro

** Tainted: O (4096)
 * Out-of-tree module has been loaded.
[this is virtualbox - I think that's not relevant]

** Kernel log:
[stripped, rebooted before running reportbug]

** Model information
not available

** Loaded modules:
[stripped, rebooted before running reportbug]

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML 
and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
Subsystem: Lenovo ThinkPad T60/R60 series [17aa:2017]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort+ SERR- PERR- INTx-
Latency: 0
Capabilities: access denied
Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 
00 [VGA controller])
Subsystem: Lenovo ThinkPad T60/R60 series [17aa:201a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at ee10 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at 1800 [size=8]
Region 2: Memory at d000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at ee20 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at unassigned [disabled]
Capabilities: access denied
Kernel driver in use: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
Subsystem: Lenovo ThinkPad T60/R60 series [17aa:201a]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Region 0: Memory at ee18 (32-bit, non-prefetchable) [size=512K]
Capabilities: access denied

00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High 
Definition Audio Controller [8086:27d8] (rev 02)
Subsystem: Lenovo ThinkPad T60/R60 series [17aa:2010]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 47
Region 0: Memory at ee24 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: HDA Intel

00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express 
Port 1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 2000-2fff
Memory behind bridge: ee00-ee0f
Prefetchable memory behind bridge: 8000-801f
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: access denied
Kernel driver in use: pcieport

00:1c.1 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express 
Port 2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 3000-4fff
Memory 

Bug#624268: [squeeze] include important changes from 2.6.32.39

2011-04-26 Thread dann frazier
Source: linux-2.6
Version: 2.6.32-33
Severity: important

2.6.32.39 seems to apply/build fine w/o any ABI changes - here's a
brief review of the changes w/ a squeeze bias:

 dcef84f1 net: fix rds_iovec page count overflow

CVE-2010-3865 (we've had a fix since 2.6.32-31)

 c4f6afb9 net: ax25: fix information leak to userland harder

follow up fix for CVE-2010-3875

 6f396d4a x86, cpu: Fix regression in AMD errata checking code

fixes hangs on some K8 systems

 5d7a20b5 USB: xhci - fix math in xhci_get_endpoint_interval()

Improves spec compliance; I suspect this translates into more reliable
behavior for any USB 3.0 users.

 53d5fa19 USB: xhci - fix unsafe macro definitions

What it says on the tin

 b90adfeb USB: fix formatting of SuperSpeed endpoints in /proc/bus/usb/devices

/proc/bus/usb/devices is deprecated, and we don't mount it by default,
but this should improve the output for anyone who does use it..

 a572af68 USB: EHCI: unlink unused QHs when the controller is stopped

fixes an issue w/ EHCI failover... which I didn't even know existed

 d86dbfba proc: do proper range check on readdir offset
 67e022f3 next_pidmap: fix overflow condition

CVE-2011-1593

 3aed738e USB: option: Added support for Samsung GT-B3730/GT-B3710 LTE USB 
 modem.
 3cd02e97 USB: option: Add new ONDA vendor id and product id for ONDA MT825UP
 fbf2ed35 USB: ftdi_sio: add ids for Hameg HO720 and HO730
 2233c6ee USB: ftdi_sio: add PID for OCT DK201 docking station
 6a1c23da USB: ftdi_sio: Added IDs for CTI USB Serial Devices

yay new hardware!

 8835b61c x86, amd: Disable GartTlbWlkErr when BIOS forgets it

avoids random reboots

 d4274252 x86, AMD: Set ARAT feature on AMD processors
 7a3b25c0 x86, cpu: Clean up AMD erratum 400 workaround
 bba4804e x86, cpu: AMD errata checking framework

These avoid switching to HPET timers in deep C states on AMD
CPUs. Though obviously an improvement, I'm not really sure what makes
these candidates for stable - unless people have been seeing hangs w/
the broadcast timer code on AMD systems?

 4f4f117c UBIFS: fix oops when R/O file-system is fsync'ed

looks good

 286ef426 MAINTAINERS: update STABLE BRANCH info

documentation change only

 e9f20dc7 ramfs: fix memleak on no-mmu arch

We don't build any no-mmu kernels

 ad18f970 mca.c: Fix cast from integer to pointer warning
 e0ab4946 tioca: Fix assignment from incompatible pointer warnings

Just fixes compiler warnings? Seem odd for stable, but correct.

 17ebcafe x86: Fix a bogus unwind annotation in lib/semaphore_32.S

Not sure what the end user value is here... better kernel backtracing?

 dd12cd10 NET: cdc-phonet, handle empty phonet header

improved hardware support

 6b29cc2f UBIFS: restrict world-writable debugfs files
 55d39791 video: sn9c102: world-wirtable sysfs files

security improvements

 b6502c56 cifs: always do is_path_accessible check in cifs_mount

fixes a BUG()



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110427001708.gf11...@dannf.org



Processed: tagging 624268

2011-04-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 624268 + pending
Bug #624268 [src:linux-2.6] [squeeze] include important changes from 2.6.32.39
Added tag(s) pending.

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
624268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.130386394212412.transcr...@bugs.debian.org



Bug#624266: marked as done (linux-image-2.6.38-2-686: Upgrading from 2.6.38-3 to 2.6.38-4 breaks fuse.ko)

2011-04-26 Thread Debian Bug Tracking System
Your message dated Wed, 27 Apr 2011 01:29:46 +0100
with message-id 20110427002946.gc2...@decadent.org.uk
and subject line Re: Bug#624266: linux-image-2.6.38-2-686: Upgrading from 
2.6.38-3 to 2.6.38-4 breaks fuse.ko
has caused the Debian Bug report #624266,
regarding linux-image-2.6.38-2-686: Upgrading from 2.6.38-3 to 2.6.38-4 breaks 
fuse.ko
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hi,

after upgrading from 2.6.38-3 to -4 fuse.ko doesn't load anymore:

[212281.279079] fuse: Unknown symbol _kstrtoul (err 0)
[212291.332634] fuse: Unknown symbol _kstrtoul (err 0)

After booting the newly installed kernel fuse loads fine.

Sebastian

- -- Package-specific info:
** Version:
Linux version 2.6.38-2-686 (Debian 2.6.38-4) (b...@decadent.org.uk) (gcc 
version 4.4.6 (Debian 4.4.6-2) ) #1 SMP Sat Apr 23 19:04:20 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.38-2-686 root=/dev/mapper/sda3_crypt ro

** Tainted: O (4096)
 * Out-of-tree module has been loaded.
[this is virtualbox - I think that's not relevant]

** Kernel log:
[stripped, rebooted before running reportbug]

** Model information
not available

** Loaded modules:
[stripped, rebooted before running reportbug]

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML 
and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
Subsystem: Lenovo ThinkPad T60/R60 series [17aa:2017]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort+ SERR- PERR- INTx-
Latency: 0
Capabilities: access denied
Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 
00 [VGA controller])
Subsystem: Lenovo ThinkPad T60/R60 series [17aa:201a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at ee10 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at 1800 [size=8]
Region 2: Memory at d000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at ee20 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at unassigned [disabled]
Capabilities: access denied
Kernel driver in use: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
Subsystem: Lenovo ThinkPad T60/R60 series [17aa:201a]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Region 0: Memory at ee18 (32-bit, non-prefetchable) [size=512K]
Capabilities: access denied

00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High 
Definition Audio Controller [8086:27d8] (rev 02)
Subsystem: Lenovo ThinkPad T60/R60 series [17aa:2010]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 47
Region 0: Memory at ee24 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: HDA Intel

00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express 
Port 1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 2000-2fff
Memory behind bridge: 

Bug#624268: [squeeze] include important changes from 2.6.32.39

2011-04-26 Thread Ben Hutchings
On Tue, Apr 26, 2011 at 06:17:08PM -0600, dann frazier wrote:
[...]
  6f396d4a x86, cpu: Fix regression in AMD errata checking code
 
 fixes hangs on some K8 systems

I believe this is a fixup for these:

[...]
  d4274252 x86, AMD: Set ARAT feature on AMD processors
  7a3b25c0 x86, cpu: Clean up AMD erratum 400 workaround
  bba4804e x86, cpu: AMD errata checking framework
 
 These avoid switching to HPET timers in deep C states on AMD
 CPUs. Though obviously an improvement, I'm not really sure what makes
 these candidates for stable - unless people have been seeing hangs w/
 the broadcast timer code on AMD systems?

I'm dubious about the value of these quite large changes, as you may
have seen in discussion on stable-review.  Given that no-one was able
to explain what bug is fixed, and there is a functional change hidden
in the 'cleanup' patch which again no-one was able to explain, I would
favour reverting these.

  17ebcafe x86: Fix a bogus unwind annotation in lib/semaphore_32.S
 
 Not sure what the end user value is here... better kernel backtracing?
[...]

I have no idea either.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110427003506.gd2...@decadent.org.uk



Bug#624266: linux-image-2.6.38-2-686: Upgrading from 2.6.38-3 to 2.6.38-4 breaks fuse.ko

2011-04-26 Thread Sebastian Schmidt
On Wed, Apr 27, 2011 at 01:29:46AM +0100, Ben Hutchings wrote:
 On Wed, Apr 27, 2011 at 01:43:54AM +0200, Sebastian Schmidt wrote:
  After booting the newly installed kernel fuse loads fine.
 
 Right, that's what you're supposed to do.

I'm quite reluctant to reopen this bug, but speaking of supposed to:
Isn't linux-image-* supposed to either increment the version in the
package name when the ABI changes or to *tell* me to reboot?


signature.asc
Description: Digital signature


Bug#624266: linux-image-2.6.38-2-686: Upgrading from 2.6.38-3 to 2.6.38-4 breaks fuse.ko

2011-04-26 Thread Ben Hutchings
On Wed, Apr 27, 2011 at 02:40:07AM +0200, Sebastian Schmidt wrote:
 On Wed, Apr 27, 2011 at 01:29:46AM +0100, Ben Hutchings wrote:
  On Wed, Apr 27, 2011 at 01:43:54AM +0200, Sebastian Schmidt wrote:
   After booting the newly installed kernel fuse loads fine.
  
  Right, that's what you're supposed to do.
 
 I'm quite reluctant to reopen this bug, but speaking of supposed to:
 Isn't linux-image-* supposed to either increment the version in the
 package name when the ABI changes

Not when the ABI changes in a backward-compatible way.

 or to *tell* me to reboot?

I think it's pretty obvious that a kernel upgrade is not complete
without a reboot.  But whereas daemon packages will restart the
daemon, I think we should not automatically restart the kernel!

Now I can see that it might be helpful to provide some sort of
reminder that a reboot will be required, but I don't know how best to
do that.  A debconf message might be suitable, but then the
requirement for acknowledgement (in a default debconf configuration)
might just be annoying.  kernel-package used to generate dire
messages and those really were annoying.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110427010827.ge2...@decadent.org.uk