Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Am Freitag, 25. November 2005 11:55 schrieb Philipp Reisner: > Am Donnerstag, 24. November 2005 22:23 schrieben Sie: > > hi, > > > > I changed the kernel parameter from acpi=off to acpi=oldboot and now the > > system did not hang up but the following problem occurs: > > > > Nov 24 21:54:14 pamolin2 kernel: bad: scheduling while atomic! > > Nov 24 21:54:14 pamolin2 kernel: Call Trace: > > Stefan, You sent only the call trace. Could you please send the > first part of the OOPS message as well... please > Hmmm, no, sorry. This was no OOPS, this was an BUG() macro, or something... BTW, the call trace is really deep. Are you using 4K kernel stacks ? phil at mescal:~$ zgrep CONFIG_4KSTACKS /proc/config.gz # CONFIG_4KSTACKS is not set I guess that such a deep call trace might hit a 4K limit, and probably works with 8K. Maybe the other IO-scheduler (elevator) just uses a few byte less on the stack... -Phil -- : Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :