Re: [LinuxBIOS] pc partitoin magic number not found?

[Uwe Hermann]

Hi Jon,

you noted that you work on the Intel 82801DB:
http://linuxbios.org/index.php?title=Supported_Chipsets_and_Devices&curi...

Please have a look at the 82801DBM code before, that's at the very least
very similar, maybe it even already supports the 82801DB, too(?)

Uwe.

[LinuxBIOS] pc partitoin magic number not found?

[Jon Dufresne]

Thanks, Uwe.

I used the 82801dbm as a starting ground. I've already had to change a
few things such as device IDs.

I know something somewhere isn't right because I get a kernel panic
anytime I modprobe a kernel module that relates to a device in the
southbridge. Since I'm responding I'll post the kernel panic in case
someone has an idea. This example is trying to bring up the sound
device. If I remove all module loading during init, I can get to a
single user prompt.

Anyway thanks for the tip.

Unable to handle kernel paging request at virtual address 019b2005
 printing eip:
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: snd_intel8x0 snd_ac97_codec snd_pcm_oss
snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart
snd_rawmidi snd_seq_device snd soundcore floppy ext3 jbd
CPU:    0
EIP:    0060:[<c0129fe0>]    Not tainted VLI
EFLAGS: 00010202   (2.6.9-42.EL)
EIP is at __request_resource+0x24/0x41
eax: 019b2001   ebx: c1ab0460   ecx: c036849c   edx: c0004014
esi: f02021ff   edi: f0202000   ebp: f0202000   esp: c1a1de80
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 1186, threadinfo=c1a1d000 task=c1a2c170)
Stack: c1ab0460 c036849c c1ab047c c012a27c dff4c800 00000200 000001ff 00000002
       dff4c800 c1a7dc24 c01f02a0 c1a7dc24 00000002 c1a7dc24 dff4c800 f885d270
       c01f033c c1a7dc00 dfce2400 dff4c800 f8858c73 00000001 c1a7dc00 c1a7dc00
Call Trace:
 [<c012a27c>] __request_region+0x52/0x74
 [<c01f02a0>] pci_request_region+0x82/0xf2
 [<c01f033c>] pci_request_regions+0x14/0x37
 [<f8858c73>] snd_intel8x0_create+0x104/0x403 [snd_intel8x0]
 [<f885903c>] snd_intel8x0_probe+0xca/0x21a [snd_intel8x0]
 [<c01f1b09>] pci_device_probe_static+0x2a/0x3d
 [<c01f1b37>] __pci_device_probe+0x1b/0x2c
 [<c01f1b63>] pci_device_probe+0x1b/0x2d
 [<c0252157>] bus_match+0x27/0x45
 [<c0252220>] driver_attach+0x37/0x66
 [<c02525d5>] bus_add_driver+0x77/0x97
 [<c02529f0>] driver_register+0x51/0x58
 [<c01f1d21>] pci_register_driver+0x85/0xa1
 [<f881400a>] alsa_card_intel8x0_init+0xa/0x39 [snd_intel8x0]
 [<c01410b6>] sys_init_module+0xe9/0x1d0
 [<c0318d93>] syscall_call+0x7/0xb
Code: 84 36 c0 5b 89 d0 c3 57 89 c1 56 53 8b 7a 04 89 d3 8b 72 08 39
fe 72 2c 3b 79 04 72 27 3b 71 08 77 22 8d 51 18 8b 02 85 c0 74 05 <39>
70 04 76 0c 89 43 14 31 c0 89 1a 89 4b 10 eb 08 39 78 08
 <0>Fatal exception: panic in 5 seconds
Kernel panic - not syncing: Fatal exception

Thanks for the tip.

On 12/13/06, Uwe Hermann  wrote:
> Hi Jon,
>
> you noted that you work on the Intel 82801DB:
> http://linuxbios.org/index.php?title=Supported_Chipsets_and_Devices&curi...
>
> Please have a look at the 82801DBM code before, that's at the very least
> very similar, maybe it even already supports the 82801DB, too(?)
> Uwe.
>
> http://www.hermann-uwe.de  | http://www.holsham-traders.de
> http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFFgD4CXdVoV3jWIbQRAk0KAJ9J8VboHY4II7umgiNPmS1TIVDynQCfT+sh
> IcESivY9FsYMzj1HaUQdhP4=
> =JSxz
> -----END PGP SIGNATURE-----

[LinuxBIOS] pc partitoin magic number not found?

[Adam Talbot]

Point filo to boot off of memtest.  I would look at memory.  Just an
idea, and its an easy test.
-Adam

Jon Dufresne wrote:
> Thanks, Uwe.
>
> I used the 82801dbm as a starting ground. I've already had to change a
> few things such as device IDs.
>
> I know something somewhere isn't right because I get a kernel panic
> anytime I modprobe a kernel module that relates to a device in the
> southbridge. Since I'm responding I'll post the kernel panic in case
> someone has an idea. This example is trying to bring up the sound
> device. If I remove all module loading during init, I can get to a
> single user prompt.
>
> Anyway thanks for the tip.
>
> Unable to handle kernel paging request at virtual address 019b2005
>  printing eip:
> *pde = 00000000
> Oops: 0000 [#1]
> Modules linked in: snd_intel8x0 snd_ac97_codec snd_pcm_oss
> snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart
> snd_rawmidi snd_seq_device snd soundcore floppy ext3 jbd
> CPU:    0
> EIP:    0060:[<c0129fe0>]    Not tainted VLI
> EFLAGS: 00010202   (2.6.9-42.EL)
> EIP is at __request_resource+0x24/0x41
> eax: 019b2001   ebx: c1ab0460   ecx: c036849c   edx: c0004014
> esi: f02021ff   edi: f0202000   ebp: f0202000   esp: c1a1de80
> ds: 007b   es: 007b   ss: 0068
> Process modprobe (pid: 1186, threadinfo=c1a1d000 task=c1a2c170)
> Stack: c1ab0460 c036849c c1ab047c c012a27c dff4c800 00000200 000001ff 00000002
>        dff4c800 c1a7dc24 c01f02a0 c1a7dc24 00000002 c1a7dc24 dff4c800 f885d270
>        c01f033c c1a7dc00 dfce2400 dff4c800 f8858c73 00000001 c1a7dc00 c1a7dc00
> Call Trace:
>  [<c012a27c>] __request_region+0x52/0x74
>  [<c01f02a0>] pci_request_region+0x82/0xf2
>  [<c01f033c>] pci_request_regions+0x14/0x37
>  [<f8858c73>] snd_intel8x0_create+0x104/0x403 [snd_intel8x0]
>  [<f885903c>] snd_intel8x0_probe+0xca/0x21a [snd_intel8x0]
>  [<c01f1b09>] pci_device_probe_static+0x2a/0x3d
>  [<c01f1b37>] __pci_device_probe+0x1b/0x2c
>  [<c01f1b63>] pci_device_probe+0x1b/0x2d
>  [<c0252157>] bus_match+0x27/0x45
>  [<c0252220>] driver_attach+0x37/0x66
>  [<c02525d5>] bus_add_driver+0x77/0x97
>  [<c02529f0>] driver_register+0x51/0x58
>  [<c01f1d21>] pci_register_driver+0x85/0xa1
>  [<f881400a>] alsa_card_intel8x0_init+0xa/0x39 [snd_intel8x0]
>  [<c01410b6>] sys_init_module+0xe9/0x1d0
>  [<c0318d93>] syscall_call+0x7/0xb
> Code: 84 36 c0 5b 89 d0 c3 57 89 c1 56 53 8b 7a 04 89 d3 8b 72 08 39
> fe 72 2c 3b 79 04 72 27 3b 71 08 77 22 8d 51 18 8b 02 85 c0 74 05 <39>
> 70 04 76 0c 89 43 14 31 c0 89 1a 89 4b 10 eb 08 39 78 08
>  <0>Fatal exception: panic in 5 seconds
> Kernel panic - not syncing: Fatal exception
>
> Thanks for the tip.
>
> On 12/13/06, Uwe Hermann  wrote:
> > Hi Jon,
> >
> > you noted that you work on the Intel 82801DB:
> > http://linuxbios.org/index.php?title=Supported_Chipsets_and_Devices&curi...
> >
> > Please have a look at the 82801DBM code before, that's at the very least
> > very similar, maybe it even already supports the 82801DB, too(?)
> > Uwe.
> >
> > http://www.hermann-uwe.de  | http://www.holsham-traders.de
> > http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.6 (GNU/Linux)
> >
> > iD8DBQFFgD4CXdVoV3jWIbQRAk0KAJ9J8VboHY4II7umgiNPmS1TIVDynQCfT+sh
> > IcESivY9FsYMzj1HaUQdhP4=
> > =JSxz
> > -----END PGP SIGNATURE-----

[LinuxBIOS] pc partitoin magic number not found?

[Jon Dufresne]

I did run a memtest and after 1 pass I received 0 errors. Should I run
it longer than one pass?

Jon

On 12/13/06, Adam Talbot  wrote:
> Point filo to boot off of memtest.  I would look at memory.  Just an
> idea, and its an easy test.
> -Adam
>
> Jon Dufresne wrote:
> > Thanks, Uwe.
> >
> > I used the 82801dbm as a starting ground. I've already had to change a
> > few things such as device IDs.
> >
> > I know something somewhere isn't right because I get a kernel panic
> > anytime I modprobe a kernel module that relates to a device in the
> > southbridge. Since I'm responding I'll post the kernel panic in case
> > someone has an idea. This example is trying to bring up the sound
> > device. If I remove all module loading during init, I can get to a
> > single user prompt.
> >
> > Anyway thanks for the tip.
> >
> > Unable to handle kernel paging request at virtual address 019b2005
> >  printing eip:
> > *pde = 00000000
> > Oops: 0000 [#1]
> > Modules linked in: snd_intel8x0 snd_ac97_codec snd_pcm_oss
> > snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart
> > snd_rawmidi snd_seq_device snd soundcore floppy ext3 jbd
> > CPU:    0
> > EIP:    0060:[<c0129fe0>]    Not tainted VLI
> > EFLAGS: 00010202   (2.6.9-42.EL)
> > EIP is at __request_resource+0x24/0x41
> > eax: 019b2001   ebx: c1ab0460   ecx: c036849c   edx: c0004014
> > esi: f02021ff   edi: f0202000   ebp: f0202000   esp: c1a1de80
> > ds: 007b   es: 007b   ss: 0068
> > Process modprobe (pid: 1186, threadinfo=c1a1d000 task=c1a2c170)
> > Stack: c1ab0460 c036849c c1ab047c c012a27c dff4c800 00000200 000001ff 00000002
> >        dff4c800 c1a7dc24 c01f02a0 c1a7dc24 00000002 c1a7dc24 dff4c800 f885d270
> >        c01f033c c1a7dc00 dfce2400 dff4c800 f8858c73 00000001 c1a7dc00 c1a7dc00
> > Call Trace:
> >  [<c012a27c>] __request_region+0x52/0x74
> >  [<c01f02a0>] pci_request_region+0x82/0xf2
> >  [<c01f033c>] pci_request_regions+0x14/0x37
> >  [<f8858c73>] snd_intel8x0_create+0x104/0x403 [snd_intel8x0]
> >  [<f885903c>] snd_intel8x0_probe+0xca/0x21a [snd_intel8x0]
> >  [<c01f1b09>] pci_device_probe_static+0x2a/0x3d
> >  [<c01f1b37>] __pci_device_probe+0x1b/0x2c
> >  [<c01f1b63>] pci_device_probe+0x1b/0x2d
> >  [<c0252157>] bus_match+0x27/0x45
> >  [<c0252220>] driver_attach+0x37/0x66
> >  [<c02525d5>] bus_add_driver+0x77/0x97
> >  [<c02529f0>] driver_register+0x51/0x58
> >  [<c01f1d21>] pci_register_driver+0x85/0xa1
> >  [<f881400a>] alsa_card_intel8x0_init+0xa/0x39 [snd_intel8x0]
> >  [<c01410b6>] sys_init_module+0xe9/0x1d0
> >  [<c0318d93>] syscall_call+0x7/0xb
> > Code: 84 36 c0 5b 89 d0 c3 57 89 c1 56 53 8b 7a 04 89 d3 8b 72 08 39
> > fe 72 2c 3b 79 04 72 27 3b 71 08 77 22 8d 51 18 8b 02 85 c0 74 05 <39>
> > 70 04 76 0c 89 43 14 31 c0 89 1a 89 4b 10 eb 08 39 78 08
> >  <0>Fatal exception: panic in 5 seconds
> > Kernel panic - not syncing: Fatal exception
> >
> > Thanks for the tip.
> >
> > On 12/13/06, Uwe Hermann  wrote:
> > > Hi Jon,
> > >
> > > you noted that you work on the Intel 82801DB:
> > > http://linuxbios.org/index.php?title=Supported_Chipsets_and_Devices&curi...
> > >
> > > Please have a look at the 82801DBM code before, that's at the very least
> > > very similar, maybe it even already supports the 82801DB, too(?)
> > > Uwe.
> > >
> > > http://www.hermann-uwe.de  | http://www.holsham-traders.de
> > > http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
> > >
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.6 (GNU/Linux)
> > >
> > > iD8DBQFFgD4CXdVoV3jWIbQRAk0KAJ9J8VboHY4II7umgiNPmS1TIVDynQCfT+sh
> > > IcESivY9FsYMzj1HaUQdhP4=
> > > =JSxz
> > > -----END PGP SIGNATURE-----

[LinuxBIOS] pc partitoin magic number not found?

[ron minnich]

On 12/13/06, Jon Dufresne  wrote:
> I did run a memtest and after 1 pass I received 0 errors. Should I run
> it longer than one pass?

run it for 24 hours ... that's always a good test

ron

[LinuxBIOS] pc partitoin magic number not found?

[Adam Talbot]

Thats good, its just a simple test to see if memory is set up correctly.
-Adam

Jon Dufresne wrote:
> I did run a memtest and after 1 pass I received 0 errors. Should I run
> it longer than one pass?
>
> Jon
>
> On 12/13/06, Adam Talbot  wrote:
> > Point filo to boot off of memtest.  I would look at memory.  Just an
> > idea, and its an easy test.
> > -Adam
> >
> > Jon Dufresne wrote:
> > > Thanks, Uwe.
> > >
> > > I used the 82801dbm as a starting ground. I've already had to change a
> > > few things such as device IDs.
> > >
> > > I know something somewhere isn't right because I get a kernel panic
> > > anytime I modprobe a kernel module that relates to a device in the
> > > southbridge. Since I'm responding I'll post the kernel panic in case
> > > someone has an idea. This example is trying to bring up the sound
> > > device. If I remove all module loading during init, I can get to a
> > > single user prompt.
> > >
> > > Anyway thanks for the tip.
> > >
> > > Unable to handle kernel paging request at virtual address 019b2005
> > >  printing eip:
> > > *pde = 00000000
> > > Oops: 0000 [#1]
> > > Modules linked in: snd_intel8x0 snd_ac97_codec snd_pcm_oss
> > > snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart
> > > snd_rawmidi snd_seq_device snd soundcore floppy ext3 jbd
> > > CPU:    0
> > > EIP:    0060:[<c0129fe0>]    Not tainted VLI
> > > EFLAGS: 00010202   (2.6.9-42.EL)
> > > EIP is at __request_resource+0x24/0x41
> > > eax: 019b2001   ebx: c1ab0460   ecx: c036849c   edx: c0004014
> > > esi: f02021ff   edi: f0202000   ebp: f0202000   esp: c1a1de80
> > > ds: 007b   es: 007b   ss: 0068
> > > Process modprobe (pid: 1186, threadinfo=c1a1d000 task=c1a2c170)
> > > Stack: c1ab0460 c036849c c1ab047c c012a27c dff4c800 00000200
> >
> > 000001ff 00000002
> > >    dff4c800 c1a7dc24 c01f02a0 c1a7dc24 00000002 c1a7dc24
> >
> > dff4c800 f885d270
> > >    c01f033c c1a7dc00 dfce2400 dff4c800 f8858c73 00000001
> >
> > c1a7dc00 c1a7dc00
> > > Call Trace:
> > >  [<c012a27c>] __request_region+0x52/0x74
> > >  [<c01f02a0>] pci_request_region+0x82/0xf2
> > >  [<c01f033c>] pci_request_regions+0x14/0x37
> > >  [<f8858c73>] snd_intel8x0_create+0x104/0x403 [snd_intel8x0]
> > >  [<f885903c>] snd_intel8x0_probe+0xca/0x21a [snd_intel8x0]
> > >  [<c01f1b09>] pci_device_probe_static+0x2a/0x3d
> > >  [<c01f1b37>] __pci_device_probe+0x1b/0x2c
> > >  [<c01f1b63>] pci_device_probe+0x1b/0x2d
> > >  [<c0252157>] bus_match+0x27/0x45
> > >  [<c0252220>] driver_attach+0x37/0x66
> > >  [<c02525d5>] bus_add_driver+0x77/0x97
> > >  [<c02529f0>] driver_register+0x51/0x58
> > >  [<c01f1d21>] pci_register_driver+0x85/0xa1
> > >  [<f881400a>] alsa_card_intel8x0_init+0xa/0x39 [snd_intel8x0]
> > >  [<c01410b6>] sys_init_module+0xe9/0x1d0
> > >  [<c0318d93>] syscall_call+0x7/0xb
> > > Code: 84 36 c0 5b 89 d0 c3 57 89 c1 56 53 8b 7a 04 89 d3 8b 72 08 39
> > > fe 72 2c 3b 79 04 72 27 3b 71 08 77 22 8d 51 18 8b 02 85 c0 74 05 <39>
> > > 70 04 76 0c 89 43 14 31 c0 89 1a 89 4b 10 eb 08 39 78 08
> > >  <0>Fatal exception: panic in 5 seconds
> > > Kernel panic - not syncing: Fatal exception
> > >
> > > Thanks for the tip.
> > >
> > > On 12/13/06, Uwe Hermann  wrote:
> > > > Hi Jon,
> > > >
> > > > you noted that you work on the Intel 82801DB:
> >
> > http://linuxbios.org/index.php?title=Supported_Chipsets_and_Devices&curi...
> > > > Please have a look at the 82801DBM code before, that's at the very
> >
> > least
> > > > very similar, maybe it even already supports the 82801DB, too(?)
> > > > Uwe.
> > > >
> > > > http://www.hermann-uwe.de  | http://www.holsham-traders.de
> > > > http://www.crazy-hacks.org |
> >
> > http://www.unmaintained-free-software.org
> > > > -----BEGIN PGP SIGNATURE-----
> > > > Version: GnuPG v1.4.6 (GNU/Linux)
> > > >
> > > > iD8DBQFFgD4CXdVoV3jWIbQRAk0KAJ9J8VboHY4II7umgiNPmS1TIVDynQCfT+sh
> > > > IcESivY9FsYMzj1HaUQdhP4=
> > > > =JSxz
> > > > -----END PGP SIGNATURE-----

[LinuxBIOS] pc partitoin magic number not found?

[Segher Boessenkool]

> I know something somewhere isn't right because I get a kernel panic
> anytime I modprobe a kernel module that relates to a device in the
> southbridge.

Any device, or just the AC'97?  Same backtrace?
> Unable to handle kernel paging request at virtual address 019b2005
> [<c012a27c>] __request_region+0x52/0x74
>  [<c01f02a0>] pci_request_region+0x82/0xf2
>  [<c01f033c>] pci_request_regions+0x14/0x37
>  [<f8858c73>] snd_intel8x0_create+0x104/0x403 [snd_intel8x0]

Try to figure out where that bad address came from (add some
printk's)?

Segher

[LinuxBIOS] pc partitoin magic number not found?

[Jon Dufresne]

Of the southbridge, I can modprobe ehci, uhci and the ide controller
(although none of them work fully, they just don't panic), the ac97
audio and the nic panic. I decided to focus on the ac97 first because
the nic is behind a PCI bridge and I wasn't sure if the crash was due
ot the nic or the bridge. However, it is very likely that these panic
for similar reason. At the bottom of my email I'll paste the kernel
panic from modprobing and I'll attach the output from linuxbios and
the kernel. I haven't tried to modprobe the ac97 modem and in the end
I'll probably disable this device.

I'll investigate that address range, thanks for the tip. I tried to
get information from this output of the panic, but I wasn't sure
exactly what it was trying to tell me. This makes a bit more sense now
that you point to this section. Are you saying add printk's to the
kernel or to linuxbios? I assume you mean lb.

Jon

# modprobe snd_intel8x0
Unable to handle kernel paging request at virtual address 019b2005
 printing eip:
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: snd_intel8x0 snd_ac97_codec snd_pcm_oss
snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart
snd_rawmidi snd_seq_device snd sounddCPU:    0
EIP:    0060:[<c0129fe0>]    Not tainted VLI
EFLAGS: 00010202   (2.6.9-42.EL)
EIP is at __request_resource+0x24/0x41
eax: 019b2001   ebx: f7a608c0   ecx: c036849c   edx: c0004014
esi: f02021ff   edi: f0202000   ebp: f0202000   esp: c1a11e80
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 2034, threadinfo=c1a11000 task=c1a2c740)
Stack: f7a608c0 c036849c f7a608dc c012a27c dff4c800 00000200 000001ff 00000002
       dff4c800 f7a53024 c01f02a0 f7a53024 00000002 f7a53024 dff4c800 f89ac270
       c01f033c f7a53000 c1a96c00 dff4c800 f89a7c73 00000001 f7a53000 f7a53000
Call Trace:
 [<c012a27c>] __request_region+0x52/0x74
 [<c01f02a0>] pci_request_region+0x82/0xf2
 [<c01f033c>] pci_request_regions+0x14/0x37
 [<f89a7c73>] snd_intel8x0_create+0x104/0x403 [snd_intel8x0]
 [<f89a803c>] snd_intel8x0_probe+0xca/0x21a [snd_intel8x0]
 [<c01f1b09>] pci_device_probe_static+0x2a/0x3d
 [<c01f1b37>] __pci_device_probe+0x1b/0x2c
 [<c01f1b63>] pci_device_probe+0x1b/0x2d
 [<c0252157>] bus_match+0x27/0x45
 [<c0252220>] driver_attach+0x37/0x66
 [<c02525d5>] bus_add_driver+0x77/0x97
 [<c02529f0>] driver_register+0x51/0x58
 [<c01f1d21>] pci_register_driver+0x85/0xa1
 [<f881400a>] alsa_card_intel8x0_init+0xa/0x39 [snd_intel8x0]
 [<c01410b6>] sys_init_module+0xe9/0x1d0
 [<c0318d93>] syscall_call+0x7/0xb
 [<c031007b>] xfrm_send_policy_notify+0x61/0x6a
Code: 84 36 c0 5b 89 d0 c3 57 89 c1 56 53 8b 7a 04 89 d3 8b 72 08 39
fe 72 2c 3b 79 04 72 27 3b 71 08 77 22 8d 51 18 8b 02 85 c0 74 05 <39>
70 04 76 0c 89 43
 <0>Fatal exception: panic in 5 seconds
Kernel panic - not syncing: Fatal exception

# modprobe e100
Unable to handle kernel paging request at virtual address 019b2005
 printing eip:
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: e100 mii dm_mirror dm_mod floppy ext3 jbd
CPU:    0
EIP:    0060:[<c0129fe0>]    Not tainted VLI
EFLAGS: 00010202   (2.6.9-42.EL)
EIP is at __request_resource+0x24/0x41
eax: 019b2001   ebx: dfce9520   ecx: c036849c   edx: c0004014
esi: f0000fff   edi: f0000000   ebp: f0000000   esp: f7a4fe8c
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 1984, threadinfo=f7a4f000 task=c1a4f320)
Stack: dfce9520 c036849c dfce953c c012a27c dff4c000 00001000 00000fff 00000000
       dff4c000 f89932d3 c01f02a0 f89932d3 00000000 f89932d3 dff4c000 f7a9e280
       c01f033c 00000000 dff4c044 f7a9e00d f8992146 f7a9e000 f8996164 dff4c000
Call Trace:
 [<c012a27c>] __request_region+0x52/0x74
 [<c01f02a0>] pci_request_region+0x82/0xf2
 [<c01f033c>] pci_request_regions+0x14/0x37
 [<f8992146>] e100_probe+0x193/0x61d [e100]
 [<c0185447>] dput+0x33/0x423
 [<c01f1b09>] pci_device_probe_static+0x2a/0x3d
 [<c01f1b37>] __pci_device_probe+0x1b/0x2c
 [<c01f1b63>] pci_device_probe+0x1b/0x2d
 [<c0252157>] bus_match+0x27/0x45
 [<c0252220>] driver_attach+0x37/0x66
 [<c02525d5>] bus_add_driver+0x77/0x97
 [<c02529f0>] driver_register+0x51/0x58
 [<c01f1d21>] pci_register_driver+0x85/0xa1
 [<f8814041>] e100_init_module+0x41/0x4c [e100]
 [<c01410b6>] sys_init_module+0xe9/0x1d0
 [<c0318d93>] syscall_call+0x7/0xb
Code: 84 36 c0 5b 89 d0 c3 57 89 c1 56 53 8b 7a 04 89 d3 8b 72 08 39
fe 72 2c 3b 79 04 72 27 3b 71 08 77 22 8d 51 18 8b 02 85 c0 74 05 <39>
70 04 76 0c 89 43
 <0>Fatal exception: panic in 5 seconds
Kernel panic - not syncing: Fatal exception