Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)

2011-01-02 Thread Stephan Austermühle 
Hi Ian!

Am 02.01.2011 20:27, schrieb Ian Campbell:

> Did -28 work OK? Otherwise what was the last known good kernel?

The -29 kernel was the one that was installed when I've setup Squeeze.
So, there was never a different kernel on that system. Anyway... I can
try -28 and see what happens.

> The issue is in dom0, right?

Yes, it is a dom0 issue.

Best regards,

Stephan



-- 
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/4d217e92.7040...@hcsd.de

Bug#597658: linux-headers-2.6.32-5-amd64: Missing aesni-intel module in kernel

2011-01-02 Thread Ben Hutchings 
On Sun, 2011-01-02 at 21:30 -0700, dann frazier wrote:
> On Sun, Jan 02, 2011 at 08:57:19PM +, Ben Hutchings wrote:
[...]
> > Please can you test whether aesni-intel loads and works in:
> > 
> > 1. Package version 2.6.32-12
> > .  This was the
> > last version with aesni-intel included.
> > 
> > 2. Package version 2.6.32-29, modified to reenable aesni-intel.  See the
> > instructions at
> > .
> > a. Follow section 4.2.1.
> > b. Change '# CONFIG_CRYPTO_AES_NI_INTEL is not set' to
> >'CONFIG_CRYPTO_AES_NI_INTEL=m' in
> >debian/config/kernelarch-x86/config-arch-64.
> > c. Follow section 4.2.4.
> 
> fyi, 2.6.32-12 & 2.6.32-29 w/ CONFIG_CRYPTO_AES_NI_INTEL=m both boot
> successfully w/ the aesni_intel module on my Lenovo T410.

I'm guessing you don't have an AES-encrypted hard drive though...

Ben.

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


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

Bug#597658: linux-headers-2.6.32-5-amd64: Missing aesni-intel module in kernel

2011-01-02 Thread dann frazier 
On Sun, Jan 02, 2011 at 08:57:19PM +, Ben Hutchings wrote:
> On Sun, 2011-01-02 at 20:41 +0100, cfchris6 wrote:
> > What has to be done until the proposed solution to blacklist the module 
> > could
> > be implemented?
> > 
> > I do think that it is not very nice to have a big part of those with a newer
> > amd64 box unable to use this functionality.
> > 
> > If I get it correctly, the main reason for the decision to disable that 
> > module
> > is that it's not playing nice with a T400. What is the number of the bug 
> > report
> > with upstream on that matter?
> 
> I don't know of one.  There is a Fedora bug report
>  and if I read that
> correctly then this is not a model-specific bug - the module was
> actually completely broken in 2.6.32 if CONFIG_CRYPTO_FIPS=y (which it
> is in Debian packages).  However, it also looks like this was fixed in
> 2.6.32.19, which is incorporated in the source for the current package.
> 
> Please can you test whether aesni-intel loads and works in:
> 
> 1. Package version 2.6.32-12
> .  This was the
> last version with aesni-intel included.
> 
> 2. Package version 2.6.32-29, modified to reenable aesni-intel.  See the
> instructions at
> .
> a. Follow section 4.2.1.
> b. Change '# CONFIG_CRYPTO_AES_NI_INTEL is not set' to
>'CONFIG_CRYPTO_AES_NI_INTEL=m' in
>debian/config/kernelarch-x86/config-arch-64.
> c. Follow section 4.2.4.

fyi, 2.6.32-12 & 2.6.32-29 w/ CONFIG_CRYPTO_AES_NI_INTEL=m both boot
successfully w/ the aesni_intel module on my Lenovo T410.



-- 
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/20110103043033.ga2...@dannf.org

Bug#607495: linux-image-2.6.32-5-amd64: kernel freeze

2011-01-02 Thread Philip Ashmore 

Timo Juhani Lindfors wrote:

Philip Ashmore  writes:

I'd recommend also attaching your hardware information, or trying it


Not sure how much this matters under xen really but the cpuinfo in dom0 has
What I really meant was your hardware device info. I can reproduce this 
bug on Lenny

running the same kernel and on Ubuntu it manifests itself as

  system instability caused by unprivileged program
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/692100

that appears to indicate that it might have something to do with the 
kernel drivers.


Philip






--
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/4d2123c3.1010...@philipashmore.com

Bug#602078: marked as done (linux-image-2.6.36-trunk-amd64: Wake-up does a full restart !)

2011-01-02 Thread Debian Bug Tracking System 
Your message dated Sun, 02 Jan 2011 23:30:48 +
with message-id <1294011048.3167.134.ca...@localhost>
and subject line Re: Bug#602078: linux-image-2.6.36-trunk-amd64: Wake-up does a 
full restart !
has caused the Debian Bug report #602078,
regarding linux-image-2.6.36-trunk-amd64: Wake-up does a full restart !
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.)


-- 
602078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.36-1~experimental.1
Severity: grave
Justification: causes non-serious data loss

Hi,

This is happening since the 2.6.35 from experimental (regression in power
managment code ?).

Most of the time (about 80%), if the system goes to standby mode, when I want
to turn it back in normal mode, a full reboot happen !

No log, nothing special !

I don't know how to trace that problem, but it is running well into 2.6.34
kernel.

Regards

Mourad



-- Package-specific info:
** Version:
Linux version 2.6.36-trunk-amd64 (Debian 2.6.36-1~experimental.1) 
(m...@stro.at) (gcc version 4.4.5 (Debian 4.4.5-5) ) #1 SMP Wed Oct 27 14:28:29 
UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.36-trunk-amd64 
root=UUID=18d08a71-e5e2-4847-bb6d-fbe434787ced ro quiet

** Tainted: PC (1025)
 * Proprietary module has been loaded.
 * Module from drivers/staging has been loaded.

** Kernel log:
[   17.569415] Bluetooth: RFCOMM TTY layer initialized
[   17.569419] Bluetooth: RFCOMM socket layer initialized
[   17.569420] Bluetooth: RFCOMM ver 1.11
[   18.685286] sshd (1836): /proc/1836/oom_adj is deprecated, please use 
/proc/1836/oom_score_adj instead.
[   18.735042] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   18.740235] sky2 :04:00.0: eth0: enabling interface
[   18.740852] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   23.085146] lp: driver loaded but no devices found
[   23.287475] ppdev: user-space parallel port driver
[   30.260962] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[   30.260966] vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the 
hardware performance
[   30.260967] vboxdrv: counter framework which can generate NMIs is active. 
You have to prevent
[   30.260968] vboxdrv: the usage of hardware performance counters by
[   30.260969] vboxdrv:   echo 2 > /proc/sys/kernel/perf_counter_paranoid
[   30.260972] vboxdrv: Found 4 processor cores.
[   30.261181] VBoxDrv: dbg - g_abExecMemory=a10821c0
[   30.261250] vboxdrv: fAsync=0 offMin=0x27c offMax=0x2895
[   30.261422] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 
'normal'.
[   30.261424] vboxdrv: Successfully loaded version 3.2.10 (interface 
0x00140001).
[   52.833902] CPUFREQ: Per core ondemand sysfs interface is deprecated - 
up_threshold
[   54.388550] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   77.417016] hda-intel: IRQ timing workaround is activated for card #1. 
Suggest a bigger bdl_pos_adj.
[   91.598149] usb 2-1.5: new high speed USB device using ehci_hcd and address 3
[   91.692340] usb 2-1.5: New USB device found, idVendor=0bda, idProduct=8174
[   91.692343] usb 2-1.5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[   91.692345] usb 2-1.5: Product: RTL8192S WLAN Adapter 
[   91.692347] usb 2-1.5: Manufacturer: Manufacturer Realtek 
[   91.692349] usb 2-1.5: SerialNumber: 00e04c01
[   91.740315] r8192s_usb: module is from the staging directory, the quality is 
unknown, you have been warned.
[   91.743324] ieee80211_crypt: registered algorithm 'NULL'
[   91.743326] ieee80211_crypt: registered algorithm 'TKIP'
[   91.743327] ieee80211_crypt: registered algorithm 'CCMP'
[   91.743328] ieee80211_crypt: registered algorithm 'WEP'
[   91.743330] 
[   91.743330] Linux kernel driver for RTL8192 based WLAN cards
[   91.743331] Copyright (c) 2007-2008, Realsil Wlan
[   91.743436] ==>ep_num:4, in_ep_num:1, out_ep_num:3
[   91.743437] ==>RtInPipes:3  
[   91.743438] ==>RtOutPipes:4  6  13  
[   91.743440] ==>txqueue_to_outpipemap for BK, BE, VI, VO, HCCA, TXCMD, MGNT, 
HIGH, BEACON:
[   91.743442] 1  1  0  0  2  2  2  2  2  
[   91.938597] usbcore: registered new interface driver rtl819xU
[   92.928163] rtl819xU:FirmwareRequest92S(): signature: 8192, version: 902b, 
size: 30, imemsize: 7408, sram size: 9688
[   92.929461] rtl819xU:FirmwareCheckReady(): LoadFWStatus(1), success
[   92.932954] rtl819xU:FirmwareCheckReady(): LoadFWStatus(2), success
[   92.933079] rtl819xU:FirmwareCheckReady(): DMEM code download success, 
CPUStatus(0x3f)
[   92.934329] rtl819xU:FirmwareC

Processed: bug 602078 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=23002

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

> forwarded 602078 https://bugzilla.kernel.org/show_bug.cgi?id=23002
Bug #602078 [linux-2.6] linux-image-2.6.36-trunk-amd64: Wake-up does a full 
restart !
Ignoring request to change the forwarded-to-address of bug#602078 to the same 
value
> thanks
Stopping processing here.

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

Processed: retitle 607879 to aufs: kernel BUG at .../mm/mmap.c:873

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

> retitle 607879 aufs: kernel BUG at .../mm/mmap.c:873
Bug #607879 [linux-2.6] System hangs up with mmap.c:873! 
Changed Bug title to 'aufs: kernel BUG at .../mm/mmap.c:873' from 'System hangs 
up with mmap.c:873! '
> thanks
Stopping processing here.

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

Processed: owner 607879

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

> owner 607879 debian-l...@lists.debian.org
Bug #607879 [linux-2.6] System hangs up with mmap.c:873! 
Owner recorded as debian-l...@lists.debian.org.
> thanks
Stopping processing here.

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

Bug#607879: System hangs up with mmap.c:873!

2011-01-02 Thread Ben Hutchings 
The Debian kernel team really doesn't like to support aufs; we include
it only to support Debian Live.  Therefore I'm passing this bug over to
the Debian Live maintainers.

Ben.

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


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

Processed: tagging 608185

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 608185 + pending
Bug #608185 [linux-2.6] btrfs-tools: balance tree action should be only 
triggered by root
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#599368: Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

2011-01-02 Thread Cesare Leonardi 

On 01/02/2011 11:51 PM, Ben Hutchings wrote:

Yes, I see, it doesn't say that this is a fatal error for watchdog
initialisation.


I've seen just now the patch (v1 and v2) you sent upstream: thank you 
very much for improving the error message and the documentation.


Very very appreciated.

Cesare.



--
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/4d21051b.10...@gmail.com

Bug#599368: [PATCH v2] watchdog: Improve initialisation error message and documentation

2011-01-02 Thread Ben Hutchings 
The error message 'NMI watchdog failed to create perf event...'  does
not make it clear that this is a fatal error for the watchdog.  It
also currently prints the error value as a pointer, rather than
extracting the error code with PTR_ERR().  Fix that.

Add a note to the description of the 'nowatchdog' kernel parameter to
associate it with this message.

Reported-by: Cesare Leonardi 
Signed-off-by: Ben Hutchings 
---
Further improved the error message based on Cesare's comments.

Ben.

 Documentation/kernel-parameters.txt |2 +-
 kernel/watchdog.c   |3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/kernel-parameters.txt 
b/Documentation/kernel-parameters.txt
index 7d0cead..6fc0cf4 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -1764,7 +1764,7 @@ and is between 256 and 4096 characters. It is defined in 
the file
 
nousb   [USB] Disable the USB subsystem
 
-   nowatchdog  [KNL] Disable the lockup detector.
+   nowatchdog  [KNL] Disable the lockup detector (NMI watchdog).
 
nowb[ARM]
 
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index d74e866..d7ebdf4 100644
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -366,7 +366,8 @@ static int watchdog_nmi_enable(int cpu)
goto out_save;
}
 
-   printk(KERN_ERR "NMI watchdog failed to create perf event on cpu%i: 
%p\n", cpu, event);
+   printk(KERN_ERR "NMI watchdog disabled for cpu%i: unable to create perf 
event: %ld\n",
+  cpu, PTR_ERR(event));
return PTR_ERR(event);
 
/* success path */
-- 
1.7.2.3





--
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/1294009362.3167.126.ca...@localhost

Bug#594561: State of the bug 594561

2011-01-02 Thread Ben Hutchings 
On Sun, 2010-12-26 at 15:42 +0100, Wenceslao González-Viñas wrote:
> Ok!, I did more or less the things you told me. I was not able to  
> patch the source in a standard way; but I changed the source code by  
> hand, I recompile the kernel and I used the resulting module with  
> insmod rt2870.ko ieee80211_regdom=EU
> 
> Please note that I did not reinstall compiled kernel (so I had to use  
> insmod instead your suggested modprobe) and that the module to use was  
> rt2870 (and not 2860). Of course I patched from 2860 folder since the  
> files were common.
> 
> Now it works perfect ! So, you were right !!! Many thanks!
> 
> My question now is how, and when this will become automatized in the  
> kernel which comes from the debian distribution ?

The module parameter will be added in the next version (2.6.32-30).

Note that in the release after 'squeeze' rt2870sta will be replaced with
a new driver 'rt2870usb' which uses the common Linux 802.11 support
code.  You will then need to specify the same parameter for the
'cfg80211' module instead (in fact, you can set that now in
preparation).

Ben.

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


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

Bug#599368: Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

2011-01-02 Thread Ben Hutchings 
On Sun, 2011-01-02 at 23:37 +0100, Cesare Leonardi wrote:
> On 01/02/2011 10:44 PM, Ben Hutchings wrote:
> >> Then add +1 to what Michael Biebl already asked: why that message should
> >> be showed?
> >
> > Because the watchdog feature was enabled at compile-time and you
> > presumably want it to work.  If you add 'nowatchdog' to the kernel
> > parameters then the kernel will not attempt to set up the watchdog, and
> > the error message will not appear.
> 
> Thanks, i didn't know that parameter, but i don't want to disable the 
> lockup detector.
> 
> I'm sure that kernel devels will find a better way to handle unsupported 
> hardware and the situation where the watchdog cannot be used (anyone 
> without a local APIC will see this message?).

So, hardly anyone.

>  From the user point of view, i think that the best is to handle 
> silently the unsupported case (at least in quiet boot) and to show a 
> meaningful message in the syslog. From the current message, if you are 
> not a kernel developer, it's not clear if it's a warning or an error 
> message. In other words, it's not clear if the watchdog will function or 
> not.

Yes, I see, it doesn't say that this is a fatal error for watchdog
initialisation.

Ben.

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


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

Processed: tagging 594561

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 594561 + pending
Bug #594561 [linux-2.6] firmware-ralink: fails to detect APs at frequency 
2.472GHz
Added tag(s) pending.
>
End of message, stopping processing here.

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

Processed: tagging 608698

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

> tags 608698 + moreinfo
Bug #608698 [linux-2.6] linux-image-2.6.37-rc7-686: suspend/hibernate fails 
with "pnp_bus_suspend+0x0/0x57 returns -5"
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#599368: Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

2011-01-02 Thread Cesare Leonardi 

On 01/02/2011 10:44 PM, Ben Hutchings wrote:

Then add +1 to what Michael Biebl already asked: why that message should
be showed?


Because the watchdog feature was enabled at compile-time and you
presumably want it to work.  If you add 'nowatchdog' to the kernel
parameters then the kernel will not attempt to set up the watchdog, and
the error message will not appear.


Thanks, i didn't know that parameter, but i don't want to disable the 
lockup detector.


I'm sure that kernel devels will find a better way to handle unsupported 
hardware and the situation where the watchdog cannot be used (anyone 
without a local APIC will see this message?).
From the user point of view, i think that the best is to handle 
silently the unsupported case (at least in quiet boot) and to show a 
meaningful message in the syslog. From the current message, if you are 
not a kernel developer, it's not clear if it's a warning or an error 
message. In other words, it's not clear if the watchdog will function or 
not.


Ciao.

Cesare.



--
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/4d20fe3f.8010...@gmail.com

Bug#608698: linux-image-2.6.37-rc7-686: suspend/hibernate fails with "pnp_bus_suspend+0x0/0x57 returns -5"

2011-01-02 Thread Ben Hutchings 
On Sun, 2011-01-02 at 00:15 +0100, Willi Mann wrote:
> Package: linux-2.6
> Version: 2.6.37~rc7-1~experimental.1
> Severity: normal
> 
> 
> After a few hibernate cycles, I can no longer suspend/hibernate my thinkpad 
> T500. It fails with mentioned error - see the attached logs. 
> 
> Additionally, my external cherry USB keyboard (plugged in the Docking 
> Station) 
> failed to work after the first failed hibernate attempt. However, unplugging
> and replugging solved this problem.  
> 
> This is the second time that hibernation fails with 2.6.37-rc?, and the error 
> message in dmesg is the same (... error -5) so this seems reproducable. 
> 
> I can't test earlier kernels because up to 2.6.36, I had memory corruption
> problems after wake-up from hibernate.

This may be fixed in Debian's 2.6.32 now as we have applied several
fixes originally made in later versions.

> In fact I'm quite happy that it
> works now at least for a few cycles, but I'd like to get back to the state 
> before Kernel Mode Setting where i had an "uptime" of 180 days with at least
> one hibernate cycle daily.
[...]

If you don't use the parallel port, you may be able to work around this
by blacklisting the 'parport_pc' module.

I see several reports of this against other distributions, but no sign
of it being tracked down or fixed.  Therefore, please report it upstream
at  under product 'ACPI', component
'Power-Other'.

Ben.

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


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

Processed: unarchiving 599368

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

> unarchive 599368
Bug #599368 {Done: Ben Hutchings } [linux-2.6] NMI 
watchdog failed to create perf event on cpu0: ffa1
Unarchived Bug 599368
> thanks
Stopping processing here.

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

Bug#608138: [PATCH] watchdog: Improve failure message and documentation

2011-01-02 Thread Ben Hutchings 
The error message 'NMI watchdog failed to create perf event...'
currently prints the error value as a pointer, rather than extracting
the error code with PTR_ERR().  Fix that.

Add a note about the 'nowatchdog' kernel parameter to associate it
with this message.

Signed-off-by: Ben Hutchings 
---
 Documentation/kernel-parameters.txt |2 +-
 kernel/watchdog.c   |3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/kernel-parameters.txt 
b/Documentation/kernel-parameters.txt
index 7d0cead..6fc0cf4 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -1764,7 +1764,7 @@ and is between 256 and 4096 characters. It is defined in 
the file
 
nousb   [USB] Disable the USB subsystem
 
-   nowatchdog  [KNL] Disable the lockup detector.
+   nowatchdog  [KNL] Disable the lockup detector (NMI watchdog).
 
nowb[ARM]
 
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index d74e866..5b44d2c 100644
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -366,7 +366,8 @@ static int watchdog_nmi_enable(int cpu)
goto out_save;
}
 
-   printk(KERN_ERR "NMI watchdog failed to create perf event on cpu%i: 
%p\n", cpu, event);
+   printk(KERN_ERR "NMI watchdog failed to create perf event on cpu%i: 
%ld\n",
+  cpu, PTR_ERR(event));
return PTR_ERR(event);
 
/* success path */
-- 
1.7.2.3




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

Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

2011-01-02 Thread Ben Hutchings 
On Wed, 2010-12-29 at 21:34 +0100, Cesare Leonardi wrote:
> On 12/27/2010 09:36 PM, Cesare Leonardi wrote:
> > Grub command lines are identical except that "lapic hpet=force" in
> > normal boot is substituted by "single" in recovery mode.
> 
> I've found that if i remove "lapic" from the command line, then the NMI 
> error appears. And in fact that paramter it's not present in recovery mode.
> In my laptop, lapic has to be used (as told in kernel logs) because it 
> is disabled by BIOS.
> 
> Googling around i've learned that NMI watchdog needs a local APIC and 
> that explain the error message. Even if the exact meaning of that 
> message is obscure to me yet.
> 
> Feel free to mark this bug as a duplicate of #599368 and close it.
> Then add +1 to what Michael Biebl already asked: why that message should 
> be showed?

Because the watchdog feature was enabled at compile-time and you
presumably want it to work.  If you add 'nowatchdog' to the kernel
parameters then the kernel will not attempt to set up the watchdog, and
the error message will not appear.

Ben.

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


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

Processed: tagging 608278

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

> tags 608278 + moreinfo
Bug #608278 [linux-2.6] linux-image-2.6.32-5-amd64: Random general protection 
faults at boot
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#608278: linux-image-2.6.32-5-amd64: Random general protection faults at boot

2011-01-02 Thread Ben Hutchings 
On Thu, 2010-12-30 at 10:08 +0100, Andrea Spadaccini wrote:
> Hi,
> 
> >> Justification: breaks the whole system
> >
> > This does *not* break the whole system - the package works for other
> > people and even you are able to reboot into another kernel version.
> 
> Sorry, I misinterpreted the options.
> 
> [cut]
> 
> >> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [] ? 
> >> usb_control_msg+0x124/0x135 [usbcore]
> >> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [] ? 
> >> finish_task_switch+0x3a/0xaf
> >> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [] ? 
> >> rtl818x_ioread8+0x61/0x7e [rtl8187]
> >> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [] ? 
> >> rtl8187_is_radio_enabled+0x24/0xc0 [rtl8187]
> >> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [] ? 
> >> rtl8187_rfkill_poll+0x25/0x78 [rtl8187]
> > [...]
> >
> > This is presumably caused by a bug in rtl8187.  However, it is not a
> > general protection fault so there may be two different bugs here.
> 
> Yes, the GPF is around sec 30. After that bug, I blacklisted rtl8187, 
> and resulted in the other GPFs at boot time that are not logged.

Can you try blacklisting the radeon driver?

Ben.

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


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

Processed: tagging 607495

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

> tags 607495 + unreproducible
Bug #607495 [linux-2.6] linux-image-2.6.32-5-amd64: kernel freeze
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#597658: linux-headers-2.6.32-5-amd64: Missing aesni-intel module in kernel

2011-01-02 Thread Ben Hutchings 
On Sun, 2011-01-02 at 20:41 +0100, cfchris6 wrote:
> What has to be done until the proposed solution to blacklist the module could
> be implemented?
> 
> I do think that it is not very nice to have a big part of those with a newer
> amd64 box unable to use this functionality.
> 
> If I get it correctly, the main reason for the decision to disable that module
> is that it's not playing nice with a T400. What is the number of the bug 
> report
> with upstream on that matter?

I don't know of one.  There is a Fedora bug report
 and if I read that
correctly then this is not a model-specific bug - the module was
actually completely broken in 2.6.32 if CONFIG_CRYPTO_FIPS=y (which it
is in Debian packages).  However, it also looks like this was fixed in
2.6.32.19, which is incorporated in the source for the current package.

Please can you test whether aesni-intel loads and works in:

1. Package version 2.6.32-12
.  This was the
last version with aesni-intel included.

2. Package version 2.6.32-29, modified to reenable aesni-intel.  See the
instructions at
.
a. Follow section 4.2.1.
b. Change '# CONFIG_CRYPTO_AES_NI_INTEL is not set' to
   'CONFIG_CRYPTO_AES_NI_INTEL=m' in
   debian/config/kernelarch-x86/config-arch-64.
c. Follow section 4.2.4.

Ben.

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


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

Bug#597658: linux-headers-2.6.32-5-amd64: Missing aesni-intel module in kernel

2011-01-02 Thread cfchris6 
What has to be done until the proposed solution to blacklist the module could
be implemented?

I do think that it is not very nice to have a big part of those with a newer
amd64 box unable to use this functionality.

If I get it correctly, the main reason for the decision to disable that module
is that it's not playing nice with a T400. What is the number of the bug report
with upstream on that matter?

Best Regards,
Christian Franke



-- 
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/20110102194127.gb19...@ts2server.com

Bug#608144: linux-image-2.6.32-5-xen-amd64: Kernel oops: net/core/dev.c:1582 skb_gso_segment+0x109/0x263() (Bug #596802 reappeared)

2011-01-02 Thread Ian Campbell 
Hi Stephan,

Thanks for the report.

On Mon, 2010-12-27 at 22:14 +0100, Stephan Austermühle wrote: 
> Package: linux-2.6
> Version: 2.6.32-29
> Severity: important
> 
> The bug reported in #596802 seems to have reappeared in kernel 2.6.32-29.

Did -28 work OK? Otherwise what was the last known good kernel?

The issue is in dom0, right?

> Problem arises when network traffic starts in freshly started HVM
> domain (W2k8R2, Citrix WHQL drivers). I've already upgraded the e1000e
> module from the one in the Debian package to the lastest available
> Intel driver (problem persists). 
> 
> Since I have setup this system as a Xen testing system to find various
> other issues I can do additional tests if needed.

Ian.
-- 
Ian Campbell

Do what you can to prolong your life, in the hope that someday you'll
learn what it's for.


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

Bug#608698: linux-image-2.6.37-rc7-686: suspend/hibernate fails with "pnp_bus_suspend+0x0/0x57 returns -5"

2011-01-02 Thread Willi Mann 
Package: linux-2.6
Version: 2.6.37~rc7-1~experimental.1
Severity: normal


After a few hibernate cycles, I can no longer suspend/hibernate my thinkpad 
T500. It fails with mentioned error - see the attached logs. 

Additionally, my external cherry USB keyboard (plugged in the Docking Station) 
failed to work after the first failed hibernate attempt. However, unplugging
and replugging solved this problem.  

This is the second time that hibernation fails with 2.6.37-rc?, and the error 
message in dmesg is the same (... error -5) so this seems reproducable. 

I can't test earlier kernels because up to 2.6.36, I had memory corruption
problems after wake-up from hibernate. In fact I'm quite happy that it
works now at least for a few cycles, but I'd like to get back to the state 
before Kernel Mode Setting where i had an "uptime" of 180 days with at least
one hibernate cycle daily.


-- Package-specific info:
** Version:
Linux version 2.6.37-rc7-686 (Debian 2.6.37~rc7-1~experimental.1) 
(b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-10) ) #1 SMP Sun Dec 26 
18:21:15 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.37-rc7-686 
root=UUID=03db9303-638d-4e66-94c9-4e72f668620e ro

** Not tainted

** Kernel log:
[143686.861383] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[143687.120060] usb 1-5.1: device not accepting address 11, error -32
[143687.120415] usb 1-5.1: USB disconnect, address 11
[143687.260178] usb 1-5.1: new low speed USB device using ehci_hcd and address 
12
[143687.348172] usb 1-5.1: device descriptor read/64, error -32
[143687.540160] usb 1-5.1: device descriptor read/64, error -32
[143687.704075] device eth0 entered promiscuous mode
[143687.716173] usb 1-5.1: new low speed USB device using ehci_hcd and address 
13
[143687.804161] usb 1-5.1: device descriptor read/64, error -32
[143687.996169] usb 1-5.1: device descriptor read/64, error -32
[143688.172181] usb 1-5.1: new low speed USB device using ehci_hcd and address 
14
[143688.580060] usb 1-5.1: device not accepting address 14, error -32
[143688.652167] usb 1-5.1: new low speed USB device using ehci_hcd and address 
15
[143689.060057] usb 1-5.1: device not accepting address 15, error -32
[143689.060203] hub 1-5:1.0: unable to enumerate USB device on port 1
[143692.705890] device eth0 left promiscuous mode
[143697.552092] eth0: no IPv6 routers present
[143702.692585] tun0: Disabled Privacy Extensions
[143707.191394] tun1: Disabled Privacy Extensions
[143766.724956] PM: Hibernation mode set to 'shutdown'
[143766.791206] PM: Marking nosave pages: 0009e000 - 0010
[143766.793731] PM: Basic memory bitmaps created
[143766.796654] PM: Syncing filesystems ... done.
[143766.837539] Freezing user space processes ... (elapsed 0.01 seconds) done.
[143766.854437] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) 
done.
[143766.870460] PM: Preallocating image memory... done (allocated 296284 pages)
[143767.049769] PM: Allocated 1185136 kbytes in 0.17 seconds (6971.38 MB/s)
[143767.052125] Suspending console(s) (use no_console_suspend to debug)
[143767.056119] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[143767.092060] ACPI handle has no context!
[143767.092070] parport_pc 00:0b: disable failed
[143767.092079] legacy_suspend(): pnp_bus_suspend+0x0/0x57 returns -5
[143767.092082] PM: Device 00:0b failed to freeze: error -5
[143767.131542] sd 0:0:0:0: [sda] Starting disk
[143767.345639] PM: restore of devices complete after 214.252 msecs
[143767.362683] Restarting tasks ... done.
[143767.367665] PM: Basic memory bitmaps freed
[143767.370174] video LNXVIDEO:00: Restoring backlight state
[143767.408193] netconsole: network logging stopped, interface tun1 unregistered
[143767.436155] usb 1-5.1: new low speed USB device using ehci_hcd and address 
16
[143767.464098] netconsole: network logging stopped, interface tun0 unregistered
[143767.526067] usb 1-5.1: device descriptor read/64, error -32
[143767.720123] usb 1-5.1: device descriptor read/64, error -32
[143767.896124] usb 1-5.1: new low speed USB device using ehci_hcd and address 
17
[143767.984135] usb 1-5.1: device descriptor read/64, error -32
[143768.180134] usb 1-5.1: device descriptor read/64, error -32
[143768.356134] usb 1-5.1: new low speed USB device using ehci_hcd and address 
18
[143768.736416] e1000e :00:19.0: irq 44 for MSI/MSI-X
[143768.764057] usb 1-5.1: device not accepting address 18, error -32
[143768.792131] e1000e :00:19.0: irq 44 for MSI/MSI-X
[143768.792598] ADDRCONF(NETDEV_UP): eth0: link is not ready
[143768.836185] usb 1-5.1: new low speed USB device using ehci_hcd and address 
19
[143769.244046] usb 1-5.1: device not accepting address 19, error -32
[143769.244197] hub 1-5:1.0: unable to enumerate USB device on port 1
[143770.356947] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: 
RX/TX
[143770.356965] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO
[143770.357394] ADDRCONF(NETDEV_CHANGE): eth0: link becom

Processed: Re: Bug#608538: btrfs root installation results in initramfs busybox prompt

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

> reassign 608538 btrfs-tools
Bug #608538 [initramfs-tools] btrfs root installation results in initramfs 
busybox prompt
Bug #602254 [initramfs-tools] initramfs-tools: [lib]crc32c* modules handling
Bug reassigned from package 'initramfs-tools' to 'btrfs-tools'.
Bug reassigned from package 'initramfs-tools' to 'btrfs-tools'.
Bug No longer marked as found in versions initramfs-tools/0.98.5.
Bug No longer marked as found in versions initramfs-tools/0.98.5.
> retitle 608538 Didn't include required module in initramfs
Bug #608538 [btrfs-tools] btrfs root installation results in initramfs busybox 
prompt
Bug #602254 [btrfs-tools] initramfs-tools: [lib]crc32c* modules handling
Changed Bug title to 'Didn't include required module in initramfs' from 'btrfs 
root installation results in initramfs busybox prompt'
Changed Bug title to 'Didn't include required module in initramfs' from 
'initramfs-tools: [lib]crc32c* modules handling'
> thanks
Stopping processing here.

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

Bug#608538: btrfs root installation results in initramfs busybox prompt

2011-01-02 Thread Otavio Salvador 
reassign 608538 btrfs-tools
retitle 608538 Didn't include required module in initramfs
thanks

On Sat, Jan 1, 2011 at 09:06, Aron Xu  wrote:
> No, nothing. But I truly only get an initramfs prompt.

It looks to be a btrfs-tools hook issue.

Reassigning it.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



--
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/aanlktimtu9xi7f5yq9puwkbqvcuv2ozbmk0pdrnxh...@mail.gmail.com

Bug#608684: linux-2.6: [INTL:sk] Slovak po-debconf translation

2011-01-02 Thread Slavko 
Package: linux-2.6
Severity: wishlist
Tags: l10n patch
Version: 2.6.32-29

sk.po attached

regards
Slavko

-- 
Slavko
http://slavino.sk
# Slovak translations for linux-2.6 package
# Slovenské preklady pre balík linux-2.6.
# Copyright (C) 2011 THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the linux-2.6 package.
# Slavko , 2011.
#
msgid ""
msgstr ""
"Project-Id-Version: linux-2.6 2.6.32-29\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2010-12-11 10:35+0100\n"
"PO-Revision-Date: 2011-01-02 18:11+0100\n"
"Last-Translator: Slavko \n"
"Language-Team: Slovak \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: sk\n"
"Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n"

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid "Update disk device IDs in system configuration?"
msgstr "Aktualizovať ID diskových zariadení v nastavení systému?"

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid ""
"The new Linux kernel version provides different drivers for some PATA (IDE) "
"controllers. The names of some hard disk, CD-ROM, and tape devices may "
"change."
msgstr ""
"Nová verzia Linuxového jadra poskytuje iné ovládače niektorých radičov PATA "
"(IDE). Názvy niektorých pevných diskov, CD-ROM a páskových mechaník sa môžu "
"zmeniť."

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid ""
"It is now recommended to identify disk devices in configuration files by "
"label or UUID (unique identifier) rather than by device name, which will "
"work with both old and new kernel versions."
msgstr ""
"V súčasnosti je odporúčané identifikovať diskové zariadenia v konfiguračných "
"súboroch pomocou ich menovky alebo UUID (jedinečný identifikátor), namiesto "
"mena zariadenia, ktoré je funkčné ako so starými, tak i s novými verziami "
"jadra."

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid ""
"If you choose to not update the system configuration automatically, you must "
"update device IDs yourself before the next system reboot or the system may "
"become unbootable."
msgstr ""
"Ak si vyberiete neaktualizovať nastavenia systému automaticky, musíte ID "
"zaradení upraviť manuálne, ešte pred nasledujúcim reštartom systému, inak sa "
"systém nemusí zaviesť."

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:3001 ../linux-base.templates:4001
msgid "Apply configuration changes to disk device IDs?"
msgstr "Použiť zmeny nastavenia ID diskových zariadení?"

#. Type: boolean
#. Description
#: ../linux-base.templates:3001
msgid "These devices will be assigned UUIDs or labels:"
msgstr "Týmto zariadeniam bude priradené UUID alebo menovka:"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:3001 ../linux-base.templates:4001
msgid "These configuration files will be updated:"
msgstr "Tieto konfiguračné súbory budú aktualizované:"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:3001 ../linux-base.templates:4001
msgid "The device IDs will be changed as follows:"
msgstr "ID zariadení budú zmenené takto:"

#. Type: error
#. Description
#: ../linux-base.templates:5001
msgid "Configuration files still contain deprecated device names"
msgstr "Konfiguračné súbory stále obsahujú zastarané mená zariadení"

#. Type: error
#. Description
#: ../linux-base.templates:5001
msgid ""
"The following configuration files still use some device names that may "
"change when using the new kernel:"
msgstr ""
"Nasledujúce konfiguračné súbory stále používajú mená zariadení, ktoré asi "
"bude treba pri použití nového jadra zmeniť:"

#. Type: error
#. Description
#: ../linux-base.templates:6001
msgid "Boot loader configuration check needed"
msgstr "Je nutná kontrola nastavenia zavádzača"

#. Type: error
#. Description
#: ../linux-base.templates:6001
msgid ""
"The boot loader configuration for this system was not recognized. These "
"settings in the configuration may need to be updated:"
msgstr ""
"Nastavenie zavádzača tohoto systému nebolo rozpoznané. Tieto nastavenia v "
"konfigurácii asi bude treba aktualizovať:"

#. Type: error
#. Description
#: ../linux-base.templates:6001
msgid ""
" * The root device ID passed as a kernel parameter;\n"
" * The boot device ID used to install and update the boot loader."
msgstr ""
" * ID koreňového zariadenia predané ako parameter jadra;\n"
" * ID zavádzacieho zariadenia, použitého na inštaláciu a aktualizáciu "
"zavádzača."

#. Type: error
#. Description
#: ../linux-base.templates:6001
msgid ""
"You should generally identify these devices by UUID or label. However, on "
"MIPS systems the root device must be identified by name."
msgstr ""
"Tieto zariadenia by ste mali označovať ich UUID či menovkou. Na s

Bug#608250: To Ben Hutchings

2011-01-02 Thread Ian Campbell 
On Wed, 2010-12-29 at 14:51 +, Ben Hutchings wrote: 
> On Wed, 2010-12-29 at 15:13 +0100, Timothée GROS wrote:
> > Even in dom0 ? 
> 
> Yes - dom0 has access to most physical devices but *not* physical CPUs.
> 
> > How could i control my CPU speed then ?
> 
> That would have to be done in the Xen hypervisor, not the dom0 kernel.

Correct. I'm not that familiar with power-management under Xen but a
good reference appears to be http://wiki.xen.org/xenwiki/xenpm

(there is a configuration option where a unique dom0 VCPU is pinned to
each PCPU in a strict 1-1 mapping which allows regular Linux power
management to be used, I don't know how well supported this is though.
Normally the hypervisor based stuff would be recommended AFAIK)

Ian.

-- 
Ian Campbell

Badges?  We don't need no stinking badges.


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

Bug#598504: linux-kbuild: And now that we have linux-kbuild 2.6.36 kernel has moved to 2.6.37-rc

2011-01-02 Thread Michal Suchanek 
Package: linux-kbuild-2.6.36
Version: 2.6.36-1~experimental.1
Severity: normal
File: linux-kbuild


linux-kbuild version still lags behind kernel version.

Any progress on docs saying how to update it?


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (500, 'unstable'), (200, 
'experimental'), (111, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.36-rc6-r600fence-smbinit-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-kbuild-2.6.36 depends on:
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib

linux-kbuild-2.6.36 recommends no packages.

linux-kbuild-2.6.36 suggests no packages.

-- no debconf information



-- 
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/20110102140719.30673.90922.report...@optiplex960.ruk.cuni.cz

Bug#584784: [34-longterm 156/260] MIPS: Set io_map_base for several PCI bridges lacking it

2011-01-02 Thread Paul Gortmaker 
From: Ben Hutchings 

commit 8faf2e6c201d95b780cd3b4674b7a55ede6dcbbb upstream.

Several MIPS platforms don't set pci_controller::io_map_base for their
PCI bridges.  This results in a panic in pci_iomap().  (The panic is
conditional on CONFIG_PCI_DOMAINS, but that is now enabled for all PCI
MIPS systems.)

Signed-off-by: Ben Hutchings 
Cc: linux-m...@linux-mips.org
Cc: Martin Michlmayr 
Cc: Aurelien Jarno 
Cc: 584...@bugs.debian.org
Patchwork: https://patchwork.linux-mips.org/patch/1377/
Signed-off-by: Ralf Baechle 
Signed-off-by: Paul Gortmaker 
---
 arch/mips/mti-malta/malta-pci.c  |2 ++
 arch/mips/nxp/pnx8550/common/pci.c   |1 +
 arch/mips/nxp/pnx8550/common/setup.c |2 +-
 arch/mips/pci/ops-pmcmsp.c   |1 +
 arch/mips/pci/pci-yosemite.c |1 +
 5 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/arch/mips/mti-malta/malta-pci.c b/arch/mips/mti-malta/malta-pci.c
index 2fbfa1a..bf80921 100644
--- a/arch/mips/mti-malta/malta-pci.c
+++ b/arch/mips/mti-malta/malta-pci.c
@@ -247,6 +247,8 @@ void __init mips_pcibios_init(void)
iomem_resource.end &= 0xfULL;   /* 64 GB */
ioport_resource.end = controller->io_resource->end;
 
+   controller->io_map_base = mips_io_port_base;
+
register_pci_controller(controller);
 }
 
diff --git a/arch/mips/nxp/pnx8550/common/pci.c 
b/arch/mips/nxp/pnx8550/common/pci.c
index eee4f3d..98e86dd 100644
--- a/arch/mips/nxp/pnx8550/common/pci.c
+++ b/arch/mips/nxp/pnx8550/common/pci.c
@@ -44,6 +44,7 @@ extern struct pci_ops pnx8550_pci_ops;
 
 static struct pci_controller pnx8550_controller = {
.pci_ops= &pnx8550_pci_ops,
+   .io_map_base= PNX8550_PORT_BASE,
.io_resource= &pci_io_resource,
.mem_resource   = &pci_mem_resource,
 };
diff --git a/arch/mips/nxp/pnx8550/common/setup.c 
b/arch/mips/nxp/pnx8550/common/setup.c
index 2aed50f..64246c9 100644
--- a/arch/mips/nxp/pnx8550/common/setup.c
+++ b/arch/mips/nxp/pnx8550/common/setup.c
@@ -113,7 +113,7 @@ void __init plat_mem_setup(void)
PNX8550_GLB2_ENAB_INTA_O = 0;
 
/* IO/MEM resources. */
-   set_io_port_base(KSEG1);
+   set_io_port_base(PNX8550_PORT_BASE);
ioport_resource.start = 0;
ioport_resource.end = ~0;
iomem_resource.start = 0;
diff --git a/arch/mips/pci/ops-pmcmsp.c b/arch/mips/pci/ops-pmcmsp.c
index 04b3147..b7c03d8 100644
--- a/arch/mips/pci/ops-pmcmsp.c
+++ b/arch/mips/pci/ops-pmcmsp.c
@@ -944,6 +944,7 @@ static struct pci_controller msp_pci_controller = {
.pci_ops= &msp_pci_ops,
.mem_resource   = &pci_mem_resource,
.mem_offset = 0,
+   .io_map_base= MSP_PCI_IOSPACE_BASE,
.io_resource= &pci_io_resource,
.io_offset  = 0
 };
diff --git a/arch/mips/pci/pci-yosemite.c b/arch/mips/pci/pci-yosemite.c
index 0357946..cf5e1a2 100644
--- a/arch/mips/pci/pci-yosemite.c
+++ b/arch/mips/pci/pci-yosemite.c
@@ -54,6 +54,7 @@ static int __init pmc_yosemite_setup(void)
panic(ioremap_failed);
 
set_io_port_base(io_v_base);
+   py_controller.io_map_base = io_v_base;
TITAN_WRITE(RM9000x2_OCD_LKM7, TITAN_READ(RM9000x2_OCD_LKM7) | 1);
 
ioport_resource.end = TITAN_IO_SIZE - 1;
-- 
1.7.3.3




-- 
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/1293952756-15010-157-git-send-email-paul.gortma...@windriver.com