From: Stas Sergeev <stsp@aknet.ru>
To: Linux kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: 2.6.18-mm1 (Oops in sata_nv)
Date: Tue, 26 Sep 2006 22:17:54 +0400 [thread overview]
Message-ID: <45196ED2.90405@aknet.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
Hi.
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18/2.6.18-mm1/
Not that I've been able to run -mm for the
last few months, but now at least I've got
an oops, which is better than nothing. :)
Attached. Any guesses, or should I start the
binary-search?
[-- Attachment #2: a --]
[-- Type: text/plain, Size: 3173 bytes --]
hdc: PHILIPS DROM6216, ATAPI CD/DVD-ROM drive
hdd: _NEC DVD_RW ND-4551A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: ATAPI 16X DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 32X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
usbcore: registered new interface driver libusual
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
TCP bic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
powernow-k8: Found 2 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ processors (version 2.00.00)
powernow-k8: 0 : fid 0xc (2000 MHz), vid 0x8
powernow-k8: 1 : fid 0xa (1800 MHz), vid 0xa
powernow-k8: 2 : fid 0x2 (1000 MHz), vid 0x12
ACPI: (supports S0 S3 S4 S5)
Freeing unused kernel memory: 220k freed
Write protecting the kernel read-only data: 457k
SCSI subsystem initialized
ACPI: PCI Interrupt Link [APSI] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [APSI] -> GSI 22 (level, low) -> IRQ 22
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD800 irq 22
general protection fault: 0000 [1] SMP
last sysfs file: /block/ram0/removable
CPU 1
Modules linked in: sata_nv libata sd_mod scsi_mod
Pid: 379, comm: insmod Not tainted 2.6.18-mm1 #3
RIP: 0010:[<ffffffff88031728>] [<ffffffff88031728>] :libata:ata_device_add+0x1c8/0x560
RSP: 0018:ffff81003fde9be8 EFLAGS: 00010246
RAX: 48000001f8b38d48 RBX: 0000000000000001 RCX: 0000000000000001
RDX: ffff81003f8eb000 RSI: ffff81003f8eb118 RDI: ffff81003f6185d0
RBP: ffff81003fde9c58 R08: 0000000000000000 R09: ffff81003f618c58
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000bf2
R13: 00000000000009f0 R14: ffff81003f6185d0 R15: 0000000000000001
FS: 000000000057b850(0063) GS:ffff810037ffb440(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000000065aea0 CR3: 000000003f85f000 CR4: 00000000000006e0
Process insmod (pid: 379, threadinfo ffff81003fde8000, task ffff81003fba3040)
Stack: 000000000000d800 ffff810000000016 ffff81003f8eb000 ffff810037ee9440
ffff810037ec8070 0000001688047720 0000000000000001 ffff810037ec8000
ffff81003fde9c58 ffff810037ec8000 0000000000000000 ffffffff88047720
Call Trace:
[<ffffffff88047640>] :sata_nv:nv_init_one+0x190/0x1f0
[<ffffffff8036dc2d>] pci_device_probe+0x5d/0xa0
[<ffffffff803d7555>] really_probe+0x65/0x100
[<ffffffff803d768c>] driver_probe_device+0x9c/0xb0
[<ffffffff803d77f3>] __driver_attach+0xa3/0xf0
[<ffffffff803d691f>] bus_for_each_dev+0x4f/0x80
[<ffffffff803d740c>] driver_attach+0x1c/0x20
[<ffffffff803d6d0f>] bus_add_driver+0x7f/0x1d0
[<ffffffff803d7ad9>] driver_register+0x89/0x90
[<ffffffff8036de9b>] __pci_register_driver+0x8b/0xb0
[<ffffffff8804b017>] :sata_nv:nv_init+0x17/0x19
[<ffffffff802b6b33>] sys_init_module+0x17b3/0x19b0
[<ffffffff8026711e>] system_call+0x7e/0x83
[<000000000040c8da>]
Code: ff 90 f8 00 00 00 85 c0 0f 85 c3 02 00 00 41 83 ff 01 75 17
RIP [<ffffffff88031728>] :libata:ata_device_add+0x1c8/0x560
RSP <ffff81003fde9be8>
next reply other threads:[~2006-09-26 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 18:17 Stas Sergeev [this message]
2006-09-26 18:23 ` 2.6.18-mm1 (Oops in sata_nv) Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45196ED2.90405@aknet.ru \
--to=stsp@aknet.ru \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox