ck804xrom ck804xrom_init_one(): Unable to register resource ... kernel bug?

Bug #90863 reported by Niko_Thien
44
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Linux
Invalid
Medium
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

The new Kernel is not working for me. The graphical userinterface freezes after some seconds. The only way back is to restart the whole computer. You cannot even restart Gnome or do anything else by Keyboard.

But the -8 Kernel is working like a charme for me.

ProblemType: Bug
Architecture: i386
Date: Fri Mar 9 16:33:45 2007
DistroRelease: Ubuntu 7.04
Uname: Linux ubuntu 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/DebuggingKernelProblems . Thanks in advance!

Revision history for this message
Niko_Thien (terrorgurke) wrote :

Sry, I simply forgot to have a look in the wiki... But anyway here we go:

uname -a: Linux ubuntu 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

dmesg.log and lspci-vvnn.log are attached!

Hoping that you find something :)

Revision history for this message
Niko_Thien (terrorgurke) wrote :
Changed in linux-source-2.6.20:
assignee: brian-murray → nobody
importance: Undecided → Medium
status: Needs Info → Confirmed
Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Jeroen Maris (jealma) wrote :

I still have this bug in kernel 2.6.20-15-25. Still not solved?

Revision history for this message
Jeroen Maris (jealma) wrote :

And my lcpci -vvnn

Revision history for this message
Ulrik Mikaelsson (rawler) wrote :

I've got the same error in dmesg, but my system is just slow when accessing Parallell ATA, not crashing. SATA works fine, though.

| $ sudo hdparm -t /dev/hdc
|
| /dev/hdc:
| Timing buffered disk reads: 116 MB in 3.04 seconds = 38.17 MB/sec

Not too bad, BUT:

| $ dd if=a of=b
| 184457216 byte (184 MB) copied, 19,9216 seconds, 9,3 MB/s

Not sure if it's related, but Googling for the error message, this was the best match.

My solution will probably be throwing out my old PATA disk, but it might give someone else a clue.

I'm attaching my lshw, can Niko or Jeroen compare and see if there are any matches?

Revision history for this message
xul (tod-liebt-dich) wrote :

hi! i'm having the same message in my logs.
couldn't install xubuntu amd64 alternate cd from sata-cd, done net install. xubuntu is up, but cdrom can't be mounted.

system: dell poweredge t105
2 sata drives (wd)
1 sata cdrom
4 gb ram

/boot is on sda1 ext3
/ is on raid1 ext (md0)
swap is on other raid (md1)

dmesg has some warnings, see attachment.

Revision history for this message
xul (tod-liebt-dich) wrote :
Revision history for this message
xul (tod-liebt-dich) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

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!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Jamie Lawler (jamie-lawler) wrote :

I don't really know where to post this information - I'm not sure if I should file a new bug report or not. This is the first time I've contributed to Launchpad.

I get the exact bug described here with 2.6.27-2-generic.
I get this line in the kernel log:

Sep 6 06:15:04 hardy-alien kernel: [ 18.979933] ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?

Ever since I upgraded to alpha 5, I haven't been able to boot using the 2.6.27-2-generic kernel correctly. Instead of loading the gdm, I get a terminal log-in. This screen disappears after a few seconds, to be replaced with the box telling me my display and graphics card aren't detected. Even if I input my monitor model and choose the right driver, the gdm is still loaded up a few seconds later in VESA mode. The previous kernel worked perfectly on my machine.

Let me know if I can be of any more help.

Revision history for this message
Neil Wilson (neil-aldur) wrote :

I get the same error

ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?

This is on 2.6.27-5

Linux test1 2.6.27-5-server #1 SMP Fri Oct 3 01:16:59 UTC 2008 x86_64 GNU/Linux

Revision history for this message
Neil Wilson (neil-aldur) wrote :
Revision history for this message
Neil Wilson (neil-aldur) wrote :

I should note that this message doesn't appear to be affecting my servers operations in any way, but then I'm not using the graphics card.

Changed in linux:
status: Incomplete → Confirmed
Revision history for this message
ljohnson (ljohnson-achieveresearch) wrote :

I can confirm this issue is also occurring in the 2.6.27 kernel. I recently upgraded from 8.04 to 8.10 and started receiving this error. I have attached the requested output from /proc/cpuinfo, uname, dmesg and lspci

Revision history for this message
ljohnson (ljohnson-achieveresearch) wrote :

Here is the uname.log

Revision history for this message
ljohnson (ljohnson-achieveresearch) wrote :

Here is the version.log

Revision history for this message
ljohnson (ljohnson-achieveresearch) wrote :

Here is the lspci-vvnn.log. One other comment. Not sure if this issue is affecting my ability to load and used the NVidia graphic drivers, but that is occurring as well. I will be reporting the driver problem separately. Thanks for the support....

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

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.

Revision history for this message
gst (g-starck) wrote :

just have upgraded from hardy to intrepid and now I also have this message in kern.log :

greg@brutus:~$ dmesg | egrep ck804xrom
[ 20.596274] ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?
greg@brutus:~$

although I have only that as indication : no other (visible) sign of problem, all is working quite fine for my setup.

greg@brutus:~$ uname -a
Linux brutus 2.6.27-11-generic #1 SMP Fri Dec 19 16:29:52 UTC 2008 i686 GNU/Linux
greg@brutus:~$

Revision history for this message
yossarian_uk (morgancoxuk) wrote :

Same here

dmesg | grep -i ck8
[ 11.199826] ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?

uname -a
----------
morgan@morgan-desktop:~$ uname -a
Linux morgan-desktop 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux

Specs:-

Athlon64 AM2 4600 X2
2X2GB (6400)
nvidia geforce 8500

Have attached text file with lspci -vvnn + dmesg

Revision history for this message
yossarian_uk (morgancoxuk) wrote :

The last lscpi -vvnn was not done as root

Here it is as root (in case this helps)

Revision history for this message
David Tomaschik (matir) wrote :

This bug is occuring in the Jaunty Kernel as well.

linux-image-2.6.28-7-generic:
  Installed: 2.6.28-7.20
  Candidate: 2.6.28-7.20

I've attached what I believe the relevant section of dmesg to be.

Revision history for this message
amaxtt (amaxtt) wrote :

same at me
ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?

jaunty kernel.

waiting for FIX

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Everyone,

I wanted to point out the following comment from the upstream bug report:

http://bugzilla.kernel.org/show_bug.cgi?id=8718#c22

">ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ffc00000-0x00000000ffffffff - kernel bug?
This doesn't break anything. It's just a warning, we could remove it completely. Did you see real breakage?"

Anyone experiencing issues, it would probably be better if you opened a new separate bug report as it is not likely related to this warning message.

Niko_Thien, since you are the original bug reporter, do you still experience graphics issues with the most recent Intrepid Ibex 8.10 release? If so, can you test the latest pre-release of Jaunty 9.04, currently Alpha 5 - http://cdimage.ubuntu.com/releases/jaunty/ . Please let us know your results. Thanks.

Changed in linux:
status: Confirmed → Incomplete
Changed in linux:
status: Unknown → Invalid
Revision history for this message
argos (argos66) wrote :

HI all,

Same problem.
But with a Call Trace (on a dmesg output) :

[ 19.058764] ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?
[ 19.060667] resource map sanity check conflict: 0xff000000 0xffffffff 0xfff80000 0xfff80fff pnp 00:0b
[ 19.062555] ------------[ cut here ]------------
[ 19.064442] WARNING: at /build/buildd/linux-2.6.28/arch/x86/mm/ioremap.c:226 __ioremap_caller+0x349/0x390()
[ 19.066397] Modules linked in: ck804xrom(+) mtd chipreg map_funcs nvidia(P+) snd_page_alloc k8temp usbhid forcedeth vesafb fbcon tileblit font bitblit softcursor
[ 19.070477] Pid: 897, comm: modprobe Tainted: P 2.6.28-11-generic #37-Ubuntu
[ 19.072561] Call Trace:
[ 19.074614] [<ffffffff802509bf>] warn_on_slowpath+0x5f/0x90
[ 19.076715] [<ffffffff8022f679>] ? default_spin_lock_flags+0x9/0x10
[ 19.078811] [<ffffffff8022f679>] ? default_spin_lock_flags+0x9/0x10
[ 19.080874] [<ffffffff80236c49>] __ioremap_caller+0x349/0x390
[ 19.082903] [<ffffffffa0a2b2db>] ? ck804xrom_init_one+0x1ab/0x5c2 [ck804xrom]
[ 19.084940] [<ffffffff80236da2>] ioremap_nocache+0x12/0x20
[ 19.086932] [<ffffffffa0a2b2db>] ck804xrom_init_one+0x1ab/0x5c2 [ck804xrom]
[ 19.088945] [<ffffffffa0a31041>] init_ck804xrom+0x41/0x59 [ck804xrom]
[ 19.090946] [<ffffffffa0a31000>] ? init_ck804xrom+0x0/0x59 [ck804xrom]
[ 19.092916] [<ffffffff8020a03b>] do_one_initcall+0x3b/0x170
[ 19.094821] [<ffffffff80242502>] ? enqueue_entity+0x122/0x2b0
[ 19.096682] [<ffffffff8024872b>] ? enqueue_task_fair+0x7b/0x80
[ 19.098513] [<ffffffff8023e2f9>] ? wakeup_preempt_entity+0x59/0x60
[ 19.100355] [<ffffffff80249350>] ? check_preempt_wakeup+0x210/0x230
[ 19.102160] [<ffffffff8024a3ec>] ? try_to_wake_up+0x12c/0x2e0
[ 19.103951] [<ffffffff8027efcd>] sys_init_module+0xad/0x1e0
[ 19.105718] [<ffffffff8021253a>] system_call_fastpath+0x16/0x1b
[ 19.107443] ---[ end trace f7230b2994bbe2b6 ]---

My "uname -a" :

argos@argos-lnx /home/argos % uname -a
Linux argos-lnx 2.6.28-11-generic #37-Ubuntu SMP Mon Mar 23 16:40:00 UTC 2009 x86_64 GNU/Linux

History of incriminate file is here -> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/mtd/maps/ck804xrom.c;hb=HEAD

Full dmesg joint.
thx ...

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

@argos, as mentioned previously this is just a warning. If you saw any other ill affects you should open a new bug report. Thanks.

Revision history for this message
dadederakh (the-q123) wrote :

Warning or not, it's perturbing. I get this message with every boot in Intrepid x86_64 with 2.6.27-14-generic.

Boot with the "nosplash" parameter and see if it isn't there. Granted, as stated above it has no visible effect on my system; it would be comforting to know what it means!

Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

There seems to be two signs of problems here. One is the "ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ff000000-0x00000000ffffffff - kernel bug?" which seems to be nothing to worry about according to the above.

The other is the "resource map sanity check conflict: 0xff000000 0xffffffff 0xfff80000 0xfff80fff pnp 00:0b" which seems to have been ignored. From Google, it seems this can be the detection of a real bug in a driver, e.g. http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-10/msg08462.html

Revision history for this message
Boniek (boniek12p) wrote :

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Lucid Lynx 10.04 release - http://cdimage.ubuntu.com/releases/lucid/alpha-2/. If the issue remains in Lucid, please test the latest 2.6.32 upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . Let us know your results. Thanks.

Revision history for this message
Boniek (boniek12p) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in linux:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.