Bug#566295: initramfs-tools: Deviation from Documentation/filesystems/nfs/nfsroot.txt WRT multiple net devs

[Vagrant Cascadian]

On Sat, Apr 10, 2010 at 07:08:47AM +0200, maximilian attems wrote:
> On Fri, 09 Apr 2010, Vagrant Cascadian wrote:
> 
> > On Wed, Feb 24, 2010 at 06:22:47PM +0100, maximilian attems wrote:
> > > could you please review belows patch.
> > > if you see no objection, I'd just merge it.
> > 
> > i finally got around to testing the proposed patch (after adjusting slightly
> > for newer version). seems to work fine with 0.94.4.
> > 
> > i'd probably leave out the support for DEVICE=all (and just rely on 
> > DEVICE=""
> > working properly), but that's just personal preference.
> > 
> > live well,
> >   vagrant
> 
> thanks for your review, as I currently lack the capability of testing
> would that look at this patch, please correct me if I missed something,
> or post me your variant, that worked, thanks:

looks good to me. :)

live well,
  vagrant

> From 4a0b7bc34031bd669d94ce2e8766e4fb5d85f2c2 Mon Sep 17 00:00:00 2001
> From: maximilian attems 
> Date: Sat, 10 Apr 2010 07:04:05 +0200
> Subject: [PATCH] configure_networking(): work with empty DEVICE string
> 
> initramfs-tools currently requires a device to be hard-coded, but this
> is not much use if the network device is not known ahead of time.  If
> the device specified in either /etc/initramfs-tools/initramfs.conf or
> on the ip=xxx kernel command line.
> 
> usefull for multiple net devices.
> 
> Closes: #566295, #575766
> Signed-off-by: maximilian attems 
> ---
>  conf/initramfs.conf |5 +++--
>  scripts/functions   |7 ---
>  2 files changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/conf/initramfs.conf b/conf/initramfs.conf
> index 2aa380f..0a108a8 100644
> --- a/conf/initramfs.conf
> +++ b/conf/initramfs.conf
> @@ -58,10 +58,11 @@ BOOT=local
>  #
>  # DEVICE: ...
>  #
> -# Specify the network interface, like eth0
> +# Specify a specific network interface, like eth0
> +# Overriden by optional ip= bootarg
>  #
>  
> -DEVICE=eth0
> +DEVICE=
>  
>  #
>  # NFSROOT: [ auto | HOST:MOUNT ]
> diff --git a/scripts/functions b/scripts/functions
> index 88f1bbd..1cc9be6 100644
> --- a/scripts/functions
> +++ b/scripts/functions
> @@ -363,10 +363,10 @@ configure_networking()
>   ;;
>   ""|on|any)
>   # Bring up device
> - ipconfig -t ${ROUNDTTT} ${DEVICE}
> + ipconfig -t ${ROUNDTTT} "${DEVICE}"
>   ;;
>   dhcp|bootp|rarp|both)
> - ipconfig -t ${ROUNDTTT} -c ${IP} -d ${DEVICE}
> + ipconfig -t ${ROUNDTTT} -c ${IP} -d "${DEVICE}"
>   ;;
>   *)
>   ipconfig -t ${ROUNDTTT} -d $IP
> @@ -391,7 +391,8 @@ configure_networking()
>   # source specific bootdevice
>   . /tmp/net-${DEVICE}.conf
>   else
> - # source any interface as not exaclty specified
> + # source any interface...
> + # ipconfig should have quit after first response
>   . /tmp/net-*.conf
>   fi
>  }
> -- 
> 1.7.0.4
> 



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100410071352.gm27...@claws.fglan

Processed: Merging nfs-common bugs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> package nfs-common
Limiting to bugs with field 'package' containing at least one of 'nfs-common'
Limit currently set to 'package':'nfs-common'

> forcemerge 568194 575503
Bug#568194: mount.nfs: new default behavior breaks current /etc/fstab
Bug#575503: nfs-common: mount.nfs defaults to nfs version 4
Forcibly Merged 568194 575503.

> 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
Archive: 
http://lists.debian.org/handler.s.c.127089320519777.transcr...@bugs.debian.org

How I can install ext 4 fsys on lenny ?

[Mehran Parchebafieh]

I have a partition that it's file system is ext4, I want to have full access
on it. How i do that?!
my kernel version is 2.6.26-2-686
Debian GNU/Linux 5.0.4 "Lenny"
Thanks.

ext4 file system mounting on debian lenny.

[Mehran Parchebafieh]

I have a partition that it's file system is ext4, I want to have full access
on it. How can i do that?!
my kernel version is 2.6.26-2-686
Debian GNU/Linux 5.0.4 "Lenny"
ext4 kernel module exist but i can't mount it.
Thanks.

Bug#576838: KVM: networking stack tanks after page allocation failure

[Ben Hutchings]

On Fri, 2010-04-09 at 23:38 -0400, micah anderson wrote:
> On Sat, 10 Apr 2010 01:48:24 +0100, Ben Hutchings  
> wrote:
> > On Thu, 2010-04-08 at 12:41 -0400, micah anderson wrote:
> > > On 2010-04-08, micah anderson wrote:
> > > > On Wed, 2010-04-07 at 11:52 -0400, Micah Anderson wrote:
> > > > > Package: linux-image-2.6.32-2-amd64
> > > > > Version: 2.6.32-8~bpo50+1
> > > > > Severity: important
> > > > > 
> > > > > I'm running a tor exit node on a kvm instance, it runs for a little
> > > > > while (between an hour and 3 days), doing 30-40mbit/sec and then
> > > > > suddenly 'swapper: page allocation failure' happens, and the entire
> > > > > networking stack of the kvm instance is dead. It stops responding on
> > > > > the net completely. No ping in or out, no traffic can be observed
> > > > > using tcpdump, the counters on the interface no longer change
> > > > > (although the interface stays up).
> > > > [...]
> > > > 
> > > > It sounds like there might be a memory leak.  Please send the contents
> > > > of /proc/meminfo and /proc/slabinfo from a 'normal' state and the broken
> > > > state.
> > > 
> > > I noticed this time when it crashed something different that I had not
> > > seen in previous 2.6.30/2.6.26 kernels:
> > > 
> > > [ 7962.841287] SLUB: Unable to allocate memory on node -1 (gfp=0x20)
> > > [ 7962.841287]   cache: kmalloc-1024, object size: 1024, buffer size: 
> > > 1024, default order: 1, min order: 0
> > > [ 7962.841287]   node 0: slabs: 606, objs: 4544, free: 0
> > > 
> > > and then the normal:
> > > [ 7963.102476] swapper: page allocation failure. order:0, mode:0x4020
> > > [ 7963.105743] Pid: 0, comm: swapper Not tainted 2.6.32-bpo.2-amd64 #1
> > > [ 7963.106418] Call Trace:
> > > [ 7963.106418][] ? 
> > > __alloc_pages_nodemask+0x55b/0x5ce
> > > etc. 
> > > 
> > > As requested here is a normal state /proc/meminfo and /proc/slabinfo. See 
> > > below for
> > > the broken state
> > [...]
> > 
> > There's no sign of a memory leak and there's actually much more free
> > memory in the broken state, perhaps because any network servers have
> > lost all their clients and freed session state.  My guess is that the
> > driver just doesn't handle allocation failure gracefully.  Which network
> > driver are you using in the guest?
> 
> I started with virtio, but had a hunch that maybe switching to e100e
> might be more stable, but sadly both produce the same results.
[...]

There's no such thing as e100e - Linux has e100, e1000 and e1000e
drivers; QEMU only emulates e1000.  Please run lsmod inside the guest to
check what's really being used.

Ben.

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


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

Re: How I can install ext 4 fsys on lenny ?

[Ben Hutchings]

On Sat, 2010-04-10 at 06:15 -0400, Mehran Parchebafieh wrote:
> I have a partition that it's file system is ext4, I want to have full
> access on it. How i do that?!
> my kernel version is 2.6.26-2-686 
> Debian GNU/Linux 5.0.4 "Lenny"

You could install Linux 2.6.32 from the backports.org repository.

Ben.

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


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

Bug#577083: linux-source-2.6.33: kernel reboots immediately after "Decompressing..."

[Christoph Anton Mitterer]

On Sat, 2010-04-10 at 01:18 +0100, Ben Hutchings wrote:
> I thought you said that a custom kernel that worked in the past, had
> stopped working now.
Well... its not directly related to a linux-image-* package... so my bug
report is probably a bit off topic...but I guess something might have
been patched into linux-source-* which makes me my problems now.

And I thought, that perhaps some of you experts might have an idea.

It's definitely not hardware-problems,.. using the official linux-image
packages (either 2.6.32 or .33) and everything works fine.

I've started yesterday to compare my kernel config side by side with
debian's.
The biggest difference so far, was that I did not activate NUMA... did
that... no I come until "Decompressing... Parsing ELF...) (or so)... and
than it hangs... without rebooting.


Ah,... and I've just seen that I obviously use ld.gold for linking...
Could it be that?

I guessed binutils-gold would use the alternative mechanism (and auto
would be the "normal" ld)... but apparently not.


Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Bug#577196: linux-2.6: IPv6 addresses and routes not removed upon disconnection

[Timothy Baldwin]

Package: linux-2.6
Version: 2.6.33
Severity: normal

IPv6 addresses and routes configured on a wired Ethernet interface by SLAAC are
not removed when the network cable is disconnected. On a multi-homed host this
may result in a loss of network connectivity.  This is on a EeePC 901 and
Network Manager detects the removal of the cable.


-- System Information:
Debian Release: squeeze/sid
Architecture: i386 (i686)

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



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100409005036.6598.89485.report...@honey.localdomain

Bug#577199: linux-image-2.6.26-2-686: NULL pointer dereference at xfs:xfs_vn_getattr+0x16/0x1cf

[Sergio Gelato]

Package: linux-image-2.6.26-2-686
Version: 2.6.26-21lenny4

I periodically walk through local filesystems compiling file ownership
statistics. On one large XFS filesystem on one server, the process has
started failing after about 42 days uptime. This is the second time I
see these symptoms; the first time, a reboot cleared them. The failure
always occurs stat()ing a particular file, and once it starts happening
it is 100% reproducible. My guess is that some kernel-internal data
structure got corrupted.

Here are the relevant kernel logs (I've obfuscated the actual host name):

Apr  9 22:03:40 HOST kernel: [6289152.198741] BUG: unable to handle kernel NULL 
pointer dereference at 0008
Apr  9 22:03:40 HOST kernel: [6289152.198809] IP: [] 
:xfs:xfs_vn_getattr+0x16/0x1cf
Apr  9 22:03:40 HOST kernel: [6289152.198873] *pde = 
Apr  9 22:03:40 HOST kernel: [6289152.198903] Oops:  [#1] SMP
Apr  9 22:03:40 HOST kernel: [6289152.198933] Modules linked in: openafs(P) 
inet_diag ppdev parport_pc lp parport autofs4 ipv6 microcode firmware_class 
nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc xt_tcpudp nf_conntrack_ipv4 
xt_state nf_conntrack iptable_filter ip_tables x_tables xfs battery ac 
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore evdev snd_page_alloc 
serio_raw pcspkr psmouse i2c_piix4 button i2c_core sworks_agp agpgart dcdbas 
ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sg sd_mod ide_cd_mod cdrom 
ide_pci_generic serverworks ide_core mptspi ata_generic mptscsih floppy 
ohci_hcd mptbase scsi_transport_spi libata tg3 usbcore scsi_mod dock thermal 
processor fan thermal_sys [last unloaded: scsi_wait_scan]
Apr  9 22:03:40 HOST kernel: [6289152.199382]
Apr  9 22:03:40 HOST kernel: [6289152.199405] Pid: 26505, comm: uid-stats 
Tainted: P  (2.6.26-2-686 #1)
Apr  9 22:03:40 HOST kernel: [6289152.199453] EIP: 0060:[] EFLAGS: 
00010246 CPU: 0
Apr  9 22:03:40 HOST kernel: [6289152.199502] EIP is at 
xfs_vn_getattr+0x16/0x1cf [xfs]
Apr  9 22:03:40 HOST kernel: [6289152.199531] EAX: df41dd80 EBX:  ECX: 
 EDX: 
Apr  9 22:03:40 HOST kernel: [6289152.199563] ESI: d1e05f64 EDI: e0c0d5a0 EBP: 
d9f26080 ESP: d1e05ed0
Apr  9 22:03:40 HOST kernel: [6289152.199594]  DS: 007b ES: 007b FS: 00d8 GS: 
0033 SS: 0068
Apr  9 22:03:40 HOST kernel: [6289152.199624] Process uid-stats (pid: 26505, 
ti=d1e04000 task=deadaca0 task.ti=d1e04000)
Apr  9 22:03:40 HOST kernel: [6289152.199658] Stack: 082efb10  c1d055b8 
e0c0d5a0 d9f26080 c0177452 d1e05f64 df41dd80
Apr  9 22:03:40 HOST kernel: [6289152.199730] d1e05f64 d1e05f04 
d1e04000 c017752a df41dd80 c1d055b8 03f6
Apr  9 22:03:40 HOST kernel: [6289152.199801]   
0001  1000 0010 
Apr  9 22:03:40 HOST kernel: [6289152.199872] Call Trace:
Apr  9 22:03:40 HOST kernel: [6289152.199919]  [] 
xfs_vn_getattr+0x0/0x1cf [xfs]
Apr  9 22:03:40 HOST kernel: [6289152.199971]  [] 
vfs_getattr+0x36/0x4d
Apr  9 22:03:40 HOST kernel: [6289152.200019]  [] 
vfs_lstat_fd+0x27/0x39
Apr  9 22:03:40 HOST kernel: [6289152.200090]  [] sys_lstat64+0xf/0x23
Apr  9 22:03:40 HOST kernel: [6289152.200154]  [] 
sysenter_past_esp+0x78/0xb1
Apr  9 22:03:40 HOST kernel: [6289152.200203]  [] 
quirk_vt8235_acpi+0x5e/0x7a
Apr  9 22:03:40 HOST kernel: [6289152.200250]  ===
Apr  9 22:03:40 HOST kernel: [6289152.200276] Code: 74 12 8b 42 4c 89 81 e8 00 
00 00 8b 42 50 89 81 ec 00 00 00 c3 55 57 56 89 ce 53 83 ec 04 8b 6a 0c 31 d2 
89 d1 8b 9d 50 01 00 00 <8b> 7b 08 8b 87 04 02 00 00 c7 04 24 05 00 00 00 83 e0 
10 09 c1
Apr  9 22:03:40 HOST kernel: [6289152.200474] EIP: [] 
xfs_vn_getattr+0x16/0x1cf [xfs] SS:ESP 0068:d1e05ed0
Apr  9 22:03:40 HOST kernel: [6289152.201029] ---[ end trace 33600cae36aa9ba8 
]---

Note: although the openafs module is loaded this problem doesn't appear to
involve OpenAFS in any way. It happens on an XFS filesystem that contains
static, archived data and is not currently being exported to clients. The
only activity on that filesystem should be my nightly uid-stats script.
Of course I can't rule out that the problem may arise as a side effect of
other system activity.

This is a production server and the problem isn't severe enough to warrant
much fiddling with the system. I can, however, peek at selected portions of
kernel memory and of the filesystem on request. I should mention that
xfs_check didn't find any fault with the filesystem, and that unmounting
the filesystem and mounting it again doesn't help. Rebooting, as I said,
did clear the problem but it has now recurred.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100410120054.ga6...@astro.su.se

Processed: reopening 577083

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 577083
Bug #577083 {Done: Ben Hutchings } [linux-source-2.6.33] 
linux-source-2.6.33: kernel reboots immediately after "Decompressing..."
> 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
Archive: 
http://lists.debian.org/handler.s.c.127090505921912.transcr...@bugs.debian.org

Bug#576942: /boot/vmlinuz-2.6.32-3-amd64: kernel fix for wrong mtrr mask from MS-7252 bios may be wrong and cause problems with fglrx-driver

[Ben Hutchings]

On Sat, 2010-04-10 at 15:18 +0200, Friedrich Delgado Friedrichs wrote:
> Ben Hutchings schrieb:
> > On Thu, 2010-04-08 at 14:26 +0200, Friedrich Delgado Friedrichs wrote:
> > > [0.00] WARNING: at 
> > > /build/mattems-linux-2.6_2.6.32-9-amd64-NYTFdD/linux-2.6-2.6.32-9/debian/build/source_amd64_none/arch/x86/kernel/cpu/mtrr/generic.c:467
> > >  generic_get_mtrr+0xbf/0xf9()
> > > [0.00] Hardware name: MS-7252
> > > [0.00] mtrr: your BIOS has set up an incorrect mask, fixing it up.
> 
> > > are supposed to indicate a crash in the kernel.
> > It's not a crash, it's a warning about a BIOS bug.
> 
> In fact, that's what I suspected as well.
> 
> Is there any way this bios bug could cause me further trouble?

Probably not.

> > > I have included the full dmesg output below, currently running the
> > > free radeon driver + module.
> > [...]
> > Does this system work properly (aside from the above warning) when using
> > the radeon driver?
> 
> It appears to work properly.
> 
> I have been constantly running the radeon driver for 3 days only so
> far, but there are no stability or performance issues that came up in
> that period. I'm currently enjoying the increased 2D performance the
> free radeon driver offers me, especially with video playback.
> 
> Can I provide more useful information?

No, we have established that fglrx is at fault.

Ben.

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


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

Bug#577083: linux-source-2.6.33: kernel reboots immediately after "Decompressing..."

[Ben Hutchings]

On Sat, 2010-04-10 at 14:08 +0200, Christoph Anton Mitterer wrote:
> On Sat, 2010-04-10 at 01:18 +0100, Ben Hutchings wrote:
> > I thought you said that a custom kernel that worked in the past, had
> > stopped working now.
> Well... its not directly related to a linux-image-* package... so my bug
> report is probably a bit off topic...but I guess something might have
> been patched into linux-source-* which makes me my problems now.
> 
> And I thought, that perhaps some of you experts might have an idea.
> 
> It's definitely not hardware-problems,.. using the official linux-image
> packages (either 2.6.32 or .33) and everything works fine.
> 
> I've started yesterday to compare my kernel config side by side with
> debian's.
> The biggest difference so far, was that I did not activate NUMA... did
> that... no I come until "Decompressing... Parsing ELF...) (or so)... and
> than it hangs... without rebooting.
> 
> 
> Ah,... and I've just seen that I obviously use ld.gold for linking...
> Could it be that?
[...]

Yes, it could be.  Try with the standard linker.

Ben.

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


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

Processed: reassign 576942 to src:fglrx-driver

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 576942 src:fglrx-driver
Bug #576942 [linux-2.6] /boot/vmlinuz-2.6.32-3-amd64: kernel fix for wrong mtrr 
mask from MS-7252 bios may be wrong and cause problems with fglrx-driver
Bug reassigned from package 'linux-2.6' to 'src:fglrx-driver'.
Bug No longer marked as found in versions 2.6.32-9.
> 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
Archive: 
http://lists.debian.org/handler.s.c.127090562526143.transcr...@bugs.debian.org

Bug#577196: marked as done (linux-2.6: IPv6 addresses and routes not removed upon disconnection)

[Debian Bug Tracking System]

Your message dated Sat, 10 Apr 2010 14:18:03 +0100
with message-id <1270905483.23823.11.ca...@localhost>
and subject line Re: Bug#577196: linux-2.6: IPv6 addresses and routes not 
removed upon disconnection
has caused the Debian Bug report #577196,
regarding linux-2.6: IPv6 addresses and routes not removed upon disconnection
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.)


-- 
577196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.33
Severity: normal

IPv6 addresses and routes configured on a wired Ethernet interface by SLAAC are
not removed when the network cable is disconnected. On a multi-homed host this
may result in a loss of network connectivity.  This is on a EeePC 901 and
Network Manager detects the removal of the cable.


-- System Information:
Debian Release: squeeze/sid
Architecture: i386 (i686)

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


--- End Message ---
--- Begin Message ---
On Fri, 2010-04-09 at 01:50 +0100, Timothy Baldwin wrote:
> Package: linux-2.6
> Version: 2.6.33
> Severity: normal
> 
> IPv6 addresses and routes configured on a wired Ethernet interface by SLAAC 
> are
> not removed when the network cable is disconnected. On a multi-homed host this
> may result in a loss of network connectivity.  This is on a EeePC 901 and
> Network Manager detects the removal of the cable.

It is not the kernel's job to change routing when an interface goes
down.

Ben.

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


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

Bug#577196: linux-2.6: IPv6 addresses and routes not removed upon disconnection

[Ben Hutchings]

On Sat, 2010-04-10 at 14:18 +0100, Ben Hutchings wrote:
> On Fri, 2010-04-09 at 01:50 +0100, Timothy Baldwin wrote:
> > Package: linux-2.6
> > Version: 2.6.33
> > Severity: normal
> > 
> > IPv6 addresses and routes configured on a wired Ethernet interface by SLAAC 
> > are
> > not removed when the network cable is disconnected. On a multi-homed host 
> > this
> > may result in a loss of network connectivity.  This is on a EeePC 901 and
> > Network Manager detects the removal of the cable.
> 
> It is not the kernel's job to change routing when an interface goes
> down.

To be more precise: it is not the kernel's job to change routing when a
link goes down.  It does remove routes when the interface is
administratively taken down (e.g. with ifconfig down).  It is the job of
a routing daemon such as Network Manager to change routing when the link
state changes.  If NM does not support SLAAC (whatever that is) then you
might consider filing a wishlist bug for that.

Ben.

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


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

Bug#577083: linux-source-2.6.33: kernel reboots immediately after "Decompressing..."

[Bastian Blank]

On Sat, Apr 10, 2010 at 02:08:47PM +0200, Christoph Anton Mitterer wrote:
> Ah,... and I've just seen that I obviously use ld.gold for linking...
> Could it be that?

Yes. Linux is known to have slightly broken linker scripts.

Bastian

-- 
Warp 7 -- It's a law we can live with.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100410133226.ga9...@wavehammer.waldi.eu.org

Bug#577211: linux-image-2.6.32-3-686: intermittent spiking iowait

[Torgeir Skjøtskift]

Package: linux-2.6
Version: 2.6.32-9
Severity: normal
Tags: sid

This is the configuration:  root on a raid 1 on top of an lvm consisting of two
PVs (two 1TB Western digital hdds).  This is what I'm experiencing:  While
mounted, the system suddenly will become unresponsive / freeze for a period of
up to 20-30 seconds.   Running iostat on a 10 second interval revealed iowait
percentages up to 99% over a 30 second period (max).  Looking at iotop output I
could see the following at the top of the list during the spikes:430 be/4
root0.00 B/s0.00 B/s  0.00 % 99.99 % [kjournald]


-- Package-specific info:
** Version:
Linux version 2.6.32-3-686 (Debian 2.6.32-9) (m...@debian.org) (gcc version 
4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Feb 25 06:14:20 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-3-686 root=/dev/mapper/vg01-lv01 ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[ 4812.706236] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
[ 4812.707163] SGI XFS Quota Management subsystem
[ 4812.729103] JFS: nTxBlock = 8192, nTxLock = 65536
[ 4812.793628] NTFS driver 2.1.29 [Flags: R/W MODULE].
[ 4812.16] QNX4 filesystem 0.2.3 registered.

** Model information
not available

** Loaded modules:
Module  Size  Used by
ufs56150  0 
qnx45118  0 
hfsplus61001  0 
hfs33093  0 
minix  17814  0 
ntfs  163909  0 
vfat6538  0 
msdos   5118  0 
fat34908  2 vfat,msdos
jfs   134642  0 
xfs   415456  0 
exportfs2618  1 xfs
reiserfs  176200  0 
ext2   46289  0 
ppdev   4058  0 
lp  5570  0 
sco 5837  2 
bridge 32983  0 
stp  996  1 bridge
bnep7444  2 
rfcomm 25131  4 
l2cap  21677  16 bnep,rfcomm
vboxnetadp  5154  0 
vboxnetflt 10202  0 
vboxdrv   114837  2 vboxnetadp,vboxnetflt
nls_utf8 908  0 
cifs  234274  0 
fuse   43750  1 
loop9753  0 
firewire_sbp2   9639  0 
ext4  254909  1 
jbd2   56059  1 ext4
crc16   1027  2 l2cap,ext4
snd_hda_codec_realtek   163098  1 
snd_hda_intel  16427  5 
btusb   7997  2 
snd_hda_codec  46002  2 snd_hda_codec_realtek,snd_hda_intel
bluetooth  36327  9 sco,bnep,rfcomm,l2cap,btusb
rfkill 10260  2 bluetooth
ipaq   14628  0 
snd_hwdep   4054  1 snd_hda_codec
snd_pcm_oss28671  0 
snd_mixer_oss  10461  1 snd_pcm_oss
snd_pcm47362  4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi3576  0 
usbserial  21843  1 ipaq
snd_rawmidi12505  1 snd_seq_midi
snd_seq_midi_event  3684  1 snd_seq_midi
snd_seq35459  2 snd_seq_midi,snd_seq_midi_event
i2c_nforce2 4464  0 
joydev  6771  0 
asus_atk01106770  0 
pcspkr  1207  0 
evdev   5609  10 
snd_timer  12258  3 snd_pcm,snd_seq
parport_pc 15799  1 
snd_seq_device  3673  3 snd_seq_midi,snd_rawmidi,snd_seq
parport22554  3 ppdev,lp,parport_pc
snd34363  19 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore   3450  1 snd
psmouse44413  0 
serio_raw   2916  0 
processor  26571  2 
snd_page_alloc  5041  2 snd_hda_intel,snd_pcm
ext3   94192  1 
jbd32161  1 ext3
mbcache 3762  3 ext2,ext4,ext3
dm_mod 46074  7 
raid1  16099  1 
md_mod 67165  2 raid1
hid_logitech5006  0 
ff_memless  3008  1 hid_logitech
usbhid 27888  1 hid_logitech
hid50657  2 hid_logitech,usbhid
sd_mod 25781  6 
crc_t10dif  1012  1 sd_mod
ide_cd_mod 21076  0 
cdrom  26487  1 ide_cd_mod
ata_generic 2015  0 
ohci_hcd   16904  0 
nvidia   9791992  40 
ide_pci_generic 1924  0 
agpgart19516  1 nvidia
sata_nv15422  4 
amd74xx 3552  0 
firewire_ohci  16509  0 
firewire_core  31139  2 firewire_sbp2,firewire_ohci
crc_itu_t   1035  1 firewire_core
i2c_core   12648  2 i2c_nforce2,nvidia
button  3598  0 
ahci   26966  0 
libata

Processed: tagging 566295

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 566295 pending
Bug #566295 [initramfs-tools] initramfs-tools: Deviation from 
Documentation/filesystems/nfs/nfsroot.txt WRT multiple net devs
Added tag(s) pending.
> 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
Archive: 
http://lists.debian.org/handler.s.c.127090813118252.transcr...@bugs.debian.org

Processed: tagging 575766

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 575766 pending
Bug #575766 [initramfs-tools] initramfs-tools: configure_networking function 
fails if no DEVICE is specified
Added tag(s) pending.
> 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
Archive: 
http://lists.debian.org/handler.s.c.127090813518304.transcr...@bugs.debian.org

Processed: block 576603 with 576678

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 576603 with 576678
Bug #576603 [initramfs-tools] stay in sid to settle dust
Was blocked by: 576677 576700 576488 576654 576641
Added blocking bug(s) of 576603: 576678
> 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
Archive: 
http://lists.debian.org/handler.s.c.127090867122780.transcr...@bugs.debian.org

Bug#566295: initramfs-tools: Deviation from Documentation/filesystems/nfs/nfsroot.txt WRT multiple net devs

[maximilian attems]

On Sat, Apr 10, 2010 at 12:13:52AM -0700, Vagrant Cascadian wrote:
> On Sat, Apr 10, 2010 at 07:08:47AM +0200, maximilian attems wrote:
> > On Fri, 09 Apr 2010, Vagrant Cascadian wrote:
> > > i finally got around to testing the proposed patch (after
> > > adjusting slightly for newer version). seems to work fine with
> > > 0.94.4.
> > > 
> > > i'd probably leave out the support for DEVICE=all (and just rely
> > > on DEVICE="" working properly), but that's just personal
> > > preference.
> > > 
> > > live well,
> > >   vagrant
> > 
> > thanks for your review, as I currently lack the capability of testing
> > would that look at this patch, please correct me if I missed something,
> > or post me your variant, that worked, thanks:
> 
> looks good to me. :)
> 
> live well,
>   vagrant

thanks pushed out, with reviewed-by tag and based on note:
http://git.debian.org/?p=kernel/initramfs-tools.git;a=commit;h=24875289070511b1039b690e72cf241b5d554688

happy hacking, sunny greetings
maks



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100410135400.gv6...@baikonur.stro.at

Bug#577215: linux-image-2.6.32-trunk-686: X failed to start with error "no screen found"

[sevenever]

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

linux-image-2.6.31-686 works fine.
If reboot to 2.6.32 X failed to start with error "no screen found"


-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-686 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc 
version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 06:32:16 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686 
root=UUID=23f3ae68-8897-4f68-91a2-8e7f0cfb8d8d ro quiet

** Not tainted

** Kernel log:
[4.202019] usb 3-2: New USB device found, idVendor=045e, idProduct=0040
[4.202024] usb 3-2: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[4.202027] usb 3-2: Product: Microsoft 3-Button Mouse with IntelliEye(TM)
[4.202030] usb 3-2: Manufacturer: Microsoft
[4.202127] usb 3-2: configuration #1 chosen from 1 choice
[4.212343] input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as 
/devices/pci:00/:00:02.1/usb3/3-2/3-2:1.0/input/input0
[4.212413] generic-usb 0003:045E:0040.0003: input,hidraw0: USB HID v1.10 
Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on 
usb-:00:02.1-2/input0
[4.548167] PM: Starting manual resume from disk
[4.575830] kjournald starting.  Commit interval 5 seconds
[4.575840] EXT3-fs: mounted filesystem with ordered data mode.
[6.43] udev: starting version 151
[7.186947] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[7.186956] ACPI: Power Button [PWRB]
[7.187068] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[7.187073] ACPI: Power Button [PWRF]
[7.197247] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[7.197642] processor LNXCPU:00: registered as cooling_device0
[7.203220] Linux agpgart interface v0.103
[7.299156] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[7.327609] input: PC Speaker as /devices/platform/pcspkr/input/input3
[7.379985] agpgart-amd64 :00:00.0: AGP bridge [10de/00e1]
[7.380027] agpgart-amd64 :00:00.0: aperture size 4096 MB is not right, 
using settings from NB
[7.380032] agpgart-amd64 :00:00.0: setting up Nforce3 AGP
[7.385720] agpgart-amd64 :00:00.0: AGP aperture is 128M @ 0xf000
[7.421638] parport_pc 00:06: reported by Plug and Play ACPI
[7.421707] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[7.436059] parport0: Printer, Hewlett-Packard HP LaserJet 6L Pro
[7.483063] ACPI: I/O resource nForce2_smbus [0x5000-0x503f] conflicts with 
ACPI region SMRG [0x5000-0x5004]
[7.483100] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[7.483104] nForce2_smbus :00:01.1: Error probing SMB1.
[7.483188] i2c i2c-0: nForce2 SMBus adapter at 0x5040
[7.497333] input: MLK rapoo 1800 as 
/devices/pci:00/:00:02.1/usb3/3-1/3-1:1.0/input/input4
[7.497417] sunplus 0003:04FC:05D8.0001: input,hidraw1: USB HID v1.00 
Keyboard [MLK rapoo 1800] on usb-:00:02.1-1/input0
[7.506028] sunplus 0003:04FC:05D8.0002: fixing up Sunplus Wireless Desktop 
report descriptor
[7.507587] input: MLK rapoo 1800 as 
/devices/pci:00/:00:02.1/usb3/3-1/3-1:1.1/input/input5
[7.509717] sunplus 0003:04FC:05D8.0002: input,hiddev96,hidraw2: USB HID 
v1.00 Mouse [MLK rapoo 1800] on usb-:00:02.1-1/input1
[8.469987] ACPI: PCI Interrupt Link [LAUI] enabled at IRQ 20
[8.469995] Intel ICH :00:06.0: PCI INT A -> Link[LAUI] -> GSI 20 
(level, low) -> IRQ 20
[8.470031] Intel ICH :00:06.0: setting latency timer to 64
[8.792010] intel8x0_measure_ac97_clock: measured 54659 usecs (2680 samples)
[8.792014] intel8x0: clocking to 46990
[9.020037] Adding 2714944k swap on /dev/sda5.  Priority:-1 extents:1 
across:2714944k 
[9.176380] EXT3 FS on sda1, internal journal
[9.395562] ide-cd driver 5.00
[9.400828] ide_generic: please use "probe_mask=0x3f" module parameter for 
probing all legacy ISA IDE ports
[9.463699] usbcore: registered new interface driver cdc_ether
[9.465246] usbcore: registered new interface driver zaurus
[9.521464] [drm] Initialized drm 1.1.0 20060810
[9.593799] [drm] radeon kernel modesetting enabled.
[9.594120] ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 19
[9.594132] radeon :01:00.0: PCI INT A -> Link[LNKE] -> GSI 19 (level, 
low) -> IRQ 19
[9.597324] [drm] radeon: Initializing kernel modesetting.
[9.597380] [drm] register mmio base: 0xFF58
[9.597382] [drm] register mmio size: 524288
[9.598379] [drm] GPU reset succeed (RBBM_STATUS=0x0140)
[9.598397] agpgart-amd64 :00:00.0: AGP 2.0 bridge
[9.598413] agpgart-amd64 :00:00.0: putting AGP V2 device into 4x mode
[9.598443] radeon :01:00.0: putting AGP V2 device into 4x mode
[9.598448] [drm] radeon: VRAM 64M
[9.598450] [drm] radeon: VRAM from 0x to 0x03FF
[9.598452] [drm] rade

Processed: Re: Bug#577215: linux-image-2.6.32-trunk-686: X failed to start with error "no screen found"

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 577215 moreinfo
Bug #577215 [linux-2.6] linux-image-2.6.32-trunk-686: X failed to start with 
error "no screen found"
Added tag(s) moreinfo.
> stop
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
Archive: 
http://lists.debian.org/handler.s.c.127091115613601.transcr...@bugs.debian.org

Bug#577215: linux-image-2.6.32-trunk-686: X failed to start with error "no screen found"

[maximilian attems]

tags 577215 moreinfo
stop

On Sat, Apr 10, 2010 at 10:28:53PM +0800, sevenever wrote:
> Package: linux-2.6
> Version: 2.6.32-5
> Severity: normal
> 
> linux-image-2.6.31-686 works fine.
> If reboot to 2.6.32 X failed to start with error "no screen found"

this is a very old 2.6.32 version try newer 2.6.32-11 from
unstable.

thanks



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2010041014.ga32...@baikonur.stro.at

Bug#577215: linux-image-2.6.32-trunk-686: X failed to start with error "no screen found"

[Ben Hutchings]

On Sat, 2010-04-10 at 22:28 +0800, sevenever wrote:
> Package: linux-2.6
> Version: 2.6.32-5

This is out of date; please try linux-image-2.6.32-4-686 (version
2.6.32-11) from unstable.

> Severity: normal
> 
> linux-image-2.6.31-686 works fine.
> If reboot to 2.6.32 X failed to start with error "no screen found"
[...]

If this still doesn't work with a later kernel version,
send /var/log/Xorg.0.log

Ben.

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


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

Bug#576838: KVM: networking stack tanks after page allocation failure

[micah anderson]

On Sat, 10 Apr 2010 12:17:51 +0100, Ben Hutchings  wrote:
> On Fri, 2010-04-09 at 23:38 -0400, micah anderson wrote:
> > On Sat, 10 Apr 2010 01:48:24 +0100, Ben Hutchings  
> > wrote:
> > > On Thu, 2010-04-08 at 12:41 -0400, micah anderson wrote:
> > > > On 2010-04-08, micah anderson wrote:
> > > > > On Wed, 2010-04-07 at 11:52 -0400, Micah Anderson wrote:
> > > > > > Package: linux-image-2.6.32-2-amd64
> > > > > > Version: 2.6.32-8~bpo50+1
> > > > > > Severity: important
> > > > > > 
> > > > > > I'm running a tor exit node on a kvm instance, it runs for a little
> > > > > > while (between an hour and 3 days), doing 30-40mbit/sec and then
> > > > > > suddenly 'swapper: page allocation failure' happens, and the entire
> > > > > > networking stack of the kvm instance is dead. It stops responding on
> > > > > > the net completely. No ping in or out, no traffic can be observed
> > > > > > using tcpdump, the counters on the interface no longer change
> > > > > > (although the interface stays up).
> > > > > [...]
> > > > > 
> > > > > It sounds like there might be a memory leak.  Please send the contents
> > > > > of /proc/meminfo and /proc/slabinfo from a 'normal' state and the 
> > > > > broken
> > > > > state.
> > > > 
> > > > I noticed this time when it crashed something different that I had not
> > > > seen in previous 2.6.30/2.6.26 kernels:
> > > > 
> > > > [ 7962.841287] SLUB: Unable to allocate memory on node -1 (gfp=0x20)
> > > > [ 7962.841287]   cache: kmalloc-1024, object size: 1024, buffer size: 
> > > > 1024, default order: 1, min order: 0
> > > > [ 7962.841287]   node 0: slabs: 606, objs: 4544, free: 0
> > > > 
> > > > and then the normal:
> > > > [ 7963.102476] swapper: page allocation failure. order:0, mode:0x4020
> > > > [ 7963.105743] Pid: 0, comm: swapper Not tainted 2.6.32-bpo.2-amd64 #1
> > > > [ 7963.106418] Call Trace:
> > > > [ 7963.106418][] ? 
> > > > __alloc_pages_nodemask+0x55b/0x5ce
> > > > etc. 
> > > > 
> > > > As requested here is a normal state /proc/meminfo and /proc/slabinfo. 
> > > > See below for
> > > > the broken state
> > > [...]
> > > 
> > > There's no sign of a memory leak and there's actually much more free
> > > memory in the broken state, perhaps because any network servers have
> > > lost all their clients and freed session state.  My guess is that the
> > > driver just doesn't handle allocation failure gracefully.  Which network
> > > driver are you using in the guest?
> > 
> > I started with virtio, but had a hunch that maybe switching to e100e
> > might be more stable, but sadly both produce the same results.
> [...]
> 
> There's no such thing as e100e - Linux has e100, e1000 and e1000e
> drivers; QEMU only emulates e1000.  Please run lsmod inside the guest to
> check what's really being used.

Indeed... it looks like regardless if I have specified 'e100e' in the
domain.xml, its ignoring that failure and providing me with:

virtio_net 10433  0 
virtio  3277  5 
virtio_rng,virtio_balloon,virtio_net,virtio_blk,virtio_pci

The host is running:

e1000e109487  0 

So i guess I can try that...

micah


pgpzTKkr0wR8q.pgp
Description: PGP signature

Bug#577227: linux-2.6: [INTL:pt] Updated Portuguese translation for debconf messages

[Américo Monteiro]

Package: linux-2.6
Version: 2.6.32-11
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for linux-2.6's debconf messages.
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .


-- 
Best regards,

Américo Monteiro
"Traduz" - Portuguese Translation Team
http://www.DebianPT.org
# Translation of linux-2.6 debconf messages to Portuguese
# Copyright (C) 2010 the linux-2.6's copyright holder
# This file is distributed under the same license as the linux-2.6 package.
#
# Américo Monteiro , 2010.
msgid ""
msgstr ""
"Project-Id-Version: linux-2.6 2.6.32-11\n"
"Report-Msgid-Bugs-To: linux-...@packages.debian.org\n"
"POT-Creation-Date: 2010-03-29 14:15+0100\n"
"PO-Revision-Date: 2010-04-10 16:35+0100\n"
"Last-Translator: Américo Monteiro \n"
"Language-Team: Portuguese \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 1.0\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: boolean
#. Description
#: ../linux-base.templates:1001
msgid "Update disk device ids in system configuration?"
msgstr ""
"Actualizar os ids dos dispositivos de disco na configuração do sistema?"

#. Type: boolean
#. Description
#: ../linux-base.templates:1001
msgid ""
"The new Linux kernel version provides different drivers for some PATA (IDE) "
"controllers.  The names of some hard disk, CD-ROM and tape devices may "
"change."
msgstr ""
"A nova versão de kernel Linux disponibiliza drivers diferentes para alguns "
"controladores PATA (IDE). Os nomes de alguns discos rígidos, CD-ROM e "
"dispositivos de fita magnética poderão mudar."

#. Type: boolean
#. Description
#: ../linux-base.templates:1001
msgid ""
"You are recommended to identify disk devices in configuration files by label "
"or UUID (unique identifier) rather than by device name, which will work with "
"both old and new kernel versions.  Your system configuration can be updated "
"automatically in most cases."
msgstr ""
"É-lhe recomendado identificar os dispositivos de discos nos ficheiros de "
"configuração pela etiqueta ou UUID (identificador único) em vez do nome de "
"dispositivo, o qual irá funcionar com ambas versões de kernel antiga e nova. "
"Na maioria dos casos a configuração do seu sistema pode ser actualizada "
"automaticamente."

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "Apply these configuration changes to disk device ids?"
msgstr ""
"Aplicar estas alterações de configuração aos ids de dispositivos de discos?"

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid "These devices will be assigned UUIDs or labels:"
msgstr "A estes dispositivos serão atribuídos UUIDs ou etiquetas:"

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid "${relabel}"
msgstr "${relabel}"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "These configuration files will be updated:"
msgstr "Estes ficheiros de configuração irão ser actualizados:"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "${files}"
msgstr "${files}"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "The device ids will be changed as follows:"
msgstr "Os ids de dispositivos irão ser alterados de acordo com o seguinte:"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "${id_map}"
msgstr "${id_map}"

#. Type: note
#. Description
#: ../linux-base.templates:4001
msgid "Please check these configuration files before rebooting"
msgstr ""
"Por favor verifique estes ficheiros de configuração antes de reiniciar o "
"sistema"

#. Type: note
#. Description
#: ../linux-base.templates:4001
msgid ""
"These configuration files still use some device names that may change when "
"using the new kernel:"
msgstr ""
"Estes ficheiros de configuração ainda usam alguns nomes de dispositivos que "
"podem alterar quando usar o novo kernel:"

#. Type: note
#. Description
#: ../linux-base.templates:4001
msgid "${unconverted}"
msgstr "${unconverted}"

#. Type: note
#. Description
#: ../linux-base.templates:5001
msgid "Check the boot loader configuration before rebooting"
msgstr ""
"Verifique a configuração do gestor de arranque antes de reiniciar o sistema"

#. Type: note
#. Description
#: ../linux-base.templates:5001
msgid ""
"The boot loader configuration for this system was not recognised.  These "
"settings in the configuration may need to be updated:"
msgstr ""
"A configuração do gestor de arranque para este sistema não foi reconhecida. "
"Estas definições na configuração podem precisar de ser actualizadas:"

#. Typ

Bug#577215: linux-image-2.6.32-trunk-686: X failed to start with error "no screen found"

[Feng Shao]

On Sat, Apr 10, 2010 at 11:08 PM, Ben Hutchings  wrote:
> On Sat, 2010-04-10 at 22:28 +0800, sevenever wrote:
>> Package: linux-2.6
>> Version: 2.6.32-5
>
> This is out of date; please try linux-image-2.6.32-4-686 (version
> 2.6.32-11) from unstable.


the new version 2.6.32-4-686 works.

for more infomation, I post my Xorg.0.log here.
my video card is radeon 7200, using open source driver.

Thanks a lot!


Xorg.0.log.old
Description: application/trash

Processed: closing 577215

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # submitter reported as fixed
> close 577215 2.6.32-11
Bug#577215: linux-image-2.6.32-trunk-686: X failed to start with error "no 
screen found"
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.6.32-11, send any further explanations to 
sevenever 

> 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
Archive: 
http://lists.debian.org/handler.s.c.127091592630932.transcr...@bugs.debian.org

Processed: unarchiving 509923, reopening 509923

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 509923
Bug #509923 {Done: maximilian attems } [linux-2.6] linux-2.6: 
hd's no longer found on marvell 88SE6145 sata controller
Unarchived Bug 509923
> reopen 509923
Bug #509923 {Done: maximilian attems } [linux-2.6] linux-2.6: 
hd's no longer found on marvell 88SE6145 sata controller
> 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
Archive: 
http://lists.debian.org/handler.s.c.127092415030428.transcr...@bugs.debian.org

Bug#509923: linux-2.6: hd's no longer found on marvell 88SE6145 sata controller

[Ben Hutchings]

On Mon, 2010-02-01 at 14:14 +0100, maximilian attems wrote:
> On Mon, 26 Oct 2009, Tom Jägermeister wrote:
> 
> > Hi Ben,
> > 
> > this issue was almost a year ago but I can remember it as it was quiet 
> > annoying.
> > It turned out that I had to use module 'ahci' instead of 'pata_marvell', I 
> > found the hint in the kernel config. However in the previous kernels 
> > (before 
> > 2.6.26-12 pata_marvell had worked alright).
> > Unfortunately pata_marvell seems to be preferred over ahci for the 
> > mentioned 
> > controller, so I had blacklisted the module and built all later kernels 
> > without it. No more problems after ...
> 
> closing as this indicates only a stable device names bug,
> which is userspace related and should be fixed by newer d-i that uses
> UUID and maybe soon on upgrade too.

This is not the problem.  The problem is that these controllers use a
single PCI function for all ports, implementing both AHCI and legacy HD
interfaces.  (Most PATA+SATA controllers have separate PCI functions.)
So one driver must bind to this function and handle all ports, but
instead we have two half-working libata drivers for this hardware:

- pata_marvell uses the legacy HD interfaces to drive both PATA and SATA
ports (despite its name), but apparently doesn't work with the SATA
ports on the 6145.

- ahci uses the AHCI, which is for SATA ports only.  Since it doesn't
support the PATA ports (bug #507432), it no longer binds to these
controllers by default (since upstream version 2.6.27 and Debian version
2.6.26-12).  In order to use it, you must blacklist pata_marvell and set
the ahci module option marvell_enable=1.

Since pata_marvell doesn't seem to work properly with the SATA ports on
the 6145, users may currently be *required* to change module parameters
just to make it work (and then without PATA functionality).

Dan Alderman has also run into this problem, and pointed me at the
vendor driver
 
which may be somewhat useful in understanding how to drive this hardware (no 
datasheet is available).  But it is very different from a standard Linux ATA 
driver.

Ben.

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


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

Adding new drivers to Debian's 2.6.32 kernel?

[Bjørn Mork]

Hello,

I am aware of the policy stated on
http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines
and that this in general means that new features/drivers are rejected.

I still would like to ask for an exception: The "mantis" DVB driver was
included in upstream version 2.6.33. This driver is very self contained,
adding one directory under drivers/media/dvb/, 5 files (2 new frontends)
under drivers/media/dvb/frontends/, a one-line bugfix patch to
drivers/media/dvb/frontends/tda10021.c (which might be forwarded through
upstream stable, if so required) and otherwise only the necessary
Makefile and Kconfig changes.

I do realize that current policy is that new drivers should be packaged
as dkms source packages, but I believe that this is not a good solution
in this specific case because:
 - the separate driver package will only ever be needed for the 2.6.32 kernel
 - the driver is highly integrated in the DVB subsystem and links with a
   number of existing frontends.  The necessary header files are not
   part of linux-headers and would therefore have to be copied from the
   kernel source, creating problems if these should ever be changed.

Do you think an exception may be possible for this driver?  If so, I can
prepare a patch proposal for review.

If not, then I guess a dkms package is the way forward.  In that case,
do you have any guidelines on how to deal with the inclusion of header
files from kernel source?  The necessary headers are:

drivers/media/dvb/dvb-core/demux.h
drivers/media/dvb/dvb-core/dmxdev.h
drivers/media/dvb/dvb-core/dvb_ca_en50221.h
drivers/media/dvb/dvb-core/dvb_demux.h
drivers/media/dvb/dvb-core/dvbdev.h
drivers/media/dvb/dvb-core/dvb_frontend.h
drivers/media/dvb/dvb-core/dvb_net.h
drivers/media/dvb/dvb-core/dvb_ringbuffer.h
drivers/media/dvb/frontends/lnbp21.h
drivers/media/dvb/frontends/stb0899_cfg.h
drivers/media/dvb/frontends/stb0899_drv.h
drivers/media/dvb/frontends/stb0899_reg.h
drivers/media/dvb/frontends/stb6100_cfg.h
drivers/media/dvb/frontends/stb6100.h
drivers/media/dvb/frontends/stv0299.h
drivers/media/dvb/frontends/zl10353.h



Bjørn


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ljcvru48@nemi.mork.no

Re: Adding new drivers to Debian's 2.6.32 kernel?

[Ben Hutchings]

On Sat, 2010-04-10 at 21:21 +0200, Bjørn Mork wrote:
> Hello,
> 
> I am aware of the policy stated on
> http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines
> and that this in general means that new features/drivers are rejected.

That page is quite outdated, and I should fix it.  New drivers can be
added so long as they have already been accepted upstream.

[...]
> I do realize that current policy is that new drivers should be packaged
> as dkms source packages, but I believe that this is not a good solution
> in this specific case because:

We recommend DKMS for out-of-tree drivers, that is drivers that have not
been accepted upstream.

[...]
> Do you think an exception may be possible for this driver?  If so, I can
> prepare a patch proposal for review.

Please do.  Also, report this as a bug.

Ben.

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


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

Re: Adding new drivers to Debian's 2.6.32 kernel?

[Bjørn Mork]

Ben Hutchings  writes:

> On Sat, 2010-04-10 at 21:21 +0200, Bjørn Mork wrote:
>> Hello,
>> 
>> I am aware of the policy stated on
>> http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines
>> and that this in general means that new features/drivers are rejected.
>
> That page is quite outdated, and I should fix it.  New drivers can be
> added so long as they have already been accepted upstream.
>
> [...]
>> I do realize that current policy is that new drivers should be packaged
>> as dkms source packages, but I believe that this is not a good solution
>> in this specific case because:
>
> We recommend DKMS for out-of-tree drivers, that is drivers that have not
> been accepted upstream.
>
> [...]
>> Do you think an exception may be possible for this driver?  If so, I can
>> prepare a patch proposal for review.
>
> Please do.  Also, report this as a bug.

Thanks. Great news!  Will do ASAP.


Bjørn


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87hbnjrtco@nemi.mork.no

Bug#577253: initramfs-tools: Keyboard is not active / detected anymore, so LVM boot passphrase entry is broken

[Colin Darie]

Package: initramfs-tools
Version: 0.94.4
Severity: normal
Tags: sid

The generated initrd image after an upgrade to initramfs-tools 0.94.4 (from
0.93.x) renders my keyboard inactive in the LVM passphrase prompt (nothing
happens when I enter my passphrase, so I guess the keyboard is not detected
anymore). Of course, using the previous initrd image works perfectly well.  I'm
runnning on a MacBook Pro so I guess it's not really a common case. How can I
provide more informations ?  Thanks.  --- Colin Darie


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.32-4-amd64 root=/dev/mapper/VM_group-LV_system ro quiet

-- /proc/filesystems
ext4
ext2
fuseblk

-- lsmod
Module  Size  Used by
acpi_cpufreq  0 
cpufreq_powersave902  0 
cpufreq_stats   2659  0 
cpufreq_conservative 5162  0 
cpufreq_userspace   1992  0 
binfmt_misc 6431  1 
uinput  6376  1 
fuse   50110  3 
ext2   52985  1 
coretemp4213  0 
loop   11783  0 
firewire_sbp2  11466  0 
snd_hda_codec_cirrus 8247  1 
snd_hda_intel  19795  4 
snd_hda_codec  54212  2 snd_hda_codec_cirrus,snd_hda_intel
snd_hwdep   5364  1 snd_hda_codec
snd_pcm_oss32591  0 
snd_mixer_oss  12606  1 snd_pcm_oss
snd_pcm60439  4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi4400  0 
snd_rawmidi15483  1 snd_seq_midi
snd_seq_midi_event  4628  1 snd_seq_midi
snd_seq42817  2 snd_seq_midi,snd_seq_midi_event
uvcvideo   51695  0 
applesmc   20986  0 
nvidia   9505953  58 
videodev   29993  1 uvcvideo
joydev  8411  0 
snd_timer  15502  3 snd_pcm,snd_seq
bcm5974 6353  0 
v4l1_compat11442  2 uvcvideo,videodev
snd_seq_device  4477  3 snd_seq_midi,snd_rawmidi,snd_seq
lib80211_crypt_tkip 7493  0 
btusb   9785  0 
led_class   2401  1 applesmc
v4l2_compat_ioctl32 8538  1 videodev
bluetooth  41795  1 btusb
snd46350  17 
snd_hda_codec_cirrus,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore   4598  1 snd
shpchp 26264  0 
rfkill 13012  1 bluetooth
snd_page_alloc  6217  2 snd_hda_intel,snd_pcm
wl   1937867  0 
pcspkr  1699  0 
i2c_nforce2 5280  0 
pci_hotplug21171  1 shpchp
evdev   7336  25 
input_polldev   1967  1 applesmc
i2c_core   15584  3 nvidia,videodev,i2c_nforce2
ac  2192  0 
battery 4998  0 
processor  30247  3 acpi_cpufreq
lib802113638  2 lib80211_crypt_tkip,wl
ext4  285163  3 
mbcache 4970  2 ext2,ext4
jbd2   66887  1 ext4
crc16   1319  1 ext4
cbc 2539  1 
hid_apple   4290  0 
usbhid 33260  0 
hid62793  2 hid_apple,usbhid
usb_storage39449  0 
sg 18728  0 
sd_mod 29689  4 
sr_mod 12602  0 
crc_t10dif  1276  1 sd_mod
cdrom  29399  1 sr_mod
ata_generic 2983  0 
ohci_hcd   19212  0 
ehci_hcd   30802  0 
ahci   32166  3 
libata132199  2 ata_generic,ahci
firewire_ohci  19484  0 
firewire_core  36688  2 firewire_sbp2,firewire_ohci
button  4634  0 
crc_itu_t   1307  1 firewire_core
scsi_mod  121941  6 
firewire_sbp2,usb_storage,sg,sd_mod,sr_mod,libata
mbp_nvidia_bl   1715  0 
forcedeth  45448  0 
usbcore   121799  8 
uvcvideo,bcm5974,btusb,usbhid,usb_storage,ohci_hcd,ehci_hcd
nls_base6377  1 usbcore
thermal11674  0 
fan 3346  0 
thermal_sys11878  3 processor,thermal,fan
aes_generic25714  2 
sha256_generic  8692  2 
dm_crypt   10507  1 
dm_mod 53690  12 dm_crypt

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=eth0
NFSROOT=auto

-- /etc/crypttab
chopinance UUID=dbfff96c-3a57-424c-9746-45530ee3567a none luks


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

Kernel: Linux 2.6.32-4-amd64 (SMP w/2 C

Processed: tagging 576925

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 576925 + pending
Bug #576925 [linux-base] [linux-base] postinst fails on undefined subroutine
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
Archive: 
http://lists.debian.org/handler.s.c.127093045814987.transcr...@bugs.debian.org

Processed: tagging 576925

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 576925 + pending
Bug #576925 [linux-base] [linux-base] postinst fails on undefined subroutine
Ignoring request to alter tags of bug #576925 to the same tags previously set
>
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
Archive: 
http://lists.debian.org/handler.s.c.12709329163868.transcr...@bugs.debian.org

Processed: tagging 577047

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 577047 + pending
Bug #577047 [linux-base] device ids will be changed as follows: (blank)
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
Archive: 
http://lists.debian.org/handler.s.c.12709329193957.transcr...@bugs.debian.org

Bug#577047: device ids will be changed as follows: (blank)

[Ben Hutchings]

On Fri, 2010-04-09 at 11:46 -0400, Anthony DeRobertis wrote:
> On Fri, Apr 09, 2010 at 11:24:23AM +0100, Ben Hutchings wrote:
> > 
> > Right.  And it is generally able to convert references to CD drives.
> > Please send the contents of /etc/udev/rules.d/70-persistent-cd.rules and
> > the output of 'ls -l /dev/disk/by-id'.
> 
> anth...@feynman:~$ cat /etc/udev/rules.d/70-persistent-cd.rules 
> # This file was automatically generated by the /lib/udev/write_cd_rules
> # program, probably run by the cd-aliases-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single line
> # and set the $GENERATED variable.
> 
> # TSSTcorpCDDVDW_TS-H552U (pci-:00:0f.1-ide-0:0)
> ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="1.0", SYMLINK+="cdrom", 
> ENV{GENERATED}="1"
> ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="1.0", SYMLINK+="cdrw", 
> ENV{GENERATED}="1"
> ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="1.0", SYMLINK+="dvd", 
> ENV{GENERATED}="1"
> ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="1.0", SYMLINK+="dvdrw", 
> ENV{GENERATED}="1"
> # TSSTcorpCDDVDW_TS-H552U (pci-:00:06.0-ide-0:0)
> ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="0.0", SYMLINK+="cdrom", 
> ENV{GENERATED}="1"
> ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="0.0", SYMLINK+="cdrw", 
> ENV{GENERATED}="1"
> ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="0.0", SYMLINK+="dvd", 
> ENV{GENERATED}="1"
> ENV{ID_CDROM}=="?*", SUBSYSTEMS=="ide", KERNELS=="0.0", SYMLINK+="dvdrw", 
> ENV{GENERATED}="1"

These rules are lacking a device path (were they generated a long time
ago?) so we can't automatically update them.

I have now fixed the postinst script so it does not report files as
being automatically updated when it cannot find any new device IDs for
them.

[...]
> > We don't know how to parse mdadm.conf.  So this is really a warning that
> > it might need to be updated.  The wording could be improved to make this
> > clearer.
> 
> I think the 'still use' part is the wording problem. Maybe split it into
> two lists, like:

This wording is currently in translation, so I don't want to change it
now.  Instead, I have implemented a simple scan for the devices listed
in mdadm.conf so that the wording can be correct.

[...]
> Also, there should probably be a note about needing to re-run
> update-initramfs after modifying e.g., mdadm.conf.

I assume that the advanced users who use mdadm already know they need to
do that after editing mdadm.conf.  Similarly, I assume that they know to
run lilo after editing lilo.conf.  Remember also that this message has
to apply to all of the many configuration files that might need to be
changed.

Ben.

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


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

Re: Bug #542629: RM: yaird -- ROKM; old, buggy and unmaintained

[maximilian attems]

[ adding relevant cc's and dropping others ]

thanks torsten for the note.

On Sat, Apr 10, 2010 at 09:43:16PM +0200, Torsten Werner wrote:
> 
> just a note: dracut has been mentioned in this bug report. I've just
> accepted its first upload.

saw it in NEW, it would have been nice if debian-kernel@lists.debian.org
would have been informed at least!

Philippe what are your dracut plans?


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100410215650.gb32...@baikonur.stro.at

Bug#509923: linux-2.6: hd's no longer found on marvell 88SE6145 sata controller

[Dan Alderman]

I replied to Ben without hitting reply-all, so sending this again,
sorry, Ben, you now have this info twice.

I haven't found a work around that lets me access the disks on the
controller, I've just found a method to get Lenny installed onto the
system, i.e. don't hook up any disks to the Marvell controller and just
use the on board Intel controller for the install (945GC + ICH7).

Blacklisting pata_marvell, remaking the initramfs and forcing the ahci
driver on the kernel boot as per the instructions on the Debian wiki
line resulted in similar timeout errors and no drives detected on the
Marvell.

http://wiki.debian.org/pata_marvell

Could this be related to the fact that the Jetway daughterboard using
the Marvell 6145 only has the SATA ports setup with no PATA ports?

The Atom 330 board I'm using is this:

http://www.jetwaycomputer.com/NC92.html

and the Marvell Daughter Board is the ADPE4S on this page

http://www.jetwaycomputer.com/Daughter_Board.html

I'll regenerate the errors from both methods I tried once I return home
on Monday and attach them to the bug report.

Cheers,

D.





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1270935802.15351.40.ca...@nano.danalderman.co.uk

Bug#576918: linux-image-2.6-686: Keyboard disabled: atkbd.c: Spurious ACK on isa0060/serio0 ...

[Ben Hutchings]

On Thu, 2010-04-08 at 09:16 +0100, ael wrote:
> Package: linux-image-2.6-686
> Version: 2.6.32+25
> Severity: important
> 
> With Linux 2.6.32-trunk-686 & Linux 2.6.32-3-686, at least, on this Aspire One
> Netbook, the system frequently boots into a state in which the keyboard does
> not respond. The mouse (Synaptics touchpad) is still active, and as far as I 
> can
> tell everything else is working. My only recourse is to hit the reset button.
> 
> So this is nondeterministic, and so probably some sort of race? I *think* 
> that 
> it happens more frequently if I happen to touch the ps/2 touchpad during 
> boot, but
> it definitely does still happen when I keep my hands well away during boot.
> 
> Looking at /var/log/messages, this seem to be correlated with the
> following message:
> Apr  6 09:58:56 elf kernel: [4.789882]
>atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying 
> access
> hardware directly.
> 
> So far as I can tell, this sort of message only appears when the kb is 
> disabled.
> Presumably, this interrupt is not really spurious, thus not serviced
> and the kb controller waits forever for the keystoke to be handled?? Just 
> guessing :-(
[...]

Please report this upstream at  under
product 'Drivers', component 'Input Devices'.  Let us know the bug
number so we can track it.

Ben.

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


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

Processed: tagging 576918

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 576918 moreinfo
Bug #576918 [linux-image-2.6-686] linux-image-2.6-686: Keyboard disabled: 
atkbd.c: Spurious ACK on isa0060/serio0 ...
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
Archive: 
http://lists.debian.org/handler.s.c.127093773732648.transcr...@bugs.debian.org

Bug#577260: linux-image-2.6.32-4-686: 2 GHz core 2 duo (E4400) reported as (or used at?) 1000 MHz

[Ben Hutchings]

On Sat, 2010-04-10 at 23:50 +0200, Bernhard Kuemel wrote:
> Package: linux-2.6
> Version: 2.6.32-11
> Severity: normal
> 
> 
> I use a intel core 2 duo E4400 CPU at stock 2 GHz. /proc/cpuinfo 
> claims its frequency is 1000 MHz. cpufreq-info says its hardware 
> limit is 1000 MHz. During boot the kernel says:
> [0.00] Detected 1999.951 MHz processor.
> [0.076234] CPU0: Intel(R) Core(TM)2 Duo CPU E4400  @ 2.00GHz stepping 
> 0d
> [0.164090] CPU1: Intel(R) Core(TM)2 Duo CPU E4400  @ 2.00GHz stepping 
> 0d
> 
> I'm not sure wether my CPU is running at 1 or 2 GHz.
> 
> This all happens while I run s...@home on both cores so the ondemand 
> governor, speedstep or whatever should switch to maximum frequency. 
> Indeed, ondemand switches to what it thinks is the maximum frequency.
> Using the performance governor didn't help.
[...]
> - cpufreq-info ---
> bernh...@be:/data/home/bernhard$ cpufreq-info
> cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
> Report errors and bugs to cpuf...@vger.kernel.org, please.
> analyzing CPU 0:
>   driver: acpi-cpufreq
>   CPUs which run at the same hardware frequency: 0
>   CPUs which need to have their frequency coordinated by software: 0
>   maximum transition latency: 160 us.
>   hardware limits: 600 MHz - 1000 MHz
>   available frequency steps: 1000 MHz, 800 MHz, 600 MHz
[...]

Note that the driver is acpi-cpufreq - this means it is dependent on the
BIOS.  Please check whether there is a BIOS update available for this
system.

Ben.

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


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

Processed: tagging 577260

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 577260 moreinfo
Bug #577260 [linux-2.6] linux-image-2.6.32-4-686: 2 GHz core 2 duo (E4400) 
reported as (or used at?) 1000 MHz
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
Archive: 
http://lists.debian.org/handler.s.c.12709383885342.transcr...@bugs.debian.org

Re: 5.0.4-i386 freezes at boot

[Ben Hutchings]

On Thu, 2010-04-08 at 09:21 +0300, Sakari Aaltonen wrote:
> I'm trying to install Debian 5.0.4-i386 on a Fujitsu Esprimo P1500  
> desktop computer with the netinst disk. However, the install stops  
> almost immediately with the message
> 
>MP-BIOS bug: 8254 timer not connected to IO-APIC
>Kernel panic - not syncing: IO-APIC + timer doesn't work!
>Boot with apic=debug and send a report. Then try booting with  
> the 'noapic' option
> 
> When I try 'apic=debug', the result is the same. There is no further output.
> 
> When I try 'noapic', the install seemingly succeeds, but when I try to  
> boot from the hard disk, the machine freezes during the start-up  
> sequence and I end up with a blank (black) screen.
> 
> The machine's BIOS is the most recent version available (October 2009.)

Please try to install the 'testing' suite (work in progress for Debian
6.0 'squeeze') using the installer from
.  This will install a
newer kernel version (2.6.32) which might include a fix for this bug.
Even if you are sure you want to use Debian 5.0 'lenny', this will at
least tell us whether a bug fix exists.

Ben.

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


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

Bug#531785: tcp-wrappers support not working

[Ben Hutchings]

On Thu, 2010-04-08 at 03:37 +0200, Marco d'Itri wrote:
> On Apr 05, Ben Hutchings  wrote:
> 
> > > echo "mountd statd portmap lockd: ALL" >> /etc/hosts.deny
> > > # the second line is acually not needed, but shows that the problem is
> > > # not a wrong service name
> > > echo "32767: ALL" >> /etc/hosts.deny
> > > 
> > > telnet servername 32767
> 
> > Port number 32767 is meaningless since SunRPC ports are dynamically
> > assigned.  You'll need to look at 'rpcinfo -p' to see which service is
> > on which port, then specify which *service* is not being wrapped.
> I am aware of this, as explained above.
> 
> > So far as I can see, rpc.mountd is using libwrap0 while the NFS server
> > is not because, er, it's in the kernel.  What do you expect?
> This is not about the NFS server but mountd, which I configured to use
> port 32767 with the -p command line option. strace shows no attempt to
> access /etc/hosts.*.

Did you try to mount from the same host?  Local addresses (i.e.
addresses bound to an interface) are specifically excluded from
checking.  Also note that mountd caches host decisions so long as the
hosts.{allow,deny} files are unchanged.

> BTW, I think it would also be useful to be able to bind the kernel lockd
> to localhost since NFSv4 does not require remote access to it.

Then report a wishlist bug for that.

Ben.

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


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

Bug#575924: linux-image-2.6.32-4-amd64: fuse module oops on boot

[Ben Hutchings]

On Wed, 2010-04-07 at 14:38 -0400, Denis Laxalde wrote:
> On Wed, 07 Apr 2010 18:18:16 +0100, Ben Hutchings wrote:
> > On Wed, 2010-04-07 at 11:45 -0400, Denis Laxalde wrote:
[...]
> > > I also noticed an constant error related to radeon very early in the
> > > boot. AFAICT, nothing is recorded in any log. Is there any way to
> > > find more info about this ?
> > 
> > First you'll have to tell use what the message is.  Normally kernel
> > messages are saved to /var/log/dmesg (boot messages only) and
> > /var/log/messages (continually).
> > 
> 
> This error was about a missing firmware (5.484487 in the previous
> dmesg). Installing firware-linux-nonfree solved this issue.
> 
> If boot failures occur again, I will give your previous advices a try
> and follow up.

That firmware is only used for 3D acceleration, and everything else will
work without it.  The more serious error messages suggest memory
corruption.  Have you tested the RAM with memtest86+ yet?

Ben.

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


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

Bug#572201: forcedeth driver hangs under heavy load

[Ben Hutchings]

Stephen Mulcahy reported a regression in forcedeth at
.  The system information and some
diagnostic information can be found there.  Anyone able to help?

Ben.

stephen mulcahy wrote:
> When running linux-image-2.6.32-trunk-amd64, the network stops 
> responding if large amounts of traffic are transmitted/received. Running 
> ifdown eth0 followed by ifup eth0 restores operation of the network. 
> There are no errors relating to this failure logged in /var/log that I 
> could see.
> 
> Downgrading to linux-image-2.6.30-2-amd64 results in a stable network. 
> Not sure if this is a forcedeth specific problem or a general problem in 
> the newer kernel (I have seen problems with forcedeth on other 
> distro/kernel combinations).
> 
> Happy to run further diagnostics to tie this down if you let me know 
> what to run.

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


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

Processed: bug 572201 is forwarded to net...@vger.kernel.org

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 572201 net...@vger.kernel.org
Bug #572201 [linux-2.6] linux-image-2.6.32-trunk-amd64: forcedeth driver hangs 
under heavy load
Set Bug forwarded-to-address to 'net...@vger.kernel.org'.
> 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
Archive: 
http://lists.debian.org/handler.s.c.12709427575527.transcr...@bugs.debian.org

Processed: tagging 576608

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 576608 + pending
Bug #576608 [linux-base] linux-base: "Invalid output format udev" during 
configuration
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
Archive: 
http://lists.debian.org/handler.s.c.127094703231188.transcr...@bugs.debian.org

Bug#572024: linux-image-2.6.32-trunk-amd64: During boot, Kernel 2.6.32 prints trace to screen then hangs

[Ben Hutchings]

Version: 2.6.32-10

On Mon, 2010-03-01 at 14:29 +1100, Gerry Butler wrote:
> Package: linux-2.6
> Version: 2.6.32-5
> Severity: important
> 
> Early in the boot process, kernel writes a trace to the screen then freezes. 
> 
> The problem is intermittent. About one boot attempt in 5 succeeds. 
> 
> Waiting a several minutes does not unfreeze the boot.
[...]

I believe this was fixed in Linux 2.6.32.10 by the following change:

commit 3048a0dbd810980f67882a8b6745d4a6ff24c53e
Author: Tejun Heo 
Date:   Fri Feb 5 17:57:02 2010 +0900

driver-core: fix race condition in get_device_parent()
 
This was included in Debian kernel package version 2.6.32-10.  Let us
know if this doesn't fix the problem for you.

Ben.

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


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

Processed: closing 572024

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # like I meant to with the last message
> close 572024 2.6.32-10
Bug#572024: linux-image-2.6.32-trunk-amd64: During boot, Kernel 2.6.32 prints 
trace to screen then hangs
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.6.32-10, send any further explanations to 
Gerry Butler 

> 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
Archive: 
http://lists.debian.org/handler.s.c.127095356832402.transcr...@bugs.debian.org

Bug#575924: linux-image-2.6.32-4-amd64: fuse module oops on boot

[Denis Laxalde]

Hi,

On Sun, 11 Apr 2010 00:28:24 +0100, Ben Hutchings wrote:
> The more serious error messages suggest memory  corruption.  Have you 
> tested the RAM with memtest86+ yet?

Yes, I've just run a pretty long test with memtest86+ and there was no
error reported.

Denis




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100410230536.485ef...@schloss

Processed: tagging 577253

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 577253 pending
Bug #577253 [initramfs-tools] initramfs-tools: Keyboard is not active / 
detected anymore, so LVM boot passphrase entry is broken
Added tag(s) pending.
> 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
Archive: 
http://lists.debian.org/handler.s.c.127096199228010.transcr...@bugs.debian.org

Bug#577253: initramfs-tools: Keyboard is not active / detected anymore, so LVM boot passphrase entry is broken

[maximilian attems]

On Sat, 10 Apr 2010, Colin Darie wrote:

> Package: initramfs-tools
> Version: 0.94.4
> Severity: normal
> Tags: sid
> 
> The generated initrd image after an upgrade to initramfs-tools 0.94.4 (from
> 0.93.x) renders my keyboard inactive in the LVM passphrase prompt (nothing
> happens when I enter my passphrase, so I guess the keyboard is not detected
> anymore). Of course, using the previous initrd image works perfectly well.  
> I'm
> runnning on a MacBook Pro so I guess it's not really a common case. How can I
> provide more informations ?  Thanks.  --- Colin Darie

as quick workaround do:

echo hid-apple >> /etc/initramfs-tools/modules
update-initramfs -u

sorry 0.93 included too many useless hid variants,
will readd hid-apple in next upload, fixed in git repo:
http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary

thanks for report.
 
-- 
maks



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100411045905.gg4...@stro.at