gmane.linux.debian.devel.kernel

nfs-utils_1.2.6-2_i386.changes ACCEPTED into unstable

Debian FTP Masters — 2012-05-26T06:06:24



Accepted:
nfs-common_1.2.6-2_i386.deb
  to main/n/nfs-utils/nfs-common_1.2.6-2_i386.deb
nfs-kernel-server_1.2.6-2_i386.deb
  to main/n/nfs-utils/nfs-kernel-server_1.2.6-2_i386.deb
nfs-utils_1.2.6-2.debian.tar.bz2
  to main/n/nfs-utils/nfs-utils_1.2.6-2.debian.tar.bz2
nfs-utils_1.2.6-2.dsc
  to main/n/nfs-utils/nfs-utils_1.2.6-2.dsc


Changes:
nfs-utils (1:1.2.6-2) unstable; urgency=low
 .
  * Move open-iscsi and watchdog to Suggests.


Override entries for your package:
nfs-common_1.2.6-2_i386.deb - standard net
nfs-kernel-server_1.2.6-2_i386.deb - optional net
nfs-utils_1.2.6-2.dsc - source net

Announcing to debian-devel-changes< at >lists.debian.org


Thank you for your contribution to Debian.

Processing of nfs-utils_1.2.6-2_i386.changes

Debian FTP Masters — 2012-05-26T05:53:38

nfs-utils_1.2.6-2_i386.changes uploaded successfully to localhost
along with the files:
  nfs-utils_1.2.6-2.dsc
  nfs-utils_1.2.6-2.debian.tar.bz2
  nfs-kernel-server_1.2.6-2_i386.deb
  nfs-common_1.2.6-2_i386.deb

Greetings,

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

Re: nfs-utils_1.2.6-1_i386.changes ACCEPTED into unstable

Ben Hutchings — 2012-05-26T03:08:06

[...]
[...]

Really?  I think I would be surprised and annoyed to get those
packages automatically installed.

Ben.

Bug#656015: marked as done (base: Monitor EDID not recognized byLinux kernel 3.x on AMD A6 CPU)

Debian Bug Tracking System — 2012-05-26T00:12:14

Your message dated Fri, 25 May 2012 19:10:12 -0500
with message-id <20120526001011.GA3296< at >burratino>
and subject line Re: Monitor EDID not recognized by Linux kernel 3.x on AMD A6 CPU
has caused the Debian Bug report #656015,
regarding base: Monitor EDID not recognized by Linux kernel 3.x on AMD A6 CPU
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 owner< at >bugs.debian.org
immediately.)

Processed (with 1 errors): Re: Monitor EDID not recognized by Linuxkernel 3.x on AMD A6 CPU

Debian Bug Tracking System — 2012-05-26T00:12:06

Processing commands for control< at >bugs.debian.org:

Unknown command or malformed arguments to command.

Bug #656015 [linux-2.6] base: Monitor EDID not recognized by Linux kernel 3.x on AMD A6 CPU
Removed tag(s) moreinfo.
Stopping processing here.

Please contact me if you need assistance.

Bug#656015:

2012-05-25T23:33:29

In package linux-image-3.2.0-2-amd64, version 3.2.18-1, the bug seems to
be fixed.

Sorry for not being able to check for it for so long a time.

Grigor

Bug#626427: Horrible Time Skew, Eventual Near-zero Responsiveness

Jonathan Nieder — 2012-05-25T21:51:36

Hi again,

Sabahattin Gucukoglu wrote:

[...]

Before the machine dies :), could you try a boot without "acpi=off"
and let us know how it goes (presence or absence of skew, logs, etc)?
3.2.y from sid would be fine, 3.3.y from experimental better.

Thanks,
Jonathan

Bug#626427: [Sabahattin Gucukoglu: Re: linux-image-2.6.38-2-686:Horrible Time Skew, Eventual Near-zero Responsiveness]

Jonathan Nieder — 2012-05-25T21:41:40


Thanks, doing so.

Processed: Re: timeout on modprobe -b pci:xxxx, oopses (Re: Theproblem is hotplug acpi)

Debian Bug Tracking System — 2012-05-25T21:36:05

Processing commands for control< at >bugs.debian.org:

Bug #665493 [linux-2.6] linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:xxxx)
Marked as found in versions linux-2.6/3.2.17-1.
Stopping processing here.

Please contact me if you need assistance.

nfs-utils_1.2.6-1_i386.changes ACCEPTED into unstable

Debian FTP Masters — 2012-05-25T21:02:05



Accepted:
nfs-common_1.2.6-1_i386.deb
  to main/n/nfs-utils/nfs-common_1.2.6-1_i386.deb
nfs-kernel-server_1.2.6-1_i386.deb
  to main/n/nfs-utils/nfs-kernel-server_1.2.6-1_i386.deb
nfs-utils_1.2.6-1.debian.tar.bz2
  to main/n/nfs-utils/nfs-utils_1.2.6-1.debian.tar.bz2
nfs-utils_1.2.6-1.dsc
  to main/n/nfs-utils/nfs-utils_1.2.6-1.dsc
nfs-utils_1.2.6.orig.tar.bz2
  to main/n/nfs-utils/nfs-utils_1.2.6.orig.tar.bz2


Changes:
nfs-utils (1:1.2.6-1) unstable; urgency=low
 .
  * New upstream version
    - Remove 18-dont-use-PAGE_SIZE.patch: merged upstream.
    - Update other patches.
    - Install osd_login (part of the autologin feature).
      - Add open-iscsi and watchdog to Recommends.
  * Check for blank exports file (Closes: #673798).
  * Add 18-osd_login-sbindir.patch to avoid FTBFS
  * Add 19-iscsiadm-path.patch so osd_login works


Override entries for your package:
nfs-common_1.2.6-1_i386.deb - standard net
nfs-kernel-server_1.2.6-1_i386.deb - optional net
nfs-utils_1.2.6-1.dsc - source net

Announcing

Bug#673798: marked as done (nfs-kernel-server: Check for blankexports file, not just existence)

Debian Bug Tracking System — 2012-05-25T21:06:52

Your message dated Fri, 25 May 2012 21:02:05 +0000
with message-id <E1SY1e9-00046O-Na< at >franck.debian.org>
and subject line Bug#673798: fixed in nfs-utils 1:1.2.6-1
has caused the Debian Bug report #673798,
regarding nfs-kernel-server: Check for blank exports file, not just existence
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 owner< at >bugs.debian.org
immediately.)

Bug#665493: The problem is hotplug acpi

Jeroen Nijhof — 2012-05-25T20:32:55

Hello again,

Upgrading to 3.2.17-1 did not help, so I started to compile linux-stable
v.3.2.6 and v3.2.15. It turns out that the problem is not the patches
between them, but the changed configuration: 

on my  HP Pavilion dv6 laptop, linux-stable v3.2.15 boots ok when
compiled with the configuration file from linux-image-3.2.0-1-amd64 (v3.2.6-1),
but not with the one from linux-image-3.2.0-2-amd64 (v3.2.17-1).

Bisecting the configuration, the offending change is the one from

          CONFIG_HOTPLUG_PCI_ACPI=m
to 
          CONFIG_HOTPLUG_PCI_ACPI=y

(see the attached configuration files: with config.good it boots fine,
config.bad doesn't).
So apparently that laptop does not like ACPI hotplug.

If I understand it correctly CONFIG_HOTPLUG_PCI_ACPI=m results in module
acpiphp. In the 3.2.0-1 kernel that is not loaded; but loading it after booting
(with 'modprobe acpiphp') doesn't cause any crashes.

Is there a kernel boot parameter, maybe, with which I can disable the
built-in ACPI hotplug?

By the way, the

Processing of nfs-utils_1.2.6-1_i386.changes

Debian FTP Masters — 2012-05-25T20:34:37

nfs-utils_1.2.6-1_i386.changes uploaded successfully to localhost
along with the files:
  nfs-utils_1.2.6-1.dsc
  nfs-utils_1.2.6.orig.tar.bz2
  nfs-utils_1.2.6-1.debian.tar.bz2
  nfs-kernel-server_1.2.6-1_i386.deb
  nfs-common_1.2.6-1_i386.deb

Greetings,

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

Bug#673107: dependency error

Arnaud Patard — 2012-05-25T19:59:57


Hi,

Oops. Uploaded at the same place:
http://www.rtp-net.org/kirkwood/linux-base_2.6.32-46~bug673107_all.deb

Arnaud

Bug#596528: Debuging large transfer under usb3 device

Sarah Sharp — 2012-05-25T18:59:05

Thanks Guillaume!  No rush, I just wanted to make sure I hadn't dropped
the ball on a bug report.

Sarah Sharp

On Fri, May 25, 2012 at 12:42:31AM +0200, Guillaume Jaouen wrote:

Processed: Re: wireless brcms_c_wait_for_tx_completion warning

Debian Bug Tracking System — 2012-05-25T18:33:06

Processing commands for control< at >bugs.debian.org:

Bug #672891 [linux-2.6] brcmsmac wireless brcms_c_wait_for_tx_completion warning
Removed tag(s) pending and patch.
End of message, stopping processing here.

Please contact me if you need assistance.

Processed: Re: wireless brcms_c_wait_for_tx_completion warning

Debian Bug Tracking System — 2012-05-25T18:15:06

Processing commands for control< at >bugs.debian.org:

Bug #672891 {Done: Ben Hutchings <ben< at >decadent.org.uk>} [linux-2.6] brcmsmac wireless brcms_c_wait_for_tx_completion warning
Marked as found in versions linux-2.6/3.2.18-1; no longer marked as fixed in versions linux-2.6/3.2.18-1 and reopened.
Stopping processing here.

Please contact me if you need assistance.

Bug#672891: wireless brcms_c_wait_for_tx_completion warning

Jonathan Nieder — 2012-05-25T18:14:16

found 672891 linux-2.6/3.2.18-1
quit

Touko Korpela wrote:

[...]

Yep, doing so.  Thanks again for the quick feedback.

Bug#672891: wireless brcms_c_wait_for_tx_completion warning

Touko Korpela — 2012-05-25T18:09:14

 _wait_scan]

(last followup was sent to cloned bug by mistake)
Hard to say if it made difference, maybe made it more rare.
Logs show only a few this kind of warnings in last weeks running 3.2.1x
It always happens after many hours of uptime except 3.2.17-1 case that
happened sooner but it doesn't mean much.
That computer is always on doing some backround calculations that causes
small amount of network traffic and is sometimes used locally for browsing
and applying updates.
But should this bug be opened again?

Bug#672891: wireless brcms_c_wait_for_tx_completion warning

Jonathan Nieder — 2012-05-25T16:34:07

Hi,

Touko Korpela wrote:

[...]
[...]
 ait_scan]

This is 20 hours after boot so I'm guessing it's not easy to reproduce.
Alas.  Thanks for reporting it.

Do you think the patch added in 3.2.18 made a difference?  How often
were you getting the wait_for_tx_completion WARNING before, and are
you getting it less often now?  (I'm asking because this information
would probably be helpful to upstream in diagnosing this.)

Hope that helps,
Jonathan

Bug#673391: Revised patches for be2net

2012-05-25T16:30:17

Ben,
  I am attaching the revised patches as per your comments. I was not sure how to handle patches (4 of them) which involved changes to other drivers too. I intend to open separate bugs for each of them and send them. Hope that is ok.

I have also taken care of your comment  to not change the return value in ndo_vlan_rx_[add/kill]_vid (8e586137e6b63af1e881b328466ab5ffbe562510). The patches also contain the upstream commit id thanks to your git-format-patch-for-backport script.

Thanks,
Sarvesh