Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
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: Nov 24 21:54:14 pamolin2 kernel: [<c0126e6e>] schedule+0xd4e/0xe40 Nov 24 21:54:14 pamolin2 kernel: [<c02e0e7c>] qdisc_restart+0x1c/0x1c2 Nov 24 21:54:14 pamolin2 kernel: [<c01282ee>] scheduler_tick+0x35e/0x6f0 Nov 24 21:54:14 pamolin2 kernel: [<c0134585>] schedule_timeout+0x75/0x100 Nov 24 21:54:14 pamolin2 kernel: [<c0133b20>] process_timeout+0x0/0x10 Nov 24 21:54:14 pamolin2 kernel: [<f901a624>] adpt_i2o_post_this+0x44/0xb0 [dpt_i2o] Nov 24 21:54:14 pamolin2 kernel: [<f901c9b7>] adpt_queue+0x2d7/0x420 [dpt_i2o] Nov 24 21:54:14 pamolin2 kernel: [<f90259e6>] scsi_dispatch_cmd+0x166/0x270 [scsi_mod] Nov 24 21:54:14 pamolin2 kernel: [<c026ff70>] cfq_remove_request+0x0/0xa0 Nov 24 21:54:14 pamolin2 kernel: [<f902aeee>] scsi_request_fn+0x25e/0x440 [scsi_mod] Nov 24 21:54:14 pamolin2 kernel: [<c026860d>] blk_run_queue+0x2d/0x50 Nov 24 21:54:14 pamolin2 kernel: [<f902b2c4>] scsi_end_request+0x114/0x140 [scsi_mod] Nov 24 21:54:14 pamolin2 kernel: [<f902b495>] scsi_io_completion+0x1a5/0x4f0 [scsi_mod] Nov 24 21:54:14 pamolin2 kernel: [<f9025412>] scsi_finish_command+0x82/0xf0 [scsi_mod] Nov 24 21:54:14 pamolin2 kernel: [<f9025d27>] scsi_softirq+0xc7/0xe0 [scsi_mod] Nov 24 21:54:14 pamolin2 kernel: [<c012fc72>] __do_softirq+0x62/0xd0 Nov 24 21:54:14 pamolin2 kernel: [<c012fd0d>] do_softirq+0x2d/0x40 Nov 24 21:54:14 pamolin2 kernel: [<c02cb1c8>] __lock_sock+0x78/0xb0 Nov 24 21:54:14 pamolin2 kernel: [<c012a7f0>] autoremove_wake_function+0x0/0x40 Nov 24 21:54:14 pamolin2 kernel: [<c02ceba2>] skb_copy_datagram_iovec+0x42/0x200 Nov 24 21:54:14 pamolin2 kernel: [<c0122081>] __wake_up_common+0x31/0x70 Nov 24 21:54:14 pamolin2 kernel: [<c012a7f0>] autoremove_wake_function+0x0/0x40 Nov 24 21:54:14 pamolin2 kernel: [<c02f7370>] tcp_recvmsg+0x250/0x970 Nov 24 21:54:14 pamolin2 kernel: [<c02cb23b>] lock_sock+0x3b/0x40 Nov 24 21:54:14 pamolin2 kernel: [<c02f714f>] tcp_recvmsg+0x2f/0x970 Nov 24 21:54:14 pamolin2 kernel: [<c017b604>] bio_hw_segments+0x14/0x20 Nov 24 21:54:14 pamolin2 kernel: [<c02649ea>] elv_merged_request+0xa/0x20 Nov 24 21:54:14 pamolin2 kernel: [<c0268bfb>] __make_request+0x52b/0x530 Nov 24 21:54:14 pamolin2 kernel: [<c012a7f0>] autoremove_wake_function+0x0/0x40 Nov 24 21:54:14 pamolin2 kernel: [<c0316d98>] inet_recvmsg+0x48/0x70 Nov 24 21:54:14 pamolin2 kernel: [<c02c853c>] sock_recvmsg+0x12c/0x190 Nov 24 21:54:14 pamolin2 kernel: [<f9190ae3>] __split_bio+0x363/0x4b0 [dm_mod] Nov 24 21:54:14 pamolin2 kernel: [<f9190de1>] dm_request+0xc1/0xf0 [dm_mod] Nov 24 21:54:14 pamolin2 kernel: [<c012a7f0>] autoremove_wake_function+0x0/0x40 Nov 24 21:54:14 pamolin2 kernel: [<f951de2c>] drbd_recv+0x8c/0x190 [drbd] Nov 24 21:54:14 pamolin2 kernel: [<f951df4d>] drbd_recv_header+0x1d/0xe0 [drbd] Nov 24 21:54:14 pamolin2 kernel: [<f9522830>] receive_DataRequest+0x0/0x750 [drbd] Nov 24 21:54:14 pamolin2 kernel: [<f9522830>] receive_DataRequest+0x0/0x750 [drbd] Nov 24 21:54:14 pamolin2 kernel: [<f9521fa9>] drbdd_init+0x89/0x2e0 [drbd] Nov 24 21:54:14 pamolin2 kernel: [<f952a379>] drbd_thread_setup+0x89/0x100 [drbd] Nov 24 21:54:14 pamolin2 kernel: [<f952a2f0>] drbd_thread_setup+0x0/0x100 [drbd] Nov 24 21:54:14 pamolin2 kernel: [<c0107005>] kernel_thread_helper+0x5/0x10 Any hints? cheers Stefan -------- Original Message -------- Subject: Re: Re-6: [DRBD-user] drbd freezes completely! (19-Nov-2005 15:59) From: Philipp Reisner <philipp.reisner at linbit.com> To: drbd-user at lists.linbit.com > > > > > > Any suggestions? > > > > > > > > > > What means "freezes completely" ? > > > > > - What is on the screen > > > > > > > > no error messages > > > > > > > > > - does it respond to key strokes > > > > > > > > no > > > > > > > > > - does it respond to pings > > > > > > > > no > > > > > > > > > - does it toggle the keyboard leds when you press "Num-Lock" etc.. > > > > > > > > no > > > > > > > > no log entries. Note with nmi_watchdog=1 there is no addintional > > > > information available! > > > > > > Please try to reproduce the freeze with an UP kernel. > > > > > > > As I already mentioned, I tried vanilla 2.6.13 without success. > > UP stands for 'uniprocessor' as opposition to SMP 'symmetric multi > processing'. This does not say anthing about vanilla or vendor kernel. > In one of your posts you state that you run the SUSE SLES9 SP2/2.6.5.-191- > smp > kernel. What I asked you to do, is to run a kernel that was build for > a single CPU machine. > > What I am trying to find out if your lockup is a lockup on a > spinlock or on an other synchronousation primitive. > > But your description so far makes no sense at all. > > If it is on a semaphore/wait queue etc... it should respond to pings > and key strokes. > > If it is on a spinlock... it should OOPS when booted with "nmi_watchdog=1" > > If it is on a spinlock the lockup will simply go away when you run on only > a singe CPU (I.e. an UP kernel) > > It looks like if your machine freezes due to some other reason, i.e. "bug" > on the PCI bus... etc. Actually your observation that it does not lock > up when it runs slower follows that pattern. > > -Phil > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > > To: philipp.reisner at linbit.com Cc: drbd-user at lists.linbit.com To: philipp.reisner at linbit.com Cc: drbd-user at lists.linbit.com