[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#366358: marked as done (Oops on shutdown with 2.6.16)

Your message dated Wed, 31 Jan 2007 23:42:11 -0800
with message-id <20070201074211.GA5161@droopy.oc.cox.net>
and subject line still happening in 2.6.18
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-image-2.6.16-1-686
Version: 2.6.16-12
Severity: important


My laptop (Compaq Evo n160) started oopsing on shutdown with 2.6.16 (not every time, in approximately half of the cases) if PCMCIA wifi card is inserted. It works fine with 2.6.15. The trace is included below

Unable to handle kernel paging request at virtual address c0a8f3a4
 printing eip:
*pde = 0ff41067
*pte = 00000000
Oops: 0000 [#1]
Modules linked in: radeon drm loop ipt_REJECT xt_tcpudp iptable_filter ip_tables
 x_tables ipv6 firmware_class e100 yenta_socket rsrc_nonstatic pcmcia_core ohci1
394 ieee1394 aes dm_crypt dm_mod psmouse intel_agp agpgart usbhid uhci_hcd usbco
re eepro100 mii snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_o
ss snd_pcm snd_timer snd soundcore snd_page_alloc rtc ext3 jbd mbcache ide_disk
generic piix ide_core evdev mousedev
CPU:    0
EIP:    0060:[<b01fbaee>]    Not tainted VLI
EFLAGS: 00010282   (2.6.16-1-686 #2)
EIP is at device_shutdown+0x2e/0x7a
eax: bed26238   ebx: bed26c38   ecx: 00000016   edx: c0a8f280
esi: 28121969   edi: a7f4cff4   ebp: bf848000   esp: bf849ea0
ds: 007b   es: 007b   ss: 0068
Process halt (pid: 3388, threadinfo=bf848000 task=bfdd7ab0)
Stack: <0>4321fedc b011f46f 00000003 b011f7fe 00000046 00000000 00000046 bff51a90
       bff51a90 00000013 00000014 b011e5b3 bff51a90 00000000 00000000 bff51a90
       00000014 bf849f28 b011e61a 00000286 bff51a90 00000014 00000286 00000014
Call Trace:
 [<b011f46f>] kernel_power_off+0x7/0x18
 [<b011f7fe>] sys_reboot+0xec/0x148
 [<b011e5b3>] __group_complete_signal+0x1ec/0x1f3
 [<b011e61a>] __group_send_sig_info+0x60/0x6a
 [<b011f191>] sys_kill+0xd8/0xe7
 [<b014c34e>] block_ioctl+0x1a/0x1e
 [<b025e7e3>] schedule+0x454/0x4c1
 [<b01549f2>] vfs_ioctl+0x1f0/0x202
 [<b0102915>] syscall_call+0x7/0xb
Code: 54 2b b0 ba 01 00 ff ff 0f c1 10 85 d2 75 68 a1 0c 54 2b b0 2d 84 00 00 00
 8b 98 88 00 00 00 eb 34 8b 90 d4 00 00 00 85 d2 74 0a <8b> 92 24 01 00 00 85 d2
 75 14 8b 90 d8 00 00 00 85 d2 74 0e 8b

Best regards,

Jurij Smakov                                        jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC

--- End Message ---
--- Begin Message ---
Version: 2.6.18-1

> hey Jurij,
>  Is this still happening in 2.6.18?

I haven't seen it with 2.6.18, so I'll close the bug now.

Jurij Smakov                                           jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                      KeyID: C99E03CC

--- End Message ---

Reply to: