Bug#659463: Not work GPU acceleration on AMD Radeon HD6570

[Гаврилов Михаил Витальевич]

On Пн., 2012-02-13 at 00:16 -0600, Jonathan Nieder wrote:
> The Radeon firmware is only provided by AMD in binary form, without
> source code, so we cannot in good conscience include it in Debian and
> promise to support it.  We do not have the relevant information about
> how it works or ability to tweak its behavior.
> 
> However, it is useful software in practice so it is distributed on
> Debian mirrors in the non-free section of the archive.  It is also
> included in a non-official installer image:
> 
>  http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
> 
> Could you say a little more about the symptoms you experienced?  Do
> programs relying on GPU acceleration run slowly or do they crash?  If
> the latter, this is definitely a bug and would be important to fix ---
> Debian should not require external extras to be non-crashy.  If the
> former, there is likely a documentation bug in that you did not know
> why acceleration was disabled and where to look for the missing
> software that would speed things up.  If you can remember where you
> looked expecting answers, that would be very useful so we can add some
> relevant documentation for the next person.
> 
> Thanks and sorry for the trouble.
> 
> Hope that helps,
> Jonathan

Without firmware-linux-nonfree package, GPU acceleration not work, GNOME
Shell not work and dual monitor worked as single monitor. This is
unusable for me, and I am not testing other software anymore. I am very
surprised, I thinking that if I not will install "fglrx", I use open
driver "Mesa - Gallium".

Bug#632880: Not work GPU acceleration on AMD Radeon HD6570

[Jonathan Nieder]

Гаврилов Михаил Витальевич wrote:

> Thanks. Installing firmware-linux-nonfree solve this problem.

To be clear, are you talking about  or
?



--
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/20120213062207.GF3230@burratino

Bug#659463: Not work GPU acceleration on AMD Radeon HD6570

[Гаврилов Михаил Витальевич]

On Сб., 2012-02-11 at 04:43 -0600, Jonathan Nieder wrote:
> reassign 659463 src:linux-2.6 3.2.4-1
> quit
> 
> Hi Михаил,
> 
> Гаврилов Михаил Витальевич wrote:
> 
> > [5.614298] ni_cp: Failed to load firmware "radeon/TURKS_pfp.bin"
> > [5.614346] [drm:evergreen_startup] *ERROR* Failed to load firmware!
> 
> Is the firmware-linux-nonfree package installed?
> 
> Curious,
> Jonathan

Thanks. Installing firmware-linux-nonfree solve this problem.
Why firmware-linux-nonfree not included in default distribution?
If you have some reasons not include firmware-linux-nonfree in default
distribution, could you automate and simplify installing
firmware-linux-nonfree in debian installer as an essential package for
some devices?

Bug#632880: Not work GPU acceleration on AMD Radeon HD6570

[Jonathan Nieder]

Гаврилов Михаил Витальевич wrote:

> Thanks. Installing firmware-linux-nonfree solve this problem.

Thanks for checking.

> Why firmware-linux-nonfree not included in default distribution?
> If you have some reasons not include firmware-linux-nonfree in default
> distribution, could you automate and simplify installing
> firmware-linux-nonfree in debian installer as an essential package for
> some devices?

The Radeon firmware is only provided by AMD in binary form, without
source code, so we cannot in good conscience include it in Debian and
promise to support it.  We do not have the relevant information about
how it works or ability to tweak its behavior.

However, it is useful software in practice so it is distributed on
Debian mirrors in the non-free section of the archive.  It is also
included in a non-official installer image:

 http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

Could you say a little more about the symptoms you experienced?  Do
programs relying on GPU acceleration run slowly or do they crash?  If
the latter, this is definitely a bug and would be important to fix ---
Debian should not require external extras to be non-crashy.  If the
former, there is likely a documentation bug in that you did not know
why acceleration was disabled and where to look for the missing
software that would speed things up.  If you can remember where you
looked expecting answers, that would be very useful so we can add some
relevant documentation for the next person.

Thanks and sorry for the trouble.

Hope that helps,
Jonathan



--
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/20120213061622.GE3230@burratino

Bug#632880: [Fwd: Re: Not work GPU acceleration on AMD Radeon HD6570]

[Гаврилов Михаил Витальевич]

On Сб., 2012-02-11 at 04:43 -0600, Jonathan Nieder wrote:
> reassign 659463 src:linux-2.6 3.2.4-1
> quit
> 
> Hi Михаил,
> 
> Гаврилов Михаил Витальевич wrote:
> 
> > [5.614298] ni_cp: Failed to load firmware "radeon/TURKS_pfp.bin"
> > [5.614346] [drm:evergreen_startup] *ERROR* Failed to load firmware!
> 
> Is the firmware-linux-nonfree package installed?
> 
> Curious,
> Jonathan

Thanks. Installing firmware-linux-nonfree solve this problem.
Why firmware-linux-nonfree not included in default distribution?
If you have some reasons not include firmware-linux-nonfree in default
distribution, could you automate and simplify installing
firmware-linux-nonfree in debian installer as an essential package for
some devices?

Processed: Re: Suspend from X session hangs Asus laptop.

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # [1]
> forwarded 658778 https://bugzilla.kernel.org/show_bug.cgi?id=37632
Bug #658778 [src:linux-2.6] linux-image-3.2.0-1-amd64: Suspend from X session 
hangs Asus laptop.
Bug #656062 [src:linux-2.6] pm-utils: pm-suspend does not enter suspend and 
hangs system on Asus U35JC
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=37632'.
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=37632'.
> quit
Stopping processing here.

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

Bug#658778: Suspend from X session hangs Asus laptop.

[Jonathan Nieder]

# [1]
forwarded 658778 https://bugzilla.kernel.org/show_bug.cgi?id=37632
quit

Boris Barbour wrote:
> Hi Jonathan,

>> If so, could you also try unloading/loading only one of the two drivers to
>> see which one is the culprit?
>
> Removing only ehci_hcd, hibernation works perfectly. If only xhci_hcd is 
> removed, the screen is blanked but stays on. A power cycle is necessary, 
> although the computer then resumes OK.

Nicely done.  Ok.

References:

 https://bugzilla.kernel.org/show_bug.cgi?id=37632
 https://bugzilla.redhat.com/show_bug.cgi?id=697150
 http://thread.gmane.org/gmane.linux.kernel/1222803

Please add yourselves to the cc list for the upstream bug [1].  Further
work can be coordinated there.



-- 
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/20120213015907.GI2256@burratino

Processed: Re: pm-suspend does not enter suspend and hangs system on Asus U35JC

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 656062 src:linux-2.6 3.1.8-2
Bug #656062 [pm-utils] pm-utils: pm-suspend does not enter suspend and hangs 
system on Asus U35JC
Bug reassigned from package 'pm-utils' to 'src:linux-2.6'.
Bug No longer marked as found in versions pm-utils/1.4.1-8.
Bug #656062 [src:linux-2.6] pm-utils: pm-suspend does not enter suspend and 
hangs system on Asus U35JC
Bug Marked as found in versions linux-2.6/3.1.8-2.
> reassign 658778 src:linux-2.6 3.2.2-1
Bug #658778 [linux-2.6] linux-image-3.2.0-1-amd64: Suspend from X session hangs 
Asus laptop.
Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'.
Bug No longer marked as found in versions 3.2.2-1.
Bug #658778 [src:linux-2.6] linux-image-3.2.0-1-amd64: Suspend from X session 
hangs Asus laptop.
Bug Marked as found in versions linux-2.6/3.2.2-1.
> merge 656062 658778
Bug#656062: pm-utils: pm-suspend does not enter suspend and hangs system on 
Asus U35JC
Bug#658778: linux-image-3.2.0-1-amd64: Suspend from X session hangs Asus laptop.
Merged 656062 658778.

> affects 656062 + pm-utils
Bug #656062 [src:linux-2.6] pm-utils: pm-suspend does not enter suspend and 
hangs system on Asus U35JC
Bug #658778 [src:linux-2.6] linux-image-3.2.0-1-amd64: Suspend from X session 
hangs Asus laptop.
Added indication that 656062 affects pm-utils
Added indication that 658778 affects pm-utils
> quit
Stopping processing here.

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

Bug#658778: pm-suspend does not enter suspend and hangs system on Asus U35JC

[Jonathan Nieder]

reassign 656062 src:linux-2.6 3.1.8-2
reassign 658778 src:linux-2.6 3.2.2-1
merge 656062 658778
affects 656062 + pm-utils
quit

Hi,

David Banks wrote:

> On an Asus U35JC, using pm-suspend does not cause the laptop to enter a
> suspended state.  The system drops to the console with a blinking cursor, but
> that's all.  The system fans continue to spin, as if CPU activity were high, 
> and
> all relevant LEDs remain as before.  Attempting to resume does nothing, and 
> the
> system is totally hung.
>
> In order to get suspend to work I had to use the following script in
> /etc/pm/sleep.d, found at at :
>
>   #!/bin/sh
>
>   BUSES=":00:1a.0 :00:1d.0"
>
>   case "${1}" in
>   hibernate|suspend)
>   # Switch USB buses off
>   for bus in $BUSES; do
>   echo -n $bus | tee /sys/bus/pci/drivers/ehci_hcd/unbind
[...]
> The hardcoded $BUSES worked for my hardware.  I don't know if this is really a
> bug, or if it should be reported against this package or the kernel package, 
> but
> maybe this information will help someone.  For the record, pm-hibernate had 
> the
> same issue that it would not shut down the system, but when booting up again
> after hard poweroff it would resume from hibernation without any problem.

Thanks.  Let's call it a kernel bug, even though it's more likely a BIOS
bug.

What kernel, BIOS version, etc do you use?  Please attach output from
"reportbug --template linux-image-$(uname -r)".

Thanks,
Jonathan



-- 
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/20120213014344.GA3655@burratino

Bug#659521: [3.1.8 -> 3.2.4 regression] ATH9K driver will not connect to my adhoc network

[Jonathan Nieder]

Jonathan Nieder wrote:

> Oh, dear.  Now I've reread your message.  Sorry for publishing your
> email address (in message ID <20120213000954.GB2256@burratino>, sent
> to bug 659521).  Don, I assume it is too late to remove that message
> from the archive? :/

Same question for listmaster (for http://lists.debian.org/debian-kernel).
I realize the mistake cannot be taken back and the message is already
public, but maybe it is possible to mitigate the damage by removing the
message from public archives.

I've contacted Lars from gmane separately.  mail-archive.com already
munges email addresses.  I'm not aware of any other public archives
of debian-kernel@ and debian-bugs-dist@, though that doesn't mean
they don't exist.  I've read

 http://www.debian.org/MailingLists/disclaimer

which makes it clear I cannot *demand* that you remove my message, but
maybe I am lucky and politely asking it can work so another does not
suffer for my mistake.  (Information on that page either way about
whether old messages can be removed and under what circumstances would
be welcome, by the way.)

Thanks and sorry,
Jonathan



-- 
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/20120213003600.GE2256@burratino

Bug#659521: [3.1.8 -> 3.2.4 regression] ATH9K driver will not connect to my adhoc network

[Jonathan Nieder]

Jonathan Nieder wrote:

> Forwarding to the bug log.

Oh, dear.  Now I've reread your message.  Sorry for publishing your
email address (in message ID <20120213000954.GB2256@burratino>, sent
to bug 659521).  Don, I assume it is too late to remove that message
from the archive? :/

Unhappily,
Jonathan



-- 
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/20120213001419.GC2256@burratino

Bug#659521: [ank...@gmail.com: Re: [3.1.8 -> 3.2.4 regression] ATH9K driver will not connect to my adhoc network]

[Jonathan Nieder]

Forwarding to the bug log.  Please use your mailer's reply-to-all
feature in the future so others can pick up the thread if I end up too
busy or miss important details.
--- Begin Message ---
Hello again,

patching failed, may be I am just overwhelmed by this all and
installed the wrong things. :-(

Got for example "tree in not stable" or similar when trying to do what
the "patch page" says. Also there is mentioned in a file the source is
for "Debian unstable" which I installed from the package manager,
while I'm sure I have "Debian testing". I also forgot to actually
unpack the tar ball. Doing it now but no time now to deal with it. May
be one of the next days, but no promise here. I really don't have the
time to elaborate what to do now.

I also did not send something to the maintainers as I still don't know
what exactly. I feel like an idiot now, sorry. Can't you just forward
them what they need?

Little update: I booted the new kernel, still no luck with adhoc. But
used the wicd this time. Unless I gave 5 times the wrong WEP key to
access the other adhoc computer it was rejected every time with "bad
passphrase".

But I was able to connect to a different WEP secured managed source.
So it seems to NOT be a problem with the authentication. Unfortunately
I have no physical access to the other adhoc computer I use to connect
to to have internet. So I cannot try an unencrypted connection.

I also tried to add you to my Gmail chat (ank...@gmail.com; this email
address shall not be published in public, while I use a different one
here) but you might not have chat or the time. We could have tried a
chat instead of emailing.

Sorry for all of that, my head is spinning.

With kind regards, Ankman

On Sun, Feb 12, 2012 at 13:52, Jonathan Nieder  wrote:
> (Resending to the correct bug.  Sorry for the duplicate messages, Ankman
> and David.)
> Hi,
>
> Ankman wrote:
>
>> Am I supposed to send all I sent to you previously to the addresses
>> given in this mail? So the dmesg log and my setup? Can't you do it
>> instead? I don't want to make a mistake.
>
> More important than the logs (which they can get e.g. through a link to
> ) is a succinct summary of the problem.
>
> I usually ask bug reporters to make the first contact with upstream
> so they can add additional information if appropriate and choose an
> appropriate time to be able to reply to followups if busy.
>
>> I also might later (cannot guarantee though) be able to apply the
>> patch you provided. But I didn't apply pages since quite some time and
>> have not much time. If you are interested that I try this can you
>> please provide me with all console commands how I do this?
>
> Thanks!  Here's a summary of the page[1] I mentioned before:
>
>        # as root:
>        apt-get source linux-2.6
>        apt-get install build-essential fakeroot devscripts
>        apt-get build-dep linux-2.6
>
>        # as a normal user:
>        cd linux-2.6-
>
>        bash debian/bin/test-patches 
>        # or, for parallel build:
>        bash debian/bin/test-patches -j  
>
>        # as root:
>        dpkg -i ../
>        reboot
>
> [...]
 ifconfig wlan0 down
 iwconfig wlan0 mode ad-hoc
 iwconfig wlan0 my-essid
 iwconfig wlan0 key 12345
 ifconfig wlan0 192.168.198.251
 route add default gw 192.168.198.78
>
> As David Goodenough hinted, upstream might be more comfortable working
> with the "ip" and "iw" tools from the iproute and iw packages.  Something
> like this:
>
>        ip link set wlan0 down
>        ip link set wlan0 up
>        iw dev wlan0 interface add ah0 type ibss
>        ip link set ah0 up
>        iw dev ah0 ibss join my-essid 2412
>        ip address add 192.168.198.251 dev wlan0
>        ip route add default via 192.168.198.78 dev wlan0
>
>        ...
>        iw dev ah0 ibss leave
>        ip link set ah0 down
>        ip link set wlan0 down
>
> Running "iw event -t" in another terminal while doing this can give
> interesting progress information.  And "dmesg" tends to report errors,
> as usual.
>
> Hope that helps,
> Jonathan
>
> [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2
--- End Message ---

Processed: Re: [regression 2.6.39 -> 3.0] RV710: no sound through hdmi, timing broken unless sound disabled

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # regression
> severity 659673 important
Bug #659673 [linux-2.6] linux-image-3.2.0-1-686-pae: Sound on ATI hdmi devices 
broken
Severity set to 'important' from 'normal'

> # [1]
> forwarded 659673 https://bugzilla.kernel.org/show_bug.cgi?id=39832
Bug #659673 [linux-2.6] linux-image-3.2.0-1-686-pae: Sound on ATI hdmi devices 
broken
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=39832'.
> quit
Stopping processing here.

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

Bug#659673: [regression 2.6.39 -> 3.0] RV710: no sound through hdmi, timing broken unless sound disabled

[Jonathan Nieder]

# regression
severity 659673 important
# [1]
forwarded 659673 https://bugzilla.kernel.org/show_bug.cgi?id=39832
quit

Hi Santiago,

Santiago Garcia Mantinan wrote:

> I've found that internal sound has stopped working on some, if not all, ATI
> cards with HDMI output. This was working on 2.6.39 without any problem at
> all, however when we changed to 3.0.0 it broke down and now in 3.2.4 it is
> still broken.
[... nice explanation snipped ...]
> I'm
> testing this on a ATI Technologies Inc RV710 [Radeon HD 4350] and the audio
> device identifies itself as ATI Technologies Inc RV710/730 (ATI R6xx HDMI).

Thanks.  Please follow up at [1] with information about the kernel
versions you've tested and attach output from the alsa-info.sh
script[2] with a working and a non-working kernel.  You can get
previous versions of the kernel at .

Hope that helps,
Jonathan

[2] from here: http://alsa-project.org/main/index.php/Help_To_Debug



-- 
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/20120213000544.GA2256@burratino

Bug#656331: RTL8168b/8111b with ASUS M2A-VM (SB600): Network device stays down after resume

[Paul Menzel]

Am Mittwoch, den 08.02.2012, 23:16 +0100 schrieb Francois Romieu:
> Paul Menzel  :

[…]

> > [18764.958557] r8169 :02:00.0: PME# disabled
> > [18781.998004] r8169 :02:00.0: eth0: link down
>  ^^
> > [18781.998024] r8169 :02:00.0: eth0: link down
>  ^^
> Two link events within 20 us. /me wonders...

[20195.408746] r8169 :02:00.0: PME# enabled
[20195.466159] r8169 :02:00.0: restoring config space at offset 0xf 
(was 0x100, writing 0x10a)
[20195.466175] r8169 :02:00.0: restoring config space at offset 0x6 
(was 0x4, writing 0xfdaff004)
[20195.466182] r8169 :02:00.0: restoring config space at offset 0x4 
(was 0x1, writing 0xdc01)
[20195.466187] r8169 :02:00.0: restoring config space at offset 0x3 
(was 0x0, writing 0x8)
[20195.466194] r8169 :02:00.0: restoring config space at offset 0x1 
(was 0x10, writing 0x100407)
[20195.466826] r8169 :02:00.0: PME# disabled
[20211.376483] r8169 :02:00.0: eth0: link down
[20211.376507] r8169 :02:00.0: eth0: link down

Only ten 24 us difference. But during this resume process the network
came back up fine. Also in my prior pasted output this is also shown at
the beginning but the network worked fine.

[20213.000840] r8169 :02:00.0: eth0: link up
[32598.618289] r8169 :02:00.0: eth0: link down

This event during resume sometimes shows up and sometimes it does not. I
could not find a correlation between successful and failed resumes.

[32599.249802] r8169 :02:00.0: PME# enabled
[32599.397941] r8169 :02:00.0: restoring config space at offset 0xf 
(was 0x100, writing 0x10a)
[32599.397956] r8169 :02:00.0: restoring config space at offset 0x6 
(was 0x4, writing 0xfdaff004)
[32599.397963] r8169 :02:00.0: restoring config space at offset 0x4 
(was 0x1, writing 0xdc01)
[32599.397968] r8169 :02:00.0: restoring config space at offset 0x3 
(was 0x0, writing 0x8)
[32599.397975] r8169 :02:00.0: restoring config space at offset 0x1 
(was 0x10, writing 0x100407)
[32599.398766] r8169 :02:00.0: PME# disabled
[32599.416148] r8169 :02:00.0: eth0: link down

Here it did not work and the link did not come back up. There is over half a 
second time bet

[32673.504101] r8169 :02:00.0: PCI INT A disabled

The module is removed and loaded below.

[32676.218019] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[32676.218078] r8169 :02:00.0: PCI INT A -> GSI 19 (level, low) -> 
IRQ 19
[32676.218152] r8169 :02:00.0: setting latency timer to 64
[32676.218246] r8169 :02:00.0: irq 41 for MSI/MSI-X
[32676.219792] r8169 :02:00.0: eth0: RTL8168b/8111b at 
0xc9368000, 00:1e:8c:aa:1d:b5, XID 1800 IRQ 41
[32676.219803] r8169 :02:00.0: eth0: jumbo features [frames: 4080 
bytes, tx checksumming: ko]
[32676.563203] r8169 :02:00.0: eth0: link down
[32678.356237] r8169 :02:00.0: eth0: link up

> The datasheet states "[the PHYStatus] register is updated continuously at
> maximum periods of 300us." but it is far from clear that the coherency
> with the interrupt status register can be taken for granted. Hayes ?
> 
> Paul, can you try the hack below ?
> 
> diff --git a/drivers/net/ethernet/realtek/r8169.c 
> b/drivers/net/ethernet/realtek/r8169.c
> index 7a0c800..6daca05 100644
> --- a/drivers/net/ethernet/realtek/r8169.c
> +++ b/drivers/net/ethernet/realtek/r8169.c
> @@ -1278,6 +1278,7 @@ static void __rtl8169_check_link_status(struct 
> net_device *dev,
>  {
>   unsigned long flags;
>  
> + udelay(500);
>   spin_lock_irqsave(&tp->lock, flags);
>   if (tp->link_ok(ioaddr)) {
>   rtl_link_chg_patch(tp);

I will try this hack next week. Thank you!

Could it be that there is something wrong with the locking though or
parallel execution? Sometimes

[32598.618289] r8169 :02:00.0: eth0: link down

is shown before 

[32599.249802] r8169 :02:00.0: PME# enabled

and sometimes it is not or only afterward.


Thanks,

Paul


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

Processed: tagging 659562

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 659562 + pending
Bug #659562 [src:linux-2.6] Changes from longterm 2.6.32.56
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 658164

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 658164 + pending
Bug #658164 {Done: Bastian Blank } [linux-2.6] 
linux-image-3.1.0-1-amd64: Baud rate of FTDI USB-to-serial converter not 
initialized
Ignoring request to alter tags of bug #658164 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 659647

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 659647 + moreinfo
Bug #659647 [initramfs-tools] initramfs-tools/hooks/cryptroot get_lvm_deps 
can't cope with vg name containing -
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#659647: initramfs-tools/hooks/cryptroot get_lvm_deps can't cope with vg name containing -

[Ben Hutchings]

On Sun, 2012-02-12 at 20:57 +0100, John Hughes wrote:
> Package: initramfs-tools
> Version: 0.99
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> I made a volume group called "coal-vg" holding a root volume called root.
> 
> (i.e. /dev/mapper/root--vg-root)
> 
>* What was the outcome of this action?
> 
> update-initramfs gave the error:
> 
> cryptsetup: WARNING: failed to find deps for /dev/mapper/root--vg-root
[...]

Surely this should be coal--vg-root?

Anyway, if the cryptsetup hook is broken then that's a bug in, er,
cryptsetup.

Ben.

-- 
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.


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

Bug#659519: [3.1 -> 3.2.4 regression] Sound problems

[David Baron]

On Sunday 12 February 2012 21:17:24 Jonathan Nieder wrote:
> reassign 659519 src:linux-2.6 3.2.4-1
> quit
> 
> Hi,
> 
> David Baron wrote:
> > reportbug-output
> > alsa-info.txt.UL...
> > alsa-info.txt.DZ...
> 
> Good.
> 
> It looks like you have two sound cards: one internal, one connected
> by USB.  I assume you are using the internal one.

Yes, the internal one is used for listening generally. The USB one is to be 
used with jack but that is not working either right now.

> 
> [...]
> 
> > Manufacturer:
Lexicon
> > Product Name:
> 
> > Product Version:
Lambda

> Can you say a little about this machine and its motherboard?  Is this
> an off-the-shelf machine, or something custom?
> 
This is a rather unique motherboard in that it has two ISA slots (something 
hard to come by these days). Intel chipset, only one IDE pair, full complement 
of SATA. 64 bit processor, running 32 bit now but will switch over once qt4 
and kde are consistent on Sid and all those held packages are resolved.

One ISA is used for another sound card which the system knows nothing about, 
an old Yamaha sw60xg sound generator. Using Yamaha's advice for Windows 2000 
before they made a driver, set the switches to a port and use mpu401 on the 
port number. No DMA, No IRQ, nothing.

I had an older speakerphone modem on the other ISA but that ceased to work. 
PCI modems that work with Linux are hard to come by since most use Windows 
software rather than their own hardware. I am using an 'antique" external 
modem until I find something else.

Another 4-in/4-out dman2044 PCI sound card I had on Windows 98 has no support 
beyond that, which is a pity, good card, breakout box, etc.

> 
> > +  Control: name="Headphone Playback Switch", index=0, device=0
> > +ControlAmp: chs=3, dir=Out, idx=0, ofs=0
> 
> Do different outputs behave differently (e.g., can you hear anything
> if you plug in headphones)?

> Does fiddling with controls in
> "alsamixer" (press F6 first to make sure you are setting ALSA
> controls, not pulseaudio ones; the keybinding for "toggle control" is
> "M") change anything?
> 
The master controls all.
I have front going to the speakers
I have center going to subwoofer (since its feed-through is problematic).
The checkboxes on alsamixer or qasmixer will switch these outputs.
Headphones do not work--programs have no toggle for it.

Things are going throught the hw0,0 "analog"
The hw0,1 "digitial" does not play, there is no spdif connected on this board.
There are six jacks on the back, not 8.


> [...]
> 
> > +[10462.836042] hda-intel: IRQ timing workaround is activated for card
> > #0. Suggest a bigger bdl_pos_adj.

I know nothing about his (be recall have seen something about it).

The other problem is that the line input seems dead which renders the card 
useless for any wired connectivity. Could be a real hardware problem but how 
often does that happen.

Worse comes to worse, I have an old ens1371 laying around which I could use, 
hard-connecting the speaker line and the woofer-line.
> 
> Weird.
> 
> Thanks much.  Hopefully we are closing in.
Good. This is apparently not the only system with problems with 3.2.4

Bug#574433: marked as done (linux-image-2.6.32-3-amd64: unable to handle kernel NULL pointer dereference at (null))

[Debian Bug Tracking System]

Your message dated Sun, 12 Feb 2012 13:56:22 -0600
with message-id <20120212195622.GA8626@burratino>
and subject line Re: linux-image-2.6.32-3-amd64: unable to handle kernel NULL 
pointer dereference at (null)
has caused the Debian Bug report #574433,
regarding linux-image-2.6.32-3-amd64: unable to handle kernel NULL pointer 
dereference at (null)
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.)


-- 
574433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-9
Severity: important


Shortly after coming out of hibernate I plugged in a USB mouse. When the mouse
didn't work I found the following in dmesg. Then, when I was trying to sumbit
a bug report, X hung. I had to ssh in and run "sudo init 0" to get the machine
back to a working state.

[23415.104319] usb 6-1: new low speed USB device using uhci_hcd and address 2
[23415.258904] usb 6-1: New USB device found, idVendor=062a, idProduct=
[23415.258913] usb 6-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[23415.259062] BUG: unable to handle kernel NULL pointer dereference at (null)
[23415.259072] IP: [] strcmp+0x5/0x1a
[23415.259088] PGD 139932067 PUD 1392cb067 PMD 0 
[23415.259098] Oops:  [#1] SMP 
[23415.259104] last sysfs file: 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
[23415.259111] CPU 0 
[23415.259116] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs vfat msdos 
fat jfs xfs exportfs reiserfs ext3 jbd ext2 ppdev lp sco bridge stp bnep rfcomm 
l2cap acpi_cpufreq cpufreq_powersave cpufreq_stats cpufreq_userspace 
cpufreq_conservative binfmt_misc uinput fuse loop firewire_sbp2 
snd_hda_codec_analog snd_hda_intel ide_cs snd_hda_codec snd_hwdep snd_pcm_oss 
snd_mixer_oss snd_pcm snd_seq_midi uvcvideo snd_rawmidi videodev 
snd_seq_midi_event arc4 snd_seq v4l1_compat btusb bluetooth v4l2_compat_ioctl32 
ecb pcmcia snd_timer parport_pc iwlagn parport iwlcore snd_seq_device joydev 
hp_accel mac80211 lis3lv02d yenta_socket rsrc_nonstatic cfg80211 rfkill evdev 
pcmcia_core snd soundcore snd_page_alloc psmouse pcspkr input_polldev container 
battery ac serio_raw wmi tpm_infineon tpm tpm_bios processor ext4 mbcache jbd2 
crc16 sg sr_mod cdrom sd_mod crc_t10dif ide_pci_generic ide_core i915 
drm_kms_helper drm ata_generic sdhci_pci uhci_hcd sdhci mmc_core led_class 
firewire_ohci rico
 h_mmc ahci firewire_core crc_itu_t libata ehci_hcd i2c_algo_bit i2c_core video 
output usbcore nls_base scsi_mod button e1000e intel_agp thermal fan 
thermal_sys [last unloaded: scsi_wait_scan]
[23415.259336] Pid: 362, comm: khubd Not tainted 2.6.32-3-amd64 #1 HP EliteBook 
6930p
[23415.259342] RIP: 0010:[]  [] 
strcmp+0x5/0x1a
[23415.259353] RSP: 0018:880138ec1b48  EFLAGS: 00010246
[23415.259359] RAX:  RBX: 880137d60640 RCX: 880137d607d0
[23415.259366] RDX: 8113dc75 RSI:  RDI: 813cf798
[23415.259372] RBP:  R08: 0001 R09: 880138ec1ab0
[23415.259378] R10: 80d0 R11: 880137d607d0 R12: fff4
[23415.259385] R13: 880137d60f00 R14: 880138ec1bd0 R15: a0096570
[23415.259393] FS:  () GS:88000520() 
knlGS:
[23415.259400] CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
[23415.259405] CR2:  CR3: 00013a4ef000 CR4: 000406f0
[23415.259412] DR0:  DR1:  DR2: 
[23415.259418] DR3:  DR6: 0ff0 DR7: 0400
[23415.259426] Process khubd (pid: 362, threadinfo 880138ec, task 
8801376bb170)
[23415.259430] Stack:
[23415.259434]  8113debc 0001 880137d60f00 
880138ec1bd0
[23415.259444] <0> 8113dfca a0096570 a0096800 
880137d60f00
[23415.259454] <0> 8113e08c fff4 a0096800 
880137d60f00
[23415.259466] Call Trace:
[23415.259479]  [] ? sysfs_find_dirent+0x1b/0x2f
[23415.259487]  [] ? __sysfs_add_one+0x18/0x84
[23415.259504]  [] ? sysfs_add_one+0x19/0xe4
[23415.259520]  [] ? sysfs_add_file_mode+0x4e/0x7f
[23415.259534]  [] ? internal_create_group+0xdc/0x15a
[23415.259551]  [] ? device_add_groups+0x22/0x5d
[23415.259560]  [] ? device_add+0x2d2/0x537
[23415.259584]  [] ? usb_new_device+0x125/0x186 [usbcore]
[23415.259609]  [] ? hub_thread+0xc23/0x117d [usbcore]
[23415.259621]  [] ? autoremove_wake_function+0x0/0x2e
[23415.259644]  [] ? hub_thread+0x0/0x117d [usbcore]
[23415.259653]  [] ? kthread

Bug#659647: initramfs-tools/hooks/cryptroot get_lvm_deps can't cope with vg name containing -

[John Hughes]

Package: initramfs-tools
Version: 0.99
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I made a volume group called "coal-vg" holding a root volume called root.

(i.e. /dev/mapper/root--vg-root)

   * What was the outcome of this action?

update-initramfs gave the error:

cryptsetup: WARNING: failed to find deps for /dev/mapper/root--vg-root

and made a bad initrd

   * What outcome did you expect instead?

a good initrd.


-- Package-specific info:
-- initramfs sizes
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-1-amd64 root=/dev/mapper/coal-root ro quiet

-- resume
RESUME=/dev/mapper/coal-swap
-- /proc/filesystems
ext3
fuseblk

-- lsmod
Module  Size  Used by
acpi_cpufreq   12935  1 
mperf  12453  1 acpi_cpufreq
cpufreq_stats  12866  0 
cpufreq_powersave  12454  0 
cpufreq_userspace  12576  0 
cpufreq_conservative13147  0 
parport_pc 22364  0 
ppdev  12763  0 
lp 17149  0 
parport31858  3 parport_pc,ppdev,lp
bnep   17567  2 
rfcomm 33656  10 
binfmt_misc12957  1 
uinput 17440  1 
fuse   61981  1 
loop   22641  0 
snd_hda_codec_hdmi 30783  2 
snd_hda_codec_realtek   188599  1 
joydev 17266  0 
tpm_infineon   12985  0 
arc4   12458  2 
snd_hda_intel  26345  2 
uvcvideo   57744  0 
snd_hda_codec  77994  3 
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
videodev   70889  1 uvcvideo
media  18148  2 uvcvideo,videodev
snd_hwdep  13186  1 snd_hda_codec
v4l2_compat_ioctl3216655  1 videodev
iwlwifi   166703  0 
snd_pcm63900  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
btusb  17502  2 
snd_seq45093  0 
radeon643235  0 
bluetooth 119406  23 bnep,rfcomm,btusb
psmouse64455  0 
snd_timer  22917  2 snd_pcm,snd_seq
snd_seq_device 13176  1 snd_seq
tpm_tis17454  0 
evdev  17562  14 
pcspkr 12579  0 
tpm17862  2 tpm_infineon,tpm_tis
iTCO_wdt   17081  0 
serio_raw  12931  0 
ttm48725  1 radeon
sony_laptop36225  0 
i2c_i801   16870  0 
crc16  12343  1 bluetooth
mac80211  192768  1 iwlwifi
rts_pstor 261770  0 
iTCO_vendor_support12704  1 iTCO_wdt
snd52850  13 
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_seq,snd_timer,snd_seq_device
tpm_bios   12948  1 tpm
battery13109  0 
cfg80211  137140  2 iwlwifi,mac80211
i915  351781  3 
rfkill 19012  5 bluetooth,sony_laptop,cfg80211
drm_kms_helper 27227  2 radeon,i915
drm   167670  6 radeon,ttm,i915,drm_kms_helper
ac 12624  0 
soundcore  13065  1 snd
power_supply   13475  3 radeon,battery,ac
snd_page_alloc 13003  2 snd_hda_intel,snd_pcm
i2c_algo_bit   12841  2 radeon,i915
i2c_core   23876  7 
videodev,radeon,i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
button 12937  1 i915
video  17628  1 i915
processor  28059  1 acpi_cpufreq
ext3  161867  3 
jbd56902  1 ext3
mbcache13065  1 ext3
sha256_generic 16797  2 
aesni_intel50643  24 
cryptd 14517  9 aesni_intel
aes_x86_64 16796  1 aesni_intel
aes_generic33026  2 aesni_intel,aes_x86_64
cbc12754  0 
dm_crypt   22586  1 
dm_mod 63545  12 dm_crypt
raid0  12904  1 
md_mod 87742  4 raid0
sr_mod 21899  0 
cdrom  35401  1 sr_mod
sd_mod 36136  2 
crc_t10dif 12348  1 sd_mod
ata_generic12479  0 
pata_marvell   12568  0 
xhci_hcd   73208  0 
ahci   24997  4 
libahci22860  1 ahci
ehci_hcd   40215  0 
r8169  46980  0 
libata140589  4 ata_generic,pata_marvell,ahci,libahci
mii12675  1 r8169
scsi_mod  162417  4 rts_pstor,sr_mod,sd_mod,libata
usbcore   128498  5 uvcvideo,btusb,xhci_hcd,ehci_hcd
usb_common 12354  1 usbcore
thermal17383  0 
thermal_sys18040  3 video,processor,thermal

-- /etc/initramfs-tools/modules

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /e

Bug#618744: nfsd gets stuck in D state

[Anton Ivanov]

On 10/02/12 01:38, Jonathan Nieder wrote:

Hi,

Anton Ivanov wrote:

   

nfsd gets stuck in D state. Initially some machines, later all which read off
the nfs server fail to read. Messages like:

Mar 17 22:03:34 localhost kernel: [1899559.532028] statd: server rpc.statd not 
responding, timed out
Mar 17 22:03:34 localhost kernel: [1899559.532055] lockd: cannot monitor greebo
 

Mph, that's no good.

What kernel do you use now?  Any changes?  Can you use "alt+sysrq; w"
while in that state to get backtraces for blocked tasks, in case it
helps find a deadlock?  (You may need to use "echo 1>/proc/sys/kernel/sysrq"
before that will work; see Documentation/sysrq.txt for details.)
   


I have upgraded most machines to current stable and I have stopped 
seeing thi.



Hope that helps,
Jonathan

   





--
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/4f380add.3090...@kot-begemot.co.uk

Processed: Re: [3.1 -> 3.2.4 regression] Sound problems

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 659519 src:linux-2.6 3.2.4-1
Bug #659519 [linux-2.6] [linux-2.6] Sound problems after update to this kernel
Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'.
Bug No longer marked as found in versions Linux-image-3.2.0-i686-pae.
Bug #659519 [src:linux-2.6] [linux-2.6] Sound problems after update to this 
kernel
Bug Marked as found in versions linux-2.6/3.2.4-1.
> quit
Stopping processing here.

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

Bug#659519: [3.1 -> 3.2.4 regression] Sound problems

[Jonathan Nieder]

reassign 659519 src:linux-2.6 3.2.4-1
quit

Hi,

David Baron wrote:

> reportbug-output
> alsa-info.txt.UL...
> alsa-info.txt.DZ...

Good.

It looks like you have two sound cards: one internal, one connected
by USB.  I assume you are using the internal one.

[...]
> Manufacturer:
> Product Name:
> Product Version:

Can you say a little about this machine and its motherboard?  Is this
an off-the-shelf machine, or something custom?

[...]
> +  Control: name="Headphone Playback Switch", index=0, device=0
> +ControlAmp: chs=3, dir=Out, idx=0, ofs=0

Do different outputs behave differently (e.g., can you hear anything
if you plug in headphones)?  Does fiddling with controls in
"alsamixer" (press F6 first to make sure you are setting ALSA
controls, not pulseaudio ones; the keybinding for "toggle control" is
"M") change anything?

[...]
> +[10462.836042] hda-intel: IRQ timing workaround is activated for card #0. 
> Suggest a bigger bdl_pos_adj.

Weird.

Thanks much.  Hopefully we are closing in.
Jonathan



-- 
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/20120212191724.GA8462@burratino

Bug#618744: marked as done (linux-image-2.6.32-5-amd64: nfsd gets stuck in D state)

[Debian Bug Tracking System]

Your message dated Sun, 12 Feb 2012 13:08:43 -0600
with message-id <20120212190843.GA8412@burratino>
and subject line Re: nfsd gets stuck in D state
has caused the Debian Bug report #618744,
regarding linux-image-2.6.32-5-amd64: nfsd gets stuck in D state
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.)


-- 
618744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-30
Severity: important


nfsd gets stuck in D state. Initially some machines, later all which read off
the nfs server fail to read. Messages like:

Mar 17 22:03:34 localhost kernel: [1899559.532028] statd: server rpc.statd not 
responding, timed out
Mar 17 22:03:34 localhost kernel: [1899559.532055] lockd: cannot monitor greebo

appear in the kernel.

I tried to restart nfs-kernel-daemon and got:

Mar 17 22:26:14 localhost kernel: [1900919.668030] rpcbind: server localhost 
not responding, timed out
Mar 17 22:26:15 localhost kernel: [1900920.452074] INFO: task rpc.nfsd:12072 
blocked for more than 120 seconds.
Mar 17 22:26:15 localhost kernel: [1900920.452150] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 17 22:26:15 localhost kernel: [1900920.452226] rpc.nfsd  D 
 0 12072  12061 0x0004
Mar 17 22:26:15 localhost kernel: [1900920.452238]  814611f0 
0082 880146d0 88007f803110
Mar 17 22:26:15 localhost kernel: [1900920.452249]  03961016 
0001 f9e0 880035d3bfd8
Mar 17 22:26:15 localhost kernel: [1900920.452258]  00015780 
00015780 880003863880 880003863b78
Mar 17 22:26:15 localhost kernel: [1900920.452267] Call Trace:
Mar 17 22:26:15 localhost kernel: [1900920.452284]  [] ? 
__alloc_pages_nodemask+0x11c/0x5f4
Mar 17 22:26:15 localhost kernel: [1900920.452303]  [] ? 
__mutex_lock_common+0x122/0x192
Mar 17 22:26:15 localhost kernel: [1900920.452315]  [] ? 
mutex_lock+0x1a/0x31
Mar 17 22:26:15 localhost kernel: [1900920.452339]  [] ? 
write_ports+0x2a/0x28a [nfsd]
Mar 17 22:26:15 localhost kernel: [1900920.452348]  [] ? 
__get_free_pages+0x9/0x46
Mar 17 22:26:15 localhost kernel: [1900920.452358]  [] ? 
simple_transaction_get+0x8c/0xa6
Mar 17 22:26:15 localhost kernel: [1900920.452375]  [] ? 
write_ports+0x0/0x28a [nfsd]
Mar 17 22:26:15 localhost kernel: [1900920.452392]  [] ? 
nfsctl_transaction_write+0x43/0x64 [nfsd]
Mar 17 22:26:15 localhost kernel: [1900920.452409]  [] ? 
nfsctl_transaction_read+0x27/0x4d [nfsd]
Mar 17 22:26:15 localhost kernel: [1900920.452420]  [] ? 
vfs_read+0xa6/0xff
Mar 17 22:26:15 localhost kernel: [1900920.452428]  [] ? 
sys_read+0x45/0x6e
Mar 17 22:26:15 localhost kernel: [1900920.452437]  [] ? 
system_call_fastpath+0x16/0x1b
Mar 17 22:26:44 localhost kernel: [1900949.668032] rpcbind: server localhost 
not responding, timed out


The machine is stable, has been used for around a year in the current hardware 
config with 2.6.26 and 2.6.32.bpo

My suspicion is offload in e1000. Something similar to this one:

http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg02489.html

I have turned off all offload except checksumming for the time being.

-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 03:40:32 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 
root=UUID=49a2baa4-c4fb-4b25-a847-da38aabf6eb4 ro quiet

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

** Kernel log:
[4.200149] raid0:   ==> UNIQUE
[4.200150] raid0: 1 zones
[4.200151] raid0: looking at sdb3
[4.200153] raid0:   comparing sdb3(1297270784)
[4.200155]  with sda3(1297270784)
[4.200156] raid0:   EQUAL
[4.200158] raid0: FINAL 1 zones
[4.200162] raid0: done.
[4.200164] raid0 : md_size is 2594541568 sectors.
[4.200167] *** md2 configuration *
[4.200168] zone0=[sda3/sdb3/]
[4.200172] zone offset=0kb device offset=0kb size=1297270784kb
[4.200173] **
[4.200174] 
[4.200225] md2: detected capacity change from 0 to 1328405282816
[4.202838]  md2: unknown partition table
[4.461090] kjournald starting.  Commit interval 5 seconds
[4.461102] EXT3-fs: mounted filesystem with ordered data mode.
[5.654925] udev[404]: starting version 164
[6.032719] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
[6.032728] ACPI:

Bug#659521: [3.1.8 -> 3.2.4 regression] ATH9K driver will not connect to my adhoc network

[Jonathan Nieder]

(Resending to the correct bug.  Sorry for the duplicate messages, Ankman
and David.)
Hi,

Ankman wrote:

> Am I supposed to send all I sent to you previously to the addresses
> given in this mail? So the dmesg log and my setup? Can't you do it
> instead? I don't want to make a mistake.

More important than the logs (which they can get e.g. through a link to
) is a succinct summary of the problem.

I usually ask bug reporters to make the first contact with upstream
so they can add additional information if appropriate and choose an
appropriate time to be able to reply to followups if busy.

> I also might later (cannot guarantee though) be able to apply the
> patch you provided. But I didn't apply pages since quite some time and
> have not much time. If you are interested that I try this can you
> please provide me with all console commands how I do this?

Thanks!  Here's a summary of the page[1] I mentioned before:

# as root:
apt-get source linux-2.6
apt-get install build-essential fakeroot devscripts
apt-get build-dep linux-2.6

# as a normal user:
cd linux-2.6-

bash debian/bin/test-patches 
# or, for parallel build:
bash debian/bin/test-patches -j  

# as root:
dpkg -i ../
reboot

[...]
>>> ifconfig wlan0 down
>>> iwconfig wlan0 mode ad-hoc
>>> iwconfig wlan0 my-essid
>>> iwconfig wlan0 key 12345
>>> ifconfig wlan0 192.168.198.251
>>> route add default gw 192.168.198.78

As David Goodenough hinted, upstream might be more comfortable working
with the "ip" and "iw" tools from the iproute and iw packages.  Something
like this:

ip link set wlan0 down
ip link set wlan0 up
iw dev wlan0 interface add ah0 type ibss
ip link set ah0 up
iw dev ah0 ibss join my-essid 2412
ip address add 192.168.198.251 dev wlan0
ip route add default via 192.168.198.78 dev wlan0

...
iw dev ah0 ibss leave
ip link set ah0 down
ip link set wlan0 down

Running "iw event -t" in another terminal while doing this can give
interesting progress information.  And "dmesg" tends to report errors,
as usual.

Hope that helps,
Jonathan

[1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2



-- 
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/20120212185222.GD7917@burratino

Bug#659521: [3.1.8 -> 3.2.4 regression] ATH9K driver will not connect to my adhoc network

[Ankman]

Hello,

as this is my first bug report ever I'm not sure if I understand.

Am I supposed to send all I sent to you previously to the addresses
given in this mail? So the dmesg log and my setup? Can't you do it
instead? I don't want to make a mistake.

I also might later (cannot guarantee though) be able to apply the
patch you provided. But I didn't apply pages since quite some time and
have not much time. If you are interested that I try this can you
please provide me with all console commands how I do this?

With kind regards, Ankman

On Sat, Feb 11, 2012 at 19:27, Jonathan Nieder  wrote:
> Ankman wrote:
>
>> This (attachment "report.txt") will be from my currently booted kernel
>> (3.1.0-1-686-pae)
>
> Thanks!  That's fine.  Forwarded to the bug log.
>
> [...]
>> I solely rely on a script I wrote (key and essid were replaced by me),
>> no network manager involved:
>>
>> ifconfig wlan0 down
>> iwconfig wlan0 mode ad-hoc
>> iwconfig wlan0 my-essid
>> iwconfig wlan0 key 12345
>> ifconfig wlan0 192.168.198.251
>> route add default gw 192.168.198.78
>>
>> Above works reliable for me since months. Until yesterday when the
>> kernel-update was installed
>
> Ok, please send a summary of this problem upstream (that's
> ath9k-de...@lists.ath9k.org, cc-ing linux-wirel...@vger.kernel.org,
> linux-ker...@vger.kernel.org, and either me or this bug log so we can
> track it).
>
> Be sure to mention the steps to reproduce, expected result, actual
> result, and versions tested, and what kind of testing you would and
> would not be able to do to track this down, just as you have here, and
> include a link to this bug log for the full story.
>
>>> If you have time to test the attached patch[2], that might also be
>>> useful.
>>
>> Sorry, I don't have much time for that.
>
> That's fine.  If we're lucky, someone more familiar with these things
> upstream can come up with some way to confirm or rule out that cause
> without having to build a new kernel.
>
> Thanks for the quick feedback.
> Jonathan



--
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/CAMke3RrKe3EbzPV=zgtypb3smr3csnwj1q+hxpgxcr0_7v8...@mail.gmail.com

Bug#659519: Misfiled messages (Re: [a...@spamfence.net: Re: [3.1.8 -> 3.2.4 regression] ATH9K driver will not connect to my adhoc network])

[Jonathan Nieder]

Messages 30 and 35 are about a different bug (bug #659521).  I cc-ed
the wrong address; sorry for the noise.



-- 
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/20120212185006.GA8230@burratino

Processed: Re: [3.1.8 -> 3.2.4 regression] Acer Aspire 7520G: no sound

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Hans-J. Ullrich wrote:
> #
> # > The bugnumber is #42758, the number of my attachement is #72356.
> forwarded 659461 https://bugzilla.kernel.org/show_bug.cgi?id=42758
Bug #659461 [linux-2.6] linux-image-3.2.0-1-amd64 - no sound after update to 
this kernel
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=42758'.
> quit
Stopping processing here.

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

Processed: Re: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 641749 AR3011: "ath3k_load_firmware: Can't change to loading 
> configuration err" unless libmtp-runtime uninstalled
Bug #641749 [linux-2.6] firmware-atheros doesn't load for Atheros AR3011
Bug #605030 [linux-2.6] general: bluetooth adapter ar3011 on acer aspire 5553g 
don't start after shutdown
Changed Bug title to 'AR3011: "ath3k_load_firmware: Can't change to loading 
configuration err" unless libmtp-runtime uninstalled' from 'firmware-atheros 
doesn't load for Atheros AR3011'
Changed Bug title to 'AR3011: "ath3k_load_firmware: Can't change to loading 
configuration err" unless libmtp-runtime uninstalled' from 'general: bluetooth 
adapter ar3011 on acer aspire 5553g don't start after shutdown'
> reassign 641749 libmtp-runtime
Bug #641749 [linux-2.6] AR3011: "ath3k_load_firmware: Can't change to loading 
configuration err" unless libmtp-runtime uninstalled
Bug #605030 [linux-2.6] AR3011: "ath3k_load_firmware: Can't change to loading 
configuration err" unless libmtp-runtime uninstalled
Bug reassigned from package 'linux-2.6' to 'libmtp-runtime'.
Bug reassigned from package 'linux-2.6' to 'libmtp-runtime'.
Bug No longer marked as found in versions linux-2.6/3.1.4-1, 3.1.8-2, and 
3.0.0-3.
Bug No longer marked as found in versions linux-2.6/3.1.4-1, 3.1.8-2, and 
3.0.0-3.
> affects 641749 + src:linux-2.6
Bug #641749 [libmtp-runtime] AR3011: "ath3k_load_firmware: Can't change to 
loading configuration err" unless libmtp-runtime uninstalled
Bug #605030 [libmtp-runtime] AR3011: "ath3k_load_firmware: Can't change to 
loading configuration err" unless libmtp-runtime uninstalled
Added indication that 641749 affects src:linux-2.6
Added indication that 605030 affects src:linux-2.6
> quit
Stopping processing here.

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

Bug#641749: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

[Jonathan Nieder]

retitle 641749 AR3011: "ath3k_load_firmware: Can't change to loading 
configuration err" unless libmtp-runtime uninstalled
reassign 641749 libmtp-runtime
affects 641749 + src:linux-2.6
quit

Hi,

Andres Cimmarusti wrote:

> This is my device:
>
> Bus 001 Device 003: ID 0cf3:3000 Atheros Communications, Inc. AR3011 
> Bluetooth (no firmware)
>
> It does not turn on and kern.log shows following errors:
>
> [9.335184] ath3k_load_firmware: Can't change to loading configuration err
> [9.335413] ath3k: probe of 1-1.3:1.0 failed with error -110
> [9.335459] usbcore: registered new interface driver ath3k

Product IDs 3000, 3002, and 3005 are somehow involved and switched
between when loading firmware.  Or something.  It's an Asus
bluetooth-USB adaptor, IIRC.

Alessio et al: here's a puzzle for you.  Removing libmtp-runtime
(which seems to have a relevant udev rule) fixes things.  Could you
let upstream know about this?  Any hints or questions for Andres?

Andres: what versions of libmtp-runtime and libmtp9 do you have
installed?

References:

 https://bugzilla.kernel.org/show_bug.cgi?id=27402
 https://bugzilla.redhat.com/show_bug.cgi?id=702375
 https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/822128
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/720949
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/714862

Thanks,
Jonathan



-- 
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/20120212180531.GE1916@burratino

Bug#641749: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

[Andres Cimmarusti]

I believe I have finally narrowed down the problem. It lies in the
'libmtp-runtime' package with the command 'mtp-probe' (only present in
wheezy or newer).

I'm not sure what this is doing to my system, but when the package
mentioned is installed, it "messes" up my atheros bluetooth device so
that the kernel/udev cannot load the firmware into it.

As soon as I uninstalled this package and thus caused the boot process
to throw some errors about missing mtp-probe command, my bluetooth
module was correctly loaded and the led turned on.

>> Inexplicably yesterday's (and the day before) Debian testing snapshot
>> seems to have the problem fixed!

I guess this snapshot that I tested earlier didn't have that package installed

I found out about this completely by chance. For whatever reason, on
my second upgrade to wheezy 'apt-get dist-upgrade' didn't pull
'libmtp-runtime' and my bluetooth module just worked.

I tried to get the bootlog messages so I can send this info, but even
with bootlogd enabled these messages happen too early on the boot
process to be logged in /var/log/boot.

I feel this is not necessarily a kernel bug anymore (all kernels
tested work fine 3.0.x, 3.1.x, 3.2.x and even 3.3.0-rc3). But the
experts will know better.

This is definitely progress!

Cheers

Andres

PS: please forward the info to other bug reports I don't have access
to, like Red Hat / Fedora and Ubuntu. Additional testing is needed.



-- 
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/CAH=dyrfs+ty2xxwvv6y-omi6stt-tyr7nl20+2fyqlv3rgs...@mail.gmail.com

Bug#659519: [3.1.8 -> 3.2.4 regression] ATH9K driver will not connect to my adhoc network

[Jonathan Nieder]

Hi,

Ankman wrote:

> Am I supposed to send all I sent to you previously to the addresses
> given in this mail? So the dmesg log and my setup? Can't you do it
> instead? I don't want to make a mistake.

More important than the logs (which they can get e.g. through a link to
) is a succinct summary of the problem.

I usually ask bug reporters to make the first contact with upstream
so they can add additional information if appropriate and choose an
appropriate time to be able to reply to followups if busy.

> I also might later (cannot guarantee though) be able to apply the
> patch you provided. But I didn't apply pages since quite some time and
> have not much time. If you are interested that I try this can you
> please provide me with all console commands how I do this?

Thanks!  Here's a summary of the page[1] I mentioned before:

# as root:
apt-get source linux-2.6
apt-get install build-essential fakeroot devscripts
apt-get build-dep linux-2.6

# as a normal user:
cd linux-2.6-

bash debian/bin/test-patches 
# or, for parallel build:
bash debian/bin/test-patches -j  

# as root:
dpkg -i ../
reboot

[...]
>>> ifconfig wlan0 down
>>> iwconfig wlan0 mode ad-hoc
>>> iwconfig wlan0 my-essid
>>> iwconfig wlan0 key 12345
>>> ifconfig wlan0 192.168.198.251
>>> route add default gw 192.168.198.78

As David Goodenough hinted, upstream might be more comfortable working
with the "ip" and "iw" tools from the iproute and iw packages.  Something
like this:

ip link set wlan0 down
ip link set wlan0 up
iw dev wlan0 interface add ah0 type ibss
ip link set ah0 up
iw dev ah0 ibss join my-essid 2412
ip address add 192.168.198.251 dev wlan0
ip route add default via 192.168.198.78 dev wlan0

...
iw dev ah0 ibss leave
ip link set ah0 down
ip link set wlan0 down

Running "iw event -t" in another terminal while doing this can give
interesting progress information.  And "dmesg" tends to report errors,
as usual.

Hope that helps,
Jonathan

[1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2



-- 
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/20120212174059.GD1916@burratino

Bug#642911: TX watchdog timeout on RTL8168B

[Jonathan Nieder]

Hi again,

Jonathan Nieder wrote:

> Something very similar to the fix you tested plus a couple more r8169
> fixes were applied upstream:
>
>  - v3.2-rc5~38^2~5 (r8169: Rx FIFO overflow fixes, 2011-12-04), which
>is the fix you helped with
>  - v3.2-rc5~38^2~4 (r8169: fix Rx index race between FIFO overflow
>recovery and NAPI handler, 2011-12-04)
>  - v3.2-rc7~12^2~8 (r8169: fix Config2 MSIEnable bit setting,
>2011-12-15)

Thanks again for making it happen.

> Am I correct in guessing that v3.2-rc7 from experimental works ok?

What kernel do you use these days?  Have you tried 3.2.y from
sid/experimental?  Would you be interested in pursuing a fix in
2.6.32.y or 3.0.y?

Jonathan



-- 
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/20120212171606.GA3036@burratino

Bug#611493: kernel panics or freezes helped but not eliminated by warm reboot or "rootdelay=20"

[Jonathan Nieder]

Pascal BERNARD wrote:

> I must say that I have had no trouble since I switched to kernel 3.x.

That's good to hear.

I still would be interested to hear what the newest kernel you know of
that does exhibit trouble is.  For example, if you can try 2.6.38 (?)
which you mentioned being troublesome before or 2.6.32.y, that would
be useful.

Trying various versions to find out when the problem was fixed could
help us find the fix and prevent others from having to experience the
same on squeeze, but more importantly, trying just _one_ broken
version of the kernel with everything else kept the same would be
enough to confirm that this was a kernel bug that has been fixed.

Thanks for the update.
Jonathan



-- 
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/20120212165524.GC1916@burratino

Bug#659629: Changes from longterm 2.6.32.57

[Ben Hutchings]

Package: src:linux-2.6
Version: 2.6.32-41
Severity: important

This is actually based on 2.6.32.57-rc1.

- IB/mlx4: pass SMP vendor-specific attribute MADs to firmware

Fixes handling of some Infiniband protocol extensions that need to be
passed to the device firmware rather than the kernel.

- mm/filemap_xip.c: fix race condition in xip_file_fault()

Not relevant to Debian configurations.

- NFSv4: Fix up the callers of nfs4_state_end_reclaim_reboot

The NFSv4 client was not properly updating some of its state after a
server reboot, presumably resulting in I/O failures and/or memory leaks.
This should fix that.

- NFSv4: The state manager shouldn't exit on errors that were handled
- NFSv4: Ensure the state manager handles NFS4ERR_NO_GRACE correctly

Fix the NFSv4 client to continue running after certain recoverable
errors, which I think would otherwise result in losing access to the
filesystem.

- NFSv4: Handle NFS4ERR_GRACE when recovering an expired lease.

Fixes handling of a server reboot during revalidation of cached state on
the NFSv4 client, which would otherwise result in an I/O failure.

- NFSv4: Fix open recovery

Fixes the NFSv4 client to send new OPEN requests for open files after
the server reboots.  Without this, I think the server might allow other
clients to cache files that we have open, resulting in data loss.

- rpc client can not deal with ENOSOCK, so translate it into ENOCONN

Fixes error reporting for RPC requests made during reconnection of the
RPC client socket.  The old behaviour apparently could result in NFS I/O
failures during recovery from a server reboot.

- udf: Mark LVID buffer as uptodate before marking it dirty

Fixes a spurious warning when rewriting metadata for this filesystem
after a prior I/O error.

- drm/i915: Fix TV Out refresh rate.

Fixes the display refresh rates for SD TV outputs connected to Intel
GPUs.  This doesn't seem to affect the actual signal rate, because the
previous rates would never have worked, but it does apparently fix
flickering.

We won't get this from 2.6.32.57 since we took DRM from 2.6.33, but we
should probably cherry-pick it anyway.

- eCryptfs: Infinite loop due to overflow in ecryptfs_write()

Fixes loop condition for a write more than 4GB beyond the previous end
of a file on this filesystem, on 32-bit systems.  This doesn't seem to
be a security issue in itself, but can be combined with the fact that
truncation/extension was not killable (before 2.6.32.56) to produce a
more effective DoS.

- atmel_lcdfb: fix usage of CONTRAST_CTR in suspend/resume
- Staging: asus_oled: fix image processing
- Staging: android: binder: Don't call dump_stack in binder_vma_open
- Staging: android: binder: Fix crashes when sharing a binder file between 
processes
- usb: gadget: zero: fix bug in loopback autoresume handling

Not relevant to Debian configurations.

- usb: Skip PCI USB quirk handling for Netlogic XLP

Adds a quirk for PCI USB controllers that should have no effect on
Debian-supported systems.

- USB: usbserial: add new PID number (0xa951) to the ftdi driver

New hardware support.

- mmc: cb710 core: Add missing spin_lock_init for irq_lock of struct cb710_chip

Fixes initialisation of a lock structure in this flash card interface
driver.  Since we don't enable lock debugging and the structure would be
zero-initialised anyway, I don't believe the bug had any effect on
Debian configurations.  But this is obviously correct and harmless.

- net: fix sk_forward_alloc corruptions
- net: sock_queue_err_skb() dont mess with sk_forward_alloc

Removes some accounting of memory used by error/exception packets (ICMP,
local errors and TX timestamps), which was subject to data races.  A
remote attacker could provoke a WARNING by sending ICMP packets, but I
don't think any worse effect was possible.  Note that memory use by
these packets is still limited by the socket receive buffer size.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.




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

Bug#659519: [a...@spamfence.net: Re: [3.1.8 -> 3.2.4 regression] ATH9K driver will not connect to my adhoc network]

[Jonathan Nieder]

Forwarding to the bug log.
--- Begin Message ---
Hello,

as this is my first bug report ever I'm not sure if I understand.

Am I supposed to send all I sent to you previously to the addresses
given in this mail? So the dmesg log and my setup? Can't you do it
instead? I don't want to make a mistake.

I also might later (cannot guarantee though) be able to apply the
patch you provided. But I didn't apply pages since quite some time and
have not much time. If you are interested that I try this can you
please provide me with all console commands how I do this?

With kind regards, Ankman

On Sat, Feb 11, 2012 at 19:27, Jonathan Nieder  wrote:
> Ankman wrote:
>
>> This (attachment "report.txt") will be from my currently booted kernel
>> (3.1.0-1-686-pae)
>
> Thanks!  That's fine.  Forwarded to the bug log.
>
> [...]
>> I solely rely on a script I wrote (key and essid were replaced by me),
>> no network manager involved:
>>
>> ifconfig wlan0 down
>> iwconfig wlan0 mode ad-hoc
>> iwconfig wlan0 my-essid
>> iwconfig wlan0 key 12345
>> ifconfig wlan0 192.168.198.251
>> route add default gw 192.168.198.78
>>
>> Above works reliable for me since months. Until yesterday when the
>> kernel-update was installed
>
> Ok, please send a summary of this problem upstream (that's
> ath9k-de...@lists.ath9k.org, cc-ing linux-wirel...@vger.kernel.org,
> linux-ker...@vger.kernel.org, and either me or this bug log so we can
> track it).
>
> Be sure to mention the steps to reproduce, expected result, actual
> result, and versions tested, and what kind of testing you would and
> would not be able to do to track this down, just as you have here, and
> include a link to this bug log for the full story.
>
>>> If you have time to test the attached patch[2], that might also be
>>> useful.
>>
>> Sorry, I don't have much time for that.
>
> That's fine.  If we're lucky, someone more familiar with these things
> upstream can come up with some way to confirm or rule out that cause
> without having to build a new kernel.
>
> Thanks for the quick feedback.
> Jonathan
--- End Message ---

Processed: tagging 649399

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 649399 + pending
Bug #649399 [initramfs-tools] initramfs-tools: please mark Multi-Arch: foreign
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#611493: kernel panics or freezes helped but not eliminated by warm reboot or "rootdelay=20"

[Pascal BERNARD]

Hi Jonathan,

I must say that I have had no trouble since I switched to kernel 3.x.

I am sorry I did not make the effort of trying different 2.6 versions in 
order to find out which version introduced the issue. I felt as if not 
many other people had this problem. I have also an old motherboard which 
has hardware problems (the audio and one on board  network card died 
which seems to be a great improvement!).


Thank you for your suggestion to try the kernel 3.0. I can keep using 
this computer that does not perform too bad yet.


Best regards,

Pascal

On 10/02/2012 00:19, Jonathan Nieder wrote:

Hi again,

Jonathan Nieder wrote:

   

Could be timing-related.  One way to learn more would be to try
various versions of initramfs-tools from snapshot.debian.org to find
when the change occured.

The investigator's mantra: manipulate one variable, keeping everything
else the same.
 

Did you try this?  Any other news?

In suspense,
Jonathan
   





--
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/4f37bd99.3020...@free.fr

Re: Bug#659521: [3.1.8 -> 3.2.4 regression] ATH9K driver will not connect to my adhoc network

[David Goodenough]

On Sunday 12 Feb 2012, Jonathan Nieder wrote:
> Ankman wrote:
> > This (attachment "report.txt") will be from my currently booted kernel
> > (3.1.0-1-686-pae)
> 
> Thanks!  That's fine.  Forwarded to the bug log.
> 
> [...]
> 
> > I solely rely on a script I wrote (key and essid were replaced by me),
> > no network manager involved:
> > 
> > ifconfig wlan0 down
> > iwconfig wlan0 mode ad-hoc
> > iwconfig wlan0 my-essid
> > iwconfig wlan0 key 12345
> > ifconfig wlan0 192.168.198.251
> > route add default gw 192.168.198.78
> > 
> > Above works reliable for me since months. Until yesterday when the
> > kernel-update was installed
> 
> Ok, please send a summary of this problem upstream (that's
> ath9k-de...@lists.ath9k.org, cc-ing linux-wirel...@vger.kernel.org,
> linux-ker...@vger.kernel.org, and either me or this bug log so we can
> track it).
I suspect that if you do that the reply will be to rewrite the script
to use iw rather than iwconfig.  It might be worth trying that first
as it may solve the problem.

David
> 
> Be sure to mention the steps to reproduce, expected result, actual
> result, and versions tested, and what kind of testing you would and
> would not be able to do to track this down, just as you have here, and
> include a link to this bug log for the full story.
> 
> >> If you have time to test the attached patch[2], that might also be
> >> useful.
> > 
> > Sorry, I don't have much time for that.
> 
> That's fine.  If we're lucky, someone more familiar with these things
> upstream can come up with some way to confirm or rule out that cause
> without having to build a new kernel.
> 
> Thanks for the quick feedback.
> Jonathan


-- 
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/201202121058.49548.david.goodeno...@btconnect.com

Bug#649399: initramfs-tools: please mark Multi-Arch: foreign

[Michael Prokop]

* Ben Hutchings [Sat Feb 11, 2012 at 07:13:10PM +]:
> On Sun, 2011-11-20 at 17:41 +, Colin Watson wrote:

> > It would be useful for initramfs-tools to be marked "Multi-Arch:
> > foreign", to indicate that it can satisfy dependencies of packages of
> > other architectures.  Although Debian's dpkg doesn't yet do anything
> > special with this, it's safe to add this tag in advance of package
> > manager support.

> > In Ubuntu, this is an early step in being able to crossgrade from i386
> > to amd64, because we don't have an -amd64 kernel flavour on i386 and (of
> > course) our kernel packages depend on initramfs-tools.  While Debian
> > does have an -amd64 flavour on i386, it still wouldn't hurt to add this
> > tag.
> [...]

> This is also relevant to Debian now.

> Max, please apply this patch.

Colin's patch is already applied on our i-t.git, I'll upload a new
i-t release in the next few days.

regards,
-mika-


signature.asc
Description: Digital signature