Re: Woke up to a crashed kernet this morning - nVidia is crap
On Thu, Aug 02, 2007 at 07:46:49AM -0700, Marc Perkel wrote: > OK - so the driver I downloaded from nVidia to fix > their problem I was having with the video installed > drivers for everything? I'm really getting to dislike > nVidia. It installs a kernel module just for the video card. Nothing else. But being a kernel module means any bugs in it could mess up other stuff in the kernel. Now if you can reproduce the crash without the nvidia module, then you have something to report. For what it is worth, it seems the nvidia module has very rarely been the cause of crashes, but since you can never tell, it is best to reproduce the problem without it to be sure. -- Len Sorensen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Woke up to a crashed kernet this morning - nVidia is crap
OK - so the driver I downloaded from nVidia to fix their problem I was having with the video installed drivers for everything? I'm really getting to dislike nVidia. --- Michal Piotrowski <[EMAIL PROTECTED]> wrote: > > Nvidia binary crap > > "When you are using a binary driver, the kernel > is "tainted", > which means that the source > of possible problems may be unrelated to the kernel > code (see > https://secure-support. > novell.com/KanisaPlatform/Publishing/250/3582750_f.SAL_Public.html > for more de- > tails). You can check whether or not the kernel was > tainted when the > problem occurred by > looking at the corresponding error message. If can > you see something > similar to the following > line: > EIP: 0060:[]Tainted: P > VLI > (the word Tainted is crucial here), the kernel was > tainted and most > probably the kernel > developers will not be able to help you. In that > case you should try > to reproduce the problem > without the binary driver loaded. Moreover, if the > problem does not > occur without it, you > should send a bug report to the creators of the > binary driver and ask > them to ï¬x it. > In the ï¬le Documentation/oops-tracing.txt, > included in the kernel > sources, there is a > list of reasons why the kernel can be considered as > tainted. As > follows from this document, > the presence of a binary module is not the only > possible reason of > tainting the kernel, but > in practice it turns out to be the most frequent > one. Generally, you > should avoid reporting > problems in tainted kernels to the LKML (or to the > kernel developers > in general) and the > problems related to binary drivers should be > reported to their providers." > > -- Linux Kernel Tester's Guide > > Regards, > Michal > > -- > LOG > http://www.stardust.webpages.pl/log/ > Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Woke up to a crashed kernet this morning
Found this in the log. Running 2.6.22,1,41,fc7 - I had just upgraded the kernel last night using yum. And - I was running a lot of backups using rsync and was backing up to a usb connected drive. I'm not sure which event triggered it but I'm guessing the latter in that it's something I rarely do using usb. Aug 2 01:54:09 bigdog kernel: [ cut here ] Aug 2 01:54:10 bigdog kernel: kernel BUG at fs/jbd/journal.c:568! Aug 2 01:54:10 bigdog kernel: invalid opcode: [1] SMP Aug 2 01:54:10 bigdog kernel: last sysfs file: /block/sde/size Aug 2 01:54:10 bigdog kernel: CPU 0 Aug 2 01:54:10 bigdog kernel: Modules linked in: iptable_filter ip_tables x_tables nvidia(P)(U) autofs4 ipv6 cpufreq_ondemand dm_mirror dm_mod raid0 video sbs button dock battery ac lp loop sr_mod cdrom snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer firewire_ohci snd soundcore snd_page_alloc k8temp firewire_core crc_itu_t hwmon rtc_cmos parport_pc forcedeth i2c_nforce2 shpchp serio_raw pata_amd floppy parport i2c_core sg usb_storage sata_nv ata_generic libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd Aug 2 01:54:10 bigdog kernel: Pid: 10240, comm: kjournald Tainted: P 2.6.22.1-41.fc7 #1 Aug 2 01:54:10 bigdog kernel: RIP: 0010:[] [] :jbd:journal_next_log_block+0x47/0x91 Aug 2 01:54:10 bigdog kernel: RSP: 0018:8100bfe53e20 EFLAGS: 00010286 Aug 2 01:54:10 bigdog kernel: RAX: 0060 RBX: 8100bf841c00 RCX: 8136c308 Aug 2 01:54:10 bigdog kernel: RDX: 0001 RSI: 0082 RDI: Aug 2 01:54:10 bigdog kernel: RBP: 8100bfe53e90 R08: 8136c308 R09: Aug 2 01:54:10 bigdog kernel: R10: 0046 R11: 8101b6c2 R12: 81000fd5ad80 Aug 2 01:54:10 bigdog kernel: R13: 810007bc6e40 R14: 01fb R15: 81008ebadf94 Aug 2 01:54:11 bigdog kernel: FS: 2aac8f20() GS:813ad000() knlGS:f7fe26c0 Aug 2 01:54:11 bigdog kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Aug 2 01:54:11 bigdog kernel: CR2: 2aac6000 CR3: 000127dda000 CR4: 06e0 Aug 2 01:54:11 bigdog kernel: Process kjournald (pid: 10240, threadinfo 8100bfe52000, task 810107262000) Aug 2 01:54:11 bigdog kernel: Stack: 810007bc6e40 81006d89dde0 8100bf841c00 88029977 Aug 2 01:54:11 bigdog kernel: 8100bfe5 01f0bfe53e98 006c 008f Aug 2 01:54:11 bigdog kernel: 810107262000 810443fd 8100bfe53e78 Aug 2 01:54:11 bigdog kernel: Call Trace: Aug 2 01:54:11 bigdog kernel: [] :jbd:journal_commit_transaction+0x77d/0x106e Aug 2 01:54:11 bigdog kernel: [] autoremove_wake_function+0x0/0x2e Aug 2 01:54:11 bigdog kernel: [] :jbd:kjournald+0xb9/0x212 Aug 2 01:54:11 bigdog kernel: [] autoremove_wake_function+0x0/0x2e Aug 2 01:54:11 bigdog kernel: [] :jbd:kjournald+0x0/0x212 Aug 2 01:54:11 bigdog kernel: [] kthread+0x47/0x73 Aug 2 01:54:11 bigdog kernel: [] child_rip+0xa/0x12 Aug 2 01:54:11 bigdog kernel: [] kthread+0x0/0x73 Aug 2 01:54:11 bigdog kernel: [] child_rip+0x0/0x12 Aug 2 01:54:11 bigdog kernel: Aug 2 01:54:11 bigdog kernel: Aug 2 01:54:11 bigdog kernel: Code: 0f 0b eb fe 48 8b b3 08 01 00 00 48 ff 8b 18 01 00 00 48 8d Aug 2 01:54:11 bigdog kernel: RIP [] :jbd:journal_next_log_block+0x47/0x91 Aug 2 01:54:11 bigdog kernel: RSP And the hardware config: Aug 2 06:36:12 bigdog syslogd 1.4.2: restart. Aug 2 06:36:12 bigdog kernel: klogd 1.4.2, log source = /proc/kmsg started. Aug 2 06:36:12 bigdog kernel: Linux version 2.6.22.1-41.fc7 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Fri Jul 27 18:21:43 EDT 2007 Aug 2 06:36:12 bigdog kernel: Command line: ro root=LABEL=/ pci=nommconf vga=794 iommu=soft Aug 2 06:36:12 bigdog kernel: BIOS-provided physical RAM map: Aug 2 06:36:12 bigdog kernel: BIOS-e820: - 0009f000 (usable) Aug 2 06:36:12 bigdog kernel: BIOS-e820: 0009f000 - 000a (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: 000f - 0010 (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: 0010 - bfee (usable) Aug 2 06:36:12 bigdog kernel: BIOS-e820: bfee - bfee3000 (ACPI NVS) Aug 2 06:36:12 bigdog kernel: BIOS-e820: bfee3000 - bfef (ACPI data) Aug 2 06:36:12 bigdog kernel: BIOS-e820: bfef - bff0 (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: c000 - d000 (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: e000 - f000 (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: fec0 - 0001 (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: 0001 - 00013000 (usable) Aug 2
Woke up to a crashed kernet this morning
Found this in the log. Running 2.6.22,1,41,fc7 - I had just upgraded the kernel last night using yum. And - I was running a lot of backups using rsync and was backing up to a usb connected drive. I'm not sure which event triggered it but I'm guessing the latter in that it's something I rarely do using usb. Aug 2 01:54:09 bigdog kernel: [ cut here ] Aug 2 01:54:10 bigdog kernel: kernel BUG at fs/jbd/journal.c:568! Aug 2 01:54:10 bigdog kernel: invalid opcode: [1] SMP Aug 2 01:54:10 bigdog kernel: last sysfs file: /block/sde/size Aug 2 01:54:10 bigdog kernel: CPU 0 Aug 2 01:54:10 bigdog kernel: Modules linked in: iptable_filter ip_tables x_tables nvidia(P)(U) autofs4 ipv6 cpufreq_ondemand dm_mirror dm_mod raid0 video sbs button dock battery ac lp loop sr_mod cdrom snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer firewire_ohci snd soundcore snd_page_alloc k8temp firewire_core crc_itu_t hwmon rtc_cmos parport_pc forcedeth i2c_nforce2 shpchp serio_raw pata_amd floppy parport i2c_core sg usb_storage sata_nv ata_generic libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd Aug 2 01:54:10 bigdog kernel: Pid: 10240, comm: kjournald Tainted: P 2.6.22.1-41.fc7 #1 Aug 2 01:54:10 bigdog kernel: RIP: 0010:[8802cd3a] [8802cd3a] :jbd:journal_next_log_block+0x47/0x91 Aug 2 01:54:10 bigdog kernel: RSP: 0018:8100bfe53e20 EFLAGS: 00010286 Aug 2 01:54:10 bigdog kernel: RAX: 0060 RBX: 8100bf841c00 RCX: 8136c308 Aug 2 01:54:10 bigdog kernel: RDX: 0001 RSI: 0082 RDI: Aug 2 01:54:10 bigdog kernel: RBP: 8100bfe53e90 R08: 8136c308 R09: Aug 2 01:54:10 bigdog kernel: R10: 0046 R11: 8101b6c2 R12: 81000fd5ad80 Aug 2 01:54:10 bigdog kernel: R13: 810007bc6e40 R14: 01fb R15: 81008ebadf94 Aug 2 01:54:11 bigdog kernel: FS: 2aac8f20() GS:813ad000() knlGS:f7fe26c0 Aug 2 01:54:11 bigdog kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Aug 2 01:54:11 bigdog kernel: CR2: 2aac6000 CR3: 000127dda000 CR4: 06e0 Aug 2 01:54:11 bigdog kernel: Process kjournald (pid: 10240, threadinfo 8100bfe52000, task 810107262000) Aug 2 01:54:11 bigdog kernel: Stack: 810007bc6e40 81006d89dde0 8100bf841c00 88029977 Aug 2 01:54:11 bigdog kernel: 8100bfe5 01f0bfe53e98 006c 008f Aug 2 01:54:11 bigdog kernel: 810107262000 810443fd 8100bfe53e78 Aug 2 01:54:11 bigdog kernel: Call Trace: Aug 2 01:54:11 bigdog kernel: [88029977] :jbd:journal_commit_transaction+0x77d/0x106e Aug 2 01:54:11 bigdog kernel: [810443fd] autoremove_wake_function+0x0/0x2e Aug 2 01:54:11 bigdog kernel: [8802d0e3] :jbd:kjournald+0xb9/0x212 Aug 2 01:54:11 bigdog kernel: [810443fd] autoremove_wake_function+0x0/0x2e Aug 2 01:54:11 bigdog kernel: [8802d02a] :jbd:kjournald+0x0/0x212 Aug 2 01:54:11 bigdog kernel: [810442a8] kthread+0x47/0x73 Aug 2 01:54:11 bigdog kernel: [8100a978] child_rip+0xa/0x12 Aug 2 01:54:11 bigdog kernel: [81044261] kthread+0x0/0x73 Aug 2 01:54:11 bigdog kernel: [8100a96e] child_rip+0x0/0x12 Aug 2 01:54:11 bigdog kernel: Aug 2 01:54:11 bigdog kernel: Aug 2 01:54:11 bigdog kernel: Code: 0f 0b eb fe 48 8b b3 08 01 00 00 48 ff 8b 18 01 00 00 48 8d Aug 2 01:54:11 bigdog kernel: RIP [8802cd3a] :jbd:journal_next_log_block+0x47/0x91 Aug 2 01:54:11 bigdog kernel: RSP 8100bfe53e20 And the hardware config: Aug 2 06:36:12 bigdog syslogd 1.4.2: restart. Aug 2 06:36:12 bigdog kernel: klogd 1.4.2, log source = /proc/kmsg started. Aug 2 06:36:12 bigdog kernel: Linux version 2.6.22.1-41.fc7 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Fri Jul 27 18:21:43 EDT 2007 Aug 2 06:36:12 bigdog kernel: Command line: ro root=LABEL=/ pci=nommconf vga=794 iommu=soft Aug 2 06:36:12 bigdog kernel: BIOS-provided physical RAM map: Aug 2 06:36:12 bigdog kernel: BIOS-e820: - 0009f000 (usable) Aug 2 06:36:12 bigdog kernel: BIOS-e820: 0009f000 - 000a (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: 000f - 0010 (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: 0010 - bfee (usable) Aug 2 06:36:12 bigdog kernel: BIOS-e820: bfee - bfee3000 (ACPI NVS) Aug 2 06:36:12 bigdog kernel: BIOS-e820: bfee3000 - bfef (ACPI data) Aug 2 06:36:12 bigdog kernel: BIOS-e820: bfef - bff0 (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: c000 - d000 (reserved) Aug 2 06:36:12 bigdog kernel: BIOS-e820: e000 -
Re: Woke up to a crashed kernet this morning - nVidia is crap
OK - so the driver I downloaded from nVidia to fix their problem I was having with the video installed drivers for everything? I'm really getting to dislike nVidia. --- Michal Piotrowski [EMAIL PROTECTED] wrote: Nvidia binary crap When you are using a binary driver, the kernel is tainted, which means that the source of possible problems may be unrelated to the kernel code (see https://secure-support. novell.com/KanisaPlatform/Publishing/250/3582750_f.SAL_Public.html for more de- tails). You can check whether or not the kernel was tainted when the problem occurred by looking at the corresponding error message. If can you see something similar to the following line: EIP: 0060:[c046c7c3]Tainted: P VLI (the word Tainted is crucial here), the kernel was tainted and most probably the kernel developers will not be able to help you. In that case you should try to reproduce the problem without the binary driver loaded. Moreover, if the problem does not occur without it, you should send a bug report to the creators of the binary driver and ask them to ï¬x it. In the ï¬le Documentation/oops-tracing.txt, included in the kernel sources, there is a list of reasons why the kernel can be considered as tainted. As follows from this document, the presence of a binary module is not the only possible reason of tainting the kernel, but in practice it turns out to be the most frequent one. Generally, you should avoid reporting problems in tainted kernels to the LKML (or to the kernel developers in general) and the problems related to binary drivers should be reported to their providers. -- Linux Kernel Tester's Guide Regards, Michal -- LOG http://www.stardust.webpages.pl/log/ Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Woke up to a crashed kernet this morning - nVidia is crap
On Thu, Aug 02, 2007 at 07:46:49AM -0700, Marc Perkel wrote: OK - so the driver I downloaded from nVidia to fix their problem I was having with the video installed drivers for everything? I'm really getting to dislike nVidia. It installs a kernel module just for the video card. Nothing else. But being a kernel module means any bugs in it could mess up other stuff in the kernel. Now if you can reproduce the crash without the nvidia module, then you have something to report. For what it is worth, it seems the nvidia module has very rarely been the cause of crashes, but since you can never tell, it is best to reproduce the problem without it to be sure. -- Len Sorensen - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
