Bug#544145: [Xen-devel] Crash with paravirt-ops 2.6.31.6 kernel

2009-11-25 Thread Jan Beulich
>>> Ian Campbell  23.11.09 17:44 >>>
>On Mon, 2009-11-23 at 16:31 +, Jan Beulich wrote:
>> >> It does not happen on XenSource 2.6.18 kernel
>> >
>> >I assume that this kernel (perhaps coincidentally) manages to use
>> >FLAT_USER_CS32 for compat mode processes.
>> >
>> >> , or the Debian 2.6.26 kernel.
>> >
>> >This was a forward ported 2.6.18-style kernel so I guess the same reason
>> >as 2.6.18.
>> 
>> If your analysis was right, 2.6.18 as well as our forward ported kernels
>> should also be affected (both ia32_sysenter_target and ia32_cstar_target
>> store __USER32_CS to the frame, and return via HYPERVISOR_iret), yet
>> supposedly they don't have the problem (though I can't say why that
>> would be). So perhaps there's some other yet un-described aspect to
>> this, or I'm being confused by something...
>
>I didn't try any of these kernels myself so I don't really know what
>happens.

Okay, I think I spotted the relevant difference: 2.6.18 and forward ports
set VGCF_in_syscall only when returning from 64-bit system calls (through
ret_from_sys_call) - 32-bit syscalls (regardless of the entry path taken)
return through int_ret_from_sys_call. 32-bit guest kernels shouldn't be
affected by this, as compat mode returns from the hypervisor
(compat_restore_all_guest) always use iret.

Jan




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#534880: linux-image-2.6.26-2-xen-686: domU crashes

2009-11-25 Thread Nagy Péter

Hi,

I also have this bug with 2.6.26-2-xen-amd64 kernel. (from proposal-updates)
I noticed that the domUs locked when i'm using vcpu>1 option.

If you take a visit to here:
http://kepfeltoltes.hu/view/091125/xen1.padmin-memory-day_www.kepfeltoltes.hu_.png

You can see, that the domU apps filling memory. The situation is the 
same, as others

write it before. I can't use the domU, can't shutdown, just can destroy it.

I hope i helped with memory graph.

Peter





--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#504805: some more crash logs

2009-11-25 Thread micah anderson
Excerpts from micah anderson's message of Tue Nov 24 20:20:51 -0500 2009:
> Excerpts from Ben Hutchings's message of Tue Nov 24 18:51:45 -0500 2009:
> > On Tue, 2009-11-24 at 18:17 -0500, micah anderson wrote:
> > > I keep getting them, so I'll keep sending them:
> > 
> > Which kernel version are you using?  Version 2.6.26-20 in
> > stable-proposed-updates fixes a crash bug in xen_spin_wait(), though I
> > don't think that accounts for all of the crashes you're seeing.
> 
> linux-image-2.6.26-2-xen-686  2.6.26-19lenny2
> 
> along with
> 
> xen-linux-system-2.6.26-2-xen-686 2.6.26-19lenny2
> 
> I can give the SPU kernel a try, wouldn't hurt.

Sadly, that wasn't a magic bullet, two machines went down last night
(both nodes of a fail-over cluster too, ouch). I was only able to
capture the console output of one of them. This one doesn't seem to
mention iret exceptions:


(XEN) domain_crash_sync called from entry.S (ff188600)
(XEN) Domain 0 (vcpu#2) crashed on cpu#2:
(XEN) [ Xen-3.2-1  x86_32p  debug=n  Not tainted ]
(XEN) CPU:2
(XEN) EIP:0061:[]
(XEN) EFLAGS: 0246   CONTEXT: guest
(XEN) eax:    ebx: 0001   ecx:    edx: ed449f90
(XEN) esi: 0002   edi: 0002   ebp:    esp: ed449f84
(XEN) cr0: 8005003b   cr4: 06f0   cr3: 001ddc80   cr2: b7fdadbd
(XEN) ds: 007b   es: 007b   fs: 00d8   gs:    ss: 0069   cs: 0061
(XEN) Guest stack trace from esp=ed449f84:
(XEN)c0105f52  0002 61b0bd7a 1dfa   
(XEN)c01028ab c0102810      
(XEN)      00d8 
(XEN)       ed43e880
(XEN)c035c460   0003    c0126f1a
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN)       
(XEN) Domain 0 crashed: 'noreboot' set - not rebooting.

micah


signature.asc
Description: PGP signature


Bug#503172: Current status

2009-11-25 Thread Martin Michlmayr
At the moment, two issues are left (regarding rev B1):

 - The power LED will blink all the time
 - The machine doesn't power off correctly.

I emailed Erik Benada who had some patches for this about the status a
few weeks ago but got no reply.  I just sent a ping.
-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#557991: Oops breaks resource failover in RHCS

2009-11-25 Thread Guido Günther
Package: linux-image-2.6.31-1-amd64
Severity: normal
Tags: patch

Hi,
current 2.6.31 oopses (attached) on resource failover with
redhat-cluster-suite.  This is fixed by this commit:

http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=063c4c99630c0b06afad080d2a18bda64172c1a2

Please apply. 
Cheers,
 -- Guido
Nov 19 15:04:26 testfoo1 rgmanager[1709]: State change: testfoo2.foo.bar DOWN
Nov 19 15:04:26 testfoo1 kernel: [  117.438037] [ cut here 
]
Nov 19 15:04:26 testfoo1 kernel: [  117.440175] kernel BUG at 
/build/buildd/linux-2.6-2.6.31/debian/build/source_amd64_none/fs/inode.c:1323!
Nov 19 15:04:26 testfoo1 kernel: [  117.440309] invalid opcode:  [#1] SMP
Nov 19 15:04:26 testfoo1 kernel: [  117.440309] last sysfs file: 
/sys/devices/virtual/input/input0/capabilities/sw
Nov 19 15:04:26 testfoo1 kernel: [  117.440309] CPU 0
Nov 19 15:04:26 testfoo1 kernel: [  117.440309] Modules linked in: nfsd lockd 
nfs_acl auth_rpcgss sunrpc exportfs dlm configfs bridge stp dm_multipath sc
si_dh loop virtio_console virtio_balloon evdev serio_raw psmouse button snd_pcm 
snd_timer snd soundcore snd_page_alloc pcspkr processor i2c_piix4 i2c_cor
e ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_snapshot dm_mod 
ide_cd_mod cdrom ata_generic libata scsi_mod virtio_blk piix ide_pci_generic 
e1000
uhci_hcd ide_core floppy virtio_pci virtio_ring virtio thermal fan thermal_sys
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] Pid: 1718, comm: dlm_send Not 
tainted 2.6.31-1-amd64 #1
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] RIP: 0010:[]  
[] iput+0x27/0x9e
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] RSP: 0018:88001bd53cb0  
EFLAGS: 00010246
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] RAX:  RBX: 
88001c1aac88 RCX: 88001c1aac88
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] RDX: 0004 RSI: 
f38c67d6 RDI: 88001c1aac88
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] RBP: 88001bd2fed0 R08: 
f38c67d6 R09: f38c67d6
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] R10: f38c67d6 R11: 
812b84ca R12: 88001bd2fee0
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] R13: 88001bd2ff00 R14: 
88003785e080 R15: 88001bd2ff88
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] FS:  41bf2950() 
GS:880001702000() knlGS:
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] CS:  0010 DS: 0018 ES: 0018 
CR0: 8005003b
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] CR2: 010d10e8 CR3: 
1bd4a000 CR4: 06f0
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] DR0:  DR1: 
 DR2: 
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] DR3:  DR6: 
0ff0 DR7: 0400
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] Process dlm_send (pid: 1718, 
threadinfo 88001bd52000, task 88003785e080)
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] Stack:
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  f38c67d6 
f38c67d6  a02aa003
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] <0> 88001c1aac40 
88001bd6b510 f38c67d6 880001716870
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] <0> 88003785e0b8 
880001716800 f38c67d6 810106ac
Nov 19 15:04:26 testfoo1 kernel: [  117.460215] Call Trace:
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
tcp_connect_to_sock+0x1f9/0x260 [dlm]
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
__switch_to+0xbe/0x28b
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
set_next_entity+0x48/0x82
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
pick_next_task_fair+0xb4/0xd3
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
process_send_sockets+0x41/0x1f3 [dlm]
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
__queue_work+0x35/0x5c
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
process_send_sockets+0x0/0x1f3 [dlm]
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
worker_thread+0x182/0x234
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
autoremove_wake_function+0x0/0x59
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
worker_thread+0x0/0x234
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
kthread+0x9b/0xa3
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
child_rip+0xa/0x20
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
pvclock_clocksource_read+0x4a/0x98
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
kthread+0x0/0xa3
Nov 19 15:04:26 testfoo1 kernel: [  117.460215]  [] ? 
child_rip+0x0/0x20




Processed: Re: Bug#544905 closed by Bastian Blank (Bug#544905: fixed in linux-2.6 2.6.32~rc8-1~experimental.1)

2009-11-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reopen 544905
Bug #544905 {Done: Bastian Blank } [linux-2.6] libsigsegv: 
FTBFS on amd64: Test failure
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
> found 544905 2.6.32~rc8-1~experimental.1
Bug #544905 [linux-2.6] libsigsegv: FTBFS on amd64: Test failure
There is no source info for the package 'linux-2.6' at version 
'2.6.32~rc8-1~experimental.1' with architecture ''
Unable to make a source version for version '2.6.32~rc8-1~experimental.1'
Bug Marked as found in versions 2.6.32~rc8-1~experimental.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#544905: closed by Bastian Blank (Bug#544905: fixed in linux-2.6 2.6.32~rc8-1~experimental.1)

2009-11-25 Thread Daniel Schepler
reopen 544905
found 544905 2.6.32~rc8-1~experimental.1
thanks

On Tuesday 24 November 2009 09:09:07 Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the linux-2.6 package:
> 
> #544905: libsigsegv: FTBFS on amd64: Test failure
> 
> It has been closed by Bastian Blank .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Bastian Blank
>   by replying to this email.

I just tried building libsigsegv under this version of linux-image-2.6.32-rc8-
amd64 and still got the same build failure.
-- 
Daniel Schepler



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#557996: linux-image-2.6.32-rc8-amd64: Missing ath5k driver

2009-11-25 Thread Daniel Schepler
Package: linux-image-2.6.32-rc8-amd64
Version: 2.6.32~rc8-1~experimental.1
Severity: normal

My wireless card doesn't work under this version of the kernel image:

09:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless 
Network Adapter (rev 01)
   
Subsystem: Hewlett-Packard Company Device 137a  
Flags: bus master, fast devsel, latency 0, IRQ 18   
Memory at d110 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [60] Express Legacy Endpoint, MSI 00
Capabilities: [90] MSI-X: Enable- Count=1 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel 
Kernel driver in use: ath5k
 (lspci output from 2.6.31-2).

It looks like the 2.6.32 kernel image doesn't have any ath5k.ko in it.
-- 
Daniel Schepler



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: scheduling 2.6.26-21

2009-11-25 Thread dann frazier
On Tue, Nov 24, 2009 at 02:02:25PM -0700, dann frazier wrote:
> We have several pending changes, plus we need to merge in the latest
> DSAs. I'll plan on uploading tomorrow, so let me know if you have any
> changes pending that might need more time.

The p-u processing isn't working at the moment, and there's no real
point in uploading until it is - so I'm postponing..


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#544145: [Xen-devel] Crash with paravirt-ops 2.6.31.6 kernel

2009-11-25 Thread Jeremy Fitzhardinge
On 11/25/09 02:22, Jan Beulich wrote:
> Okay, I think I spotted the relevant difference: 2.6.18 and forward ports
> set VGCF_in_syscall only when returning from 64-bit system calls (through
> ret_from_sys_call) - 32-bit syscalls (regardless of the entry path taken)
> return through int_ret_from_sys_call. 32-bit guest kernels shouldn't be
> affected by this, as compat mode returns from the hypervisor
> (compat_restore_all_guest) always use iret.
>   

I think dropping the VCGF_in_syscall flag is the simplest possible fix
then.  There doesn't seem to be a huge benefit to using sysret in this
case.  Does this look OK?

J

Subject: [PATCH] xen: use iret for return from 64b kernel to 32b usermode

If Xen wants to return to a 32b usermode with sysret it must use the
right form.  When using VCGF_in_syscall to trigger this, it looks at
the code segment and does a 32b sysret if it is FLAT_USER_CS32.
However, this is different from __USER32_CS, so it fails to return
properly if we use the normal Linux segment.

So avoid the whole mess by dropping VCGF_in_syscall and simply use
plain iret to return to usermode.

Signed-off-by: Jeremy Fitzhardinge 

diff --git a/arch/x86/xen/xen-asm_64.S b/arch/x86/xen/xen-asm_64.S
index 02f496a..f681d55 100644
--- a/arch/x86/xen/xen-asm_64.S
+++ b/arch/x86/xen/xen-asm_64.S
@@ -96,7 +96,7 @@ ENTRY(xen_sysret32)
pushq $__USER32_CS
pushq %rcx
 
-   pushq $VGCF_in_syscall
+   pushq $0
 1: jmp hypercall_iret
 ENDPATCH(xen_sysret32)
 RELOC(xen_sysret32, 1b+1)





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558011: linux-image-2.6.32-rc8-amd64: several missing modules

2009-11-25 Thread Uwe Kleine-König
Package: linux-2.6
Version: 2.6.32~rc8-1~experimental.1
Severity: normal
Tags: patch

Hello,

compared with linux-image-2.6.31-1-amd64 the following modules are missing:

(This list is more a documentation what I checked and provided for reference
that you don't need to recheck.  So the "removed" and "renamed" items are not
part of this bug.)

 1  drivers/dma/ioatdma.ko
renamed to drivers/dma/ioat/ioatdma.ko

 2  drivers/hwmon/fscher.ko
 3  drivers/hwmon/fscpos.ko
2-3 removed upstream, superseed by fschmd (included in 
32~rc8-1~experimental.1)

 4  drivers/i2c/chips/pca9539.ko
 5  drivers/i2c/chips/pcf8574.ko
 6  drivers/i2c/chips/pcf8575.ko
4-6 removed upstream, superseeded by drivers/gpio/pca953x.c and
drivers/gpio/pcf857x.c (not included in 32~rc8-1~experimental.1
as they depend on GPIOLIB which is not available on x86)

 7  drivers/input/touchscreen/w90p910_ts.ko
depends on CONFIG_HAVE_CLK now which isn't available on x86

 8  drivers/isdn/hisax/isdnhdlc.ko
renamed to drivers/isdn/i4l/isdnhdlc.ko

 9  drivers/media/radio/radio-si470x.ko
10  drivers/net/wireless/ath/ar9170/ar9170usb.ko
11  drivers/net/wireless/ath/ath5k/ath5k.ko
12  drivers/net/wireless/ath/ath9k/ath9k.ko
13  drivers/net/wireless/ath/ath.ko
14  drivers/net/wireless/wl12xx/wl12xx.ko
9-15 are fixed by the attached patches

15  drivers/staging/rt3070/rt3070sta.ko
removed upstream, superseeded by rt2870 (included in 
32~rc8-1~experimental.1)

Best regards
Uwe
Index: debian-linux-2.6/debian/changelog
===
--- debian-linux-2.6.orig/debian/changelog	2009-11-25 22:31:58.079095557 +0100
+++ debian-linux-2.6/debian/changelog	2009-11-25 22:32:03.815096688 +0100
@@ -8,6 +8,9 @@
   * Enable PCI_MSI.
   * [powerpc] Properly enable Apple PMU battery.
 
+  [ Uwe Kleine-König ]
+  * reenable Atheros wireless drivers
+
  -- Martin Michlmayr   Sun, 22 Nov 2009 13:56:12 +
 
 linux-2.6 (2.6.32~rc8-1~experimental.1) unstable; urgency=low
Index: debian-linux-2.6/debian/config/config
===
--- debian-linux-2.6.orig/debian/config/config	2009-11-25 22:30:27.487096098 +0100
+++ debian-linux-2.6/debian/config/config	2009-11-25 22:30:45.663096523 +0100
@@ -1569,6 +1569,11 @@
 CONFIG_AR9170_USB=m
 
 ##
+## file: drivers/net/wireless/ath/Kconfig
+##
+CONFIG_ATH_COMMON=m
+
+##
 ## file: drivers/net/wireless/ath/ath5k/Kconfig
 ##
 CONFIG_ATH5K=m
Index: debian-linux-2.6/debian/config/config
===
--- debian-linux-2.6.orig/debian/config/config	2009-11-25 22:30:45.663096523 +0100
+++ debian-linux-2.6/debian/config/config	2009-11-25 22:32:33.631095905 +0100
@@ -1674,6 +1674,10 @@
 ## file: drivers/net/wireless/wl12xx/Kconfig
 ##
 CONFIG_WL12XX=m
+CONFIG_WL1251=m
+CONFIG_WL1251_SPI=m
+CONFIG_WL1251_SDIO=m
+CONFIG_WL1271=m
 
 ##
 ## file: drivers/net/wireless/zd1211rw/Kconfig
Index: debian-linux-2.6/debian/changelog
===
--- debian-linux-2.6.orig/debian/changelog	2009-11-25 22:32:42.507095982 +0100
+++ debian-linux-2.6/debian/changelog	2009-11-25 22:33:28.903095424 +0100
@@ -10,6 +10,7 @@
 
   [ Uwe Kleine-König ]
   * reenable Atheros wireless drivers
+  * reenable TI wl12xx wireless drivers
 
  -- Martin Michlmayr   Sun, 22 Nov 2009 13:56:12 +
 
Index: debian-linux-2.6/debian/config/config
===
--- debian-linux-2.6.orig/debian/config/config	2009-11-25 22:32:33.631095905 +0100
+++ debian-linux-2.6/debian/config/config	2009-11-25 22:33:45.567095565 +0100
@@ -854,6 +854,7 @@
 CONFIG_RADIO_ADAPTERS=y
 CONFIG_USB_MR800=m
 CONFIG_RADIO_TEA5764=m
+CONFIG_RADIO_SI470X=y
 
 ##
 ## file: drivers/media/radio/si470x/Kconfig
Index: debian-linux-2.6/debian/changelog
===
--- debian-linux-2.6.orig/debian/changelog	2009-11-25 22:35:11.819096256 +0100
+++ debian-linux-2.6/debian/changelog	2009-11-25 22:36:06.455097773 +0100
@@ -11,6 +11,7 @@
   [ Uwe Kleine-König ]
   * reenable Atheros wireless drivers
   * reenable TI wl12xx wireless drivers
+  * reenable Silicon Labs Si470x FM Radio Receiver driver
 
  -- Martin Michlmayr   Sun, 22 Nov 2009 13:56:12 +
 


Bug#558023: firmware-linux-nonfree: please, include radeon/RV635_pfp.bin firmware

2009-11-25 Thread Nicolas Maître
Package: firmware-linux-nonfree
Version: 0.21
Severity: wishlist

Hi,

I was trying to get the latest KMS features for my radeon HD3650 graphic card, 
with the new 2.6.32 kernel (rc8, in debian). However, it seems it's not working 
because of a missing firmware : RV635_pfp.bin

Here is the dmesg :
[   22.803137] [drm] Initialized drm 1.1.0 20060810
[   22.861239] [drm] radeon kernel modesetting enabled.
[   22.861351] radeon :01:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[   22.861417] radeon :01:00.0: setting latency timer to 64
[   22.862956] [drm] radeon: Initializing kernel modesetting.
[   22.863063] [drm] register mmio base: 0xFDFF
[   22.863126] [drm] register mmio size: 65536
[   22.863356] ATOM BIOS: M51Va
[   22.863422] [drm] Clocks initialized !
[   22.863501] mtrr: type mismatch for d000,1000 old: write-back
new: write-combining
[   22.863576] [drm] Detected VRAM RAM=256M, BAR=256M
[   22.863641] [drm] RAM width 128bits DDR
[   22.864634] [TTM] Zone  kernel: Available graphics memory: 2031782
kiB.
[   22.864715] [drm] radeon: 256M of VRAM memory ready
[   22.864777] [drm] radeon: 512M of GTT memory ready.
[   22.864868] [drm] Loading RV635 CP Microcode
[   22.864958] platform radeon_cp.0: firmware: requesting
radeon/RV635_pfp.bin
[   22.892286] r600_cp: Failed to load firmware "radeon/RV635_pfp.bin"
[   22.892350] [drm:r600_init] *ERROR* Failed to load firmware!
[   22.892413] [drm:radeon_driver_load_kms] *ERROR* Fatal error while
trying to initialize radeon.
[   22.892575] radeon :01:00.0: PCI INT A disabled


So, could you please include that firmware in the package ? Maybe i'm
not reporting on the right package, but anyway, I haven't found such a
file in the whole debian archive.
On the other hand, if you know another way to find the file, or to make
it work, please share it !

Thanks

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (400, 'karmic'), (2, 
'experimental')
Architecture: amd64 (x86_64)

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

firmware-linux-nonfree depends on no packages.

firmware-linux-nonfree recommends no packages.

Versions of packages firmware-linux-nonfree suggests:
ii  initramfs-to 0.93.4  tools for generating an initramfs
ii  linux-image- 2.6.30-8Linux 2.6.30 image on AMD64
ii  linux-image- 2.6.31-2Linux 2.6.31 for 64-bit PCs
ii  linux-image- 2.6.32~rc8-1~experimental.1 Linux 2.6.32-rc8 for 64-bit PCs

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558033: firmware-linux-nonfree: debian/copyright vague about upstream location

2009-11-25 Thread Piotr Engelking
Package: firmware-linux-nonfree
Version: 0.21
Severity: normal

The debian/copyright file states:

   The binary firmware may be downloaded from
http://ftp.kernel.org/pub/linux/kernel/.

This is highly vague - the location pointed at contains many files, and
it is not necessarily obvious where the firmware can be found. (It can
be found in the 'firmware' directory in the upstream Linux kernel
source.) Please include this information.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.31 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

firmware-linux-nonfree depends on no packages.

firmware-linux-nonfree recommends no packages.

Versions of packages firmware-linux-nonfree suggests:
ii  initramfs-to 0.93.4  tools for generating an initramfs
ii  linux-image- 2.6.32~rc8-1~experimental.1 Linux 2.6.32-rc8 for 64-bit PCs

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Processed: fixed-in 2.6.32~rc8~experimental.1 (Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ccccb5b0)

2009-11-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 555826 2.6.32~rc8-1~experimental.1
Bug #555826 [linux-2.6] linux-image-2.6.31-1-686: Kernel panic - not syncing: 
stack-protector: Kernel stack is corrupted in: b5b0
There is no source info for the package 'linux-2.6' at version 
'2.6.32~rc8-1~experimental.1' with architecture ''
Unable to make a source version for version '2.6.32~rc8-1~experimental.1'
Bug Marked as fixed in versions 2.6.32~rc8-1~experimental.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#544145: [Xen-devel] Crash with paravirt-ops 2.6.31.6 kernel

2009-11-25 Thread Jan Beulich
>>> Jeremy Fitzhardinge  25.11.09 22:24 >>>
>On 11/25/09 02:22, Jan Beulich wrote:
>> Okay, I think I spotted the relevant difference: 2.6.18 and forward ports
>> set VGCF_in_syscall only when returning from 64-bit system calls (through
>> ret_from_sys_call) - 32-bit syscalls (regardless of the entry path taken)
>> return through int_ret_from_sys_call. 32-bit guest kernels shouldn't be
>> affected by this, as compat mode returns from the hypervisor
>> (compat_restore_all_guest) always use iret.
>>   
>
>I think dropping the VCGF_in_syscall flag is the simplest possible fix
>then.  There doesn't seem to be a huge benefit to using sysret in this
>case.  Does this look OK?

Yes, with one (more cosmetic than really useful) adjustment - the flag
should also be dropped from the !CONFIG_IA32_EMULATION code path
at the end of the file.

In any case,
Acked-by: Jan Beulich 

Jan




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org