|
Bugzilla – Full Text Bug Listing |
| Summary: | supressed kernel messages? | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Ioana Josephine Ciuca <Josephine_k> |
| Component: | Kernel | Assignee: | Ruediger Oertel <ro> |
| Status: | RESOLVED WORKSFORME | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Ioana Josephine Ciuca
2005-08-27 19:16:18 UTC
I'm not aware of any removed or suppressed kernel messages. Maybe somebody is changing the kernel log level from user space. Rudi, any idea? Btw, I don't think this is a MAJOR bug :/ is the kernel really the only thing that differs here ? of course different boot-scripts can have different effects ... btw: that can be changed any time at runtime: echo 7 > /proc/sysrq_trigger (or just ALT+SYSRQ-7 if sysrq is enabled) the loglevel can be adjusted in /etc/sysconfig/kernel Variable: KERNEL_LOGLEVEL Tried that. Still no luck. And without a decent logging I am not able to identify why rmmod acx_pci hangs in a D-state...neither fix my not-working acx111 wifi card...and so on. At least you could have tried probing what I wrote here (loading and unloading acx_pci) and see what i refer to. Thanks for the support... maybe this is even before the boot-scripts set the loglevel. Hubert: isn't there a cmdline option for the kernel, to set the initial loglevel to debug. Just try kernel parameter "debug" and I can load and unload acx_pci without a problem ... probably beacause I do not have the hardware. ok, we have listed all possible ways of getting more debug output from the kernel ... -> worksforme |