Processing commands for [EMAIL PROTECTED]:
> severity 409435 important
Bug#409435: linux-image-2.6.18-4-amd64: old version of libdevmapper1.02
installed == eat filesystem on pvmove
Severity set to `important' from `critical'
> thanks
Stopping processing here.
Please contact me if you need assis
severity 409435 important
thanks
On Sat, Feb 03, 2007 at 03:21:31AM +0100, Marc Lehmann wrote:
> I just upgraded to 2.6.18.4 and tried pvmove /dev/hdc1 /dev/sda1
> Result (dmesg):
>device-mapper: mirror log: unrecognised sync argument to mirror log: 2
>device-mapper: table: 254:3: mirror
Package: linux-image-2.6.18-4-amd64
Version: 2.6.18.dfsg.1-9
Severity: critical
Justification: causes serious data loss
I just upgraded to 2.6.18.4 and tried pvmove /dev/hdc1 /dev/sda1
Result (dmesg):
device-mapper: mirror log: unrecognised sync argument to mirror log: 2
device-mapper: ta
Package: linux-image-2.6.18-3-powerpc64
Version: 2.6.18-7
Severity: important
Fan control doesn't work properly: Using this kernel on my
first-gen iMac G5 causes it to overheat if the ambient
temperature is in the high twenties (Celsius) or above.
(The computer shuts down and refuses to start up
Package: linux-image-2.6-vserver-686
Version: 2.6.18+5
Followup-For: Bug #404777
Heres my kernel error when i stop a vserver
Jan 31 23:40:33 localhost kernel: BUG: unable to handle kernel NULL pointer
dereference at virtual address
Jan 31 23:40:33 localhost kernel: printing eip:
Jan 31
Accepted:
kernel-image-2.6-power3-smp_2.6.18+6_powerpc.deb
to
pool/main/l/linux-latest-2.6/kernel-image-2.6-power3-smp_2.6.18+6_powerpc.deb
kernel-image-2.6-power3_2.6.18+6_powerpc.deb
to pool/main/l/linux-latest-2.6/kernel-image-2.6-power3_2.6.18+6_powerpc.deb
kernel-image-2.6-power4-smp_2.6
linux-latest-2.6_6_powerpc.changes uploaded successfully to localhost
along with the files:
linux-latest-2.6_6.dsc
linux-latest-2.6_6.tar.gz
linux-image-powerpc_2.6.18+6_powerpc.deb
linux-image-2.6-powerpc_2.6.18+6_powerpc.deb
linux-headers-2.6-powerpc_2.6.18+6_powerpc.deb
linux-image-p
Your message dated Fri, 02 Feb 2007 14:17:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401183: fixed in linux-2.6 2.6.18.dfsg.1-10
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 02 Feb 2007 14:17:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401183: fixed in linux-2.6 2.6.18.dfsg.1-10
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 02 Feb 2007 14:17:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#379090: fixed in linux-2.6 2.6.18.dfsg.1-10
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Fri, 02 Feb 2007 14:17:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#406181: fixed in linux-2.6 2.6.18.dfsg.1-10
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Accepted:
linux-2.6_2.6.18.dfsg.1-10.diff.gz
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-10.diff.gz
linux-2.6_2.6.18.dfsg.1-10.dsc
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-10.dsc
linux-doc-2.6.18_2.6.18.dfsg.1-10_all.deb
to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-10
linux-2.6_2.6.18.dfsg.1-10_powerpc.changes uploaded successfully to localhost
along with the files:
linux-2.6_2.6.18.dfsg.1-10.dsc
linux-2.6_2.6.18.dfsg.1-10.diff.gz
linux-doc-2.6.18_2.6.18.dfsg.1-10_all.deb
linux-manual-2.6.18_2.6.18.dfsg.1-10_all.deb
linux-patch-debian-2.6.18_2.6.18.dfs
dann frazier wrote:
hey Martin,
Thanks for your detailed investigation.
Can you reproduce with the latest trunk builds? I didn't see any
changesets upstream that obviously fix this issue, but just in case...
Trunk builds can be installed from here:
deb http://kernel-archive.buildserver.net/deb
On Thu, Feb 01, 2007 at 08:27:58AM +0100, Mauro Sanna wrote:
>
> -- Package-specific info:
> -- /proc/cmdline
> root=/dev/mapper/vg00-root ro
ok looks good.
> I've installed sarge with lvm and kernel 2.6.8 with initrd.
> At the end of installation I reboot the system and all works
> well.
> The
Processing commands for [EMAIL PROTECTED]:
> reassign 409347 linux-image-2.6.18-amd64
Bug#409347: kernel: rsync create bad file on udf filesystem
Warning: Unknown package 'linux-image-2.6.18-amd64'
Bug reassigned from package `kernel' to `linux-image-2.6.18-amd64'.
> tags 409347 moreinfo
Bug#409
reassign 409347 linux-image-2.6.18-amd64
tags 409347 moreinfo
stop
On Fri, Feb 02, 2007 at 09:34:07AM +0100, Jean-Michel wrote:
> Package: kernel
> Severity: normal
for the next time fill the bug against the linux image
package you are using.
> After doing an
> rsync -r --max-size=600M /pa
Your message dated Fri, 2 Feb 2007 10:02:18 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385095: linux-image-2.6.17-2-k7: Flaky mouse and sluggish
interactive response
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been de
On Thu, Feb 01, 2007 at 10:14:10AM +0100, Matthias Popp wrote:
> Hallo,
>
> Why is kernel 2.6.19 removed from here ?
>
> http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/
just use the 2.6.20-rc6
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: kernel
Severity: normal
After doing an
rsync -r --max-size=600M /partages/users/Restauration
$DEST/__.../
Some inodes seems corrupted:
ls -l /mnt/iomega/./#Root/gay
drwxr-x--- 4 root root 696 2007-02-01 21:35 lebel
drwxr-x--- 2 root root
Your message dated Fri, 2 Feb 2007 09:26:06 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#398136: Failure to reclaim swap in 2.6.18-2-ixp4xx
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
On Thu February 1 2007 12:13, you wrote:
> Sorry, Mike, for not responding earlier but I don't have enough
> knowledge to say information of value about this issue. Do you think
> you could describe this problem on the kernel mailing list? Of
> course, this assumes there is a real problem. I'll
22 matches
Mail list logo