Bug#635573: marked as done (Endless message of "Unable to enumerate usb device on port 5")

[Debian Bug Tracking System]

Your message dated Wed, 24 Aug 2011 01:39:08 -0500
with message-id <20110824063908.ga2...@elie.gateway.2wire.net>
and subject line Re: linux-image-2.6.32-5-amd64: unable to enumerate usb device 
6
has caused the Debian Bug report #620848,
regarding Endless message of "Unable to enumerate usb device on port 5"
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.)


-- 
620848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package:  linux-image-2.6.32-5-amd64
Version:   2.6.32-31

Package:linux-image-2.6.38-2-amd64
Version: 2.6.38-5

Package: linux-image-2.6.39-2-amd64
Version:  2.6.39-3


Console terminal is barraged by endless messages of "Unable to enumerate 
usb device on port 5".



I am using Debian Wheezy with installed kernels of the above.  However 
kernel linux-image-2.6.32-3-amd642.6.32-9  is not affected.




--- End Message ---
--- Begin Message ---
Version: 3.0.0-2

>From :

| commit d05dcfcd0fea25eefa8b85926792b161239ac6b1
| Author: Alan Stern 
| Date:   Fri Jul 15 17:22:15 2011 -0400
|
| USB: OHCI: fix another regression for NVIDIA controllers
|
| commit 6ea12a04d295235ed67010a09fdea58c949e3eb0 upstream.
[...]
| This fixes Bugzilla #22052.

--- End Message ---

Bug#622649: marked as done (linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6)

[Debian Bug Tracking System]

Your message dated Wed, 24 Aug 2011 01:39:08 -0500
with message-id <20110824063908.ga2...@elie.gateway.2wire.net>
and subject line Re: linux-image-2.6.32-5-amd64: unable to enumerate usb device 
6
has caused the Debian Bug report #620848,
regarding linux-image-2.6.38-2-amd64: unable to enumerate USB device on port 6
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.)


-- 
620848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Severity: important
Tags: squeeze sid



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

** Command line:
root=UUID=f2f57267-0289-412c-9f9b-e8702e8b7010 ro vga=791

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

** Kernel log:
[  230.578300] hub 4-0:1.0: USB hub found
[  230.578308] hub 4-0:1.0: 6 ports detected
[  230.612090] usb 1-3: new high speed USB device using ehci_hcd and address 3
[  231.038773] usb 1-3: New USB device found, idVendor=5986, idProduct=0102
[  231.038788] usb 1-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[  231.038796] usb 1-3: Product: Acer Crystal Eye webcam 
[  231.088304] uvcvideo: Found UVC 1.00 device Acer Crystal Eye webcam  
(5986:0102)
[  231.249563] input: Acer Crystal Eye webcam  as 
/devices/pci:00/:00:02.1/usb1/1-3/1-3:1.0/input/input13
[  231.360073] hub 1-0:1.0: unable to enumerate USB device on port 6
[  231.676055] usb 3-1: new low speed USB device using ohci_hcd and address 2
[  231.888074] usb 3-1: New USB device found, idVendor=093a, idProduct=2510
[  231.888080] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  231.888083] usb 3-1: Product: USB OPTICAL MOUSE
[  231.888086] usb 3-1: Manufacturer: PIXART
[  231.901501] input: PIXART USB OPTICAL MOUSE as 
/devices/pci:00/:00:02.0/usb3/3-1/3-1:1.0/input/input14
[  231.901716] generic-usb 0003:093A:2510.0002: input,hidraw0: USB HID v1.11 
Mouse [PIXART USB OPTICAL MOUSE] on usb-:00:02.0-1/input0
[  232.100123] hub 3-0:1.0: unable to enumerate USB device on port 6
[  232.228179] usbcore: registered new interface driver usbserial_generic
[  232.228192] usbserial: USB Serial Driver core
[  232.287673] USB Serial support registered for GSM modem (1-port)
[  232.468049] hub 1-0:1.0: unable to enumerate USB device on port 6
[  232.608135] usbcore: registered new interface driver option
[  232.608141] option: v0.7.2:USB Driver for GSM modems
[  232.808064] hub 3-0:1.0: unable to enumerate USB device on port 6
[  233.048161] hub 1-0:1.0: unable to enumerate USB device on port 6
[  233.260194] hub 3-0:1.0: unable to enumerate USB device on port 6
[  233.500086] hub 1-0:1.0: unable to enumerate USB device on port 6
[  233.712061] hub 3-0:1.0: unable to enumerate USB device on port 6
[  233.952061] hub 1-0:1.0: unable to enumerate USB device on port 6
[  234.164060] hub 3-0:1.0: unable to enumerate USB device on port 6
[  234.404067] hub 1-0:1.0: unable to enumerate USB device on port 6
[  234.616083] hub 3-0:1.0: unable to enumerate USB device on port 6
[  234.856123] hub 1-0:1.0: unable to enumerate USB device on port 6
[  235.068063] hub 3-0:1.0: unable to enumerate USB device on port 6
[  235.308071] hub 1-0:1.0: unable to enumerate USB device on port 6
[  235.520066] hub 3-0:1.0: unable to enumerate USB device on port 6
[  235.760066] hub 1-0:1.0: unable to enumerate USB device on port 6
[  235.972060] hub 3-0:1.0: unable to enumerate USB device on port 6
[  236.212064] hub 1-0:1.0: unable to enumerate USB device on port 6
[  236.424061] hub 3-0:1.0: unable to enumerate USB device on port 6
[  236.528145] ehci_hcd :00:04.1: remove, state 4
[  236.528171] usb usb2: USB disconnect, address 1
[  236.535859] ehci_hcd :00:04.1: USB bus 2 deregistered
[  236.535974] ehci_hcd :00:04.1: PCI INT B disabled
[  236.536053] ehci_hcd :00:02.1: remove, state 1
[  236.536247] usb usb1: USB disconnect, address 1
[  236.552089] hub 1-0:1.0: hub_port_status failed (err = -19)
[  236.552102] hub 1-0:1.0: connect-debounce failed, port 6 disabled
[  236.552155] usb 1-3: USB disconnect, address 3
[  236.592413] ehci_hcd :00:02.1: USB bus 1 deregistered
[  236.592534] ehci_hcd :00:02.1: PCI INT B disabled
[  236.868074] hub 3-0:1.0: unable to enumerate USB device on port 6
[  237.172054] usb 3-3: new full speed USB device using ohci_hcd and address 14
[  237.595095] usb 3-3

Bug#620848: marked as done (linux-image-2.6.32-5-amd64: unable to enumerate usb device 6)

[Debian Bug Tracking System]

Your message dated Wed, 24 Aug 2011 01:39:08 -0500
with message-id <20110824063908.ga2...@elie.gateway.2wire.net>
and subject line Re: linux-image-2.6.32-5-amd64: unable to enumerate usb device 
6
has caused the Debian Bug report #620848,
regarding linux-image-2.6.32-5-amd64: unable to enumerate usb device 6
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.)


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



-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 7 21:35:22 UTC 2011

** Command line:
root=UUID=f2f57267-0289-412c-9f9b-e8702e8b7010 ro vga=791

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

** Kernel log:
[  473.256064] hub 3-0:1.0: unable to enumerate USB device on port 6
[  473.496096] hub 1-0:1.0: unable to enumerate USB device on port 6
[  473.708089] hub 3-0:1.0: unable to enumerate USB device on port 6
[  473.948068] hub 1-0:1.0: unable to enumerate USB device on port 6
[  474.160068] hub 3-0:1.0: unable to enumerate USB device on port 6
[  474.400079] hub 1-0:1.0: unable to enumerate USB device on port 6
[  474.612083] hub 3-0:1.0: unable to enumerate USB device on port 6
[  474.852070] hub 1-0:1.0: unable to enumerate USB device on port 6
[  475.064053] hub 3-0:1.0: unable to enumerate USB device on port 6
[  475.304067] hub 1-0:1.0: unable to enumerate USB device on port 6
[  475.516077] hub 3-0:1.0: unable to enumerate USB device on port 6
[  475.756082] hub 1-0:1.0: unable to enumerate USB device on port 6
[  475.968485] hub 3-0:1.0: unable to enumerate USB device on port 6
[  476.209078] hub 1-0:1.0: unable to enumerate USB device on port 6
[  476.420068] hub 3-0:1.0: unable to enumerate USB device on port 6
[  476.660073] hub 1-0:1.0: unable to enumerate USB device on port 6
[  476.872057] hub 3-0:1.0: unable to enumerate USB device on port 6
[  477.112096] hub 1-0:1.0: unable to enumerate USB device on port 6
[  477.325029] hub 3-0:1.0: unable to enumerate USB device on port 6
[  477.565034] hub 1-0:1.0: unable to enumerate USB device on port 6
[  477.776039] hub 3-0:1.0: unable to enumerate USB device on port 6
[  478.016091] hub 1-0:1.0: unable to enumerate USB device on port 6
[  478.229145] hub 3-0:1.0: unable to enumerate USB device on port 6
[  478.472082] hub 1-0:1.0: unable to enumerate USB device on port 6
[  478.684094] hub 3-0:1.0: unable to enumerate USB device on port 6
[  478.925083] hub 1-0:1.0: unable to enumerate USB device on port 6
[  479.137094] hub 3-0:1.0: unable to enumerate USB device on port 6
[  479.376106] hub 1-0:1.0: unable to enumerate USB device on port 6
[  479.591279] hub 3-0:1.0: unable to enumerate USB device on port 6
[  479.829102] hub 1-0:1.0: unable to enumerate USB device on port 6
[  480.040060] hub 3-0:1.0: unable to enumerate USB device on port 6
[  480.280099] hub 1-0:1.0: unable to enumerate USB device on port 6
[  480.492076] hub 3-0:1.0: unable to enumerate USB device on port 6
[  480.732088] hub 1-0:1.0: unable to enumerate USB device on port 6
[  480.944078] hub 3-0:1.0: unable to enumerate USB device on port 6
[  481.184098] hub 1-0:1.0: unable to enumerate USB device on port 6
[  481.396058] hub 3-0:1.0: unable to enumerate USB device on port 6
[  481.637082] hub 1-0:1.0: unable to enumerate USB device on port 6
[  481.848079] hub 3-0:1.0: unable to enumerate USB device on port 6
[  482.088093] hub 1-0:1.0: unable to enumerate USB device on port 6
[  482.300061] hub 3-0:1.0: unable to enumerate USB device on port 6
[  482.540110] hub 1-0:1.0: unable to enumerate USB device on port 6
[  482.752081] hub 3-0:1.0: unable to enumerate USB device on port 6
[  482.992095] hub 1-0:1.0: unable to enumerate USB device on port 6
[  483.204271] hub 3-0:1.0: unable to enumerate USB device on port 6
[  483.444061] hub 1-0:1.0: unable to enumerate USB device on port 6
[  483.656101] hub 3-0:1.0: unable to enumerate USB device on port 6
[  483.896086] hub 1-0:1.0: unable to enumerate USB device on port 6
[  484.108091] hub 3-0:1.0: unable to enumerate USB device on port 6
[  484.348090] hub 1-0:1.0: unable to enumerate USB device on port 6
[  484.560075] hub 3-0:1.0: unable to enumerate USB device on port 6
[  484.800125] hub 1-0:1.0: unable to enumerate USB device on port 6
[  485.016058] hub 3-0:1.0: unable to enumerate USB device on port 6
[  485.260091] hub 1-0:1.0: unable to enumerate USB de

Bug#638913: linux-source-3.0.0: cpu frequency speedstep_centrino Intel(R) Pentium(R) M processor

[Grzegorz Kochański]

2011/8/23 Ben Hutchings 

> On Tue, 2011-08-23 at 13:30 +0100, Ben Hutchings wrote:
> > On Tue, 2011-08-23 at 09:33 +0200, Grzegorz Kochański wrote:
> > >
> > > It works on my T42 with the 1.8 GHz version of this processor,
> > > using
> > > lenny, squeeze and sid kernel versions.  The BIOS version is
> > > 3.05a.
> > > Maybe there was a regression in a later BIOS version?
> > >
> > > Ben.
> > >
> > >
> > > I have applied the newest BIOS version available at lenovo support for
> > > my T42 (model 2374):
> > > BIOS Version   3.23 (1RETDRWW)
> > > BIOS Date   2007-06-18
> > > Embedded Controller Version 3.03
> > > CPU TypeIntel(R) Pentium(R) M processr,
> > > CPU Speed   1.53GHz
> > [...]
> >
> > Previously you said 1.73 GHz... and Wikipedia doesn't mention a 1.53 GHz
> > version so I think that was correct.
> >
> > Is 'Intel(R) SpeedStep technology' enabled in the BIOS?
> >
> > Have you run any other kernel version or distribution, in which the
> > acpi-cpufreq driver?
>   ...works?
>
> Ben.
>
>
sorry for so not long responding,
I was fighting with  Embedded Controller Version 3.03 and finally it is
3.04, but nothing else has changed.

I did not make a mistake BIOS presents:
CPU Speed   1.53GHz

what is the source of /proc/cpuinfo ?
when I load and unload patched speedstep-centrino module /proc/cpuinfo
stucked with single frequency, even it was changed by ondemand kernel
governor.

so it seems to be still BIOS problem...

rgds
rumi

Processed: Re: brcmsmac: "firmware bug" warning when connecting, hang when unloading brcmsmac driver unless near AP

[Debian Bug Tracking System]

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

> # Camaleón wrote:
> #
> # > I will write to the suggested mailing lists (thanks for that!) and
> # > also to the mentioned devels and hope this can be solved soon.
> #
> # Thanks, Camaleón.
> forwarded 637240 
> http://thread.gmane.org/gmane.linux.kernel.wireless.general/75265
Bug #637240 [linux-2.6] [regression] Compaq Mini CQ10 hangs after soft reset
Set Bug forwarded-to-address to 
'http://thread.gmane.org/gmane.linux.kernel.wireless.general/75265'.
>
End of message, stopping processing here.

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

Processed: tagging 637560

[Debian Bug Tracking System]

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

> tags 637560 + moreinfo
Bug #637560 [linux-2.6] linux-image-3.0.0-1-amd64: CIFS / DFS regression since 
2.6.39-2-amd64: unable to mount a dfs or cifs subtree of a share
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#637560: linux-image-3.0.0-1-amd64: CIFS / DFS regression since 2.6.39-2-amd64: unable to mount a dfs or cifs subtree of a share

[Ben Hutchings]

On Fri, 2011-08-12 at 17:24 +0200, xavier.x.la...@externe.bnpparibas.com
wrote:
[...]
> This message and any attachments (the "message") is
> intended solely for the addressees and is confidential. 
> If you receive this message in error, please delete it and 
> immediately notify the sender. Any use not in accord with 
> its purpose, any dissemination or disclosure, either whole 
> or partial, is prohibited except formal approval. The internet
> can not guarantee the integrity of this message. 
> BNP PARIBAS (and its subsidiaries) shall (will) not 
> therefore be liable for the message if modified. 
> Do not print this message unless it is necessary,
> consider the environment.
[...]

I must inform you that all messages to the Debian BTS are public.
Please confirm that you understand and accept this.

Ben.



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

Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0

[Ben Hutchings]

On Fri, 2011-08-12 at 21:55 +0200, Stefan Lippers-Hollmann wrote:
> Hi
> 
> On Friday 12 August 2011, Ben Hutchings wrote:
> > On Mon, 2011-08-01 at 19:36 -0300, Willian Gustavo Veiga wrote:
> > > Ben, probably you're right. I've missed some information, sorry about 
> > > that:
> > > 
> > > # dmesg
> > > [  312.484057] usb 1-5: new high speed USB device number 9 using ehci_hcd
> > > [  312.664228] usb 1-5: New USB device found, idVendor=0cf3, 
> > > idProduct=1002
> > > [  312.664233] usb 1-5: New USB device strings: Mfr=16, Product=32, 
> > > SerialNumber=48
> > > [  312.664237] usb 1-5: Product: USB2.0 WLAN
> > > [  312.664239] usb 1-5: Manufacturer: ATHER
> > > [  312.664241] usb 1-5: SerialNumber: 12345
> > > [  312.780058] usb 1-5: reset high speed USB device number 9 using 
> > > ehci_hcd
> > > [  312.954434] usb 1-5: firmware not found.
> > 
> > This driver requires the wireless controller to run different firmware,
> > which must be installed as /lib/firmware/carl9170-1.fw.  That file
> > should be included in the firmware-free package, but it isn't yet.  See
> > .
> 
> Given that the licensing for carl9170fw is a bit special[1] for a 
> firmware image targetted at a different architecture and not easy to 
> fulfill in a way that avoids wget on the buildds or code duplication,
> I've started some preliminary packaging for it at:
> 
> Vcs-Svn: svn://svn.berlios.de/fullstory/firmware-carl9170/trunk
> Vcs-Browser: 
> http://svn.berlios.de/svnroot/repos/fullstory/firmware-carl9170/trunk/
>
> While this should meet upstream license conditions in wording and 
> spirit and may pass ftp-master checking, its strong dependencies
> on packaging structures of binutils-source, newlib-source and the 
> versioned gcc-$(GCC_VER)-source make it rather fragile and high 
> maintenance, not to say downright ugly (looking at the list of 
> build-depends). This packaging compiles the sh-2 cross-compiling
> environment at build-time, as introducing a newlib based sh-2
> cross-compiling toolchain for this single package is hardly a preferred
> option for Debian and binutils/ newlib/ gcc maintainers.
[...]

I suggest that you ask the FTP team whether they consider it necessary
for the package to be built in this way.

firmware-free includes source code but does not actually use it at
package build time.  It is rather taken on trust that the source code
can actually be built, though you have prompted me to actually check
this...

Ben.



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

Re: [stable] [Stable-review] Future of the -longterm kernel releases (i.e. how we pick them).

[Greg KH]

On Wed, Aug 17, 2011 at 12:33:56PM +0200, Jeremiah Foster wrote:
> 
> On Aug 17, 2011, at 00:33, Greg KH wrote:
> > On Tue, Aug 16, 2011 at 09:26:24PM +0200, Jeremiah C. Foster wrote:
> >> I'd like to echo Ben's sentiment, particularly in the area of automotive. 
> >> A car has to be supported with parts for at least ten years, often longer, 
> >> and this includes the build system for the infotainment software.
> >> The GENIVI Alliance is now building infotainment systems for their member 
> >> companies (BMW, GM, PSA, Hyundai, etc.) which will have to preserve a 
> >> working kernel for a long time, like lark's tongues in aspic. So there is 
> >> an 
> >> interest in a "longterm, stable" kernel in the automotive industry. 
> >> Furthermore,
> >> know-how around choosing a long term kernel relevant to a car is in short 
> >> supply, so there is a lot of reliance on the distros and commercial OSVs 
> >> in 
> >> this regard.
> > 
> > Isn't that the job of the distros and commercial OSVs today?  
> 
> My understanding is yes. It appears to be a business opportunity for
> many OSVs and others as well, but the distro's are doing a good job so
> increasingly commercial companies are turning to distros, at least
> initially.
> 
> > Are they
> > somehow not doing this job well?  
> 
> I think they are doing the job well which is why there is increasing
> choice; use a distro or pay for an OSV? Rely on the community or
> develop in-house competence? These questions are new, at least for the
> automotive industry, since previously it was all proprietary all the
> time.

Yes, it's a new model that they need to get used to :)

> > Do they need help from the community
> > instead to help define, implement, and maintain this for them?
> 
> I think the answer is yes.
> 
> > I'm genuinely curious about this, I haven't heard this directly from
> > users before, only from companies who are in this line of work, wanting
> > help in doing this for them, for a variety of odd reasons.
> 
> If it helps at all, I can bring up this topic inside GENIVI and ask if
> there are OEMs, Tier 1s and others who would be interested in how to
> identify a kernel that is appropriate for their long-term needs. I
> have participated in GENIVI discussions like this previously and there
> has not necessarily been clarity. Having your perspective and the
> perspective of others with experience in kernel maintenance would be
> helpful.

Please do.  My view of GENIVI from the outside is that it reminds me a
lot of the problems that plagued the old CGL initiative.  Hopefully that
is incorrect on my part.

If there's anyone, or any group, I should be talking to about this, or
any meeting I could attend to help explain it all better, please let me
know, I am more than willing to do so.

> > If so, doesn't this imply that maybe those users should be choosing a
> > different company for this support, or that they have given up on this
> > and want to work directly with the community instead?  
> 
> That is the eternal question. For the auto industry it often boils
> down to the cost / benefit ratio and the cost sensitivity for
> production vehicles per unit is a major factor in what they choose. I
> think if they can find a reasonable long-term kernel they'll help
> maintain it in conjunction with the community.

That's good to hear, any help is appreciated.

Mostly I want to know what patches should be applied, that fix problems
they have.  That and testing the -rc releases would be wonderful.

> > If the latter,
> > I'd be very happy to work with them, contacts are greatly appreciated.
> 
> Very generous of you. Let me see if I can pull together a list of
> people where this can be discussed.

That would be great, odds are, a new thread can be started, and everyone
on cc: taken off, as I doubt they care about this :)

thanks,

greg k-h


-- 
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/20110824044636.gc...@kroah.com

Re: [stable] [Stable-review] Future of the -longterm kernel releases (i.e. how we pick them).

[Greg KH]

On Wed, Aug 17, 2011 at 01:20:37PM -0700, da...@lang.hm wrote:
> On Wed, 17 Aug 2011, Jeremiah Foster wrote:
> 
> >>Do they need help from the community
> >>instead to help define, implement, and maintain this for them?
> >
> >I think the answer is yes.
> >
> 
> to expand on this a bit.
> 
> it's a lot easier to look at changelogs and see if a -stable or
> -longterm update is relavent to your systems than it is to watch the
> flood of merges to the latest kerenl and then figure out how to
> backport them. BUt people who start up just compiling their own
> kernels frequently become testers, if not contributers to the
> kernel. If everyone only runs the distro kernels, then the upstream
> kernel quality will suffer because nobody is testing it.

I totally agree.

> people running -longterm kernels on their productionsystems will not
> be testing the llatest -rc kernel on those systems, but they are
> likely to be more interested in watching and testng new kernel
> releases (at least on lab machines) than people who just wait for
> things to be backported to the distro kernel.

That's good to hear, hopefully the -longterm kernels are useful for them
and their usage model.  If not, please let me know.

greg k-h


-- 
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/20110824044738.gd...@kroah.com

Processed: Re: Kernel-oops while find_busiest_group

[Debian Bug Tracking System]

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

> reassign 639092 linux-2.6 2.6.32-30
Bug #639092 [linux-image-2.6.32-5-amd64] Kernel-oops while find_busiest_group
Bug reassigned from package 'linux-image-2.6.32-5-amd64' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.32-30.
Bug #639092 [linux-2.6] Kernel-oops while find_busiest_group
There is no source info for the package 'linux-2.6' at version '2.6.32-30' with 
architecture ''
Unable to make a source version for version '2.6.32-30'
Bug Marked as found in versions 2.6.32-30.
> forcemerge 636797 639092
Bug#636797: linux-image-2.6.32-5-amd64: avoid divide-by-zero ("divide error: 
") in scheduler
Bug#639092: Kernel-oops while find_busiest_group
Forcibly Merged 636797 639092.

> tags 636797 + upstream
Bug #636797 [linux-2.6] linux-image-2.6.32-5-amd64: avoid divide-by-zero 
("divide error: ") in scheduler
Bug #639092 [linux-2.6] Kernel-oops while find_busiest_group
Added tag(s) upstream.
Added tag(s) upstream.
> quit
Stopping processing here.

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

Bug#639092: Kernel-oops while find_busiest_group

[Jonathan Nieder]

reassign 639092 linux-2.6 2.6.32-30
forcemerge 636797 639092
tags 636797 + upstream
quit

Hi,

Bjoern Boschman wrote:

> After running this kernel for about ~200 days I got the attached
> kernel-oops.
> I'm filling this bugreport as this has happened quite often on different
> machines in the last time.

Thanks much.  If you have time to answer upstream questions or test
patches, please add yourself to the cc list at
.  dkg posted a
workaround patch there that could be useful, especially if tweaked to
use WARN_ON so the kernel could continue to print information to help
understand the bug when this gets triggered.



-- 
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/20110824032755.ga23...@elie.gateway.2wire.net

Processed: tagging 635840

[Debian Bug Tracking System]

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

> tags 635840 - moreinfo
Bug #635840 [firmware-free] Missing firmware for carl9170 driver
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: tagging 637659

[Debian Bug Tracking System]

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

> tags 637659 + pending
Bug #637659 [linux-2.6] pci :00:00.0: BAR 0: address space collision on of 
device [0xc800-0xcfff]
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#637659: pci 0000:00:00.0: BAR 0: address space collision on of device [0xc8000000-0xcfffffff]

[Ben Hutchings]

On Sat, 2011-08-13 at 16:27 +0200, Paul Menzel wrote:
> Package: linux-2.6
> Version: 2.6.32-31

The current stable version is 2.6.32-35; please upgrade.

> Severity: normal
> Tags: upstream fixed-upstream
> 
> Dear Debian folks,
> 
> 
> with Linux kernel 2.6.32 the following message is shown on each boot. 
> 
> [0.206656] pci :00:00.0: BAR 0: address space collision on of 
> device [0xc800-0xcfff]
> 
> Testing 3.0.0-1 this message is *not* shown, so it seems to have been
> fixed in the meanwhile. There is a related Launchpad bug report (linked
> from [1]) [2] indicating that the patch in the Linux patch queue [3]
> fixes this issue.
[...]

This fix was included in longterm update 2.6.32.42 and will be in the
next stable point release (Debian 6.0.3).

Ben.



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

Bug#638921: firmware-netxen: HP NC375i network card fails to autonegotiate with a 100full cisco switch

[Ben Hutchings]

On Tue, 2011-08-23 at 10:12 -0400, Michael Mastrogiacomo wrote:
[...]
> root@odin:~# ethtool -i eth3
> driver: netxen_nic
> version: 4.0.50
> firmware-version: 4.0.555
> bus-info: :06:00.3
> 
> 
> Note, the above is one of the few ethtool commands/options that actually
> work.
> 
> I'd consider attempting to manually flash the card with:
> 
> ethtool --flash eth3 /lib/firmware/phanfw.bin
> 
> but I don't think the flash function works.  But let me know if you'd like
> me to give that a try.
[...]

The --flash command was only recently defined and this driver doesn't
support it.  I don't think it should be necessary to upgrade the
firmware in flash, anyway.

There is a version 4.0.556 available on the HP web site, but the
description is 'This firmware resolves a hang seen on some P3 adapters.'
So I don't think it would fix this problem.

I suspect that this is actually a driver bug that may be resolved in a
newer version.  Can you try installing Linux 2.6.39 or 3.0 from the
'testing' or 'squeeze-backports' suite?

Ben.



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

Processed: tagging 638984

[Debian Bug Tracking System]

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

> tags 638984 + moreinfo
Bug #638984 [linux-2.6] BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188]
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#638984: BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188]

[Ben Hutchings]

On Tue, 2011-08-23 at 16:17 +0200, Sandro Tosi wrote:
> Package: linux-2.6
> Version: 2.6.32-35
> Severity: important
> 
> Hello,
> we've had several server-class machine (G6 and G7 HP Proliant blades) affected
> by the kernel bug mentioned in the subject.
> 
> On the console we can see several several instances of the message:
> 
>   BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188]
> 
> and then the machine is freezed and need a hard reset.
> 
> I've cut&pasted what's left from the kern.log (remotely logged on another
> machine) since I don't have access anymore to those files (plus a bit of
> anonymization about the network :)).
> 
> It's an high priority for us to get it fixed so we can provide all the help 
> you
> might need: just ask about it.
> 
> I've googled a bit about the problem and found these references:
> 
>   http://kerneltrap.org/mailarchive/linux-kernel/2010/11/16/4646082/thread
>   https://bugzilla.redhat.com/show_bug.cgi?id=649694
[...]

The error message you are seeing is not at all specific, so we should
not assume it has anything to do with the Red Hat bug report.

Unfortunately your log shows almost no useful information; the call
traces have been lost.  The only function that is mentioned in your log
is find_get_pages(), which is not present in any of the call traces in
the Red Hat bug report.

It may be that serial logging will be more reliable; could you enable a
serial console and try to capture the error log on another system?

Ben.



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

linux-2.6_2.6.26-26lenny3_powerpc.changes REJECTED

[Debian FTP Masters]

Reject Reasons:
linux-2.6 - temporary reject for package re-sign




===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.


-- 
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/e1qw2g7-0008uv...@franck.debian.org

linux-2.6_2.6.26-26lenny3_i386.changes REJECTED

[Debian FTP Masters]

Reject Reasons:
linux-2.6 - temporary reject for package re-sign




===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.


-- 
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/e1qw2g3-0008tc...@franck.debian.org

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

[Bjorn Helgaas]

Your error is "SP5100 TCO timer: mmio address 0xbafe00 already in
use".  (Same error, but different address.)  That looks like it's in
the middle of your RAM, i.e., it looks completely bogus.  Given the
ugliness of the sp5100_tco driver, that doesn't surprise me.  Possibly
the BIOS configured it differently and we tried to read the MMIO
address from the wrong (hard-coded) I/O ports.  If we can dig up a
spec for this device, maybe this could be fixed up.



-- 
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/CAErSpo7JgG1o_+_Q-hr3WfWXb7xut4joYdmD1=g9zoqff49...@mail.gmail.com

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

[Bjorn Helgaas]

Here's a test patch for the TCO timer issue.  That SP5100 watchdog
driver is a mess -- it gropes around at hard-coded places in I/O port
space -- so while I think this patch will fix the message, the
watchdog itself still may not work.  If you can verify that the
watchdog works, that would be great.

> [    0.470960] pci_root PNP0A03:00: address space collision: host bridge
> window [mem 0x000cc000-0x000c] conflicts with Video ROM [mem
> 0x000c-0x000ce9ff]
> [    0.471052] pci_root PNP0A03:00: address space collision: host bridge
> window [mem 0x000ec000-0x000e] conflicts with reserved [mem
> 0x000ef000-0x000f]

These are unrelated and I'm doing some other work that addresses them.

> [    1.480097] pci :00:04.0: ASPM: Could not configure common clock

I don't know about this one.  It looks like we tried a link retrain
but it failed.  I would poke Shaohua Li  about
this since he submitted the original code for that.


ioapic
Description: Binary data

Bug#601732: xserver-xorg-video-intel: render error upon S3 wakeup

[Sanjoy Mahajan]

I don't think the fix in 
solved the problem for me.  That fix was in 2.6.35-rc2, but the problem
happened for me even with the 2.6.36 kernel.  

However, the good news is that the error is now gone; or rather the
error shows up but is cleared so the system doesn't hang.  I don't know
exactly which kernel solved the problem.  I think it was 2.6.38.  What I
noticed different in the dmesg log is that, ever since I stopped
experiencing hangs, the following line showed up implying that the error
is being cleared automatically:

[1099952.207172] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, 
masking

Here's a few more lines of context from the current dmesg output (Debian
2.6.39 kernel):

[830137.389798] [drm:intel_opregion_setup], graphic opregion physical addr: 0x0
[830137.389804] [drm:intel_opregion_setup], ACPI OpRegion not supported!
[830137.390304] render error detected, EIR: 0x0010
[830137.390308] page table error
[830137.390311]   PGTBL_ER: 0x0001
[830137.390316] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, 
masking
[830137.390328] render error detected, EIR: 0x0010
[830137.390331] page table error
[830137.390335]   PGTBL_ER: 0x0001
[830137.390407] [drm:drm_crtc_helper_set_mode], [CRTC:4]
[830137.390415] [drm:intel_sdvo_debug_write], SDVOB: W: 05 00 00
   (SDVO_CMD_SET_ACTIVE_OUTPUTS)

-- 
-Sanjoy

`Until lions have their historians, tales of the hunt shall always
 glorify the hunters.'  --African Proverb



-- 
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/87d3fvbuiw@approx.mit.edu

Re: lkcl interference with initramfs-tools bug handling

[Ben Hutchings]

On Tue, Aug 23, 2011 at 11:58:33PM +0300, Touko Korpela wrote:
> On Tue, Aug 23, 2011 at 08:05:26PM +, maximilian attems wrote:
> > On Mon, Aug 22, 2011 at 09:10:17PM +0100, Ben Hutchings wrote:
> > > Luke Kenneth Casson Leighton  (lkcl) reported bug
> > > #636123, which then received a follow-up which is very clearly (to me)
> > 
> > this guy is adding to much noise, so that various bug reports get
> > useless. if strong words didn't help yet, please cut him off.
> 
> Maybe give him one more chance. I told him that messages to bug address
> don't reach bug submitter (he wasn't aware of it, now he knows). That has
> caused some miscommunication before.
> It would be good if more people could help with bugs if right ways are told.
 
The whole problem at the moment is that he is contacting another bug
submitter and wasting the other persons's time.  So it would have been
better if you had not let him know hbout the submitter address.

We absolutely do welcome people helping to triage bugs, but lkcl is
hindering us through bad information and a worse attitude.

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/20110823213707.gh29...@decadent.org.uk

Re: lkcl interference with initramfs-tools bug handling

[Touko Korpela]

On Tue, Aug 23, 2011 at 08:05:26PM +, maximilian attems wrote:
> On Mon, Aug 22, 2011 at 09:10:17PM +0100, Ben Hutchings wrote:
> > Luke Kenneth Casson Leighton  (lkcl) reported bug
> > #636123, which then received a follow-up which is very clearly (to me)
> 
> this guy is adding to much noise, so that various bug reports get
> useless. if strong words didn't help yet, please cut him off.

Maybe give him one more chance. I told him that messages to bug address
don't reach bug submitter (he wasn't aware of it, now he knows). That has
caused some miscommunication before.
It would be good if more people could help with bugs if right ways are told.


-- 
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/20110823205833.GA31830@tiikeri.vuoristo.local

Re: lkcl interference with initramfs-tools bug handling

[maximilian attems]

On Mon, Aug 22, 2011 at 09:10:17PM +0100, Ben Hutchings wrote:
> Luke Kenneth Casson Leighton  (lkcl) reported bug
> #636123, which then received a follow-up which is very clearly (to me)

this guy is adding to much noise, so that various bug reports get
useless. if strong words didn't help yet, please cut him off.

thanks

-- 
maks


-- 
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/20110823200526.ge1...@vostochny.stro.at

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

[Ralf Jung]

Hi Bjorn,

> Ralf, can you attach your /proc/iomem contents, too?  I looked at the
> "SP5100 TCO timer: mmio address 0xfec000f0 already in use" message,
> but I don't see why that address is in use.
Sure, you can find it attached.

I am getting some more kernel error messages during boot (that I planned to 
report later), they may or may not be related, so I just log them here for the 
sake of completeness - please feel free to ignore them if you think they are 
unrelated:

[0.470960] pci_root PNP0A03:00: address space collision: host bridge 
window [mem 0x000cc000-0x000c] conflicts with Video ROM [mem  
0x000c-0x000ce9ff]
[0.471052] pci_root PNP0A03:00: address space collision: host bridge  
window [mem 0x000ec000-0x000e] conflicts with reserved [mem  
0x000ef000-0x000f]
(at least one of them seems to be covered by 
https://bugzilla.kernel.org/show_bug.cgi?id=38522 so I will wait until 3.1 is 
out before reporting)

Sometimes I also get this message - unfortunately, I could not yet find a 
pattern for when this occurs and when not:
[1.480097] pci :00:04.0: ASPM: Could not configure common clock

Kind regards,
Ralf
- : reserved
0001-0009fbff : System RAM
0009fc00-0009 : reserved
000a-000b : PCI Bus :00
000c-000ce9ff : Video ROM
  000c-000c3fff : PCI Bus :00
  000c4000-000c7fff : PCI Bus :00
  000c8000-000cbfff : PCI Bus :00
000d-000d3fff : PCI Bus :00
000d4000-000d7fff : PCI Bus :00
000d8000-000dbfff : PCI Bus :00
000dc000-000d : PCI Bus :00
000e-000e3fff : PCI Bus :00
000e4000-000e7fff : PCI Bus :00
000e8000-000ebfff : PCI Bus :00
000ef000-000f : reserved
  000f-000f : System ROM
0010-acb6 : System RAM
  0100-0133f2e2 : Kernel code
  0133f2e3-0168a07f : Kernel data
  0171b000-017f7fff : Kernel bss
acb7-acb7 : ACPI Non-volatile Storage
acb8-afd4efff : System RAM
afd4f000-afdcefff : reserved
afdcf000-afecefff : ACPI Non-volatile Storage
afecf000-afefefff : ACPI Tables
afeff000-afef : System RAM
aff0-afff : RAM buffer
c000-dfff : PCI Bus :00
  c000-cfff : PCI Bus :01
c000-cfff : :01:05.0
  d000-d0ff : PCI Bus :02
  d100-d1ff : PCI Bus :03
  d200-d20f : PCI Bus :06
d200-d2003fff : :06:00.0
  d210-d30f : PCI Bus :03
  d310-d41f : PCI Bus :02
d310-d3103fff : :02:00.0
  d310-d3103fff : sky2
  d420-d43f : PCI Bus :01
d420-d42f : :01:05.0
d430-d430 : :01:05.0
  d440-d4403fff : :00:14.2
d440-d4403fff : ICH HD audio
  d4404000-d4404fff : :00:14.5
d4404000-d4404fff : ohci_hcd
  d4405000-d4405fff : :00:13.1
d4405000-d4405fff : ohci_hcd
  d4406000-d4406fff : :00:13.0
d4406000-d4406fff : ohci_hcd
  d4407000-d4407fff : :00:12.1
d4407000-d4407fff : ohci_hcd
  d4408000-d4408fff : :00:12.0
d4408000-d4408fff : ohci_hcd
  d4409000-d44093ff : :00:11.0
d4409000-d44093ff : ahci
  d4409400-d44094ff : :00:13.2
d4409400-d44094ff : ehci_hcd
  d4409500-d44095ff : :00:12.2
d4409500-d44095ff : ehci_hcd
e000-efff : PCI MMCONFIG  [bus 00-ff]
  e000-efff : reserved
e000-efff : pnp 00:05
f000- : PCI Bus :00
  feb0-feb00fff : reserved
feb0-feb00fff : pnp 00:05
  fec0-fec00fff : reserved
fec0-fec003ff : IOAPIC 0
  fed0-fed003ff : HPET 0
  fee0-fee00fff : Local APIC
fee0-fee00fff : reserved
  fee0-fee00fff : pnp 00:05
  ffe0- : reserved
ffe0- : pnp 00:05
1-13fff : System RAM

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

[Bjorn Helgaas]

Ralf, can you attach your /proc/iomem contents, too?  I looked at the
"SP5100 TCO timer: mmio address 0xfec000f0 already in use" message,
but I don't see why that address is in use.



-- 
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/CAErSpo51cfAb==k3DrCV7KzXtKtkFxQmMeYq=r7ene-jbu0...@mail.gmail.com

Bug#637284: Can't install wheezy on a 2011 iMac

[Jonathan Nieder]

Mike Hore wrote:
> Hi Jonathan,

>> at the moment, using the
>> squeeze installer and then upgrading is more likely to be reliable.
>
> That was the first thing I tried a while ago -- then somebody suggested I
> try the latest installer which is what I did.

Based on [1] it looks like the fix to http://bugs.debian.org/627705
should help once it hits squeeze.

[...]
> But I'm not in a
> particular hurry -- I've just installed MacOSX 10.7 (Lion) and I've got
> heaps of other things to keep busy with  :-)

Sure, makes sense.  Have fun with the new computer. :)

[1] http://thread.gmane.org/gmane.linux.debian.user/414937



-- 
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/20110823162852.gc3...@elie.gateway.2wire.net

Bug#638938: marked as done (linux-tools-3.0.0: "perf report" segfaults when using binary version; compiling from source works)

[Debian Bug Tracking System]

Your message dated Tue, 23 Aug 2011 09:22:57 -0700
with message-id 

and subject line linux-tools-3.0.0: "perf report" segfaults when using binary 
version; compiling from source works
has caused the Debian Bug report #638938,
regarding linux-tools-3.0.0: "perf report" segfaults when using binary version; 
compiling from source works
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.)


-- 
638938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-tools-3.0.0
Version: 3.0.0-1
Severity: normal


I captured a few perf traces on a live system (using "perf record --event
cpu-clock --freq 1000 -a --output=mylog.perf").

When I try to run a report on those perf logs, it segfaults.  I can run it
under gdb and get a stacktrace (below).

If I install the linux-source package, expand it, and do a "make" in
tools/perf, then that version of perf works (no segfault).

The version I built does reference different shared libraries (according to
ldd).  Most notably, it include libbfd-2.21.52-system.20110606.so.  I
believe that cplus_demangle is only called if bfd is not present(?)


Stacktrace from gdb:

Program received signal SIGSEGV, Segmentation fault.
0x0047630f in ?? ()
(gdb) bt
#0  0x0047630f in ?? ()
#1  0x00477be3 in ?? ()
#2  0x004765d9 in ?? ()
#3  0x004752f6 in ?? ()
#4  0x004776e5 in ?? ()
#5  0x00473e8a in ?? ()
#6  0x004742e7 in ?? ()
#7  0x00479f67 in cplus_demangle_print_callback ()
#8  0x0047a0d6 in ?? ()
#9  0x0047a267 in ?? ()
#10 0x0047a41e in cplus_demangle_v3 ()
#11 0x0046e778 in cplus_demangle ()
#12 0x0043f308 in ?? ()
#13 0x004413db in dso__load ()
#14 0x00449db0 in map__load ()
#15 0x00449f0d in map__find_symbol ()
#16 0x0042ed7d in perf_event__preprocess_sample ()
#17 0x00419fed in ?? ()
#18 0x0044c585 in ?? ()
#19 0x0044dbb3 in __perf_session__process_events ()
#20 0x0041a3c5 in cmd_report ()
#21 0x00410a59 in _start ()


-- System Information:
Debian Release: wheezy/sid
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-tools-3.0.0 depends on:
ii  libc62.13-16 Embedded GNU C Library: Shared
lib
ii  libelf1  0.152-1 library to read and write ELF
file
ii  libnewt0.52  0.52.11-2.1 Not Erik's Windowing Toolkit -
tex
ii  libperl5.12  5.12.4-4shared Perl library
ii  libpython2.6 2.6.7-3 Shared Python runtime library
(ver
ii  libslang22.2.4-2 S-Lang programming library -
runti
ii  perl 5.12.4-4Larry Wall's Practical
Extraction
ii  python   2.6.7-3 interactive high-level
object-orie

Versions of packages linux-tools-3.0.0 recommends:
ii  linux-base3.3Linux image base package

Versions of packages linux-tools-3.0.0 suggests:
pn  linux-doc-3.0.0(no description available)

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.0.0-2

Thanks for the suggestions.  I tried manually installing 3.0.0-2 and
that did fix the problem (and going back to 3.0.0-1 did reintroduce
the problem).  The problem also was fixed when I compiled with
HAVE_CPLUS_DEMANGLE=YesPlease (and that was indeed linked without
libbfd).

I agree that this does likely point to a bugfix in a newer version of
a statically linked library, probably binutils-dev.

Thanks for the fix, and the help.  Closing, as this is fixed in 3.0.0-2.

Justin

--- End Message ---

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

[Bjorn Helgaas]

Thanks!  These tests:

if ((dev->vendor == PCI_VENDOR_ID_AMD) || (dev->device ==
PCI_DEVICE_ID_AMD_GOLAM_7450))

are clearly wrong.  I suspect "&&" was intended instead of "||", but
this code seems to have been that  way since the beginning, so I don't
know how to verify that.

In any event, it would be perfectly legal for any other (non-AMD)
manufacturer to make a PCI bridge that uses the 0x7450 device ID, and
this code would do the wrong thing with it.

I think we should change that "||" to "&&".  That will fix your
message and avoid any conflicts with non-AMD devices.  It's possible
that it will break shpchp on some non-7450 AMD bridges, but we'll just
have to deal with those as we discover them.

I cc'd a couple AMD folks in case they have comments [see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638863].



-- 
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/caerspo5yuusersofbk8y3up64dpyzn+ztp9+valmxhhd2df...@mail.gmail.com

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

[Bjorn Helgaas]

Hi Ralf, can you attach the complete dmesg log to the bug report,
please?  I see a snippet (starting with "Bluetooth: SCO socket layer
initialized"), but there's a lot of useful information before that.
The "dmesg" command only shows the most recent part of the log, so if
the kernel's buffer has wrapped around, it doesn't show the beginning.
 The /var/log/dmesg (or similar) file should contain the useful bits.



-- 
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/caerspo5fpmjqf5pycm+6iytdosh4jh7nu3tepkofwu-cntk...@mail.gmail.com

Bug#638921: firmware-netxen: HP NC375i network card fails to autonegotiate with a 100full cisco switch

[Michael Mastrogiacomo]

>So, does the system have firmware-netxen installed?  If not, can you try
>installing it and rebooting?

Yes:

# dpkg -l | grep -i netxen
ii  firmware-netxen 0.28 Binary
firmware for QLogic Intelligent Ethernet (3000 and 3100 Series)





>What does the command 'dmesg | grep netxen' show?

Here's the output...looks like the firmware already installed on the card is
newer than what the OS driver is trying to put there if I'm interpreting it
right:

[3.023934] NetXen Network Driver version 4.0.50
[3.024026] netxen_nic :06:00.0: PCI INT A -> GSI 24 (level, low) ->
IRQ 24
[3.024035] netxen_nic :06:00.0: setting latency timer to 64
[3.024159] netxen_nic :06:00.0: 2MB memory map
[3.024253] netxen_nic :06:00.0: firmware: requesting phanfw.bin
[3.040514] netxen_nic :06:00.0: phanfw.bin: firmware is older than
flash
[3.051231] netxen_nic :06:00.0: firmware: requesting nx3fwct.bin
[3.055436] netxen_nic :06:00.0: nx3fwct.bin: firmware is older than
flash
[3.267122] netxen_nic :06:00.0: using 64-bit dma mask
[3.267451] NetXen NX3031 Gigabit Ethernet Board S/N KD98MP1738  Chip rev
0x42
[3.267456] netxen_nic :06:00.0: firmware v4.0.555 [legacy]
[3.267520] netxen_nic :06:00.0: irq 103 for MSI/MSI-X
[3.267532] netxen_nic :06:00.0: irq 104 for MSI/MSI-X
[3.267544] netxen_nic :06:00.0: irq 105 for MSI/MSI-X
[3.267556] netxen_nic :06:00.0: irq 106 for MSI/MSI-X
[3.267571] netxen_nic :06:00.0: using msi-x interrupts
[3.268277] netxen_nic :06:00.0: eth0: GbE port initialized
[3.268299] netxen_nic :06:00.1: PCI INT A -> GSI 24 (level, low) ->
IRQ 24
[3.268306] netxen_nic :06:00.1: setting latency timer to 64
[3.268385] netxen_nic :06:00.1: 2MB memory map
[3.268475] netxen_nic :06:00.1: using 64-bit dma mask
[3.268803] netxen_nic :06:00.1: firmware v4.0.555 [legacy]
[3.268844] netxen_nic :06:00.1: irq 107 for MSI/MSI-X
[3.268856] netxen_nic :06:00.1: irq 108 for MSI/MSI-X
[3.268868] netxen_nic :06:00.1: irq 109 for MSI/MSI-X
[3.268880] netxen_nic :06:00.1: irq 110 for MSI/MSI-X
[3.268895] netxen_nic :06:00.1: using msi-x interrupts
[3.269589] netxen_nic :06:00.1: eth1: GbE port initialized
[3.269606] netxen_nic :06:00.2: PCI INT A -> GSI 24 (level, low) ->
IRQ 24
[3.269612] netxen_nic :06:00.2: setting latency timer to 64
[3.269690] netxen_nic :06:00.2: 2MB memory map
[3.269780] netxen_nic :06:00.2: using 64-bit dma mask
[3.270108] netxen_nic :06:00.2: firmware v4.0.555 [legacy]
[3.270147] netxen_nic :06:00.2: irq 111 for MSI/MSI-X
[3.270159] netxen_nic :06:00.2: irq 112 for MSI/MSI-X
[3.270170] netxen_nic :06:00.2: irq 113 for MSI/MSI-X
[3.270182] netxen_nic :06:00.2: irq 114 for MSI/MSI-X
[3.270197] netxen_nic :06:00.2: using msi-x interrupts
[3.270936] netxen_nic :06:00.2: eth2: GbE port initialized
[3.270954] netxen_nic :06:00.3: PCI INT A -> GSI 24 (level, low) ->
IRQ 24
[3.270960] netxen_nic :06:00.3: setting latency timer to 64
[3.271039] netxen_nic :06:00.3: 2MB memory map
[3.271138] netxen_nic :06:00.3: using 64-bit dma mask
[3.271466] netxen_nic :06:00.3: firmware v4.0.555 [legacy]
[3.271506] netxen_nic :06:00.3: irq 115 for MSI/MSI-X
[3.271518] netxen_nic :06:00.3: irq 116 for MSI/MSI-X
[3.271530] netxen_nic :06:00.3: irq 117 for MSI/MSI-X
[3.271542] netxen_nic :06:00.3: irq 118 for MSI/MSI-X
[3.271556] netxen_nic :06:00.3: using msi-x interrupts
[3.272346] netxen_nic :06:00.3: eth3: GbE port initialized
[7.270065] netxen_nic: eth2 NIC Link is up
[  283.125441] netxen_nic: eth2 NIC Link is down
[  296.787316] netxen_nic: eth2 NIC Link is up



root@odin:~# ethtool -i eth3
driver: netxen_nic
version: 4.0.50
firmware-version: 4.0.555
bus-info: :06:00.3


Note, the above is one of the few ethtool commands/options that actually
work.

I'd consider attempting to manually flash the card with:

ethtool --flash eth3 /lib/firmware/phanfw.bin

but I don't think the flash function works.  But let me know if you'd like
me to give that a try.


-Original Message-
From: Ben Hutchings [mailto:b...@decadent.org.uk] 
Sent: Tuesday, August 23, 2011 9:07 AM
To: Michael Mastrogiacomo
Cc: 638...@bugs.debian.org
Subject: RE: Bug#638921: firmware-netxen: HP NC375i network card fails to
autonegotiate with a 100full cisco switch

On Tue, 2011-08-23 at 08:59 -0400, Michael Mastrogiacomo wrote:
> Hello Ben, thanks for the reply.  
> 
> 
> >Right, if autonegotiation fails then it is possible for 'parallel
> >detection' to establish a 100HD link.  The question is why autoneg
> >failed.
> 
> I concur.  I suspect the driver.  
> 
> I should mention that this sounds like a similar issue:
> 
>
http://h3049

Bug#638921: firmware-netxen: HP NC375i network card fails to autonegotiate with a 100full cisco switch

[Michael Mastrogiacomo]

Hello Ben, thanks for the reply.  


>Right, if autonegotiation fails then it is possible for 'parallel
>detection' to establish a 100HD link.  The question is why autoneg
>failed.

I concur.  I suspect the driver.  

I should mention that this sounds like a similar issue:

http://h30499.www3.hp.com/t5/Networking/Problem-with-NC375i-and-NC375T-on-Re
dHat-Linux5/td-p/4712102 


I assume nx_nic drivers are in nx3fwct.bin and phanfw.bin contains the
netxen_nic drivers. I guess the installer overrides nx3fwct.bin if it 
finds phanfw.bin because lsmod has only shown netxen_nic drivers loaded
in both of my install attempts.

I suppose I could try deleting phanfw.bin from my removable media to leave
only nx3fwct.bin there and see what happens with the different drivers.


>When you say that the installation failed, do you mean that you
>were unable to complete the installation, or that the installation
>was broken because it could not set up the network connection?

Sorry for that ambiguity.  The installer ran fine to completion.  I meant
"failed" in the sense that end result was that the NIC card still failed to
autonegotiate after rebooting after installation.




Thanks

==



On Mon, Aug 22, 2011 at 06:53:44PM -0400, Michael Mastrogiacomo wrote:
> Package: firmware-netxen
> Version: 0.28
> Severity: critical
> Justification: breaks the whole system
>
> The HP NC375i network card on an HP ML370 G6 server with Debian
> squeeze OS installed as problems.
> The server is connected to a switch that does only 100/full and it
> fails to autonegotiate correctly during reboot.  A network
> connection can be used if the switch side gets locked to 100 half
> however which seems to be what the HP card assumes if negotiaton
> fails.

Right, if autonegotiation fails then it is possible for 'parallel
detection' to establish a 100HD link.  The question is why autoneg
failed.

[...]
> A perhaps related issue is that during install nx3fwct.bin is
> requested by the installer but are not available in the non-free zip
> file.

The file phanfw.bin should also work, and I understand that this
is the preferred firmware file.

> I tried 2 different installs, both which failed; one involved
> skippin that file during the install by just hitting next at the
> installer prompt; the other way involved extracting the file from an
> rpm provided for redhat installs...I got that RPM from the HP
> website, hp-nx-nic-tools_4.0_520-6_all.rpm

When you say that the installation failed, do you mean that you
were unable to complete the installation, or that the installation
was broken because it could not set up the network connection?

If the installation failed, you should report a bug against
'installation-reports'.

If the installation is broken, does the installed system actually have
the package firmware-netxen installed?

Ben.


-Original Message-
From: Ben Hutchings [mailto:b...@decadent.org.uk] 
Sent: Monday, August 22, 2011 8:36 PM
To: Michael Mastrogiacomo; 638...@bugs.debian.org
Subject: Re: Bug#638921: firmware-netxen: HP NC375i network card fails to
autonegotiate with a 100full cisco switch

On Mon, Aug 22, 2011 at 06:53:44PM -0400, Michael Mastrogiacomo wrote:
> Package: firmware-netxen
> Version: 0.28
> Severity: critical
> Justification: breaks the whole system
>
> The HP NC375i network card on an HP ML370 G6 server with Debian
> squeeze OS installed as problems.
> The server is connected to a switch that does only 100/full and it
> fails to autonegotiate correctly during reboot.  A network
> connection can be used if the switch side gets locked to 100 half
> however which seems to be what the HP card assumes if negotiaton
> fails.

Right, if autonegotiation fails then it is possible for 'parallel
detection' to establish a 100HD link.  The question is why autoneg
failed.

[...]
> A perhaps related issue is that during install nx3fwct.bin is
> requested by the installer but are not available in the non-free zip
> file.

The file phanfw.bin should also work, and I understand that this
is the preferred firmware file.

> I tried 2 different installs, both which failed; one involved
> skippin that file during the install by just hitting next at the
> installer prompt; the other way involved extracting the file from an
> rpm provided for redhat installs...I got that RPM from the HP
> website, hp-nx-nic-tools_4.0_520-6_all.rpm

When you say that the installation failed, do you mean that you
were unable to complete the installation, or that the installation
was broken because it could not set up the network connection?

If the installation failed, you should report a bug against
'installation-reports'.

If the installation is broken, does the installed system actually have
the package firmware-netxen installed?

Ben.

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




-- 
To U

Bug#638921: firmware-netxen: HP NC375i network card fails to autonegotiate with a 100full cisco switch

[Ben Hutchings]

On Tue, 2011-08-23 at 08:59 -0400, Michael Mastrogiacomo wrote:
> Hello Ben, thanks for the reply.  
> 
> 
> >Right, if autonegotiation fails then it is possible for 'parallel
> >detection' to establish a 100HD link.  The question is why autoneg
> >failed.
> 
> I concur.  I suspect the driver.  
> 
> I should mention that this sounds like a similar issue:
> 
> http://h30499.www3.hp.com/t5/Networking/Problem-with-NC375i-and-NC375T-on-Re
> dHat-Linux5/td-p/4712102 
> 
> 
> I assume nx_nic drivers are in nx3fwct.bin and phanfw.bin contains the
> netxen_nic drivers.

The netxen_nic driver is in the kernel package
(linux-image-2.6.32-5-amd64).  I assume nx_nic is an earlier version of
the driver; no driver of that name has been included in Linux.

> I guess the installer overrides nx3fwct.bin if it 
> finds phanfw.bin

The driver decides which firmware file to load.  The current version of
netxen_nic prefers phanfw.bin but can also use one of the nx3fw*.bin
files (dependent on the hardware model).  If none are found then it
falls back to using the firmware loaded from flash (which is presumably
buggy).

> because lsmod has only shown netxen_nic drivers loaded
> in both of my install attempts.
> 
> I suppose I could try deleting phanfw.bin from my removable media to leave
> only nx3fwct.bin there and see what happens with the different drivers.
> 
> 
> >When you say that the installation failed, do you mean that you
> >were unable to complete the installation, or that the installation
> >was broken because it could not set up the network connection?
> 
> Sorry for that ambiguity.  The installer ran fine to completion.  I meant
> "failed" in the sense that end result was that the NIC card still failed to
> autonegotiate after rebooting after installation.
[...]

So, does the system have firmware-netxen installed?  If not, can you try
installing it and rebooting?

What does the command 'dmesg | grep netxen' show?

Ben.



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

Processed: tagging 638956

[Debian Bug Tracking System]

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

> tags 638956 + pending
Bug #638956 [linux-2.6] include-network bug script doesn't work in case of 
bonding
Ignoring request to alter tags of bug #638956 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 638956

[Debian Bug Tracking System]

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

> tags 638956 + pending
Bug #638956 [linux-2.6] include-network bug script doesn't work in case of 
bonding
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#638913: linux-source-3.0.0: cpu frequency speedstep_centrino Intel(R) Pentium(R) M processor

[Ben Hutchings]

On Tue, 2011-08-23 at 13:30 +0100, Ben Hutchings wrote:
> On Tue, 2011-08-23 at 09:33 +0200, Grzegorz Kochański wrote:
> > 
> > It works on my T42 with the 1.8 GHz version of this processor,
> > using
> > lenny, squeeze and sid kernel versions.  The BIOS version is
> > 3.05a.
> > Maybe there was a regression in a later BIOS version?
> > 
> > Ben.
> > 
> > 
> > I have applied the newest BIOS version available at lenovo support for
> > my T42 (model 2374):
> > BIOS Version   3.23 (1RETDRWW)
> > BIOS Date   2007-06-18
> > Embedded Controller Version 3.03
> > CPU TypeIntel(R) Pentium(R) M processr,
> > CPU Speed   1.53GHz
> [...]
> 
> Previously you said 1.73 GHz... and Wikipedia doesn't mention a 1.53 GHz
> version so I think that was correct.
> 
> Is 'Intel(R) SpeedStep technology' enabled in the BIOS?
> 
> Have you run any other kernel version or distribution, in which the
> acpi-cpufreq driver?
  ...works?

Ben.



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

Bug#638956: include-network bug script doesn't work in case of bonding

[Ben Hutchings]

On Tue, 2011-08-23 at 12:15 +0200, Sandro Tosi wrote:
> Package: linux-2.6
> Version: 2.6.32-30
> Severity: minor
> File: /usr/share/bug/linux-image-2.6.32-5-amd64/include-network
> 
> include-network does a 
> 
>  for dir in /sys/class/net/*; do
>   ...
>   cat "$dir"/features >&3
> 
> but when bonding is active, there's also a file 'bonding_masters' under
> /sys/class/net/ and so the 'cat' fails. I've just replaced that line with
> 
>   [ -f "$dir"/features ] && cat "$dir"/features >&3
> 
> and it works.
[...]

We might as well remove this line; the 'features' attribute is being
removed in Linux 3.1.

Ben.



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

Bug#638956: include-network bug script doesn't work in case of bonding

[Ben Hutchings]

On Tue, 2011-08-23 at 12:25 +0200, Sandro Tosi wrote:
> On Tue, Aug 23, 2011 at 12:15, Sandro Tosi  wrote:
> > Package: linux-2.6
> > Version: 2.6.32-30
> 
> dunno how those pkg name & version came out, I was referring to
> linux-image-2.6.32-5-amd64
[...]

Kernel bugs usually apply to many binary packages.  We configure
reportbug to use the source package name instead.

Ben.



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

Bug#638913: linux-source-3.0.0: cpu frequency speedstep_centrino Intel(R) Pentium(R) M processor

[Ben Hutchings]

On Tue, 2011-08-23 at 09:33 +0200, Grzegorz Kochański wrote:
> 
> It works on my T42 with the 1.8 GHz version of this processor,
> using
> lenny, squeeze and sid kernel versions.  The BIOS version is
> 3.05a.
> Maybe there was a regression in a later BIOS version?
> 
> Ben.
> 
> 
> I have applied the newest BIOS version available at lenovo support for
> my T42 (model 2374):
> BIOS Version   3.23 (1RETDRWW)
> BIOS Date   2007-06-18
> Embedded Controller Version 3.03
> CPU TypeIntel(R) Pentium(R) M processr,
> CPU Speed   1.53GHz
[...]

Previously you said 1.73 GHz... and Wikipedia doesn't mention a 1.53 GHz
version so I think that was correct.

Is 'Intel(R) SpeedStep technology' enabled in the BIOS?

Have you run any other kernel version or distribution, in which the
acpi-cpufreq driver?

Ben.



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

Bug#638938: linux-tools-3.0.0: "perf report" segfaults when using binary version; compiling from source works

[Ben Hutchings]

On Mon, 2011-08-22 at 23:08 -0700, Justin Santa Barbara wrote:
> Package: linux-tools-3.0.0
> Version: 3.0.0-1
> Severity: normal
> 
> 
> I captured a few perf traces on a live system (using "perf record
> --event cpu-clock --freq 1000 -a --output=mylog.perf").
> 
> When I try to run a report on those perf logs, it segfaults.  I can
> run it under gdb and get a stacktrace (below).
> 
> If I install the linux-source package, expand it, and do a "make" in
> tools/perf, then that version of perf works (no segfault).
> 
> The version I built does reference different shared libraries
> (according to ldd).  Most notably, it include
> libbfd-2.21.52-system.20110606.so.  I believe that cplus_demangle is
> only called if bfd is not present(?)
[...]

Right.  Bug report #606050 explains why we build perf using
cplus_demangle() from libiberty and not the similar function in libbfd.

Ben.




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

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

[Ralf Jung]

Hi list,

each time I start up my laptop (Debian testing, Linux 3.0 as provided in the 
repositories), the following error (warning?) appears:

[5.083819] shpchp :00:01.0: Cannot reserve MMIO region

The system is working fine as far as I can tell. I observed that message for 
quite a while already, even back when I still used Kubuntu with the kernel 
version 2.6.38, then with 2.6.39 on Debian testing, and now with 3.0.

I reported this downstream at http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=638863 where you can also find the full dmesg and lspci 
output, the loaded kernel modules, and so on. Jonathan replied with a quick 
analysis and saying that I should report this upstream on this list. Here's 
what he wrote:

> The relevant code is in drivers/pci/hotplug/shpchp_hpc.c:
> 
>   if (!request_mem_region(ctrl->mmio_base, ctrl->mmio_size, MY_NAME)) {
>   ctrl_err(ctrl, "Cannot reserve MMIO region\n");
>   rc = -1;
>   goto abort;
>   }
> 
> This comes after a message like
> 
>   shpchp :00:01.0: HPC vendor_id 1022 device_id 9602 ss_vid 1022 
> ss_did
> 9602
> 
> which means that a hotplug controller was detected.  Looking at "lspci -nn"
> output, I can see that this device is
> 
>   00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI
> bridge (int gfx)
> 
> So the problem would seem to be that Linux thinks this PCI-PCI bridge
> supports the standard hotplug controller interface (because it assumes
> _anything_ with AMD's vendor id does), when it doesn't.
> 
>   static int is_shpc_capable(struct pci_dev *dev)
>   {
>   if ((dev->vendor == PCI_VENDOR_ID_AMD) || (dev->device ==
>   
> PCI_DEVICE_ID_AMD_GOLAM_7450))
>   return 1;
>   if (!pci_find_capability(dev, PCI_CAP_ID_SHPC))
>   return 0;
>   if (get_hp_hw_control_from_firmware(dev))
>   return 0;
>   return 1;
>   }
> 
> The test has been that way ever since v2.6.15-rc1~731^2~22^2~13
> (shpchp: detect SHPC capability before doing a lot of work,
> 2006-10-13).  The false positive (if it actually is a false positive)
> is clearly harmless.  If someone wants to remove the "if (dev->vendor
> == PCI_VENDOR_ID_AMD)" exception, it would be necessary to research
> why it is there in the first place (are there AMD hotplug controllers
> that do not advertise the shpc capability for which that exception is
> needed?) and if so, what a more precise exception to solve the same
> problem would be.

Kind regards,
Ralf

(I am not subscribed to linux-pci, so please CC me in replies)



-- 
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/201108231433.08257.ralfjun...@gmx.de

Bug#638956: include-network bug script doesn't work in case of bonding

[Sandro Tosi]

On Tue, Aug 23, 2011 at 12:15, Sandro Tosi  wrote:
> Package: linux-2.6
> Version: 2.6.32-30

dunno how those pkg name & version came out, I was referring to
linux-image-2.6.32-5-amd64

> File: /usr/share/bug/linux-image-2.6.32-5-amd64/include-network


-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



-- 
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/capdtaj0+nwbpd86rwsgwgazxbi+mhqsuueohxdht9wjicwj...@mail.gmail.com

Bug#637284: Can't install wheezy on a 2011 iMac

[Mike Hore]

Hi again Jonathan,


> Hmmm - interesting.  I might check Ubuntu forums too.

The same problem has shown up there too:

http://ubuntuforums.org/showthread.php?t=1578342

Some fixes have been posted on that thread.  I can't really take the 
time to apply them all myself, but it probably suggests a way forward.


My suggestion would be for this bug to stand until a fix has been rolled 
into a new installer, so that we can do a straightforward installation 
on these machines.  Hopefully this can be done.


Cheers,  Mike.

---
  Mike Horemike_h...@aapt.net.au
---



--
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/4e537deb.10...@aapt.net.au

Bug#638956: include-network bug script doesn't work in case of bonding

[Sandro Tosi]

Package: linux-2.6
Version: 2.6.32-30
Severity: minor
File: /usr/share/bug/linux-image-2.6.32-5-amd64/include-network

include-network does a 

 for dir in /sys/class/net/*; do
  ...
  cat "$dir"/features >&3

but when bonding is active, there's also a file 'bonding_masters' under
/sys/class/net/ and so the 'cat' fails. I've just replaced that line with

  [ -f "$dir"/features ] && cat "$dir"/features >&3

and it works.

Cheers,
Sandro


-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages linux-image-2.6.32-5-amd64 depends on:
ii  debconf [debconf 1.5.37  Debian configuration management sy
ii  initramfs-tools  0.98.7  tools for generating an initramfs
ii  linux-base   2.6.37-1~experimental.1 Linux image base package
ii  module-init-tool 3.12-1  tools for managing Linux kernel mo

Versions of packages linux-image-2.6.32-5-amd64 recommends:
ii  firmware-linux-f 2.6.37-1~experimental.1 Binary firmware for various driver

Versions of packages linux-image-2.6.32-5-amd64 suggests:
pn  grub | lilo(no description available)
pn  linux-doc-2.6.32   (no description available)

Versions of packages linux-image-2.6.32-5-amd64 is related to:
pn  firmware-bnx2  (no description available)
pn  firmware-bnx2x (no description available)
pn  firmware-ipw2x00   (no description available)
pn  firmware-ivtv  (no description available)
ii  firmware-iwlwifi  0.28   Binary firmware for Intel Wireless
ii  firmware-linux0.28   Binary firmware for various driver
ii  firmware-linux-nonfree0.28   Binary firmware for various driver
pn  firmware-qlogic(no description available)
pn  firmware-ralink(no description available)
pn  xen-hypervisor (no description available)

-- debconf information excluded



-- 
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/20110823101552.9175.75576.report...@sandrotosi.register.it

Bug#637284: Can't install wheezy on a 2011 iMac

[Mike Hore]

Hi Jonathan,


Mike Hore wrote:


I don't know that I want to try any more -- I seem to be getting nowhere.  I
think it might need someone who really understands the Debian boot process
to get their hands on a new iMac and sort this whole thing out.  There are
plenty of them around by now.  I've got a lot of other things on my plate
and this isn't a high priority for me.


Might also be worth asking on debian-u...@lists.debian.org if anyone has
tried installing on a 2011 iMac.


I did earlier on -- I got no replies for over a week even though I 
followed up my own posts several times.  I concluded nobody else had 
even tried at that stage.  I might give it a month and then try again.





Sorry for the trouble and thanks for testing.  As you saw with e.g.
the "co" bug, we're not at a stage in the release cycle when the
installer is completely polished yet.  So at the moment, using the
squeeze installer and then upgrading is more likely to be reliable.


That was the first thing I tried a while ago -- then somebody suggested 
I try the latest installer which is what I did.




If you do get a working installation, I would still be very interested
in tracking down the radeon modesetting trouble (e.g., by taking a
snapshot of the screen with artifacts and recovering any log entries
that appear before then).  I suspect the cause is similar to
Bug#637943 (modesetting not working correctly without
firmware-linux-nonfree installed).


Hmmm - interesting.  I might check Ubuntu forums too.  But I'm not in a 
particular hurry -- I've just installed MacOSX 10.7 (Lion) and I've got 
heaps of other things to keep busy with  :-)


Cheers,  Mike.


---
  Mike Horemike_h...@aapt.net.au
---



--
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/4e537548.2080...@aapt.net.au

Bug#638913: linux-source-3.0.0: cpu frequency speedstep_centrino Intel(R) Pentium(R) M processor

[Bjørn Mork]

Grzegorz Kochański  writes:

>> It works on my T42 with the 1.8 GHz version of this processor, using
>> lenny, squeeze and sid kernel versions.  The BIOS version is 3.05a.
>> Maybe there was a regression in a later BIOS version?
>>
>> Ben.
>>
>>
>> I have applied the newest BIOS version available at lenovo support for my
> T42 (model 2374):
> BIOS Version   3.23 (1RETDRWW)
> BIOS Date   2007-06-18
> Embedded Controller Version 3.03

Please see 

 
http://support.lenovo.com/en_US/downloads/detail.page?&LegacyDocID=MIGR-50273#summary

which says

 "Note: This BIOS version will only work with Embedded Controller
  Program Version 3.04 (or higher)."

This may explain your issues unless the values above are a result of a
typo.


Bjørn



--
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/87ei0cblj7@nemi.mork.no

Bug#638938: linux-tools-3.0.0: "perf report" segfaults when using binary version; compiling from source works

[Jonathan Nieder]

Hi Justin,

Justin Santa Barbara wrote:

> I captured a few perf traces on a live system (using "perf record --event
> cpu-clock --freq 1000 -a --output=mylog.perf").
>
> When I try to run a report on those perf logs, it segfaults.  I can run it
> under gdb and get a stacktrace (below).

I wasn't able to reproduce it, alas.  (Neither with 3.0.0-1 nor
3.0.0-2.)

> If I install the linux-source package, expand it, and do a "make" in
> tools/perf, then that version of perf works (no segfault).

Please try building with HAVE_CPLUS_DEMANGLE=YesPlease, to get a
backtrace without so many frames missing.  It might be that this is
fixed in sid already, since 3.0.0-2 was built against a version of
binutils-dev with some newish NULL checking fixes in cplus_demangle().



-- 
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/20110823073938.ga16...@elie.gateway.2wire.net

Bug#638913: linux-source-3.0.0: cpu frequency speedstep_centrino Intel(R) Pentium(R) M processor

[Grzegorz Kochański]

> It works on my T42 with the 1.8 GHz version of this processor, using
> lenny, squeeze and sid kernel versions.  The BIOS version is 3.05a.
> Maybe there was a regression in a later BIOS version?
>
> Ben.
>
>
> I have applied the newest BIOS version available at lenovo support for my
T42 (model 2374):
BIOS Version   3.23 (1RETDRWW)
BIOS Date   2007-06-18
Embedded Controller Version 3.03
CPU TypeIntel(R) Pentium(R) M processr,
CPU Speed   1.53GHz

Changing BIOS setting from Slow to Max custom setting changes time between
"Grub loading." to "Welcome to GRUB!" from 15 to 5 cursor blinks :).
However, when system is loaded then mprime benchmark shows exactly the same
(SLOW) result regardless of BIOS setting.

System initiation changes the frequency to the lowest one.
Loading patched speedstep-centrino module causes mprime benchmark faster
results.

rgds
rumi

Bug#637284: Can't install wheezy on a 2011 iMac

[Jonathan Nieder]

Mike Hore wrote:

> I don't know that I want to try any more -- I seem to be getting nowhere.  I
> think it might need someone who really understands the Debian boot process
> to get their hands on a new iMac and sort this whole thing out.  There are
> plenty of them around by now.  I've got a lot of other things on my plate
> and this isn't a high priority for me.

Might also be worth asking on debian-u...@lists.debian.org if anyone has
tried installing on a 2011 iMac.

Sorry for the trouble and thanks for testing.  As you saw with e.g.
the "co" bug, we're not at a stage in the release cycle when the
installer is completely polished yet.  So at the moment, using the
squeeze installer and then upgrading is more likely to be reliable.

If you do get a working installation, I would still be very interested
in tracking down the radeon modesetting trouble (e.g., by taking a
snapshot of the screen with artifacts and recovering any log entries
that appear before then).  I suspect the cause is similar to
Bug#637943 (modesetting not working correctly without
firmware-linux-nonfree installed).



-- 
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/20110823072309.gh4...@elie.gateway.2wire.net

Bug#637284: Can't install wheezy on a 2011 iMac

[Mike Hore]

Hi again Jonathan,


Mike Hore wrote:


Ummm...  Mac keyboards don't have scroll lock!


It seems that scroll lock is shift+f14.


Nope, that has no effect whatsoever.




Yes, single WAS there!!  Let me double-check...

yes, what I said was what happened.  Both single and quiet were there. The
actual line printed was

Starting GNOME Display Manager: gdm3


Weird.  I have no idea what happened there.


Right.  Running again with "quiet" off, once it starts rapidly flashing 
messages without progressing, I was able to read these lines:


usb 2-1.4: usbfs: interface 2 claimed by usb-storage while 'usb' sets 
config #1


usb 2-1.4: usbfs: process 2008(usb) did not claim interface 0 before use

I have no idea what these lines mean.  The other flashing lines releated 
to eth0, but I didn't copy them down.




There should be entries from "recovery mode" in the boot menu, too,
with similar effect.  Maybe that's worth a try. :/
.


I don't know that I want to try any more -- I seem to be getting 
nowhere.  I think it might need someone who really understands the 
Debian boot process to get their hands on a new iMac and sort this whole 
thing out.  There are plenty of them around by now.  I've got a lot of 
other things on my plate and this isn't a high priority for me.


Cheers,  Mike.

---
  Mike Horemike_h...@aapt.net.au
---



--
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/4e53510a.3070...@aapt.net.au