On Wed, 2010-12-29 at 17:12 +0100, Andrea Spadaccini wrote:
> Package: linux-2.6
> Version: 2.6.32-29
> Severity: critical
> 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.

> The system randomly (say, 2 times every 3 boots) shows General Protection 
> Fault
> errors at boot time. I don't get to multiuser init levels.
[...]
> I found in /var/log/syslog.0 a similar trace, but I 
> don't know if it's the same problem. Here it is:
> 
> Dec 28 11:33:38 beriserv kernel: [   20.816204] ------------[ cut here 
> ]------------
> Dec 28 11:33:38 beriserv kernel: [   20.817009] kernel BUG at 
> /build/buildd-linux-2.6_2.6.32-28-amd64-EUJiNq/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969!
> Dec 28 11:33:38 beriserv kernel: [   20.817895] invalid opcode: 0000 [#1] SMP 
> Dec 28 11:33:38 beriserv kernel: [   20.818786] last sysfs file: 
> /sys/module/processor/initstate
> Dec 28 11:33:38 beriserv kernel: [   20.819697] CPU 0 
> Dec 28 11:33:38 beriserv kernel: [   20.820173] Modules linked in: 
> acpi_cpufreq cpufreq_conservative cpufreq_powersave cpufreq_userspace 
> cpufreq_stats fuse loop firewire_sbp2 snd_hda_codec_analog snd_hda_intel 
> snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm arc4 snd_seq_midi 
> snd_rawmidi snd_seq_midi_event snd_seq ecb snd_timer radeon snd_seq_device 
> rtl8187 ttm drm_kms_helper mac80211 led_class cfg80211 drm i2c_algo_bit snd 
> rfkill i2c_i801 soundcore eeprom_93cx6 i2c_core button snd_page_alloc evdev 
> pcspkr asus_atk0110 processor serio_raw ext3 jbd mbcache usbhid hid sg sd_mod 
> crc_t10dif sr_mod cdrom ata_generic pata_jmicron uhci_hcd ahci ata_piix 
> ehci_hcd thermal firewire_ohci firewire_core crc_itu_t sky2 floppy libata 
> scsi_mod thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan]
> Dec 28 11:33:38 beriserv kernel: [   20.820173] Pid: 9, comm: events/0 Not 
> tainted 2.6.32-5-amd64 #1 P5K-E
> Dec 28 11:33:38 beriserv kernel: [   20.820173] RIP: 
> 0010:[<ffffffff810e6e5f>]  [<ffffffff810e6e5f>] kfree+0x55/0xcb
> Dec 28 11:33:38 beriserv kernel: [   20.820173] RSP: 0018:ffff88007fb9bd00  
> EFLAGS: 00010246
> Dec 28 11:33:38 beriserv kernel: [   20.820173] RAX: 0000000000000000 RBX: 
> 0000000000000001 RCX: ffffffff8118fda5
> Dec 28 11:33:38 beriserv kernel: [   20.820173] RDX: 0000000000000001 RSI: 
> ffff880001811d10 RDI: ffffea0000000000
> Dec 28 11:33:38 beriserv kernel: [   20.820173] RBP: ffff880000000000 R08: 
> ffff88007fb9a000 R09: ffffffff81452c20
> Dec 28 11:33:38 beriserv kernel: [   20.820173] R10: ffff880001812ba0 R11: 
> dead000000200200 R12: ffffffffa000f6b8
> Dec 28 11:33:38 beriserv kernel: [   20.820173] R13: 0000000000000001 R14: 
> ffff88007ca3f7c0 R15: 000000000000ff91
> Dec 28 11:33:38 beriserv kernel: [   20.820173] FS:  0000000000000000(0000) 
> GS:ffff880001800000(0000) knlGS:0000000000000000
> Dec 28 11:33:38 beriserv kernel: [   20.820173] CS:  0010 DS: 0018 ES: 0018 
> CR0: 000000008005003b
> Dec 28 11:33:38 beriserv kernel: [   20.820173] CR2: 00007f873667f000 CR3: 
> 00000000379d8000 CR4: 00000000000006f0
> Dec 28 11:33:38 beriserv kernel: [   20.820173] DR0: 0000000000000000 DR1: 
> 0000000000000000 DR2: 0000000000000000
> Dec 28 11:33:38 beriserv kernel: [   20.820173] DR3: 0000000000000000 DR6: 
> 00000000ffff0ff0 DR7: 0000000000000400
> Dec 28 11:33:38 beriserv kernel: [   20.820173] Process events/0 (pid: 9, 
> threadinfo ffff88007fb9a000, task ffff88007fba0000)
> Dec 28 11:33:38 beriserv kernel: [   20.820173] Stack:
> Dec 28 11:33:38 beriserv kernel: [   20.820173]  0000000000000001 
> ffff880000000000 0000000000000008 ffffffffa000f6b8
> Dec 28 11:33:38 beriserv kernel: [   20.820173] <0> 0000000000000001 
> 8000028005810000 ffff88007c8ca000 ffffffff8104800d
> Dec 28 11:33:38 beriserv kernel: [   20.820173] <0> 0000000100015780 
> ffff88007ca3f1a0 ffff880001818180 000000000000ff91
> Dec 28 11:33:38 beriserv kernel: [   20.820173] Call Trace:
> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [<ffffffffa000f6b8>] ? 
> usb_control_msg+0x124/0x135 [usbcore]
> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [<ffffffff8104800d>] ? 
> finish_task_switch+0x3a/0xaf
> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [<ffffffffa031bd2e>] ? 
> rtl818x_ioread8+0x61/0x7e [rtl8187]
> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [<ffffffffa031bd6f>] ? 
> rtl8187_is_radio_enabled+0x24/0xc0 [rtl8187]
> Dec 28 11:33:38 beriserv kernel: [   20.820173]  [<ffffffffa031be30>] ? 
> 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.

Ben.

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

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

Reply via email to