Re: [Debian] Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread maximilian attems
On Wed, Sep 10, 2008 at 08:25:10AM +0200, Thorsten Schifferdecker wrote:
 Hi Maximilian,
 
 since you add upstream OpenVZ fixes up to git commit 0f14912e3d2251aff,
 Checkpointing work if enabled if enabled in feature-set/openvz/config,
 but a bug existes in 2.6.24 and 2.6.26, chkpnt with a sit device doesnt
 work, see http://bugzilla.openvz.org/874

latest sid image that will be uploaded today has up to 24cebf40278cb071ff8b,
but that still has checkpointing defaulting to no.
 
-- 
maks


ps please don't top post.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [Debian] Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread Thorsten Schifferdecker
Hi Maximilian,

Am Mi, 10.09.2008, 08:28, schrieb maximilian attems:
 On Wed, Sep 10, 2008 at 08:25:10AM +0200, Thorsten Schifferdecker wrote:
 Hi Maximilian,

 since you add upstream OpenVZ fixes up to git commit 0f14912e3d2251aff,
 Checkpointing work if enabled if enabled in feature-set/openvz/config,
 but a bug existes in 2.6.24 and 2.6.26, chkpnt with a sit device doesnt
 work, see http://bugzilla.openvz.org/874

 latest sid image that will be uploaded today has up to
 24cebf40278cb071ff8b,
 but that still has checkpointing defaulting to no.

 --
 maks


 ps please don't top post.
 ___
 Debian mailing list
 [EMAIL PROTECTED]
 https://openvz.org/mailman/listinfo/debian


Yesterday sync my own debain linux-2.6 tree with the last OpenVZ git
commit and checkpoint feature enabled, and checkpoint works.

Hope this helps.

Regards,
 Thorsten


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [Debian] Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread Thorsten Schifferdecker
Hi Maximilian,

since you add upstream OpenVZ fixes up to git commit 0f14912e3d2251aff,
Checkpointing work if enabled if enabled in feature-set/openvz/config,
but a bug existes in 2.6.24 and 2.6.26, chkpnt with a sit device doesnt
work, see http://bugzilla.openvz.org/874

Regards,
 Thorsten
--
Thorsten Schifferdecker
[EMAIL PROTECTED]

Am Di, 9.09.2008, 23:58, schrieb maximilian attems:
 On Tue, Sep 09, 2008 at 11:26:49PM +0300, Mert Dirik wrote:

 Do you plan to fix #497292 for this release? It would be good although
 I'm not
 sure if it can be done before release since it is not important.

 hmmm, CONFIG_VZ_CHECKPOINT defaults to n according to the openvz patchset.
 and the options where taken in accordance with openvz team.

 maybe kir or pavel have some input, but that be pretty hard to change now,
 as this may well be an abi breaker.

 --
 maks
 ___
 Debian mailing list
 [EMAIL PROTECTED]
 https://openvz.org/mailman/listinfo/debian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#497796: maybe solved upstream?

2008-09-10 Thread Santiago Garcia Mantinan
I've seen that on 2.6.26.4's changelog it says:

commit 464f8f4932d128a3e80402ec85d7c40c1f5e6899
Author: David S. Miller [EMAIL PROTECTED]
Date:   Wed Sep 3 01:03:39 2008 -0700

ipsec: Fix deadlock in xfrm_state management.

[ Upstream commit 37b08e34a98c664bea86e3fae718ac45a46b7276 ]

Ever since commit 4c563f7669c10a12354b72b518c2287ffc6ebfb3
([XFRM]: Speed up xfrm_policy and xfrm_state walking) it is
illegal to call __xfrm_state_destroy (and thus xfrm_state_put())
with xfrm_state_lock held.  If we do, we'll deadlock since we
have the lock already and __xfrm_state_destroy() tries to take
it again.

Fix this by pushing the xfrm_state_put() calls after the lock
is dropped.

Signed-off-by: David S. Miller [EMAIL PROTECTED]
Signed-off-by: Greg Kroah-Hartman [EMAIL PROTECTED]

Which could be the fix to the hangs I was seeing, I suppose you'll be adding
latest upstream patches to a -5 version of the kernel and thus this patch,
if so, and I'm right about this patch, this bug could then be closed.

Regards...
-- 
Santiago García Mantiñán



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: tagging 497796

2008-09-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.26
 tags 497796 + pending
Bug#497796: linux-image-2.6.26-1-686: kernel 2.6.26 hangs when using ipsec
There were no tags set.
Tags added: pending


End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#497911: 2.6.26-1-686-bigmem/aacraid WARNING: at lib/scatterlist.c:316 sg_copy_buffer+0x2f/0x14d()

2008-09-10 Thread Winfried Tilanus
Because this bug is not I Debian specific, I reported this bug also
upstream: Kernel Bug Tracker Bug #11529

http://bugzilla.kernel.org/show_bug.cgi?id=11529




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: bug 497911 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=11529

2008-09-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.10.35
 forwarded 497911 http://bugzilla.kernel.org/show_bug.cgi?id=11529
Bug#497911: linux-image-2.6.26-1-686-bigmem: 2.6.26-1-686-bigmem/aacraid 
WARNING: at lib/scatterlist.c:316 sg_copy_buffer+0x2f/0x14d()
Noted your statement that Bug has been forwarded to 
http://bugzilla.kernel.org/show_bug.cgi?id=11529.


End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#497230: [alpha] legacy and generic package descriptions

2008-09-10 Thread Fabian Greffrath
Well, I still don't entirely know what the -legacy package is for nor 
what constitutes an Alpha Legacy Machine. Looking at the linux-2.6 
Debian changelog it appears it may be something to do with MILO.


Yes, same problem here.

Please provide a (non-exhaustive) list of model and/or system types 
that are supported by each particular package. For example, I have an 
Alpha EV67 with system type and variation reported as Tsunami and 
Monet by /proc/cpuinfo. However, I still don't have any clue if I 
have to install the -generic or the -legacy kernel.


Thanks!

Cheers,
Fabian
--
Dipl.-Phys. Fabian Greffrath

Ruhr-Universität Bochum
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150, IB 3/134
D-44780 Bochum

Telefon: +49 (0)234 / 32-26334
Fax: +49 (0)234 / 32-14227
E-Mail:  [EMAIL PROTECTED]



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#498472: linux-image-2.6.26-1-xen-686: does not boot under Etch Xen

2008-09-10 Thread Ferenc Wagner
Package: linux-image-2.6.26-1-xen-686
Version: 2.6.26-4
Severity: normal

Hi,

I know an Etch host with its stock Xen 3.0.3 hypervisor may be of no
interest, but I hope it still is.  After all, a while ago I tested 
linux-image-2.6.26-rc8-xen-686_2.6.26~rc8-1~experimental.1~snapshot.11752_i386.deb
and that booted OK with the same config on the same system.

Unfortunately, I can't find any more such images under
http://kernel-archive.buildserver.net/debian-kernel/, so I can't tell
which snapshot was the last workable version.  From that pool,
2.6.25-7snapshot.11833 works, 2.6.27~rc5-1~experimental.1~snapshot.12183
crashes very much the same.

Here is the config:

name = sandbox.aai
kernel = /home/wferi/vmlinuz-2.6.26-1-xen-686
ramdisk = /home/wferi/initrd.img-2.6.26-1-xen-686
memory = 300
vif = [ 'mac=00:16:3e:01:00:31, bridge=br894' ]
disk = [ 'phy:/dev/mapper/sandbox.aai,xvda,w' ]
root = /dev/mapper/sandbox-root ro
extra = 2
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash= 'restart'

And the full console output:

[0.00] Reserving virtual address space above 0xf57fe000
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.26-1-xen-686 (Debian 2.6.26-4) ([EMAIL 
PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP 
Thu Aug 28 16:22:33 UTC 2008
[0.00] BIOS-provided physical RAM map:
[0.00]  Xen:  - 0009f000 (usable)
[0.00]  Xen: 0010 - 12c0 (usable)
[0.00] 0MB HIGHMEM available.
[0.00] 300MB LOWMEM available.
[0.00] Zone PFN ranges:
[0.00]   DMA 0 - 4096
[0.00]   Normal   4096 -76800
[0.00]   HighMem 76800 -76800
[0.00] Movable zone start PFN for each node
[0.00] early_node_map[1] active PFN ranges
[0.00] 0:0 -76800
[0.00] DMI not present or invalid.
[0.00] Allocating PCI resources starting at 2000 (gap: 
12c0:ed40)
[0.00] SMP: Allowing 0 CPUs, 0 hotplug CPUs
[0.00] PERCPU: Allocating 42056 bytes of per cpu data
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 76200
[0.00] Kernel command line:  root=/dev/mapper/sandbox-root ro 2
[0.00] Local APIC disabled by BIOS -- you can enable it with lapic
[0.00] Enabling fast FPU save and restore... done.
[0.00] Enabling unmasked SIMD FPU exception support... done.
[0.00] Initializing CPU#0
[0.00] PID hash table entries: 2048 (order: 11, 8192 bytes)
[0.00] Detected 2392.232 MHz processor.
[0.004000] Console: colour dummy device 80x25
[0.004000] console [tty0] enabled
[0.004000] console [hvc0] enabled
[0.004000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.004000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[0.004000] Memory: 292528k/307200k available (1603k kernel code, 14192k 
reserved, 635k data, 208k init, 0k highmem)
[0.004000] virtual kernel memory layout:
[0.004000] fixmap  : 0xf5617000 - 0xf57fd000   (1944 kB)
[0.004000] pkmap   : 0xf520 - 0xf540   (2048 kB)
[0.004000] vmalloc : 0xd380 - 0xf51fe000   ( 537 MB)
[0.004000] lowmem  : 0xc000 - 0xd2c0   ( 300 MB)
[0.004000]   .init : 0xc0337000 - 0xc036b000   ( 208 kB)
[0.004000]   .data : 0xc0290d03 - 0xc032fa80   ( 635 kB)
[0.004000]   .text : 0xc010 - 0xc0290d03   (1603 kB)
[0.004000] Checking if this processor honours the WP bit even in supervisor 
mode...Ok.
[0.004000] installing Xen timer for CPU 0
[0.080011] Calibrating delay using timer specific routine.. 3831.81 
BogoMIPS (lpj=7663624)
[0.080090] Security Framework initialized
[0.080108] SELinux:  Disabled at boot.
[0.080122] Capability LSM initialized
[0.080154] Mount-cache hash table entries: 512
[0.080354] Initializing cgroup subsys ns
[0.080375] Initializing cgroup subsys cpuacct
[0.080388] Initializing cgroup subsys devices
[0.080437] CPU: Trace cache: 12K uops, L1 D cache: 8K
[0.080457] CPU: L2 cache: 512K
[0.080468] CPU: Physical Processor ID: 3
[0.080483] Intel machine check architecture supported.
[0.080506] Intel machine check reporting enabled on CPU#0.
[0.080522] CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
[0.080567] general protection fault:  [#1] SMP 
[0.080587] Modules linked in:
[0.080598] 
[0.080607] Pid: 0, comm: swapper Not tainted (2.6.26-1-xen-686 #1)
[0.080625] EIP: e019:[c010245b] EFLAGS: 00010202 CPU: 0
[0.080644] EIP is at xen_write_cr4+0x2/0x6
[0.080657] EAX: 0620 EBX: 0020 ECX: c0331f3f EDX: 0036
[0.080673] ESI: c0331fe4 EDI:  EBP:  ESP: c0331fc8
[0.080690]  DS: e021 ES: e021 FS: 00d8 GS:  SS: e021
[   

Bug#498472: linux-image-2.6.26-1-xen-686: does not boot under Etch Xen

2008-09-10 Thread Ian Campbell
On Wed, 2008-09-10 at 11:01 +0200, Ferenc Wagner wrote:
 [0.080644] EIP is at xen_write_cr4+0x2/0x6

Unfortunately the 3.0.3 hypervisor is stricter in what it will allow CR4
to be set to than necessary and won't allow some of the fields which
newer kernels use. I think we are unlikely to fix this in the kernel in
Debian. You could ask upstream but I'm not sure they would want/be able
to change this behaviour.

Ian.
-- 
Ian Campbell

13. ...  r-q1




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread Pavel Emelyanov
maximilian attems wrote:
 On Tue, Sep 09, 2008 at 11:26:49PM +0300, Mert Dirik wrote:
 Do you plan to fix #497292 for this release? It would be good although I'm 
 not
 sure if it can be done before release since it is not important.
 
 hmmm, CONFIG_VZ_CHECKPOINT defaults to n according to the openvz patchset.

My fault :( I forgot to put it back when we finally made it working...

 and the options where taken in accordance with openvz team.
 
 maybe kir or pavel have some input, but that be pretty hard to change now,
 as this may well be an abi breaker.

Can you elaborate on this? CPT modules provide only two ioctl-s for
vzctl and nothing more that can affect any other binary.

Thanks,
Pavel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#498479: bug in linux-image-2.6-686

2008-09-10 Thread slim
Package: linux-image-2.6-686
Version: 2.6.26+16
Severity: important

Looks like there is the bug in linux-image-2.6-686  2.6.26+16  lenny
  
  [EMAIL PROTECTED]:~]# ethtool -i eth0
  driver: tg3
  version: 3.92.1
  firmware-version: 5721-v3.40a, ASFIPMI v6.14
  bus-info: :07:00.0
  
  SKB BUG comes to dmesg every sec
  
  [  903.012779] SKB BUG: Invalid truesize (276) len=99, sizeof(sk_buff)=180
  [  903.116830] SKB BUG: Invalid truesize (244) len=66, sizeof(sk_buff)=180
  [  903.198230] SKB BUG: Invalid truesize (244) len=66, sizeof(sk_buff)=180
  [  903.532004] SKB BUG: Invalid truesize (244) len=66, sizeof(sk_buff)=180
  [  903.619414] SKB BUG: Invalid truesize (244) len=66, sizeof(sk_buff)=180
  [  903.665378] SKB BUG: Invalid truesize (244) len=66, sizeof(sk_buff)=180
  [  903.721706] SKB BUG: Invalid truesize (244) len=66, sizeof(sk_buff)=180
  [  903.732325] SKB BUG: Invalid truesize (372) len=194, sizeof(sk_buff)=180
  [  903.736004] SKB BUG: Invalid truesize (532) len=354, sizeof(sk_buff)=180
  [  903.768004] SKB BUG: Invalid truesize (372) len=206, sizeof(sk_buff)=180
  [  903.840003] SKB BUG: Invalid truesize (276) len=99, sizeof(sk_buff)=180
  [  904.360003] SKB BUG: Invalid truesize (244) len=71, sizeof(sk_buff)=180
  [  904.483398] SKB BUG: Invalid truesize (308) len=141, sizeof(sk_buff)=180
  [  904.592193] SKB BUG: Invalid truesize (308) len=141, sizeof(sk_buff)=180
  [  904.737862] SKB BUG: Invalid truesize (372) len=194, sizeof(sk_buff)=180
  [  904.737862] SKB BUG: Invalid truesize (308) len=141, sizeof(sk_buff)=180
  [  904.818475] SKB BUG: Invalid truesize (532) len=354, sizeof(sk_buff)=180
  [  904.828916] SKB BUG: Invalid truesize (308) len=134, sizeof(sk_buff)=180
  [  904.878677] SKB BUG: Invalid truesize (372) len=206, sizeof(sk_buff)=180
  [  904.902845] SKB BUG: Invalid truesize (276) len=99, sizeof(sk_buff)=180
  [  904.937299] SKB BUG: Invalid truesize (308) len=134, sizeof(sk_buff)=180
  [  905.016003] SKB BUG: Invalid truesize (308) len=141, sizeof(sk_buff)=180
  [  905.152873] SKB BUG: Invalid truesize (308) len=141, sizeof(sk_buff)=180
  [  905.263748] SKB BUG: Invalid truesize (308) len=134, sizeof(sk_buff)=180
  [  905.496737] SKB BUG: Invalid truesize (244) len=71, sizeof(sk_buff)=180
  [  905.739766] SKB BUG: Invalid truesize (372) len=194, sizeof(sk_buff)=180




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#498472: linux-image-2.6.26-1-xen-686: does not boot under Etch Xen

2008-09-10 Thread Ferenc Wagner
Ian Campbell [EMAIL PROTECTED] writes:

 On Wed, 2008-09-10 at 11:01 +0200, Ferenc Wagner wrote:
 [0.080644] EIP is at xen_write_cr4+0x2/0x6

 Unfortunately the 3.0.3 hypervisor is stricter in what it will allow CR4
 to be set to than necessary and won't allow some of the fields which
 newer kernels use. I think we are unlikely to fix this in the kernel in
 Debian. You could ask upstream but I'm not sure they would want/be able
 to change this behaviour.

Hi Ian,

thanks for the quick and very informative response!  Is it enough if I
upgrade to 3.2.0-3~bpo4+2 or should I go for 3.2.1-2 in Lenny?

Interesting, though, that a CR flag changed going from rc8 to final...
-- 
Thanks,
Feri.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread Kir Kolyshkin

maximilian attems wrote:

On Tue, Sep 09, 2008 at 11:26:49PM +0300, Mert Dirik wrote:
  

Do you plan to fix #497292 for this release? It would be good although I'm not
sure if it can be done before release since it is not important.



hmmm, CONFIG_VZ_CHECKPOINT defaults to n according to the openvz patchset.
and the options where taken in accordance with openvz team.

maybe kir or pavel have some input, but that be pretty hard to change now,
as this may well be an abi breaker.

Max,

If it's still possible to change this option, please do it. 
Checkpointing is now working fine, it's totally our fault that we forgot 
to switch the relative option.


So, please set CONFIG_VZ_CHECKPOINT=m. From the ABI point of view this 
adds two new ioctl()s for /dev/vzctl, nothing more.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread maximilian attems
On Wed, Sep 10, 2008 at 02:09:52PM +0400, Kir Kolyshkin wrote:
 
 If it's still possible to change this option, please do it. 
 Checkpointing is now working fine, it's totally our fault that we forgot 
 to switch the relative option.
 
 So, please set CONFIG_VZ_CHECKPOINT=m. From the ABI point of view this 
 adds two new ioctl()s for /dev/vzctl, nothing more.

thanks kir and pavel for input.

did a build test and abicheck went positive like according your
statements. so enabled it for 2.6.26-6. as 2.6.26-5 upload happened
today can't say for sure when this will land. depends mostly on
next upstream stable release. will see to get it into Lenny.

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [Debian] Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread maximilian attems
On Wed, 10 Sep 2008, Thorsten Schifferdecker wrote:

 since you add upstream OpenVZ fixes up to git commit 0f14912e3d2251aff,
 Checkpointing work if enabled if enabled in feature-set/openvz/config,
 but a bug existes in 2.6.24 and 2.6.26, chkpnt with a sit device doesnt
 work, see http://bugzilla.openvz.org/874

can i have an bug report with severity important against linux-2.6
so that the commited checkpoint enabling really lands in lenny?

thanks

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#498489: linux-image-2.6.26-1-686: disconnecting USB cellphone while using it for PPP causes oops

2008-09-10 Thread Simon McVittie
Package: linux-image-2.6.26-1-686
Version: 2.6.26-4
Severity: normal

When using a 3G phone over USB for PPP connectivity, the kernel oopses if
the phone is accidentally unplugged (or, as in the attached log, its battery
runs out) before pppd has been terminated. After this happens, ppp does not
work (and new pppd processes become unkillable) until after the next reboot.

This oops trace results from a Nokia 6120 rebooting due to a low battery
while it's in use by an i386 laptop (in the oops trace you can see it
disconnecting from USB and then reconnecting), but I've seen the same symptoms
when the phone was unplugged rather than rebooting.

I've also seen the same symptoms when a Nokia 6233 was unplugged from an
amd64 with etch's 2.6.18 kernel.

The nearest I can find upstream is
http://bugzilla.kernel.org/show_bug.cgi?id=4407 which was apparently
fixed back in 2.6.13 - perhaps by 2.6.18 it had crept back in?

-- Package-specific info:
** Version:
Linux version 2.6.26-1-686 (Debian 2.6.26-4) ([EMAIL PROTECTED]) (gcc version 
4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 12:00:54 UTC 
2008

** Command line:
root=/dev/mapper/carbon-root ro resume=/dev/mapper/carbon-swap 
usbcore.autosuspend=1 

** Tainted: G D W (640)

** Kernel log:
[241643.596467] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[241643.596497] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[241643.599541] PM: Writing back config space on device :15:00.2 at offset 
4 (was 0, writing e4301800)
[241643.599551] PM: Writing back config space on device :15:00.2 at offset 
3 (was 80, writing 804000)
[241643.599561] PM: Writing back config space on device :15:00.2 at offset 
1 (was 210, writing 216)
[241643.599586] ACPI: PCI Interrupt :15:00.2[C] - GSI 18 (level, low) - 
IRQ 18
[241643.601405] nsc-ircc 00:0a: activated
[241644.522294] sd 0:0:0:0: [sda] Starting disk
[241644.544985] PCI: Setting latency timer of device :00:02.0 to 64
[241644.620565] Restarting tasks ... 6usb 4-2: USB disconnect, address 31
[241644.671313] ADDRCONF(NETDEV_UP): eth0: link is not ready
[241644.684251] done.
[241644.691629] ACPI: PCI Interrupt :03:00.0[A] - GSI 17 (level, low) - 
IRQ 17
[241644.771525] Registered led device: iwl-phy0:radio
[241644.772615] Registered led device: iwl-phy0:assoc
[241644.773688] Registered led device: iwl-phy0:RX
[241644.774668] Registered led device: iwl-phy0:TX
[241644.776216] wlan0: Initial auth_alg=0
[241644.776221] wlan0: authenticate with AP 00:12:da:bf:65:40
[241644.798116] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[241644.804550] wlan0: Initial auth_alg=0
[241644.804550] wlan0: authenticate with AP 00:12:da:bf:65:40
[241644.911278] usb 4-2: new full speed USB device using uhci_hcd and address 32
[241645.001250] wlan0: authenticate with AP 00:12:da:bf:65:40
[241645.093260] usb 4-2: configuration #1 chosen from 1 choice
[241645.095529] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
[241645.095538] usb 4-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[241645.095541] usb 4-2: Product: Biometric Coprocessor
[241645.095544] usb 4-2: Manufacturer: STMicroelectronics
[241645.209260] wlan0: authenticate with AP 00:12:da:bf:65:40
[241645.407967] wlan0: authentication with AP 00:12:da:bf:65:40 timed out
[241739.094958] usb 3-1: new full speed USB device using uhci_hcd and address 23
[241739.267638] usb 3-1: configuration #1 chosen from 1 choice
[241739.279920] cdc_acm 3-1:1.8: ttyACM0: USB ACM device
[241739.286159] usb 3-1: bad CDC descriptors
[241739.286159] usb 3-1: bad CDC descriptors
[241739.293816] usb 3-1: New USB device found, idVendor=0421, idProduct=002f
[241739.293827] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[241739.293833] usb 3-1: Product: Nokia 6120 classic
[241739.293840] usb 3-1: Manufacturer: Nokia
[241790.084054] CPU0 attaching NULL sched-domain.
[241790.084054] CPU1 attaching NULL sched-domain.
[241790.100097] CPU0 attaching sched-domain:
[241790.100105]  domain 0: span 0-1
[241790.100108]   groups: 0 1
[241790.100114] CPU1 attaching sched-domain:
[241790.100116]  domain 0: span 0-1
[241790.100119]   groups: 1 0
[241922.249493] tun0: Disabled Privacy Extensions
[242005.905301] usb 3-1: USB disconnect, address 23
[242006.149355] usb 3-1: new full speed USB device using uhci_hcd and address 24
[242006.308336] usb 3-1: configuration #1 chosen from 1 choice
[242006.308336] usb 3-1: New USB device found, idVendor=0421, idProduct=0106
[242006.308336] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[242006.308336] usb 3-1: Product: Nokia USB ROM
[242006.308336] usb 3-1: Manufacturer: Nokia
[242006.916292] BUG: unable to handle kernel NULL pointer dereference at 
0458
[242006.916292] IP: [c02b81d5] mutex_unlock+0x0/0xb
[242006.916292] *pde =  
[242006.916292] Oops: 0002 [#1] SMP 
[242006.916292] Modules linked in: ppp_deflate zlib_deflate bsd_comp 

Bug#469693: Turned out to be a topology problem

2008-09-10 Thread Juergen Pfennig
Hi,
the problem can be avoided by connecting the keyboard/mouse dongle directly 
(without an extra hub). The card-reader itself works fine and causes no extra 
problems. Occasional USB-stick problems are gone. Summary:

- If the cherry-marlin keyboard/mouse usb dongle is connected via a hub the 
USB stack becomes instable and will hang after a while.

- If the same dongle is connected directly to the mobo all problems are gone.

I still consider this as a serious bug because with linux the whole USB stack 
hangs while Windows 2003 can recover this problem (the mouse hangs only for a 
second). I tried a different hub with no effect, but I did not try a 
different keyboard.

Jürgen




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processing of linux-2.6_2.6.26-5_powerpc.changes

2008-09-10 Thread Archive Administrator
linux-2.6_2.6.26-5_powerpc.changes uploaded successfully to localhost
along with the files:
  linux-2.6_2.6.26-5.dsc
  linux-2.6_2.6.26-5.diff.gz
  linux-doc-2.6.26_2.6.26-5_all.deb
  linux-manual-2.6.26_2.6.26-5_all.deb
  linux-patch-debian-2.6.26_2.6.26-5_all.deb
  linux-source-2.6.26_2.6.26-5_all.deb
  linux-support-2.6.26-1_2.6.26-5_all.deb
  linux-tree-2.6.26_2.6.26-5_all.deb
  linux-image-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
  linux-headers-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
  linux-image-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
  linux-headers-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
  linux-image-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
  linux-headers-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
  linux-headers-2.6.26-1-common_2.6.26-5_powerpc.deb
  linux-headers-2.6.26-1-all_2.6.26-5_powerpc.deb
  linux-headers-2.6.26-1-all-powerpc_2.6.26-5_powerpc.deb
  linux-libc-dev_2.6.26-5_powerpc.deb
  linux-image-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
  linux-headers-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
  linux-image-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
  linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
  linux-headers-2.6.26-1-common-vserver_2.6.26-5_powerpc.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



linux-2.6_2.6.26-5_powerpc.changes ACCEPTED

2008-09-10 Thread Debian Installer

Accepted:
linux-2.6_2.6.26-5.diff.gz
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-5.diff.gz
linux-2.6_2.6.26-5.dsc
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-5.dsc
linux-doc-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-doc-2.6.26_2.6.26-5_all.deb
linux-headers-2.6.26-1-all-powerpc_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-all-powerpc_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-all_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-all_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-common-vserver_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-common-vserver_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-common_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-common_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
linux-libc-dev_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-libc-dev_2.6.26-5_powerpc.deb
linux-manual-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-manual-2.6.26_2.6.26-5_all.deb
linux-patch-debian-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-5_all.deb
linux-source-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-source-2.6.26_2.6.26-5_all.deb
linux-support-2.6.26-1_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-support-2.6.26-1_2.6.26-5_all.deb
linux-tree-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-tree-2.6.26_2.6.26-5_all.deb


Override entries for your package:
linux-2.6_2.6.26-5.dsc - source devel
linux-doc-2.6.26_2.6.26-5_all.deb - optional doc
linux-headers-2.6.26-1-all-powerpc_2.6.26-5_powerpc.deb - optional devel
linux-headers-2.6.26-1-all_2.6.26-5_powerpc.deb - optional devel
linux-headers-2.6.26-1-common-vserver_2.6.26-5_powerpc.deb - optional devel
linux-headers-2.6.26-1-common_2.6.26-5_powerpc.deb - optional devel
linux-headers-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb - optional devel
linux-headers-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb - optional devel
linux-headers-2.6.26-1-powerpc_2.6.26-5_powerpc.deb - optional devel
linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb - optional devel
linux-headers-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb - optional devel
linux-image-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb - optional admin
linux-image-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb - optional admin
linux-image-2.6.26-1-powerpc_2.6.26-5_powerpc.deb - optional admin
linux-image-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb - optional admin
linux-image-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb - optional admin
linux-libc-dev_2.6.26-5_powerpc.deb - optional devel
linux-manual-2.6.26_2.6.26-5_all.deb - optional doc
linux-patch-debian-2.6.26_2.6.26-5_all.deb - optional devel
linux-source-2.6.26_2.6.26-5_all.deb - optional devel
linux-support-2.6.26-1_2.6.26-5_all.deb - optional devel
linux-tree-2.6.26_2.6.26-5_all.deb - optional devel

Announcing to [EMAIL PROTECTED]
Closing bugs: 484432 496603 497528 497796 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: Significant problem

2008-09-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 494144 serious
Bug#494144: Checking versions of the symbols in modules
Severity set to `serious' from `normal'

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#497528: marked as done (openvz: Multiple bridges crashing when second veth device configured in the container.)

2008-09-10 Thread Debian Bug Tracking System

Your message dated Wed, 10 Sep 2008 14:32:58 +
with message-id [EMAIL PROTECTED]
and subject line Bug#497528: fixed in linux-2.6 2.6.26-5
has caused the Debian Bug report #497528,
regarding openvz: Multiple bridges crashing when second veth device configured 
in the container.
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 [EMAIL PROTECTED]
immediately.)


-- 
497528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497528
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-image-2.6.26-1-openvz-amd64
Version: 2.6.26-4

I'm trying to get openvz working in a somewhat complex networking 
environment, and hitting a hard lock-up when using multiple bridges.

I attach /etc/network/interfaces from CT0, plus the CT100 config and a 
script used (manually at the moment) to bring up the bridges once the 
CT100 has been started.

CT0 is networked to three separate subnets, called main, deploy and 
ilom respectively.

deploy: this is physically plumbed into eth0.
main: this is physically plumbed into bond0 (eth1 and eth2).
ilom: this is physically plumbed into eth3.

There are three bridge devices created (and assigned IP addresses) 
within CT0, named as above - see the attached interfaces for details. 
The only subtle thing here is that the main bridge is on a bonded 
interface.

This all works, and the box boots and can see its attached networks.

I can do the following:

vzctl start 100

and the zone comes up. The zone itself only has its ethIlom configured 
and allocated a network address.

Once the vzbridge script (attached) is run, the veth devices of the new 
CT100 are attached to their respective bridges.

All good so far: I have visibility to the ILOM network from CT0 and from 
the VE.

However, once I attempt to bring up ethDeploy within the VE, the host 
locks up hard:

vzctl enter 100
ifconfig ethDeploy up
[hard lockup]

I've a requirement to multiply-connect these containers, so any help 
here would be appreciated. Certainly a hard lockup doesn't sound like 
the correct behaviour.

Cheers,
jan


-- 
jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/
Tel +44 (0)117 3317661   http://ioctl.org/jan/
ioctl(2): probably the coolest Unix system call in the world# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto deploy
iface deploy inet static
bridge_ports eth0
bridge_maxwait 8
address 172.16.4.10
netmask 255.255.255.0
network 172.16.4.0
broadcast 172.16.4.255
# gateway 172.16.4.128
metric 20
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 99.99.99.99
dns-search example.org
up route add -net 224.0.0.0/4 dev deploy
down route del -net 224.0.0.0/4 dev deploy

#auto bond0
iface bond0 inet manual
slaves eth1 eth2

auto main
iface main inet static
address 172.16.9.31
netmask 255.255.255.0
network 172.16.9.0
broadcast 172.16.9.255
gateway 172.16.9.250
metric 5
bridge_ports bond0
bridge_maxwait 8
pre-up /sbin/ifconfig bond0 up
pre-up /sbin/ifenslave bond0 eth1 eth2

auto ilom
iface ilom inet static
address 10.0.0.38
netmask 255.255.255.0
network 10.0.0.0
broadcast 10.0.0.255
metric 20
bridge_ports eth3
bridge_maxwait 8
#!/bin/sh
# /etc/vz/scripts/vzbridge
# a script to add virtual network interfaces (veth's) in a CT to a bridge on CT0

if [ -z $VEID ]; then
VEID=$1
fi

CTID=$VEID

CONFIGFILE=/etc/vz/conf/$CTID.conf
. $CONFIGFILE

echo $NETIF | tr ';' '\n' | while read line
do
HOSTIF=$( echo $line | tr ',' '\n' | grep '^host_ifname=' | sed -e 
's/^host_ifname=//' )
BRIDGE=$( echo $line | tr ',' '\n' | grep '^bridge=' | sed -e 
's/^bridge=//' )
if [ -n $HOSTIF -a -n $BRIDGE ]; then
echo Adding interface $HOSTIF to bridge $BRIDGE on CT0 for 
CT$CTID
/sbin/ifconfig $HOSTIF 0
echo 1  /proc/sys/net/ipv4/conf/$HOSTIF/proxy_arp
echo 1  /proc/sys/net/ipv4/conf/$HOSTIF/forwarding
/usr/sbin/brctl addif $BRIDGE $HOSTIF
fi
done

exit 0

KMEMSIZE=14372700:14790164
LOCKEDPAGES=256:256
PRIVVMPAGES=65536:69632
SHMPAGES=21504:21504
NUMPROC=240:240
PHYSPAGES=0:9223372036854775807
VMGUARPAGES=33792:9223372036854775807
OOMGUARPAGES=26112:9223372036854775807
NUMTCPSOCK=360:360
NUMFLOCK=188:206
NUMPTY=16:16
NUMSIGINFO=256:256
TCPSNDBUF=1720320:2703360

Bug#497796: marked as done (linux-image-2.6.26-1-686: kernel 2.6.26 hangs when using ipsec)

2008-09-10 Thread Debian Bug Tracking System

Your message dated Wed, 10 Sep 2008 14:32:58 +
with message-id [EMAIL PROTECTED]
and subject line Bug#497796: fixed in linux-2.6 2.6.26-5
has caused the Debian Bug report #497796,
regarding linux-image-2.6.26-1-686: kernel 2.6.26 hangs when using ipsec
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 [EMAIL PROTECTED]
immediately.)


-- 
497796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497796
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-image-2.6.26-1-686
Severity: important



I has a working setup for lenny with 2.6.25 but now that 2.6.26 has entered
lenny I have found that the machine hangs.

Even though I have spent a lot of time trying to isolate the problem I can't
say much right now, the machines I started seing this on are [EMAIL PROTECTED] 
which
had to stablish an ipsec tunnel on their eth2 interface.

As I said the machines run ok on 2.6.25 but hang on 2.6.26 tested both
current lenny's -3 and also sid's -4 with the same result, a hang. I even
tested a -amd64 kernel copying the 32 bits files from the PIII to a core duo
machine and it also hanged. Typically it hangs on restarting openntpd when
configuring the network interfaces, the messages I was getting were like
this one:
[  125.628018] BUG: soft lockup - CPU#0 stuck for 61s! [ntpd:1915]
and are repeating every 64 seconds average.

The hang tends to be always when the machine is setting up the network on
booting, at that time it reloads the ntp daemon (I'm using openntpd) but
removing this daemon didn't mahe a change. Also sometimes it stops before
this point, when mounting the swap, but in a faster machine I found the
problem at a later stage, when starting the IKE server (racoon). It was on
this fater machine that I was able to boot on single user mode using the
amd64 kernel, but then when I tried to ping over the ipsec tunnel (I even
had the network cables off, so no tunnel had been established yet), the
machin hanged and started outputing to the screen a register dump and a call
trace.

I'll try to type here part of the call trace:

[80429785] ? _spin_lock_bh+0x9/0x1f
[80410505] ? __xfrm_state_destroy+0x3a/0xaf
[80411c1a] ? xfrm_state_find+0x542/0x5a9
[8040c51d] ? xfrm_tmpl_resolve+0x1af/0x2ed
[803c585a] ? flow_cache_lookup+0x30a/0x35d
[8040e367] ? xfrm_policy_lookup+0x0/0x1d4
[804296bf] ? _read_lock_bh+0x9/0x19
[8040caae] ? __xfrm_lookup+0x197/0x8e4
[803d69bd] ? __ip_route_output_flow+0x83a/0x8f8
[803d6ae4] ? ip_route_output_flow+0x69/0x1de
[803f59e5] ? ip4_datagram_connect+0x165/0x248
[803b047f] ? sys_connect+0x76/0xa6
[802ab114] ? d_instantiate+0x52/0x67
[803af60c] ? sock_attach_fd+0x84/0xaf
[80299129] ? fd_install+0x25/0x56
[803af686] ? sock_map_fd+0x4f/0x5a
[803c8e1e] ? compat_sys_socketcall+0x73/0x172
[80224bb2] ? sysenter_do_cal+0x1b/0x66

This dump was alternating with one that was the same as this one but without
the ? and lacking the __xfrm_state_destroy+0x3a/0xaf line but with this
extra line at the end:
[80306316] cap_task_post_setuid+0x0/0x1d3

The only way I could stop this message was to rename eth2 to eth3 for
example, without touching any other config, that way the eth2 card didn't
exist anymore and the services trying to use it wouldn't work, but the
machine did boot. After the boot I did ifconfig eth3 manually just to make
sure that having the interface down didn't have anything to do and the
machine wouldn't hang.

Just in case it was a problem with some network driver I changed the network
cards (a total of 3) for e100 driven cards on one test and 8139too on
another one with similar results as I had obtained on my first setup which
had a mixture of cards.

I tried to change stuff on the bios and tried not to load some of the unused
drivers just in case but nothing changed, I also did a clone of the machine
but without using a sofware raid which the first one had but nothing
changed.

Hope this helps finding the problem.


---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.26-5

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

linux-2.6_2.6.26-5.diff.gz
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-5.diff.gz
linux-2.6_2.6.26-5.dsc
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-5.dsc
linux-doc-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-doc-2.6.26_2.6.26-5_all.deb
linux-headers-2.6.26-1-all-powerpc_2.6.26-5_powerpc.deb
  to 

Bug#484432: marked as done (linux-image-2.6.24-1-versatile: Please enable the RTC)

2008-09-10 Thread Debian Bug Tracking System

Your message dated Wed, 10 Sep 2008 14:32:58 +
with message-id [EMAIL PROTECTED]
and subject line Bug#484432: fixed in linux-2.6 2.6.26-5
has caused the Debian Bug report #484432,
regarding linux-image-2.6.24-1-versatile: Please enable the RTC
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 [EMAIL PROTECTED]
immediately.)


-- 
484432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484432
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-image-2.6.24-1-versatile
Version: 2.6.24-7
Severity: important

# CONFIG_RTC_DRV_PL031 is not set

This is both the device emulated by qemu, and the device present (I
believe) on real Versatile boards.  Without it qemu always starts the
clock at the epoch.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-rc9 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.26-5

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

linux-2.6_2.6.26-5.diff.gz
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-5.diff.gz
linux-2.6_2.6.26-5.dsc
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-5.dsc
linux-doc-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-doc-2.6.26_2.6.26-5_all.deb
linux-headers-2.6.26-1-all-powerpc_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-all-powerpc_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-all_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-all_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-common-vserver_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-common-vserver_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-common_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-common_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
linux-libc-dev_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-libc-dev_2.6.26-5_powerpc.deb
linux-manual-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-manual-2.6.26_2.6.26-5_all.deb
linux-patch-debian-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-5_all.deb
linux-source-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-source-2.6.26_2.6.26-5_all.deb
linux-support-2.6.26-1_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-support-2.6.26-1_2.6.26-5_all.deb
linux-tree-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-tree-2.6.26_2.6.26-5_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank [EMAIL PROTECTED] (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])



Bug#496603: marked as done ([linux-image-2.6.26-1-686] module sata_sis has been disable)

2008-09-10 Thread Debian Bug Tracking System

Your message dated Wed, 10 Sep 2008 14:32:58 +
with message-id [EMAIL PROTECTED]
and subject line Bug#496603: fixed in linux-2.6 2.6.26-5
has caused the Debian Bug report #496603,
regarding [linux-image-2.6.26-1-686] module sata_sis has been disable
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 [EMAIL PROTECTED]
immediately.)


-- 
496603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496603
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-image-2.6.26-1-686
Version: 2.6.26-3
Severity: normal

--- Please enter the report below this line. ---

This module has been disable due to a problem between the pata_sis and 
sis5513 modules with same PCI ID, but this problem it does not affect 
at sata_sis module.

The sata_sis module can drive SATA Controler SiS with PCI ID 1039:1183.


--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.25-2-amd64

Debian Release: lenny/sid
  500 unstablewww.debian-multimedia.org 
  500 unstableftp.us.debian.org 
  500 unstabledebian.o-hand.com 
  500 stable  security.debian.org 
  500 stable  ftp.debian.org 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends (Version) | Installed
=-+-=
module-init-tools | 3.4-1
initramfs-tools(= 0.55)  | 0.92f
 OR yaird(= 0.0.13)  | 
 OR linux-initramfs-tool  | 

--- Output from package bug script ---

(xfce4-terminal:4419): Pango-WARNING **: Error loading GPOS table 5503



---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.26-5

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

linux-2.6_2.6.26-5.diff.gz
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-5.diff.gz
linux-2.6_2.6.26-5.dsc
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-5.dsc
linux-doc-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-doc-2.6.26_2.6.26-5_all.deb
linux-headers-2.6.26-1-all-powerpc_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-all-powerpc_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-all_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-all_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-common-vserver_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-common-vserver_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-common_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-common_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
linux-headers-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc-smp_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc64_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.26-1-vserver-powerpc64_2.6.26-5_powerpc.deb
linux-image-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.26-1-vserver-powerpc_2.6.26-5_powerpc.deb
linux-libc-dev_2.6.26-5_powerpc.deb
  to pool/main/l/linux-2.6/linux-libc-dev_2.6.26-5_powerpc.deb
linux-manual-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-manual-2.6.26_2.6.26-5_all.deb
linux-patch-debian-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-5_all.deb
linux-source-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-source-2.6.26_2.6.26-5_all.deb
linux-support-2.6.26-1_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-support-2.6.26-1_2.6.26-5_all.deb
linux-tree-2.6.26_2.6.26-5_all.deb
  to pool/main/l/linux-2.6/linux-tree-2.6.26_2.6.26-5_all.deb



A 

Bug#494144: Significant problem

2008-09-10 Thread Michael Meskes
severity 494144 serious
thanks

I think we have a very severe problem here that must be fixed before Lenny is
released. There may be a solution around that I don't know or see that lies
outside of the kernel and thus the bug should be reassigned, but still I think
this needs a fix before the release.

Now to my reasoning, :

Jordi already pointed out there was a change in kernel
behaviour with 2.6.26 in that the kernel default when not finding symbol
version information. Up to kernel 2.6.25 the kernel called itself tainted and
accepted the module. Since 2.6.26. the kernel throws an error. There is,
however, a way to insmod modules without version information, namely by using
modprobe --force. But this is no longer possible because the kernel is
compiled without setting CONFIG_MODULE_FORCE_LOAD.

This has an effect for all out-of-tree modules, I stumbled upon it by looking
at virtualbox-ose-guest-modules. There simply appears to be no way at all to
include the vboxvfs module which depends on the vboxadd module.

I might be wrong and like to hear what I missed, but if I didn't miss anything
we are in must-fix situation.

Michael

-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
   Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: severity of 494144 is minor

2008-09-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.26
 severity 494144 minor
Bug#494144: Checking versions of the symbols in modules
Severity set to `minor' from `serious'


End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#494144: Checking versions of the symbols in modules

2008-09-10 Thread Bastian Blank
On Thu, Aug 07, 2008 at 03:23:03PM +0200, Jordi Pujol wrote:
 In a kernel already compiled, we install new modules, some of that depend of 
 the others. 
 after starting that kernel, the module who has the dependencies can not find 
 the symbols that uses from the first module, and does not load.

Yes, you don't provide the correct set of symbol versions for the build
of the second module. You even should get a warning from modpost.

 a good solution is done modifying the kernel source,

No.

If you want a real solution, please start with linux-modules-extra-2.6
and add support to save the Module.symvers somewhere in the package and
use them to get correct versions in dependant packages.

Bastian

-- 
Four thousand throats may be cut in one night by a running man.
-- Klingon Soldier, Day of the Dove, stardate unknown



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#267212: DDrunk Driver Taunts Poliice In Colorado

2008-09-10 Thread Elisha Rawe



  
   
Of liberty. Now, later on we shall have to understand the
reigning families of europe. To speak plainly, now refused
to suffer any longer. They said they harold, perhaps. Not
brother alfred. He added a piperack within his reach upon
the right, and.

Bug#498510: Checkpointing missing in openvz enabled kernel

2008-09-10 Thread Ola Lundqvist
Package: linux-2.6
Severity: important
Version: 2.6.26-4

Hi

The CONFIG_VZ_CHECKPOINT is currently set to 'n' which is not
good as the checkpointing function will not work.

Please enable that by setting it to 'm'.

For more information see #497292 and the thread on [EMAIL PROTECTED]

Best regards,

// Ola

-- 
 - Ola Lundqvist ---
/  [EMAIL PROTECTED] Annebergsslingan 37  \
|  [EMAIL PROTECTED]  654 65 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [Debian] Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread Ola Lundqvist
Hi

I have filed an important bug now. It should enter the bug archive
shortly.

Best regards,

// Ola

On Wed, Sep 10, 2008 at 02:57:48PM +0200, maximilian attems wrote:
 On Wed, 10 Sep 2008, Thorsten Schifferdecker wrote:
 
  since you add upstream OpenVZ fixes up to git commit 0f14912e3d2251aff,
  Checkpointing work if enabled if enabled in feature-set/openvz/config,
  but a bug existes in 2.6.24 and 2.6.26, chkpnt with a sit device doesnt
  work, see http://bugzilla.openvz.org/874
 
 can i have an bug report with severity important against linux-2.6
 so that the commited checkpoint enabling really lands in lenny?
 
 thanks
 
 -- 
 maks
 ___
 Debian mailing list
 [EMAIL PROTECTED]
 https://openvz.org/mailman/listinfo/debian
 

-- 
 - Ola Lundqvist ---
/  [EMAIL PROTECTED] Annebergsslingan 37  \
|  [EMAIL PROTECTED]  654 65 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: forcibly merging 497292 498510

2008-09-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.26
 forcemerge 497292 498510
Bug#497292: [linux-2.6] Please enable checkpointing support
Bug#498510: Checkpointing missing in openvz enabled kernel
Forcibly Merged 497292 498510.


End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [Debian] Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread Ola Lundqvist
Hi again

The bug id is now #498510.

Best regards,

// Ola

On Wed, Sep 10, 2008 at 07:28:18PM +0200, Ola Lundqvist wrote:
 Hi
 
 I have filed an important bug now. It should enter the bug archive
 shortly.
 
 Best regards,
 
 // Ola
 
 On Wed, Sep 10, 2008 at 02:57:48PM +0200, maximilian attems wrote:
  On Wed, 10 Sep 2008, Thorsten Schifferdecker wrote:
  
   since you add upstream OpenVZ fixes up to git commit 0f14912e3d2251aff,
   Checkpointing work if enabled if enabled in feature-set/openvz/config,
   but a bug existes in 2.6.24 and 2.6.26, chkpnt with a sit device doesnt
   work, see http://bugzilla.openvz.org/874
  
  can i have an bug report with severity important against linux-2.6
  so that the commited checkpoint enabling really lands in lenny?
  
  thanks
  
  -- 
  maks
  ___
  Debian mailing list
  [EMAIL PROTECTED]
  https://openvz.org/mailman/listinfo/debian
  
 
 -- 
  - Ola Lundqvist ---
 /  [EMAIL PROTECTED] Annebergsslingan 37  \
 |  [EMAIL PROTECTED]  654 65 KARLSTAD  |
 |  http://inguza.com/  +46 (0)70-332 1551   |
 \  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
  ---
 ___
 Debian mailing list
 [EMAIL PROTECTED]
 https://openvz.org/mailman/listinfo/debian
 

-- 
 - Ola Lundqvist ---
/  [EMAIL PROTECTED] Annebergsslingan 37  \
|  [EMAIL PROTECTED]  654 65 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread Mert Dirik
maximilian attems wrote:
 
 did a build test and abicheck went positive like according your
 statements. so enabled it for 2.6.26-6. as 2.6.26-5 upload happened
 today can't say for sure when this will land. depends mostly on
 next upstream stable release. will see to get it into Lenny.
 

Thank you very much!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: tagging 497292

2008-09-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.26
 tags 497292 + pending
Bug#497292: [linux-2.6] Please enable checkpointing support
There were no tags set.
Bug#498510: Checkpointing missing in openvz enabled kernel
Tags added: pending


End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#494144: Checking versions of the symbols in modules

2008-09-10 Thread Jordi Pujol
El Wednesday 10 September 2008 18:00:46 Bastian Blank va escriure:
 If you want a real solution, please start with linux-modules-extra-2.6
 and add support to save the Module.symvers somewhere in the package and
 use them to get correct versions in dependant packages.

thanks, I will try that,

nevertheless consider activating the config option to force loading of 
modules, so that the Debian kernel complies with the guidelines of operation 
following:

Modules without symbol version information can only be loaded on the
exact kernel version for which they were compiled. Modules with symbol
version information can be loaded into more recent kernels as long as
none of the symbols exported by the kernel have changed. This provides
a reasonable level of confidence but does not guarantee that the module
will work.
Authors:  Linus Torvalds [EMAIL PROTECTED]


Jordi,



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#498518: found more in logs

2008-09-10 Thread bugs

I also found this in kern.log. The system is unstable, few reboots were
needed in the last three hours and debian package management utilities and
even other binaries keep segfaulting from time to time (I don't know if
it's the kernel to blame for this or just the /var/lib/dpkg/status or 
/var/lib/dpkg/available files which were corrupted after the kernel bug was
hit).

Sep 10 20:54:44 bogdanflorin kernel: [  219.950230] [ cut here
]
Sep 10 20:54:44 bogdanflorin kernel: [  219.950236] kernel BUG at
mm/slab.c:3008!
Sep 10 20:54:44 bogdanflorin kernel: [  219.950239] invalid opcode: 
[1] SMP 
Sep 10 20:54:44 bogdanflorin kernel: [  219.950241] CPU 1 
Sep 10 20:54:44 bogdanflorin kernel: [  219.950243] Modules linked in:
fglrx(P) ipv6 ppdev lp nls_utf8 nls_cp437 vfat fat nls_base deflate
zlib_deflate zlib_inflate ctr twofish twofish_common camellia serpent
blowfish des_generic cbc aes_x86_64 aes_generic xcbc sha256_generic
sha1_generic crypto_null crypto_blkcipher af_key fuse snd_hda_intel
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd button k8temp i2c_nforce2
soundcore snd_page_alloc i2c_core psmouse serio_raw parport_pc parport
evdev pcspkr reiserfs sg sd_mod sr_mod cdrom ide_pci_generic amd74xx 8139cp
ide_core floppy sata_nv ata_generic libata scsi_mod dock forcedeth 8139too
mii ehci_hcd ohci_hcd thermal processor fan thermal_sys
Sep 10 20:54:44 bogdanflorin kernel: [  219.950282] Pid: 3056, comm: juk
Tainted: P  2.6.26-1-amd64 #1
Sep 10 20:54:44 bogdanflorin kernel: [  219.950285] RIP:
0010:[80295bc7]  [80295bc7]
cache_alloc_refill+0xfa/0x20c
Sep 10 20:54:44 bogdanflorin kernel: [  219.950292] RSP:
0018:81002c4a5c78  EFLAGS: 00010012
Sep 10 20:54:44 bogdanflorin kernel: [  219.950294] RAX: 0002d1b0
RBX: 0296 RCX: 0011
Sep 10 20:54:44 bogdanflorin kernel: [  219.950296] RDX: 
RSI:  RDI: 
Sep 10 20:54:44 bogdanflorin kernel: [  219.950298] RBP: 81000f5e6000
R08: 81003f9f7c00 R09: 81003f82e000
Sep 10 20:54:44 bogdanflorin kernel: [  219.950301] R10: 00730063006f0064
R11: 802f1cd5 R12: 81003f825b40
Sep 10 20:54:44 bogdanflorin kernel: [  219.950303] R13: 81003f9f7c00
R14: 003c R15: 81003f82a9c0
Sep 10 20:54:44 bogdanflorin kernel: [  219.950306] FS: 
7f82f0562780() GS:81003f9fb9c0() knlGS:7eb92b90
Sep 10 20:54:44 bogdanflorin kernel: [  219.950308] CS:  0010 DS:  ES:
 CR0: 8005003b
Sep 10 20:54:44 bogdanflorin kernel: [  219.950310] CR2: 7f47648c6000
CR3: 2c489000 CR4: 06e0
Sep 10 20:54:44 bogdanflorin kernel: [  219.950312] DR0: 
DR1:  DR2: 
Sep 10 20:54:44 bogdanflorin kernel: [  219.950314] DR3: 
DR6: 0ff0 DR7: 0400
Sep 10 20:54:44 bogdanflorin kernel: [  219.950317] Process juk (pid: 3056,
threadinfo 81002c4a4000, task 81003da880c0)
Sep 10 20:54:44 bogdanflorin kernel: [  219.950319] Stack: 
00d0 0296 81003f82a9c0 00d0
Sep 10 20:54:44 bogdanflorin kernel: [  219.950323]  
81002c4a5eb8 81002c4a5d98 80295e81
Sep 10 20:54:44 bogdanflorin kernel: [  219.950327]  fffe
81000f5ef3c0 81002c4a5d98 802ab14d
Sep 10 20:54:44 bogdanflorin kernel: [  219.950331] Call Trace:
Sep 10 20:54:44 bogdanflorin kernel: [  219.950338]  [80295e81] ?
kmem_cache_alloc+0x78/0xf6
Sep 10 20:54:44 bogdanflorin kernel: [  219.950342]  [802ab14d] ?
d_alloc+0x24/0x1a8
Sep 10 20:54:44 bogdanflorin kernel: [  219.950348]  [802a19a9] ?
do_lookup+0xb2/0x1c1
Sep 10 20:54:44 bogdanflorin kernel: [  219.950355]  [802a3b2c] ?
__link_path_walk+0x87a/0xd05
Sep 10 20:54:44 bogdanflorin kernel: [  219.950366]  [a02c8393] ?
:fat:__fat_readdir+0x8fe/0x912
Sep 10 20:54:44 bogdanflorin kernel: [  219.950374]  [802a3ffd] ?
path_walk+0x46/0x8b
Sep 10 20:54:44 bogdanflorin kernel: [  219.950380]  [802a4329] ?
do_path_lookup+0x158/0x1cf
Sep 10 20:54:44 bogdanflorin kernel: [  219.950383]  [802a3134] ?
getname+0x140/0x1a7
Sep 10 20:54:44 bogdanflorin kernel: [  219.950388]  [802a4c98] ?
__user_walk_fd+0x37/0x4c
Sep 10 20:54:44 bogdanflorin kernel: [  219.950394]  [80299a48] ?
sys_faccessat+0xbc/0x186
Sep 10 20:54:44 bogdanflorin kernel: [  219.950399]  [802b0343] ?
mnt_drop_write+0x25/0xdd
Sep 10 20:54:44 bogdanflorin kernel: [  219.950403]  [802a68c5] ?
vfs_readdir+0x92/0xa7
Sep 10 20:54:44 bogdanflorin kernel: [  219.950409]  [802a6b32] ?
sys_getdents+0xaf/0xbd
Sep 10 20:54:44 bogdanflorin kernel: [  219.950415]  [8020be9a] ?
system_call_after_swapgs+0x8a/0x8f
Sep 10 20:54:44 bogdanflorin kernel: [  219.950422] 
Sep 10 20:54:44 bogdanflorin kernel: [  219.950423] 
Sep 10 20:54:44 bogdanflorin kernel: [  

Re: Scheduling linux-2.6 2.6.26-5

2008-09-10 Thread Kir Kolyshkin

maximilian attems wrote:

On Wed, Sep 10, 2008 at 02:09:52PM +0400, Kir Kolyshkin wrote:
  
If it's still possible to change this option, please do it. 
Checkpointing is now working fine, it's totally our fault that we forgot 
to switch the relative option.


So, please set CONFIG_VZ_CHECKPOINT=m. From the ABI point of view this 
adds two new ioctl()s for /dev/vzctl, nothing more.



thanks kir and pavel for input.

did a build test and abicheck went positive like according your
statements. so enabled it for 2.6.26-6. as 2.6.26-5 upload happened
today can't say for sure when this will land. depends mostly on
next upstream stable release. will see to get it into Lenny.

Thanks a lot Max!


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#497505: virtualbox-ose doesn't work with linux 2.6.26

2008-09-10 Thread Stefan Lippers-Hollmann
Hi

Just as a status update, Ubuntu has added a patch[1], disabling interrupts 
in the critical boot up path, to their kernel today, which avoids this 
issue from triggering - and after initial testing, it seems to succeed.

On the other hand, looking at the VirtualBox bug tracker[2], it seems to 
have been identified as a real bug in VirtualBox' recompiler (which is 
supposed to have been fixed in VirtualBox 2.0.2).

Given the circumstances that this patch to the kernel only seems to paper
around the real issue, I do not recommend to add it to Debian's kernel 
though.

Regards
Stefan Lippers-Hollmann

[1] 
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commitdiff;h=00d6c877bc34ff6e2705385764f6e7426cd362a8
[2] http://www.virtualbox.org/ticket/1875#comment:7


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


Bug#498536: .26 breaks firmware loading for qla2xxx on sparc

2008-09-10 Thread Josip Rodin
Package: linux-image-2.6.26-1-sparc64-smp
Version: 2.6.26-4
Severity: grave
Tags: upstream

Hi,

qla2xxx's firmware loading thingy got hosed between .25 and .26,
I've already reported something along these lines to upstream, but I just
verified it with our kernel image so I'm filing it here too.

[egin: Loading essential drivers... ...
49.444722] SCSI subsystem initialized
[   49.524563] QLogic Fibre Channel HBA Driver: 8.02.01-k4-debug
[   49.602779] qla2xxx 0001:00:04.0: Found an ISP2200, irq 19, iobase 0x07fd
[010
[   49.714344] qla2xxx 0001:00:04.0: Configuring PCI space...
[   49.789041] scsi(0): No matching ROM signature.
[   49.851178] qla2xxx 0001:00:04.0: Configure NVRAM parameters...
[   50.025526] qla2xxx 0001:00:04.0: Inconsistent NVRAM detected: checksum=0x0 i
L=4qla2xxx 0001:00:04.0: Falling back to functioning (yet invalid -- WWPN) def
Bults.
[   50.230463] scsi(0): NVRAM configuration failed!
[   50.293695] qla2xxx 0001:00:04.0: Verifying loaded RISC code...
[   50.373898] scsi(0):  Load RISC code 
0   50.449209] firmware: requesting ql2200_fw.bin
[  110.508456] scsi(0): Failed to load firmware image (ql2200_fw.bin).
[  110.593119] qla2xxx 0001:00:04.0: Firmware image unavailable.
[  110.671025] qla2xxx 0001:00:04.0: Firmware images can be retrieved from: ftp:
[/ftp.qlogic.com/outgoing/linux/firmware/.
d  110.819988] scsi(0): Setup chip  FAILED .
a  110.884362] qla2xxx 0001:00:04.0: Failed to initialize adapter
[  110.963425] scsi(0): Failed to initialize adapter - Adapter flags 10.
[one.

-- 
 2. That which causes joy or happiness.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: severity of 498536 is important

2008-09-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.26
 severity 498536 important
Bug#498536: .26 breaks firmware loading for qla2xxx on sparc
Severity set to `important' from `grave'


End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: severity of 498536 is important

2008-09-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.10.35
 severity 498536 important
Bug#498536: .26 breaks firmware loading for qla2xxx on sparc
Severity set to `important' from `important'


End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#498472: linux-image-2.6.26-1-xen-686: does not boot under Etch Xen

2008-09-10 Thread Ian Campbell
On Wed, 2008-09-10 at 12:57 +0200, Ferenc Wagner wrote:
 Ian Campbell [EMAIL PROTECTED] writes:
 
  On Wed, 2008-09-10 at 11:01 +0200, Ferenc Wagner wrote:
  [0.080644] EIP is at xen_write_cr4+0x2/0x6
 
  Unfortunately the 3.0.3 hypervisor is stricter in what it will allow CR4
  to be set to than necessary and won't allow some of the fields which
  newer kernels use. I think we are unlikely to fix this in the kernel in
  Debian. You could ask upstream but I'm not sure they would want/be able
  to change this behaviour.
 
 Hi Ian,
 
 thanks for the quick and very informative response!  Is it enough if I
 upgrade to 3.2.0-3~bpo4+2 or should I go for 3.2.1-2 in Lenny?

I don't recall when the relaxation of cr4 changes happened. Newer is
normally better ( ;-) ) but 3.2.0 is probably worth a go if you have an
aversion to 3.2.1.

 Interesting, though, that a CR flag changed going from rc8 to final...

it was probably side effect of an otherwise innocent looking change...

-- 
Ian Campbell

BOFH excuse #87:

Password is too complex to decrypt


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


Weirdity in linux-modules-extra-2.6

2008-09-10 Thread Steve McIntyre
Hi folks,

I've been tracking down a build failure in the current lenny
multi-arch i386/amd64/powerpc/source DVD. What I've found is an oddity
in the Sources.gz file: the stanza for the source package
linux-modules-extra-2.6 does not list the powerpc packages generated
it in the Binary: field. This seems to be the case for both lenny and
sid. Is that a bug in the package, or somewhere else (e.g. dak)?

Cheers,
-- 
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
We don't need no education.
We don't need no thought control.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Weirdity in linux-modules-extra-2.6

2008-09-10 Thread Bastian Blank
On Wed, Sep 10, 2008 at 11:49:51PM +0100, Steve McIntyre wrote:
 I've been tracking down a build failure in the current lenny
 multi-arch i386/amd64/powerpc/source DVD. What I've found is an oddity
 in the Sources.gz file: the stanza for the source package
 linux-modules-extra-2.6 does not list the powerpc packages generated
 it in the Binary: field. This seems to be the case for both lenny and
 sid. Is that a bug in the package, or somewhere else (e.g. dak)?

Its in apt, it crops the Binary field. See #489296.

Bastian

-- 
Yes, it is written.  Good shall always destroy evil.
-- Sirah the Yang, The Omega Glory, stardate unknown


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#498548: linux-image-2.6.26-1-686: SKB BUG: Invalid truesize

2008-09-10 Thread Emiliano Castagnari
Package: linux-image-2.6.26-1-686
Version: 2.6.26-4
Severity: important


I am getting this kernel messages at least 9 times per second. 
I belive there is a patch to this problem, I dont know if it is already aplied 
in the current package.

  http://marc.info/?l=linux-netdevm=116284186427122w=2

-- Package-specific info:
** Version:
Linux version 2.6.26-1-686 (Debian 2.6.26-4) ([EMAIL PROTECTED]) (gcc version 
4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 12:00:54 UTC 
2008

** Command line:
root=/dev/md0 ro quiet vga=791

** Not tainted

** Kernel log:
[32302.869912] SKB BUG: Invalid truesize (276) len=126, sizeof(sk_buff)=180
[32302.874730] SKB BUG: Invalid truesize (276) len=118, sizeof(sk_buff)=180
[32302.887026] SKB BUG: Invalid truesize (276) len=118, sizeof(sk_buff)=180
[32302.905774] SKB BUG: Invalid truesize (308) len=142, sizeof(sk_buff)=180
[32302.906150] SKB BUG: Invalid truesize (276) len=118, sizeof(sk_buff)=180
[32302.910099] SKB BUG: Invalid truesize (276) len=110, sizeof(sk_buff)=180
[32302.910099] SKB BUG: Invalid truesize (276) len=110, sizeof(sk_buff)=180
...

** Loaded modules:
Module  Size  Used by
tun 8292  2 
xt_iprange  2272  4 
xt_limit2180  12 
xt_tcpudp   2816  292 
xt_state2016  1 
iptable_mangle  2688  0 
iptable_filter  2624  1 
xt_multiport2816  0 
ipt_LOG 5028  11 
nf_conntrack_irc5124  0 
nf_nat_ftp  2528  0 
nf_conntrack_ftp6852  1 nf_nat_ftp
iptable_nat 4680  1 
nf_nat 15576  2 nf_nat_ftp,iptable_nat
nf_conntrack_ipv4  12268  4 iptable_nat,nf_nat
nf_conntrack   55508  7 
xt_state,nf_conntrack_irc,nf_nat_ftp,nf_conntrack_ftp,iptable_nat,nf_nat,nf_conntrack_ipv4
ip_tables  10160  3 iptable_mangle,iptable_filter,iptable_nat
x_tables   13284  8 
xt_iprange,xt_limit,xt_tcpudp,xt_state,xt_multiport,ipt_LOG,iptable_nat,ip_tables
authenc 5056  38 
xfrm4_mode_tunnel   2304  76 
video  16400  0 
output  2912  1 video
ac  4196  0 
battery10180  0 
xfrm_user  17760  2 
xfrm4_tunnel2304  0 
tunnel4 3016  1 xfrm4_tunnel
ipcomp  5288  0 
esp45600  38 
aead6400  2 authenc,esp4
ah4 4416  0 
ipv6  235204  14 
deflate 2624  0 
zlib_deflate   17624  1 deflate
zlib_inflate   14144  1 deflate
ctr 3936  0 
twofish 8224  0 
twofish_common 13888  1 twofish
camellia   19136  0 
serpent18688  0 
blowfish8352  0 
des_generic16672  38 
cbc 3264  38 
aes_i5867744  0 
aes_generic29256  1 aes_i586
xcbc4296  0 
sha256_generic 11360  0 
sha1_generic2304  4 
crypto_null 2880  0 
crypto_blkcipher   15236  42 authenc,ctr,cbc,crypto_null
af_key 25428  0 
loop   12748  0 
snd_pcm62628  0 
snd_timer  17800  1 snd_pcm
snd45604  2 snd_pcm,snd_timer
soundcore   6368  1 snd
parport_pc 22500  0 
parport30988  1 parport_pc
snd_page_alloc  7816  1 snd_pcm
serio_raw   4740  0 
i2c_i8017920  0 
psmouse32336  0 
i2c_core   19828  1 i2c_i801
intel_rng   4576  0 
rng_core3940  2 intel_rng
iTCO_wdt9508  0 
pcspkr  2432  0 
button  6064  0 
intel_agp  22300  0 
agpgart28776  1 intel_agp
i82875p_edac4936  0 
edac_core  36144  3 i82875p_edac
shpchp 25528  0 
pci_hotplug23460  1 shpchp
evdev   8000  0 
ext3  105256  7 
jbd39444  1 ext3
mbcache 7108  1 ext3
raid1  18016  5 
md_mod 67036  6 raid1
sd_mod 22200  16 
ata_piix   14180  14 
ata_generic 4676  0 
libata140416  2 ata_piix,ata_generic
scsi_mod  129356  2 sd_mod,libata
piix6568  0 [permanent]
dock8272  1 libata
floppy 47716  0 
ide_pci_generic 3908  0 [permanent]
ide_core   92628  2 piix,ide_pci_generic
e100   28908  0 
e1000 102624  0 
mii 4896  1 e100
ehci_hcd   28428  0 
uhci_hcd   18672  0 
usbcore   118160  3 ehci_hcd,uhci_hcd
thermal15228  0 
processor  32576  1 thermal
fan   

Bug#498548: linux-image-2.6.26-1-686: SKB BUG: Invalid truesize

2008-09-10 Thread dann frazier
On Wed, Sep 10, 2008 at 09:30:43PM -0400, Emiliano Castagnari wrote:
 Package: linux-image-2.6.26-1-686
 Version: 2.6.26-4
 Severity: important
 
 
 I am getting this kernel messages at least 9 times per second. 
 I belive there is a patch to this problem, I dont know if it is already 
 aplied in the current package.
 
   http://marc.info/?l=linux-netdevm=116284186427122w=2

yeah, that patch went in years ago. This is a more current report, but
might not be the same thing:
  http://marc.info/?l=linux-netdevm=121674755618486w=2

Your best bet maybe to file a bug upstream at
http://bugzilla.kernel.org. Did this start occuring after a kernel
upgrade? If so, you might be able to help find the problem by
bisecting - see http://wiki.debian.org/DebianKernelReportingBugs for
more information.

-- 
dann frazier




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#497843: marked as done (linux-2.6: [s390] 2.6.26 does not boot in Hercules emulator)

2008-09-10 Thread Debian Bug Tracking System

Your message dated Thu, 11 Sep 2008 07:11:41 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#497843: linux-2.6: [s390] 2.6.26 does not boot in Hercules 
emulator
has caused the Debian Bug report #497843,
regarding linux-2.6: [s390] 2.6.26 does not boot in Hercules emulator
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 [EMAIL PROTECTED]
immediately.)


-- 
497843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497843
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.26-1
Tags: fixed-upstream, d-i

Current 2.6.26 kernels [1] will fail to boot in the Hercules emulator:

Begin: Running /scripts/init-premount ...
23.398929! dasd(eckd): 0.0.0120: PSF-SSC on storage subsystem HRC.ZZ
0001.0120 returned rc=0
23.401291! dasd_generic couldn't online device 0.0.0120 with discipline 
ECKD rc=-5

This should be fixed with upstream stable release 2.6.26.4 which is currently
being prepared with commit 49fd38bdaa96f093fcad3176a781a4d0de8f8602.

[1] The same issue was also there in 2.6.25; 2.6.24-7 is the last good version.


---End Message---
---BeginMessage---
Version: 2.6.26-5

Fixed with new upload based on upstream 2.6.26.4.

---End Message---