Bug#535006: nfs-kernel-server: errors in dmesg

2010-02-11 Thread Christoph Kaminski

Ben Hutchings schrieb:
 > Right, looks reasonable.  Actually I should have read this off the

original log messages.

It looks like this is a known regression, and not yet solved:
.  We'll track that
bug report and pick up any fixes for it.

Please could you test whether this has somehow been fixed in Linux
2.6.32, currently in unstable?

Ben.


have since 4-6 Weeks .32 running and it looks good...

Greetz



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



Boot problem in squeeze

2010-02-11 Thread Lars Segerlund
 Hello,

 I have a Sony Vaio TX3 ( VGN-TX3XT ) , which runs a on an intel
celeron ULW, and has a i945g graphics chip.

 I have reinstalled with the squeeze install cd, but cannot boot the
kernels on the machine.

 I can get into the machine from the rescue mode on the installer, (
if I chroot into the env. it looks fairly ok ).

 I can boot memtest86 and memtest86+ from the boot menu on the hd, but
not the kernels.

 I have looked at the initrd and it looks ok, ( atleast it is possible
to gunzip, and un cpio it and have a look around ).

 grub2 reads the initrd image, unpacks the kernel and hans after
writing 'Booting the kernel'

 I have tried noapic nolapic acpi=off no-hlt no-irq nomodeset and most
options I can find to the kernel.
 I suspect it hangs partly into the linux init() function, and if i
set vga=788 or vga=777 the text clears and I am greeted with a blank
screen ... ( vga=788 is what the installer cd uses ).

 I have tried linux-image-2.6.32-trunk-686,
linux-image-2.6.32-trunk-486 , linux-image-2.6.30-trunk-686 to no
avail.

 I suspect I am loosing the display so that I don't get the kernel
output, and I don't have a serial port on it.

 I simply does not know howto continue debugging this, does anyone
have any idea?

 Any help apreciated.

 Next I will build the kernel from source on the system, and try.

 / regards, Lars Segerlund.


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



Processed (with 1 errors): taggin

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

> tags 564198 + sid squeeze
Bug #564198 [hexxagon] hexxagon: FTBFS error: __simple is not a valid template 
argument for type bool
Added tag(s) squeeze and sid.
> severity 565654 important
Bug #565654 [initramfs-tools] Debian Bug Tracking System - revised ( did not 
store narrative)
Severity set to 'important' from 'serious'

> tags 565654 + moreinfo
Bug #565654 [initramfs-tools] Debian Bug Tracking System - revised ( did not 
store narrative)
Added tag(s) moreinfo.
> tags 566514 + sid squeeze
Bug #566514 [java-gcj-compat] gcc-defaults makes java-gcj-compat-headless 
uninstallable
Added tag(s) squeeze and sid.
> tags 566763 + sid squeeze
Bug #566763 [src:opensync] FTBFS: lib/libcheck.a: could not read symbols: Bad 
value
Added tag(s) squeeze and sid.
> tags 566765 + sid squeeze
Bug #566765 {Done: Thorsten Glaser } [src:hercules] FTBFS: 
/bin/sh: Can't open ../autoconf/mkinstalldirs
Added tag(s) squeeze and sid.
> tags 568072 + sid squeeze
Bug #568072 {Done: Michael Banck } [opensync-plugin-syncml] 
opensync-plugin-syncml: package uninstallable.
Added tag(s) squeeze and sid.
> takk
Unknown command or malformed arguments to command.

>
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 debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Incomplete upload found in Debian upload queue

2010-02-11 Thread Archive Administrator
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
  linux-2.6_2.6.32-8.diff.gz
  linux-2.6_2.6.32-8.dsc
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.

If no .changes file arrives within 23:27:44, the files will be deleted.

If you didn't upload those files, please just ignore this message.

Greetings,

Your Debian queue daemon (running on host ries.debian.org)


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



Processing of linux-2.6_2.6.32-8_multi.changes

2010-02-11 Thread Archive Administrator
linux-2.6_2.6.32-8_multi.changes uploaded successfully to localhost
along with the files:
  linux-2.6_2.6.32-8.dsc
  linux-2.6_2.6.32-8.diff.gz
  linux-support-2.6.32-2_2.6.32-8_all.deb
  linux-patch-debian-2.6.32_2.6.32-8_all.deb
  firmware-linux-free_2.6.32-8_all.deb
  linux-source-2.6.32_2.6.32-8_all.deb
  linux-doc-2.6.32_2.6.32-8_all.deb
  linux-manual-2.6.32_2.6.32-8_all.deb
  linux-headers-2.6.32-2-486_2.6.32-8_i386.deb
  linux-image-2.6.32-2-486_2.6.32-8_i386.deb
  linux-headers-2.6.32-2-686_2.6.32-8_i386.deb
  linux-image-2.6.32-2-686_2.6.32-8_i386.deb
  linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
  linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
  linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
  linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
  linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb
  linux-libc-dev_2.6.32-8_i386.deb
  linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb

Greetings,

Your Debian queue daemon (running on host ries.debian.org)


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



Bug#569329: marked as done (bnx2: Please add PCI IDs for BCM5716)

2010-02-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Feb 2010 14:43:06 +0100
with message-id <4b74096a.3050...@mgoetze.net>
and subject line Re: Bug#569329: Acknowledgement (bnx2: Please add PCI IDs for 
BCM5716)
has caused the Debian Bug report #569329,
regarding bnx2: Please add PCI IDs for BCM5716
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
569329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux-2.6
Version: 2.6.26-21
Severity: normal
Tags: patch lenny

The bnx2 driver fails to work with BCM5716 network cards such as those
in the latest Dell servers. As far as I know, the driver should work
fine, it just doesn't recognize the PCI IDs. Please consider adding a
patch similar to the following (which is against 2.6.24 but, as far as I
can see, should apply except for the version info):

http://launchpadlibrarian.net/35888957/bcm5716-patch-linux-2.6.24.diff

Thanks,
Michael


--- End Message ---
--- Begin Message ---
Nevermind, I missed that this was already reported in #565353.

--- End Message ---


Bug#569329: bnx2: Please add PCI IDs for BCM5716

2010-02-11 Thread Michael Goetze
Source: linux-2.6
Version: 2.6.26-21
Severity: normal
Tags: patch lenny

The bnx2 driver fails to work with BCM5716 network cards such as those
in the latest Dell servers. As far as I know, the driver should work
fine, it just doesn't recognize the PCI IDs. Please consider adding a
patch similar to the following (which is against 2.6.24 but, as far as I
can see, should apply except for the version info):

http://launchpadlibrarian.net/35888957/bcm5716-patch-linux-2.6.24.diff

Thanks,
Michael



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



linux-2.6_2.6.32-8_multi.changes is NEW

2010-02-11 Thread Archive Administrator
firmware-linux-free_2.6.32-8_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-8_all.deb
linux-2.6_2.6.32-8.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-8.diff.gz
linux-2.6_2.6.32-8.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-8.dsc
linux-doc-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-8_all.deb
(new) linux-headers-2.6.32-2-486_2.6.32-8_i386.deb optional kernel
Header files for Linux 2.6.32-2-486
 This package provides the architecture-specific kernel header files for
 Linux kernel 2.6.32-2-486, generally used for building out-of-tree kernel
 modules.  These files are going to be installed into
 /usr/src/linux-headers-2.6.32-2-486, and can be used for building modules
 that load into the kernel provided by the linux-image-2.6.32-2-486
 package.
(new) linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb optional kernel
Header files for Linux 2.6.32-2-686-bigmem
 This package provides the architecture-specific kernel header files for
 Linux kernel 2.6.32-2-686-bigmem, generally used for building out-of-tree
 kernel modules.  These files are going to be installed into
 /usr/src/linux-headers-2.6.32-2-686-bigmem, and can be used for building
 modules that load into the kernel provided by the
 linux-image-2.6.32-2-686-bigmem package.
(new) linux-headers-2.6.32-2-686_2.6.32-8_i386.deb optional kernel
Header files for Linux 2.6.32-2-686
 This package provides the architecture-specific kernel header files for
 Linux kernel 2.6.32-2-686, generally used for building out-of-tree kernel
 modules.  These files are going to be installed into
 /usr/src/linux-headers-2.6.32-2-686, and can be used for building modules
 that load into the kernel provided by the linux-image-2.6.32-2-686
 package.
(new) linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb optional kernel
All header files for Linux 2.6.32
 This package depends against all architecture-specific kernel header files
 for Linux kernel version 2.6.32, generally used for building out-of-tree
 kernel modules.
linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
(new) linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb optional 
kernel
Header files for Linux 2.6.32-2-vserver-686-bigmem
 This package provides the architecture-specific kernel header files for
 Linux kernel 2.6.32-2-vserver-686-bigmem, generally used for building
 out-of-tree kernel modules.  These files are going to be installed into
 /usr/src/linux-headers-2.6.32-2-vserver-686-bigmem, and can be used for
 building modules that load into the kernel provided by the
 linux-image-2.6.32-2-vserver-686-bigmem package.
(new) linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb optional kernel
Header files for Linux 2.6.32-2-vserver-686
 This package provides the architecture-specific kernel header files for
 Linux kernel 2.6.32-2-vserver-686, generally used for building out-of-tree
 kernel modules.  These files are going to be installed into
 /usr/src/linux-headers-2.6.32-2-vserver-686, and can be used for building
 modules that load into the kernel provided by the
 linux-image-2.6.32-2-vserver-686 package.
(new) linux-image-2.6.32-2-486_2.6.32-8_i386.deb optional kernel
Linux 2.6.32 for old PCs
 The Linux kernel 2.6.32 and modules for use on PCs with a 486, Pentium or
 compatible processor.
(new) linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb optional kernel
Linux 2.6.32 for PCs with 4GB+ RAM
 The Linux kernel 2.6.32 and modules for use on PCs with 4-64GB RAM, using
 PAE (Physical Address Extension).
 .
 This kernel also runs on a Xen hypervisor.  It supports only unprivileged
 (domU) operation.
(new) linux-image-2.6.32-2-686_2.6.32-8_i386.deb optional kernel
Linux 2.6.32 for modern PCs
 The Linux kernel 2.6.32 and modules for use on PCs with Intel Pentium
 Pro/II/III/4/4M/D/M, Xeon, Celeron, Core or Atom; AMD K6, Geode LX/NX,
 Athlon (K7), Duron, Opteron, Sempron, Turion or Phenom; Transmeta
 Efficeon; VIA C3 "Nehemiah" or C7 processors.
linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
(new) linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb optional kernel
Linux 2.6.32 for PCs with 4GB+ RAM, Linux-VServer support
 The Linux kernel 2.6.32 and modules for use on PCs with 4-64GB RAM, using
 PAE (Physical Address Extension).
 .
 This kernel includes support for Linux-VServer virtualization.
 .
 This kernel also runs on a Xen hypervisor.  It supports only unprivileged
 (domU) operation.
(new) linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb optional kernel
Linux 2.6.32 for modern PC

Processed: reassign linux-image-2.6.32-1-amd64 / open-iscsi amd64 login hang

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

> reassign 502845 linux-image-2.6.32-1-amd64
Bug #502845 [linux-image-2.6.18-6-amd64] open-iscsi: no login using amd64
Bug reassigned from package 'linux-image-2.6.18-6-amd64' to 
'linux-image-2.6.32-1-amd64'.
> 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#502845: linux-image-2.6.32-1-amd64 / open-iscsi amd64 login hang

2010-02-11 Thread Florian Lohoff
reassign linux-image-2.6.32-1-amd64
thanks

Hi,
the bug is still existant on amd64 with kernel image linux-image-2.6.32-1-amd64.

Still all attempts to mount an iscsi target with open-iscsi leads
to a hang in the --login ...

Renders open-iscsi unusable for amd64 ...

strace Log of an open-iscsi login which hangs ...

11280 execve("/usr/bin/iscsiadm", ["iscsiadm", "-m", "node", "--targetname", 
"iqn.1997-01.org.rfc822.lab.t4:st"..., "--portal", "195.71.99.251:3260", 
"--login"], [/* 14 vars */]) = 0
11280 brk(0)= 0x8cfb000
11280 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
11280 mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0xf77d2000
11280 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
11280 open("/etc/ld.so.cache", O_RDONLY) = 3
11280 fstat64(3, {st_mode=S_IFREG|0644, st_size=26171, ...}) = 0
11280 mmap2(NULL, 26171, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf77cb000
11280 close(3)  = 0
11280 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
11280 open("/lib/i686/cmov/libc.so.6", O_RDONLY) = 3
11280 read(3, 
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260e\1\0004\0\0\0\4"..., 512) 
= 512
11280 fstat64(3, {st_mode=S_IFREG|0755, st_size=1413540, ...}) = 0
11280 mmap2(NULL, 1418864, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 
0) = 0xf767
11280 mmap2(0xf77c5000, 12288, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x155) = 0xf77c5000
11280 mmap2(0xf77c8000, 9840, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xf77c8000
11280 close(3)  = 0
11280 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0xf766f000
11280 set_thread_area({entry_number:-1 -> 12, base_addr:0xf766f6b0, 
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, 
seg_not_present:0, useable:1}) = 0
11280 mprotect(0xf77c5000, 4096, PROT_READ) = 0
11280 munmap(0xf77cb000, 26171) = 0
11280 rt_sigaction(SIGINT, {0x8066bc0, [], 0}, {SIG_DFL}, 8) = 0
11280 umask(0177)   = 022
11280 getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
11280 setrlimit(RLIMIT_NOFILE, {rlim_cur=16*1024, rlim_max=16*1024}) = 0
11280 access("/etc/iscsi/", F_OK)   = 0
11280 mmap2(NULL, 462848, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0xf75fe000
11280 access("/var/lock/iscsi", F_OK)   = 0
11280 open("/var/lock/iscsi/lock", O_RDWR|O_CREAT, 0666) = 3
11280 close(3)  = 0
11280 link("/var/lock/iscsi/lock", "/var/lock/iscsi/lock.write") = 0
11280 access("/etc/iscsi/ifaces", F_OK) = 0
11280 unlink("/var/lock/iscsi/lock.write") = 0
11280 brk(0)= 0x8cfb000
11280 brk(0x8d1c000)= 0x8d1c000
11280 open("/sys/class/iscsi_host", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
11280 fstat64(3, {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
11280 fcntl64(3, F_GETFD)   = 0x1 (flags FD_CLOEXEC)
11280 getdents(3, /* 2 entries */, 4096) = 32
11280 getdents(3, /* 0 entries */, 4096) = 0
11280 close(3)  = 0
11280 open("/etc/iscsi/nodes", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
11280 fstat64(3, {st_mode=S_IFDIR|0600, st_size=1024, ...}) = 0
11280 getdents(3, /* 4 entries */, 1024) = 132
11280 open("/etc/iscsi/nodes/iqn.1997-01.org.rfc822.lab.t4:storage.t4.disk1", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 4
11280 fstat64(4, {st_mode=S_IFDIR|0600, st_size=1024, ...}) = 0
11280 getdents(4, /* 3 entries */, 1024) = 64
11280 
open("/etc/iscsi/nodes/iqn.1997-01.org.rfc822.lab.t4:storage.t4.disk1/195.71.99.251,3260,1",
 O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 5
11280 fstat64(5, {st_mode=S_IFDIR|0600, st_size=1024, ...}) = 0
11280 getdents(5, /* 3 entries */, 1024) = 52
11280 access("/var/lock/iscsi", F_OK)   = 0
11280 open("/var/lock/iscsi/lock", O_RDWR|O_CREAT, 0666) = 6
11280 close(6)  = 0
11280 link("/var/lock/iscsi/lock", "/var/lock/iscsi/lock.write") = 0
11280 
open("/etc/iscsi/nodes/iqn.1997-01.org.rfc822.lab.t4:storage.t4.disk1/195.71.99.251,3260,1/default",
 O_RDONLY) = 6
11280 fstat64(6, {st_mode=S_IFREG|0600, st_size=1676, ...}) = 0
11280 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0xf77d1000
11280 _llseek(6, 0, [0], SEEK_SET)  = 0
11280 read(6, "node.name = iqn.1997-01.org.rfc82"..., 1024) = 1024
11280 read(6, "n.iscsi.MaxConnections = 1\nnode.s"..., 1024) = 652
11280 read(6, ""..., 1024)  = 0
11280 close(6)  = 0
11280 munmap(0xf77d1000, 4096)  = 0
11280 unlink("/var/lock/iscsi/lock.write") = 0
11280 getdents(5, /* 0 entries */, 1024) = 0
11280 close(5)  = 0
11280 getdents(4, /* 0 entries */, 1024) = 0
11280 close(4)  = 0
11280 open("/etc/

Bug#502845: linux-image-2.6.32-1-amd64 / open-iscsi amd64 login hang

2010-02-11 Thread Bastian Blank
On Thu, Feb 11, 2010 at 04:37:36PM +0100, Florian Lohoff wrote:
> 11280 connect(3, {sa_family=AF_FILE, path=@"ISCSIADM_ABSTRACT_NAMESPACE"...}, 
> 110) = 0
> 11280 write(3, 
> "\1\0\0\0\0\0\0\0\0\0\0\0\230q\304\377\230q\304\377iqn.1997-01.o"..., 5244) = 
> 5244
> 11280 recv(3, 0xffc46760, 2464, MSG_WAITALL) = ? ERESTARTSYS (To be restarted)

This only shows that iscsid does not respond to the requests of
iscsiadm. However I consider it unlikely that such a bug should have
survived for 14 kernel releases.

Please show all the relevant configs, strace outputs of iscsiadm _and_
iscsid and also network traces.

Bastian

-- 
A princess should not be afraid -- not with a brave knight to protect her.
-- McCoy, "Shore Leave", stardate 3025.3



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



Bug#569351: linux-2.6: Please support newer Areca controllers

2010-02-11 Thread Tollef Fog Heen
Package: linux-2.6
Severity: important

Hi,

we have a host with an 07:00.0 RAID bus controller: Areca Technology Corp. 
Device 1201
(aka 07:00.0 0104: 17d3:1201)

The kernel driver is arcmsr.

Could you please backport the necessary driver to lenny?

-- 
Tollef Fog Heen 
UNIX is user friendly, it's just picky about who its friends are



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



Processed: [bts-link] source package linux-2.6

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

> #
> # bts-link upstream status pull for source package linux-2.6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #567985 (http://bugs.debian.org/567985)
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=15209
> #  * remote status changed: NEW -> CLOSED
> #  * remote resolution changed: (?) -> INVALID
> #  * closed upstream
> tags 567985 + fixed-upstream
Bug #567985 [linux-source-2.6.32] [linux-source-2.6.32] kerneloops on boot if 
LBDAF not used
Added tag(s) fixed-upstream.
> usertags 567985 - status-NEW
Bug#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used
Usertags were: status-NEW.
Usertags are now: .
> usertags 567985 + status-CLOSED resolution-INVALID
Bug#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used
There were no usertags set.
Usertags are now: resolution-INVALID status-CLOSED.
> # remote status report for #568428 (http://bugs.debian.org/568428)
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=15235
> #  * remote status changed: (?) -> NEW
> usertags 568428 + status-NEW
Bug#568428: linux-source-2.6.32: Unable to use MagicPro ProTV DMB-TH usb Tuner 
(Conexant DMB-TH Stick)
There were no usertags set.
Usertags are now: status-NEW.
> 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



[bts-link] source package linux-2.6

2010-02-11 Thread bts-link-upstream
#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #567985 (http://bugs.debian.org/567985)
#  * http://bugzilla.kernel.org/show_bug.cgi?id=15209
#  * remote status changed: NEW -> CLOSED
#  * remote resolution changed: (?) -> INVALID
#  * closed upstream
tags 567985 + fixed-upstream
usertags 567985 - status-NEW
usertags 567985 + status-CLOSED resolution-INVALID

# remote status report for #568428 (http://bugs.debian.org/568428)
#  * http://bugzilla.kernel.org/show_bug.cgi?id=15235
#  * remote status changed: (?) -> NEW
usertags 568428 + status-NEW

thanks


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



Bug#384955: marked as done (Nokia E70 as "PC suite" destabilises kernel)

2010-02-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Feb 2010 18:39:59 +0100
with message-id <20100211173959.ga3...@galadriel.inutil.org>
and subject line Re: Nokia E70 as "PC suite" destabilises kernel
has caused the Debian Bug report #384955,
regarding Nokia E70 as "PC suite" destabilises kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
384955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kernel
Version: linux-image-2.6.17-2-686 2.6.17-7 x debian unstable
Severity: normal

Hardware Environment: Toshiba Portege R100, Nokia E70

When connecting Nokia E70 as "PC suite", kernel 
destabilises to the point of crashing randomly. When connecting the USB 
cable, the E70 gives you a menu of 3 options: "PC Suite","Data 
Transfer", and "IP passthrouh". The "Data transfer" mode makes the 
(mini-SD) mem card in the phone look like a USB_storage - that works 
99%. But if you ask for "PC suite", which AFAIK will establish some sort 
of serial channell to speak to the phone for syncing etc, All hell 
breaks loose. Never tried the "IP passthrough" option.

I attach the kernel log. The Oops occured in the "Gnome-ternimal" 
process, so probably is just an effect, but what do I know, never 
debugged kernels.

Here is the log:
Aug 28 10:19:44 r100 kernel: klogd 1.4.1#18, log source = /proc/kmsg started.
Aug 28 10:19:44 r100 kernel: Linux version 2.6.17-2-686 (Debian 2.6.17-7) 
(wa...@debian.org) (gcc version 4.1.2 20060814 (prerelease) (Debian 4.1.1-11)) 
#1 SMP Thu Aug 24 23:24:19 UTC 2006
Aug 28 10:19:44 r100 kernel: BIOS-provided physical RAM map:
Aug 28 10:19:44 r100 kernel:  BIOS-e820:  - 0009fc00 
(usable)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: 0009fc00 - 000a 
(reserved)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: 000e - 000eee00 
(reserved)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: 000eee00 - 000ef000 
(ACPI NVS)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: 000ef000 - 0010 
(reserved)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: 0010 - 1ffca000 
(usable)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: 1ffca000 - 1ffd 
(reserved)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: 1ffd - 1ffe 
(ACPI data)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: 1ffe - 2000 
(reserved)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: feda - fedc 
(reserved)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: ffb8 - ffc0 
(reserved)
Aug 28 10:19:44 r100 kernel:  BIOS-e820: fff0 - 0001 
(reserved)
Aug 28 10:19:44 r100 kernel: 0MB HIGHMEM available.
Aug 28 10:19:44 r100 kernel: 511MB LOWMEM available.
Aug 28 10:19:44 r100 kernel: On node 0 totalpages: 131018
Aug 28 10:19:44 r100 kernel:   DMA zone: 4096 pages, LIFO batch:0
Aug 28 10:19:44 r100 kernel:   Normal zone: 126922 pages, LIFO batch:31
Aug 28 10:19:44 r100 kernel: DMI 2.3 present.
Aug 28 10:19:44 r100 kernel: ACPI: RSDP (v000 TOSHIB
) @ 0x000f01e0
Aug 28 10:19:44 r100 kernel: ACPI: RSDT (v001 TOSHIB 750  0x00970814 TASM 
0x0401) @ 0x1ffd
Aug 28 10:19:44 r100 kernel: ACPI: FADT (v002 TOSHIB 750  0x20030101 TASM 
0x0401) @ 0x1ffd005c
Aug 28 10:19:44 r100 kernel: ACPI: SSDT (v001 TOSHIB R100 0x20030220 MSFT 
0x010e) @ 0x1ffd537a
Aug 28 10:19:44 r100 kernel: ACPI: DBGP (v001 TOSHIB 750  0x00970814 TASM 
0x0401) @ 0x1ffd00e0
Aug 28 10:19:44 r100 kernel: ACPI: DSDT (v001 TOSHIB R100 0x20030313 MSFT 
0x010e) @ 0x
Aug 28 10:19:44 r100 kernel: ACPI: PM-Timer IO Port: 0xd808
Aug 28 10:19:44 r100 kernel: Allocating PCI resources starting at 3000 
(gap: 2000:deda)
Aug 28 10:19:44 r100 kernel: Built 1 zonelists
Aug 28 10:19:44 r100 kernel: Kernel command line: root=/dev/hda2 ro 
pci=assign-busses 
Aug 28 10:19:44 r100 kernel: Local APIC disabled by BIOS -- you can enable it 
with "lapic"
Aug 28 10:19:44 r100 kernel: mapped APIC to d000 (0140a000)
Aug 28 10:19:44 r100 kernel: Enabling fast FPU save and restore... done.
Aug 28 10:19:44 r100 kernel: Enabling unmasked SIMD FPU exception support... 
done.
Aug 28 10:19:44 r100 kernel: Initializing CPU#0
Aug 28 10:19:44 r100 kernel: PID hash table entries: 2048 (order: 11, 8192 
bytes)
Aug 28 10:19:44 r100 kernel: Detected 897.853 MHz processor.
Aug 28 10:19:44 r100 kernel: Using pmtmr for high-res timesource
Aug 28 10:19:44 r100 kernel: Console: colour VGA+ 80x25
Aug

Re: [Debian] openvz kernel for debian squeeze

2010-02-11 Thread Ola Lundqvist
Hi Kir

On Thu, Feb 11, 2010 at 09:33:05PM +0300, Kir Kolyshkin wrote:
> Hi Ola, guys,
>
> Thanks for the info. We have discussed this at length and
> the resolution is we are all for it. This means we will try
> hard to do a rebase as soon as possible, and I hope we
> will succeed.

Sounds great.

> If (or whenever you will) know the exact deadline date
> (or any close approximation), please let us know, this is
> important.

I will let you know when I know. So far I do not know better
than the below.

> Also, can you please point us to the location of the git
> repository of what will become the linux kernel for the
> next debian release? I checked git.debian.org but
> where there are too many kernels to look at.
> If it is not in git then when it is?

You have the kernel team page at
http://wiki.debian.org/DebianKernel

As you can see subversion is used for all kernel packaging
handling.

Information about the source is available at
http://wiki.debian.org/DebianKernelSource

Please tell me if you do not find what you are looking for
there.

I'll dig into the kernel archive now to see information about
which kernel that will be used for next stable release.

Best regards,

// Ola

> Regards,
>   Kir.
>
> On 02/09/2010 10:31 AM, Ola Lundqvist wrote:
>> Hi Kir and other Openvz people
>>
>> We are closing in to the freeze period. This means that we have about
>> a month to include openvz enabled kernels in Debian.
>>
>> Best regards,
>>
>> // Ola
>>
>> - Forwarded message from Marc Brockschmidt  -
>>
>> Envelope-to: o...@inguza.com
>> Delivery-date: Mon, 08 Feb 2010 20:51:21 +0100
>> Old-Return-Path:
>> X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on liszt.debian.org
>> X-Spam-Level:
>> X-Spam-Status: No, score=-11.4 required=4.0 tests=ALL_TRUSTED,LDO_WHITELIST,
>>  PGPSIGNATURE autolearn=failed version=3.2.5
>> X-Virus-Scanned: at lists.debian.org with policy bank moderated
>> X-Amavis-Spam-Status: No, score=-11.8 tagged_above=-1 required=5.3
>>  tests=[ALL_TRUSTED=-1.8, LDO_WHITELIST=-5, PGPSIGNATURE=-5]
>>  autolearn=ham
>> X-Greylist: delayed 2161 seconds by postgrey-1.31 at liszt; Mon, 08 Feb 2010 
>> 19:50:05 UTC
>> From: Marc Brockschmidt
>> To: debian-devel-annou...@lists.debian.org
>> Subject: Bits from the release team: Release schedule; the RT needs YOU
>> X-Debian-Message: Signature check passed for Debian member
>> Mail-Followup-To: debian-de...@lists.debian.org
>> X-Rc-Spam: 2008-11-04_01
>> Resent-Message-ID:
>> Resent-From: debian-devel-annou...@lists.debian.org
>> X-Mailing-List:  archive/latest/1209
>> List-Id:
>> List-Post:
>> List-Help:
>> List-Subscribe:
>> List-Unsubscribe:
>> Resent-Sender: debian-devel-announce-requ...@lists.debian.org
>> Resent-Date: Mon,  8 Feb 2010 19:50:21 + (UTC)
>> X-Spam-Score: -1.0 (-)
>> X-Spamcheck-provider: Checked for spam by inguza.net, postmas...@inguza.net
>>
>> Heya,
>>
>> As you may have noticed, updates from the release team have been scarce
>> in the past few months. We are trying to perform better in the future,
>> but would be glad to get help.
>>
>> Release schedule
>> 
>> We hoped to freeze in March, but the current number of RC bugs makes
>> this highly unlikely. From our experiences with previous release cycles,
>> we wish to freeze only after the number of these bugs has dropped below
>> the mark of 300. As you can see on the usual overview pages [RC-Bugs],
>> we are currently far away from this goal.
>>
>> Work towards fixing these bugs is greatly appreciated. We will use our
>> release superpowers to aggressively remove leaf packages from testing
>> (in fact, another round of removals happened on the weekend). Please
>> check if packages you maintain or use are removal candidates, for
>> example by running ``rc-alert'' (from the devscripts package).
>>
>> There are still some ongoing transitions, but we are confident of finishing
>> them as part of our usual day-to-day business. Some smaller transitions
>> are still in the queue, but should be finished fast as soon as they get
>> the green light.
>>
>> Request for help
>> 
>> As you may have noticed, the release team has been notably less active in
>> the last six months. If you want to invest more time into making Squeeze
>> the best Debian release ever, feel free to send a mail or contact us in
>> IRC. We need more manpower to coordinate transitions and bug fixes, so
>> please consider lending a helping hand.
>>
>> Cheers,
>> Marc
>>
>> Footnotes:
>>   [RC-Bugs] http://bugs.debian.org/release-critical/
>> http://bts.turmzimmer.net/
>>
>
> ___
> Debian mailing list
> deb...@openvz.org
> https://openvz.

openvz kernel for debian squeeze

2010-02-11 Thread Kir Kolyshkin

Hi Ola, guys,

Thanks for the info. We have discussed this at length and
the resolution is we are all for it. This means we will try
hard to do a rebase as soon as possible, and I hope we
will succeed.

If (or whenever you will) know the exact deadline date
(or any close approximation), please let us know, this is
important.

Also, can you please point us to the location of the git
repository of what will become the linux kernel for the
next debian release? I checked git.debian.org but
where there are too many kernels to look at.
If it is not in git then when it is?

Regards,
  Kir.

On 02/09/2010 10:31 AM, Ola Lundqvist wrote:

Hi Kir and other Openvz people

We are closing in to the freeze period. This means that we have about
a month to include openvz enabled kernels in Debian.

Best regards,

// Ola

- Forwarded message from Marc Brockschmidt  -

Envelope-to: o...@inguza.com
Delivery-date: Mon, 08 Feb 2010 20:51:21 +0100
Old-Return-Path:
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on liszt.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-11.4 required=4.0 tests=ALL_TRUSTED,LDO_WHITELIST,
PGPSIGNATURE autolearn=failed version=3.2.5
X-Virus-Scanned: at lists.debian.org with policy bank moderated
X-Amavis-Spam-Status: No, score=-11.8 tagged_above=-1 required=5.3
tests=[ALL_TRUSTED=-1.8, LDO_WHITELIST=-5, PGPSIGNATURE=-5]
autolearn=ham
X-Greylist: delayed 2161 seconds by postgrey-1.31 at liszt; Mon, 08 Feb 2010 
19:50:05 UTC
From: Marc Brockschmidt
To: debian-devel-annou...@lists.debian.org
Subject: Bits from the release team: Release schedule; the RT needs YOU
X-Debian-Message: Signature check passed for Debian member
Mail-Followup-To: debian-de...@lists.debian.org
X-Rc-Spam: 2008-11-04_01
Resent-Message-ID:
Resent-From: debian-devel-annou...@lists.debian.org
X-Mailing-List:  archive/latest/1209
List-Id:
List-Post:
List-Help:
List-Subscribe:
List-Unsubscribe:
Resent-Sender: debian-devel-announce-requ...@lists.debian.org
Resent-Date: Mon,  8 Feb 2010 19:50:21 + (UTC)
X-Spam-Score: -1.0 (-)
X-Spamcheck-provider: Checked for spam by inguza.net, postmas...@inguza.net

Heya,

As you may have noticed, updates from the release team have been scarce
in the past few months. We are trying to perform better in the future,
but would be glad to get help.

Release schedule

We hoped to freeze in March, but the current number of RC bugs makes
this highly unlikely. From our experiences with previous release cycles,
we wish to freeze only after the number of these bugs has dropped below
the mark of 300. As you can see on the usual overview pages [RC-Bugs],
we are currently far away from this goal.

Work towards fixing these bugs is greatly appreciated. We will use our
release superpowers to aggressively remove leaf packages from testing
(in fact, another round of removals happened on the weekend). Please
check if packages you maintain or use are removal candidates, for
example by running ``rc-alert'' (from the devscripts package).

There are still some ongoing transitions, but we are confident of finishing
them as part of our usual day-to-day business. Some smaller transitions
are still in the queue, but should be finished fast as soon as they get
the green light.

Request for help

As you may have noticed, the release team has been notably less active in
the last six months. If you want to invest more time into making Squeeze
the best Debian release ever, feel free to send a mail or contact us in
IRC. We need more manpower to coordinate transitions and bug fixes, so
please consider lending a helping hand.

Cheers,
Marc

Footnotes:
  [RC-Bugs] http://bugs.debian.org/release-critical/
http://bts.turmzimmer.net/
   



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



Bug#502845: linux-image-2.6.32-1-amd64 / open-iscsi amd64 login hang

2010-02-11 Thread Florian Lohoff
On Thu, Feb 11, 2010 at 05:51:38PM +0100, Bastian Blank wrote:
> On Thu, Feb 11, 2010 at 04:37:36PM +0100, Florian Lohoff wrote:
> > 11280 connect(3, {sa_family=AF_FILE, 
> > path=@"ISCSIADM_ABSTRACT_NAMESPACE"...}, 110) = 0
> > 11280 write(3, 
> > "\1\0\0\0\0\0\0\0\0\0\0\0\230q\304\377\230q\304\377iqn.1997-01.o"..., 5244) 
> > = 5244
> > 11280 recv(3, 0xffc46760, 2464, MSG_WAITALL) = ? ERESTARTSYS (To be 
> > restarted)
> 
> This only shows that iscsid does not respond to the requests of
> iscsiadm. However I consider it unlikely that such a bug should have
> survived for 14 kernel releases.
> 
> Please show all the relevant configs, strace outputs of iscsiadm _and_
> iscsid and also network traces.

Something _is_ broken - I am very successful building up open-iscsi/iscsitarget
pairs on i386 - as soon as the initiator (open-iscsi) is on amd64 the login
hangs forever ... No matter whether the target is on the same machine
or on a different machine ...

What i did now:

bladesys3:~# tcpdump -i eth0 -s0 -w /tmp/login.pcap host t4.lab.rfc822.org and 
port 3260

and in parallel:

bladesys3:~# strace -t -f -o /tmp/scsid.strace.log /etc/init.d/open-iscsi start

Starting iSCSI initiator service: iscsid.
Setting up iSCSI targets:
iscsiadm: No records found!
.
Mounting network filesystems:.

And then:

iscsiadm -m discovery -t st -p 195.71.99.251
iscsiadm -m node

iscsiadm -m node --targetname "iqn.1997-01.org.rfc822.lab.t4:storage.t4.disk1" 
--portal "195.71.99.251:3260" --op=update --name node.session.auth.authmethod 
--value=CHAP
iscsiadm -m node --targetname "iqn.1997-01.org.rfc822.lab.t4:storage.t4.disk1" 
--portal "195.71.99.251:3260" --op=update --name node.session.auth.username 
--value=storage1
iscsiadm -m node --targetname "iqn.1997-01.org.rfc822.lab.t4:storage.t4.disk1" 
--portal "195.71.99.251:3260" --op=update --name node.session.auth.password 
--value=mi4Taibi

iscsiadm -m node --targetname "iqn.1997-01.org.rfc822.lab.t4:storage.t4.disk1" 
--portal "195.71.99.251:3260" --login

tcpdump:

http://silicon-verl.de/home/flo/tmp/iscsilogin.pcap
http://silicon-verl.de/home/flo/tmp/scsid.strace.log

The scsid strace shows repeated stuff like:

3444  20:14:08 connect(9, {sa_family=AF_INET, sin_port=htons(3260), 
sin_addr=inet_addr("195.71.99.251")}, 128) = -1 EINPROGRESS (Operation now in 
progress)

Although telnet (as the tcpdump) reports the connect is no problem:

bladesys3:/tmp# telnet t4.lab.rfc822.org 3260
Trying 195.71.99.251...
Connected to tiles-four.lab.rfc822.org.
Escape character is '^]'.
^]
telnet> close
Connection closed.

Still - the login hangs - dead ... I have never seen something like this
between i386 machines.

open-iscsi config is untouched.

What else?

Flo
-- 
Florian Lohoff f...@zz.de
"Es ist ein grobes Missverständnis und eine Fehlwahrnehmung, dem Staat
im Internet Zensur- und Überwachungsabsichten zu unterstellen."
- - Bundesminister Dr. Wolfgang Schäuble -- 10. Juli in Berlin 


signature.asc
Description: Digital signature


Re: lxc linux image flavour

2010-02-11 Thread Ola Lundqvist
Hi all

I can now announce an "half official" statement from Kir
(who is the project manager of openvz) that they are now
dedicated to make a openvz. This is what he states:

-
Hi Ola, guys,

Thanks for the info. We have discussed this at length and
the resolution is we are all for it. This means we will try
hard to do a rebase as soon as possible, and I hope we
will succeed.

If (or whenever you will) know the exact deadline date
(or any close approximation), please let us know, this is
important.

Also, can you please point us to the location of the git
repository of what will become the linux kernel for the
next debian release? I checked git.debian.org but
where there are too many kernels to look at.
If it is not in git then when it is?

Regards,
  Kir.
--

So it looks like we are going to have openvz available in squeeze.

Best regards,

// Ola

On Mon, Jan 25, 2010 at 12:46:42AM +0100, maximilian attems wrote:
> On Sun, Jan 24, 2010 at 03:17:14PM +0100, Marco d'Itri wrote:
> > On Jan 24, maximilian attems  wrote:
> > 
> > > the plan as decided in Portland was to go forward with openvz
> > > if upstream provides us with a patch in time. as currently this
> > > looks quite bad (latest available patch is for 2.6.27, there is
> > > no sign of a patch for 2.6.32, nor any schedule like it happened
> > > to be for Lenny).
> > I expect that it will be released after the first beta of RHEL 6.
> 
> point to an official statement of an openvz dev.
> currently it looks like they are waiting too long to be in the squeeze
> boat also kernel version should match.
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> 
> 

-- 
 - Ola Lundqvist ---
/  o...@debian.org Annebergsslingan 37  \
|  o...@inguza.com  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 debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#502845: linux-image-2.6.32-1-amd64 / open-iscsi amd64 login hang

2010-02-11 Thread Bastian Blank
On Thu, Feb 11, 2010 at 08:23:12PM +0100, Florian Lohoff wrote:
> Something _is_ broken - I am very successful building up 
> open-iscsi/iscsitarget
> pairs on i386 - as soon as the initiator (open-iscsi) is on amd64 the login
> hangs forever ... No matter whether the target is on the same machine
> or on a different machine ...

Yes, it is. The iscsi_uevent structure defined in scsi/iscsi_if.h
suffers of the 64-bit-allignment-desease on i386.

Also please not that this interface is officialy _not_ exported.

Bastian

-- 
Captain's Log, star date 21:34.5...



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



Bug#524464: USB related crash

2010-02-11 Thread George Tellalov
It seems that the problem is gone with 2.6.32-6. I've tested for over an hour
today and I couldn't crash it. I'll leave the on-board usb controller on with
all the devices attached and if the problem appears again, I'll reopen the
bug. Right now I think it's safe to close it.

Thanks!



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



linux-2.6_2.6.32-8_multi.changes ACCEPTED

2010-02-11 Thread Archive Administrator



Accepted:
firmware-linux-free_2.6.32-8_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-8_all.deb
linux-2.6_2.6.32-8.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-8.diff.gz
linux-2.6_2.6.32-8.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-8.dsc
linux-doc-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-8_all.deb
linux-headers-2.6.32-2-486_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-486_2.6.32-8_i386.deb
linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
linux-headers-2.6.32-2-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-686_2.6.32-8_i386.deb
linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb
linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb
linux-image-2.6.32-2-486_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-486_2.6.32-8_i386.deb
linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
linux-image-2.6.32-2-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-686_2.6.32-8_i386.deb
linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb
linux-libc-dev_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-8_i386.deb
linux-manual-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-8_all.deb
linux-patch-debian-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-8_all.deb
linux-source-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-8_all.deb
linux-support-2.6.32-2_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-2_2.6.32-8_all.deb


Override entries for your package:
firmware-linux-free_2.6.32-8_all.deb - optional kernel
linux-2.6_2.6.32-8.dsc - source devel
linux-doc-2.6.32_2.6.32-8_all.deb - optional doc
linux-headers-2.6.32-2-486_2.6.32-8_i386.deb - optional kernel
linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb - optional kernel
linux-headers-2.6.32-2-686_2.6.32-8_i386.deb - optional kernel
linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb - optional kernel
linux-headers-2.6.32-2-all_2.6.32-8_i386.deb - optional kernel
linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb - optional kernel
linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb - optional kernel
linux-headers-2.6.32-2-common_2.6.32-8_i386.deb - optional kernel
linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb - optional kernel
linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb - optional kernel
linux-image-2.6.32-2-486_2.6.32-8_i386.deb - optional kernel
linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb - optional kernel
linux-image-2.6.32-2-686_2.6.32-8_i386.deb - optional kernel
linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb - optional kernel
linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb - optional kernel
linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb - optional kernel
linux-libc-dev_2.6.32-8_i386.deb - optional devel
linux-manual-2.6.32_2.6.32-8_all.deb - optional doc
linux-patch-debian-2.6.32_2.6.32-8_all.deb - optional kernel
linux-source-2.6.32_2.6.32-8_all.deb - optional kernel
linux-support-2.6.32-2_2.6.32-8_all.deb - optional devel

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 503172 568414 568416 568457 


Thank you for your contribution to Debian.


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



Bug#568416: marked as done (64-bit kernel/32-bit userland boot failure)

2010-02-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Feb 2010 22:13:07 +
with message-id 
and subject line Bug#568416: fixed in linux-2.6 2.6.32-8
has caused the Debian Bug report #568416,
regarding 64-bit kernel/32-bit userland boot failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
568416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux-2.6
Version: 2.6.32-7
Severity: grave

This release is known to cause boot problems on 32-bit systems w/ a
64-bit kernel:
  http://article.gmane.org/gmane.linux.kernel/946249

-- 
dann frazier



--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-8

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:

firmware-linux-free_2.6.32-8_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-8_all.deb
linux-2.6_2.6.32-8.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-8.diff.gz
linux-2.6_2.6.32-8.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-8.dsc
linux-doc-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-8_all.deb
linux-headers-2.6.32-2-486_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-486_2.6.32-8_i386.deb
linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
linux-headers-2.6.32-2-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-686_2.6.32-8_i386.deb
linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb
linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb
linux-image-2.6.32-2-486_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-486_2.6.32-8_i386.deb
linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
linux-image-2.6.32-2-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-686_2.6.32-8_i386.deb
linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb
linux-libc-dev_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-8_i386.deb
linux-manual-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-8_all.deb
linux-patch-debian-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-8_all.deb
linux-source-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-8_all.deb
linux-support-2.6.32-2_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-2_2.6.32-8_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 568...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Feb 2010 02:17:17 +
Source: linux-2.6
Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 
linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-2 linux-base 
linux-libc-dev linux-headers-2.6.32-2-all linux-headers-2.6.32-2-all-alpha 
linux-headers-2.6.32-2-common linux-image-2.6.32-2-alpha-generic 
linux-headers-2.6.32-2-alp

Bug#568679: marked as done ([linux-2.6] linux-image-2.6.32-2-amd64: All 32 bit programs segfault on run)

2010-02-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Feb 2010 22:13:07 +
with message-id 
and subject line Bug#568416: fixed in linux-2.6 2.6.32-8
has caused the Debian Bug report #568416,
regarding [linux-2.6] linux-image-2.6.32-2-amd64: All 32 bit programs segfault 
on run
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: linux-2.6
Version: 2.6.32-7
Severity: normal

--- Please enter the report below this line. ---
This problems appears in 2.6.32-7; 2.6.32-6 is unaffected.
Every 32-bit program I have attempted to load (wine and
bash-static) fails with a segmentation fault and no output.
Attempts to debug the problem directly have failed:

> % gdb bash-static
> GNU gdb (GDB) 7.0.1-debian
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> For bug reporting instructions, please see:
> ...
> Reading symbols from /home/antonio/bash/bash-static...(no debugging symbols 
found)...done.
> (gdb) run
> Starting program: /home/antonio/bash/bash-static
> Failed to read a valid object file image from memory.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x08048152 in ?? ()
> (gdb)

I am running an i7-920, if that for some reason might be useful to know.

--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.32-2-amd64

Debian Release: squeeze/sid
  502 unstablewww.debian-multimedia.org
  502 unstableftp.us.debian.org
  401 testing ftp.us.debian.org
  400 stable  dl.google.com

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.





--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-8

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:

firmware-linux-free_2.6.32-8_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-8_all.deb
linux-2.6_2.6.32-8.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-8.diff.gz
linux-2.6_2.6.32-8.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-8.dsc
linux-doc-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-8_all.deb
linux-headers-2.6.32-2-486_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-486_2.6.32-8_i386.deb
linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
linux-headers-2.6.32-2-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-686_2.6.32-8_i386.deb
linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb
linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb
linux-image-2.6.32-2-486_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-486_2.6.32-8_i386.deb
linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
linux-image-2.6.32-2-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-686_2.6.32-8_i386.deb
linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb
linux-libc-dev_2.6.32-8_i386.deb
  to

Bug#568457: marked as done (FTBFS [powerpc] - format '%x' expects type 'unsigned int')

2010-02-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Feb 2010 22:13:07 +
with message-id 
and subject line Bug#568457: fixed in linux-2.6 2.6.32-8
has caused the Debian Bug report #568457,
regarding FTBFS [powerpc] - format '%x' expects type 'unsigned int'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
568457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux-2.6
Version: 2.6.32-7
Severity: serious

I tried to do a local build of trunk on powerpc, and hit the following
bug (apparently introduced in 2.6.32-7):

cc1: warnings being treated as errors
/tmp/buildd/linux-2.6-2.6.32/debian/build/source_powerpc_none/arch/powerpc/kernel/time.c:
 In function 'register_decrementer_clockevent':
/tmp/buildd/linux-2.6-2.6.32/debian/build/source_powerpc_none/arch/powerpc/kernel/time.c:922:
 error: format '%x' expects type 'unsigned int', but argument 3 has type 'long 
unsigned int'


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-8

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:

firmware-linux-free_2.6.32-8_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-8_all.deb
linux-2.6_2.6.32-8.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-8.diff.gz
linux-2.6_2.6.32-8.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-8.dsc
linux-doc-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-8_all.deb
linux-headers-2.6.32-2-486_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-486_2.6.32-8_i386.deb
linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
linux-headers-2.6.32-2-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-686_2.6.32-8_i386.deb
linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-all-i386_2.6.32-8_i386.deb
linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-all_2.6.32-8_i386.deb
linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-amd64_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common-vserver_2.6.32-8_i386.deb
linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-common_2.6.32-8_i386.deb
linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  to 
main/l/linux-2.6/linux-headers-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-headers-2.6.32-2-vserver-686_2.6.32-8_i386.deb
linux-image-2.6.32-2-486_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-486_2.6.32-8_i386.deb
linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-686-bigmem_2.6.32-8_i386.deb
linux-image-2.6.32-2-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-686_2.6.32-8_i386.deb
linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-amd64_2.6.32-8_i386.deb
linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-vserver-686-bigmem_2.6.32-8_i386.deb
linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-image-2.6.32-2-vserver-686_2.6.32-8_i386.deb
linux-libc-dev_2.6.32-8_i386.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-8_i386.deb
linux-manual-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-8_all.deb
linux-patch-debian-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-8_all.deb
linux-source-2.6.32_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-8_all.deb
linux-support-2.6.32-2_2.6.32-8_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-2_2.6.32-8_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 568...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 11 Feb 2010 02:17:17 

Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686

2010-02-11 Thread maximilian attems
On Thu, 11 Feb 2010, Bruce Ward wrote:

> Greetings.
> 
> More data. I have managed to get an initramfs debug out of the
> system and have also provided a debug from a 2.6.26-1-686 kernel
> which boots OK. I'm damned if I can see any reason from the debug
> for the recent kernel (2.6.26-2-686) to fail to boot!
> 
> Interesting (but possibly not relevant) observations from my playing
> around (exploration). Remember there are only a few modules (thermal
> ones) loaded when the system drops out.
> 
> 1. Load USB drivers - they find the pendrive, but no entry created in /dev.
> 2. Use mknod to create /dev/sda3 for the ext3 partition on pendrive.
> sda3 is the only SCSI entry in /dev.
> 3. Load ext3 module, and mount the sda3 partition and, behold, there
> are entries in /dev/ for sda, sda1, and sda2, as well as sda3.
> 4. Load the SATA drivers and suddenly there are sdb entries in /dev
> for all partitions on the drive I have failed to boot from.

that points a bit to udev is it running  at this stage?
 



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



Processed: fix pkg name

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

> reassign 524985 linux-2.6
Bug #524985 [linux] python2.5: commands.getstatusoutput fails in i386 chroot
Warning: Unknown package 'linux'
Bug reassigned from package 'linux' to 'linux-2.6'.
> --
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



Processed: tagging 567985, closing 567985

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

> tags 567985 - fixed-upstream moreinfo
Bug #567985 [linux-source-2.6.32] [linux-source-2.6.32] kerneloops on boot if 
LBDAF not used
Removed tag(s) moreinfo and fixed-upstream.
> # submitter acknowledged as not a bug
> close 567985
Bug#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to "Brent S. Elmer Ph.D." 


> 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



Processed: closing 524464

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

> # submitter reported as fixed in this version
> close 524464 2.6.32-6
Bug#524464: USB related crash
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.6.32-6, send any further explanations to 
George Tellalov 

> 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



Processed: reassign old kernel bugs (2.6.30 mostly)

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

> reassign 550068 linux-2.6
Bug #550068 [linux-image-2.6.30-2-686] linux-image-2.6.30-2-686: i915 KMS : 
oops on load
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 550358 linux-2.6
Bug #550358 [linux-image-2.6.30-2-686] linux-image-2.6.30-2-686: Enable 
BOOTPARAM_HUNG_TASK_PANIC feature
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 550923 linux-2.6
Bug #550923 [linux-image-2.6.30-2-686] fails to suspend
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 551624 linux-2.6
Bug #551624 [linux-image-2.6.30-2-686] linux-image-2.6.30: btusb: 0a5c:2101 
Broadcom USB in 'lsusb', but not in 'hcitool dev', regression from 2.6.30-6
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 551804 linux-2.6
Bug #551804 [linux-image-2.6.30-2-686] linux-image-2.6.30-2-686: Booting with 
PAT enabled crashes kernel in OpenGL apps
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 554272 linux-2.6
Bug #554272 [linux-image-2.6.30-2-686] linux-image-2.6.30-2-686: Deferences 
NULL pointer in xfs
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 555835 linux-2.6
Bug #555835 [linux-image-2.6.30-2-686] linux-image-2.6.30-2-686: Unusual usb 
storage Samsung YP-CP3 not working
Bug #555836 [linux-image-2.6.30-2-686] linux-image-2.6.30-2-686: Unusual 
usb_storage device Samsung YP-CP3 not working
Warning: Unknown package 'linux-image-2.6.30-2-686'
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 555836 linux-2.6
Bug #555836 [linux-2.6] linux-image-2.6.30-2-686: Unusual usb_storage device 
Samsung YP-CP3 not working
Bug #555835 [linux-2.6] linux-image-2.6.30-2-686: Unusual usb storage Samsung 
YP-CP3 not working
Ignoring request to reassign bug #555836 to the same package
Ignoring request to reassign bug #555835 to the same package
> reassign 556585 linux-2.6
Bug #556585 [linux-image-2.6.30-2-686] iwlagn gone bananas after a couple of 
hours
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 559342 linux-2.6
Bug #559342 [linux-image-2.6.30-2-686] linux-image-2.6.30-2-686: USB Devices 
managed by uhci_hcd fail to mount
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 561092 linux-2.6
Bug #561092 [linux-image-2.6.30-2-686] Linux-image-2.6.30+ post-install
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8squeeze1.
> reassign 563947 linux-2.6
Bug #563947 [linux-image-2.6.30-2-686] linux-image-2.6.30-2-686 doesn't start 
software raid on boot
Warning: Unknown package 'linux-image-2.6.30-2-686'
Bug reassigned from package 'linux-image-2.6.30-2-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8squeeze1.
> reassign 548397 linux-2.6
Bug #548397 [linux-image-2.6.30-2-686-bigmem] linux-image-2.6.30-2-686-bigmem: 
Random Lockup with automount, mysqld, and kswapd0 error messages.
Warning: Unknown package 'linux-image-2.6.30-2-686-bigmem'
Bug reassigned from package 'linux-image-2.6.30-2-686-bigmem' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-7.
> reassign 552987 linux-2.6
Bug #552987 [linux-image-2.6.30-2-686-bigmem] linux-image-2.6.30-2-686-bigmem: 
intel i810 module is not found by Xorg
Warning: Unknown package 'linux-image-2.6.30-2-686-bigmem'
Bug reassigned from package 'linux-image-2.6.30-2-686-bigmem' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.30-8.
> reassign 550665 linux-2.6
Bug #550665 [linux-image-2.6.30-2-amd64] linux-image-2.6.30-2-amd64: ALSA: When

Bug#569351: linux-2.6: Please support newer Areca controllers

2010-02-11 Thread Ben Hutchings
On Thu, 2010-02-11 at 18:03 +0100, Tollef Fog Heen wrote:
> Package: linux-2.6
> Severity: important
> 
> Hi,
> 
> we have a host with an 07:00.0 RAID bus controller: Areca Technology Corp. 
> Device 1201
> (aka 07:00.0 0104: 17d3:1201)
> 
> The kernel driver is arcmsr.
> 
> Could you please backport the necessary driver to lenny?

The driver is already included in lenny kernel images and has this PCI
id in its device id table.  It has not changed in any significant way
post-2.6.26.  Perhaps it is not included in the appropriate d-i package?
What kind of error are you seeing when trying to use it?

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.


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


Processed: tagging 569351

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

> tags 569351 moreinfo
Bug #569351 [linux-2.6] linux-2.6: Please support newer Areca controllers
Added tag(s) moreinfo.
> 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



Processed: closing 535006

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

> # submitter reported as fixed in 2.6.32
> close 535006 2.6.32-1
Bug#535006: nfs-kernel-server: errors in dmesg
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug#525114: Debian NFS bug in testing (comm: nfsd Not tainted 2.6.29.1)
Bug#51: 2.6.29.1: nfsd: page allocation failure - nfsd or kernel problem?
Bug marked as fixed in version 2.6.32-1, send any further explanations to 
Christoph Kaminski 

> 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



Processed: reassign 569225 to src:linux-2.6

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

> reassign 569225 src:linux-2.6 2.6.32-6
Bug #569225 [linux-image-2.6.32-1-686-bigmem] i915: Increase fb alignment to 64k
Bug reassigned from package 'linux-image-2.6.32-1-686-bigmem' to 
'src:linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.32-6.
Bug #569225 [src:linux-2.6] i915: Increase fb alignment to 64k
Bug Marked as found in versions linux-2.6/2.6.32-6.
> 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



Processed: more kernel bugs

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

> reassign 508492 linux-2.6
Bug #508492 [linux-image-2.6.26-1-parisc64] linux-image-2.6.26-1-parisc64: 
[hppa64] XFS internal error xlog_valid_rec_header(2)
Warning: Unknown package 'linux-image-2.6.26-1-parisc64'
Bug reassigned from package 'linux-image-2.6.26-1-parisc64' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-11.
> reassign 514415 linux-2.6
Bug #514415 [linux-modules-2.6.26-1-xen-amd64] Kernel: mtr352 hangs with log: 
mt352_read_register: readreg error
Warning: Unknown package 'linux-modules-2.6.26-1-xen-amd64'
Bug reassigned from package 'linux-modules-2.6.26-1-xen-amd64' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-13.
> reassign 517627 linux-2.6
Bug #517627 [linux-image-2.6.26-1-parisc64-smp] 
linux-image-2.6.26-1-parisc64-smp: Acenic driver without firmware triggers HPMC
Warning: Unknown package 'linux-image-2.6.26-1-parisc64-smp'
Bug reassigned from package 'linux-image-2.6.26-1-parisc64-smp' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-13.
> reassign 506118 linux-2.6
Bug #506118 [xen-linux-system-2.6.26-1-xen-amd64] 
xen-linux-system-2.6.26-1-xen-amd64: Dom0 reboots after loading xend when atl1 
network is present
Warning: Unknown package 'xen-linux-system-2.6.26-1-xen-amd64'
Bug reassigned from package 'xen-linux-system-2.6.26-1-xen-amd64' to 
'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-10.
> reassign 566405 linux-2.6
Bug #566405 [linux-image-2.6.686] Kernel 2.6.32 trunk does not boot within 
Virtualbox
Warning: Unknown package 'linux-image-2.6.686'
Bug reassigned from package 'linux-image-2.6.686' to 'linux-2.6'.
Bug No longer marked as found in versions 2.6.30+21.
> reassign 517243 linux-2.6
Bug #517243 [linux-image-2.6.26-1-parisc64] linux-image-2.6.26-1-parisc64: tg3 
probe triggers HPMC
Warning: Unknown package 'linux-image-2.6.26-1-parisc64'
Bug reassigned from package 'linux-image-2.6.26-1-parisc64' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-13.
> reassign 505239 linux-2.6
Bug #505239 [linux-image-2.6.26-1-686-bigmem] preinst: initrddep not initialized
Warning: Unknown package 'linux-image-2.6.26-1-686-bigmem'
Bug reassigned from package 'linux-image-2.6.26-1-686-bigmem' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-10.
> reassign 500145 linux-2.6
Bug #500145 [linux-image-2.6.26-1-openvz-686] Subject: 
linux-image-2.6.26-1-openvz-686: more warnings in logs
Warning: Unknown package 'linux-image-2.6.26-1-openvz-686'
Bug reassigned from package 'linux-image-2.6.26-1-openvz-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-5.
> reassign 506654 linux-2.6
Bug #506654 [linux-image-2.6.26-1-686-bigmem] linux-image-2.6.26-1-686-bigmem: 
Firewire removable hard drive re-detected after S3 Suspend
Warning: Unknown package 'linux-image-2.6.26-1-686-bigmem'
Bug reassigned from package 'linux-image-2.6.26-1-686-bigmem' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.29-5 and 
linux-2.6/2.6.26-10.
> reassign 513095 linux-2.6
Bug #513095 [linux-image-2.6.26-1-openvz-686] linux-image-2.6.26-1-openvz-686: 
openvz kernel fails at recognizing keyboard and at ACPI handling
Warning: Unknown package 'linux-image-2.6.26-1-openvz-686'
Bug reassigned from package 'linux-image-2.6.26-1-openvz-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-13.
> reassign 513537 linux-2.6
Bug #513537 [linux-image-2.6.26-1-openvz-amd64] 
linux-image-2.6.26-1-openvz-amd64: KDE42 processes hang unpredictably in 
uninterruptable sleep (D state)
Warning: Unknown package 'linux-image-2.6.26-1-openvz-amd64'
Bug reassigned from package 'linux-image-2.6.26-1-openvz-amd64' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-13.
> --
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#569351: linux-2.6: Please support newer Areca controllers

2010-02-11 Thread Frans Pop
On Friday 12 February 2010, Ben Hutchings wrote:
> Perhaps it is not included in the appropriate d-i package?

arcmsr has been included in scsi-extra-modules since Nov 2006, if available
for an architecture.

For amd64:
$ dpkg -c scsi-extra-modules-2.6.30-2-amd64-di_1.61_amd64.udeb | grep arcmsr
drwxr-xr-x root/root 0 2009-10-08 15:58
 ./lib/modules/2.6.30-2-amd64/kernel/drivers/scsi/arcmsr/
-rw-r--r-- root/root 34621 2009-09-26 00:21
 ./lib/modules/2.6.30-2-amd64/kernel/drivers/scsi/arcmsr/arcmsr.ko

Cheers,
FJP



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



Bug#567747: [stable] (fwd) drm/i915: Fix DDC on some systems by clearing BIOS GMBUS setup.

2010-02-11 Thread Greg KH
On Thu, Feb 04, 2010 at 11:48:58AM +0100, maximilian attems wrote:
> we have a report that this fix is need for mac mini
> http://bugs.debian.org/567747
> could you please apply belows to 2.6.32

Now queued up, thanks.

gre k-h



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



Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686

2010-02-11 Thread Bruce Ward



maximilian attems wrote:

On Thu, 11 Feb 2010, Bruce Ward wrote:


Greetings.

More data. I have managed to get an initramfs debug out of the
system and have also provided a debug from a 2.6.26-1-686 kernel
which boots OK. I'm damned if I can see any reason from the debug
for the recent kernel (2.6.26-2-686) to fail to boot!

Interesting (but possibly not relevant) observations from my playing
around (exploration). Remember there are only a few modules (thermal
ones) loaded when the system drops out.

1. Load USB drivers - they find the pendrive, but no entry created in /dev.
2. Use mknod to create /dev/sda3 for the ext3 partition on pendrive.
sda3 is the only SCSI entry in /dev.
3. Load ext3 module, and mount the sda3 partition and, behold, there
are entries in /dev/ for sda, sda1, and sda2, as well as sda3.
4. Load the SATA drivers and suddenly there are sdb entries in /dev
for all partitions on the drive I have failed to boot from.


that points a bit to udev is it running  at this stage?
 



Yes, udev is running. Attached is a ps capture as soon as I had the 
pendrive mounted.


When the boot stopped, the listing of processes stopped at PID 732. udev 
is there before running the rescue shell.


Bruce

===
Bruce Ward, Nelson, New Zealand
PID   USER COMMAND
1 0/bin/sh /init 
2 0[kthreadd]
3 0[migration/0]
4 0[ksoftirqd/0]
5 0[watchdog/0]
6 0[events/0]
7 0[khelper]
   39 0[kblockd/0]
   41 0[kacpid]
   42 0[kacpi_notify]
  149 0[kseriod]
  186 0[pdflush]
  187 0[pdflush]
  188 0[kswapd0]
  189 0[aio/0]
  396 0udevd --daemon 
  732 0/bin/sh -i 
  736 0[ksuspend_usbd]
  739 0[khubd]
  788 0[scsi_eh_0]
  789 0[usb-storage]
  842 0[kjournald]
  843 0ps 


Bug#569494: linux-image-2.6.32-trunk-686: pcspkr sometimes breaks audio

2010-02-11 Thread Andres Salomon
In theory, this should never happen; snd_card_create() takes an idx
that sets the order of cards, /etc/modprobe.d/alsa-base-blacklist.conf
blacklists snd-pcsp (so it should never be loaded!),
and /etc/modprobe.d/alsa-base.conf sets idx=-2 for snd_pcsp so that
it's not loaded as the first soundcard.

This is a fresh install; alsa-base was not initially installed (I did a
minimal install, and then installed packages manually).  That's why I
hit this.

I'd suggest adding alsa-base as a Recommends or Suggests for
linux-image-2.6*-686 (and possibly others).




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



Bug#569012: linux-image-2.6.32-1-amd64: Freezes and memory corruption

2010-02-11 Thread Ben Hutchings
On Tue, 2010-02-09 at 17:26 +0400, Stepan Golosunov wrote:
> Package: linux-2.6
> Version: 2.6.32-6
> Severity: critical
> 
> After running 2.6.32 (as well as 2.6.31 and 2.6.30) for several minutes,
> computer freezes completely. Network or alt-sysrq-b do not work.
> 
> Further investigation showed that data is being corrupted while reading
> or writing files.
> Corruption on reading is easily reproduced with debsums (it fails on
> random files), corruption on writing happened at least once (under
> 2.6.32-trunk-amd64) and looks like:
[...]

Given that the first advertised feature of the P5Q Turbo motherboard is
'Easy Overclocking', I have to ask: are you overclocking it?

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.


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


Processed: tagging 569012

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

> tags 569012 moreinfo
Bug #569012 [linux-2.6] linux-image-2.6.32-1-amd64: Freezes and memory 
corruption
Added tag(s) moreinfo.
> 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#568903: Enable USB/IP staging drivers

2010-02-11 Thread Ben Hutchings
On Tue, 2010-02-09 at 14:21 +0100, Max Vozeler wrote:
> Hi Ben,
> 
> On Tue, Feb 09, 2010 at 03:21:15AM +, Ben Hutchings wrote:
> > On Mon, 2010-02-08 at 18:15 +0100, Max Vozeler wrote:
> > > Please consider including the USB/IP drivers from the
> > > staging directory:
> > > 
> > > CONFIG_USB_IP_COMMON=m
> > > CONFIG_USB_IP_VHCI_HCD=m
> > > CONFIG_USB_IP_HOST=m
> > > 
> > > As I understand, the drivers remain in staging not so much
> > > because of quality issues but due to discussions about the
> > > userspace API, which may still change.
> > 
> > The implementation is questionable too.
> 
> Could you point me to related discussions or things you
> noticed which look odd?

Comments like:

/*
 * When removing an exported device, kernel panic sometimes occurred
 * and then EIP was sk_wait_data of stub_rx thread. Is this because
 * sk_wait_data returned though stub_rx thread was already finished by
 * step 1?
 */

> > > The only users of the API which exist today are the usbip 
> > > userspace tools through libusbip0. It should be possible to
> > > adapt those if/when the API changes.
> > > 
> > > If these modules were provided in linux-2.6, we could drop
> > > the usbip-source module package.
> > 
> > Given that this is not needed for hardware support, I would like to see
> > a good reason for including it.
> 
> OK. Let me try to give a balanced view:
> 
> The drivers provide a new and experimental feature,
> which has gotten to the point of being usable in some 
> limited but practical scenarios.
> 
> One I've been working on is remote access to hardware
> security modules from within virtual machines.

What could possibly go wrong?!

> There are still limitations that make it unsuitable 
> for less specialized setups. Device reconnects are not
> handeled transparently yet, for example.
> 
> Other limitations lie in the usbip userspace tools, the
> most important probably being the lack of authorization
> for access to the usbip daemon.

Apparently there are some serious problems with the protocol too.

[]
> So in the future the usbip-source module package will
> be mostly a copy of the drivers from staging.
> 
> Including it in linux-2.6 would likely allow us to drop 
> the separate usbip-source package, make it easier for 
> users to get the modules and keep them updated.
> 
> I don't think these are really strong reasons for 
> including it in linux-2.6 vs. having the module package
> considering that it is experimental and niche enough 
> to only be interesting to relatively few people.
> 
> On the other hand, since staging is going to be where 
> the development happens, it seems that it is also the 
> best place to build the modules from.
> 
> Hope that gives you a basis for deciding about whether 
> to include it or keep it separate.

OK, I suppose 'staging' is probably a big enough warning label.  I think
we can enable this for x86.  Please look for out bug reports.

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.


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


Bug#569494: linux-image-2.6.32-trunk-686: pcspkr sometimes breaks audio

2010-02-11 Thread Ben Hutchings
On Thu, 2010-02-11 at 19:43 -0500, Andres Salomon wrote:
> In theory, this should never happen; snd_card_create() takes an idx
> that sets the order of cards, /etc/modprobe.d/alsa-base-blacklist.conf
> blacklists snd-pcsp (so it should never be loaded!),
> and /etc/modprobe.d/alsa-base.conf sets idx=-2 for snd_pcsp so that
> it's not loaded as the first soundcard.
> 
> This is a fresh install; alsa-base was not initially installed (I did a
> minimal install, and then installed packages manually).  That's why I
> hit this.
> 
> I'd suggest adding alsa-base as a Recommends or Suggests for
> linux-image-2.6*-686 (and possibly others).

I actually want to get rid of alsa-driver as there should be no need for
a second copy of the drivers.  What little useful functionality is left
in alsa-base could perhaps be merged into udev.

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.


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


Processed: tagging 568903

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 568903 + pending
Bug #568903 [linux-2.6] Enable USB/IP staging drivers
Added tag(s) 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 debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Processed: reassign 2.6.26 ABI 1 bugs

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

> reassign 497767 linux-2.6
Bug #497767 [linux-image-2.6.26-1-486] linux-image-2.6.26-1-486: webcams with 
pwc chipset no long work
Warning: Unknown package 'linux-image-2.6.26-1-486'
Bug reassigned from package 'linux-image-2.6.26-1-486' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-3.
> reassign 499406 linux-2.6
Bug #499406 [linux-image-2.6.26-1-486] linux-image-2.6.26-1-486: Atmel driver 
claims register interrupt 15 failed, no wireless with 00:0a.0
Warning: Unknown package 'linux-image-2.6.26-1-486'
Bug reassigned from package 'linux-image-2.6.26-1-486' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-4.
> reassign 500062 linux-2.6
Bug #500062 [linux-image-2.6.26-1-486] linux-image-2.6.26-1-486: Disables IDE 
ports, can't find root fs afterwards
Warning: Unknown package 'linux-image-2.6.26-1-486'
Bug reassigned from package 'linux-image-2.6.26-1-486' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-5.
> reassign 500158 linux-2.6
Bug #500158 [linux-image-2.6.26-1-486] linux-image-2.6.26-1-486: Upgrade from 
Debian Etch to Debian Lenny may cause a kernel halt
Warning: Unknown package 'linux-image-2.6.26-1-486'
Bug reassigned from package 'linux-image-2.6.26-1-486' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-5.
> reassign 504386 linux-2.6
Bug #504386 [linux-image-2.6.26-1-486] linux-image-2.6.26-1-486: rtl8180 module 
detects aps but fails  toauthenticate (pci id 10ec:8180 (rev 20)
Warning: Unknown package 'linux-image-2.6.26-1-486'
Bug reassigned from package 'linux-image-2.6.26-1-486' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-8.
> reassign 514592 linux-2.6
Bug #514592 [linux-image-2.6.26-1-486] linux-image-2.6.26-1-486: does not 
support ethernet adaptor Intel 0x10de
Warning: Unknown package 'linux-image-2.6.26-1-486'
Bug reassigned from package 'linux-image-2.6.26-1-486' to 'linux-2.6'.
Bug No longer marked as found in versions 2.6.26+17.
> reassign 519815 linux-2.6
Bug #519815 [linux-image-2.6.26-1-486] serious SCSI errors using Debian 5 
network install image
Warning: Unknown package 'linux-image-2.6.26-1-486'
Bug reassigned from package 'linux-image-2.6.26-1-486' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-13.
> reassign 525308 linux-2.6
Bug #525308 [linux-image-2.6.26-1-486] vmlinuz: cannot mount partition
Warning: Unknown package 'linux-image-2.6.26-1-486'
Bug reassigned from package 'linux-image-2.6.26-1-486' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-13.
> reassign 540172 linux-2.6
Bug #540172 [linux-image-2.6.26-1-486] linux-image-2.6.26-1-486: writing per 
sector causes disk reads
Warning: Unknown package 'linux-image-2.6.26-1-486'
Bug reassigned from package 'linux-image-2.6.26-1-486' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-13.
> reassign 480207 linux-2.6
Bug #480207 [linux-image-2.6.26-1-686] linux-image-2.6.24-1-686: computer 
freezes when insanely removing card using saa7133
Warning: Unknown package 'linux-image-2.6.26-1-686'
Bug reassigned from package 'linux-image-2.6.26-1-686' to 'linux-2.6'.
> reassign 493832 linux-2.6
Bug #493832 [linux-image-2.6.26-1-686] ath5k disconnects regularly and has poor 
performance
Warning: Unknown package 'linux-image-2.6.26-1-686'
Bug reassigned from package 'linux-image-2.6.26-1-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-1.
> reassign 494249 linux-2.6
Bug #494249 [linux-image-2.6.26-1-686] linux-image-2.6.26-1-686 monitor button 
does not work in hp nx 6110
Warning: Unknown package 'linux-image-2.6.26-1-686'
Bug reassigned from package 'linux-image-2.6.26-1-686' to 'linux-2.6'.
> reassign 494360 linux-2.6
Bug #494360 [linux-image-2.6.26-1-686] linux-image-2.6.26-1-686: ipg claims 
dl2k device it does not work with
Warning: Unknown package 'linux-image-2.6.26-1-686'
Bug reassigned from package 'linux-image-2.6.26-1-686' to 'linux-2.6'.
Bug No longer marked as found in versions 2.6.25-1, 2.6.24-1, and 
linux-2.6/2.6.26-1.
> reassign 494573 linux-2.6
Bug #494573 [linux-image-2.6.26-1-686] [linux-image-2.6.26-1-686] ACPI 
unsupportet Model --> DSDT
Warning: Unknown package 'linux-image-2.6.26-1-686'
Bug reassigned from package 'linux-image-2.6.26-1-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-1.
> reassign 494976 linux-2.6
Bug #494976 [linux-image-2.6.26-1-686] linux-image-2.6.26-1-686: Usb disk does 
not work
Warning: Unknown package 'linux-image-2.6.26-1-686'
Bug reassigned from package 'linux-image-2.6.26-1-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-2.
> reassign 495718 linux-2.6
Bug #495718 [linux-image-2.6.26-1-686] linux-image-2.6.26-1-686: ark3116 module 
doesn't work anymore
Warning: Unknown package 'linux-image-2.6.26-1-686'
Bug reassigned from packag

Bug#569012: linux-image-2.6.32-1-amd64: Freezes and memory corruption

2010-02-11 Thread Stepan Golosunov
12.02.2010 в 02:42:29 + Ben Hutchings написал:
> On Tue, 2010-02-09 at 17:26 +0400, Stepan Golosunov wrote:
> > Package: linux-2.6
> > Version: 2.6.32-6
> > Severity: critical
> > 
> > After running 2.6.32 (as well as 2.6.31 and 2.6.30) for several minutes,
> > computer freezes completely. Network or alt-sysrq-b do not work.
> > 
> > Further investigation showed that data is being corrupted while reading
> > or writing files.
> > Corruption on reading is easily reproduced with debsums (it fails on
> > random files), corruption on writing happened at least once (under
> > 2.6.32-trunk-amd64) and looks like:
> [...]
> 
> Given that the first advertised feature of the P5Q Turbo motherboard is
> 'Easy Overclocking', I have to ask: are you overclocking it?

No. Unless it overclocks something automatically.



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



Re: Upgrade script for libata transition

2010-02-11 Thread Ben Hutchings
On Thu, 2010-01-07 at 22:49 +, Ben Hutchings wrote:
> On Tue, 2009-12-29 at 12:06 +, Ben Hutchings wrote:
> > Linux kernel packages for "squeeze" will use libata-based drivers in
> > preference to old-style IDE drivers.  On some systems this will change
> > the names of PATA devices and will also change the names of SCSI devices
> > already present in those systems if they are enumerated after the PATA
> > devices.
> > 
> > On upgrade, we will recommend that users identify hard disk volumes in
> > configuration files by label or UUID (unique identifier) rather than by
> > device name, which will work with both old and new kernel versions.  I
> > think that in most cases it should be possible to update the system
> > configuration automatically, if the user agrees to this.  The following
> > script implements this.  Please review and verify that it does the right
> > thing for your package's configuration file(s).  (I would also welcome a
> > more general review of the code.)
> [...]
> 
> I have not yet seen any comments from maintainers of the various boot
> loaders.  It is vital that this upgrade process is reliable and does not
> prevent systems from booting, so please do review the code for your boot
> loader.
> 
> If you prefer, I can prepare packages that include this script on
> postinst and upload them to people.debian.org for you or others to test.

Sorry about the delay in doing this.  You can now get a source package
by doing:

$ apt-get -d source linux-2.6
$ dget http://people.debian.org/~benh/linux-2.6_2.6.32-8a~test.dsc

To build a kernel image package, follow the instructions at:

http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official

Note in particular the instructions beginning 'For example, to build
only the binary packages for 686 flavour...'

The kernel image packages will depend on the linux-base package which
contains the transition script.  To build that, run:

$ fakeroot make -f debian/rules.real install-linux-base

Please test both the transition script and the new drivers so far as you
can (most are x86-only but some are available for all architectures with
PCI).  I suggest starting with an emulated/virtualised system before you
risk breaking anything real!

Ben.

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


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


Bug#569012: linux-image-2.6.32-1-amd64: Freezes and memory corruption

2010-02-11 Thread Ben Hutchings
On Fri, 2010-02-12 at 08:46 +0400, Stepan Golosunov wrote:
> 12.02.2010 в 02:42:29 + Ben Hutchings написал:
> > On Tue, 2010-02-09 at 17:26 +0400, Stepan Golosunov wrote:
> > > Package: linux-2.6
> > > Version: 2.6.32-6
> > > Severity: critical
> > > 
> > > After running 2.6.32 (as well as 2.6.31 and 2.6.30) for several minutes,
> > > computer freezes completely. Network or alt-sysrq-b do not work.
> > > 
> > > Further investigation showed that data is being corrupted while reading
> > > or writing files.
> > > Corruption on reading is easily reproduced with debsums (it fails on
> > > random files), corruption on writing happened at least once (under
> > > 2.6.32-trunk-amd64) and looks like:
> > [...]
> > 
> > Given that the first advertised feature of the P5Q Turbo motherboard is
> > 'Easy Overclocking', I have to ask: are you overclocking it?
> 
> No. Unless it overclocks something automatically.

According to the manual there is an 'Ai Tweaker' menu in the BIOS setup
program.  Check that all settings are 'Auto', except the last one. The
'CPU Margin Enhancement' setting has different options.  I found some
reports that the 'Optimized' option can result in instability and
recommending the 'Performance' option.

If the BIOS settings are already as I said or if setting them like this
does not fix the problem, please file a bug at
.  I don't know how the bug should be
assigned, but if you set the product to 'Memory Management' and
component to 'Other' then I think it will get some attention and can be
reassigned as necessary.  Let us know what the bug number is so we can
track it.

Ben.

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


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


Bug#569524: linux-image-2.6.26-2-686: cannot mount ext2 fs created by 2.6.30 but fsck is clean

2010-02-11 Thread David L. Craig
Package: linux-2.6
Version: 2.6.26-21
Severity: important

Created two USB flash drive ext2 filesystems using Sid,
one in a partition (/dev/sdc1) and one w/o MBR (/dev/sdd).
After falling back to Lenny due to instability, could not
mount either USB filesystem.  Running e2fsck found nothing
to fix.  Used tune2fs to whittle down possible options
that might be problematic without success.  Filesystems
contain large files so large_file cannot be disabled.
Am currently using debugfs to dump big files to other
media, then will try to mount w/o large_file feature.

# cat /etc/fstab
# 

#
LABEL=_100125_root  /   ext3 errors=remount-ro  0   
1
LABEL=_100125_var   /varext3 nodev  0   
2
LABEL=_100125_usr   /usrext3 nodev  0   
2
LABEL=_100125_home  /home   ext3 nodev,nosuid   0   
2
LABEL=_100125_projects  /projects   ext3 users,rw   0   
2
LABEL=_100125_spare1/spare1 ext3 defaults   0   
2
LABEL=_100125_spare2/spare2 ext3 defaults   0   
2
LABEL=NETFINITYSP   /_sys_part  vfat utf8,noauto0   0
LABEL=_u0   /_/_ua  ext2 users,noamode  0   0
LABEL=_u1   /_/_ub  ext2 users,noamode  0   0
proc/proc   proc defaults   0   0
/dev/sda2   noneswap sw 0   0
/dev/sdb2   noneswap sw 0   0
/dev/hda/media/cdrom0   udf,iso9660  users,noauto   0   0
/dev/fd0/media/floppy0  auto rw,users,noauto0   0

# mount - /_/_ua
mount: fstab path: "/etc/fstab"
mount: lock path:  "/etc/mtab~"
mount: temp path:  "/etc/mtab.tmp"
mount: going to mount LABEL=_u0 by LABEL
mount: spec:  "/dev/sdd"
mount: node:  "/_/_ua"
mount: types: "ext2"
mount: opts:  "users,noamode"
mount: mount(2) syscall: source: "/dev/sdd", target: "/_/_ua", filesystemtype: 
"ext2", mountflags: -1058209778, data: noamode
mount: wrong fs type, bad option, bad superblock on /dev/sdd,
   missing codepage or helper program, or other error
   In some cases useful info is found in syslog - try
   dmesg | tail  or so

# tune2fs -l /dev/sdc1
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name:   _u1
Last mounted on:  
Filesystem UUID:  67062ed5-8a8a-4863-84a4-289ee01d7c14
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  dir_index sparse_super large_file
Filesystem flags: signed_directory_hash 
Default mount options:(none)
Filesystem state: clean
Errors behavior:  Remount read-only
Filesystem OS type:   Linux
Inode count:  981120
Block count:  3921916
Reserved block count: 196095
Free blocks:  480744
Free inodes:  981103
First block:  0
Block size:   4096
Fragment size:4096
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8176
Inode blocks per group:   511
Filesystem created:   Sun Feb  1 18:34:34 2009
Last mount time:  Wed Jan 27 15:00:04 2010
Last write time:  Thu Feb 11 18:23:56 2010
Mount count:  0
Maximum mount count:  26
Last checked: Thu Feb 11 18:23:56 2010
Check interval:   15552000 (6 months)
Next check after: Tue Aug 10 19:23:56 2010
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 28
Desired extra isize:  28
Default directory hash:   half_md4
Directory Hash Seed:  4fe7f418-dc9d-416c-a698-a2bdf65bb856

# tune2fs -l /dev/sdd
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name:   _u0
Last mounted on:  
Filesystem UUID:  fda786bf-af75-409a-aebb-381b76cbd205
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  dir_index sparse_super large_file
Filesystem flags: signed_directory_hash 
Default mount options:(none)
Filesystem state: clean
Errors behavior:  Remount read-only
Filesystem OS type:   Linux
Inode count:  1920
Block count:  3909120
Reserved block count: 195456
Free blocks:  2392084
Free inodes:  1896
First block:  0
Block size:   4096
Fragment size:4096
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 16
Inode blocks per group:   1
Filesystem created:   Sun Jan 24 14:43:36 2010
Last mount time:  Wed Jan 27 15:00:31 2010
Last write time:  Thu Feb 11 18:34:11 2010
Moun

Bug#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686

2010-02-11 Thread Bruce Ward



maximilian attems wrote:

On Thu, 11 Feb 2010, Bruce Ward wrote:


Greetings.

More data. I have managed to get an initramfs debug out of the
system and have also provided a debug from a 2.6.26-1-686 kernel
which boots OK. I'm damned if I can see any reason from the debug
for the recent kernel (2.6.26-2-686) to fail to boot!

Interesting (but possibly not relevant) observations from my playing
around (exploration). Remember there are only a few modules (thermal
ones) loaded when the system drops out.

1. Load USB drivers - they find the pendrive, but no entry created in /dev.
2. Use mknod to create /dev/sda3 for the ext3 partition on pendrive.
sda3 is the only SCSI entry in /dev.
3. Load ext3 module, and mount the sda3 partition and, behold, there
are entries in /dev/ for sda, sda1, and sda2, as well as sda3.
4. Load the SATA drivers and suddenly there are sdb entries in /dev
for all partitions on the drive I have failed to boot from.


that points a bit to udev is it running  at this stage?
 

And more data. Attached is the list of entries in /dev at fail-time. Not 
extensive and no subdirectories. It seems that udev is doing something, 
but not enough.


Bruce

===
Bruce Ward, Nelson, New Zealand
crw-rw1 00  5,   1 Feb 12 19:12 console
crw-rw1 00 10,  63 Feb 12 19:11 cpu_dma_latency
crw-rw1 00  1,   7 Feb 12 19:11 full
crw-rw1 00 10, 228 Feb 12 19:11 hpet
crw-rw1 00  1,   2 Feb 12 19:11 kmem
crw-rw1 00  1,  11 Feb 12 19:11 kmsg
crw-rw1 00  1,   1 Feb 12 19:11 mem
crw-rw1 00 13,  63 Feb 12 19:11 mice
crw-rw1 00 10,  62 Feb 12 19:11 network_latency
crw-rw1 00 10,  61 Feb 12 19:11 network_throughput
crw-rw1 00  1,   3 Feb 12 19:11 null
crw-rw1 00  1,   4 Feb 12 19:11 port
crw-rw1 00 10,   1 Feb 12 19:11 psaux
crw-rw1 00  5,   2 Feb 12 19:11 ptmx
brw-rw1 00  1,   0 Feb 12 19:11 ram0
brw-rw1 00  1,   1 Feb 12 19:11 ram1
brw-rw1 00  1,  10 Feb 12 19:11 ram10
brw-rw1 00  1,  11 Feb 12 19:11 ram11
brw-rw1 00  1,  12 Feb 12 19:11 ram12
brw-rw1 00  1,  13 Feb 12 19:11 ram13
brw-rw1 00  1,  14 Feb 12 19:11 ram14
brw-rw1 00  1,  15 Feb 12 19:11 ram15
brw-rw1 00  1,   2 Feb 12 19:11 ram2
brw-rw1 00  1,   3 Feb 12 19:11 ram3
brw-rw1 00  1,   4 Feb 12 19:11 ram4
brw-rw1 00  1,   5 Feb 12 19:11 ram5
brw-rw1 00  1,   6 Feb 12 19:11 ram6
brw-rw1 00  1,   7 Feb 12 19:11 ram7
brw-rw1 00  1,   8 Feb 12 19:11 ram8
brw-rw1 00  1,   9 Feb 12 19:11 ram9
crw-rw1 00  1,   8 Feb 12 19:11 random
crw-rw1 00254,   0 Feb 12 19:11 rtc0
crw-rw1 00 10, 231 Feb 12 19:11 snapshot
crw-rw1 00  5,   0 Feb 12 19:11 tty
crw-rw1 00  4,   0 Feb 12 19:11 tty0
crw-rw1 00  4,   1 Feb 12 19:11 tty1
crw-rw1 00  4,  10 Feb 12 19:11 tty10
crw-rw1 00  4,  11 Feb 12 19:11 tty11
crw-rw1 00  4,  12 Feb 12 19:11 tty12
crw-rw1 00  4,  13 Feb 12 19:11 tty13
crw-rw1 00  4,  14 Feb 12 19:11 tty14
crw-rw1 00  4,  15 Feb 12 19:11 tty15
crw-rw1 00  4,  16 Feb 12 19:11 tty16
crw-rw1 00  4,  17 Feb 12 19:11 tty17
crw-rw1 00  4,  18 Feb 12 19:11 tty18
crw-rw1 00  4,  19 Feb 12 19:11 tty19
crw-rw1 00  4,   2 Feb 12 19:11 tty2
crw-rw1 00  4,  20 Feb 12 19:11 tty20
crw-rw1 00  4,  21 Feb 12 19:11 tty21
crw-rw1 00  4,  22 Feb 12 19:11 tty22
crw-rw1 00  4,  23 Feb 12 19:11 tty23
crw-rw1 00  4,  24 Feb 12 19:11 tty24
crw-rw1 00  4,  25 Feb 12 19:11 tty25
crw-rw1 00  4,  26 Feb 12 19:11 tty26
crw-rw1 00  4,  27 Feb 12 19:11 tty27
crw-rw1 00  4,  28 Feb 12 19:11 tty28
crw-rw1 00  4,  29 Feb 12 19:11 tty29
crw-rw1 00  4,   3 Feb 12 19:11 tty3
crw-rw1 00  4,  30 Feb 12 19:11 tty30
crw-rw1 00  4,  31 Feb 12 19:11 tty31
crw-rw1 0 

Bug#569524: Bug 569524: Follow-up on ext2 large_file test

2010-02-11 Thread David L. Craig
Rats, I guess.  Removing the three big files, resetting
large_file, rerunning e2fsck, and the mount is still no
different.  Do you want to look at this before I just
let Lenny remake the filesys (which had _better_ mount)?
-- 
May the LORD God bless you exceedingly abundantly!

Dave_Craig__
"'So the universe is not quite as you thought it was.
 You'd better rearrange your beliefs, then.
 Because you certainly can't rearrange the universe.'"
__--from_Nightfall_by_Asimov/Silverberg_



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