Bug 8675 - mageia system crash during document scanning with SCSI Canon Canoscan 300 scanner
Summary: mageia system crash during document scanning with SCSI Canon Canoscan 300 sca...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-12 21:03 CET by Denis Prost
Modified: 2013-01-22 21:54 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Denis Prost 2013-01-12 21:03:36 CET 
I scanned five pages with simple-scan.
No problem with the first four, but during the fifth page scanning, system crashed. No more keyboard, mouse, and so on. I had to brutally poweroff with the poweroff button.

Below is the end of the syslog file after crash occured :

Jan  9 14:21:09 localhost kernel: [ 1345.260006] INFO: rcu_sched detected stall on CPU 0 (t=6000 jiffies)
Jan  9 14:21:09 localhost kernel: [ 1345.260007] Pid: 15510, comm: kworker/0:0 Tainted: G         C   3.3.6-server-2.mga2 #1
Jan  9 14:21:09 localhost kernel: [ 1345.260007] Call Trace:
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c04cab87>] ? printk+0x1d/0x1f
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c01bcd59>] __rcu_pending+0x189/0x370
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c0171ab8>] ? account_process_tick+0x58/0x200
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c01bd340>] rcu_check_callbacks+0xa0/0x160
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c01533bb>] update_process_times+0x3b/0x70
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c0194a7e>] tick_sched_timer+0x5e/0xc0
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c0166390>] ? __remove_hrtimer+0x40/0xa0
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c01668dc>] __run_hrtimer+0x6c/0x1b0
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c0194a20>] ? tick_nohz_handler+0x100/0x100
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c0167535>] hrtimer_interrupt+0xe5/0x260
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c012e024>] smp_apic_timer_interrupt+0x54/0x90
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c04d26e5>] apic_timer_interrupt+0x31/0x38
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c015007b>] ? ptrace_request+0x44b/0x690
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<f53254cb>] ? datai_run+0x6b/0x530 [aha152x_cs]
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c015c5ea>] ? queue_delayed_work_on+0xea/0x100
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c015c61b>] ? schedule_delayed_work_on+0x1b/0x20
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<f5322b79>] run+0x229/0x5e0 [aha152x_cs]
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c015dd1f>] process_one_work+0xff/0x3a0
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c015b940>] ? do_work_for_cpu+0x20/0x20
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<f5322950>] ? msgi_run+0x5f0/0x5f0 [aha152x_cs]
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c015e94a>] worker_thread+0x12a/0x2e0
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c015e820>] ? manage_workers.isra.26+0x1f0/0x1f0
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c01627f2>] kthread+0x72/0x80
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c0162780>] ? kthread_freezable_should_stop+0x60/0x60
Jan  9 14:21:09 localhost kernel: [ 1345.260007]  [<c04d923e>] kernel_thread_helper+0x6/0x10
Denis Prost 2013-01-12 21:03:54 CET

CC: (none) => denis.prost

Comment 1 Manuel Hiebel 2013-01-20 12:58:48 CET 
same with a more updated kernel like 3.3.8 or 3.4.24 ?
Comment 2 Denis Prost 2013-01-20 14:20:09 CET 
I just updated to 3.3.8.
I'll let you know if it happens again (since it's a random problem, I cannot immediately reproduce it).
Comment 3 Denis Prost 2013-01-22 21:54:48 CET 
I scanned twelve pages without problem. 
That does not make sure that the problem is resolved, but it is probable, so I close it and will reopen if it happens again.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.