badness initialising ps3disk on cell

Bug #145451 reported by Colin Watson on 2007-09-27
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

On a non-PS3 Cell box (where I probably shouldn't have tried to load ps3disk, but it was early morning and I was forgetful), loading ps3disk from the initramfs produces:

[ 28.377882] ------------[ cut here ]------------
[ 28.381745] Badness at /org/gutsy-powerpc/ubuntu-2.6/debian/build/custom-source-cell/lib/kref.c:33
[ 28.391062] ------------[ cut here ]------------
[ 28.395522] Badness at /org/gutsy-powerpc/ubuntu-2.6/debian/build/custom-source-cell/lib/kref.c:33
[ 28.404797] Unable to handle kernel paging request for data at address 0x00000000
[ 28.412211] Faulting instruction address: 0xc0000000001d5278
[ 28.417959] Oops: Kernel access of bad area, sig: 11 [#1]
[ 28.423427] SMP NR_CPUS=32 NUMA Cell
[ 28.427048] Modules linked in: ps3disk ps3stor_lib
[ 28.431907] NIP: c0000000001d5278 LR: c0000000001d53d8 CTR: 0000000000000000
[ 28.439062] REGS: c000000001d93680 TRAP: 0300 Not tainted (2.6.22-12-cell)
[ 28.446302] MSR: 9000000000009032 <EE,ME,IR,DR> CR: 22024482 XER: 00000000
[ 28.453456] DAR: 0000000000000000, DSISR: 0000000042000000
[ 28.459021] TASK = c00000002fce56e0[1083] 'modprobe' THREAD: c000000001d90000 CPU: 1
[ 28.466703] GPR00: c0000000001d53d8 c000000001d93900 c00000000060cdb0 c0000000005693a0
[ 28.474829] GPR04: 0000000000000000 c0000000004a3ef8 c000000001d93a70 fffffffffffffffe
[ 28.482954] GPR08: 0000000000000073 c000000000569388 0000000000000000 d000000000011488
[ 28.491080] GPR12: 0000000000000001 c00000000055de80 d00000000001cab8 aaaaaaaaaaaaaaab
[ 28.499205] GPR16: d00000000001caf8 0000000000000000 000000000000006c 000000000000006c
[ 28.507330] GPR20: d0000000000103f8 0000000000000000 000000000000001c d00000000001c35c
[ 28.515456] GPR24: d000000000019000 d00000000001c438 c0000000005693a0 fffffffffffffffe
[ 28.523581] GPR28: d000000000011458 d000000000011468 c000000000597c00 0000000000000000
[ 28.531884] NIP [c0000000001d5278] .kobject_shadow_add+0x98/0x230
[ 28.538066] LR [c0000000001d53d8] .kobject_shadow_add+0x1f8/0x230
[ 28.544248] Call Trace:
[ 28.546723] [c000000001d93900] [c0000000001d53d8] .kobject_shadow_add+0x1f8/0x230 (unreliable)
[ 28.555466] [c000000001d939a0] [c0000000001d55cc] .kobject_register+0x2c/0x90
[ 28.562708] [c000000001d93a30] [c0000000002efa20] .bus_add_driver+0xb0/0x250
[ 28.569862] [c000000001d93ad0] [c0000000002f0f94] .driver_register+0x64/0xc0
[ 28.577016] [c000000001d93b50] [c000000000073cb0] .ps3_system_bus_driver_register+0x50/0xa0
[ 28.585495] [c000000001d93bf0] [d00000000000ec5c] .ps3disk_init+0x6c/0x9b8 [ps3disk]
[ 28.593355] [c000000001d93c80] [c0000000000b3fdc] .sys_init_module+0x20c/0x1960
[ 28.600774] [c000000001d93e30] [c0000000000086b4] syscall_exit+0x0/0x40
[ 28.607485] Instruction dump:
[ 28.610489] 419e0058 38630018 48205001 60000000 2fba0000 419e0170 e93d0038 397d0020
[ 28.618349] 39290008 e9490008 f93d0020 f9690008 <f96a0000> f94b0008 880d01dc e93d0038
Segmentation fault

Changed in linux-source-2.6.22:
importance: Undecided → Medium
status: New → Triaged
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Jim Lieb (lieb) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an isThis bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers