Bug#708094: linux: FTBFS on powerpcspe due to missing mkimage

2013-05-13 Thread Roland Stigge
Source: linux
Version: 3.8.12-1
Severity: wishlist
Tags: sid
User: debian-powerpc...@breakpoint.cc
Usertags: powerpcspe

Hi,

on powerpcspe[1], linux currently FTBFS like this:

...
  HOSTCC  arch/powerpc/boot/mktree
  WRAParch/powerpc/boot/uImage
INFO: Uncompressed kernel (size 0x5d1000) overlaps the address of the 
wrapper(0x40)
INFO: Fixing the link_address of wrapper to (0x60)
mkimage command not found - U-Boot images will not be built
make[6]: *** [arch/powerpc/boot/uImage] Error 1
...

This is because the platforms CONFIG_MPC85xx activated in our powerpcspe config
select CONFIG_DEFAULT_UIMAGE which leads to mkimage (for uImage creation) to be
called.

Adding Build-Depends: u-boot-tools fixes this. Limiting to [powerpcspe] would
be fine for now, IMO.

Thanks in advance,

Roland


[1] http://wiki.debian.org/PowerPCSPEPort


-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: powerpcspe (ppc)

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


-- 
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/20130513070127.31588.17225.report...@spe2.antcom.de



Bug#707960: Bug confirmation

2013-05-13 Thread Thomas Luzat
I can confirm this bug on a Debian sid x86-64 machine trying to mount
a kerberized export:

[ 4872.101092] rpc.gssd[26050]: segfault at 1 ip 7f32992e1e95 sp
7fff6a3b8970 error 4 in libgssglue.so.1.0.0[7f32992de000+9000]
[ 4918.920391] rpc.gssd[26179]: segfault at 1 ip 7f4b9e17ae95 sp
7fffe7684470 error 4 in libgssglue.so.1.0.0[7f4b9e177000+9000]

Reverting to 1.2.6-3 helps. Installing nfs-kernel-server and starting
statd both do not help. The machine (client) is running a custom-built
3.9.1 kernel. I'd be happy to provide additional information on
request.

Cheers,

Thomas Luzat

--
Thomas Luzat  SoftwareentwicklungUSt-IdNr.: DE255529066
Schlagbaumstege 4 Fon: +49 281 3361281-2 Web:   http://luzat.com
46485 Wesel   Fax: +49 281 3361281-3 E-Mail:tho...@luzat.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/capz_h9mh8vvtoopvya+zu44ahwl1sz0m2lnyhj8rsqys7zc...@mail.gmail.com



Bug#708094: linux: FTBFS on powerpcspe due to missing mkimage

2013-05-13 Thread Ben Hutchings
Control: tag -1 moreinfo

On Mon, 2013-05-13 at 09:01 +0200, Roland Stigge wrote:
 Source: linux
 Version: 3.8.12-1
 Severity: wishlist
 Tags: sid
 User: debian-powerpc...@breakpoint.cc
 Usertags: powerpcspe
 
 Hi,
 
 on powerpcspe[1], linux currently FTBFS like this:
 
 ...
   HOSTCC  arch/powerpc/boot/mktree
   WRAParch/powerpc/boot/uImage
 INFO: Uncompressed kernel (size 0x5d1000) overlaps the address of the 
 wrapper(0x40)
 INFO: Fixing the link_address of wrapper to (0x60)
 mkimage command not found - U-Boot images will not be built
 make[6]: *** [arch/powerpc/boot/uImage] Error 1
 ...
 
 This is because the platforms CONFIG_MPC85xx activated in our powerpcspe 
 config
 select CONFIG_DEFAULT_UIMAGE which leads to mkimage (for uImage creation) to 
 be
 called.
 
 Adding Build-Depends: u-boot-tools fixes this. Limiting to [powerpcspe] would
 be fine for now, IMO.

On many ARM platforms, u-boot images are generated by flash-kernel at
installation time.  Shouldn't this platform be handled in the same way?

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an expert.


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


Processed: Re: Bug#708094: linux: FTBFS on powerpcspe due to missing mkimage

2013-05-13 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 moreinfo
Bug #708094 [src:linux] linux: FTBFS on powerpcspe due to missing mkimage
Added tag(s) moreinfo.

-- 
708094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708094
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.b708094.136845243321109.transcr...@bugs.debian.org



Bug#708094: linux: FTBFS on powerpcspe due to missing mkimage

2013-05-13 Thread Roland Stigge
Hi,

On 05/13/2013 03:40 PM, Ben Hutchings wrote:
 On Mon, 2013-05-13 at 09:01 +0200, Roland Stigge wrote:
 Source: linux
 Version: 3.8.12-1
 Severity: wishlist
 Tags: sid
 User: debian-powerpc...@breakpoint.cc
 Usertags: powerpcspe

 Hi,

 on powerpcspe[1], linux currently FTBFS like this:

 ...
   HOSTCC  arch/powerpc/boot/mktree
   WRAParch/powerpc/boot/uImage
 INFO: Uncompressed kernel (size 0x5d1000) overlaps the address of the 
 wrapper(0x40)
 INFO: Fixing the link_address of wrapper to (0x60)
 mkimage command not found - U-Boot images will not be built
 make[6]: *** [arch/powerpc/boot/uImage] Error 1
 ...

 This is because the platforms CONFIG_MPC85xx activated in our powerpcspe 
 config
 select CONFIG_DEFAULT_UIMAGE which leads to mkimage (for uImage creation) to 
 be
 called.

 Adding Build-Depends: u-boot-tools fixes this. Limiting to [powerpcspe] would
 be fine for now, IMO.
 
 On many ARM platforms, u-boot images are generated by flash-kernel at
 installation time.  Shouldn't this platform be handled in the same way?

Thank you for the quick response!

You are right - the uImage generated in the above step is not directly
used on boot (without flashing separately on typical PowerPCSPE boards).
I'm working on a solution for this, separately.

However, the powerpc specific option CONFIG_DEFAULT_UIMAGE always tries
to build uImage at (Debian package) linux build time, see
arch/powerpc/boot/Makefile:207:

image-$(CONFIG_DEFAULT_UIMAGE)  += uImage

So can we add u-boot-tools as build-dep for powerpcspe? Or do you have a
different suggestion for making the default package linux build?

Thanks in advance,

Roland


-- 
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/5190fff4.1040...@antcom.de



Bug#708156: nfs-common: Please include /etc/request-key.d/id_resolver.conf

2013-05-13 Thread Norbert Veber
Package: nfs-common
Version: 1:1.2.8-1
Severity: normal

Hi,

Thanks for packaging version 1.2.8 so promptly (re Bug#707258)!

I have installed this version, but the request-key errors persist with
newer kernels (at least anything newer than 3.7).  

May 13 11:19:10 hostname request-key: Cannot find command to construct key 
213728982
etc..

It turns out that an additonal config file needs to be provided.  

In RHEL they named this file /etc/request-key.d/id_resolver.conf, so
Debian can probably just use the same name.  As per 'man nfsidmap' I
used the following line:

$ cat /etc/request-key.d/id_resolver.conf 
createid_resolver**/usr/sbin/nfsidmap -t 600 %k %d

Once that file was created, the errors stop, and NFSv4 works properly
again.

Thanks,

Norbert


-- 
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/20130513153304.30761.19331.report...@pyre.virge.net



Bug#708094: linux: FTBFS on powerpcspe due to missing mkimage

2013-05-13 Thread Ben Hutchings
On Mon, May 13, 2013 at 05:00:04PM +0200, Roland Stigge wrote:
 Hi,
 
 On 05/13/2013 03:40 PM, Ben Hutchings wrote:
  On Mon, 2013-05-13 at 09:01 +0200, Roland Stigge wrote:
  Source: linux
  Version: 3.8.12-1
  Severity: wishlist
  Tags: sid
  User: debian-powerpc...@breakpoint.cc
  Usertags: powerpcspe
 
  Hi,
 
  on powerpcspe[1], linux currently FTBFS like this:
 
  ...
HOSTCC  arch/powerpc/boot/mktree
WRAParch/powerpc/boot/uImage
  INFO: Uncompressed kernel (size 0x5d1000) overlaps the address of the 
  wrapper(0x40)
  INFO: Fixing the link_address of wrapper to (0x60)
  mkimage command not found - U-Boot images will not be built
  make[6]: *** [arch/powerpc/boot/uImage] Error 1
  ...
 
  This is because the platforms CONFIG_MPC85xx activated in our powerpcspe 
  config
  select CONFIG_DEFAULT_UIMAGE which leads to mkimage (for uImage creation) 
  to be
  called.
 
  Adding Build-Depends: u-boot-tools fixes this. Limiting to [powerpcspe] 
  would
  be fine for now, IMO.
  
  On many ARM platforms, u-boot images are generated by flash-kernel at
  installation time.  Shouldn't this platform be handled in the same way?
 
 Thank you for the quick response!
 
 You are right - the uImage generated in the above step is not directly
 used on boot (without flashing separately on typical PowerPCSPE boards).
 I'm working on a solution for this, separately.
 
 However, the powerpc specific option CONFIG_DEFAULT_UIMAGE always tries
 to build uImage at (Debian package) linux build time, see
 arch/powerpc/boot/Makefile:207:
 
 image-$(CONFIG_DEFAULT_UIMAGE)  += uImage
 
 So can we add u-boot-tools as build-dep for powerpcspe? Or do you have a
 different suggestion for making the default package linux build?

Please provide a patch to disable building the unwanted file.

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/20130513162913.ga31...@decadent.org.uk



Processed: Re: lxc-attach does not work

2013-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # duplicate of 595920
 reassign 708144 linux
Bug #708144 [lxc] lxc-attach fails to attach to a running container
Bug reassigned from package 'lxc' to 'linux'.
No longer marked as found in versions lxc/0.8.0~rc1-8+deb7u1, 
lxc/0.9.0~alpha3-2, and lxc/0.9.0-4.
Ignoring request to alter fixed versions of bug #708144 to the same values 
previously set
 close 708144 3.8-1~experimental.1
Bug #708144 [linux] lxc-attach fails to attach to a running container
There is no source info for the package 'linux' at version 
'3.8-1~experimental.1' with architecture ''
Unable to make a source version for version '3.8-1~experimental.1'
Marked as fixed in versions 3.8-1~experimental.1.
Bug #708144 [linux] lxc-attach fails to attach to a running container
Marked Bug as done
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
708144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708144
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.13684630827842.transcr...@bugs.debian.org



Bug#708144: lxc-attach does not work

2013-05-13 Thread Daniel Baumann
# duplicate of 595920
reassign 708144 linux
close 708144 3.8-1~experimental.1
thanks

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


-- 
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/51911760.5090...@progress-technologies.net



Bug#708156: nfs-common: Please include /etc/request-key.d/id_resolver.conf

2013-05-13 Thread Luk Claes
On 05/13/2013 05:33 PM, Norbert Veber wrote:

 Hi,

Hi

 Thanks for packaging version 1.2.8 so promptly (re Bug#707258)!

I intended to upload a newer upstream after wheezy's release anyway...

 I have installed this version, but the request-key errors persist with
 newer kernels (at least anything newer than 3.7).  
 
 May 13 11:19:10 hostname request-key: Cannot find command to construct key 
 213728982
 etc..
 
 It turns out that an additonal config file needs to be provided.  
 
 In RHEL they named this file /etc/request-key.d/id_resolver.conf, so
 Debian can probably just use the same name.  As per 'man nfsidmap' I
 used the following line:
 
 $ cat /etc/request-key.d/id_resolver.conf 
 createid_resolver**/usr/sbin/nfsidmap -t 600 %k %d
 
 Once that file was created, the errors stop, and NFSv4 works properly
 again.

Thank you very much. Hopefully the segfaults some people got are also
fixed now! New package uploading now...

Cheers

Luk


-- 
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/5191295b.8010...@debian.org



Bug#638157: marked as done (nfs-kernel-server: attempt to mount -t nfs4 -o sec=krb5 hangs on squeeze, works with nfs-utils from testing)

2013-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2013 18:02:51 +
with message-id e1ubx5h-0003lv...@franck.debian.org
and subject line Bug#638157: fixed in nfs-utils 1:1.2.8-2
has caused the Debian Bug report #638157,
regarding nfs-kernel-server: attempt to mount -t nfs4 -o sec=krb5 hangs on 
squeeze, works with nfs-utils from testing
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.)


-- 
638157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: nfs-kernel-server
Version: 1:1.2.2-4
Severity: important

Hi, 

I observed the following after installing a Debian Squeeze network on
virtual machines:

After switching on sec=krb5 for the NFSv4 mounts, the mount process
hangs immeditely, it doesn't return at all:

root@workstation00:~# mount -t nfs4 -o sec=krb5 mainserver:/home0 /mnt

No error, nothing.  Ctrl-c brings you back to the command line.  The
same when logging in, as the automounter tries to mount the home
directory: After entering the password nothing happens.

I tried to find the reason and checked logs with rpc.gssd -f -rrr  
and rpc.svcgssd -fvvv, but could not find any indication there,
anything seems to work as expected.

I tried the kernel 2.6.38-bpo.2-686 from backports, same results.

Finally I installed the nfs-common and nfs-kernel-server from testing
on the nfs-server: 
ii  nfs-common 1:1.2.4-1
ii  nfs-kernel-server  1:1.2.4-1

And without further changes anything worked as expected.  Something
comparable (with some patch) is described here:
URL:http://www.spinics.net/lists/linux-nfs/msg14723.html, same
nfs-utils 1.2.2
 
It would be great if that could be fixed for squeeze.  If I can help
with more debug info, testing or full logs, please let me know.

Best regards,

 Andi



-- Package-specific info (after installing packages from backports/testing):
-- rpcinfo --
root@mainserver:~# rpcinfo
   program version netid addressserviceowner
104tcp6  ::.0.111   portmapper superuser
103tcp6  ::.0.111   portmapper superuser
104udp6  ::.0.111   portmapper superuser
103udp6  ::.0.111   portmapper superuser
104tcp   0.0.0.0.0.111  portmapper superuser
103tcp   0.0.0.0.0.111  portmapper superuser
102tcp   0.0.0.0.0.111  portmapper superuser
104udp   0.0.0.0.0.111  portmapper superuser
103udp   0.0.0.0.0.111  portmapper superuser
102udp   0.0.0.0.0.111  portmapper superuser
104local /var/run/rpcbind.sock  portmapper superuser
103local /var/run/rpcbind.sock  portmapper superuser
1000241udp   0.0.0.0.217.30 status 103
1000241tcp   0.0.0.0.227.137status 103
1000241udp6  ::.147.207 status 103
1000241tcp6  ::.235.58  status 103
132udp   0.0.0.0.8.1nfssuperuser
133udp   0.0.0.0.8.1nfssuperuser
134udp   0.0.0.0.8.1nfssuperuser
1002272udp   0.0.0.0.8.1-  superuser
1002273udp   0.0.0.0.8.1-  superuser
132tcp   0.0.0.0.8.1nfssuperuser
133tcp   0.0.0.0.8.1nfssuperuser
134tcp   0.0.0.0.8.1nfssuperuser
1002272tcp   0.0.0.0.8.1-  superuser
1002273tcp   0.0.0.0.8.1-  superuser
1000211udp   0.0.0.0.159.30 nlockmgr   superuser
1000213udp   0.0.0.0.159.30 nlockmgr   superuser
1000214udp   0.0.0.0.159.30 nlockmgr   superuser
1000211tcp   0.0.0.0.191.167nlockmgr   superuser
1000213tcp   0.0.0.0.191.167nlockmgr   superuser
1000214tcp   0.0.0.0.191.167nlockmgr   superuser
151udp   0.0.0.0.192.8  mountd superuser
151tcp   0.0.0.0.212.240mountd superuser
151udp6  ::.190.124 mountd superuser
151tcp6  ::.170.160 mountd superuser

Bug#707908: marked as done (Missing source for nfsdcltrack.8)

2013-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2013 18:02:51 +
with message-id e1ubx5h-0003le...@franck.debian.org
and subject line Bug#707908: fixed in nfs-utils 1:1.2.8-2
has caused the Debian Bug report #707908,
regarding Missing source for nfsdcltrack.8
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.)


-- 
707908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: nfs-kernel-server
Version: 1:1.2.8-1
Severity: serious
Tags: upstream

Hi,

The nfsdcltrack.8 man page is “Automatically generated by Pod::Man 2.25
(Pod::Simple 3.16)” but the POD source is not provided, thus failing to
comply with the terms of its licence (GPL2+) and DFSG2.

Regards

David


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: nfs-utils
Source-Version: 1:1.2.8-2

We believe that the bug you reported is fixed in the latest version of
nfs-utils, which is due to be installed in the Debian FTP archive.

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 707...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luk Claes l...@debian.org (supplier of updated nfs-utils 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: SHA256

Format: 1.8
Date: Mon, 13 May 2013 19:46:42 +0200
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source amd64
Version: 1:1.2.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team debian-kernel@lists.debian.org
Changed-By: Luk Claes l...@debian.org
Description: 
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 638157 707908 707960 708156
Changes: 
 nfs-utils (1:1.2.8-2) unstable; urgency=medium
 .
   * Fix reportbug scripts to use rpcinfo in /usr/sbin.
   * Add id_resolver.conf to fix nfsidmap invocation
 (Closes: #708156, #638157, #707960).
   * Remove autogenerated roff as nfsdcltrack.man is meant to be used
 as the actual source according to author (Closes: #707908).
Checksums-Sha1: 
 b7b40569b221c91d88557b9a6023121ba5e7a021 2263 nfs-utils_1.2.8-2.dsc
 099ac2249faa5a02f4b375c487546e5a219a02cd 38033 nfs-utils_1.2.8-2.debian.tar.bz2
 f2ebfda07f46858c8683d2e41893d28307ad7aa1 144776 
nfs-kernel-server_1.2.8-2_amd64.deb
 16945acdb8e4e3ceaadc330faf067df721a610aa 271020 nfs-common_1.2.8-2_amd64.deb
Checksums-Sha256: 
 ce374c1b5c32f84e7802e83e29e5089ef04665dd4b6e29a01aa927473ccb7540 2263 
nfs-utils_1.2.8-2.dsc
 84e90889e401bc1b27b68677a61edfe7dd62d2243ed43f639dbca534a9972e92 38033 
nfs-utils_1.2.8-2.debian.tar.bz2
 bac081bc4fbde32d1bb9ea582f02c399c50ec5fa1f94814e044f02b3b0bf1b6a 144776 
nfs-kernel-server_1.2.8-2_amd64.deb
 a2b8aa1d4c123f71af347c8f37e2b56094b68fecee82de35c7a0e8b8f9b2f750 271020 
nfs-common_1.2.8-2_amd64.deb
Files: 
 50a1e44f3afe830b5836b6d030986a37 2263 net standard nfs-utils_1.2.8-2.dsc
 4e5eca1f4ee4429b981e037b1c18a55e 38033 net standard 
nfs-utils_1.2.8-2.debian.tar.bz2
 439d9927e9b25f834f9d7ea701a81e03 144776 net optional 
nfs-kernel-server_1.2.8-2_amd64.deb
 8b0e68894293bd176f0abe8d7d5196d3 271020 net standard 
nfs-common_1.2.8-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRkSjHAAoJECEnNxubsjBieJoP/i/uOvk54rZrqT/NOnl/Jt8g
G60f77s1MrY6cv5cfR3MWX2GgN3H5I6tsNaXkq34TW+L53nTJvnzMj3Y0yxZGwiq
kWaoQ+NI3QjFqMjxcyFgqJwM4jKoiYB3a/HCKetJC0m+XyN67OcqHRr0hI3IZ7y+
60oKv/1Wmmw3sYsUeVp5wb4ENt2ibqYi6V8tiq5ckSVHTN9uyCNqRfohWkP1vzXR
U9B+kBywCkrNSiyAzkn3hqZb6rtZFeGlJnFdBzFguLEzqG+srUSiDGvOFkT7D3cW
8r6mztrSBXgoDsS6HFYy9cpfKRY/PCANsrITqT/QUopVUvK5yKiZSxsNlS3B4VMz
08CNQ5/iUt1pvjd6PaztAJjagW8PMQFQmDkgTdiZMMm66o7YPov2ImlrhhkSSkBS
EGAM5sBefXMWJ36JxpLWd7GEixJsYOX7ebOap7reZ1YK17cG27qcajrkwYWc1tgE
MYoFlBZAffS6qgvkNJ7qZWRIlXuYLB0KMRo4KUl5CxCkBOa3j/MYWojqmRWmgzq1
j5TPzDBXBHcVWzSR8eKi95qXRNI5PeKhealntCY3EtmnqAqAN6Cb1OB3Rd9OFMVj
HFC8hbnFmWj/0Oz0+RML+d84H+jFf+ZJY8QMvZa02BgL/toqMn/srn+FTitE26K2
+kkjos/EwOXAqZf7AfHO
=g5AR
-END PGP SIGNATUREEnd Message---


Bug#707960: marked as done (rpc.gssd segfaults when mounting a nfsv4 volume)

2013-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2013 18:02:51 +
with message-id e1ubx5h-0003lj...@franck.debian.org
and subject line Bug#707960: fixed in nfs-utils 1:1.2.8-2
has caused the Debian Bug report #707960,
regarding rpc.gssd segfaults when mounting a nfsv4 volume
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.)


-- 
707960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: nfs-common
Version: 1:1.2.8-1
Severity: grave

(elided):/  /media/nfs  nfs4noauto,soft,intr,sec=krb5p  0 0

[2262594.734234] rpc.gssd[2729]: segfault at 1 ip f74714ba sp 
ff830170 error 4 in libgssglue.so.1.0.0[f746e000+8000]

Reverting nfs-common to 1:1.2.6-3 fixes the issue.

BTW:

/usr/share/bug/nfs-common/script: 5: /usr/share/bug/nfs-common/script: rpcinfo: 
not found

-- Package-specific info:
-- rpcinfo --

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

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

Versions of packages nfs-common depends on:
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-41
ii  libc6   2.17-1
ii  libcap2 1:2.22-1.2
ii  libcomerr2  1.42.5-1.1
ii  libdevmapper1.02.1  2:1.02.77-1
ii  libevent-2.0-5  2.0.19-stable-3
ii  libgssglue1 0.4-2
ii  libk5crypto31.10.1+dfsg-5
ii  libkeyutils11.5.5-7
ii  libkrb5-3   1.10.1+dfsg-5
ii  libmount1   2.20.1-5.3
ii  libnfsidmap20.25-4
ii  libtirpc1   0.2.2-5
ii  libwrap07.6.q-24
ii  lsb-base4.1+Debian9
ii  rpcbind 0.2.0-8
ii  ucf 3.0025+nmu3

Versions of packages nfs-common recommends:
ii  python  2.7.3-4

Versions of packages nfs-common suggests:
pn  open-iscsi  none
pn  watchdognone

-- no debconf information

-- 
ciao,
Marco


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: nfs-utils
Source-Version: 1:1.2.8-2

We believe that the bug you reported is fixed in the latest version of
nfs-utils, which is due to be installed in the Debian FTP archive.

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 707...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luk Claes l...@debian.org (supplier of updated nfs-utils 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: SHA256

Format: 1.8
Date: Mon, 13 May 2013 19:46:42 +0200
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source amd64
Version: 1:1.2.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team debian-kernel@lists.debian.org
Changed-By: Luk Claes l...@debian.org
Description: 
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 638157 707908 707960 708156
Changes: 
 nfs-utils (1:1.2.8-2) unstable; urgency=medium
 .
   * Fix reportbug scripts to use rpcinfo in /usr/sbin.
   * Add id_resolver.conf to fix nfsidmap invocation
 (Closes: #708156, #638157, #707960).
   * Remove autogenerated roff as nfsdcltrack.man is meant to be used
 as the actual source according to author (Closes: #707908).
Checksums-Sha1: 
 b7b40569b221c91d88557b9a6023121ba5e7a021 2263 nfs-utils_1.2.8-2.dsc
 099ac2249faa5a02f4b375c487546e5a219a02cd 38033 nfs-utils_1.2.8-2.debian.tar.bz2
 f2ebfda07f46858c8683d2e41893d28307ad7aa1 144776 
nfs-kernel-server_1.2.8-2_amd64.deb
 16945acdb8e4e3ceaadc330faf067df721a610aa 271020 nfs-common_1.2.8-2_amd64.deb
Checksums-Sha256: 
 ce374c1b5c32f84e7802e83e29e5089ef04665dd4b6e29a01aa927473ccb7540 2263 
nfs-utils_1.2.8-2.dsc
 84e90889e401bc1b27b68677a61edfe7dd62d2243ed43f639dbca534a9972e92 38033 
nfs-utils_1.2.8-2.debian.tar.bz2
 bac081bc4fbde32d1bb9ea582f02c399c50ec5fa1f94814e044f02b3b0bf1b6a 144776 
nfs-kernel-server_1.2.8-2_amd64.deb
 a2b8aa1d4c123f71af347c8f37e2b56094b68fecee82de35c7a0e8b8f9b2f750 271020 
nfs-common_1.2.8-2_amd64.deb
Files: 
 50a1e44f3afe830b5836b6d030986a37 2263 net standard 

Bug#708156: marked as done (nfs-common: Please include /etc/request-key.d/id_resolver.conf)

2013-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2013 18:02:51 +
with message-id e1ubx5h-0003lm...@franck.debian.org
and subject line Bug#708156: fixed in nfs-utils 1:1.2.8-2
has caused the Debian Bug report #708156,
regarding nfs-common: Please include /etc/request-key.d/id_resolver.conf
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.)


-- 
708156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: nfs-common
Version: 1:1.2.8-1
Severity: normal

Hi,

Thanks for packaging version 1.2.8 so promptly (re Bug#707258)!

I have installed this version, but the request-key errors persist with
newer kernels (at least anything newer than 3.7).  

May 13 11:19:10 hostname request-key: Cannot find command to construct key 
213728982
etc..

It turns out that an additonal config file needs to be provided.  

In RHEL they named this file /etc/request-key.d/id_resolver.conf, so
Debian can probably just use the same name.  As per 'man nfsidmap' I
used the following line:

$ cat /etc/request-key.d/id_resolver.conf 
createid_resolver**/usr/sbin/nfsidmap -t 600 %k %d

Once that file was created, the errors stop, and NFSv4 works properly
again.

Thanks,

Norbert
---End Message---
---BeginMessage---
Source: nfs-utils
Source-Version: 1:1.2.8-2

We believe that the bug you reported is fixed in the latest version of
nfs-utils, which is due to be installed in the Debian FTP archive.

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 708...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luk Claes l...@debian.org (supplier of updated nfs-utils 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: SHA256

Format: 1.8
Date: Mon, 13 May 2013 19:46:42 +0200
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source amd64
Version: 1:1.2.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team debian-kernel@lists.debian.org
Changed-By: Luk Claes l...@debian.org
Description: 
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 638157 707908 707960 708156
Changes: 
 nfs-utils (1:1.2.8-2) unstable; urgency=medium
 .
   * Fix reportbug scripts to use rpcinfo in /usr/sbin.
   * Add id_resolver.conf to fix nfsidmap invocation
 (Closes: #708156, #638157, #707960).
   * Remove autogenerated roff as nfsdcltrack.man is meant to be used
 as the actual source according to author (Closes: #707908).
Checksums-Sha1: 
 b7b40569b221c91d88557b9a6023121ba5e7a021 2263 nfs-utils_1.2.8-2.dsc
 099ac2249faa5a02f4b375c487546e5a219a02cd 38033 nfs-utils_1.2.8-2.debian.tar.bz2
 f2ebfda07f46858c8683d2e41893d28307ad7aa1 144776 
nfs-kernel-server_1.2.8-2_amd64.deb
 16945acdb8e4e3ceaadc330faf067df721a610aa 271020 nfs-common_1.2.8-2_amd64.deb
Checksums-Sha256: 
 ce374c1b5c32f84e7802e83e29e5089ef04665dd4b6e29a01aa927473ccb7540 2263 
nfs-utils_1.2.8-2.dsc
 84e90889e401bc1b27b68677a61edfe7dd62d2243ed43f639dbca534a9972e92 38033 
nfs-utils_1.2.8-2.debian.tar.bz2
 bac081bc4fbde32d1bb9ea582f02c399c50ec5fa1f94814e044f02b3b0bf1b6a 144776 
nfs-kernel-server_1.2.8-2_amd64.deb
 a2b8aa1d4c123f71af347c8f37e2b56094b68fecee82de35c7a0e8b8f9b2f750 271020 
nfs-common_1.2.8-2_amd64.deb
Files: 
 50a1e44f3afe830b5836b6d030986a37 2263 net standard nfs-utils_1.2.8-2.dsc
 4e5eca1f4ee4429b981e037b1c18a55e 38033 net standard 
nfs-utils_1.2.8-2.debian.tar.bz2
 439d9927e9b25f834f9d7ea701a81e03 144776 net optional 
nfs-kernel-server_1.2.8-2_amd64.deb
 8b0e68894293bd176f0abe8d7d5196d3 271020 net standard 
nfs-common_1.2.8-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRkSjHAAoJECEnNxubsjBieJoP/i/uOvk54rZrqT/NOnl/Jt8g
G60f77s1MrY6cv5cfR3MWX2GgN3H5I6tsNaXkq34TW+L53nTJvnzMj3Y0yxZGwiq
kWaoQ+NI3QjFqMjxcyFgqJwM4jKoiYB3a/HCKetJC0m+XyN67OcqHRr0hI3IZ7y+
60oKv/1Wmmw3sYsUeVp5wb4ENt2ibqYi6V8tiq5ckSVHTN9uyCNqRfohWkP1vzXR
U9B+kBywCkrNSiyAzkn3hqZb6rtZFeGlJnFdBzFguLEzqG+srUSiDGvOFkT7D3cW
8r6mztrSBXgoDsS6HFYy9cpfKRY/PCANsrITqT/QUopVUvK5yKiZSxsNlS3B4VMz
08CNQ5/iUt1pvjd6PaztAJjagW8PMQFQmDkgTdiZMMm66o7YPov2ImlrhhkSSkBS
EGAM5sBefXMWJ36JxpLWd7GEixJsYOX7ebOap7reZ1YK17cG27qcajrkwYWc1tgE

Processing of nfs-utils_1.2.8-2_amd64.changes

2013-05-13 Thread Debian FTP Masters
nfs-utils_1.2.8-2_amd64.changes uploaded successfully to localhost
along with the files:
  nfs-utils_1.2.8-2.dsc
  nfs-utils_1.2.8-2.debian.tar.bz2
  nfs-kernel-server_1.2.8-2_amd64.deb
  nfs-common_1.2.8-2_amd64.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/e1ubx0h-0002cg...@franck.debian.org



nfs-utils_1.2.8-2_amd64.changes ACCEPTED into unstable

2013-05-13 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 May 2013 19:46:42 +0200
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source amd64
Version: 1:1.2.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team debian-kernel@lists.debian.org
Changed-By: Luk Claes l...@debian.org
Description: 
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 638157 707908 707960 708156
Changes: 
 nfs-utils (1:1.2.8-2) unstable; urgency=medium
 .
   * Fix reportbug scripts to use rpcinfo in /usr/sbin.
   * Add id_resolver.conf to fix nfsidmap invocation
 (Closes: #708156, #638157, #707960).
   * Remove autogenerated roff as nfsdcltrack.man is meant to be used
 as the actual source according to author (Closes: #707908).
Checksums-Sha1: 
 b7b40569b221c91d88557b9a6023121ba5e7a021 2263 nfs-utils_1.2.8-2.dsc
 099ac2249faa5a02f4b375c487546e5a219a02cd 38033 nfs-utils_1.2.8-2.debian.tar.bz2
 f2ebfda07f46858c8683d2e41893d28307ad7aa1 144776 
nfs-kernel-server_1.2.8-2_amd64.deb
 16945acdb8e4e3ceaadc330faf067df721a610aa 271020 nfs-common_1.2.8-2_amd64.deb
Checksums-Sha256: 
 ce374c1b5c32f84e7802e83e29e5089ef04665dd4b6e29a01aa927473ccb7540 2263 
nfs-utils_1.2.8-2.dsc
 84e90889e401bc1b27b68677a61edfe7dd62d2243ed43f639dbca534a9972e92 38033 
nfs-utils_1.2.8-2.debian.tar.bz2
 bac081bc4fbde32d1bb9ea582f02c399c50ec5fa1f94814e044f02b3b0bf1b6a 144776 
nfs-kernel-server_1.2.8-2_amd64.deb
 a2b8aa1d4c123f71af347c8f37e2b56094b68fecee82de35c7a0e8b8f9b2f750 271020 
nfs-common_1.2.8-2_amd64.deb
Files: 
 50a1e44f3afe830b5836b6d030986a37 2263 net standard nfs-utils_1.2.8-2.dsc
 4e5eca1f4ee4429b981e037b1c18a55e 38033 net standard 
nfs-utils_1.2.8-2.debian.tar.bz2
 439d9927e9b25f834f9d7ea701a81e03 144776 net optional 
nfs-kernel-server_1.2.8-2_amd64.deb
 8b0e68894293bd176f0abe8d7d5196d3 271020 net standard 
nfs-common_1.2.8-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRkSjHAAoJECEnNxubsjBieJoP/i/uOvk54rZrqT/NOnl/Jt8g
G60f77s1MrY6cv5cfR3MWX2GgN3H5I6tsNaXkq34TW+L53nTJvnzMj3Y0yxZGwiq
kWaoQ+NI3QjFqMjxcyFgqJwM4jKoiYB3a/HCKetJC0m+XyN67OcqHRr0hI3IZ7y+
60oKv/1Wmmw3sYsUeVp5wb4ENt2ibqYi6V8tiq5ckSVHTN9uyCNqRfohWkP1vzXR
U9B+kBywCkrNSiyAzkn3hqZb6rtZFeGlJnFdBzFguLEzqG+srUSiDGvOFkT7D3cW
8r6mztrSBXgoDsS6HFYy9cpfKRY/PCANsrITqT/QUopVUvK5yKiZSxsNlS3B4VMz
08CNQ5/iUt1pvjd6PaztAJjagW8PMQFQmDkgTdiZMMm66o7YPov2ImlrhhkSSkBS
EGAM5sBefXMWJ36JxpLWd7GEixJsYOX7ebOap7reZ1YK17cG27qcajrkwYWc1tgE
MYoFlBZAffS6qgvkNJ7qZWRIlXuYLB0KMRo4KUl5CxCkBOa3j/MYWojqmRWmgzq1
j5TPzDBXBHcVWzSR8eKi95qXRNI5PeKhealntCY3EtmnqAqAN6Cb1OB3Rd9OFMVj
HFC8hbnFmWj/0Oz0+RML+d84H+jFf+ZJY8QMvZa02BgL/toqMn/srn+FTitE26K2
+kkjos/EwOXAqZf7AfHO
=g5AR
-END PGP SIGNATURE-


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/e1ubx5h-0003lp...@franck.debian.org



Bug#708058: cannot set freq 48000 to ep 0x86; beeps cause temporary gnome session hang

2013-05-13 Thread Richard Kettlewell

On 2013-05-12 21:35, Ben Hutchings wrote:

Did the webcam work as an audio device under squeeze?


I've just tested on a machine still running squeeze and audio capture 
works fine.



Can you test whether this is still broken in Linux 3.8 (from unstable)?


I've installed linux-image-3.8-1-amd64 3.8.12-1.  It didn't produce the 
same behaviour immediately.  I'll continue using this kernel for the 
time being.


Audacity had trouble seeing the device (initially it was visible, after 
fiddling with input volume it wasn't).  However, other applications 
could set the input volume and record from it.  I don't know what 
criteria Audacity uses so this may be an irrelevant bug in Audacity!


ttfn/rjk


--
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/51913112.70...@terraraq.org.uk



Processed: tagging 708058

2013-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 708058 - moreinfo
Bug #708058 [src:linux] cannot set freq 48000 to ep 0x86; beeps cause temporary 
gnome session hang
Removed tag(s) moreinfo.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
708058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708058
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.136847016724653.transcr...@bugs.debian.org



linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Thorsten Glaser
Hi all,

ARAnyM cannot boot the latest kernel images (still compiling,
but I copied out vmlinux.gz):

tglase@tglase:~/stuff/aranym/vm2 $ ./run
Running Ara2 on X11: :2
ARAnyM 0.9.15
Using config file: 'aranym.config.x11'
Could not open joystick 0
ARAnyM RTC Timer: /dev/rtc: Permission denied
ARAnyM LILO: Error loading ramdisk 'root.bin'
CPU: Double bus fault detected !
CPU: Halting

Unfortunately, the SDL window stops there. “Headless” does
not show anything either.

I notice its uncompressed size is 4361000 as opposed to the
latest previous kernel image of 3790400 bytes (3.2.35-2).
Is there a known size limit (architectural, like sparc, or
otherwise)?

I put up https://www.freewrt.org/~tg/f/vmlinuz-3.8.12-1-amiga
and https://www.freewrt.org/~tg/f/vmlinuz-3.8.12-1-atari and
would be glad if people can test them (both) on real hardware,
if need be with a minimal initrd as root filesystem (only):
https://www.freewrt.org/~tg/f/mirnitrd

bye,
//mirabilos
-- 
«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and went downhill from there” – “at least jetDB doesn’t claim to
be a database”  (#nosec)‣‣‣ Please let MySQL and MariaDB finally die!


--
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/alpine.deb.2.02.1305132122190.14...@tglase.lan.tarent.de



Bug#708183: linux-image-3.2.0-4-amd64: File access via symlink on tmpfs filesystem gives permission denied

2013-05-13 Thread Henrik Stoerner
Package: src:linux
Version: 3.2.41-2
Severity: important

Dear Maintainer,

on the 3.2.0-4 kernel, access to a directory via a symlink on a tmpfs
filesystem gives permission denied - if the tmpfs filesystem mountpoint
is not owned by root. The same setup on a 2.6.32-5 (Squeeze) system 
works fine.

Apparently, access via a symlink on a tmpfs filesystem fails if the
mountpoint is not owned either by root or by the user attempting to
use the symlink.


This is my test setup:

* Two user accounts, henrik and dummy
* Create directories /test/fsdir and /test/memdir
* Mount a tmpfs filesystem on /test/memdir
* In /test/fsdir: ln -s ../../home/henrik .
* In /test/memdir: create the same link
* Change owner of tmpfs mountpoint: chown dummy:dummy /test/memdir

Now, try this as user henrik:

cd /test/fsdir/henrik -- works
cd /test/memdir/henrik -- fails


Here are the commands used:

 run these as root 
adduser henrik
adduser dummy
mkdir /test /test/fsdir /test/memdir
mount -t tmpfs tmpfs /test/memdir
cd /test/fsdir; ln -s ../../home/henrik .
cd /test/memdir; ln -s ../../home/henrik .
chown dummy:dummy /test/memdir

 run these as user henrik 
# This works:
cd /test/fsdir/henrik
# This fails:
cd /test/memdir/henrik


Tested on clean installs of Wheezy and Squeeze in a Virtualbox
setup, but originally found on a physical server upgraded from
Squeeze to Wheezy.

-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=0741f671-0f50-4b20-993f-6be28b07d50e ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[1.384269] usb usb1: Manufacturer: Linux 3.2.0-4-amd64 ohci_hcd
[1.384270] usb usb1: SerialNumber: :00:06.0
[1.384341] hub 1-0:1.0: USB hub found
[1.384353] hub 1-0:1.0: 8 ports detected
[1.384671] ahci :00:0d.0: version 3.0
[1.384802] ahci: SSS flag set, parallel bus scan disabled
[1.384934] ahci :00:0d.0: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 
impl SATA mode
[1.384937] ahci :00:0d.0: flags: 64bit ncq stag only ccc 
[1.386052] scsi0 : ahci
[1.386160] ata1: SATA max UDMA/133 abar m8192@0xf0806000 port 0xf0806100 
irq 21
[1.386363] ata_piix :00:01.1: version 2.13
[1.388085] scsi1 : ata_piix
[1.389502] scsi2 : ata_piix
[1.389569] ata2: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xd000 irq 14
[1.389572] ata3: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xd008 irq 15
[1.544990] ata3.00: ATAPI: VBOX CD-ROM, 1.0, max UDMA/133
[1.545812] ata3.00: configured for UDMA/33
[1.708334] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[1.708475] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133
[1.708479] ata1.00: 41943040 sectors, multi 128: LBA48 NCQ (depth 31/32)
[1.708674] ata1.00: configured for UDMA/133
[1.708816] scsi 0:0:0:0: Direct-Access ATA  VBOX HARDDISK1.0  
PQ: 0 ANSI: 5
[1.709916] scsi 2:0:0:0: CD-ROMVBOX CD-ROM   1.0  
PQ: 0 ANSI: 5
[1.719128] sd 0:0:0:0: [sda] 41943040 512-byte logical blocks: (21.4 
GB/20.0 GiB)
[1.719153] sd 0:0:0:0: [sda] Write Protect is off
[1.719154] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[1.719164] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[1.745840]  sda: sda1 sda2  sda5 
[1.746065] sd 0:0:0:0: [sda] Attached SCSI disk
[1.747304] sr0: scsi3-mmc drive: 32x/32x xa/form2 tray
[1.747306] cdrom: Uniform CD-ROM driver Revision: 3.20
[1.747506] sr 2:0:0:0: Attached scsi CD-ROM sr0
[1.749104] sd 0:0:0:0: Attached scsi generic sg0 type 0
[1.749148] sr 2:0:0:0: Attached scsi generic sg1 type 5
[1.792308] usb 1-1: new full-speed USB device number 2 using ohci_hcd
[1.952087] PM: Starting manual resume from disk
[1.952090] PM: Hibernation image partition 8:5 present
[1.952091] PM: Looking for hibernation image.
[1.952418] PM: Image not found (code -22)
[1.952419] PM: Hibernation image not present or could not be loaded.
[1.973394] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[2.040074] usb 1-1: New USB device found, idVendor=80ee, idProduct=0021
[2.040077] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[2.040078] usb 1-1: Product: USB Tablet
[2.040087] usb 1-1: Manufacturer: VirtualBox
[2.348442] Switching to clocksource tsc
[3.086456] udevd[277]: starting version 175
[3.258308] input: Unspecified device as /devices/virtual/input/input1
[3.259412] vboxguest: major 0, IRQ 20, I/O port d020, MMIO at 
f040 (size 0x40)
[3.259417] vboxguest: Successfully loaded version 4.1.18_Debian (interface 
0x00010004)
[3.271326] input: PC Speaker as /devices/platform/pcspkr/input/input2
[3.301639] input: Power Button as 

Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Geert Uytterhoeven
Hi Thorsten,

On Mon, May 13, 2013 at 9:30 PM, Thorsten Glaser t...@mirbsd.de wrote:
 ARAnyM cannot boot the latest kernel images (still compiling,
 but I copied out vmlinux.gz):

 tglase@tglase:~/stuff/aranym/vm2 $ ./run
 Running Ara2 on X11: :2
 ARAnyM 0.9.15
 Using config file: 'aranym.config.x11'
 Could not open joystick 0
 ARAnyM RTC Timer: /dev/rtc: Permission denied
 ARAnyM LILO: Error loading ramdisk 'root.bin'
 CPU: Double bus fault detected !
 CPU: Halting

 Unfortunately, the SDL window stops there. “Headless” does
 not show anything either.

 I notice its uncompressed size is 4361000 as opposed to the
 latest previous kernel image of 3790400 bytes (3.2.35-2).
 Is there a known size limit (architectural, like sparc, or
 otherwise)?

Kernel images fail to boot on Atari if they're bigger than 4 MiB.
I also noticed this a while ago when bisecting an allmodconfig boot failure.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds


--
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/CAMuHMdX+t0=J+8a1JoF6Jf=go_roul_kgavjf0dja-cgpgp...@mail.gmail.com



Bug#708183: marked as done (linux-image-3.2.0-4-amd64: File access via symlink on tmpfs filesystem gives permission denied)

2013-05-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 May 2013 22:12:17 +0100
with message-id 20130513211217.gb31...@decadent.org.uk
and subject line Re: Bug#708183: linux-image-3.2.0-4-amd64: File access via 
symlink on tmpfs filesystem gives permission denied
has caused the Debian Bug report #708183,
regarding linux-image-3.2.0-4-amd64: File access via symlink on tmpfs 
filesystem gives permission denied
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.)


-- 
708183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:linux
Version: 3.2.41-2
Severity: important

Dear Maintainer,

on the 3.2.0-4 kernel, access to a directory via a symlink on a tmpfs
filesystem gives permission denied - if the tmpfs filesystem mountpoint
is not owned by root. The same setup on a 2.6.32-5 (Squeeze) system 
works fine.

Apparently, access via a symlink on a tmpfs filesystem fails if the
mountpoint is not owned either by root or by the user attempting to
use the symlink.


This is my test setup:

* Two user accounts, henrik and dummy
* Create directories /test/fsdir and /test/memdir
* Mount a tmpfs filesystem on /test/memdir
* In /test/fsdir: ln -s ../../home/henrik .
* In /test/memdir: create the same link
* Change owner of tmpfs mountpoint: chown dummy:dummy /test/memdir

Now, try this as user henrik:

cd /test/fsdir/henrik -- works
cd /test/memdir/henrik -- fails


Here are the commands used:

 run these as root 
adduser henrik
adduser dummy
mkdir /test /test/fsdir /test/memdir
mount -t tmpfs tmpfs /test/memdir
cd /test/fsdir; ln -s ../../home/henrik .
cd /test/memdir; ln -s ../../home/henrik .
chown dummy:dummy /test/memdir

 run these as user henrik 
# This works:
cd /test/fsdir/henrik
# This fails:
cd /test/memdir/henrik


Tested on clean installs of Wheezy and Squeeze in a Virtualbox
setup, but originally found on a physical server upgraded from
Squeeze to Wheezy.

-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=0741f671-0f50-4b20-993f-6be28b07d50e ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[1.384269] usb usb1: Manufacturer: Linux 3.2.0-4-amd64 ohci_hcd
[1.384270] usb usb1: SerialNumber: :00:06.0
[1.384341] hub 1-0:1.0: USB hub found
[1.384353] hub 1-0:1.0: 8 ports detected
[1.384671] ahci :00:0d.0: version 3.0
[1.384802] ahci: SSS flag set, parallel bus scan disabled
[1.384934] ahci :00:0d.0: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 
impl SATA mode
[1.384937] ahci :00:0d.0: flags: 64bit ncq stag only ccc 
[1.386052] scsi0 : ahci
[1.386160] ata1: SATA max UDMA/133 abar m8192@0xf0806000 port 0xf0806100 
irq 21
[1.386363] ata_piix :00:01.1: version 2.13
[1.388085] scsi1 : ata_piix
[1.389502] scsi2 : ata_piix
[1.389569] ata2: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xd000 irq 14
[1.389572] ata3: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xd008 irq 15
[1.544990] ata3.00: ATAPI: VBOX CD-ROM, 1.0, max UDMA/133
[1.545812] ata3.00: configured for UDMA/33
[1.708334] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[1.708475] ata1.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133
[1.708479] ata1.00: 41943040 sectors, multi 128: LBA48 NCQ (depth 31/32)
[1.708674] ata1.00: configured for UDMA/133
[1.708816] scsi 0:0:0:0: Direct-Access ATA  VBOX HARDDISK1.0  
PQ: 0 ANSI: 5
[1.709916] scsi 2:0:0:0: CD-ROMVBOX CD-ROM   1.0  
PQ: 0 ANSI: 5
[1.719128] sd 0:0:0:0: [sda] 41943040 512-byte logical blocks: (21.4 
GB/20.0 GiB)
[1.719153] sd 0:0:0:0: [sda] Write Protect is off
[1.719154] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[1.719164] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[1.745840]  sda: sda1 sda2  sda5 
[1.746065] sd 0:0:0:0: [sda] Attached SCSI disk
[1.747304] sr0: scsi3-mmc drive: 32x/32x xa/form2 tray
[1.747306] cdrom: Uniform CD-ROM driver Revision: 3.20
[1.747506] sr 2:0:0:0: Attached scsi CD-ROM sr0
[1.749104] sd 0:0:0:0: Attached scsi generic sg0 type 0
[1.749148] sr 2:0:0:0: Attached scsi generic sg1 type 5
[1.792308] usb 1-1: new full-speed USB device number 2 using ohci_hcd
[1.952087] PM: Starting manual resume from disk
[1.952090] PM: Hibernation image partition 8:5 present
[1.952091] PM: 

Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Thorsten Glaser
Geert Uytterhoeven dixit:

Kernel images fail to boot on Atari if they're bigger than 4 MiB.

OK, thanks. What about the others (amiga, bvme*, mac, two mvme*)?

Who’s in charge of the Debian kernel configs (IIRC Stephen Marenka
and Wouter Verhelst)? Or otherwise, could the Debian Linux kernel
team and you Geert work together on getting configs done that boot
on each subarch and “make sense”? (I could probably hack on it
until it’s small enough, but my kernel skillz have mostly not
gone past the Linux 2.0 era…)

Whoever it’ll be, please talk to each other, people ;)

Thanks,
//mirabilos
-- 
Natureshadow Oh, ich hab mim Bauch Mittelklick gemacht, als ich nach dem
Kaffee gegriffen habe…
mirabilos Cool, ich hab ne neue eMail-Signatur
Natureshadow Sag doch sowas nich, wenn ich den Kaffee in der Hand habe!
Gib mir nen Lappen! Schnell! Das kommt aber nicht mit in die Signatur!


--
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/pine.bsm.4.64l.1305132126170.11...@herc.mirbsd.org



Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Christian T. Steigies
On Mon, May 13, 2013 at 11:06:54PM +0200, Geert Uytterhoeven wrote:
 Hi Thorsten,
 
 On Mon, May 13, 2013 at 9:30 PM, Thorsten Glaser t...@mirbsd.de wrote:
  ARAnyM cannot boot the latest kernel images (still compiling,
  but I copied out vmlinux.gz):
 
  tglase@tglase:~/stuff/aranym/vm2 $ ./run
  Running Ara2 on X11: :2
  ARAnyM 0.9.15
  Using config file: 'aranym.config.x11'
  Could not open joystick 0
  ARAnyM RTC Timer: /dev/rtc: Permission denied
  ARAnyM LILO: Error loading ramdisk 'root.bin'
  CPU: Double bus fault detected !
  CPU: Halting
 
  Unfortunately, the SDL window stops there. ???Headless??? does
  not show anything either.
 
  I notice its uncompressed size is 4361000 as opposed to the
  latest previous kernel image of 3790400 bytes (3.2.35-2).
  Is there a known size limit (architectural, like sparc, or
  otherwise)?
 
 Kernel images fail to boot on Atari if they're bigger than 4 MiB.
 I also noticed this a while ago when bisecting an allmodconfig boot failure.

Does not boot on Amiga either, nothing on the screen nor in dmesg
(debug=mem).

Christian


-- 
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/20130513214942.gg11...@chumley.earth.sol



Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Ben Hutchings
On Mon, May 13, 2013 at 09:29:11PM +, Thorsten Glaser wrote:
 Geert Uytterhoeven dixit:
 
 Kernel images fail to boot on Atari if they're bigger than 4 MiB.
 
 OK, thanks. What about the others (amiga, bvme*, mac, two mvme*)?
 
 Who’s in charge of the Debian kernel configs (IIRC Stephen Marenka
 and Wouter Verhelst)? Or otherwise, could the Debian Linux kernel
 team and you Geert work together on getting configs done that boot
 on each subarch and “make sense”? (I could probably hack on it
 until it’s small enough, but my kernel skillz have mostly not
 gone past the Linux 2.0 era…)
 
 Whoever it’ll be, please talk to each other, people ;)

As m68k is not a release architecture, I don't care much what goes
in debian/config/m68k (well, it had better not break gencontrol.py).
Whatever the m68k porters come up with is fine.

If there is an initramfs-supporting bootloader for Atari now, you
could drop a whole lot of built-in stuff.  But let me guess, does
that 4 MB limit include the initramfs too?

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/20130513215028.gc31...@decadent.org.uk



Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Thorsten Glaser
Ben Hutchings dixit:

As m68k is not a release architecture, I don't care much what goes
in debian/config/m68k (well, it had better not break gencontrol.py).
Whatever the m68k porters come up with is fine.

OK, thanks. I’d kinda like to have it somewhat in sync with
the rest of Debian of course, so people who can do informed
decisions should do it.

If there is an initramfs-supporting bootloader for Atari now, you
could drop a whole lot of built-in stuff.  But let me guess, does

The problem here is that you normally do not have access to
“where the kernel is” from the booted Linux system, or need
to go through extra hoops. From my experience in running an
x86 Debian system, the initrd is regenerated very often and
system-specific; kernel images are pretty static and share‐
able as a contrast.

ARAnyM and ataboot can both load initrds. No idea about
other loaders or the other flavours. Also, supposedly,
you can make an installed system “bootable”¹, but I’ve
not yet seen it (I deal mostly with package compilation
and related bugfixes, in VMs, thus not with the out-of-
Linux environment).

① Kinda like lilo or grub with blocklists, from what I heard.

I had an idea to make a “pretty static” initrd which would
then contain a set of tools to load the real kernel and
initrd from ext4fs (or whatever) and kexec it, but that
would need someone to port kexec to m68k first.

that 4 MB limit include the initramfs too?

That is very likely.

bye,
//mirabilos
-- 
22:20⎜asarch The crazy that persists in his craziness becomes a master
22:21⎜asarch And the distance between the craziness and geniality is
only measured by the success 18:35⎜asarch Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent


--
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/pine.bsm.4.64l.1305132216580.11...@herc.mirbsd.org



Re: linux 3.8.12-1 (atari flavour) does not boot

2013-05-13 Thread Ben Hutchings
On Mon, May 13, 2013 at 10:21:50PM +, Thorsten Glaser wrote:
 Ben Hutchings dixit:
 
 As m68k is not a release architecture, I don't care much what goes
 in debian/config/m68k (well, it had better not break gencontrol.py).
 Whatever the m68k porters come up with is fine.
 
 OK, thanks. I’d kinda like to have it somewhat in sync with
 the rest of Debian of course, so people who can do informed
 decisions should do it.
 
 If there is an initramfs-supporting bootloader for Atari now, you
 could drop a whole lot of built-in stuff.  But let me guess, does
 
 The problem here is that you normally do not have access to
 “where the kernel is” from the booted Linux system, or need
 to go through extra hoops. From my experience in running an
 x86 Debian system, the initrd is regenerated very often and
 system-specific; kernel images are pretty static and share‐
 able as a contrast.
[...]

If you use initramfs-tools configured with MODULES=most, the
initramfs is hardly system-specific.

initramfs-tools itself will put the resume (swap) partition device ID
in there, and mdadm will copy in mdadm.conf.  But neither resume from
disk nor booting from md-RAID will work without an initramfs anyway,
so far as I can see.

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/20130513230538.gd31...@decadent.org.uk



Bug#707902: xserver-xorg-video-radeon: No 3D acceleration after Wheezy update

2013-05-13 Thread rich

Hi,

I tried a newer kernel 3.8-1-686-pae, but no luck.
Seems to be the same as 3.2.0-4-686-paefor modeset 0 and 1.

Here is modeset=1 information, probe fails in dmesg log.
-
=== :~$ dmesg | grep -e drm -e radeon


[0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-3.8-1-686-pae root=UUID= ro quiet 
radeon.modeset=1

[7.004741] [drm] Initialized drm 1.1.0 20060810
[7.191986] [drm] radeon kernel modesetting enabled.
[7.193070] [drm] initializing kernel modesetting (RV100 
0x1002:0x5159 0x1002:0x5159).

[7.193118] [drm] register mmio base: 0xD900
[7.193121] [drm] register mmio size: 65536
[7.195941] radeon :01:00.0: putting AGP V2 device into 4x mode
[7.195948] radeon :01:00.0: GTT: 256M 0xC000 - 0xCFFF
[7.195959] radeon :01:00.0: VRAM: 128M 0xD000 - 
0xD7FF (64M used)

[7.204930] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[7.204940] [drm] Driver supports precise vblank timestamp query.
[7.204955] radeon :01:00.0: Fatal error during GPU init
[7.205007] [drm] radeon: finishing device.
[7.205056] [drm] radeon: cp finalized
[7.209748] radeon: probe of :01:00.0 failed with error -22

Thank you for your efforts,
Rich


--
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/519190e5.5040...@stoicgarden.org



Bug#708058: cannot set freq 48000 to ep 0x86; beeps cause temporary gnome session hang

2013-05-13 Thread Ben Hutchings
On Mon, 2013-05-13 at 19:29 +0100, Richard Kettlewell wrote:
 On 2013-05-12 21:35, Ben Hutchings wrote:
  Did the webcam work as an audio device under squeeze?
 
 I've just tested on a machine still running squeeze and audio capture 
 works fine.
[...]

What are the contents of
/sys/devices/pci:00/:00:1d.7/usb2/2-4/quirks under 3.2?

(I'm assuming the webcam shows up at address 2-4 again - check what the
kernel log shows as the address, alongside the manufacturer and product
names.)

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an expert.


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


Re: Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze

2013-05-13 Thread Sergio Balerdi
Hi All

I have the same problem, i have notebook samsung np530, and the fix was
change kernel's version from 3.2 to 3.5

There are a apt-get install  for it!!

after i change to kernel

quantal

the problem doesn't appear any more!!!