...

...

On 5/4/2009 at 12:45 PM, Jean Delvare wrote: Hi Werner,

Le dimanche 03 mai 2009, Werner LEMBERG a écrit :

...

[kernel 2.6.30-rc3-13-vanilla from factory on top of 11.1] (...) . There's a typo in a boot message:

could not finy any ACPI SRAT memory areas. ^

This one has been there for years. Thanks for reporting, I'll send a fix upstream.

I had sent one for this, already. :) Thanks Nikanth

...

. What do these messages mean?

Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods

Something I should take care of?

This is a reminder for kernel developers to update their code. As a user, you can safely ignore these messages.

...

. Ditto for this message:

Warning! ehci_hcd should always be loaded before \ uhci_hcd and ohci_hcd, not after

I'm seeing this message as well, and I am interested in the answer too. I suspect this is something the distribution and/or the kernel should take care of, rather than the user.

-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Werner LEMBERG wrote:

...

[kernel 2.6.30-rc4-14-vanilla from factory on top of 11.1]

As Greg has mentioned on another list, combining a recent factoryk ernel with 11.1 works just fine. However, there are some issues:

. With my 945GM intel graphics card, I don't get TTYs which I could switch to with Ctrl-Alt-Shift-F1, for example. Only F7 to switch back to graphics mode works fine. In particular, I don't see any boot messages at start-up. This has worked fine with a previous kernel like 2.6.27.21.

Are there new boot parameters to add or is this a bug? It seems that `vga=0x31a' fails (which yast provides) since without it I can see boot messages.

BTW, for `vga=0x31a' I get

Console: colour dummy device 80x25

in the log file, while without this parameter I get

Console: colour VGA+ 80x25

I've just upgraded to RC4, but the problem persists. This looks like a serious issue IMHO. I suspect that the responsible authors are not on this list -- whom shall I contact?

If you're testing the -vanilla kernel, that means we don't apply any patches other than ones needed to build. The right place to report regressions in mainline is on linux-kernel@vger.kernel.org. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkn/DCcACgkQLPWxlyuTD7KsgACgogrjDpP2gkUMwaVdSaJzSKEt oikAn0aW5aTh5fV83cbO+mqa2l54DBch =niow -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Werner LEMBERG wrote:

...

...

I've just upgraded to RC4, but the problem persists. This looks like a serious issue IMHO. I suspect that the responsible authors are not on this list -- whom shall I contact? If you're testing the -vanilla kernel, that means we don't apply any patches other than ones needed to build. The right place to report regressions in mainline is on linux-kernel@vger.kernel.org.

OK. Sigh. There's sooo much traffic -- I've hoped that I can avoid it :-)

Yep, but that's a benefit too since it means the people you need to reach will probably be on there - or at least someone who can ping whomever is responsible. It's convention on LKML to CC the original author and add other people as needed. LKML is mostly for developers and those who want to follow along at home. You needn't subscribe to it to post. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkn/E9wACgkQLPWxlyuTD7IgQwCdG+HI51I0LlOlyyyvjejf0hll MUcAn2+evH8aVCJYCz89uz+5O1f0/7Yo =JOo8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org

[kernel 2.6.30-rc4-14-vanilla from openSuSE factory on top of openSuSE 11.1] With my 945GM intel graphics card, I don't get TTYs which I could switch to with Ctrl-Alt-Shift-F1, for example, after X has started. Only F7 to switch back to graphics mode works fine. In particular, I don't see any boot messages at start-up. This has worked fine with a previous kernel like 2.6.27.21. Are there new boot parameters to add or is this a bug? It seems that `vga=0x31a' fails (which openSuSE's yast installer provides) since without it I can see boot messages. BTW, for `vga=0x31a' I get Console: colour dummy device 80x25 in the log file, while without this parameter I get Console: colour VGA+ 80x25 Werner -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org

[kernel 2.6.30-rc4-14-vanilla from openSuSE factory on top of openSuSE 11.1]

Oops, sorry, I've hit the send button too early without changing the email address appropriately. Werner -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org

On Mon, May 04, 2009 at 08:58:01PM +0200, Markus Koßmann wrote:

Am Montag, 4. Mai 2009 schrieb Greg KH:

...

On Mon, May 04, 2009 at 06:25:27PM +0200, Werner LEMBERG wrote:

...

[kernel 2.6.30-rc4-14-vanilla from openSuSE factory on top of openSuSE 11.1]

With my 945GM intel graphics card, I don't get TTYs which I could switch to with Ctrl-Alt-Shift-F1, for example, after X has started. Only F7 to switch back to graphics mode works fine. In particular, I don't see any boot messages at start-up. This has worked fine with a previous kernel like 2.6.27.21.

This is due to kernel mode setting and the new xorg code. It's all still being shaken out, give it a bit of time.

Are you sure ? I see that "feature" allready with 2.6.29- master_20090410180944_41da72a7-default and with nvidia graphics .

I really don't know as there's no way to know what is going on with nvidia graphics drivers :) Good luck, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org

...

...

Greg KH 04.05.09 18:18 >>> On Sun, May 03, 2009 at 01:29:58PM +0200, Werner LEMBERG wrote: . Ditto for this message:

Warning! ehci_hcd should always be loaded before \ uhci_hcd and ohci_hcd, not after

Odd, this should be resolved by the fact that we are building some of these drivers into the kernel. Or I thought we were...

Anyway, a simple line in modprobe.conf will handle this for you.

That is a certainly a temporary workaround, but not a solution (after all, the warning message has been existing for quite a while - it was introduced in .28): EHCI/OHCI/UHCI are configurable independently, and any possible config option combination should work (including e.g. USB_OHCI_HCD=y, USB_UHCI_HCD=y, and USB_EHCI_HCD=m). For the all-three-are-modules one, introducing a fake dependency would apparently be the easiest solution, but dealing with the example setting above would likely require some Kconfig games (so one can't select ehci_hcd to be a module anymore when either ohci_hcd or uhci_hcd are built-in). Once these are all consistent, that odd warning message could then also go away again. Jan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org

On Tue, May 05, 2009 at 09:34:45AM +0200, Jean Delvare wrote:

Le lundi 04 mai 2009, Greg KH a écrit :

...

On Sun, May 03, 2009 at 01:29:58PM +0200, Werner LEMBERG wrote:

...

. Ditto for this message:

Warning! ehci_hcd should always be loaded before \ uhci_hcd and ohci_hcd, not after

Odd, this should be resolved by the fact that we are building some of these drivers into the kernel. Or I thought we were...

Anyway, a simple line in modprobe.conf will handle this for you.

And that line is...?

The lines provided already today by the module-init-tools package. It's in the /etc/modprobe.d/00-system.conf file. If this is for some reason not on your system, please upgrade your version of module-init-tools to the one in FACTORY, it is correct there. Oh, if you want to type them in yourself, here is what is needed: install uhci-hcd /sbin/modprobe ehci-hcd; /sbin/modprobe --ignore-install uhci-hcd install ohci-hcd /sbin/modprobe ehci-hcd; /sbin/modprobe --ignore-install ohci-hcd thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org

Hi Greg, Le mardi 05 mai 2009, Greg KH a écrit :

On Tue, May 05, 2009 at 09:34:45AM +0200, Jean Delvare wrote:

...

Le lundi 04 mai 2009, Greg KH a écrit :

...

Anyway, a simple line in modprobe.conf will handle this for you.

And that line is...?

The lines provided already today by the module-init-tools package. It's in the /etc/modprobe.d/00-system.conf file.

If this is for some reason not on your system, please upgrade your version of module-init-tools to the one in FACTORY, it is correct there.

Oh, if you want to type them in yourself, here is what is needed:

install uhci-hcd /sbin/modprobe ehci-hcd; /sbin/modprobe --ignore-install uhci-hcd install ohci-hcd /sbin/modprobe ehci-hcd; /sbin/modprobe --ignore-install ohci-hcd

I'm running openSUSE 11.1, the lines above are in /etc/modprobe.conf, "modprobe -c" shows them, still lsmod and the kernel log agree that uhci_hcd gets loaded first, and I see the warning about it in my logs. The interesting thing is that, after unpacking the initrd, I see that the included copy of modprobe.conf does _not_ contain these lines. Something on the way is stripping them... apparently together with _all_ install rules. So apparently this is a bug in our mkinit script. OTOH I guess there is a reason why install rules are removed... Milan? -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org