[asterisk-bugs] [JIRA] (DAHLIN-314) wcb4xxp: kernel oopses when debug st state is enabled
Russ Meyerriecks (JIRA)
noreply at issues.asterisk.org
Fri Jan 25 17:01:58 CST 2013
[ https://issues.asterisk.org/jira/browse/DAHLIN-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202244#comment-202244 ]
Russ Meyerriecks commented on DAHLIN-314:
-----------------------------------------
This is fixed in current master, 2.6.y, and in release 2.6.2-rc1:
http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commit;h=85e6cdde83c3edc2d2efd3dd29dfd9de1536a838
You can download a tarball of the release here: http://downloads.asterisk.org/pub/telephony/dahdi-linux/dahdi-linux-2.6.2-rc1.tar.gz
Or you can check out the v2.6.2-rc1 tag from git:
git clone git.asterisk.org/dahdi/linux dahdi-linux
cd dahdi-liux
git checkout v2.6.2-rc1
> wcb4xxp: kernel oopses when debug st state is enabled
> -----------------------------------------------------
>
> Key: DAHLIN-314
> URL: https://issues.asterisk.org/jira/browse/DAHLIN-314
> Project: DAHDI-Linux
> Issue Type: Bug
> Security Level: None
> Components: wcb4xxp
> Affects Versions: 2.6.1
> Environment: CentOS 6.3, kernel 2.6.32-279.el6.x86_64, Digium B410P
> Reporter: Gerald Schnabel
> Assignee: Russ Meyerriecks
> Severity: Minor
> Attachments: messages.txt
>
>
> When wcb4xxp is loaded with debug st state bit set (e.g. module option debug=32) kernel oopses appear from time to time, see attached [^messages.txt].
> Changing the kmalloc() flag _GFP_KERNEL_ to _GFP_ATOMIC_ in function _hfc_decode_st_state()_ seems to make the oopses disappear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list