Bug 9529

Summary: General protection fault in thread_return, called by hrtimer code
Product: Other Reporter: Tim Kosse (tim.kosse)
Component: OtherAssignee: Jiri Kosina (jikos)
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.24-rc3 Subsystem:
Regression: --- Bisected commit-id:
Attachments: My kernel config

Description Tim Kosse 2007-12-08 08:10:34 UTC
I'm running kernel 2.6.24-rc3 patched only with unionfs-2.1.10.

While trying to stop apcupsd on my system, the task froze. The kernel log contained the following message:

general protection fault: 0000 [1] PREEMPT
CPU 0
Modules linked in: ipv6 pcspkr iptable_filter ip_tables x_tables i2c_viapro i2c_core via_agp dm_mirror scsi_wait_scan sl811_hcd usbhid ohci_hcd uhci_hcd usb_storage ehci_hcd usbcore
Pid: 5659, comm: apcupsd Not tainted 2.6.24-rc3 #1
RIP: 0010:[<ffffffff8805c70a>]  [<ffffffff8805c70a>] :usbhid:hiddev_ioctl+0x2f/0xa9b
RSP: 0018:ffff81001eb2be08  EFLAGS: 00010292
RAX: 22f3e9bffc9755f7 RBX: 00000000400c4807 RCX: 00007fff5153e8e0
RDX: ffff81001ce34cc0 RSI: ffff810002834000 RDI: ffff81001dcda6e8
RBP: ffff810019536000 R08: ffffffff8805e260 R09: 0000000000000016
R10: 0000000000000000 R11: ffffffff803864c2 R12: 00000000400c4807
R13: 00007fff5153e8e0 R14: 00000000400c4807 R15: 0000000000000000
FS:  00002ac659ce1b00(0000) GS:ffffffff8062d000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffff5622e08 CR3: 000000001e1a9000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process apcupsd (pid: 5659, threadinfo ffff81001eb2a000, task ffff81001eabf5c0)
Stack:  0000000000000000 ffff810019548900 ffff81001eb2be78 ffffffff804eaf7d
 ffff81001eabf5c0 ffff81001dd2e000 0000000000000296 ffffffff80246513
 0000000000000803 ffff81001eb2beb8 0000000000000001 ffff81001eb2beb8
Call Trace:
 [<ffffffff804eaf7d>] thread_return+0x4e/0x215
 [<ffffffff80246513>] hrtimer_try_to_cancel+0x3f/0x8e
 [<ffffffff80246572>] hrtimer_cancel+0x10/0x16
 [<ffffffff804ec123>] do_nanosleep+0x64/0x7c
 [<ffffffff80246bc4>] hrtimer_nanosleep+0x7c/0x118
 [<ffffffff8022b4cb>] default_wake_function+0x0/0xe
 [<ffffffff802946c2>] do_ioctl+0x62/0x83
 [<ffffffff80294740>] vfs_ioctl+0x5d/0x298
 [<ffffffff80287b2a>] vfs_read+0x123/0x160
 [<ffffffff802949e6>] sys_ioctl+0x6b/0x85
 [<ffffffff8020bf6e>] system_call+0x7e/0x83


Code: 48 8b 88 c8 00 00 00 48 8b bd d0 19 00 00 b8 fb ff ff ff 44
RIP  [<ffffffff8805c70a>] :usbhid:hiddev_ioctl+0x2f/0xa9b
 RSP <ffff81001eb2be08>

This bug might be related to bug 9216 which I have previously reported (which is either fixed or hasn't since been triggered on my system).
Comment 1 Tim Kosse 2007-12-08 08:12:39 UTC
Created attachment 13916 [details]
My kernel config
Comment 2 Anonymous Emailer 2007-12-08 10:15:10 UTC
Reply-To: akpm@linux-foundation.org

On Sat,  8 Dec 2007 08:10:36 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=9529
> 
>            Summary: General protection fault in thread_return, called by
>                     hrtimer code
>            Product: Other
>            Version: 2.5
>      KernelVersion: 2.6.24-rc3
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: other_other@kernel-bugs.osdl.org
>         ReportedBy: tim.kosse@gmx.de
> 
> 
> I'm running kernel 2.6.24-rc3 patched only with unionfs-2.1.10.
> 
> While trying to stop apcupsd on my system, the task froze. The kernel log
> contained the following message:
> 
> general protection fault: 0000 [1] PREEMPT
> CPU 0
> Modules linked in: ipv6 pcspkr iptable_filter ip_tables x_tables i2c_viapro
> i2c_core via_agp dm_mirror scsi_wait_scan sl811_hcd usbhid ohci_hcd uhci_hcd
> usb_storage ehci_hcd usbcore
> Pid: 5659, comm: apcupsd Not tainted 2.6.24-rc3 #1
> RIP: 0010:[<ffffffff8805c70a>]  [<ffffffff8805c70a>]
> :usbhid:hiddev_ioctl+0x2f/0xa9b
> RSP: 0018:ffff81001eb2be08  EFLAGS: 00010292
> RAX: 22f3e9bffc9755f7 RBX: 00000000400c4807 RCX: 00007fff5153e8e0
> RDX: ffff81001ce34cc0 RSI: ffff810002834000 RDI: ffff81001dcda6e8
> RBP: ffff810019536000 R08: ffffffff8805e260 R09: 0000000000000016
> R10: 0000000000000000 R11: ffffffff803864c2 R12: 00000000400c4807
> R13: 00007fff5153e8e0 R14: 00000000400c4807 R15: 0000000000000000
> FS:  00002ac659ce1b00(0000) GS:ffffffff8062d000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffff5622e08 CR3: 000000001e1a9000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process apcupsd (pid: 5659, threadinfo ffff81001eb2a000, task
> ffff81001eabf5c0)
> Stack:  0000000000000000 ffff810019548900 ffff81001eb2be78 ffffffff804eaf7d
>  ffff81001eabf5c0 ffff81001dd2e000 0000000000000296 ffffffff80246513
>  0000000000000803 ffff81001eb2beb8 0000000000000001 ffff81001eb2beb8
> Call Trace:
>  [<ffffffff804eaf7d>] thread_return+0x4e/0x215
>  [<ffffffff80246513>] hrtimer_try_to_cancel+0x3f/0x8e
>  [<ffffffff80246572>] hrtimer_cancel+0x10/0x16
>  [<ffffffff804ec123>] do_nanosleep+0x64/0x7c
>  [<ffffffff80246bc4>] hrtimer_nanosleep+0x7c/0x118
>  [<ffffffff8022b4cb>] default_wake_function+0x0/0xe
>  [<ffffffff802946c2>] do_ioctl+0x62/0x83
>  [<ffffffff80294740>] vfs_ioctl+0x5d/0x298
>  [<ffffffff80287b2a>] vfs_read+0x123/0x160
>  [<ffffffff802949e6>] sys_ioctl+0x6b/0x85
>  [<ffffffff8020bf6e>] system_call+0x7e/0x83
> 
> 
> Code: 48 8b 88 c8 00 00 00 48 8b bd d0 19 00 00 b8 fb ff ff ff 44
> RIP  [<ffffffff8805c70a>] :usbhid:hiddev_ioctl+0x2f/0xa9b
>  RSP <ffff81001eb2be08>
> 
> This bug might be related to bug 9216 which I have previously reported (which
> is either fixed or hasn't since been triggered on my system).
> 

The hrtimer stuff is just noise on the stack.  This crash is the same one
as you described in the (apparently incorrectly closed) 9216.  
Comment 3 Jiri Kosina 2007-12-11 15:23:59 UTC
I agree. Let's reopen 9216.

*** This bug has been marked as a duplicate of bug 9216 ***