Bug#608278: linux-image-2.6.32-5-amd64: Random general protection faults at boot

2010-12-30 Thread Andrea Spadaccini

Hi,


Justification: breaks the whole system


This does *not* break the whole system - the package works for other
people and even you are able to reboot into another kernel version.


Sorry, I misinterpreted the options.

[cut]


Dec 28 11:33:38 beriserv kernel: [   20.820173]  [a000f6b8] ? 
usb_control_msg+0x124/0x135 [usbcore]
Dec 28 11:33:38 beriserv kernel: [   20.820173]  [8104800d] ? 
finish_task_switch+0x3a/0xaf
Dec 28 11:33:38 beriserv kernel: [   20.820173]  [a031bd2e] ? 
rtl818x_ioread8+0x61/0x7e [rtl8187]
Dec 28 11:33:38 beriserv kernel: [   20.820173]  [a031bd6f] ? 
rtl8187_is_radio_enabled+0x24/0xc0 [rtl8187]
Dec 28 11:33:38 beriserv kernel: [   20.820173]  [a031be30] ? 
rtl8187_rfkill_poll+0x25/0x78 [rtl8187]

[...]

This is presumably caused by a bug in rtl8187.  However, it is not a
general protection fault so there may be two different bugs here.


Yes, the GPF is around sec 30. After that bug, I blacklisted rtl8187, 
and resulted in the other GPFs at boot time that are not logged.


Andrea



--
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/4d1c4bf0.5010...@gmail.com



Bug#607709: XEN kernel crash (this time with a shorter trace)

2010-12-30 Thread Giuseppe Sacco
A new crash on that machine, after upgrading kernel, is shown here:

Dec 29 22:21:28 atf-124 kernel: [49041.588528] [ cut here 
]
Dec 29 22:21:28 atf-124 kernel: [49041.591269] kernel BUG at 
/build/buildd-linux-2.6_2.6.32-29-i386-Of6Yt1/linux-2.6-2.6
.32/debian/build/source_i386_xen/arch/x86/xen/enlighten.c:309!
Dec 29 22:21:28 atf-124 kernel: [49041.592505] invalid opcode:  [#1] SMP
Dec 29 22:21:28 atf-124 kernel: [49041.592505] last sysfs file: 
/sys/hypervisor/version/minor
Dec 29 22:21:28 atf-124 kernel: [49041.592505] Modules linked in: bridge stp 
xen_evtchn xenfs vboxnetadp vboxnetflt vboxdrv lp parport psmouse shpchp 
i5100_edac button edac_core pci_hotplug serio_raw evdev dcdbas processor 
acpi_processor ext3 jbd mbcache sd_mod crc_t10dif sg osst sr_mod dm_mod cdrom 
st usbhid hid ata_generic mptspi mptsas scsi_transport_spimptscsih ata_piix 
mptbase libata scsi_transport_sas tg3 scsi_mod ehci_hcd uhci_hcd libphy usbcore 
nls_base thermal thermal_sys radeonfb fb_ddc i2c_algo_bit i2c_core
Dec 29 22:21:28 atf-124 kernel: [49041.614238]
Dec 29 22:21:28 atf-124 kernel: [49041.614238] Pid: 17208, comm: 
python2.3 Not tainted (2.6.32-5-xen-686 #1) PowerEdge T300
Dec 29 22:21:28 atf-124 kernel: [49041.614238] EIP: 0061:[c1003b51] EFLAGS: 
00210282 CPU: 1
Dec 29 22:21:28 atf-124 kernel: [49041.614238] EIP is at 
set_aliased_prot+0x9e/0x10d
Dec 29 22:21:28 atf-124 kernel: [49041.614238] EAX: ffea EBX: f8c2b000 ECX: 
70567063 EDX: 8001
Dec 29 22:21:28 atf-124 kernel: [49041.614238] ESI:  EDI: 8000 EBP: 
00039e3b ESP: f5a3df08
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  DS: 007b ES: 007b FS: 00d8 GS: 
00e0 SS: 0069
Dec 29 22:21:28 atf-124 kernel: [49041.614238] Process python2.3 (pid: 17208, 
ti=f5a3c000 task=f492ea40 task.ti=f5a3c000)
Dec 29 22:21:28 atf-124 kernel: [49041.614238] Stack:
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  8001 70567063 0163 
f8c2b000 c2e56000 0001 0200 f8c2b000
Dec 29 22:21:28 atf-124 kernel: [49041.614238] 0 2000 f24978b4 c1003be2 
f2497880 f492ea40 f2497880 c100b2ab f2497880
Dec 29 22:21:28 atf-124 kernel: [49041.614238] 0 f2497880 c103564a  
c1038a8e f5aa98c0 c128e818 f5aa98c0 f492ea40
Dec 29 22:21:28 atf-124 kernel: [49041.614238] Call Trace:
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c1003be2] ? 
xen_free_ldt+0x22/0x30
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c100b2ab] ? 
destroy_context+0x38/0x79
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c103564a] ? 
__mmdrop+0x1d/0x3a
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c1038a8e] ? exit_mm+0xd5/0xdc
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c128e818] ? 
_spin_lock_irq+0xb/0x21
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c103a237] ? 
do_exit+0x1a3/0x5cd
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c1290598] ? 
do_page_fault+0x2f1/0x307
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c103a6c0] ? 
do_group_exit+0x5f/0x82
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c103a6f4] ? 
sys_exit_group+0x11/0x14
Dec 29 22:21:28 atf-124 kernel: [49041.614238]  [c1008ebb] ? 
sysenter_do_call+0x12/0x28
Dec 29 22:21:28 atf-124 kernel: [49041.614238] Code: ea 0c c1 e0 0c 09 d1 09 c3 
89 ca 89 d8 ff 15 8c fe 3c c1 31 f6 89 c1 8b 5c 24 0c 89 44 24 04 89 14 24 e8 
73 e6 ff ff 85 c0 74 04 0f 0b eb fe 8b 54 24 10 89 e8 c1 e0 05 8b 04 10 c1 e8 
1e  69 c0
Dec 29 22:21:28 atf-124 kernel: [49041.614238] EIP: [c1003b51] 
set_aliased_prot+0x9e/0x10d SS:ESP 0069:f5a3df08
Dec 29 22:21:28 atf-124 kernel: [49041.715932] ---[ end trace 0969558a522287f2 
]---
Dec 29 22:21:28 atf-124 kernel: [49041.716511] Fixing recursive fault but 
reboot is needed!

Bye,
Giuseppe




-- 
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/1293721321.4583.27.ca...@scarafaggio



Processed: Re: Bug#608343: installation-reports: nouveau makes display unusable (GeForce 5200 FX)

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

 reassign 608343 linux-2.6 2.6.32-29
Bug #608343 [xserver-xorg-video-nouveau] installation-reports: nouveau makes 
display unusable (GeForce 5200 FX)
Bug reassigned from package 'xserver-xorg-video-nouveau' to 'linux-2.6'.
Bug #608343 [linux-2.6] installation-reports: nouveau makes display unusable 
(GeForce 5200 FX)
There is no source info for the package 'linux-2.6' at version '2.6.32-29' with 
architecture ''
Unable to make a source version for version '2.6.32-29'
Bug Marked as found in versions 2.6.32-29.
 kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
608343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
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.12937217138443.transcr...@bugs.debian.org



Bug#608415: linux-image-2.6.37-rc7-686: CPU temperature sensor lost on EEE Pc

2010-12-30 Thread Mikolaj Menke
Package: linux-image-2.6.37-rc7-686
Severity: normal


The CPU temperature sensor on Asus 1015PED EEE PC is lost. There used to
be such sensor on 2.6.32 and 2.6.36.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
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/20101230174654.30610.42878.report...@menek.one.pl



Bug#608339: initramfs-tools: MODULES=dep fails when / is ubifs (reopen)

2010-12-30 Thread maximilian attems
On Thu, Dec 30, 2010 at 12:29:16AM +, Alexander Clouter wrote:
 Package: initramfs-tools
 Severity: normal
 
 Similar to #582858, however for me it still does not work.

hehe, I see.
 
 When I set MODULES=dep, root cannot be found as the root mountpoint
 device does not start with '^/dev/' (thanks to my symlinking /etc/mtab
 to /proc/mounts I also get two /'s also):
  output of 'mount' 
 rootfs on / type rootfs (rw)
 ubi0:rootfs on / type ubifs (rw,relatime)
 tmpfs on /lib/init/rw type tmpfs (rw,nosuid,relatime,mode=755)
 proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
 sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
 varrun on /var/run type tmpfs (rw,nosuid,relatime,mode=755)
 varlock on /var/lock type tmpfs (rw,nosuid,nodev,noexec,relatime)
 tmpfs on /dev type tmpfs (rw,relatime,size=10240k,mode=755)
 tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
 devpts on /dev/pts type devpts 
 (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
 tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,relatime,size=32768k)
 tmpfs on /var/tmp type tmpfs (rw,nosuid,nodev,noexec,relatime,size=8192k)
 /dev/sda1 on /root/moo type vfat 
 (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro)
  contents of /proc/mounts 
 rootfs / rootfs rw 0 0
 ubi0:rootfs / ubifs rw,relatime 0 0
 tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
 varrun /var/run tmpfs rw,nosuid,relatime,mode=755 0 0
 varlock /var/lock tmpfs rw,nosuid,nodev,noexec,relatime 0 0
 tmpfs /dev tmpfs rw,relatime,size=10240k,mode=755 0 0
 tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 
 0 0
 tmpfs /tmp tmpfs rw,nosuid,nodev,noexec,relatime,size=32768k 0 0
 tmpfs /var/tmp tmpfs rw,nosuid,nodev,noexec,relatime,size=8192k 0 0
 /dev/sda1 /root/moo vfat 
 rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro
  0 0
 

ok, thanks for the details.
 
 This is trivially resolved by amending the routines that search for the
 root block device and fstype in /usr/share/initramfs-tools/hook-functions
 to the following instead:
 
 # findout root block device + fstype
 eval $(mount | awk '!/^rootfs /  / on \/ type / {print root= $1 
 \nFSTYPE= $5; exit}')
 
 # On failure fallback to /proc/mounts if readable
 if [ -z $root ]  [ -r /proc/mounts ]; then
 eval $(awk '!/^rootfs /  / \/ / {print root= $1 \nFSTYPE= $3; 
 exit}' /proc/mounts)
 fi
 

first please if you do changes send them as diff, it is pretty
trivial these days and helps a lot for the review of a change:
git clone git://git.debian.org/kernel/initramfs-tools.git
and see short guide on how to add features or fixes
http://git.debian.org/?p=kernel/initramfs-tools.git;a=blob_plain;f=docs/maintainer-notes.html;hb=HEAD

now on the direct review, your code aboves may work for your testcase,
but will fail several others as it now subtily change a lot of things.

first off you could just keep the current way of parsing mount
and propose a change on the /proc/mount fallback. I see that the matching
prefix /dev poses a problem for ubifs, but please do not drop the matching
'/' on the explicit field.
 
 This filters out the useless '^rootfs' entry (enabling embedded folk to
 continue symlinking) and permits anything (not just '^/dev/...') as the
 root device.  Now the ubifs root filesystem detection functions.

so based on your proposal a diff would look like this:

diff --git a/hook-functions b/hook-functions
index cc8b344..6dfd54d 100644
--- a/hook-functions
+++ b/hook-functions
@@ -229,7 +229,7 @@ dep_add_modules()
 
# On failure fallback to /proc/mounts if readable
if [ -z $root ]  [ -r /proc/mounts ]; then
-   eval $(awk '/\/dev\// {if ($2 == /) {print root= $1 
\nFSTYPE= $5; exit}}' /proc/mounts)
+   eval $(awk '!/^rootfs / {if ($2 == /) {print root= $1 
\nFSTYPE= $3; exit}}' /proc/mounts)
fi
 
# recheck root device

 
 It should also be noted, the original 'failure fallback' does not work
 anyway as it incorrectly refers to $5 (over eager cutting and pasting it
 seems) when it should refer to $3 for FSTYPE.

well you may choose your words more wisely, as if you'd continue to read
the function you would see that we don't use this FSTYPE value, so this
doesn't matter (;
 

could you please test aboves patch on your box?
thank you 

-- 
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/2010123027.gq20...@vostochny.stro.at



Processed: severity of 608339 is important

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

 severity 608339 important
Bug #608339 [initramfs-tools] initramfs-tools: MODULES=dep fails when / is 
ubifs (reopen)
Severity set to 'important' from 'normal'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
608339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
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.129374618516336.transcr...@bugs.debian.org



Processed: tagging 608339

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

 tags 608339 + patch
Bug #608339 [initramfs-tools] initramfs-tools: MODULES=dep fails when / is 
ubifs (reopen)
Added tag(s) patch.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
608339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
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.129374618616351.transcr...@bugs.debian.org



How to compile experimental kernels?

2010-12-30 Thread Willy Gommel
I have run into a problem.

It seems that the newest (experimental) kernels will not respond to Make in 
the usual way, Invariably, I am told that ngcc is not found, How it comes up 
with ngcc is indeed part of my problem.

N.B.: The main reason I need the experimental version of the kernel is that the 
current testing version cannot be persuaded to run for me at all after I get 
done compiling it. Invariably I get told that the kernel has panicked.

Help!

-- 
Willy Gommel
www.wg3.net


-- 
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/201012301626.33940.w...@spamcop.net