All updated kernels starting from 2.6.24-14 are failed too boot the system (it hangs) on my samsung Q70 laptop - reason is the problems with a driver for built-in ricoh cardreader.

Bug #216185 reported by Andrei
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I'm using Ubuntu 8.04.
All updated kernels starting from 2.6.24-14 are failed too boot the system (it hangs) on my samsung Q70 laptop - reason is the problems with a driver for built-in ricoh cardreader (ricoh-mmc driver). 2.6.24-12 kernel works fine, and cardreader is functional (at least with sdhc cards).
Kernel output:
[33.456395] ricoh-mmc: Ricoh mmc controller disabling driver
...........................
[33.475154] ricoh-mmc: Main Fireware function not found. Cannot disable driver.

system locks after the last message.

Revision history for this message
Sebastian Rode (sebastian-ro-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

Revision history for this message
Sven Voigt (sven-voigt) wrote :

Same problem on my Samsung R65 since upgrade to Heron. Booting with 2.6.22-14-generic goes well, but 2.6.24-16-generic gets stuck during boot after the same message...

Revision history for this message
Sven Voigt (sven-voigt) wrote :

And also same with linux kernel 2.6.24-17...

Revision history for this message
Sebastian Rode (sebastian-ro-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 88992, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
Sven Voigt (sven-voigt) wrote :

Hi Sebastian,

I don't think that this is a duplicate of 88992 as our laptops fail to *boot*. It's not a matter of lacking functionality... Booting 2.6.24-17 with acpi=off is OK, although the 2.6.22 kernel didn't need this.

Thank you
Sven

Revision history for this message
Sebastian Rode (sebastian-ro-deactivatedaccount) wrote :

Yes, you are right.

Changed in linux:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux:
status: Confirmed → New
Revision history for this message
Sven Voigt (sven-voigt) wrote :

Hello there,

seems that it is problem with the video module. After reading some postings I remembered that I once had the video module blacklisted. I did so again and now all the kernels boot without any problems! :-)

Is there any way to find out where the problem really lies? Is there anything I could do to support?

Regards,
Sven

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Andrei, can you try Sven's suggestion and add "blacklist ricoh_mmc" to /etc/modprobe.d/blacklist.
Sven, can you try kernel 2.6.26 with a liveCD ?

Thanks in advance.

Changed in linux:
status: New → Incomplete
Revision history for this message
pittipatti (pittipatti) wrote :

I think this bug might be a duplicate of bug #146692 which describes the freeze on a Samsung Q45.
On the q45 the last message before the freeze is the "ricoh"-message as well, but the freeze is caused by the module video.ko.

It would be interesting to know which graphics hardware is build into your notebooks, since there are different versions of these notebooks with either Intel or Nvidia graphics.

So
@ Sven and
@ Andrei:

Can you please tell if your notebook has either Intel or Nvidia-graphics? (eg. "lspci | grep VGA")

Revision history for this message
pittipatti (pittipatti) wrote :

I forgot:

If your notebook has Intel graphics, can you please boot with acpi=off and add "blacklist video" to /etc/modprobe.d/blacklist

After that please try a normal boot. Thanks.

Revision history for this message
Sven Voigt (sven-voigt) wrote :

My Samsung runs with Intel graphics and as I wrote beforte: blacklisting the *video* module did the trick. Obviuosly, my problem isn't caused by the ricoh card reader. Using acpi=off boots the laptop OK, but it drains the battery extremely fast... I also tried blacklisting the ricoh module, but that didn't help.

All the listed kernel did boot on my laptop after I blacklisted the video module. The acpi switch is not needed.

Greetings
Sven

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.

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.